Feels Like shows on Graph but has no Legend item

I'm not sure if this is intended behavior or a bug but I noticed that the Temperature (orange dashed) and Feels Like (yellow dashed) always show on the Energy Usage graph but there is no Legend item for "Feels Like."
If you click on the Temperature legend item it will then show a Feels Like legend item that can be selected as well.
Is this maybe a Grafana limitation? Too many legend items currently? Default view has eight clickable (to start), but all show in the graph.

This was on purpose. The legend is crowded as it is. I debated on removing "feels like" altogether but ended up just hiding it to allow users to turn it off if they want. You can edit the panel and unhide the legend if you want.

Great! Wasn't sure if it was intentional or not. I definitely don't need the "feels like" data on my graph so I don't mind it not showing in the legend. Thanks for the quick response.


How will we capture the video from the camera using this library, like in the case of images?

Closed by https://github.com/Atwa/filepicker/pull/27
CC : @MihirBha


Create 0000-01-02-tmannino.md

I added an introduction file on GitHub

Completed Course, merged changes and deleted the branch


Documentation for creating webhooks is missing MessageStream

serverClient.createWebhook allows you to pass a MessageStream key in the object, in addition to Url and Triggers. However, the documentation and the wiki don't specify this.

Hi @courthead
could you share more details?
I don't see MessageStream as a parameter for create in Postmark developer docs, neither in create webhook request model. It is available only when listing webhooks. I am wondering if we missed something in the logic of the API.

You can see it here in the docs: https://postmarkapp.com/developer/api/webhooks-api#create-a-webhook

Got it, thank you, will see to resolve that today

In latest version 2.6.1 released today, we have added MessageStream to typescript model and updated documentation.


Propagate platform to all marshals.

Signed-off-by: Erik Sipsma<EMAIL_ADDRESS>Should fix the problems when running from macos.
Opened an issue for automating that: https://github.com/dagger/dagger/issues/3225
But for now verified by running directly from macos.
This will also be a little bit of setup for integration the multiplatform PR w/ the new API, so no throwaway here hopefully.
@vito the rebase w/ your PRs will be painful sadly. I had one important comment on your PR (here), but let's try to merge that first then I'll do the rebase on this one if possible.

Also @vito the linter scolded me for having too many return args from Container.Decode(), specifically when I had to ignore most of them in some calls (this linter called dogsled).
So the second commit just has Container.Decode return the whole payload object. This slightly deviates it from the pattern established elsewhere, let me know if you think that's worth re-figuring out.

Looking forward to multi-platform support being merged, I'm guessing its tests would have caught this. (It's also just, like, cool.)

Yeah we gotta settle on which approach to take (discussion) and at this point it's probably worth just rebasing it entirely on the new API since the old one's expiration date is approaching fast. Fortunately this PR is a little bit of a layup for all that.


Allow users to provide custom Y axis scale for the LineChart.

Fixes #121
Updates #111

Pull Request Test Coverage Report for Build 746

40 of 40 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 90.525%

Totals

Change from base Build 743:
0.06%

Covered Lines:
4949

Relevant Lines:
5467

💛  - Coveralls


feat : adapter count

Description
infer_adapter :

Implemented Aho Carosick algorithm, keeping in mind the time constraints O(n) time complexity for N number of adapters
here n <= 100000 and read length < 1000.
Added confidence logic.
For every run creating a file for user with counts of adapters.
Added more input parameters :

min_match :  minimum match percentage that first adapter needs to have.
factor : factor by which first adapter is greater than the second.

Unit tests :

Wrote more unit tests for infer_adapter for full coverage.

Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality
to not work as expected)
[X] Documentation update

Checklist
Please carefully read these items and tick them off if the statements are true
or do not apply.

[X] I have performed a self-review of my own code
[X] My code follows the existing coding style, lints and generates no new
warnings
[ ] I have added type annotations to all function/method signatures, and I
have added type annotations for any local variables that are non-trivial,
potentially ambiguous or might otherwise benefit from explicit typing.
[X] I have commented my code in hard-to-understand areas
[ ] I have added ["Google-style docstrings"] to all new modules, classes,
methods/functions or updated previously existing ones
[X] I have added tests that prove my fix is effective or that my feature
works
[X] New and existing unit tests pass locally with my changes and I have not
reduced the code coverage relative to the previous state
[ ] I have updated any sections of the app's documentation that are affected
by the proposed changes

Hi @uniqueg ,
As you mentioned, I have created another branch by the name adapter for the feat: infer_adapter.
Added more unit tests. Coverage is now 100 %
Fixed linting bugs.
However 2 linting type errors are still there in the build.


:bug: Alternate gold/red color for tag sources

PF Label support the following 8 colors "gold" | "red" | "blue" | "cyan" | "green" | "orange" | "purple" | "grey" .
Tag colors depends upon their TagCategory colors which are defined as either keyword names (blue, etc) or hexadecimal values (for the recent ones V3).
Therefore depending on the color of the tag the Label can be displayed with a supported color or will fall back to "grey" (Label default) when not supported.
On the other hand the requirement is to display tags from their sources and their tagCategory and to display those alternatively in gold or red. See https://github.com/konveyor/enhancements/tree/master/enhancements/autotagging for  details.

Resolves https://issues.redhat.com/browse/MTA-332

This might help :) https://github.com/migtools/lib-ui/pull/125

@mturley, thanks and nice work with the migtools/lib-ui wrapper.
Good luck with the backend change in that regard.


note which includes [[XX]] will lead to corruption after enctryption

In the attached md file, e.g., KMP算法.md, there are three references, e.g., ![[imgk1.jpg]] , ![[imgk2.jpg]] and ![[imgk3.jpg]],
these references point to 3 jpg files located in the Attachments subfolder which is kept in the same directory as the md file.

Next, I run Cryptsidian: Open Encrypt Model and type in the password Flag3Flag3Flag3. As we expected, the content of the MD file is encrypted as follows.

However, after I run Cryptsidian: Open Decrypt Model and type in the same password Flag3Flag3Flag3, the md file is still encrypted while other md files in my vault are decrypted successfully

This kind of encrypt/decrypt related corruption happend all the time and thus leads to a very bad impression of the cryptsidian. Please kindly take a look at this issue,

The Cryptsidian's version is 1.1.0


Could we add class for negative margin horitzontal/vertical like 'nh/nv'

could we have classes for negative margin vertical or horizontal like regular margin?
like:
.nh1 {
margin-right: -var(--spacing-extra-small);
margin-left: -var(--spacing-extra-small);
}

Added too much bloat for the main build based on frequency of use. Suggest adding it as a custom addition to your build.


⚠ Processors has degraded performance

In d188255, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 96 ms

Resolved: Processors performance has improved in 22e2f9b.


Run conformance periodic jobs on specific branches for 1.10

What this PR does / why we need it:
It is not necessary to run both master and release 1.10 branch
cloud-provider-openstack to test against k8s master, v1.10 and v1.11
in OpenLab periodic jobs, that allocate lots of testing vm resources.
Add branches option into job define in order to limiting specific job
just run on specific branch.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Hi @dims could you help to merged this PR, #251 have been merged for master, this for release-1.0 branch.

/ok-to-test


Move git from PACKAGES_DEV to PACKAGES for Gitlab CI Sensor

Description:
Using the upcoming Gitlab Ci Sensor it would be nice to use the 'command line' sensors. These sensors provide my local commit ID and local commit time. Read more about it here: https://old.reddit.com/r/homeassistant/comments/9m5q8k/gitlab_ci_sensor_addition_for_home_assistant/
Checklist:

[x] The code change is tested and works locally.

I'm not in favor of this, the git binary isn't needed for the gitlab ci sensor.

I agree with @michaelarnauts.

Are you going to use, or use the gitlab ci sensor? It's easy not to want what you don't need.

There's similar value for the git binary to be present for the travis ci sensor as well.
Though I would argue that it's easy enough to make a custom dockerfile based off the official one with git included. Not that git is a huge binary, but it's nice to avoid unneeded ones.

We should not merge this. This is adding development tools for a command line sensor. If we want to support command line sensors, we end up with including every binary ever out there? So no, we should not merge this. It's a slippery slope. Our container packages Home Assistant and it's requirements. You should use your own Dockerfile.


chore/auth: MAID-2503 throw informative error for container request on nonexist…

…ent containers
The current behavior is that safe_client_libs returns null pointer if access_container_fetch is called on an app with no containers.
In safe_app_nodejs, if this is the case at the time of calling getContainersPermissions then the error, Uncaught Error: reinterpret: Cannot reinterpret from NULL pointer, is returned but not handled.
In the web API under the same conditions, getContainersPermissions hangs and returns no informative error.
@bochaco This PR is a WIP because it will be an on-going exploration of where we need to handle errors and to also prompt discussion about whether we should be handling the error or if, for example, access_container_fetch should be calling a separate error callback instead of using o_cb for all responses.

Coverage increased (+0.02%) to 90.897% when pulling a31b8a77c23baee50c436dde51b78c15b778642c on hunterlester:error-mngmt into 4a1229a420060b04bfea69f1379e0cf5e887a946 on maidsafe:master.

Should access_container_fetch return an error instead of a null pointer for an empty container set for a given app?

@bochaco I've confirmed with safe-core that access_container_fetch returning a null pointer for an empty container set is appropriate. PR ready for review.

@bochaco Before I get too far into documenting errors, checkout my example that I pushed with my latest commit to see if it makes sense.


Document histograms and histogram_quantile.

@juliusv @brian-brazil

I'll comment and rework the text ASAP. Just very busy with other stuff right now. Will get back to this tomorrow or so.

 Stay tuned. :)

Sorry for the longer-then-expected delay... Here is the heavily reworked version.
Most importantly, I have created a completely new section for the delicate subject of histograms and
summaries and updated all the references.

PHAL

:+1:


