Add support for List timelines

Just creating an issue to dump some initial investigation into
Adding a separate timeline header

Find the <h2> containing the list title
Create a clone of its parent as a next sibling to hold the fake timeline heading
Make the following style changes on their shared parent:flex-direction: row;
align-items: center;
justify-content: space-between;

Do people ever use the Share button next to the menu button? Nothing on the menu it pops up seems that useful:

For Retweets in Lists, I'm thinking we should add an item to this menu to toggle their display on and off. On desktop we could add something to the header, but on mobile there's no room and I'd rather not add 2 different ways to control this.


Sync movie ratings and add to watched history

Hey, I just stumbled across your project and it works amazing. I only got one little feature request:
Would it be possible to mark a movie as watched on Trakt when the rating from IMDb is synced? I now only got the rating synced but it's not in the history.
Best Regards
Nico

Update: it works like I wished. Just the first sync got a timeout and therefore the history wasn't written correctly. Case closed.

I stumbled across the same problem. All the ratings are syncing but on Trakt are not marked as watched. I got the movies on ratings and not on history also.

@rafae667, do you mind sending me a link to an IMDb item that you've rated and hasn't synced its rating or history to Trakt?
I tried with The Godfather (1972) and it worked as expected 🤔
I couldn't reproduce this issue...

In my trakt account I have everything synced well. The ratings on IMDB went to the ratings in the Trakt.
But in the Trakt history, where the movies I've seen are, is empty.
It isn't supposed to the rating movies to appear also in the Trakt history marked as seen?

The way history is being synced is the following:

you rate movies, shows and episodes on IMDb
treating IMDb as the source of truth, imdb-trakt-sync would find the difference between your IMDb and Trakt ratings
it will add and/or remove any items that are in a different state on Trakt
if an item is being added/removed, at the same time the history will be synced too

If for some reason an item's rating was synced to Trakt, but its history wasn't, on the subsequent runs the history will be ignored. The approach I took for this is the following because IMDb doesn't have an equivalent to Trakt history.
To verify this is what happened with your rating/history, remove the rating for an item on Trakt and do a sync. The rating and history should be synced together during that sync run.

Thank you for the explanation. Also, thank you so much for the repo. Great work.
I'm not able to understand the code and I'm not a developer. Fortunately I was able to make this work.
I was just wondering if it wasn't supposed to sync IMDB ratings for both Trakt ratings and history.
I guess it's best to leave it as is. I doesn't bothers me since I'll continue using IMDB. Trakt is just for integrate the watchlists in Kodi.

I’m glad that I could help you sync your IMDb library to Trakt. Unfortunately, with the current implementation the ratings and history are tightly coupled. I’ll look into separating the history sync into its own flow and push an update soon. You can star and watch the repository to see when I update it.
That’s exactly my use case too! 🙂 I’m using Kodi as my media player. It integrates nicely with Trakt, but I still mostly use IMDb for finding movies and creating lists.


fix: ZA

This PR fixes ZA, which had a CSV parsing failure. The CSV provided by the ZA community project included 3 blank lines at the end of the document. I modified the CSV fetch script to remove empty lines at the beginning and end of documents to address this issue.

Thanks!


Clone depth of 0 no longer supported

Troubleshooting

[X] I've searched discuss.bitrise.io for possible solutions.
Which version of the step is effected? 7.0.0
Is the issue reproducible with the latest version? YES
Does the issue happen sporadically, or every time? EVERY TIME

Useful information

FAQ
devcenter.bitrise.io
Shallow clone by default release notes

Issue description
A clone_depth of 0 is no longer supported.

Steps to reproduce

Under Clone options, set a Clone depth of 0
Run the step

Expected outcome: git fetch uses a depth of 0
Actual outcome: git fetch uses a depth of 1

@steliosfran by "depth of 0" do you mean literally adding the --depth=0 flag to the git commands? Because 0 is not a valid value, the smallest depth is 1.
$ git clone --depth=0 ...
fatal: depth 0 is not a positive number

Would be nice if we could disable the depth somehow, I quickly checked the code and it seems that if you set the depth to 0 in the input values of the step it will choose the ideal depth for you (which is 1 or 50).
We have a custom step later in our workflow that uses the commit count as the value for the patch version of our build version: x.x.GIT_CLONE_COMMIT_COUNT. (Not the most ideal solution, I know... 😅)

@steliosfran by "depth of 0" do you mean literally adding the --depth=0 flag to the git commands? Because 0 is not a valid value, the smallest possible depth is 1.
$ git clone --depth=0 ...
fatal: depth 0 is not a positive number

@ofalvai You're right, it's not supported by git.
In the previous versions of this step though, a value of 0 was disabling the depth.
How can we disable it in version 7.0.0?

There needs to be an option to disable shallow clone entirely. This breaks our mainline builds because they use commit count for build number. We have to revert to an earlier version to work around this.

Yes, it would be good if it supports disabling the shallow clone option. the new version should support backward compatibility for many builds which is using commit count.

👋 everyone - we released version 7.0.1 with the option to disable depth limiting completely. If you really want to fetch the entire repo history, just set -1 as the clone_depth input.


jaSelectStoreResources

分かってる限り大丈夫そうです。
でも名前は大丈夫なのかな？
Maybe we should use something more descriptive like selectStoreResourceArray. I'm not sure what should be considered best practice

it's plural, I think developers will expect it's array in javascript. and in this library, many function use the word Resources

なるほど。If thats the case then it sounds fine

I'll merge original master branch instead of this feature branch


feat(): added a new uri-strict validation

Related to https://github.com/snapshot-labs/snapshot/pull/1881

@ChaituVR this will need a new version after merged :)


[cocoon test]Temporarily skip a test case('SignInButton shows avatar when authenticated')

Context addresses https://github.com/flutter/cocoon/pull/1043#issuecomment-756288403
This issue should be opened until relanding the test case.
CC @CaseyHillers @Piinks

Friendly ping. Is there an ETA for when we can re-enable this test case?

Friendly ping. Is there an ETA for when we can re-enable this test case?

Thanks for reminds.
I think it will be a couple of days in case of that the change was not revert! :)

Thanks for reminds.
I think it will be a couple of days in case of that the change was not revert! :)

Once https://github.com/flutter/flutter/pull/70160 rolls to dev we'll know it won't be reverted. It should be fine, but we can wait on the roll to land and then turn this back on.

Once https://github.com/flutter/flutter/pull/70160 rolls to dev we'll know it won't be reverted. It should be fine, but we can wait on the roll to land and then turn this back on.

Update: Unfortunately, #70160 was reverted by #74439. I will try to fix it as soon as possible. @CaseyHillers
If it cannot be resolved in a short time, it will consider resuming the test first.

Update: Unfortunately, #70160 was reverted by #74439. I will try to fix it as soon as possible. @CaseyHillers
If it cannot be resolved in a short time, it will consider resuming the test first.

Thanks @xu-baolin for the update. If this issue is getting periodic updates, it's fine to keep the test disabled.

Thanks @xu-baolin for the update. If this issue is getting periodic updates, it's fine to keep the test disabled.

Update: Reland via #74620. Waiting to roll to the dev branch.


Ensure Pod Restarts upon Object Update.

Ensure Pod restarts automatically whenever the Secret object is updated.
A hash of the object is now included in Deployment.