Option to send Deprecation Warnings and/or Errors to Sentry, "plugin" or Script

Hej,
we have quite some deployments on a not so insignificant number of clusters. So it's "hard"/time consuming to always keep an eye on the output generated by helm.
Would it be a good idea to integrate some form of callback in Helm to signal/notify senty/slack/etc about deprecation warnings, or also errors, in a standardized way?

I don't think it's a bad idea at all.
Today, helm lint will show the warnings. You can scrape those.
To improve this, lint would need machine-readable output and would need the ability to set the kubernetes version that you're linting against.

Maybe it's a good think to improve lint too, but to be honest i would prefer "the real deal" and signal while(/after) applying.
Linting is already done in our pipelines to check if those charts "work", and I'm fine with change requests having failing lint jobs cause someone missed something - and i prefer not to see those errors in sentry or else where. But when those lint pipelines are green, those changes get merged and are used on different clusters and will not be linted again (they can't change magically, so why should we?). In the daily life cycle those charts are then applied to a cluster where we didn't "know" an update had hapend (yep, out of our reach), and that's where it would help to capture those problems and give us a heads up.

I wonder if you could implement such a thing using a plugin or post-renderer

Looks like this proposal has gone inactive. Closing.


Implement this in Ionic 2+???

Is there any way to implement this in Ionic 2+?? if yes, how??

Hi @damonsomu,
you can of course use it with Ionic 2+ (I'm using it with version 3.9.2):

install plugin via cordova or ionic cordova,
use it accessing method via window.plugins or create an Angular service as a wrapper.


Increase emphasis/visibility of version-specific nature on Config documentation

rustfmt is a highly configurable formatter that supports various configuration options that allow users to override the default formatting rules (e.g. tabs instead of spaces). The set of supported configuration options, and their associated variants/stability/etc., is tightly associated to the corresponding rustfmt version.
For example, if a new configuration option foo_bar is added during the rustfmt v1.4.30 release, foo_bar is available in version v1.4.30, but foo_bar is of course not available in earlier versions of rustfmt (rustfmt v1.4.10 has no idea what foo_bar is).
As such, it's really important that when a user is browsing the rustfmt config documentation that they are looking at the version of the config docs that maps to the version of rustfmt they are actually using. Accordingly, the config documentation website has a dropdown field that allows users to select their corresponding version of rustfmt:

Unfortunately though, many users are unaware of the need to use the correct version and end up running into issues when they try to use a newer config option that isn't available in the rustfmt version they are actually using. We've tried a couple things to address this, such as adding this section to the file  in source control which does appear a bit lower on the site for some versions, but we need to do more to make this obvious on the config site.
I'm open to any changes to the config site that makes it more visual and obvious, and helps users avoid these issues

A possible enhancement may be to add the selected version number to the heading of each config option, e.g.:

Although that does not tell the users from which version the option is available, at least it may be more clear that the option documentation is for that specific version.
I am not submitting a PR with the change, as I am not sure if this approach is acceptable.

Thanks for looking at this. I think the problem with that proposal is that it's going to be duplicative and still wouldn't itself convey the intent. I.e. folks either will already know the version relationship and this will just be noise, or they won't and still won't know what that text means.
The intent here is to loudly inform the uninformed user that configuration options can and do change from one version to the next, and users need to look at the right version of the docs

What about adding a text to each option that is was not available at the first (documented) release or is not available in the last released version?  Something like:
binop_separator(available from v<IP_ADDRESS>)
or:
binop_separator(not released)
The added text may be red or any other color to draw the user's intention.
At least the first approach may significantly increase the time of the initial page load, as it requires parsing all the versions documentations, but if it is desired then maybe it will be possible to do one time parsing for all and prepare a file with the first version for each configuration option.


Update apache-client, kinesis to 2.20.124

About this PR
📦 Updates

software.amazon.awssdk:apache-client
software.amazon.awssdk:kinesis

from 2.20.118 to 2.20.124
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #634.


Implement WebView panels and floats

Commits

Improve layout options on addWebView
Implement float layout
Stopped retrying addWebView on actual errors
Implement panel layout
Improve tests and DX on error
Fix rc-dock types

Features

Closed WebView tabs will come back on a restart.
When adding a WebView, a layout can be specified as tab (default), float or panel.
Better DX experience since addWebView errors show as errors in the browser console.
Added ts-mockito mocking library.
Added a way to extend and fix .d.ts files from packages. See the src/@types folder.

The commits have be organised into feature changes so it may be useful to review the commits separately to speedup understanding of the changes.

This change is

src/renderer/components/docking/paranext-dock-layout.component.tsx line 136 at r6 (raw file):
Previously, lyonsil wrote…
Is there a property that only exists on TabData?  I see title on TabData and nowhere else based on a (potentially naive) search online - https://github.com/ticlo/rc-dock/blob/master/src/DockData.ts#L196.  The if statement below looks kind of fragile.

I did the same search as you but somehow missed both title and content on TabData. I'm fixing in a follow-up PR. Thanks for spotting that.


Update CoreOS to 2135.6.0

Updating the CoreOS content to match the latest stable: https://coreos.com/releases/#2135.6.0

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


Document Contact Us page

Overview
Document file and code structure for Contact Us page
Action Items

[ ] Document file and code structure for Contact Us page

Resources/Instructions
Civic Tech Index Site Architecture documentation can be updated here

@bhaggya  has completed core documentation.  Future changes are possible as page functionality is updated.


Win10 - No shortcut & start menu

Just installed Atom on my Windows 10 x64, the installer goes fine but there is no entry on Start Menu or Desktop Shortcut created. Downloaded & using Atom 1.19.3.

The same issue with me.

Thanks for taking the time to contribute!
We noticed that this is a duplicate of #12124. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Make ReindexJob raise so honeybadger can notify

and sidekiq can retry
closes #1294

Tested on staging; reindexed https://dpul-staging.princeton.edu/eastasian/dashboard successfully.


Missing dependencies when running the module inside docker

We currently use https://github.com/davidalger/warden for our projects. Running npx cypress run --spec ./cypress/integration/path/to/some.spec.js leads to the following error:
Your system is missing the dependency: Xvfb

Install Xvfb and run Cypress again.

Read our documentation on dependencies for more information:

https://on.cypress.io/required-dependencies

If you are using Docker, we provide containers with all required dependencies installed.

----------

Error: spawn Xvfb ENOENT

----------

Platform: linux-x64 (CentOS - 8
)
Cypress Version: 10.3.0

I see two possible solutions to this:

Require these packages directly into warden so that each installation will have them
Update the README.md to include this so that people running into this issues should know how to fix it.

The installation instructions from the cypress website work:
apt-get install -y libgtk2.0-0 libgtk-3-0 libgbm-dev libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2 libxtst6 xauth xvfb

@Vinai true, this indeed fixed our issue. This issue is more of updating the documentation for people who use warden. The correct link for the warden fix is https://docs.cypress.io/guides/getting-started/installing-cypress#CentOS since warden uses CentOS

Ah, I'm using it on a debian based Linux distribution in CI.


crystal: 1.7 -> 1.8

Description of changes

Changelog
The key changes package-wise are the use of llvm15 and pcre2. I'm not sure if the approach I took is the best one but considering the size of the nix file, I'm leaning towards it than maintaining multiple copies of it for each version.
Why LLVM 15?
Crystal 1.8 is the first version with LLVM 15 support which includes opaque pointers. It has performance improvements including an up to 34% speed-up for release builds. You can read more on this great write-up from HertzDevil: https://crystal-lang.org/2023/03/23/llvm-opaque-pointers/
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)
[X] 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
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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

[X] Fits CONTRIBUTING.md.

12 packages failed to build:
ameba amqpcat crystal2nix icr invidious kakoune-cr lucky-cli mint oq scry shards thicket

3 packages built:
crystal crystal.bin crystal.lib

I guess not requiring pcre2 directly can't be helped, thanks for running a review!

1 package failed to build:
ameba

20 packages built:
amqpcat crystal crystal.bin crystal.lib crystal2nix crystal_1_2 crystal_1_2.bin crystal_1_2.lib crystal_1_7 crystal_1_7.bin crystal_1_7.lib icr invidious kakoune-cr lucky-cli mint oq scry shards thicket

ameba requires this patch. Otherwise, LGTM.

I'll go ahead and tag @straight-shoota in case I missed anything with the LLVM15 + pcre2 migration.
The build and most crystal 1.7 packages succeeded, however while building packages that use the crystal buildCrystalPackage passthru, pcre1 was required:
https://logs.ofborg.org/?attempt_id=01871269-0766-4496-954b-d6cb41723bc1&key=nixos%2Fnixpkgs.226371
/nix/store/f4qnwzv6y0nq8lix33jr5ykkyybs6fxf-binutils-2.40/bin/ld: cannot find -lpcre (this usually means you need to install the development package for libpcre): No such file or directory
collect2: error: ld returned 1 exit status
Error: execution of command failed with exit status 1: gcc "${@}" -o /build/source/.crystal/build-source-lib-teeplate-src-lib-file_tree-macros-directory.cr/macro_run  -rdynamic -L/nix/store/8vj98hwkr7glgkdhf345nqlkr5ldywyi-boehm-gc-8.2.2/lib -L/nix/store/pj02km2syw6xc8rdribscls9lpc5g3vr-pcre2-10.42/lib -L/nix/store/mimlcvy3miz847x4icwvi7w8vdn2i3pc-libevent-2.1.12/lib -L/nix/store/xvld1wgp4bj6cscc7in811cnq8k36hb9-libyaml-0.2.5/lib -L/nix/store/2ldgh1qis9p4zf8bgsdm7897gw8vv36g-zlib-1.2.13/lib -L/nix/store/s44s0yzxw4s7nq108css5lcqck6dg6dz-libxml2-2.10.3/lib -L/nix/store/ijk9j536zs30kha06rr966gplwxd7fbg-openssl-3.0.8/lib -lpcre -lm -lgc -lpthread -levent -lrt -lpthread -ldl

I just included pcre1 even on the 1.8 builds to fix it, not sure if it's something upstream should be aware of

@GeopJr You may want to

remove pcre from pkgs/development/compilers/crystal/default.nix, then,
add pcre2 to buildInputs in pkgs/development/compilers/crystal/build-package.nix.

pcre is needed for crystal < 1.8, the weird part is that even though lucky-cli (and any other latest crystal package that used the passthru) used crystal 1.8 - which uses pcre2 - it needed pcre1

I'm not sure it's a good idea to keep pcre as a dependency for Crystal 1.8. It should not be necessary unless a package explicitly chooses to use it over pcre2. In that case it should be added as a dependency of that particular package, not the crystal package.
Also pcre2 should not be a dependency for older releases. At the most it's useful for 1.7 because you can already opt-in to preview. But older versions have no use of pcre2.
About that failing spec, it's a bit hard to trace what exactly is being built there. I suppose it's a nix package for https://github.com/luckyframework/teeplate ? Do you know where that's defined?

Just built lucky-cli with pcre2 without any problem. For crystal <1.8 you could just choose the right pcre conditionally.

Just to keep a log of what I have committed:

initial: pcre was defined as pcre2 on crystal_1_8 and crystal - It prompt the first review to fail on all packages except crystal
https://github.com/NixOS/nixpkgs/pull/226371/commits/35f5549e29e0056eb379ad8d24475482bfd87d79: pcre2 was included in crystal but pcre1 was only used in crystal < 1.8 and not 1.8 - same issue as the initial
https://github.com/NixOS/nixpkgs/pull/226371/commits/70cc7966aa62905e6b8f06b1503fb6fe2261fdfc: pcre2 and pcre1 are included - issues got fixed

About that failing spec, it's a bit hard to trace what exactly is being built there. I suppose it's a nix package for https://github.com/luckyframework/teeplate ? Do you know where that's defined?

I don't think it has to do with teeplate specifically but rather the passthru https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/crystal/build-package.nix since it happens locally for ameba too (the passthru is used to build crystal apps and it deals with their shards (hence treeplate))

Just built lucky-cli with pcre2 without any problem.

I assume you built it without pcre included, right? Because right now it also builds but pcre is also required.

For crystal <1.8 you could just choose the right pcre conditionally.

I think the initial commit was the ideal solution - using pcre2 on crystal >= 1.8 and pcre1 on < 1.8, but building crystal packages didn't work, any guidance or suggestions on how to deal with it are welcome!

I assume you built it without pcre included, right? Because right now it also builds but pcre is also required.

Yes, without pcre.


node-exporter DaemonSet ~> Pod 'Evicted', not Replaced => Node 'Vanishes', No Rule/Alert Triggered

What did you do?
Run kube-prometheus
What did you expect to see?
Pods for node-exporter DaemonSet all up and running.
What did you see instead? Under which circumstances?
Had issues with a node -> DiskPressure which led to pods getting evicted - expected behaviour in general..
..but I noticed the pod from the DaemonSet got evicted too, yet not replaced by a new one which led to having no more metrics for that node - it kind of just vanished out of existence and didn't trigger any alerts.
That may be a rare case? But still would be great to either solve the issue with the evicted DaemonSet Pod (which may be a kubernetes native issue) - or at least catch via a rule -> alert.
Environment

Kubernetes version information:
v1.6.6

Kubernetes cluster kind:
kops

Manifests:
https://github.com/coreos/prometheus-operator/tree/master/contrib/kube-prometheus

Note: Just discovered https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/assets/prometheus/rules/node.rules
which was not triggered - for the value is not != 1 but the whole metrics just vanishes.

Thanks for bringing this up! Any failure report can potentially be a valuable alerting rule! :slightly_smiling_face:
It's a bit more complicated than that, because that rule actually triggers when all targets disappear (which usually indicates, that something is wrong with discovery). That's how this rule is intended to work currently, however, I do agree, that we should add some additional ones. We already have similar alerts for kubelets, this sounds like it would make sense to add similar ones for nodes/node-exporter. The caveat would be that we can tell how many node-exporters there should be through the metrics exposed by kube-state-metrics.
If you want to give this a go, I'd be happy to guide you.

thx, will definitely have a look!

@hartmut-pq do you think you can get to this? If not I'm happy to take over.

Hi, I think I have a solution, the rules for kubelets didn't help though - but could improve those, too...
I'm just quite busy right now - will come back to you if I can't squeeze it in... but ideally will create one/multiple PRs

Now I'm curious :wink: feel free to open multiple PRs. Just wanted to ping and see what's up, no rush. Thanks for all your efforts!

Any progress on this?

How about adding a more general rule about daemonsets? to kube-state
Something on the line of
    ALERT DaemonSetsNotScheduled
      IF kube_daemonset_status_desired_number_scheduled - kube_daemonset_status_current_number_scheduled > 0
      FOR 10m
      LABELS {
        severity = "warning"
      }
      ANNOTATIONS {
        summary = "Daemonsets not scheduled correctly",
        description = "A number of daemonsets are not scheduled."
        }

    ALERT DaemonSetsNotRunning
      IF kube_daemonset_status_desired_number_scheduled - kube_daemonset_status_number_ready > 0
      FOR 10m
      LABELS {
        severity = "warning"
      }
      ANNOTATIONS {
        summary = "Daemonsets not ready",
        description = "A number of daemonsets are not ready.."
        }

    ALERT DaemonSetsMissScheduled
      IF kube_daemonset_status_number_misscheduled > 0
      FOR 10m
      LABELS {
        severity = "warning"
      }
      ANNOTATIONS {
        summary = "Daemonsets not scheduled correctly",
        description = "A number of daemonsets are running where they are not supposed to run."
      }

All of those sound great! Could you open a PR for them @atopuzov ?
(they will have to be in the Prometheus 2.0 alerting rule format though :slightly_smiling_face: )

@brancz Will do.
I'll also try to update the charts to use the new prom 2.0 rules.

@brancz does this look ok?

I'll also try to update the charts to use the new prom 2.0 rules.

That sounds fantastic! Thanks a lot!

With #755 merged, I'll close this here.


Transition fails to render new handler

I have the following routes
var routes = [
    <Route handler={Portal}>
        <Route name="dashboard" path="/p/" handler={Dashboard} />
        <Route name="support" path="/p/support" handler={Support} />
    </Route>,

    <Route name="logout" path="/p/logout" handler={Logout} />,
    <Route name="login" path="/p/login" handler={Login} />,
    <NotFoundRoute name="not-found" handler={NotFound} />
];

In the componentDidMount method in my LoginHandler I am doing some checking for certain conditions and transitioning to the dashboard route if they are met.
The URL updates, but the page does not re-render, staying on the Login handler. If I transition to the logout path it works as expected.
I dont know enough about internals to debug further but would appreciate any assistance.

Having an array of routes is fine.
What you're describing is very basic behavior of the router that is both tested in this project and working in my apps. I'm going to need more to go on.
I'm closing the ticket but I'd like to help you get it working. Can you post some code?


chore(merge-back): 1.99.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 259ffb0a1d1400e93b7242c4c3bea76839090a6d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Proposal Template: local files to folder local

Id like to propose a subfolder for local environment files:

/config/main-local to /config/local/main
/config/params-local to /config/local/params

Why?
Within the last year, I guess I have had to click the correct file for more that 5000 times, which is in my opinion not optimal with these two files. Why?:

names start equal
main-local is grayed out because of its git ignore, making it harder to read.

Therefore I would propose to put the local files in their own folder. They aren't used that often, are grouped together on type and I dont get bothered by their git color.
Besides, Id rather save my concentration for more important stuff then picking the right files.

Well, then you may get confused when working with /config/main.php and /config/local/main.php because they have the same name.

they are hidden in their own folder so I am not disturbed by them anymore. It is not that my eyes are triggered by a folder name "local"
when talking about having these files open in the IDE, I am not so afraid. The local files are not used that often.

If you are accustomed to using keyboard shortcuts to open files instead of using mouse to choose which file to open, you won't have this problem. But anyway, this is personal preference, and I don't see there will be a unanimous solution. We will keep the current solution as is. You can adjust the file location yourself, if you prefer.

I will, thanks