(note that the CI is actually fine, ti's just a permissions issue w/ pushing the built image)


Support to audit creation of new objects in the database

The <<Auditable>> feature provided by the ADO library and Dynamo code generator can audit the update of database table fields.
Sometimes, it is necessary to have an audit field that records the creation of a new database object/row.
This can be done in UML by assigning the <<Auditable>> stereotype to the table primary key.

Done in 1.4.0


BUG: Refactor the CCA and Parsec-CCA commonality inside arm/cca

Refactor the CCA and Parsec-CCA commonality inside arm/cca

This also addresses the remainder of unresolved comments, about formatting log.Debugf() for debug prints requiring formatting.
Also the same needs to be done for scheme plugin for cca-ssd-platform , which will be addressed using this issue.


Lambda syntax design & parser

Let's vote.
Option 0 (Haskell, add a 🎉 to vote for this):
\x -> x
\x y -> y x

Option 1 (Idris, add a 🚀 to vote for this):
\x => y
\x => \y => y x

Option 2 (Mini-TT, add a ❤ to vote for this):
\x. x
\x y. y x

D S S Q

I'm sorry -- I have already implemented the parser. I've just forgotten it. My bad.
However, I did change the syntax according to this vote. We'll see.

... and please continue vote, new comers.

Is this vote in progress?  Why was this issue closed?  Anyway the option 1 with the bonus Shift for -> hurts me.

This issue is closed by a commit, which means it's fixed as an issue or implemented as a new feature


rename lastKvIdx

fix issues https://github.com/ethstorage/storage-contracts-v1/issues/38

This is a breaking change because es-node is using the lastKvIdx to request, so we may need to wait for the next testnet to check in this PR.
Also, does the FlatDirectory contract use this property? @iteyelmp

This is a breaking change because es-node is using the lastKvIdx to request, so we may need to wait for the next testnet to check in this PR. Also, does the FlatDirectory contract use this property? @iteyelmp

FlatDirectory is not used


remove or refactor nucleic_acid_concentration slot

It's not used in MongoDB. It's range is asserted to be InstrumentValue, which doesn't make any sense. InstrumentValue is also going to be removed.
It was a see_also for the following slots

dna_concentration in src/schema/portal/jgi_metagenomics.yaml
rna_concentration in src/schema/portal/jgi_metatranscriptomics.yaml

It was associated with class ProcessedSample in src/schema/core.yaml
It is commented out as a slot on a ProcessedSample in the following. In these cases, it illustrates a hybrid QuantityValue/InstrumentValue structure

src/data/problem/uncertain/Database-analytical_sample-extract-exhaustive.yaml
src/data/valid/Database-processed_sample-extract-exhaustive.yaml

assets/misc/neon_nmdc_term_mapping.tsv also suggests that it be used in the QuantityValue/InstrumentValue style in support of NEON's nucleicAcidConcentration and nucleicAcidQuantMethod
cc @aclum @mslarae13

So we did this before we had 'JGI MT Interface' and 'JGI MG Interface' in the submission schema. I agree, we make nucleic_acid_conc (and do the same for all the other rna & dna shared slots) .... and then have slot usage for the MT and MG interfaces as necessary.
@pkalita-lbl  fyi


style(tslint): expand tslint rules

Applied small refactoring along with expanding additional tslint rules.

Great. I remember putting those rules was too aggressive at the time, but now is a good time to add them.

Yes, I thought also it's considerable to expand more rules into lint. Plans to add couple of more rules further which requires some additional efforts.

it looks like there are some lint errors.

<EMAIL_ADDRESS>lint_src /Users/blesh/GitHub/blesh/RxJS
tslint -c .tslintrc src/**/*.ts

src/operators/expand-support.ts[2, 8]: unused variable: 'Observer'
src/operators/first.ts[4, 8]: unused variable: 'Observer'
src/operators/last.ts[4, 8]: unused variable: 'Observer'
src/operators/shareBehavior.ts[2, 8]: unused variable: 'Scheduler'
src/operators/switch.ts[2, 8]: unused variable: 'Observer'
src/operators/takeUntil.ts[47, 21]: block is empty

Updated PR with changes of

applying lint rules for rest of codes
found travis did not run lint after removing duplicated build execution, added lint to be executed

Thanks, @kwonoj


CodePush dependencies are really old

In vsts-task-code-push-release task we can see that it uses "code-push-cli": "^1.10.0-beta", which is very old (3 years). Current version is https://www.npmjs.com/package/code-push-cli/v/2.1.9. Can you please update the dependency and make sure it works correctly. Current version has issues when uploading android bundle with assets.

Hi @Imroath .
Thanks for reporting!
Yeah, you are absolutely right. I'll update this dependency and make release. I'll do it a little later. It is in queue.
Thanks,
Alexander


cilium: CI, fix DatapathConfiguration tests previously running with default config

We were running DatapathConfiguration tests without applying test options. This series fixes the encryption nil pointer error when using encryption values and pushes test options into configuration.

This change is

test-me-please

Coverage decreased (-0.02%) to 44.133% when pulling<PHONE_NUMBER>7c1ee5a78fba5ad787024856f8552d on ci-fixes into 683c087d043f028ba8a01dc1c1be5d8529f9d6e3 on master.

Seems like it contains fix from https://github.com/cilium/cilium/pull/8797/files , but it's fine

Status probe failed: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14119/

test-me-please

Namespace selector test failure: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/14125/
This is a known failure unrelated to this PR. Merging as this is critical for CI correctness.


discuss vpn pp req in os pp for trusted path

FCS_IPSEC_EXT.1.1 through FCS_IPSEC_EXT.1.12
from
https://www.niap-ccevs.org/pp/pp_vpn_ipsec_client_v1.4.pdf

Discussed.  Tentatively we plan to keep the current form, which would require an additional evaluation for VPN functionality.
This should motivate reworking of the VPN PP as an EP, which is the desired end state.


[stable/ambassador] default keep crds to false

The ambassador chart currently defaults to keeping CRDs. This means that when you delete the release the CRD resources are kept.
It's very natural to install ambassador and uninstall it and then install it again. We do this a lot with Seldon. To accommodate this we have to override the default value of the crds.keep flag. For us it would be much better if the default were the other way around.
I appreciate there are other users out there who might prefer the default the other way. I'm proposing that the more common use-case might well be to have a single ambassador cluster-wide. In that case when you remove it you want the crds removed too.

Closing following discussion on PR


Change current working dir to location of exec

I have a function that I deploy via a Docker container (ie. I do: wsk action update mydemo exec.zip --native). Inside of that zip I have some files that my function needs to access at runtime.  Those files appear at the root of the location of where the zip file is extracted/expanded. However, when the function's code (exec) is run, the current working dir is someplace else in the filesystem. In order for my app to locate its needed files I need to get the program's args[0] and strip off the /exec at the end to find where I should look for the files.  While obviously do-able, this isn't the greatest UX. It would be nicer if the current working dir was the root of where the zip file was expanded. Then the function author doesn't need to jump through hoops to find the data from their zip file.

This belongs in the respective runtime and should already be done.


Can't choose alternate calling codes from same country despite said options being displayed

Countries like Vatican City and Dominican Republic have multiple calling codes which are displayed on the list but are unable to be selected, instead it defaults to the first, how to deal with this?

this library use this packages react-native-country-picker-modal and then list data "DO":{"currency":["DOP"],"callingCode":["1809","1829","1849"],"callingCode":["3906698","379"]. for this reason show the first callingCode.


Add support for packages containing @ and /

When trying to install a package like this:
@sailshq/lodash
https://www.npmjs.com/package/@sailshq/lodash
Error:
npm ERR! 404 no such package available : @sailshq/lodash
npm ERR! 404
npm ERR! 404  '@sailshq/lodash' is not in the npm registry.

@zoell you need to add something like this into your config file
packages:
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    proxy: npmjs

Worked for me without any change.
Was having this problem with sinopia tho.

It works for me however the readme files won't load in the web interface.


Possible implementation of SessionManagerListener

Right now I allow for renewal in the event. This allows for moving all of the code into there for renewal for the two LifecycleSessionManager, but is currently dubious logic.
My reactive fu is weak - so the Reactive part needs scrutiny.

Arguably instead of hitting the subclass we need separate implementations of listener in the two Lifecycle concrete classes to preserve reactive semantics. Then the renewal needed would return some form of TokenWrapper directly.

Not quite sure about the idea behind the change. Could you please elaborate the rationale or what you're trying to achieve before proposing changes?

Sure. Let me start by saying this is sort of a sketch and I'm not sold 100% on the solution.
Here are the problems I am trying to solve:
Primary: An Event that lets you know when the tokens are bad.
Rationale: When wrapping spring vault into a service client (eg one of 1000 containers), it's important that a failure to renew tokens, etc is known and action can be done, such as logging metrics, exiting the container, firing alarms, debugging, etc. Right now that's all encapsulated and not expandable cleanly.
Secondary: Allow another option for getting a token. I guess I don't mind if we drop this per se, one could override renewToken. OTOH, there's an argument to be made that the entire renew/revoke logic itself should be attached to an event listener.
Improvement in signature: Instead of passing the token when renewal is successful, one could pass the SessionManager (which makes getting the token trivial). That would clean up the signature to
onRenewedFailed(SessionManager)
onRenewedSuccessfully(SessionManager)

So the primary purpose is to just allow an event driven set of hooks to react in any way seen fit to successful or failed renewals. It also parallels the SecretLeaseContainer

Thanks for the insight. We could provide hooks to allow event dispatching. LifecycleAwareSessionManager isn't as event-based as SecretLeaseContainer. We have to see whether a switch to an event-driven approach reduces the complexity or whether it raises complexity.
We used events in SecretLeaseContainer to decouple things which helped to organize the code better.

Right that's the basic idea. The secondary idea of switch it all to events is dubious, and if we dropped the first method (aboutToRenew) we could skip it for now and extend it later

I've  now simplified this a lot

Removed the problematic method allowing overriding of Token acquisition
Both remaining methods provide no injection of parameters.

@mp911de I think this is now simple enough to be clear and extensible ;)

We decided to not merge the pull request as we feel there's not sufficient demand for the feature. Thanks a lot for contributing.


No way to contact main dev regarding adding functionality.

I don't know if this is taboo to open a bug on this but I couldn't find a way to contact TimSimpsonR directly to ask some questions.
I work for a company that uses testng as a base for the java automation framework. I started using proboscis because they also want a python automation framework and the work that's been done here already is fantastic. The hope I was having was to make the java and python frameworks we have close as possible to one another to make it easy for dev and QA to switch between the two. Same functions, same functionality, etc.
This means I'm wrapping proboscis with another class where most of our framework functionality will go, but this also means I'm working on proboscis making modifications such as I got @BeforeMethod and @AfterMethod working. However moving forward I'd still like to get updates from here as they're made. So I wanted to ping you regarding questions I had on how you're approaching things so I could hopefully do them in a compatible fashion as well as possibly contribute to helping you out.
If that's making a new branch on here and porting in your changes as they're made then so be it. I just want to know what the correct approach would be so I could possibly try contributing the work we're doing here to help out.

I am a fan of proboscis too. I wonder why the project stays inactive for the last few years. Please come back!

@BattleCorgi I am interested in @beforeMethod and @afterMethod that you have added. Where may we get that code? Thank you!


avoid blocking in the default executor's thread pool

Use Task.after rather than Thread.sleep.
When running on a single-core machine, scalaz's default executor
service uses a pool of exactly one thread. waitForInput was blocking
that thread continuously, so requests would just hang.
This fix was verified (applied to 8.0.1) on @damonLL's single-core Ubuntu image.

LGTM. I’m going to declare it ready, just to get it out the door faster (hope I’m not stepping on your toes @drostron).

Merged as 9.2.2


further link light admin pages

Beyond those from #1714 adds a couple more links among light admin pages. See https://trello.com/c/kDxd1MeO/57-cross-reference-light-admin-docs for background.

I realise it's not strictly within the scope of this PR but I also find the title of the permissions mapping page somewhat difficult to parse and also wonder whether that page would be better NOT listed in the main index and instead added to an invisible TOC at the bottom of the main light admins page.

Invisible TOC sounds scary but if my suggested retitling does not suffice then I'll happily accept a PR. :smiley:

Your retitling is indeed helpful, we can probably leave it there (someone else will probably complain if we hide the page ;))