[Don't merge] Nikita/Affiliates sign up flow

Changes:

...

Type of change

[ ] Bug fix
[x] New feature
[ ] Update feature
[x] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[x] Dependency update
[ ] Documentation update
[ ] Release

Please help to take a look at the inputs here, there seems to be some text that is visible.

terms & conditions link is not clickable as it will toggle the checkbox instead.

Please check the sizes for these links across the different screen widths as well especially for >1980px.

Some other pointers:

Why do we have this validation yah?

I can't switch pages on date picker
I don't see the success message upon form submission.

Some other pointers:

Why do we have this validation yah?

I can't switch pages on date picker.
I don't see the success message upon form submission.

Please also address the code smells 🙏

And lastly your responsive design is not supported down to 320px.

Please help with the conflicts 🙏


Point addition gadget impl

Implements a point addition gadget within Bulletproofs

The tests are now passing once I added the same CS to the Verifier.
Equalty seems to hold between RistrettoPoints with the Ristretto formulas to avoid modular division.
Would be nice to know if the test is correctly done in order to continue the work.

As @decentralisedkev mentioned to me, it will be a good idea to follow the guidelines stated here: https://github.com/dalek-cryptography/bulletproofs/blob/main/tests/r1cs.rs#L353 in order to have a better code which will be easier to understand and read.
So I'll make the refactor and re-request the reviews.


BZ1248991 show Input/Output counts on Assignments properties

6.4.x commit. Kris advised that the commit for BZ1248991 already on master should go in 6.4.x as well.

6.4.x: 6b1fb1e32e0b25476c11f3eb346ab97568dacea0


View upvoted listings

Give users a page to view listings they've upvoted

Hi @Winston-Hsiao ,
I'd like to work on this ticket if it's available. Let me know if you're currently working on it or if I can assist in any way.
Looking forward to contributing!

Hi @Winston-Hsiao ,
I'd like to work on this ticket if it's available. Let me know if you're currently working on it or if I can assist in any way.
Looking forward to contributing!

I'm not working on it currently, and I don't believe anyone else is, so feel free to take it!


Find out what Stripe actually puts on bank statements

And also if it is configurable.

We also need to know if it is always the same thing, currently, or if it changes. Ex: have we configured something without knowing it, but done it inconsistently?


Write a Java program to find power of a number by recursion

Description
Write a Java program to find power of a number by recursion
Power of a number is calculated by multiplying the number by itself for the given number of times. For example, 2^3 = 2 * 2 * 2 = 8.
Power of a number can be calculated by recursion. The formula is:
x^n = x * x^{n-1}

Input  : 2 3
Output : 8

How to contribute

Save the solution in FindPowerOfANumberByRecursion.java file
Add FindPowerOfANumberByRecursion.java file in find-power-of-a-number-by-recursion folder

I would like to contribute to this. Please assign this issue to me

I want to work on this issue, can you assign this to me.

!assign


renovatebot(deps): update dependency de.codecentric:spring-boot-admin-starter-server to v2.1.5

This PR contains the following updates:

Package
Update
Change

de.codecentric:spring-boot-admin-starter-server
patch
2.1.4 -> 2.1.5

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.null seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


chore: refresh monitoring deployment

Fixes #
Description
Update Prometheus and Grafana deployment to tolerate system pool taints, reference the latest dashboard, and target karpenter in kube-system namespace
How was this change tested?

make az-mon-deploy && make az-mon-access

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.235%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
37173

Relevant Lines:
39447

💛  - Coveralls


Unimplemented instruction in simarm64?

Reproduction:
% tools/build.py -mrelease -asimarm64,x64 runtime_kernel
...

% out/ReleaseX64/dart --dfe=out/ReleaseX64/gen/kernel-service.dart.snapshot --kernel-binaries=out/ReleaseX64 --strong --reify-generic-functions --limit-ints-to-64-bits tests/corelib_2/int_parse_radix_test.dart
% echo $?
0

% out/ReleaseSIMARM64/dart --dfe=out/ReleaseSIMARM64/gen/kernel-service.dart.snapshot --kernel-binaries=out/ReleaseSIMARM64 --strong --reify-generic-functions --limit-ints-to-64-bits tests/corelib_2/int_parse_radix_test.dart
Simulator hit Unimplemented instruction: at 0x7f4239ac13f4, last_pc=0x7f4239ac13f0

sim>

In debug mode
out/ReleaseSIMARM64/dart --dfe=out/ReleaseSIMARM64/gen/kernel-service.dart.snapshot --kernel-binaries=out/ReleaseSIMARM64 --strong --reify-generic-functions --limit-ints-to-64-bits tests/corelib_2/int_parse_radix_test.dart

It fails with an assertion in the assembler:
../../runtime/vm/compiler/assembler/assembler_arm64.h: 405: error: expected: ((imm & 0xfff) == 0) && (Utils::IsUint(12, imm >> 12))

Call stack:
#2  0x0000000000a78489 in dart::OS::Abort () at ../../runtime/vm/os_linux.cc:379
#3  0x0000000000dadb4b in dart::DynamicAssertionHelper::Fail (this=0x7ffff6738788,
    format=<optimized out>) at ../../runtime/platform/assert.cc:42
#4  0x0000000000c10ccd in Operand (imm=-2, this=<optimized out>)
    at ../../runtime/vm/compiler/assembler/assembler_arm64.h:405
#5  dart::FlowGraphCompiler::CopyParameters (this=<optimized out>,
    expect_type_args=<optimized out>,
    check_arguments=<error reading variable: access outside bounds of object referenced via synthetic pointer>) at ../../runtime/vm/compiler/backend/flow_graph_compiler_arm64.cc:734
#6  0x0000000000c12152 in dart::FlowGraphCompiler::CompileGraph (this=0x7ffff6738a48)
    at ../../runtime/vm/compiler/backend/flow_graph_compiler_arm64.cc:1063
#7  0x0000000000d4a640 in dart::CompileParsedFunctionHelper::Compile (this=<optimized out>,
    pipeline=0x1de0a20) at ../../runtime/vm/compiler/jit/compiler.cc:1212
#8  0x0000000000d4b864 in dart::CompileFunctionHelper (pipeline=0x1de0a20, function=...,
    optimized=<optimized out>, osr_id=-1) at ../../runtime/vm/compiler/jit/compiler.cc:1344
#9  0x0000000000d4b1b8 in dart::Compiler::CompileFunction (thread=<optimized out>, function=...)
    at ../../runtime/vm/compiler/jit/compiler.cc:1531
#10 0x000000000093bd55 in dart::DartEntry::InvokeFunction (function=..., arguments=...,
    arguments_descriptor=..., current_sp=140737328161008) at ../../runtime/vm/dart_entry.cc:122
#11 0x0000000000cef645 in dart::kernel::StreamingConstantEvaluator::RunFunction (
    this=0x7ffff673a450, function=..., arguments=..., names=...)
    at ../../runtime/vm/compiler/frontend/kernel_binary_flowgraph.cc:3266
#12 0x0000000000cef4d0 in dart::kernel::StreamingConstantEvaluator::RunFunction (
    this=<optimized out>, function=..., argument_count=<optimized out>,

Code at flow_graph_compiler_arm64.cc:734
    __ and_(R8, R8,
            Operand(Smi::RawValue(
                ArgumentsDescriptor::PositionalCountField::mask_in_place())));

was added recently in https://github.com/dart-lang/sdk/commit/a991c17dc9cc4597feaa385f0b15f2c667e83677.
It looks like the value of the mask is not a valid 12-bit immediate.
/cc @sjindel-google


Discuss: Should "datapackage-py" change the descriptors it received?

Consider the following example:
descriptor = {
    'name': 'my-datapackage',
    'resources': [
        {
            'name': 'main',
            'profile': 'tabular-data-resource',
            'data': [
                {'value': 10},
                {'value': 20},
                {'value': 30},
            ]
        }
    ]
}
dp = Package(descriptor)
assert dp.descriptor == descriptor

As a user, I'd expect the assertion to pass. However, it doesn't, because datapackage-py modifies the descriptor it received. In this case, it adds a descriptor['profile'] = 'data-package', but there were a few other cases in my tests. For example, it automatically adds 'missingValues': [''] to the schema, 'encoding': 'utf-8' to the resources, and 'format': 'default' to the resources schema's fields.
This complicates testing that the descriptor is what you expect it to be, as you have to take into account not only what you added yourself, but also what datapackage-py (which might change, causing your tests to break).
As a general rule, I think it's better not to change the user's data unless necessary. Most (all) of the examples I found were caused because datapackage-py explicitly added default values to the descriptors. I understand why this would make the datapackage-py code simpler, but then it makes my tests (as a library user) more complicated.
WDYT?

I think I agree. There should at least be a way to inspect the source descriptor, even as the representation that the library uses (and outputs) is mutated from this source.

I raised exactly the same issue today with @roll while updating ckanext-datapackager. +1 to not change the user input.

A brief history of this one that after we've started specs-v1 update there was a specs requirements to apply defaults from JSON schemas - https://github.com/frictionlessdata/implementations/issues/4. We had never discussed on which level this requirement exists (like specs requires implementations to updated descriptor or something else etc). So on implementations level we've just added descriptor mutation.
So I'm +1 on not mutating descriptor and use defaults on-demand internally. For now it's clear for me that descriptor mutation can't be a spec requirement (it's too low-level thing so I've just got it wrong). We've already ruled out for implementations normalizing things like PK/FK (string/array) on descriptor level because it could break client code. So not mutating descriptor at all makes sense also for me.

@roll I think this is worth adding to your current queue.

Frictionless Framework is designed that a user can only explicitly change metadata. This problem is resolved there


Remove buffers noAssert argument

Support for the noAssert argument dropped in the upcoming Node.js
v.10. This removes the argument to make sure everything works as it
should.
Refs: https://github.com/nodejs/node/pull/18395

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

Coverage decreased (-71.0%) to 8.036% when pulling 43b9a556599ab5af217819402fce66bd0eee6556 on BridgeAR:master into 63f11c69d87da204d7aebb4160c2d21bbfee3d4a on yahoo:master.

Coverage decreased (-71.0%) to 8.036% when pulling 43b9a556599ab5af217819402fce66bd0eee6556 on BridgeAR:master into 63f11c69d87da204d7aebb4160c2d21bbfee3d4a on yahoo:master.

Coverage decreased (-71.0%) to 8.036% when pulling 43b9a556599ab5af217819402fce66bd0eee6556 on BridgeAR:master into 63f11c69d87da204d7aebb4160c2d21bbfee3d4a on yahoo:master.

Coverage decreased (-71.0%) to 8.036% when pulling 43b9a556599ab5af217819402fce66bd0eee6556 on BridgeAR:master into 63f11c69d87da204d7aebb4160c2d21bbfee3d4a on yahoo:master.

Ping

Ping @davglass @marcelerz

PTAL
(cla: is signed but the bot does not give any updates; the CI failed due to unrelated things)


Support pystac.Item

Currently xstac writes pystac.Collection objects. The datacube extension also supports Items, so we should too.
I think the implementation will be essentially identical. All the logic around extracting STAC metadata from xarray / Zarr will be identical. The primary question is around the API.
IMO we can have one or both of:

A pair of methods like generate_stac_collection(ds, template, ...) and generate_stac_item(ds, template, ...).
A single method like generate_stac_object(ds, template) that dispatches on the type of the template.

Right now our template is a dictionary. Maybe that should be a pystac.Item or pystac.Collection (or we call from_dict on it). This might be a bit difficult since pystac doesn't seem to want to create an Item with a null geometry / datetime, which we'll typically derive from the dataset.

This was implemented in #11


attestion: make InvalidAttestationError non-fatal in CI

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

I don't think I've seen an InvalidAttestationError that wasn't some
sort of network problem (e.g., rate limit, connection timeout, 503).
Let's emit a warning instead of erroring out.
Note that MissingAttestationError is still fatal, and that will still
produce errors in CI.

attestation.rb:135: Method `system_command!` does not exist on `T.class_of(Homebrew::Attestation)` https://srb.help/7003
     135 |        result = system_command!(gh_executable, args: cmd,
                           ^^^^^^^^^^^^^^^
Errors: 1

Huh, interesting. Not even code I touched though. Would love a suggestion here. CC @dduugg ?

Try pairing this with an explicit begin, i don't think the way code aligns matches the control flow. (Then, I think you should be getting a different type error, since you've made the return type nilable)

Implemented retry logic instead.

Let's keep the retry timing as is. The case for backing this out if we need to will be stronger if we were more patient about retries.


[u/user/permission] Adding the root user to a group does not work.

Example request:
{
  "authkey":"...",
  "uid":0,
  "gid":1,
  "permission":"velocity.user.create"
}

Returns "200 OK", but no membership is being created. This only seems to affect the root user, other users work fine.

Figured it out (Pretty sure) - Since the user already has all permission from the parent group already, only the "root" membership will be listed in the u/user Endpoint. Since it would be beneficial to display all permissions, I think this should be changed. The database seemingly already contains the dataset I would expect.

This might be related to a possible bug in checking if the permission does already exist. It is well possible that it uses the recursive instead of the direct permission check. I will look into this issue...

This issue is resolved with 51873a0. I already cherry-picked it into main so it is immediately available.

Aftermath: As I already guessed, this had to do with the recursive checking for permissions. This bug would surface on other users than root, too.


cranelift-isle crate is missing the LICENSE file

It looks like the cranelift-isle is missing a LICENSE file (or symlink). Since all other crates I see in this repository contain a LICENSE file or symlink, this seems to have been a simple oversight when creating the cranelift-isle crate a few months ago.

Thanks for noticing this!

It now looks like the cranelift-isle crate was split into multiple crates, and the LICENSE file was not moved / copied accordingly :(

Sorry about that! I'll fix it, and see about adding a check to our CI to ensure we don't break this again.


Extension stopped working, looking for an interpreter even when "fromEnvironment" is selected.

Type: Bug

Behaviour
Black server doesn't start because it requires an interpreter configured, even if  "black-formatter.importStrategy": "fromEnvironment".
Expected vs. Actual
It should use the environment python as interpreter if fromEnvironment is setup and not require the additional setting.
Steps to reproduce:

Open a python file
Black doesn't start because of missing interpreter

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): venv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings
{
  "workbench.tree.indent": 15,
  "terminal.integrated.profiles.windows": {
    "Git Bash (Scoop)": {
      "path": "C:\\Users\\xxxx\\scoop\\apps\\git\\current\\bin\\bash.exe",
      "args": ["--login"]
    },
    "UCRT64": {
      "path": "C:\\Users\\xxxx\\scoop\\apps\\msys2\\current\\usr\\bin\\bash.exe",
      "args": ["--login", "-i"],
      "env": {
        "MSYSTEM": "UCRT64",
        "CHERE_INVOKING": "1",
        "MSYS2_PATH_TYPE": "inherit"
      }
    },

    "MINGW64": {
      "path": "C:\\Users\\xxxx\\scoop\\apps\\msys2\\current\\usr\\bin\\bash.exe",
      "args": ["--login", "-i"],
      "env": {
        "MSYSTEM": "MINGW64",
        "CHERE_INVOKING": "1",
        "MSYS2_PATH_TYPE": "inherit"
      }
    }
  },
  "workbench.colorTheme": "Solarized Dark+",
  "python.defaultInterpreterPath": "C:\\Users\\xxxx\\scoop\\shims\\python3",
  "python.venvPath": "C:\\Users\\xxxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs",
  "python.formatting.provider": "none",
  "editor.formatOnSave": true,
  "isort.args": ["--profile", "black"],
  "[python]": {
    "editor.defaultFormatter": "ms-python.black-formatter",
    "editor.codeActionsOnSave": {
      "source.organizeImports": true
    },
    "editor.formatOnType": true
  },
  "[terraform]": {
    "editor.formatOnSave": true,
    "editor.defaultFormatter": "hashicorp.terraform",
    "editor.tabSize": 2 // optionally
  },
  "python.analysis.logLevel": "Error",
  "terminal.integrated.defaultProfile.windows": "UCRT64",
  "editor.rulers": [80, 120],
  "vim.useSystemClipboard": true,
  "vim.leader": ",",
  "vim.foldfix": true,
  "vim.normalModeKeyBindings": [
    {
      "before": ["<leader>", "r"],
      "commands": ["editor.action.rename"]
    },
    {
      "before": ["<leader>", "R"],
      "commands": ["editor.action.refactor"]
    },
    {
      "before": ["<leader>", "d"],
      "commands": ["editor.action.revealDefinition"]
    },
    {
      "before": ["<leader>", "t"],
      "commands": ["editor.action.goToTypeDefinition"]
    }
  ],
  "diffEditor.ignoreTrimWhitespace": false,
  "editor.fontFamily": "MesloLGM NF, Consolas, 'Courier New', monospace, 'Segoe UI Emoji'",
  "rust-client.rustupPath": "C:\\Users\\xxxx\\scoop\\persist\\rustup\\.cargo\\bin\\rustup.exe",
  "security.workspace.trust.untrustedFiles": "open",
  "jupyter.askForKernelRestart": false,
  "terminal.integrated.fontFamily": "MesloLGM NF",
  "terminal.integrated.fontWeightBold": "bold",
  "editor.fontSize": 13,
  "explorer.confirmDelete": false,
  "[json]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "vim.neovimConfigPath": "C:\\Users\\xxxx\\scoop\\shims\\nvim",
  "vim.enableNeovim": true,
  "remote.SSH.path": "C:\\Users\\xxxx\\scoop\\apps\\msys2\\current\\usr\\bin\\ssh.exe",
  "redhat.telemetry.enabled": true,
  "workbench.editorAssociations": {
    "git-rebase-todo": "default"
  },
  "[javascript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[yaml]": {
    "editor.defaultFormatter": "redhat.vscode-yaml"
  },
  "http.proxyStrictSSL": true,
  "[jsonc]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "black-formatter.importStrategy": "fromEnvironment",
  "black-formatter.interpreter": [
    "C:\\Users\\xxxx\\scoop\\shims\\python.exe"
  ],
  "git.openRepositoryInParentFolders": "never",
  "window.zoomLevel": -1,
  "[nginx]": {
    "editor.defaultFormatter": "ahmadalli.vscode-nginx-conf"
  }
}

Multiroot scenario, following user settings may not apply:

venvPath: "<placeholder>"

languageServer: "Pylance"

formatting
• provider: "none"

Extension version: 2023.2.0
VS Code version: Code 1.78.1 (6a995c4f4cc2ced6e3237749973982e751cb0bf9, 2023-05-04T09:48:08.683Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.85GB (15.06GB free)

Process Argv
--enable-proposed-api genuitecllc.codetogether --crash-reporter-id ed01675f-67d1-4c85-8363-79de19e446c3

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
vsctsb:30705553
azdwalk:30687957
pythonms35:30701012
pythonclientmvcf:30708686

If I specify the interpreter the server starts, but then it doesn't utilise the environment

2023-05-10 18:13:31.375 [info] Name: Black Formatter
2023-05-10 18:13:31.375 [info] Module: black
2023-05-10 18:13:31.376 [info] Python extension loading
2023-05-10 18:13:31.376 [info] Waiting for interpreter from python extension.
2023-05-10 18:13:39.347 [info] Python extension loaded
2023-05-10 18:13:39.408 [error] Python interpreter missing:
[Option 1] Select python interpreter using the ms-python.python.
[Option 2] Set an interpreter using "black-formatter.interpreter" setting.
Please use Python 3.7 or greater.
2023-05-10 18:13:57.057 [info] Formatting requested before server has started.

I have a multiproject workspace, so I have a virtualenvironment selected per project.
(monitoring-WTCPidQC-py3.10)
xxx@xxxxUCRT64 ~/git/qupynt-monitoring (delay)
$ which black
/c/Users/xxx/AppData/Local/pypoetry/Cache/virtualenvs/monitoring-WTCPidQC-py3.10/Scripts/black

2023-05-10 18:13:31.375 [info] Name: Black Formatter
2023-05-10 18:13:31.375 [info] Module: black
2023-05-10 18:13:31.376 [info] Python extension loading
2023-05-10 18:13:31.376 [info] Waiting for interpreter from python extension.
2023-05-10 18:13:39.347 [info] Python extension loaded
2023-05-10 18:13:39.408 [error] Python interpreter missing:
[Option 1] Select python interpreter using the ms-python.python.
[Option 2] Set an interpreter using "black-formatter.interpreter" setting.
Please use Python 3.7 or greater.
2023-05-10 18:13:57.057 [info] Formatting requested before server has started.

I have a multiproject workspace, so I have a virtualenvironment selected per project.
(monitoring-WTCPidQC-py3.10)
xxx@xxxxUCRT64 ~/git/***-monitoring (delay)
$ which black
/c/Users/xxx/AppData/Local/pypoetry/Cache/virtualenvs/monitoring-WTCPidQC-py3.10/Scripts/black

monitoring-WTCPidQC-py3.10 is the virtualenv configured for the project on which I have triggered the format document.

@rdbisme Can you share your *.code-workspace?

A sanitized version:
{
  "folders": [
    {
      "name": "****_prod",
      "path": "****/src/****_prod"
    },
    {
      "name": "****",
      "path": "****"
    },
    {
      "name": "qp",
      "path": "****-deploy/src/qp"
    },
    {
      "name": "****-strats-ci",
      "path": "****-strats-ci"
    },
    {
      "name": "xxxy0",
      "path": "xxxy0"
    },
    {
      "name": "****-ci",
      "path": "****-ci"
    },
    {
      "name": "backfill-ci",
      "path": "****-deploy/src/backfill-ci"
    },
    {
      "name": "internal-docs",
      "path": "****-deploy/src/internal-docs"
    },
    {
      "path": "****-api"
    },
    {
      "path": "****-monitoring"
    },
    {
      "path": "****-deploy/src/cmd-batch"
    },
    {
      "path": "****-ui"
    }
  ],
  "settings": {
    "yaml.schemas": {
      "https://gitlab.com/gitlab-org/gitlab/-/raw/master/app/assets/javascripts/editor/schema/ci.json": "file:///c%3A/Users/xxxxx/git/****-strats-ci/template-research-ci.yml"
    }
  },
  "launch": {
    "version": "0.2.0",
    "configurations": [
      {
        "name": "Python: Debug Tests",
        "type": "python",
        "request": "launch",
        "program": "${file}",
        "purpose": ["debug-test"],
        "console": "integratedTerminal",
        "justMyCode": false,
        "env": { "PYTEST_ADDOPTS": "--no-cov -v" }
      }
    ],
    "compounds": []
  }
}

@rdbisme Can you share the logs from the python extension? Also, when you select interpreter for your multi root scenario did you select for the entire workspace or per root?

@rdbisme Can you share the logs from the python extension? Also, when you select interpreter for your multi root scenario did you select for the entire workspace or per root?

I selected per root. And Intellisense and completions work as expected. Do you still need the logs?

@rdbisme Can you select one for the entire workspace as well? and see if that helps.
Another option is to add the interpreter here, (this is a temporary solution):
  "settings": {
    "yaml.schemas": {
      "https://gitlab.com/gitlab-org/gitlab/-/raw/master/app/assets/javascripts/editor/schema/ci.json": "file:///c%3A/Users/xxxxx/git/****-strats-ci/template-research-ci.yml"
    },
    "black-formatter.interpreter": ["c:/Users/xxx/AppData/Local/pypoetry/Cache/virtualenvs/monitoring-WTCPidQC-py3.10/Scripts/python"]
  },

This is scenario that is not currently handled well. I will need to investigate what we can do to provide a better fix for this in these cases.

That unfortunately doesn't work because I have different black versions requirements on different roots.

The root cause if this seems to be same as https://github.com/microsoft/vscode-black-formatter/issues/233 Closing this against that issue.

@karthiknadig are you sure about this? I'm pretty confident this configuration was working before. The problem is that right now it requires an interpreter set up before starting.
Also I have explicitly set up fromEnvironment, so the issue you would seem to not apply.
It stopped worked very recently.

I see. When you say recently was it in the last week? If it is last week, it could be due to python extension. You could revert python extension to 2023.6.1 and see if it helps.

You can also try selecting a python version for this level:

It need not be the python that you use for the workspace, we just need one to run the server.

If none of that works, would it be possible for you to create a minimal repro with details on how and where you have environments. That will greatly help debug this. I tried creating a few different styles of multi-root repositories, I was not able to repro it.

I have no environments, just the system-level Python, with Black installed with pip install --user black and today this extension has stopped working. It was working yesterday.
Windows 10
Python 3.11.3
Black 23.3.0
Python is installed for all users, it's in C:\Program Files\... and python.exe is in the PATH.
No environments. No workspace. I just start VSCode, open a folder, then open a Jupyter Notebook in that folder. I cannot format the notebook.
The notebooks work just fine with this Python interpreter.
The only recent change I'm aware of is the latest VSCode update to 1.78.2. I believe yesterday I was using the previous version.
2023-05-11 16:01:07.303 [info] Name: Black Formatter
2023-05-11 16:01:07.304 [info] Module: black
2023-05-11 16:01:07.304 [info] Python extension loading
2023-05-11 16:01:07.304 [info] Waiting for interpreter from python extension.
2023-05-11 16:01:09.417 [info] Python extension loaded
2023-05-11 16:01:09.427 [error] Python interpreter missing:
[Option 1] Select python interpreter using the ms-python.python.
[Option 2] Set an interpreter using "black-formatter.interpreter" setting.
Please use Python 3.7 or greater.
2023-05-11 16:06:06.168 [info] Formatting requested before server has started.
2023-05-11 16:07:50.329 [info] Formatting requested before server has started.
2023-05-11 16:09:11.814 [info] Formatting requested before server has started.
2023-05-11 16:09:11.815 [info] Formatting requested before server has started.

@karrtikr We have not release a new version of the black extension in weeks, but seems like the ability to get python paths stopped working. Can you help investigate?
@FlorinAndrei what is the version of VS Code, and Python extension you have installed? did you by change update VS Code or python extension recently

VSCode 1.78.2
Python 3.11.3
Black 23.3.0
Black Formatter v2023.2.0
Yeah, today I've applied the update to the latest VSCode. Now the extension is not working anymore.
It was working yesterday. I cannot think of any recent meaningful change other than the VSCode update.

Can you try reverting the python extension to older version?

And select 2023.6.1:

See if that fixes this.

Success! Black Formatter v2022.6.0 works just fine.

@FlorinAndrei I actually want you to rever Python extension to 2023.6.1... keep Black at 2023.2.0

Okay. Reverted Black Formatter to the latest version.
Downgraded the Python extension in VSCode to version v2023.6.1 - and now Black Formatter works just fine.
Re-updated the Python extension to the latest v2023.8.0 and Black Formatter still works just fine.
I now have all VSCode extensions updated to the latest and the formatter is working. I cannot reproduce the issue anymore.

Tested: Reverting Python extension to v2023.6.1 doesn't change the behaviour:
2023-05-12 10:43:59.525 [info] Name: Black Formatter
2023-05-12 10:43:59.525 [info] Module: black
2023-05-12 10:43:59.525 [info] Python extension loading
2023-05-12 10:43:59.525 [info] Waiting for interpreter from python extension.
2023-05-12 10:44:15.666 [info] Python extension loaded
2023-05-12 10:44:15.708 [error] Python interpreter missing:
[Option 1] Select python interpreter using the ms-python.python.
[Option 2] Set an interpreter using "black-formatter.interpreter" setting.
Please use Python 3.7 or greater.

Reverting VScode to 1.77.3 also doesn't fix for me.
Reverting the Black formatter extension to v2022.6.0 fixes the problem for me. The server starts successfully and it's able to find black in the environments that have it (and fail for the others).
Name: Black Formatter
Module: black
Python extension loading
Waiting for interpreter from python extension.
Python extension loaded
CWD Server: c:\Users\xxx\git\qupy0
sys.path used to run Server:
   C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool
   C:\Users\xxx\scoop\apps\python310\current\python310.zip
   C:\Users\xxx\scoop\apps\python310\current\DLLs
   C:\Users\xxx\scoop\apps\python310\current\lib
   C:\Users\xxx\scoop\apps\python310\current
   c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0
   c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0\lib\site-packages
   C:\Users\xxx\git\qupy0\src
   c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0\lib\site-packages\win32
   c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0\lib\site-packages\win32\lib
   c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0\lib\site-packages\Pythonwin
   C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\libs
Settings used to run Server:
[
    {
        "workspace": "file:///c%3A/Users/xxx/git/***/src/***_prod",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\***-4-3s-KfG-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-deploy/src/qp",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\qp-k9BKPGhN-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-strats-ci",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\***-strats-ci-25nC5AIC-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/qupy0",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\qupy0\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-ci",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\scoop\\shims\\python3"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-deploy/src/backfill-ci",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\backfill-ci-6e_RSQmN-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-deploy/src/internal-docs",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\***-internal-docs-ll0pM7nK-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-api",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\app-kh5kM_7w-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-monitoring",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\monitoring-WTCPidQC-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-deploy/src/cmd-batch",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\AppData\\Local\\pypoetry\\Cache\\virtualenvs\\cmd-batch-e6bUdhSH-py3.10\\Scripts\\python.exe"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    },
    {
        "workspace": "file:///c%3A/Users/xxx/git/***-ui",
        "logLevel": "error",
        "args": [],
        "path": [],
        "interpreter": [
            "c:\\Users\\xxx\\scoop\\shims\\python3"
        ],
        "importStrategy": "fromEnvironment",
        "showNotifications": "off"
    }
]

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***\src\***_prod
Version info for formatter running for c:\Users\xxx\git\***\src\***_prod:
black, 22.10.0 (compiled: no)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==22.10.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\***-4-3s-KfG-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***
Version info for formatter running for c:\Users\xxx\git\***:
black, 22.12.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==22.12.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qp-k9BKPGhN-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-deploy\src\qp
Version info for formatter running for c:\Users\xxx\git\***-deploy\src\qp:
black, 23.3.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==23.3.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\***-strats-ci-25nC5AIC-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-strats-ci
Version info for formatter running for c:\Users\xxx\git\***-strats-ci:
black, 23.3.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==23.3.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\qupy0\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\qupy0
Version info for formatter running for c:\Users\xxx\git\qupy0:
black, 22.10.0 (compiled: no)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==22.10.0

c:\Users\xxx\scoop\shims\python3 -m black --version
CWD formatter: c:\Users\xxx\git\***-ci
[Error - 10:47:28 AM] Traceback (most recent call last):
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\runner.py", line 57, in <module>
    result = utils.run_module(
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\utils.py", line 141, in run_module
    return _run_module(module, argv, use_stdin, source)
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\utils.py", line 128, in _run_module
    runpy.run_module(module, run_name="__main__")
  File "C:\Users\xxx\scoop\apps\python310\current\lib\runpy.py", line 220, in run_module
    mod_name, mod_spec, code = _get_module_details(mod_name)
  File "C:\Users\xxx\scoop\apps\python310\current\lib\runpy.py", line 140, in _get_module_details
    raise error("No module named %s" % mod_name)
ImportError: No module named black

Version info for formatter running for c:\Users\xxx\git\***-ci:

Error while detecting black version:
Traceback (most recent call last):
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\server.py", line 231, in _log_version_info
    first_line = result.stdout.splitlines(keepends=False)[0]
IndexError: list index out of range

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\backfill-ci-6e_RSQmN-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-deploy\src\backfill-ci
Version info for formatter running for c:\Users\xxx\git\***-deploy\src\backfill-ci:
black, 22.10.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==22.10.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\***-internal-docs-ll0pM7nK-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-deploy\src\internal-docs
[Error - 10:47:28 AM] Traceback (most recent call last):
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\runner.py", line 57, in <module>
    result = utils.run_module(
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\utils.py", line 141, in run_module
    return _run_module(module, argv, use_stdin, source)
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\utils.py", line 128, in _run_module
    runpy.run_module(module, run_name="__main__")
  File "C:\Users\xxx\scoop\apps\python310\current\lib\runpy.py", line 220, in run_module
    mod_name, mod_spec, code = _get_module_details(mod_name)
  File "C:\Users\xxx\scoop\apps\python310\current\lib\runpy.py", line 140, in _get_module_details
    raise error("No module named %s" % mod_name)
ImportError: No module named black

Version info for formatter running for c:\Users\xxx\git\***-deploy\src\internal-docs:

Error while detecting black version:
Traceback (most recent call last):
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\server.py", line 231, in _log_version_info
    first_line = result.stdout.splitlines(keepends=False)[0]
IndexError: list index out of range

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\app-kh5kM_7w-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-api
Version info for formatter running for c:\Users\xxx\git\***-api:
black, 23.3.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==23.3.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\monitoring-WTCPidQC-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-monitoring
Version info for formatter running for c:\Users\xxx\git\***-monitoring:
black, 23.3.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==23.3.0

c:\Users\xxx\AppData\Local\pypoetry\Cache\virtualenvs\cmd-batch-e6bUdhSH-py3.10\Scripts\python.exe -m black --version
CWD formatter: c:\Users\xxx\git\***-deploy\src\cmd-batch
Version info for formatter running for c:\Users\xxx\git\***-deploy\src\cmd-batch:
black, 23.3.0 (compiled: yes)
Python (CPython) 3.10.11

SUPPORTED black>=22.3.0
FOUND black==23.3.0

c:\Users\xxx\scoop\shims\python3 -m black --version
CWD formatter: c:\Users\xxx\git\***-ui
[Error - 10:47:31 AM] Traceback (most recent call last):
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\runner.py", line 57, in <module>
    result = utils.run_module(
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\utils.py", line 141, in run_module
    return _run_module(module, argv, use_stdin, source)
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\utils.py", line 128, in _run_module
    runpy.run_module(module, run_name="__main__")
  File "C:\Users\xxx\scoop\apps\python310\current\lib\runpy.py", line 220, in run_module
    mod_name, mod_spec, code = _get_module_details(mod_name)
  File "C:\Users\xxx\scoop\apps\python310\current\lib\runpy.py", line 140, in _get_module_details
    raise error("No module named %s" % mod_name)
ImportError: No module named black

Version info for formatter running for c:\Users\xxx\git\***-ui:

Error while detecting black version:
Traceback (most recent call last):
  File "C:\Users\xxx\scoop\persist\vscode\data\extensions\ms-python.black-formatter-2022.6.0\bundled\tool\server.py", line 231, in _log_version_info
    first_line = result.stdout.splitlines(keepends=False)[0]
IndexError: list index out of range

The problem seems black extension to me @karthiknadig

I confirm old black extension (v2022.6.0) and new Python extension works also Ok, both on Vscode 1.77.x and 1.78.x.

@rdbisme Now that it started working with the old black, if you switch back to newer version does it work?

@rdbisme Looks like an invalid interpreter was selected was for the workspace file:///c%3A/Users/xxx/git/***/src/***_prod:

If you're able to reproduce the issue again with latest Black and latest Python extension, kindly provide the following:

Open a file from the problematic workspace, run Python: Select Interpreter command and provide a screenshot of what appears. For eg in my case:

Open a Python file in problematic workspace stated above, wait for extension to activate and provide the Python logs.

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

We very much appreciated!

The problem is occurring again.
I need this extension to simply work. I don't have time for this. So I am going to uninstall it and revert to the old formatter until the issues are sorted out.

Moving this to python extension. This is an issue with environment selection. The error is shown when Python extension does not provide a python path for the current workspace.


Postgres Compatibility Issues

I am in the process of integrating the latest and greatest of cashu.  I am opening this issue to keep track of the Postgres compatibility issues and how I am addressing and resolving these issues.
There are two main areas of issues - using postgres for the mint database, and using postgres (via the cashu wallet) to access the mint.
As for cashu mint, it is fairly straightforward to use postgres.
As for the cashu wallet, it less straightforward - I am encountering the following incompatibilities, which I am resolving

datetime, timestamp conversion issues
sql variants - AS and NOT EXISTS
enumerating SQL into proofs.

You can monitor the pull requests I am publishing, you can comment on the pull requests or comment here. Hopefully, in time, we can get these changes incorporated into the main branch.

I am happy to be assigned this issue. Not sure how to do that in GitHub

I am getting this really weird error from WalletSecrets in secrets.py
AttributeError: 'Wallet' object has no attribute 'keyset_id'. Did you mean: 'keysets'?
It seems like Python can't resolve self.keyset_id during runtime. I am a bit stumped at the moment. Any help would be appreciated. @callebtc do you have any insights.


When Chronos is run using Marathon, jobs submitted to Chronos do not run

I have mesos 0.21.1, marathon 0.7.6 and chronos 2.3.0. I've deployed chronos using Marathon.
I am able to create a chronos job, where the command is simple like "echo hello", however, the job never runs. The "success" and "error" counts for the job are always 0. If I tail the chronos logs, I don't see any errors. Also, the Mesos UI shows no tasks for the jobs I submit to Chronos.
I've also tried other commands such as "echo hello > /tmp/hello.txt" and even "curl http://myserver" (so I could watch the server log to see if the job runs).
If I run Chronos outside of Marathon it works just fine.
Details:
OS: CentOS 6
Chronos installed with the chronos-2.3.0 rpm.
Command used to start chronos: /usr/local/bin/chronos
Chronos configured via /etc/chronos/conf
__ /etc/chronos/conf/http_port = 8081
__ /etc/chronos/conf/master = zk://myserver:2181/mesos
__ /etc/chronos/conf/zk_hosts = zk://myserver:2181/mesos
Mesos version: 0.21.1
java -version: 1.7.0_55

Here's what I see in the logs when I submit a simple job named "say hello" that is scheduled to run every minute using the command: "/usr/bin/echo hello":
WARN adding vertex: say hello
WARN Current number of vertices:1
Persisting job: say hellomindscratch>
Persisting job 'say hello' with data
State J_say hello does not exist yet. Adding to state
State update successful: true
Adding schedule for time:5:41:25 PM UTC
Checking schedules with tmie horizon:PT60S
Calling nextmindscratch> for stream: R/2015-01-16T17:41:03Z/PT1M, jobname: say hello
Task ready for scheduling: 2015-01-16T17:41:03.000Z
Scheduling:say hello
Scheduling task 'ct:1421430063000:0:say hello does not exist yet. Adding to state5] <mindscratch> Checking schedules with tmie horizon:PT60S
Calling nextmindscratch> for stream: R/2015-01-16T17:41:03Z/PT1M, jobname: say hello
Task ready for scheduling: 2015-01-16T17:41:03.000Z
Scheduling:say hello
Scheduling task 'ct:1421430063000:0:say hello does not exist yet. Adding to state
State update successful true
Saving updated job:ScheduleBasedJob(....)
Triggering: 'say hello'
removing task mapping
State update successful true
Saving updated job:ScheduleBasedJob(....)
Triggering: 'say hello'
removing task mapping

I disabled iptables on all hosts and now it works...looks like a network configuration issue. Chronos (2.3.0) on Marathon (0.7.6) is working just fine.

Thanks @mindscratch for debugging this! The only thing we need to close this issue is some documentation in the readme, The LIBPROCESS_IP environment variable should be set to a PORT that the Mesos Master can communicate with.

@elingg slight correction, that should be

The LIBPROCESS_PORT environment variable should be set to a PORT...

instead of LIBPROCESS_IP

correct, thx!

@elingg, @mindscratch note that this will only work if the IP is visible from mesos master. If, for example, you're running from within a docker container, you'd have to use host network --net=host and set LIBPROCES_IP to the public IP.
See https://issues.apache.org/jira/browse/MESOS-2587 for details

@mindscratch Can you tell me your json file content?  Beacuse I don't know how to  make Chronos  run using Marathon. Thanks.

Are there a marathon reference config file?

@wangqunOne I'll post something on Monday.

Where @mindscratch ?

I'll share in this comment.

Marathon configuration for running Chronos:
{
  "id": "chronos",
  "cmd": "LIBPROCESS_PORT=6500 ./chronos --http_port $PORT",
  "cpus": 1,
  "mem": 512,
  "instances": 1,
  "uris": ["http://myfileserver/chronos-2.4.0.tgz"],
  "ports": [4400],
  "requirePorts": true,
  "healthChecks": [
    {"protocol": "HTTP", "path": "/scheduler/jobs"}
  ]
}

How about a marathon config for running chronos in a docker container?

Something like this should work; with constraints
{
  "id": "chronos",
  "args": [
    "--mesos_role=private",
    "--mesos_framework_name=chronos" ,
    "--hostname=<hostname>",
    "--master=zk://,<ip>:2181,<ip>:2181,<ip>:2181/mesos",
    "--zk_hosts=zk://,<ip>:2181,,<ip>:2181,,<ip>:2181",
    "--http_credentials=username:pass"
  ],
  "cpus": 0.5,
  "ports": [8080, 8081],
  "constraints": [["hostname", "LIKE", "<hostname>"]],
  "mem": 500.0,
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "mesosphere/chronos:v3.0.0",
      "forcePullImage": true,
      "network": "HOST"
    }
  },
  "healthChecks": [
      {
        "path": "/",
        "port": 8080,
        "protocol": "HTTP",
        "gracePeriodSeconds": 300,
        "intervalSeconds": 60,
        "timeoutSeconds": 20,
        "maxConsecutiveFailures": 3,
        "ignoreHttp1xx": false
      }
  ],
  "env": {
    "PORT0": "8080",
    "PORT1": "8081"
  }
}

I was able to run Chronos and schedule a job but it stays there. Noticed that chronos framework becomes inactive in mesos after couple of mins.


The configuration used in this guide will not find repositories and entities defined in the library module

The current setup will not find JPA entities and repositories defined in the library module, but this paragraph gives the impression that it will:

Because DemoApplication is inside a different package (hello.app) than MyService (hello.service), @SpringBootApplication won't detect it initially. There are different ways to allow `MyService to be picked up:

Import it directly with @Import(MyService.class).
Fetch everything from it's package using @SpringBootApplication(scanBasePackageClasses={...}).
The method this guide uses--specifying the parent package by name, hello.

But if in the shared lib, we have entity classes defined under hello.entity and repositories under hello.repository, @SpringBootApplication(scanBasePackages = "hello") won't pick them up.
To make the app module pickup the entity and repository types, either DemoApplication should be defined in the hello package (as opposed to hello.app) or it is should be annotated with @EntityScan("hello.entity") and @EnableJpaRepositories("hello.repository").

This project does not use JPA though, so wouldn't it complicate matters to discuss it directly. Maybe a footnote would help? In any case I'm not sure I understand the point (since hello.entity will definitely be picked up by a scan of hello).

In any case I'm not sure I understand the point (since hello.entity will definitely be picked up by a scan of hello).

It will get component scanned but it will not get entity scanned. I will upload an example tomorrow. 🙂

I have attached two examples that show this problem. I might have time to fork the current guide and add some extra details next month.
Just to recap:
Without an explicit @EntityScan, the app crashes at runtime with error

Caused by: java.lang.IllegalArgumentException: Not a managed type: class com.example.utils.entity.Message

Without an explicit @EnableJpaRepositories, the app crashes at runtime with error:

NoSuchBeanDefinitionException: No qualifying bean of type 'com.example.utils.repository.MessageRepository' available: expected at least 1 bean which qualifies as autowire candidate.

ExtraAnnotations.zip
OnlySpringBootApplication.zip

OK, I see. Your sample apps have @SpringBootApplication on a class in com.example.app which is not a parent of the entity and repository packages (like in your description above). Spring Boot doesn't automatically apply the basePackages= from @SpringBootApplication to its @EntityScan and @EnableJpaRepositories.
I'm still not convinced we need to mention it here (there is no JPA), but maybe it wouldn't hurt to just add a quick sidebar or something. Also you could raise an issue in Spring Boot if you find this behaviour surprising.


Allow users to be able to add labels to tasks

Currently, Tasks are plain and simple textboxes. Allow, users to be able to add labels to them.

I'll work on this after #5  as we discussed in email 😇

Should the labels be pre defined? Also, will the user be able to add custom labels?

@PriyavKaneria We can start off with a few predefined labels. Then later we can allow users to customize them.

@sanskaromar Raised a PR for the Labels with UI as we discussed on email


Missing assumption for congr tactic

When applying congr in a situation where the the equality A = B of two types has to be shown before showing a == b for some a : A and b : B, congr should add A = B as an assumption for the latter goal, since it has already been shown. Might be related to #1830. Small example:
structure foo :=
  (A : Type)
  (a : A)

example (x y : foo) : x = y :=
begin
  cases x with A a, cases y with B b, congr,

end

I think not adding the assumption is a fine default (maybe there are independent reasons that a==b (in this particular case, a==b actually implies A=B). Fortunately, you can define your own congr tactic which does what you request.

I guess I'll close this until we have a few more cases than just mine.


Use native JSON and Array methods

@substack, do you mind merging this? Having zero dependencies is a big win.

Since this RP is from unknown repository (arrg)
I was able to remove the dependency on jsonify doing

make a clone
git fetch upstream pull/21/head:without_unlicenced_jsonify
push without_unlicenced_jsonify branch
in package.json

  "resolutions": {
    "json-stable-stringify": "git+https://github.com/ForbesLindesay/stable-stringify.git#master",
    "shell-quote": "git+https://github.com/srghma/node-shell-quote.git#without_unlicenced_jsonify"
  },

Or you could use something like license zero

:package: 1.6.2
thanks!


Allow fnamemodify to be a function

Give the user more power / customization by allowing them to use either an fnamemodify option string like it currently does OR a function that inputs the buffer name and returns the title string for the tab.
I found this useful/powerful for a couple of scenarios I ran into:

Could shorten names when too long
Searched for duplicate file names w/ different path and format the name so you can tell which is which.

For example, I have a repo I work on with similarly named files i.e. common/v1.py, external/v1.py, internal/v1.py, so I can make my function look for multiple files name v1.py and extend the path in that case.
Lots of possibilities.

sgtm, thanks!


optimize the spidermultusconfigs

the original field is long to be hard for writing

implement it in https://github.com/spidernet-io/spiderpool/pull/1904


FAQ on Terminology/Taxonomy/Ontology

There should be a FAQ for those new to this field on what ontology is and explaining Terminology vs Taxonomy vs Ontology

While we wait for someone to have the time to create the FAQ in response to this request, here is a good link with some simple explanations of the differences:
https://www.quora.com/Whats-the-difference-between-an-ontology-and-a-taxonomy


[bug] SYS_OrgStorageSnapshot_SCH - Missing "Overall Situation" data

Describe the bug
The "Overall Situation" Org storage data (corresponding to the first table of the "Storage Usage" Setup page is no longer generated in the SYS_OrgStorageSnapshot__c object.
To Reproduce
N/A
Expected behavior
All data from the Setup page should be in the
Screenshots
N/A
Additional context
Probably a change in a recent Salesforce release has removed the  title of the first section.

Issue fixed


Add filesystem plugin

Added "yet another" filesystem plugin :-)
=> https://github.com/josbeir/cakephp-filesystem

Is there an 'evalution' period on these pr's ? :-)

I think people were just hesitant because there are so many file handling ones already in the list.
Are there any key differences/improvements here?
I do like the docs verbosity :)

I can't speak of the other plugins but the 'cool' thing here is that instead of working with files directly the requirement is that we work with a file entity interface and a simple file entity class (nothing related to the ORM). There is no database requirement by default for storing and manipulating files.
But the beauty of this is that storing entities in the db can be easily done by just swapping the entity class configuration entityClass with an ORM one, this entity then needs to implement the FileEntityInterface interface and add a required method...
And of course we have events, php 7.1 strictness, working with Zend PSR streams, paths and $_FILES..., filename formatters, ...

Well, I dont think it hurts to add if it is well documented and tested.
It does sound like a valuable addition.

I would think it passes those two requirements :-)

Why does the readme still say "(WIP)"? :)

@ADmad yeah, because it is still WIP, it is not battle tested in production as i'm still working on the project where it is made for. But it works pretty well :-)
I'll remove it because it will probably confuse people...

It can deter potential users, so better to remove. Also better to use 0.x versioning until you are satisfied with your product :)

@dereuromark Good to merge?

Where did the plugin load part go?
And composer require josbeir/cakephp-filesystem:dev-master should be only composer require josbeir/cakephp-filesystem when you have tags.

Correct, upated.
There is currently no need to load the plugin as there are no components, behaviors, routes, ...


3 bug dash

Pick 3 bugs from the Find Your Bugs document
Comment which 3 bugs you fix
Mark the 3 fixed bugs as done on the document
closes #171

FIXED BUGS 1, 2, 6, 7, 9, 10, 26, 28 (you are welcome)

Thanks for fixing so many bugs this sprint :) Couple comments on this PR, lmk if y'all have any questions about them. Also, since y'all are fixing bug 6 in this PR, could you make the footer sticky on the About page as well?

made footer on about page sticky


⚠ Bofrost.fr has degraded performance

In 61b95ed, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1893 ms

Resolved: Bofrost.fr performance has improved in 8209429 after 23 minutes.


How to set up -i Parameter

Hi
How to set up -i Parameter to get mail content

domain  your  have control on it check https://exploitbox.io/vuln/WordPress-Exploit-4-7-Unauth-Password-Reset-0day-CVE-2017-8295.html  for more info


Fix recommender model load from 4.0

Not sure how this happened, but model load for recommender broke between
4.0 and 4.1. This seems to fix it, but the root cause is still unclear.
Models saved in 4.0 use vector<vector> for new_user_seed_items.
Models saved in 4.1+ use vector<pair<size_t, double>>.
Possibly something to do with flexible_type automatic conversion?

After chatting with @hoytak in person, I plan to flip the try/catch blocks so the newer-model case doesn't take a perf hit on exception handling.

Changed got merged with #623.