Having looked at what else we are doing on the index page, I'm thinking we should move the mapping page down a level in the TOC but I can do that on a new PR. Are you happy with this now @joshmoore ?

Thanks, @mtbc


Create index.html file for a website

This file is meant to be used as a Github page. This file dynamically grabs readme.md and converts it to HTML. Creating a Github page now should be a straightforward task.
Sample site: https://shakil-shahadat.github.io/showdown/
This is alternate PR for #516.
Future ToDo

Add a reference to the website to the readme.md.
Remove readme.html as that file is already obsolete and no longer needed.

wow so original

https://github.com/Igglybuff/awesome-piracy/pull/524#issuecomment-848969254


Change the word APPEAL" to RequestaChange" in Database.

Never use the word Appeal

Would prefer to have the use of Appeal be replaced by requestachange for all request a change actions. The reason why this is valuable is due to the future potential of actually having true appeals become a part of the SIMS system.
Replace references to appeal in the data base and processes with requestachange.


Add logical implication and bi-implication

This provides another way of establishing a relation between a given constraint and another.
For example, suppose we want the following to be true:
(only) if Baker lives on the fifth floor, then Cooper must also live on the fifth floor
This could be expressed as the following:
require(implication(Baker === 5, Cooper === 5));

Fixing the conflicts locally

Code looks good.
However, in your example (only) if Baker lives on the fifth floor, then Cooper must also live on the fifth floor
Wouldn't this correspond to implication(Cooper === 5, Baker === 5) ?

Code looks good.
However, in your example (only) if Baker lives on the fifth floor, then Cooper must also live on the fifth floor ... so Baker living on fifth floor is necessary for Cooper living on fifth floor?
Wouldn't this correspond to implication(Cooper === 5, Baker === 5) ?

Nope, Cooper living on fifth floor is necessary for Baker living on fifth floor. You can ignore the only.
What I meant was:
if Baker lives on the fifth floor, Cooper must then also live on the fifth floor. But it is not necessary that Baker lives on the fifth floor.


calculate the number of arguments

Binary Ninja Version: 4.2.6447-dev Personal (5ca6dc49)
OS: manjaro
OS Version:

cat /proc/version
Linux version 6.10.13-3-MANJARO (builduser@fv-az1246-770) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.0) #1 SMP PREEMPT_DYNAMIC Tue Oct  8 03:24:49 UTC 2024

CPU Architecture: x64

Bug Description:
in Pseudo C code, when we are calculating the number of arguments, we treat the following reg of x18 as an argument:
Here is the code
ffffffc0082effb0    void audit_core_dumps(int64_t* arg1, int64_t* arg2 @ x18)

ffffffc0082effb0  5f2403d5   bti     c
ffffffc0082effb4  5e8600f8   str     x30, [x18], #0x8
ffffffc0082effb8  3f2303d5   paciasp
ffffffc0082effbc  ff4301d1   sub     sp, sp, #0x50
ffffffc0082effc0  fd7b02a9   stp     x29, x30, [sp, #0x20] {__saved_x29} {var_28}
ffffffc0082effc4  f65703a9   stp     x22, x21, [sp, #0x30] {__saved_x22} {__saved_x21}

I think it is not a special case in the specific function, I found it in many functions.
But to be honest, the real definition of this function is
void audit_core_dumps(long signr)
{
	struct audit_buffer *ab;

	if (!audit_enabled)
		return;

	if (signr == SIGQUIT)	/* don't care for those */
		return;

	ab = audit_log_start(audit_context(), GFP_KERNEL, AUDIT_ANOM_ABEND);
	if (unlikely(!ab))
		return;
	audit_log_task(ab);
	audit_log_format(ab, " sig=%ld res=1", signr);
	audit_log_end(ab);
}

And also, because this assemble instruction code locates before
paciasp
as this is a Pac instruction, I don't know whether I am right. as my personal sense, Pac is added by the compiler.
So, register of x18 is not designed by normal programmer, So, it is not the arguments of the original function.
As a comparation of Ida, we get the follow code
void __fastcall audit_core_dumps(long signr)
{
  _QWORD *v1; // x18
  __int64 v2; // x30
  task_struct_26 *StatusReg; // x21
  audit_buffer *v5; // x0
  audit_buffer *v6; // x20
  size_t v7; // x0
  mm_struct *mm; // x0
  file_2 *mm_exe_file; // x0
  file *v10; // x21
  char buf[8]; // [xsp+8h] [xbp-18h] BYREF
  __int64 v12; // [xsp+18h] [xbp-8h]

  *v1 = v2;
  v12 = *(_QWORD *)(_ReadStatusReg(ARM64_SYSREG(3, 0, 4, 1, 0)) + 1504);
  if ( signr != 3 )
  {
    if ( audit_enabled )

a little urgly but maybe the true result.
If we need the binary plz call me.

i think i should upload these two files, because its really a little time confusing to reproduce .

Well I get what is happening, and I am probably going to close it as intended. Still, I will first discuss it with the team
Our philosophy is to produce the output that is closet to the behavior of the code. In this sense, the source code is only a reference and our decompiling captures the behavior of the assembly instructions better than that

OK~
https://1drv.ms/f/c/01e018a652fc6a6e/Ej4Ra1Am3aZOgnvoAAcTKC8BRXfZ7cHC7o804U3X6CoNQQ

Sorry that I did not notice x18 is related to PAC. I have updated the issue title accordingly

Vector 35 employees can search private slack for unknown chicken hammer bull


ENH add private arg to push

Fixes #112 and #114

@narsil @osanseviero do we not want to support private repos on the inference side? I wanted to have all repos created by the CI to be private, but we can't test the inference engine if we make them private.

I'd say we can merge (if the CI is green) and make the inference test repo private once/if we support that in the backend side.
cc @skops-dev/maintainers

adding some more docs ...

Now done!


[Candidate 2v2 Freezing Bursa ZH v1] Some Tech Buildings clip into terrain

Observed behavior
2 Tech Buildings clip into terrain.
Expected behavior
Tech Buildings sit tight on terrain.
Screenshots

fixed


Include src in compiled package

My webpack throwing a lot of warnings about sourcemaps.
WARNING in ./node_modules/zod/lib/types/string.js
Module Warning (from ./node_modules/source-map-loader/index.js):
(Emitted value instead of an instance of Error) Cannot find source file '../../src/types/string.ts': Error: Can't resolve '../../src/types/string.ts' in '/Users/okhomenko/brightback/brightback-server/src/main/webpack/node_modules/zod/lib/types'

WARNING in ./node_modules/zod/lib/types/object.js
Module Warning (from ./node_modules/source-map-loader/index.js):
(Emitted value instead of an instance of Error) Cannot find source file '../../src/types/object.ts': Error: Can't resolve '../../src/types/object.ts' in '/Users/okhomenko/brightback/brightback-server/src/main/webpack/node_modules/zod/lib/types'

It's trying to merge sourcemaps from zod and can't find source typescript files.
@vriad Could you please include src as part of the published package?

It causes issues in other people's builds if the source is included with the package.
Based on a quick search you can solve your issue by excluding node_modules from their source-maps-loader plugin. Link: https://github.com/apollographql/react-apollo/issues/597#issuecomment-306091791
Let me know if that works, closing in the meantime. 👍


fix extended key version bytes not updating after switching tabs

Looks good. Can you please confirm these are the steps to reproduce this bug:

generate a random mnemonic
switch to bip84 and notice the bip32 root key has changed from xprv to zprv
reload the page and paste in a bip39 seed (not a mnemonic)
switch tabs to bip84 and see the bip32 root key has not changed but should have changed

Yes, thanks, I confirm


Bug Trying to use Tox with coveragepy[BUG]

setuptools version
setuptools==65.5.0
Python version
Python 3.10.10
OS
Windows 10 VS Code Terminal
Additional environment information
No response
Description
When I try and run tox I get this long error.
https://pastebin.com/ZvxFhA9a
Expected behavior
Expected tox to run.
How to Reproduce

open integrated terminal in VS code
python-m venv env
source env/Scripts/activate
git clone https://github.com/nedbat/coveragepy
cd coveragepy
python3 -m pip install -r requirements/dev.pip
python3 -m pip install -r requirements/dev.in
python3 -m tox

Output

$ python3 -m tox
ROOT: tox-gh won't override envlist because tox is not running in GitHub Actions
py37: skipped because could not find python interpreter with spec(s): py37
py37: SKIP ⚠ in 0 seconds
py38: skipped because could not find python interpreter with spec(s): py38
py38: SKIP ⚠ in 0 seconds
py39: skipped because could not find python interpreter with spec(s): py39
py39: SKIP ⚠ in 0.02 seconds
.pkg: _optional_hooks> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
.pkg: get_requires_for_build_editable> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta.pkg: build_editable> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
py310: packaging backend failed (code=error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"), with SystemExit: error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
no previously-included directories found matching 'doc_build'
no previously-included directories found matching 'doc_spell'
no previously-included directories found matching 'tests\eggsrc\build'
C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\wheel\bdist_wheel.py:83: RuntimeWarning: Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
if get_flag("Py_DEBUG", hasattr(sys, "gettotalrefcount"), warn=(impl == "cp")):
Traceback (most recent call last):
File "", line 172, in build_extension
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 549, in build_extension
objects = self.compiler.compile(
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 344, in compile
self.initialize()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 253, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 210, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 164, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 140, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 330, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 261, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 288, in _run_build_subcommands
self.run_command(name)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 163, in run
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 84, in run
_build_ext.run(self)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 346, in run
self.build_extensions()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
File "", line 174, in build_extension
BuildFailed
Traceback (most recent call last):
File "", line 172, in build_extension
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 549, in build_extension
objects = self.compiler.compile(
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 344, in compile
self.initialize()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 253, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 210, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 164, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 140, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 330, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 261, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 288, in _run_build_subcommands
self.run_command(name)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 163, in run
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 84, in run
_build_ext.run(self)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 346, in run
self.build_extensions()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
File "", line 174, in build_extension
BuildFailed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\core.py", line 201, in run_commands
dist.run_commands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 969, in run_commands
self.run_command(cmd)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 154, in run
raise errors.InternalError(cleandoc(msg)) from ex
distutils.errors.DistutilsInternalError: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py", line 90, in run
outcome = backend_proxy(parsed_message["cmd"], **parsed_message["kwargs"])
File "C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py", line 32, in call
return getattr(on_object, name)(*args, **kwargs)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\build_meta.py", line 442, in build_editable
return self._build_with_temp_dir(
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\build_meta.py", line 398, in build_with_temp_dir
self.run_setup()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\build_meta.py", line 335, in run_setup
exec(code, locals())
File "", line 224, in
File "", line 214, in main
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_init.py", line 108, in setup
return distutils.core.setup(**attrs)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\core.py", line 185, in setup
return run_commands(dist)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\core.py", line 215, in run_commands
raise SystemExit("error: " + str(msg))
SystemExit: error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
Backend: run command build_editable with args {'wheel_directory': '.tox\.pkg\dist', 'config_settings': {'--build-option': []}, 'metadata_directory': None}
running editable_wheel
creating C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info
writing C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\PKG-INFO
writing dependency_links to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\dependency_links.txt
writing entry points to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\entry_points.txt
writing requirements to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\requires.txt
writing top-level names to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\top_level.txt
writing manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\SOURCES.txt'
reading manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
writing manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage.egg-info\SOURCES.txt'
creating 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage-7.2.3a0.dev1.dist-info'
creating C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-7wl1m1av\coverage-7.2.3a0.dev1.dist-info\WHEEL
running build_py
running build_ext
building 'coverage.tracer' extension
Backend: Wrote response {'code': 'error: Support for editable installs via PEP 660 was recently introduced\nin setuptools. If you are seeing this error, please report to:\n\nhttps://github.com/pypa/setuptools/issues\n\nMeanwhile you can try the legacy behavior by setting an\nenvironment variable and trying to install again:\n\nSETUPTOOLS_ENABLE_FEATURES="legacy-editable"', 'exc_type': 'SystemExit', 'exc_msg': 'error: Support for editable installs via PEP 660 was recently introduced\nin setuptools. If you are seeing this error, please report to:\n\nhttps://github.com/pypa/setuptools/issues\n\nMeanwhile you can try the legacy behavior by setting an\nenvironment variable and trying to install again:\n\nSETUPTOOLS_ENABLE_FEATURES="legacy-editable"'} to C:\Users\Jordan\AppData\Local\Temp\pep517_build_editable-mlt4umie.json
py310: FAIL ✖ in 1.09 seconds
.pkg-cpython311: _optional_hooks> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
.pkg-cpython311: get_requires_for_build_editable> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
.pkg-cpython311: build_editable> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
py311: packaging backend failed (code=error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"), with SystemExit: error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
no previously-included directories found matching 'doc_build'
no previously-included directories found matching 'doc_spell'
no previously-included directories found matching 'tests\eggsrc\build'
C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\wheel\bdist_wheel.py:83: RuntimeWarning: Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
if get_flag("Py_DEBUG", hasattr(sys, "gettotalrefcount"), warn=(impl == "cp")):
Traceback (most recent call last):
File "", line 172, in build_extension
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 549, in build_extension
objects = self.compiler.compile(
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils_msvccompiler.py", line 344, in compile
self.initialize()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils_msvccompiler.py", line 253, in initialize
vc_env = _get_vc_env(plat_spec)
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\msvc.py", line 210, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\msvc.py", line 164, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 140, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 330, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 261, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 288, in _run_build_subcommands
self.run_command(name)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 163, in run
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\build_ext.py", line 84, in run
_build_ext.run(self)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 346, in run
self.build_extensions()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
File "", line 174, in build_extension
BuildFailed
Traceback (most recent call last):
File "", line 172, in build_extension
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 549, in build_extension
objects = self.compiler.compile(
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils_msvccompiler.py", line 344, in compile
self.initialize()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils_msvccompiler.py", line 253, in initialize
vc_env = _get_vc_env(plat_spec)
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\msvc.py", line 210, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\msvc.py", line 164, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 140, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 330, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 261, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\editable_wheel.py", line 288, in _run_build_subcommands
self.run_command(name)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 163, in run
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools\command\build_ext.py", line 84, in run
_build_ext.run(self)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 346, in run
self.build_extensions()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\Lib\site-packages\setuptools_distutils\command\build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
Backend: run command build_editable with args {'wheel_directory': '.tox\.pkg-cpython311\dist', 'config_settings': {'--build-option': []}, 'metadata_directory': None}
running editable_wheel
creating C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info
writing C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\PKG-INFO
writing dependency_links to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\dependency_links.txt
writing entry points to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\entry_points.txt
writing requirements to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\requires.txt
writing top-level names to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\top_level.txt
writing manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\SOURCES.txt'
reading manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
writing manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage.egg-info\SOURCES.txt'
creating 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage-7.2.3a0.dev1.dist-info'
creating C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg-cpython311\dist.tmp-di4cwr_0\coverage-7.2.3a0.dev1.dist-info\WHEEL
running build_py
running build_ext
building 'coverage.tracer' extension
Backend: Wrote response {'code': 'error: Support for editable installs via PEP 660 was recently introduced\nin setuptools. If you are seeing this error, please report to:\n\nhttps://github.com/pypa/setuptools/issues\n\nMeanwhile you can try the legacy behavior by setting an\nenvironment variable and trying to install again:\n\nSETUPTOOLS_ENABLE_FEATURES="legacy-editable"', 'exc_type': 'SystemExit', 'exc_msg': 'error: Support for editable installs via PEP 660 was recently introduced\nin setuptools. If you are seeing this error, please report to:\n\nhttps://github.com/pypa/setuptools/issues\n\nMeanwhile you can try the legacy behavior by setting an\nenvironment variable and trying to install again:\n\nSETUPTOOLS_ENABLE_FEATURES="legacy-editable"'} to C:\Users\Jordan\AppData\Local\Temp\pep517_build_editable-a27vu3v1.json
py311: FAIL ✖ in 0.92 seconds
py312: skipped because could not find python interpreter with spec(s): py312
py312: SKIP ⚠ in 0 seconds
pypy3: skipped because could not find python interpreter with spec(s): pypy3
pypy3: SKIP ⚠ in 0 seconds
.pkg: build_editable> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
doc: packaging backend failed (code=error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"), with SystemExit: error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
no previously-included directories found matching 'doc_build'
no previously-included directories found matching 'doc_spell'
no previously-included directories found matching 'tests\eggsrc\build'
C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\wheel\bdist_wheel.py:83: RuntimeWarning: Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
if get_flag("Py_DEBUG", hasattr(sys, "gettotalrefcount"), warn=(impl == "cp")):
Traceback (most recent call last):
File "", line 172, in build_extension
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 549, in build_extension
objects = self.compiler.compile(
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 344, in compile
self.initialize()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 253, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 210, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 164, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 140, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 330, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 261, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 288, in _run_build_subcommands
self.run_command(name)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 163, in run
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 84, in run
_build_ext.run(self)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 346, in run
self.build_extensions()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
File "", line 174, in build_extension
BuildFailed
Traceback (most recent call last):
File "", line 172, in build_extension
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 549, in build_extension
objects = self.compiler.compile(
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 344, in compile
self.initialize()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils_msvccompiler.py", line 253, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 210, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\msvc.py", line 164, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 140, in run
self._create_wheel_file(bdist_wheel)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 330, in _create_wheel_file
files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 261, in _run_build_commands
self._run_build_subcommands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 288, in _run_build_subcommands
self.run_command(name)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "", line 163, in run
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\build_ext.py", line 84, in run
_build_ext.run(self)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 346, in run
self.build_extensions()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\command\build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
File "", line 174, in build_extension
BuildFailed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\core.py", line 201, in run_commands
dist.run_commands()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 969, in run_commands
self.run_command(cmd)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\dist.py", line 1213, in run_command
super().run_command(command)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\dist.py", line 988, in run_command
cmd_obj.run()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\command\editable_wheel.py", line 154, in run
raise errors.InternalError(cleandoc(msg)) from ex
distutils.errors.DistutilsInternalError: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py", line 90, in run
outcome = backend_proxy(parsed_message["cmd"], **parsed_message["kwargs"])
File "C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py", line 32, in call
return getattr(on_object, name)(*args, **kwargs)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\build_meta.py", line 442, in build_editable
return self._build_with_temp_dir(
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\build_meta.py", line 398, in build_with_temp_dir
self.run_setup()
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools\build_meta.py", line 335, in run_setup
exec(code, locals())
File "", line 224, in
File "", line 214, in main
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_init.py", line 108, in setup
return distutils.core.setup(**attrs)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\core.py", line 185, in setup
return run_commands(dist)
File "C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\lib\site-packages\setuptools_distutils\core.py", line 215, in run_commands
raise SystemExit("error: " + str(msg))
SystemExit: error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable"
Backend: run command build_editable with args {'wheel_directory': '.tox\.pkg\dist', 'config_settings': {'--build-option': []}, 'metadata_directory': None}
running editable_wheel
creating C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info
writing C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\PKG-INFO
writing dependency_links to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\dependency_links.txt
writing entry points to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\entry_points.txt
writing requirements to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\requires.txt
writing top-level names to C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\top_level.txt
writing manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\SOURCES.txt'
reading manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
writing manifest file 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage.egg-info\SOURCES.txt'
creating 'C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage-7.2.3a0.dev1.dist-info'
creating C:\Users\Jordan\Desktop\Coding\Devmountain\14Week\coveragepy.tox.pkg\dist.tmp-2nm_ilf8\coverage-7.2.3a0.dev1.dist-info\WHEEL
running build_py
running build_ext
building 'coverage.tracer' extension
Backend: Wrote response {'code': 'error: Support for editable installs via PEP 660 was recently introduced\nin setuptools. If you are seeing this error, please report to:\n\nhttps://github.com/pypa/setuptools/issues\n\nMeanwhile you can try the legacy behavior by setting an\nenvironment variable and trying to install again:\n\nSETUPTOOLS_ENABLE_FEATURES="legacy-editable"', 'exc_type': 'SystemExit', 'exc_msg': 'error: Support for editable installs via PEP 660 was recently introduced\nin setuptools. If you are seeing this error, please report to:\n\nhttps://github.com/pypa/setuptools/issues\n\nMeanwhile you can try the legacy behavior by setting an\nenvironment variable and trying to install again:\n\nSETUPTOOLS_ENABLE_FEATURES="legacy-editable"'} to C:\Users\Jordan\AppData\Local\Temp\pep517_build_editable-fjde8_x4.json
doc: FAIL ✖ in 0.34 seconds
lint: install_deps> python -m pip install -U -r requirements/lint.pip
Collecting alabaster==0.7.13
Using cached alabaster-0.7.13-py3-none-any.whl (13 kB)
Collecting astroid==2.15.0
Using cached astroid-2.15.0-py3-none-any.whl (277 kB)
Collecting attrs==22.2.0
Using cached attrs-22.2.0-py3-none-any.whl (60 kB)
Collecting babel==2.12.1
Using cached Babel-2.12.1-py3-none-any.whl (10.1 MB)
Collecting bleach==6.0.0
Using cached bleach-6.0.0-py3-none-any.whl (162 kB)
Collecting build==0.10.0
Using cached build-0.10.0-py3-none-any.whl (17 kB)
Collecting cachetools==5.3.0
Using cached cachetools-5.3.0-py3-none-any.whl (9.3 kB)
Collecting certifi==2022.12.7
Using cached certifi-2022.12.7-py3-none-any.whl (155 kB)
Collecting chardet==5.1.0
Using cached chardet-5.1.0-py3-none-any.whl (199 kB)
Collecting charset-normalizer==3.1.0
Using cached charset_normalizer-3.1.0-cp310-cp310-win_amd64.whl (97 kB)
Collecting check-manifest==0.49
Using cached check_manifest-0.49-py3-none-any.whl (20 kB)
Collecting click==8.1.3
Using cached click-8.1.3-py3-none-any.whl (96 kB)
Collecting click-log==0.4.0
Using cached click_log-0.4.0-py2.py3-none-any.whl (4.3 kB)
Collecting cogapp==3.3.0
Using cached cogapp-3.3.0-py2.py3-none-any.whl (28 kB)
Collecting colorama==0.4.6
Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Collecting dill==0.3.6
Using cached dill-0.3.6-py3-none-any.whl (110 kB)
Collecting distlib==0.3.6
Using cached distlib-0.3.6-py2.py3-none-any.whl (468 kB)
Collecting docutils==0.18.1
Using cached docutils-0.18.1-py2.py3-none-any.whl (570 kB)
Collecting exceptiongroup==1.1.1
Using cached exceptiongroup-1.1.1-py3-none-any.whl (14 kB)
Collecting execnet==1.9.0
Using cached execnet-1.9.0-py2.py3-none-any.whl (39 kB)
Collecting filelock==3.10.0
Using cached filelock-3.10.0-py3-none-any.whl (9.9 kB)
Collecting flaky==3.7.0
Using cached flaky-3.7.0-py2.py3-none-any.whl (22 kB)
Collecting greenlet==2.0.2
Using cached greenlet-2.0.2-cp310-cp310-win_amd64.whl (192 kB)
Collecting hypothesis==6.70.0
Using cached hypothesis-6.70.0-py3-none-any.whl (403 kB)
Collecting idna==3.4
Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting imagesize==1.4.1
Using cached imagesize-1.4.1-py2.py3-none-any.whl (8.8 kB)
Collecting importlib-metadata==6.0.0
Using cached importlib_metadata-6.0.0-py3-none-any.whl (21 kB)
Collecting importlib-resources==5.12.0
Using cached importlib_resources-5.12.0-py3-none-any.whl (36 kB)
Collecting iniconfig==2.0.0
Using cached iniconfig-2.0.0-py3-none-any.whl (5.9 kB)
Collecting isort==5.11.5
Using cached isort-5.11.5-py3-none-any.whl (104 kB)
Collecting jaraco-classes==3.2.3
Using cached jaraco.classes-3.2.3-py3-none-any.whl (6.0 kB)
Collecting jedi==0.18.2
Using cached jedi-0.18.2-py2.py3-none-any.whl (1.6 MB)
Collecting jinja2==3.1.2
Using cached Jinja2-3.1.2-py3-none-any.whl (133 kB)
Collecting keyring==23.13.1
Using cached keyring-23.13.1-py3-none-any.whl (37 kB)
Collecting lazy-object-proxy==1.9.0
Using cached lazy_object_proxy-1.9.0-cp310-cp310-win_amd64.whl (22 kB)
Collecting libsass==0.22.0
Using cached libsass-0.22.0-cp37-abi3-win_amd64.whl (880 kB)
Collecting livereload==2.6.3
Using cached livereload-2.6.3-py2.py3-none-any.whl (24 kB)
Collecting markdown-it-py==2.2.0
Using cached markdown_it_py-2.2.0-py3-none-any.whl (84 kB)
Collecting markupsafe==2.1.2
Using cached MarkupSafe-2.1.2-cp310-cp310-win_amd64.whl (16 kB)
Collecting mccabe==0.7.0
Using cached mccabe-0.7.0-py2.py3-none-any.whl (7.3 kB)
Collecting mdurl==0.1.2
Using cached mdurl-0.1.2-py3-none-any.whl (10.0 kB)
Collecting more-itertools==9.1.0
Using cached more_itertools-9.1.0-py3-none-any.whl (54 kB)
Collecting packaging==23.0
Using cached packaging-23.0-py3-none-any.whl (42 kB)
Collecting parso==0.8.3
Using cached parso-0.8.3-py2.py3-none-any.whl (100 kB)
Collecting pkginfo==1.9.6
Using cached pkginfo-1.9.6-py3-none-any.whl (30 kB)
Collecting platformdirs==3.1.1
Using cached platformdirs-3.1.1-py3-none-any.whl (14 kB)
Collecting pluggy==1.0.0
Using cached pluggy-1.0.0-py2.py3-none-any.whl (13 kB)
Collecting pudb==2022.1.3
Using cached pudb-2022.1.3.tar.gz (220 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting pyenchant==3.2.2
Using cached pyenchant-3.2.2-py3-none-win_amd64.whl (11.9 MB)
Collecting pygments==2.14.0
Using cached Pygments-2.14.0-py3-none-any.whl (1.1 MB)
Collecting pylint==2.17.0
Using cached pylint-2.17.0-py3-none-any.whl (535 kB)
Collecting pyproject-api==1.5.1
Using cached pyproject_api-1.5.1-py3-none-any.whl (12 kB)
Collecting pyproject-hooks==1.0.0
Using cached pyproject_hooks-1.0.0-py3-none-any.whl (9.3 kB)
Collecting pytest==7.2.2
Using cached pytest-7.2.2-py3-none-any.whl (317 kB)
Collecting pytest-xdist==3.2.1
Using cached pytest_xdist-3.2.1-py3-none-any.whl (41 kB)
Collecting pytz==2022.7.1
Using cached pytz-2022.7.1-py2.py3-none-any.whl (499 kB)
Collecting readme-renderer==37.3
Using cached readme_renderer-37.3-py3-none-any.whl (14 kB)
Collecting requests==2.28.2
Using cached requests-2.28.2-py3-none-any.whl (62 kB)
Collecting requests-toolbelt==0.10.1
Using cached requests_toolbelt-0.10.1-py2.py3-none-any.whl (54 kB)
Collecting rfc3986==2.0.0
Using cached rfc3986-2.0.0-py2.py3-none-any.whl (31 kB)
Collecting rich==13.3.2
Using cached rich-13.3.2-py3-none-any.whl (238 kB)
Collecting scriv==1.2.1
Using cached scriv-1.2.1-py2.py3-none-any.whl (32 kB)
Collecting six==1.16.0
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting snowballstemmer==2.2.0
Using cached snowballstemmer-2.2.0-py2.py3-none-any.whl (93 kB)
Collecting sortedcontainers==2.4.0
Using cached sortedcontainers-2.4.0-py2.py3-none-any.whl (29 kB)
Collecting sphinx==5.3.0
Using cached sphinx-5.3.0-py3-none-any.whl (3.2 MB)
Collecting sphinx-autobuild==2021.3.14
Using cached sphinx_autobuild-2021.3.14-py3-none-any.whl (9.9 kB)
Collecting sphinx-rtd-theme==1.2.0
Using cached sphinx_rtd_theme-1.2.0-py2.py3-none-any.whl (2.8 MB)
Collecting sphinxcontrib-applehelp==1.0.2
Using cached sphinxcontrib_applehelp-1.0.2-py2.py3-none-any.whl (121 kB)
Collecting sphinxcontrib-devhelp==1.0.2
Using cached sphinxcontrib_devhelp-1.0.2-py2.py3-none-any.whl (84 kB)
Collecting sphinxcontrib-htmlhelp==2.0.0
Using cached sphinxcontrib_htmlhelp-2.0.0-py2.py3-none-any.whl (100 kB)
Collecting sphinxcontrib-jquery==4.1
Using cached sphinxcontrib_jquery-4.1-py2.py3-none-any.whl (121 kB)
Collecting sphinxcontrib-jsmath==1.0.1
Using cached sphinxcontrib_jsmath-1.0.1-py2.py3-none-any.whl (5.1 kB)
Collecting sphinxcontrib-qthelp==1.0.3
Using cached sphinxcontrib_qthelp-1.0.3-py2.py3-none-any.whl (90 kB)
Collecting sphinxcontrib-restbuilder==0.3
Using cached sphinxcontrib_restbuilder-0.3-py2.py3-none-any.whl (11 kB)
Collecting sphinxcontrib-serializinghtml==1.1.5
Using cached sphinxcontrib_serializinghtml-1.1.5-py2.py3-none-any.whl (94 kB)
Collecting sphinxcontrib-spelling==8.0.0
Using cached sphinxcontrib_spelling-8.0.0-py3-none-any.whl (16 kB)
Collecting tomli==2.0.1
Using cached tomli-2.0.1-py3-none-any.whl (12 kB)
Collecting tomlkit==0.11.6
Using cached tomlkit-0.11.6-py3-none-any.whl (35 kB)
Collecting tornado==6.2
Using cached tornado-6.2-cp37-abi3-win_amd64.whl (425 kB)
Collecting tox==4.4.7
Using cached tox-4.4.7-py3-none-any.whl (148 kB)
Collecting tox-gh==1.0.0
Using cached tox_gh-1.0.0-py3-none-any.whl (5.9 kB)
Collecting twine==4.0.2
Using cached twine-4.0.2-py3-none-any.whl (36 kB)
Collecting typed-ast==1.5.4
Using cached typed_ast-1.5.4-cp310-cp310-win_amd64.whl (162 kB)
Collecting typing-extensions==4.5.0
Using cached typing_extensions-4.5.0-py3-none-any.whl (27 kB)
Collecting urllib3==1.26.15
Using cached urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
Collecting urwid==2.1.2
Using cached urwid-2.1.2.tar.gz (634 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting urwid-readline==0.13
Using cached urwid_readline-0.13.tar.gz (7.9 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting virtualenv==20.21.0
Using cached virtualenv-20.21.0-py3-none-any.whl (8.7 MB)
Collecting webencodings==0.5.1
Using cached webencodings-0.5.1-py2.py3-none-any.whl (11 kB)
Collecting wrapt==1.15.0
Using cached wrapt-1.15.0-cp310-cp310-win_amd64.whl (36 kB)
Collecting zipp==3.15.0
Using cached zipp-3.15.0-py3-none-any.whl (6.8 kB)
Collecting pip==23.0.1
Using cached pip-23.0.1-py3-none-any.whl (2.1 MB)
Collecting setuptools==65.7.0
Using cached setuptools-65.7.0-py3-none-any.whl (1.2 MB)
Collecting pywin32-ctypes>=0.2.0
lint: FAIL ✖ in 21.34 seconds                                                                         b842edf10007e4547ea8157b0b9fc78599a/pywin32_ctypes-0.2.0-py2.py3-none-any.whl (from keyring==23.13.1->-r requirements/lint.pip (line 300
mypy: skipped because could not find python interpreter with spec(s): python3.8
.pkg: _exit> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2ip install -U -r requirements/lint.pip pid=29192kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta
.pkg-cpython311: _exit> python C:\Users\Jordan\AppData\Local\Packages\PythonSoftwareFoundation.Python.kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_meta3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True se3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\pyproject_api_backend.py True setuptools.build_metatuptools.build_meta
py37: SKIP (0.00 seconds)
py38: SKIP (0.00 seconds)
py39: SKIP (0.02 seconds)
py310: FAIL code error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable" (1.09 seconds)
py311: FAIL code error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable" (0.92 seconds)
py312: SKIP (0.00 seconds)
pypy3: SKIP (0.00 seconds)
doc: FAIL code error: Support for editable installs via PEP 660 was recently introduced
in setuptools. If you are seeing this error, please report to:
https://github.com/pypa/setuptools/issues
Meanwhile you can try the legacy behavior by setting an
environment variable and trying to install again:
SETUPTOOLS_ENABLE_FEATURES="legacy-editable" (0.33 seconds)
lint: FAIL code 1 (21.34 seconds)
mypy: SKIP (0.11 seconds)
evaluation failed :( (24.69 seconds)

Hi @talihashi, this seems to be at the core of the error:

distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/

Have you tried to install Microsoft Visual C++ and try again?
My recommendations for debugging this problem are:

Try to install the project normally, without using the editable mode.
Does the error still persist?
(If it does, try fixing the problem before attempting the editable mode).
If you are using binary extensions, make sure you have all OS-level dependencies installed (e.g. compilers, toolchains, binary libraries, ...).
Try the latest version of setuptools (maybe the error was already fixed).
If you (or your project dependencies) are using any setuptools extension or customization, make sure they support the editable mode.


Add parameter to PlutoRow to block edits

Hello @bosskmk ,
Hope you are doing well! thanks for this awesome package!
I am running into a use case where I need to block edits on certain rows. Do you think we could eventually have a enableEditingMode bool on the PlutoRow class?
thanks,
K

You can restrict editing of rows in certain states.
However, it is limited to cells in a specific row.
Could you please refer to the link below?
If you add a row with add rows , you can edit the Id cell, but you cannot edit the Id cell for a row that has already been added.
Please try this and if it doesn't work, please comment again.
https://weblaze.dev/pluto_grid/build/web/#add-and-remove-column-row


Fix typos in upgrading_version_7.adoc

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Multi-line task list items don't properly indent

Problem Summary
When a task list item is very long and wraps to a new line the additional lines are not indented to align with the text on the first line.  Instead the text is aligned with the checkbox.

Reproducing the Problem
The following markdown:
### Task List Alignment Issue

- [ ] Single line task
- [ ] Multiple line task.  Because I have a whole lot to explain for this task, as it is potentially exceptionally complex, and I am putting it all on one task list item even though I would probably be better suited to splitting it into multiple tasks or sub tasks.  Phew!
- [ ] Another single line task

Renders like this:

Console Error
There is an error in the console but I don't think it is related to this issue.  Here it is anyway, just in case.
[Extension Host] [vscode.markdown-language-features] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[markdown]', provide the URI of a resource or 'null' for any resource.
t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:393
(anonymous) @ extensionHost.ts:210
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104

Fixed in the latest CI build. You can find the download link at the end of README.

Thanks!


TILSDK-34: update code to php 8 & use attributes instead of tons of methods

PLEASE DO NOT SQUASH!


set up operator monitoring

People we don't know inquire about being operators, sometimes they seem trustworthy. We should be able to evaluate their work, then we could add them and remove them if they are not appropriate.
Log or metric when operator accepts call, including number

this is the MVP
then we could check the operator log, see how they describe calls or ask why they haven't logged

Record operator calls

stretch goal
notify both sides or at least the caller

MixMonitor to record?
use the b argument to followme to gosub to a context that starts MixMonitor?
use the b argument to followme to gosub to a context that logs operator?


Remove note about systemctl

What article on docs.github.com is affected?
<EMAIL_ADDRESS>What part(s) of the article would you like to see updated?
The note about systemctl should be removed.
Additional information
Since 2.22 services have begun to migrate to Nomad, and are no longer available with systemctl. Customers can't find many important services to restart. It doesn't look like there is anything about Nomad in the command line page, so this is best simply removed.

@lecoursen Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

Images and photos  videos


Feature request: Object tree transfer of ownership between isolates

Basically I want a way to transfer an object (and all other objects linked from it) from one isolate to another.
Right now you can only transfer basic primitives, lists and maps between isolates.

You should be able to transfer anything between isolates except a few rare types like closures. It might be limited to immutable types? Not sure. But it's definitely more than just primitives. See for example: https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/services/binding.dart#L64
Does that satisfy your needs?

The example you provided is just transferring a list of strings which is supported as stated above (basic primitives, lists and maps).

I thought this was supported but then reverted but I'm not sure.
Anyway I guess this should be reported in the Dart SDK repo.

If you think there is still something that needs to be done, please create a new issue in the dart-lang/sdk repo. Isolates are not Flutter specific.


fix llvm3.9 builds on windows

Looks like LLVM 3.9 decided to change the output format of llvm-config --libs.  This PR changes the build script to account for this and supresses a warning from LLVM headers.

This should fix the CI builds for #1210.

Thanks!

Thank you @kulibali!


dist/redhat: drop dependency on pystache

The scylla.git toolchain moved to Fedora 32, which no longer ships
"pystache". Let's drop the dependency like scylla.git did.

@penberg what about deleting the spec.mustache file ?

@bentsi we'll need to make sure we merge this to enterprise after this get to master

@fruch The pull request renames the file.

Queued to next as 8c2cb2d20bf34bdae33254f87fa0c3fab3c2190a, thanks @fruch!


#3186 - Enhancement and fix for issue - cannot change Versioned $versionableExtensions

Allow Versioned $versionableExtensions to be manipulated via config.

This is an excellent PR, thanks!

Thanks, @tractorcow !

Late to the party, but awesome work!


telemetry: consider environment-specific selection / automation

Describe the feature request
In a discussion of access logging on VMs, an issue with systemd-based logging was raised regarding access to /dev/stdout. It appears that in various environments, a blanket configuration to log to /dev/stdout could cause access logging to fail.
At the moment, it should be possible to use the Telemetry API to select different providers per namespace or per workload. However, if VMs are distributed across multiple namespaces, etc., it could be cumbersome to define Telemetry resources in each namespace that select on a given VM-specific label and to label each VM with that consistent label to enable overriding of provider selection.
We should determine if it makes sense, at some level, to allow configuration at the provider level for environment-specific customizations. Alternatively, should we make it easier to provide mesh-wide defaults per environment? Another option would be to automatically detect /dev/stdout in certain environments and automatically redirect to a well-known path (something like: /var/log/istio/proxy.log).
Describe alternatives you've considered
Define two providers in MeshConfig. Label all VMs in all namespaces with something like "istio-env: vm". Create Telemetry resources in all namespaces with a WorkloadSelector with something like matchLabels: istio-env: vm.
Affected product area (please put an X in all that apply)
[ X ] Extensions and Telemetry
[ X ] User Experience
Affected features (please put an X in all that apply)
[ X ] Virtual Machine
Additional context
/cc: @GregHanson @linsun @zirain @costinm

Define two providers in MeshConfig. Label all VMs in all namespaces with something like "istio-env: vm". Create Telemetry resources in all namespaces with a WorkloadSelector with something like matchLabels: istio-env: vm.

do you means some like discoverySelectors, but for Telemetry?
if we decide to add something, I prefer to use annotation.

link to https://github.com/istio/istio/issues/30598

if we decide to add something, I prefer to use annotation.

In that particular example, I was suggesting using the existing label-based WorkloadSelector implementation. If we want to pursue an annotation-based approach, we would need to ensure selection could happen.
Having some environment aware behavior might be better for users?
This came out of a discussion in one of the community meetings re: VM issues.

For security (and other cases), agent detects the environment and adds some
node metadata automatically. There is no reason for user to have to
configure things that we can auto-configure or detect.
The current API is probably wrong - it should not explicitly specify a
file, just 'enable', and let the implementation pick.
On Mon, Apr 18, 2022, 10:29 Douglas Reid @.***> wrote:

if we decide to add something, I prefer to use annotation.
In that particular example, I was suggesting using the existing
label-based WorkloadSelector implementation. If we want to pursue an
annotation-based approach, we would need to ensure selection could happen.
Having some environment aware behavior might be better for users?
This came out of a discussion in one of the community meetings re: VM
issues.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/38271#issuecomment-1101589059, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2WD22FI3HJGNPJSRBTVFWLV5ANCNFSM5SWUQDEQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

For security (and other cases), agent detects the environment and adds some
node metadata automatically. There

@costinm do you means OWNER: kubernetes://apis/apps/v1/namespaces/default/deployments/httpbin?
metadata:
        ANNOTATIONS:
          kubectl.kubernetes.io/default-container: httpbin
          kubectl.kubernetes.io/default-logs-container: httpbin
          kubernetes.io/config.seen: "2022-04-07T08:30:03.148168045Z"
          kubernetes.io/config.source: api
          prometheus.io/path: /stats/prometheus
          prometheus.io/port: "15020"
          prometheus.io/scrape: "true"
          proxy.istio.io/config: |-
            proxyStatsMatcher:
              inclusionPrefixs:
              - 'http'
          sidecar.istio.io/status: '{"initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["istio-envoy","istio-data","istio-podinfo","istio-token","istiod-ca-cert"],"imagePullSecrets":null,"revision":"default"}'
        APP_CONTAINERS: httpbin
        CLUSTER_ID: Kubernetes
        DNS_CAPTURE: "true"
        ENVOY_PROMETHEUS_PORT: 15090
        ENVOY_STATUS_PORT: 15021
        INSTANCE_IPS: <IP_ADDRESS>,fe80::6c8f:bbff:fec7:2297
        INTERCEPTION_MODE: REDIRECT
        ISTIO_PROXY_SHA: istio-proxy:ff44db02db5a99a7f06c31441c3a5a0f7ce9e2b4
        ISTIO_VERSION: 1.12.0
        LABELS:
          app: httpbin
          pod-template-hash: 65b46bcd4f
          security.istio.io/tlsMode: istio
          service.istio.io/canonical-name: httpbin
          service.istio.io/canonical-revision: v1
          version: v1
        MESH_ID: mesh1
        NAME: httpbin-65b46bcd4f-t9sr7
        NAMESPACE: default
        OWNER: kubernetes://apis/apps/v1/namespaces/default/deployments/httpbin
        PILOT_SAN:
        - istiod.istio-system.svc
        POD_PORTS: '[{"containerPort":80,"protocol":"TCP"}]'
        PROV_CERT: var/run/secrets/istio/root-cert.pem
        PROXY_CONFIG:
          binaryPath: /usr/local/bin/envoy
          concurrency: 2
          configPath: ./etc/istio/proxy
          controlPlaneAuthPolicy: MUTUAL_TLS
          discoveryAddress: istiod.istio-system.svc:15012
          drainDuration: 45s
          extraStatTags:
          - url_path
          - response_status
          meshId: mesh1
          parentShutdownDuration: 60s
          proxyAdminPort: 15000
          proxyMetadata:
            BOOTSTRAP_XDS_AGENT: "true"
            ISTIO_META_DNS_CAPTURE: "true"
          proxyStatsMatcher: {}
          serviceCluster: httpbin.default
          statNameLength: 189
          statusPort: 15020
          terminationDrainDuration: 5s
          tracing:
            zipkin:
              address: zipkin.istio-system:9411
        SERVICE_ACCOUNT: httpbin
        WORKLOAD_NAME: httpbin