Add support for generating dot output from yotta

This modifies yotta list to add support for generating Graphviz dot output.  The output is just dumped to stdout, where it can be processed by the dot tool, or redirected to a file.
While I did highlight test dependencies in blue, missing dependencies in red, I did not see support in yotta list for identifying testDependencies and their selection criteria.

cc @salkinium @bogdanm

:ok_hand: :+1: :smile: :beers: :cocktail: :tada: :confetti_ball: :notes: :crescent_moon: zzzz

Usage: yotta list --dot --all | dot -Tpdf -o ytls.pdf && open ytls.pdf

For reference, you don't need to generate PDFs with it.  Dot supports many output formats.

As discussed, would prefer to do this as yotta ls --json | someprogram | dot. This is definitely a very useful concept though.

Closing this because I think yotta ls --json | sometool is the right approach. The JSON format will be stable once #508 lands.


Ana Carolina's useful resources

Pull Request
Types of changes made
Modified Issue_Resource_Template.md in order to include three more useful resources and my name and interests in relation to issue #7

@all-contributors add @anacarolinaarellano for docs


Support for Python 3.11?

Does strawberry-django-auth support 3.11? I see it listed on the badge, but when I try to install it via poetry, I get this error:
The current project's Python requirement (>=3.10,<4.0) is not compatible with some of the required packages Python requirement:

strawberry-django-auth requires Python >=3.8,<3.11, so it will not be satisfied for Python >=3.11,<4.0

oh it is just poetry thing, I'll need to update pyproject.toml.. other than that tests are running agianst 3.11 as well.


Is It Possible To Get This to Work With MongoDB's ObjectId Type

Thanks for the excellent library!  Polymorphic ids is such a great idea!
Is it possible to get this to work with MongoDB's MongoDB.Bson.ObjectId type? Or, is it even a good idea to use ObjectId as an ID field?
    [NodeEx]
    public class SomeEntity
    {
        /// <summary>
        /// Id that uniquely identifies this entity
        /// </summary>
        [ID]
        public ObjectId Id { get; set; }

        [Required]
        public string? Name { get; set; }

        public string? Description { get; set; }

        public static async Task<SomeEntity> Get([ID] ObjectId id,
            [Service] SomeEntityDataLoader service)
        {
            var node= await service.LoadAsync(id);
            return node;
        }
    }

It looks like a code change would be necessary for custom types.  For now I have switched to representing my ObjectId as a string to get polymorphic id's working:
        [ID]
        [BsonRepresentation(BsonType.ObjectId)]
        public string Id { get; set; } = string.Empty;

Sorry @bbrandt , happy to leave this open and have a closer look when I get time. It's been a while since I've been in MongoDB land. What type do you represent mongo ids as usually @pascalsenn?

Thanks for the reply.
I do not need it left open as we are early in our project with HC and Mongo, making it cheap to do, and switching over to string is working great for us.


build(deps): Remove cometbft-db from cometbft build.

Partially addresses #4486.
This PR removes cometbft-db from cometbft build process:

Dockerfiles
Makefiles
CI

Note to Reviewers
Please add in the discussion below any file that I have forgotten to update.

PR checklist

~[ ] Tests written/updated~
~[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)~
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Should we update the docs about how to build cometbft in this PR, or as part of a single future PR (to be merged in the feature branch as well) in which we update ALL the docs to remove mentions to cometbft-db and add new information?

I am in favor of doing this separately as it can take a lot of time, and it should not block the implementation. Make sure we have an issue for it.


Contextual button moves blocks to the left outside of clickable area

When the contextual button is visible, roam blocks are shifted to the left like in the following screenshot:

I've flagged this but can't narrow down the specific cause... I could hack a fix but would like to investigate more & figure out why it's happening exactly before publishing a change. Adding to my TODOs!

Btw. just tested this in a completely empty graph. Same behavior on
ROAM VERSION:
0.8.8-394e628e

Hey @sebastianpech - I was able to reproduce the issue previously in my own graph, and was working on a fax, but after recent updates in Roam version I can't reproduct this behavior anymore.
Is this still happening for you ?
ROAM VERSION:
0.8.8-908838fd

It's not happening on the DNP page directly, but if you are in the DNP overview, the issue is still there.

I can confirm this still hapenning on the daily page in ROAM VERSION: 0.8.8-ebc7098a
The .zotero-roam-page-related{opacity:0.6;float:right;margin-top:-40px;} css style is to blaim. Anything above -30px does the error. I suggest changing it to -30px.


Run save-expect with Scala 2.13

Currently, ExpectSuite is defined only in 2.12  https://github.com/scalameta/scalameta/blob/1a9ec6f9aa06e20bc786b5c7ef6d7aa500e59eaf/tests/jvm/src/test/scala-2.12/scala/meta/tests/semanticdb/ExpectSuite.scala

@tgodzik @tanishiking did #2995 fix this issue?

I think so, let's close it


Ability to specify left right padding on columns as well As vertical margin between rows

@troolee In some cases you want to be able to define the padding on columns and rows.  By default currently rows have a padding of 20px and columns have a padding of 10px on both left and right sides.  These values should be options.  This will allow users to have grid items touch if so desired.

just out of curiosity. Why is it 20 and not 0 by default.. or configuratble anyway, it seems to me a usual need.. any thoughts welcome in advance.

I'm slightly stumped why there's no horizontal margin setting. Over-riding the horizontal margin settings in CSS does not seem to work for me. So I have a nice 20px gap between rows and no gap at all between columns.

I found that I had to add a class to the selector to get a high enough specificity:
.grid-stack .grid-stack-item .grid-stack-item-content,
.grid-stack .grid-stack-item .placeholder-content {
    left: 10px;
    right: 10px;
}


When a link was disconnected from inlet, node/process should be called with default value for this inlet

Should it? It is possible to create the util/clear node, similar to a util/bang one, so it would send clear-signal to any inlet (not to revert to default, though).
The problem here is that this behaviour looks unexpected when there's no streams coming through connections. On the other hand, it also looks illogical to send any value to inlet on disconnect.


Get tests to pass when running Julia with --compiled-modules=no.

This fixes https://github.com/chriselrod/LoopVectorization.jl/issues/192#issuecomment-771332647 for me: Trixi's tests pass, as do ArrayInterface's after starting Julia with --compiled-modules=no.
Normally, all functions in a module have the same world age, so the order in which generated functions are defined with respect to everything else is irrelevant. But not with --compiled-modules=no, which causes world age errors whenever an @generated function calls a method defined later.
I addressed this the lazy way, but just searching for all the @generated functions calling non-base methods and sticking them in a file at the end.
We could certainly do a lot better organizationally.
@Tokazama I'm not sure why it isn't letting me request you as a reviewer.

We could certainly do a lot better organizationally

Agreed. Did you have any suggestions? I've been trying to move away from having one gigantic file but I probably complicated things in the process

Agreed. Did you have any suggestions? I've been trying to move away from having one gigantic file but I probably complicated things in the process

I think breaking it up into indexing/dimensions/etc is fine, but breaking things up into "is it a @generated function", which this PR did, is not. Except that it fixes world age problems introduced by using --compiled-modules=no.
However, I now deleted generatedfuncs.jl, moving most of the code back, with a much more minor reordering to make sure we don't get world age issues under --compiled-modules=no. @generated definitions should all be following the definitions they're using now, or at least all of them covered by our unit tests.
So this PR is in much better shape/much less objectionable now. I'll merge and make a new release fairly soon.


Update Org json files to setting format

Critical Changes
Based on Salesforce Winer 19, you can specify scratch org settings or org preferences in your scratch org definition file, but not both. Salesforce encourages to convert org preferences to scratch org settings in your scratch org definition. Scratch org settings provide more settings that aren’t currently available as org preferences.
Issues Closed
#24

Thanks for making the update @nickers3! We're having to do it across all the product repos as well. :-)


New arguments for OSS influxdb backup

URL for relevant page?
https://docs.influxdata.com/influxdb/v1.3/administration/backup_and_restore/
What products and version are you using?
influxdb future version 1.5
Where did you look before opening the issue?
new arguments to existing command.  Additive, all existing arguments + operations remain unchanged:
-start <2015-12-24T08:12:23Z>::
All points earlier than this time stamp will be excluded from the export. Not compatible with -since.
-end <2015-12-24T08:12:23Z>::
All points later than this time stamp will be excluded from the export. Not compatible with -since.
-enterprise::
Generate backup files in the format used for influxdb enterprise.

@stevebang   let me know if this is enough to kick off a doc change.  This is my first time making a request; let me know what works for you.

Closing as this was documented, with @aanthony1243 reviewing, for the InfluxDB 1.5 release.


feat: better workflow

Users can now move between open chat buffers with } and {. There is prevention built into the plugin to stop multiple chat buffers being open at the same time. Global variables have also been reduced.

@niba please try this PR out and let me know your thoughts

Wow, that was fast! Thanks! I'll test it tomorrow and update this comment with feedback

Looks like the keymaps in your config don't conform to the new API: https://github.com/olimorris/codecompanion.nvim/issues/9#issuecomment-2265075381

I updated my config to the latest version. The version from the main branch works without problems. I even created pr #89 to fix some issues with the new config.
I also tried calling the command directly without using keymaps, and the effect is the same. I will double-check everything.

That's odd. Could you share your complete config with me?

I resolved the issue. You changed the callback names for header navigation, and I still had the old ones in my config. Sorry about that.

Great spot! Yeah I need to do better in terms of breaking the config and making it easier for users to identify what's changed

This is incredibly good. I tested all combinations, and everything works perfectly. Superb job!
The only nitpick I have is this scenario:

Open two chats: Chat 1 and Chat 2.
Destroy Chat 2 - Question: Should destroying a chat close the chat buffer or shift focus to the previous/next chat?
Destroying a chat closes it, leaving you in the code buffer. Use the toggle command to bring up the chat buffer again.
The toggle creates a new chat instead of focusing on existing one. This only happens when your last action in the chat buffer was to destroy a chat.

Thanks!
Functionally, everything works, but there is one small visual detail. I have Treesitter context on my code buffer that renders a white line and function header. When I jump between chats, this line and header appear across the entire screen for a few milliseconds. I didn't notice this thing in the previous version.
Gif:

That seems really odd as it shouldn't technically draw the lines. I've just remove some debug statements that were there purely for testing...that's technically an I/O request if you have the log level at debug (I need to make that async!). Let me know if it continues.

@olimorris  so I tested it this morning and this is still happenning
I manage to resolve it by changing the order of operations
    chats[index].chat:hide()
    chats[next].chat:open()

    to =>

    chats[next].chat:open()
    chats[index].chat:hide()

I also noticed that the width of my chat window jumps. You should probably try to read the current width and height of the window (if the chat is visible) and pass it to the open function, then try to reuse it inside"

Bizarrely I only find the jumping occurs when the order is open and then hide. If you do hide and open it seems to be fine.
I believe that's because it's trying to open a chat buffer in the already open split. I'd advise playing around with the minimal.lua config in the bug report and seeing if that works. Could be a conflicting plugin. Also, I'm testing this on Nightly so may be something upstream in Neovim that is fixed.

Hmm, that's weird. I want to clarify:
We have two different problems:

Flickering Treesitter context data

This is fixed by swapping hide and open.

Width and height of the chat window jumps

This started appearing when I swapped hide and open. I hadn't realized that I caused this bug, sorry.

When you mentioned 'jumping,' did you mean the second problem?


Connect to Redis over ipv6?

I'm looking at using Redis as a cache on Fly.IO, but traffic to the Upstash instances they provide seems to be routed over ipv6.  From this issue, it seems like this might require passing socket_opts: [:inet6] to Radix, but a cursory look through the prima_auth0_ex code suggests that it's not possible to pass additional options to Radix.  Have I missed something?

Hello! Right now prima_auth0_ex doesn't expose generic options for Redix so you are right.
The simplest thing would be to expose an option like redis_use_ipv6: true | false. Would that work for you?
We can think about whether we want to let users configure Redix directly. The idea was not to tie users to Redix and thus expose more "agnostic" options, but Redix is the de-facto standard, and mirroring every possible option is not feasible or desirable.


RequiresProjectError: Running Certain SFDX Commands in VSCode and Command Prompt/PowerShell Yields Different Results

Summary
I am able, from within vscode, to execute sfdx force:source:deploy --manifest (…) --json --loglevel fatal command for any manifest location in a project folder from the vscode terminal.
However, I cannot do the same in either Command Prompt or PowerShell, not using vscode.
Steps To Reproduce:

From within vscode with Ctrl+Shift+P run the command SFDX: Create Project with Manifest
Select standard template
Set Project Name
Select folder for project
From within vscode with Ctrl+Shift+P run the command SFDX: Authorize an Org
Select Project default (login.salesforce.com)
Set alias
Browser opens, type in credentials and log ind
In vscode go to Terminal
Type in sfdx force:source:deploy --manifest  --json --loglevel fatal
Successfully deploy (status: 0, result: deployedSource[])
Copy folder from step 4 with all content to a new location
Type in sfdx force:source:deploy --manifest <exact location of package.xml for step 12> --json --loglevel fatal
Successfully deploy (status: 0, result: deployedSource[])
Hit windows key and open Command Prompt
Type sfdx –version to verify that sfdx command can be run outside of vscode
Get response: sfdx-cli/7.43.1-ef237e8b37 win32-x64 node-v10.15.3
Type in sfdx force:source:deploy --manifest  --json --loglevel fatal
Get error (See actual result)
Repeat for new location in Step 12
Get error (See actual result)
Repeat above steps 15-20, just for PowerShell
Get error (See actual result)

Expected result
Since I am able to run sfdx commands outside of vscode, and I have copied the files in the project folder 1:1 to a new location (thus cloning the SFDX project), I expect to be able to deploy and thus get the below result (empty deployedSource, since local repository is identical to org).
{
"status": 0,
"result": {
"deployedSource": []
}
}
Actual result
Both command prompt, powershell throw the same error. The error is not possible for me to decipher, beyond that the context of being within an SFDX project is missing:
Note, the below stack trace should include double backslashes for the folder structure.
{
"status": 1,
"name": "RequiresProjectError",
"message": "This command is required to run from within an SFDX project.",
"exitCode": 1,
"commandName": "SourceDeployCommand",
"stack": "RequiresProjectError: This command is required to run from within an SFDX project.\n    at Function.create (C:\Users\userName\AppData\Local\sfdx\client\7.43.1-ef237e8b37\node_modules\@salesforce\core\lib\sfdxError.js:141:16)\n    at SourceDeployCommand.assignProject (C:\Users\userName\AppData\Local\sfdx\client\7.43.1-ef237e8b37\node_modules\@salesforce\command\lib\sfdxCommand.js:110:40)",
"warnings": []
}
Additional information

SFDX CLI Version (to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.43.1-ef237e8b37 win32-x64 node-v10.15.3
SFDX plugin Version (to find the version of the CLI plugin run sfdx plugins --core):
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 2.2.3 (core)
@oclif/plugin-not-found 1.2.3 (core)
@oclif/plugin-plugins 1.7.9 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.4.1 (core)
generator 1.1.2 (core)
salesforcedx 47.16.0 (core)
├─ salesforcedx-templates 47.17.0 (core)
└─ salesforce-alm 47.15.0 (core)
sfdx-cli 7.43.1 (core)
OS and version:
Windows 10, 64-bit, version 1903

That errors comes when you run a command that requires a project but your
current working directory is not a project, or more specific, doesn’t have
an sfdx-project.json file in it.
VS Code will automatically place the shell prompt into the current
workspace directory but your fresh prompt must be moved (cd ...) into that
same directory.
If you look at your file path in your promp you can see that one appears to
run from a project directory while the other is running at the root of your
user’s profile folder.
On Mon, Feb 3, 2020 at 2:44 PM Nicky Torstensson<EMAIL_ADDRESS>wrote:

Summary
I am able, from within vscode, to execute sfdx force:source:deploy
--manifest (…) --json --loglevel fatal command for any manifest location in
a project folder from the vscode terminal.
However, I cannot do the same in either Command Prompt or PowerShell, not
using vscode.
Steps To Reproduce:

From within vscode with Ctrl+Shift+P run the command SFDX: Create
Project with Manifest
Select standard template
Set Project Name
Select folder for project
From within vscode with Ctrl+Shift+P run the command SFDX:
Authorize an Org
Select Project default (login.salesforce.com)
Set alias
Browser opens, type in credentials and log ind
In vscode go to Terminal
Type in sfdx force:source:deploy --manifest --json --loglevel fatal
Successfully deploy (status: 0, result: deployedSource[])
Copy folder from step 4 with all content to a new location
Type in sfdx force:source:deploy --manifest <exact location of
package.xml for step 12> --json --loglevel fatal
Successfully deploy (status: 0, result: deployedSource[])
Hit windows key and open Command Prompt
Type sfdx –version to verify that sfdx command can be run outside
of vscode
Get response: sfdx-cli/7.43.1-ef237e8b37 win32-x64 node-v10.15.3
Type in sfdx force:source:deploy --manifest --json --loglevel fatal
Get error (See actual result)
Repeat for new location in Step 12
Get error (See actual result)
Repeat above steps 15-20, just for PowerShell
Get error (See actual result)

Expected result
Since I am able to run sfdx commands outside of vscode, and I have copied
the files in the project folder 1:1 to a new location (thus cloning the
SFDX project), I expect to be able to deploy and thus get the below result
(empty deployedSource, since local repository is identical to org).
{
"status": 0,
"result": {
"deployedSource": []
}
}
Actual result
Both command prompt, powershell throw the same error. The error is not
possible for me to decipher, beyond that the context of being within an
SFDX project is missing:
{
"status": 1,
"name": "RequiresProjectError",
"message": "This command is required to run from within an SFDX project.",
"exitCode": 1,
"commandName": "SourceDeployCommand",
"stack": "RequiresProjectError: This command is required to run from
within an SFDX project.\n at Function.create
(C:\Users\AppData\Local\sfdx\client\7.43.1-ef237e8b37\node_modules
@salesforce https://github.com/salesforce\core\lib\sfdxError.js:141:16)\n
at SourceDeployCommand.assignProject
(C:\Users\AppData\Local\sfdx\client\7.43.1-ef237e8b37\node_modules
@salesforce https://github.com/salesforce
\command\lib\sfdxCommand.js:110:40)",
"warnings": []
}
Additional information
[image: vscode vs command prompt]
https://user-images.githubusercontent.com/55800560/73693311-430b9680-46d6-11ea-841f-05a462b9494c.png
SFDX CLI Version(to find the version of the CLI engine run sfdx
--version):
sfdx-cli/7.43.1-ef237e8b37 win32-x64 node-v10.15.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx
plugins --core):
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 2.2.3 (core)
@oclif/plugin-not-found 1.2.3 (core)
@oclif/plugin-plugins 1.7.9 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.4.1 (core)
generator 1.1.2 (core)
salesforcedx 47.16.0 (core)
├─ salesforcedx-templates 47.17.0 (core)
└─ salesforce-alm 47.15.0 (core)
sfdx-cli 7.43.1 (core)
OS and version:
Windows 10, 64-bit, version 1903
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/cli/issues/294?email_source=notifications&email_token=AAQSRPFVIIUD3XO7UICBZATRBCF5LA5CNFSM4KPMSSL2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IKXBV4A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQSRPF5XQ4BTBBHDUBMLXDRBCF5LANCNFSM4KPMSSLQ
.

Hi aheber,
Thanks for the clarification. I was under the impression that since some sfdx commands could be run from anywhere, then that would not be an issue for the force:source:deploy command as well.
Could the error message be made any more clear? As a suggestion, something like:
"RequiresProjectError: This command is required to run from within folder location, where a sfdx-project.json file exists"
I am sorry for the inconvenience of creating a bug.

Not an inconvenience for me ;)
This error is shown in your output:
This command is required to run from within an SFDX project.
It is buried in the JSON structure as you're requesting that output be returned in JSON format (--json)
Some commands will run from anywhere but there are some that would be ambiguous if they ran from anywhere on your file system. These require the context of a project file to help them understand the intent.
You will also find that default orgs are set as part of the project so any command that allows you to leave off the target username in favor of the default org will also normally not work outside of a project. You can still act on the org using the username or alias but not the ability to leave them off and have the command assume the default org.
Hope that helps. Maybe the CLI team will review this and find options for improvement but my guess is they will close and assume the given error message is sufficient.

@aheber I have a follow-up question, which may be a bit off the original topic:
If I authenticate with the command force:auth:jwt:grant (via a connected app), then I would assume I don't need the defaultusername value in the sfdx-config.json file, and then be able to force:source:deploy - but as such that would leave the sfdx-config.json file empty.
Let me know, if I may write you a direct message to not cloud the correspondence on this topic.

I've reached out on LinkedIn. (I think) Feel free to ping me there.
At a high level, force:auth:jwt:grant adds an available connection to your pool of Auth'd orgs (force:org:list). If you use the --setdefaultusername flag and are not in a project directory it will set it globally (~/.sfdx/sfdx-config.json). If you are in a project directory then it is sets locally to the project only (/.sfdx/sfdx-config.json). So that flag will behave slightly differently depending on your current working directory.
If it is set globally then it is used anytime you are not in a project or that project does not have a defaultusername set on its own.
Normally I don't have a default username at a global level. This is usually because we have different projects running and have different defaults per-project. Haven't really needed a default set at the global level.
Hope that helps.


Java Program to check whether number is Armstrong or not

🚀 Feature
Program in Java to check whether the number is Amstrong or not.
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
As a GSSOC'21 participant I would like to work on this issue.
Pitch
For every programmer basic should be clear hence this is one of the most useful program for students to practise.

I want to work on it.I can code it in java. I have read the Contributing Guidelines on Pull Requests. So Please assign me

Greetings sir/Mam,
I would like to contribute the code for Bubble Sort Algorithm #933 in C++/CPP.
The code is ready. I have added the code , along with proper explanation of the algorithm , test cases , time complexity and space complexity of the same, as per the guidelines.
Kindly assign it to me.
This is regarding GSSOC'21.
Regards,
Hitain Kakkar

when will the issue get assigned?

I am a GSSOC participant, Can I work on this issue, I can code it in Java programming language.

@bhav09 please assign me this issue.

/assign


SCP-1826 Verified renaming and substitution for NEAT types via agda2hs

This PR yanks out the definition of well-scoped types, type renaming and substitution used in the NEAT generator into an Agda file and then proves the functor and monad laws for renaming and substitution. We can then compile the Agda file back to Haskell using agda2hs.
The Haskell code remains unchanged except Type.hs is split into Term (not verified) and Type (verified). I wrote my own instance of renaming rather than using deriving Functor for TypeG and I had to kill the import list. I also turned Common.hs into an Agda file to get my hands on the datatypes S (aka Maybe) and Z (aka Empty).
The NEAT generator is supposed to generate only well-typed programs. It is a model of PLC. Its typechecker makes use of type substitution, which makes use of renaming.. These properties are easy to prove but hard to test and currently untested.
I have committed both the Agda code and the Haskell code.
Some questions:

Do we want to commit both Agda and generated Haskell code?
Do we want this at all?

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

If you updated any cabal files or added Haskell packages:

[x] nix-shell shell.nix --run updateMaterialized to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[x] nix-shell shell.nix --run fix-stylish-haskell to fix any formatting issues

If you changed any Purescript files:

[x] nix-shell shell.nix --run fix-purty to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[x] Commits have useful messages
[ ] Review clarifications made it into the code
[x] History is moderately tidy; or going to squash-merge

I think this is cool, and it's a good testbed for actually using something generated by agda2hs - we'll need to do something like this if we wanted to have e.g. verified evaluators using it.
WRT the generation, I think we have two options:

Serious version: require agda2hs as a build tool for plutus-core, add a custom setup to generate the files. Or figure out some other way of doing the code generation.

It would be nice to have a better code generation method but I'm not sure whether there are any...

Easy version: just commit the generated code for now.

The big downsides are that we won't be checking the Agda code and regenerating things will be annoyingly manual.

I think we should probably stick with the easy version for now. Questions:

Is agda2hs on Hackage?
Can we get agda2hs to generate a big scary comment at the top of generated modules saying "This is a generated module, do not edit manually!" or something?

I think this is cool, and it's a good testbed for actually using something generated by agda2hs - we'll need to do something like this if we wanted to have e.g. verified evaluators using it.

Great!

I think we should probably stick with the easy version for now. Questions:

Is agda2hs on Hackage?

No. Perhaps we should consider a release of it. And then it might make sense to do the serious version.

Can we get agda2hs to generate a big scary comment at the top of generated modules saying "This is a generated module, do not edit manually!" or something?

I wrote a warning into each file as a Haskell comment and wrote an Agda comment at the top.

That looks really cool. I wonder if it makes incorporating extensible builtins a harder task, though. I guess we can't embed stuff from Universe.Core in a transparent manner, so that you can for example match on Haskell's Some in Agda? I.e. will we need to (partially) reimplement definitions from Universe.Core in Agda? Not a big deal, I guess.

I think you're right that one would have to replicate Universe.Core as you cannot currently compile it with agda2hs.
I would like to go ahead with this which is quite self contained and we can back it out later if necessary.

@michaelpj do you have any further thoughts?

Seems fine, merge at your leisure!


Status bar area problem

i used "SystemChrome.setEnabledSystemUIMode(SystemUiMode.manual,
overlays: []); " to make the status bar hide when not needed , now its working as needed but now the status bar area is completely black, i wanted my scaffold to extend to that area also.... what should i do ??

@NARIKODANHRIDUL
Your question is better suited for support channels like StackOverflow so please ask the same there.
Closing from here as this isn't a bug or a feature request.


ycmd: 2019-09-19 -> 2020-02-22

Motivation for this change
It seems YCMD was left behind (from YCM) with #80218.
This normally might not make a difference, but this time, they came out of sync with commits that dropped python2 support.
The commits mentioned are https://github.com/ycm-core/YouCompleteMe/pull/3566 and https://github.com/ycm-core/ycmd/pull/1382, both of which were merged within the last month.
This broke YouCompleteMe, throwing the message:
YouCompleteMe unavailable: No module named 'future'
Things done
This PR updates YCMD and disables python2 support for both YCM and YCMD.

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

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

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

The diff looks good, but does last commit need to go with ycmd update? It looks like it touches quite some things beside ycmd

The diff looks good, but does last commit need to go with ycmd update? It looks like it touches quite some things beside ycmd

Assuming that vimPlugins is to be updated with PRs pertaining to any packages in the set, then yes.
I know we need to update the set for plugin additions, though I’m not sure about plugin updates.
Vim Section Docs
This is assuming that the change for dropping python2 support for youcompleteme should be done in this PR, anyway.
As YCMD is a dependency of YCM, I felt this was acceptable.

@rasendubi, @evanjs is right, it's common practice to update all vimplugins before adding a new plugin

@rasendubi, @evanjs is right, it's common practice to update all vimplugins before adding a new plugin

Thanks for clarifying! I wasn’t certain if this also applies to updates!


NIFI-12446 Refactor FilterAttribute to align with code conventions

Summary
Refactors the recently added FilterAttribute processor to align with common code practices followed by other processors, before it's included in a first release version.
NIFI-12446
Note: This targets the support/nifi-1.x branch. The main will be receive a PR once the changes have finalized and this PR is merged.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-12446
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-12446

Pull Request Formatting

[x] Pull Request based on current revision of the mainsupport/nifi-1.x branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21JDK 1.8

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

I've taken a first shot at refactoring the FilterAttribute processor.
I'd appreciate if you'd take a look at the changes @mosermw / @exceptionfactory as you both are familiar with the topic.
I've encountered that allowableValues actually support passing in an enum class (that implements DescribedValue) and that's used by a multitude of existing processors. I thought that is a good match to align the declaration and usage, instead of passing String values around. Let me know what you think about that.
Also I noticed that we did a trim where that was not needed, as were trimming all values beforehand:
                .map(String::trim)
                .filter(attributeName -> !attributeName.trim().isEmpty())`

It seems there is no not() function available (at least for Java 1.8). I think the expression without the trim is now readable enough to: !attributeName.isEmpty(). Do you agree @exceptionfactory?

Merged in https://github.com/apache/nifi/commit/c565e08ccca6c1fce17b1d3de49d7a160cfbee38


add end-to-end tests

It'd be cool if I could have a dir that contains yamls, where each yaml is something like:
given: |
  <markdown contents>
check:
  - ["# my selector"]: |
    <expected markdown for section>
  - [--some-switch, "[]()"]: |
    <expected markdown for links>
  - ...

... and then be able to turn that into a bunch of tests.
This would (a) be useful to have, just for testing; but also (b) be good for documentation of examples.
Ideally, each of those check cases would be a separate sub-test; but I think that would require parsing the yaml at compile-time (so that I can use it in a macro), and I don't know if any libraries allow that.
I do think keeping the md and checks in one file (as opposed to something like test-1.md + test-1-check-1.txt) is useful, because it lets you see the inputs and outputs together more easily.

(note: marking this as "enhancement" and not "task" because of the public-facing nature of the examples. see also #85)

I may be able to use a build script for this: https://doc.rust-lang.org/cargo/reference/build-scripts.html
Also, it looks like the main yaml parser library is in archive mode and not getting any new updates, so I should consider another format. Maybe toml?

(It'd be tempting to use markdown for these tests, but then I wouldn't be able to detect certain failure modes. For example, if the selector # Test cases | - *  erroneously always returned an empty stream, then all of the files would have no test cases, and thus no test cases would fail! I could work around that, but I think it's best to keep it simple and just do the tests in another language.)

ah, this one is still maintained: https://docs.rs/serde_yml/latest/serde_yml/


Add command line argument support

Overview
The main program here only has the option right now to run a simple demo. Instead, it would be great to use main as an entry point to really use the library. For example, we could have things like:

by default, run the demo
run the five-card stats analysis with N samples
run the seven-card stats analysis with N samples
interactively draw and score hands for a selected game

Notes
We should probably do the command line argument parsing with an external crate. Step one for implementing this feature would be to figure out which crate has the best implementation for this project.
Update:
Based on some initial(brief) research (https://rust-cli-recommendations.sunshowers.io/cli-parser.html and Google), it seems like Rust CLAP is probably the best choice in terms of features and standardization, with pico-args being an alternative that has fewer dependencies and build overhead.

You need something like this ?
`// Note: Each of the utility files must be added here as a
// module so that it can be properly included in others.
mod aggregate_score;
mod card;
mod deck;
mod hand;
mod hand_score;
mod hand_stats;
use std::env;
use poker_stats::aggregate_score::sample_aggregate_scores;
use crate::card::Card;
use crate::hand::Hand;
use crate::hand_score::HandScore;
use crate::hand_stats::HandStats;
/// Simple demo for the poker-stats crate. For now it
/// does not support any arguments. It will do three things:
/// (1) print out the cards in a sorted deck
/// For each of two randomly drawn hands:
/// (2) print out the hand
/// (3) compute and print the card stats
fn main() {
let args: Vec = env::args().collect(); // Take args
if args.len() == 1{

    let mut rng = rand::thread_rng();

    println!("Sorted Deck:");
    for id in 0..52 {
        let card = Card { id };
        if card.suit().id == 3 {
            println!("  {}", card);
        } else {
            print!("  {}  ", card);
        }
    }

    println!("");
    let five_card_hand = Hand::<5>::draw(&mut rng);
    println!("{five_card_hand}");
    let hand_stats = HandStats::from(&five_card_hand);
    println!("{hand_stats}");
    let hand_score = HandScore::from(&hand_stats);
    println!("{hand_score}");

    println!("");
    let seven_card_hand = Hand::<7>::draw(&mut rng);
    println!("{seven_card_hand}");
    let hand_stats = HandStats::from(&seven_card_hand);
    println!("{hand_stats}");
    let hand_score = HandScore::from(&hand_stats);
    println!("{hand_score}");

    // Now draw N random hands and check the stats!
    println!("");
    // Note: there is probably some way to deduce the type of the RNG here...
    let scores = sample_aggregate_scores::<5, rand::rngs::ThreadRng>(&mut rng, 20_000);
    println!("{scores}")
}

else if args.len() == 3 && args[2].parse::<u32>().is_ok(){

    let mut rng = rand::thread_rng();

    println!("Sorted Deck:");
    for id in 0..52 {
        let card = Card { id };
        if card.suit().id == 3 {
            println!("  {}", card);
        } else {
            print!("  {}  ", card);
        }
    }

    let num_samples:u32 = args[2].parse().unwrap();
    if args[1] == "five"{
        println!("");
        let five_card_hand = Hand::<5>::draw(&mut rng);
        println!("{five_card_hand}");
        let hand_stats = HandStats::from(&five_card_hand);
        println!("{hand_stats}");
        let hand_score = HandScore::from(&hand_stats);
        println!("{hand_score}");
        let scores = sample_aggregate_scores::<5, rand::rngs::ThreadRng>(&mut rng, num_samples);
        println!("{scores}")
    }

    else if args[1] == "seven"{
        println!("");
        let seven_card_hand = Hand::<7>::draw(&mut rng);
        println!("{seven_card_hand}");
        let hand_stats = HandStats::from(&seven_card_hand);
        println!("{hand_stats}");
        let hand_score = HandScore::from(&hand_stats);
        println!("{hand_score}");
        let scores = sample_aggregate_scores::<7, rand::rngs::ThreadRng>(&mut rng, num_samples);
        println!("{scores}")
    }
}

else if args.len() == 3 && !args[2].parse::<u32>().is_ok(){
    // Print error and Usage
    println!("Usage: Cargo run <hand_number> <sample_number>");
    println!("where hand_number can be five or seven and sample_number can be any integer");
}

else{
    // Print Usage
    println!("Usage: Cargo run <hand_number> <sample_number>");
}

}
`

You need something like this?

Not quite, although something like that might be a step toward a solution. In your proposal, you do manual argument parsing. I want to use an external crate to do the setup for us. There are a variety of reasons to do that, but the key ones are (1) standardization and (2) this is a common problem that other people have carefully studied and solved. There are also lots of weird edge cases that are hard to catch and handle correctly.
Take a look at https://rust-cli-recommendations.sunshowers.io/cli-parser.html for some context. Based on reading that article, it seems like Rust CLAP is probably the best choice in terms of features and standardization, with pico-args being an alternative that has fewer dependencies and build overhead.

Oh ok thanks I will check it and repost the solution

Great!
Otherwise, the general idea of your posted code looked about right: breaking up the existing functionality into a few different command line argument sets.
Feel free to open a PR if you want -- that makes it a bit easier to see the code changes and leave line-by-line comments.

I added the clap and some commands. Please check the PR and let me know the additional things needed and how much the codes deviates.
It shows like this currently:
Usage: poker-stats [OPTIONS] [CARDS_NUMBER] [SAMPLES_NUMBER]
Arguments:
[CARDS_NUMBER]    Number of cards [default: default]
[SAMPLES_NUMBER]  Number of samples [default: 20000]
Options:
-r, --run      Run program
-h, --help     Print help
-V, --version  Print version
Cards_number can take two values five and seven and to run the program one should use the -r option.

Thanks!  I'll take a more detailed look at the code (and try out the new feature!) sometime in the next week.

Did few changes. Refactored the functions in main.rs to new file output.rs. And a few more things as required per the review.

This has been (mostly) resolved by https://github.com/MatthewPeterKelly/poker-stats/pull/9. The "interactive five card draw" part has is covered by: https://github.com/MatthewPeterKelly/poker-stats/issues/8.


Document the use of the package

There is currently little to no documentation on how to use the package. It would be great to have at least a short explanation of how it works and how to use it. A small, simple test scene would also be great so the users have a working example to rely on.

I actually made a small sample scene. It can be found here:
https://github.com/QuentinDaveau/ConnectToMySql_sample_scene


[Enhancement] ADDDATE(TIME'00:00:00', INTERVAL 1 HOUR) does not work

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
SELECT ADDDATE(DATE'2021-01-01', INTERVAL 1 HOUR);
2021-01-01 01:00:00
SELECT ADDDATE(TIMESTAMP'2021-01-01 00:00:00', INTERVAL 1 DAY);
2021-01-01 01:00:00
SELECT ADDDATE(TIME'00:00:00', INTERVAL 1 HOUR);
SQL 错误 [1105] [HY000]: errCode = 2, detailMessage = Syntax error in line 1:
...ql> */ SELECT ADDDATE(TIME'00:00:00', INTERVAL 1 HOUR)
^
Encountered: STRING LITERAL
Expected: ||, COMMA, .
Solution
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I want to try it

hello, I want to try it


Fix readthedocs issues

This PR contains a bunch of small changes that fix problems with getting documentation to compile correctly on Read the Docs:

Updated conf.py (by regenerating with sphinx-autostart and copying over information.
Fixed a bunch of warnings in docstrings, usually related to escaping asterisks (*)
Changed a few other things for consistency (quote marks, indentation, blank lines, etc)
Changed "0 dB" to "1" in margins.py, to avoid EE-centric terminology
Updated the readthedocs requirements list
Got rid of the use of mock (didn't seem to need it once numpy, scipy, matplotlib were imported in doc-requirements)
Updated chapter, section headings in .rst files to be more consistent

Coverage remained the same at 78.962% when pulling d8e5684e75a2edd89470b01e447322a5a85b76f4 on murrayrm:fix_readthedocs into 26661f6758c7343606bb0acce6f51f037ccd7825 on python-control:master.

Coverage remained the same at 78.962% when pulling d8e5684e75a2edd89470b01e447322a5a85b76f4 on murrayrm:fix_readthedocs into 26661f6758c7343606bb0acce6f51f037ccd7825 on python-control:master.


Add a "continue generating..." option when the response is partially generated

I would really like a feature to continue the response generation when the response gets cut off due to the length of it. ChatGPT has this feature iirc. It'd be really great since when I'm dealing with files of codes which are about thousands of lines.

guys, is there any way you can expand the ability of copilot to comprehend the workspace a user is currently working on? when the workspace gets too big, it's hard for copilot to get accurate reading on the codebase.  when the file has the about more than 1000 lines, copilot cannot read it properly. Is that a problem of client's PC or Copilot's backend?


Add Attachment Support

Add the ability to add an attachment to a record.

Support for this was added via this Pull Request.


Error: Css styling failed: ReferenceError: Can't find variable: __spreadArrays

When I run tns run ios or tns run android I get the following error in Terminal on my MacBook Pro:
CONSOLE ERROR file:///node_modules/tns-core-modules/trace/trace.js:174:0: Error: Css styling failed: ReferenceError: Can't find variable: __spreadArrays
tns doctor:
No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 10.3.0 satisfies minimum required version 10.
✔ Getting NativeScript components versions information...
✔ Component nativescript has 6.1.0 version and is up to date.
✔ Component tns-core-modules has 6.1.1 version and is up to date.
✔ Component tns-android has 6.1.0 version and is up to date.
✔ Component tns-ios has 6.1.0 version and is up to date.
Package:
  "nativescript": {
    "id": "com.myapp.MyApp",
    "tns-ios": {
      "version": "6.1.0"
    },
    "tns-android": {
      "version": "6.1.0"
    }
  },
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "repository": "<fill-your-repository-here>",
  "scripts": {
    "lint": "tslint \"app/**/*.ts\""
  },
  "dependencies": {
    "@angular/animations": "~8.2.6",
    "@angular/common": "~8.2.6",
    "@angular/compiler": "~8.2.6",
    "@angular/core": "~8.2.6",
    "@angular/forms": "~8.2.6",
    "@angular/http": "~7.2.15",
    "@angular/platform-browser": "~8.2.6",
    "@angular/platform-browser-dynamic": "~8.2.6",
    "@angular/router": "~8.2.6",
    "@types/node": "^12.7.5",
    "html-encoder-decoder": "^1.3.8",
    "jwt-decode": "^2.2.0",
    "nativescript-advanced-webview": "^4.0.1",
    "nativescript-angular": "^8.2.1",
    "nativescript-appversion": "^1.4.2",
    "nativescript-email": "^1.5.5",
    "nativescript-https": "^1.1.0",
    "nativescript-iqkeyboardmanager": "^1.5.1",
    "nativescript-ngx-fonticon": "^4.2.1",
    "nativescript-plugin-firebase": "^9.1.1",
    "@nstudio/nativescript-pulltorefresh": "^1.0.1",
    "nativescript-root-detection": "^1.0.0",
    "nativescript-secure-storage": "^2.5.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-ui-gauge": "^5.0.0",
    "reflect-metadata": "~0.1.13",
    "rxjs": "^6.5.3",
    "rxjs-compat": "^6.5.3",
    "snyk": "^1.227.0",
    "tns-core-modules": "6.1.1",
    "webpack": "^4.40.2",
    "zone.js": "^0.10.2"
  },
  "devDependencies": {
    "@angular/compiler-cli": "8.2.0",
    "@ngtools/webpack": "8.2.0",
    "codelyzer": "~5.1.0",
    "nativescript-dev-webpack": "^1.2.0",
    "node-sass": "4.12.0",
    "tns-platform-declarations": "^6.1.1",
    "tslint": "~5.20.0",
    "typescript": "~3.5.3",
    "webpack-obfuscator": "^0.18.3"
  },
  "readme": "NativeScript Application"
}

Describe the bug
Both iOS and Android emulators fire up with either an unstyled app (iOS) or a blank screen (Android) after upgrading to NS6.
To Reproduce
Just run tns run ios or tns run android
Expected behavior
Should boot up the app login screen
Sample project
This is a private app.

Thanks to @tsonevn, I managed to resolve this issue by doing the following:

Delete the follow files/folders:

node_modules
platforms
hooks
package-lock.json
webpack.config.js

Run: npm i

Then just rebuild the project: tns run <platform_name>

This should resolve the issue.

Was able to resolve it with @marklanhamhc's workaround from here: https://github.com/NativeScript/nativescript-dev-webpack/issues/1037#issue-489216505

This didn't resolve the issue for me.  I'm stilling getting the error after deleting the folders/files and running tns run ios.  I'm running tns-ios: 6.1.1 in my package json.


Floating point data columns are sometimes displayed as ternary values

In some circumstances, floating-point number columns are displayed as ternary columns:
from fin.api.yf import Client
from fin.seq import fc

ticker = "^FCHI"
duration = dict(days=5)

client = Client()
data = client.historical_data(ticker, duration)

# Yahoo! Finance has dirty data. Do some clean-up
data = data.where(
        (fc.all, "Open", "High", "Low", "Close", "Adj Close"),
    )

print(data)

Displays:
      Date | Open     | High     | Low      | Close    | Adj Clo… |   Volume
---------- | -------- | -------- | -------- | -------- | -------- | --------
2024-05-03 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 69643700
2024-05-06 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 43781100
2024-05-07 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 58688300
2024-05-08 | 1.000000 | 1.000000 | 1.000000 | 1.000000 | 1.000000 |        0

It is probably caused when the same column has cached several representations. We do not have a mechanism to select the "most appropriate" representation.

Two possible solutions:

The exact representation is based on the column's type,
We remember what was the native type at the column's creation time,

Actually, the implementation uses the "richest" representation first by default (Python objects > float > ternary), so it is not a conversion issue. The problem was with Column.c_remap, which didn't copy all the cached data types.


Update the view option 'Active and deleted blobs' to 'Active and soft deleted blobs' for one ADLS Gen2 blob container

Storage Explorer Version: 1.21.0-dev
Build Number: 20210710.1
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS Big Sur 11.4
Architecture: ia32/x64
How Found: Exploratory testing
Regression From: Not a regression
Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Select one blob container -> Open it.
Click the view dropdown icon -> Observe the view options.
Check whether there is an option 'Active and soft deleted blobs'.

Expected Experience
There is an option 'Active and soft deleted blobs'.

Actual Experience
There is an option 'Active and deleted blobs'.

Verified on the build main/20210719.1. Reproduces.

Verified on the build main 20210720.1. Fixed.


Sign Transaction (memory key)

We need to implement the signTransaction method for the Key Management interface for in-memory keys

#10


v1.2 revise

Codecov Report

Merging #36 (50721dc) into release-1.2.0 (d594829) will decrease coverage by 0.87%.
The diff coverage is 87.86%.

@@                Coverage Diff                @@
##           release-1.2.0      #36      +/-   ##
=================================================
- Coverage          90.83%   89.96%   -0.88%
=================================================
  Files                 35       34       -1
  Lines               1954     1913      -41
=================================================
- Hits                1775     1721      -54
- Misses               179      192      +13

Impacted Files
Coverage Δ

crypto/zkp/utils/src/lib.rs
76.31% <ø> (ø)

third_party/fisco_bcos_java_sdk/src/lib.rs
88.11% <ø> (ø)

...rypto/oblivious_transfer/base_ot/src/ot_message.rs
81.44% <81.44%> (ø)

crypto/oblivious_transfer/base_ot/src/ot_kv.rs
93.57% <93.57%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d594829...50721dc. Read the comment docs.


Automatic PR from RestAPI-PR1225

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1225

Codecov Report

Merging #1176 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1176   +/-   ##
=======================================
  Coverage   55.18%   55.18%
=======================================
  Files        2191     2191
  Lines       60958    60958
=======================================
  Hits        33637    33637
  Misses      27321    27321

Impacted Files
Coverage Δ

...analytics/catalog/operations/catalog_operations.py
52.39% <ø> (ø)
:arrow_up:

...g/data_lake_analytics_catalog_management_client.py
93.1% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 687d0cb...842d638. Read the comment docs.

Doc only


workflow: enable pod-to-world tests

This commit enables pod-to-world tests that were disabled due to flaky results. With the configurable --external-target flag we are configuring different targets per cloud provider. Targets were chosen to be the least hops from the clusters. They were determined by experimenting with connection times from cloud providers. Splitting targets also has the advantage of not overloading a single target.
Signed-off-by: Birol Bilgin<EMAIL_ADDRESS>

Test result samples per cloud provider are below,
https://github.com/cilium/cilium/actions/runs/4005780524/jobs/6876559560
https://github.com/cilium/cilium/actions/runs/4005780528/jobs/6876556152
https://github.com/cilium/cilium/actions/runs/4005780517/jobs/6876550760
https://github.com/cilium/cilium/actions/runs/4005780538/jobs/6876558497
https://github.com/cilium/cilium/actions/runs/4005780504/jobs/6876550560
https://github.com/cilium/cilium/actions/runs/4005780566/jobs/6876559970
https://github.com/cilium/cilium/actions/runs/4005780547/jobs/6876552863


[Feature request] Recursive fuzzing

It would be awesome to have a recursive option, with --recursive for example, with an option to specify the depth.
Every time we have a 200 response on a folder, ffuf would automatically scan the subfolders after the initial scan.

I have been thinking of this, or rather the way to:

Signal the user that we just extended the search space, instead of just bumping the total try count up
Handle it internally in a sane way within ffuf codebase.

Additional note: this feature only fits one of the multiple use cases for ffuf, and I would like to keep it all consistent. (as the tool can be used to fuzz HTTP headers, payload etc.)


"Hosted by"-string printed as b'Hosted by...'

So I was speedtesting my connection when I noticed something weird
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Ziggo (ip here)...
Selecting best server based on latency...
b'Hosted by SoftLayer Technologies, Inc. (Amsterdam) [32.92 km]: 15.53 ms'
Testing download speed........................................
Download: 68.76 Mbit/s
Testing upload speed..................................................
Upload: 12.13 Mbit/s

The "Hosted by"-string is printed as b'Hosted by...'.
 b'Hosted by SoftLayer Technologies, Inc. (Amsterdam) [32.92 km]: 15.53 ms'

This has to do with the UTF-8 encoding as shown in this snippet:
 >>> print(("test".encode('UTF-8')))
 b'test'

I'm seeing this consistently too (Python 3.4.3 in Alpine Linux).
@maride any reason you didn't make 81fa7c5 into a PR? :smile:  (does it not appropriately fix the issue?)
I also see the issue when I do --list:
$ speedtest-cli --list
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
b'6412) T-Mobile (North Las Vegas, NV, United States) [7.52 km]\n1431) Switch (Las Vegas, NV, United States) [12.67 km]\n....'

A little less esoteric place I can reproduce easily is Python 3.5.1 from Debian Unstable (installing python3-pip and then doing pip3 install speedtest-cli).

Sorry if this is already obvious (I'll admit openly that my Python-fu is subpar), but it appears that this is caused by the fact that in Python 2, str.encode returns a "string" (https://docs.python.org/2/howto/unicode.html - "which returns an 8-bit string version of the Unicode string") vs Python3 str.encode which returns a "bytes object" (https://docs.python.org/3/library/stdtypes.html#str.encode - "Return an encoded version of the string as a bytes object")

Found more info on the topic: https://docs.python.org/3/howto/pyporting.html#text-versus-binary-data
I will try to make a patch for it.

I just wonder @sivel, why is it even encoded like that?

It will be fixed in a future version. It is already solved in another branch that I have.

Allright, thanks!


Typo

[skip ci]

It looks like your package will be number 8000, just in time for JuliaCon, so I took a look at it (and wanted to fix he typo), I already linked to it here:
https://discourse.julialang.org/t/over-7000-registered-packages-congratulation-julia-community/36702/22

@PallHaraldsson This package is actually a rename, so I'm not the 8000th either!


Filter Field Symbols from Visible Symbols in the Context of Fields

Purpose

Filter the field symbols in the visible symbols API when the cursor is in the context of fields.

Fixes #29382
Fixes #33089
Approach

Class Field Symbols
Object Field Symbols
Record Field Symbols
are filtered in the Semantic API.

Samples

Remarks

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[x] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

The issue @nadeeshaan mentioned is still there isn't it?

@sanjana can you please resolve the conflicts?

@sanjana can you please resolve the conflicts?

@mohanvive, resolved the merge conflicts and fixed a few other failing LS test cases as well.


Update validation rules for service config

Update validation rules for service config as per https://github.com/grpc/proposal/pull/100

Thanks for reviewing!


Updated validations.py python script

Updated validations.py pyhton script.
Fixed the behaviour of validate_user function in validations.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it


The chart in the report screenshot is sent before the animation is finished.

The chart in the report screenshot is sent before the animation is finished.
Expected results
Take a screenshot of the chart with the chart animation finished and send the report.
Actual results
Before the chart animation is finished, a screenshot is taken and a report is sent.
Screenshots
Image sent as a report

How to reproduce the bug
Environment

superset version: Superset 1.2.0 + https://github.com/apache/superset/blob/f52b6715cf2d9da8455a7a62d0c1d9cab64bf5aa/superset/utils/webdriver.py
python version: Python 3.7.9
node.js version:

Checklist

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.

There was no stack trace.

[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Pull request submitted. https://github.com/apache/superset/pull/15610

@u-aiaa can you clarify what "animation" means in a video or gif? thanks!

@junlincc
This is a video of the chart when viewed in a browser.

When submitting a report, I wondered if a screenshot would be taken before this animation was finished. Therefore, I added a wait time to the pull request.
Instead of a wait time, should it not animate when sending a report?

makes sense! thanks!

#15610 merged.


Update tapir-core, tapir-json-circe, ... to 0.17.4

Updates

com.softwaremill.sttp.tapir:tapir-core
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-openapi-circe-yaml
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-swagger-ui-http4s
com.softwaremill.sttp.tapir:tapir-zio
com.softwaremill.sttp.tapir:tapir-zio-http4s-server

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

labels: library-update, semver-minor

Superseded by #166.

Superseded by #166.


refactor admin section builder

the menu item does not remain open and selected/highlighted when clicked..
for example of right behaviout: have a look at this product sub menu

 Just like reports and users, we are dealing with only one link, I dont see value on having sub menu here..
Just a menu titled 'Product Questions' should be enough

in case you are linking to pending questions only, we can title 'Pending Questions'


read QC

Hi,
Thanks for the brilliant tool.
I just wanted to enquire a few things:

Does TRUST4 handle alignments well without adaptor trimming? It is unclear from the manuscript and vignettes on whether this improves performance or whether keeping the reads untrimmed results in better coverage, as has been suggested in some manuscripts.
Does TRUST4 have any internal quality controls on base quality during alignments?

Many thanks in advance

TRUST4 internally handles the read-through issue by checking the overlap of mate pairs. So there is no need for adaptor trimming.
For the base quality, TRUST4 trims the read end with bad quality bases near the end. Internally, the bad quality means the quality symbol is less or equal to "/" and the corresponding kmer counts are 1.

Brilliant, thanks for clarifying so quickly!


Unable to use list of LoRA embed statements in Wildcards txt file

My prompt contains LoRAs (surrounded by two underscores on either side) and the file LoRAs.txt contains
<lora:list of LoRA embeds:1>
<lora:another LoRA embeds:1>
<lora:another LoRA embeds:1>
Dynamic prompts are enabled but the prompt doesn't substitute. File permissions are good.

I'm not getting any substitutions for the wildcard text files, so I'm going to check on that night. I'd hold on this issue can't verify that it's a real issue.

I'm experiencing this with all my wildcards so I don't think it's a programming issue.

LoRAs can only be different per separate batch. Increase number of batches, not batch size.


Unable to start session for kernel Python 3.8.5 32-bit

Bug: Notebook Editor, Interactive Window, Editor cells
Unable to start session for kernel Python 3.8.5 32-bit ('venv': venv). Select another kernel to launch with.

Steps to cause the bug to occur
There is really nothing special here

Clone repo and start VSCode
Run python -m venv venv
Switch interpreter to venv and restart terminal
Create main.ipynb
Install data-science package when automatically prompted
Unable to start-session.

Actual behavior
Unable to start session for kernel Python 3.8.5 32-bit ('venv': venv). Select another kernel to launch with.
Expected behavior
Notebook runs!

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: Local
Extension version: v2020.8.105369
VS Code version: 1.48.2
Setting python.jediEnabled: I don't have this in my settings JSON file so default settings?
Setting python.languageServer: Microsoft
Python and/or Anaconda version: 3.8.5 32-bit
OS: Windows 10 Home 64-bit
Virtual environment: venv  ...

Python Output

The notebook can't run so there is nothing to copy here. However, here is the installed package in the environment if it helps at all:
Package            Version

argon2-cffi        20.1.0
attrs              20.1.0
backcall           0.2.0
bleach             3.1.5
cffi               1.14.2
colorama           0.4.3
decorator          4.4.2
defusedxml         0.6.0
entrypoints        0.3
flake8             3.8.3
ipykernel          5.3.4
ipython            7.18.1
ipython-genutils   0.2.0
ipywidgets         7.5.1
jedi               0.17.2
Jinja2             2.11.2
jsonschema         3.2.0
jupyter            1.0.0
jupyter-client     6.1.7
jupyter-console    6.2.0
jupyter-core       4.6.3
MarkupSafe         1.1.1
mccabe             0.6.1
mistune            0.8.4
nbconvert          5.6.1
nbformat           5.0.7
notebook           6.1.3
packaging          20.4
pandocfilters      1.4.2
parso              0.7.1
pickleshare        0.7.5
pip                20.1.1
prometheus-client  0.8.0
prompt-toolkit     3.0.7
pycodestyle        2.6.0
pycparser          2.20
pyflakes           2.2.0
Pygments           2.6.1
pyparsing          2.4.7
pyrsistent         0.16.0
python-dateutil    2.8.1
pywin32            228
pywinpty           0.5.7
pyzmq              19.0.2
qtconsole          4.7.6
QtPy               1.9.0
Send2Trash         1.5.0
setuptools         47.1.0
six                1.15.0
terminado          0.8.3
testpath           0.4.4
tornado            6.0.4
traitlets          5.0.0
wcwidth            0.2.5
webencodings       0.5.1
widgetsnbextension 3.5.1
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

Hello, I'm having a similar issue. It happens with any kernel I try to choose. Attaching a dev console log
-1598962107726.log

Hello,
almost the same issue:
Unable to start session for kernel Python 3.8.5 32-bit. Select another kernel to launch with.
Version: 1.48.2 (user setup)
Commit: a0479759d6e9ea56afa657e454193f72aef85bd0
Date: 2020-08-25T10:13:11.295Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 6.3.9600

Same issue with Python 3.8.5 64-bit
output.txt

There is a workaround, you can use dependencies from an older workspace, if you have any. For example this set of requirements works in my case, but the updated ones not any more. I don't know which version exactly causes the problem.

requirements.txt
absl-py==0.9.0
alembic==1.4.2
apispec==3.3.1
appdirs==1.4.4
astunparse==1.6.3
attrs==19.3.0
azure-core==1.6.0
azure-storage-blob==12.3.2
Babel==2.8.0
backcall==0.2.0
black==19.10b0
bleach==3.1.5
blinker==1.4
Boruta==0.3
cachetools==4.1.0
certifi==2020.6.20
cffi==1.14.0
chardet==3.0.4
click==7.1.2
cloudpickle==1.4.1
convertdate==2.2.1
country-currencies==0.2
coverage==5.1
cryptography==2.9.2
cycler==0.10.0
databricks-cli==0.11.0
decorator==4.4.2
defusedxml==0.6.0
Deprecated==1.2.10
distlib==0.3.0
docker==4.2.1
eli5==0.10.1
entrypoints==0.3
et-xmlfile==1.0.1
fastavro==0.24.0
fastparquet==0.4.0
filelock==3.0.12
future==0.18.2
gast==0.3.3
gitdb==4.0.5
google-auth==1.18.0
google-auth-oauthlib==0.4.1
google-pasta==0.2.0
gorilla==0.3.0
graphviz==0.14
grpcio==1.30.0
gunicorn==20.0.4
h5py==2.10.0
holidays==0.10.3
hyperopt==0.2.4
idna==2.9
importlib-metadata==1.6.1
ipdb==0.13.3
ipykernel==5.3.0
ipython==7.15.0
ipython-genutils==0.2.0
ipywidgets==7.5.1
isodate==0.6.0
itsdangerous==1.1.0
jdcal==1.4.1
jedi==0.17.1
jellyfish==0.8.2
Jinja2==2.11.2
joblib==0.16.0
jsonpointer==2.0
jsonschema==3.2.0
jupyter==1.0.0
jupyter-client==6.1.3
jupyter-console==6.1.0
jupyter-core==4.6.3
kafka-python==2.0.1
Keras-Preprocessing==1.1.2
kiwisolver==1.2.0
korean-lunar-calendar==0.2.1
llvmlite==0.33.0
Mako==1.1.3
Markdown==3.2.2
MarkupSafe==1.1.1
marshmallow==3.7.1
marshmallow-jsonschema==0.10.0
matplotlib==3.2.2
mistune==0.8.4
more-itertools==8.4.0
msgpack==1.0.0
msrest==0.6.16
nbconvert==5.6.1
nbformat==5.0.7
networkx==2.4
notebook==6.0.3
numba==0.50.0
numpy==1.19.1
oauthlib==3.1.0
openpyxl==3.0.1
opt-einsum==3.2.1
packaging==20.4
pandas==1.1.0
pandocfilters==1.4.2
parso==0.7.0
pathspec==0.8.0
pexpect==4.8.0
phonenumbers==8.12.7
pickleshare==0.7.5
Pillow==7.2.0
plotly==4.8.1
pluggy==0.13.1
prometheus-client==0.8.0
prometheus-flask-exporter==0.14.1
prompt-toolkit==3.0.5
protobuf==3.12.2
psutil==5.7.2
psycopg2-binary==2.8.5
ptvsd==4.3.2
ptyprocess==0.6.0
py==1.8.2
pyarrow==1.0.0
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.20
Pygments==2.6.1
PyMeeus==0.3.7
pyparsing==2.4.7
pyrsistent==0.16.0
pytest==5.4.3
pytest-cov==2.10.0
python-dateutil==2.8.1
python-editor==1.0.4
pytz==2020.1
PyYAML==5.3.1
pyzmq==19.0.1
qtconsole==4.7.5
QtPy==1.9.0
querystring-parser==1.2.4
regex==2020.6.8
requests==2.24.0
requests-oauthlib==1.3.0
responses==0.10.15
retrying==1.3.3
rfc3339-validator==0.1.2
rfc3986-validator==0.1.1
rsa==4.6
scikit-learn==0.23.1
scipy==1.4.1
seaborn==0.10.1
Send2Trash==1.5.0
sentry-sdk==0.16.3
shap==0.35.0
six==1.15.0
smmap==3.0.4
tabulate==0.8.7
termcolor==1.1.0
terminado==0.8.3
testpath==0.4.4
threadpoolctl==2.1.0
thrift==0.13.0
toml==0.10.1
tornado==6.0.4
traitlets==4.3.3
typed-ast==1.4.1
typing-extensions==<IP_ADDRESS>
urllib3==1.25.9
uWSGI==<IP_ADDRESS>
virtualenv==20.0.25
wcwidth==0.2.5
webargs==5.5.3
webcolors==1.11.1
webencodings==0.5.1
websocket-client==0.57.0
widgetsnbextension==3.5.1
wrapt==1.12.1
zipp==3.1.0

There is a workaround, you can use dependencies from an older workspace, if you have any. For example this set of requirements works in my case, but the updated ones not any more. I don't know which version exactly causes the problem.

Actually just pip install notebook==6.0.3 works for me

@Krendelev Unfortunately this workaround isn't working for me.

Just want to echo I have the same issue starting this morning and it seems like #13715 and #13714 both may be referring to the same problem.

Strangely, this bug is also present when using devcontainers.
It doesn't seem to be linked to the version of Python.

Looking into it now. The logs that I've seen all have signature mismatch issues.

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

If this works (or doesn't) for you please post back as I have only my data point to work with.

https://github.com/ipython/traitlets/issues/608

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Confirming that this resolves the issue. Thank you for looking into it.

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history

In an activated environment that is not working try the following to drop it back to the older version:
python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Confirmed on my end (Python3.8.5 64-bit; Windows).

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

This really helped!

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Thank you very much

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

I just started today with VScode+jupyter (was already in with anaconda).
This issue really tired me up and took my 4-5 hours to get to this post.
FIrstly there was some compatibility issue with conda env kernel and then this stuff came up.
but this solution saved my day. Thanks a lot

Thank you very much!
It is working now.
Quotation marks are not necessary:
python3 -m pip install traitlets==4.3.3 --force-reinstall
or
pip3 install traitlets==4.3.3 --force-reinstall
On Tue, Sep 1, 2020 at 11:56 AM liteform<EMAIL_ADDRESS>wrote:

Hey folks. In my local testing I believe that it was this update here to
5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop
it back to the older version:
python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in
the background, this will make sure that you pick up the install fresh the
next time that you start).
Confirming that this resolves the issue. Thank you for looking into it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/13701#issuecomment-684998235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM2HQQAJZTBZHEHLI243SLSDURSLANCNFSM4QQ4BE3Q
.

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

perfect for me! thanks!

I feel like I'm missing something? When I run python -m pip install 'traitlets==4.3.3' --force-reinstall and then open up VS Code and start up a new notebook, it tells me Data Science library ipykernel is not installed. Install? And if I select "Yes" it will update and then send me back to the Unable to start session for kernel Python 3.8.5 32-bit. Basically putting me in a loop.

python -m pip install 'traitlets==4.3.3' --force-reinstall confirmed to work for me. Thanks a lot.
Python 3.8.5 32-bit on Windows 10 64-bit

python3 -m pip install traitlets==4.3.3 --force-reinstall worked for me as well. Python 3.8.2 64-bit on Windows 10 64-bit

I feel like I'm missing something? When I run python -m pip install 'traitlets==4.3.3' --force-reinstall and then open up VS Code and start up a new notebook, it tells me Data Science library ipykernel is not installed. Install? And if I select "Yes" it will update and then send me back to the Unable to start session for kernel Python 3.8.5 32-bit. Basically putting me in a loop.

Go to vscode (change the python interpreter to what you want), then run
python -m pip install ipykernel
and then do the degradation by
python -m pip install 'traitlets==4.3.3' --force-reinstall
because when you are degrading it first then the installation of ipykernel updates it again nullfying your degradation

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history

In an activated environment that is not working try the following to drop it back to the older version:
python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Confirmed on my end (Python3.8.5 64-bit; Windows).

"python -m pip install traitlets==4.3.3 --force-reinstall --user"
It works perfectly now! Thanks very much!!!!!

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

also works for me, thank you!

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

It worked, thanks!

Thank you very much! It is working now. Quotation marks are not necessary: python3 -m pip install traitlets==4.3.3 --force-reinstall or pip3 install traitlets==4.3.3 --force-reinstall
…
On Tue, Sep 1, 2020 at 11:56 AM liteform @.***> wrote: Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install: https://pypi.org/project/traitlets/#history In an activated environment that is not working try the following to drop it back to the older version: python -m pip install 'traitlets==4.3.3' --force-reinstall Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start). Confirming that this resolves the issue. Thank you for looking into it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13701 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACM2HQQAJZTBZHEHLI243SLSDURSLANCNFSM4QQ4BE3Q .

Really worked!

I feel like I'm missing something? When I run python -m pip install 'traitlets==4.3.3' --force-reinstall and then open up VS Code and start up a new notebook, it tells me Data Science library ipykernel is not installed. Install? And if I select "Yes" it will update and then send me back to the Unable to start session for kernel Python 3.8.5 32-bit. Basically putting me in a loop.

Go to vscode (change the python interpreter to what you want), then run
python -m pip install ipykernel
and then do the degradation by
python -m pip install 'traitlets==4.3.3' --force-reinstall
because when you are degrading it first then the installation of ipykernel updates it again nullfying your degradation

Well, like I said, I seem to be stuck in a loop. if I install ipykernel, then I can't start a session. So then I need to do the degradation. But the problem here is that if I degrade it, vscode keeps telling me that I don't have an ipykernel installed. Therefore, it still doesn't work.
Here's the other thing, after running python -m pip install 'traitlets==4.3.3' --force-reinstall, if I were to install ipykernel with pip, nothing happens as all my requirement are satisfied. Its just that if I try to select an interpreter for notebooks, again, vscode will force me to install Data Science library ipykernel and it will add Installing collected packages: ipython-genutils, traitlets, six, decorator. This seems to be the only difference between installing through VS Code and using  python -m pip install ipykernel.
I should also add that this is my first time installing and running notebooks on vscode, so I don't have any older versions to revert back to maybe? I'm honestly not sure what's going on.

@dwang040 Sounds like you are dealing with a different issue here. Could you please file a new issue on this? Also turning Python->Logging->Level setting to 'debug' and then including the contents of the Output:Python window could help us to diagnose this.

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Also works very well for me, thanks
If someone here is using pipenv to manage your packages, use the command below to install this package
pipenv install  jupyter
pipenv install  traitlets==4.3.3
With both commands you can create the complete environment to work with jupyter notebook on vscode.

OMG!!!! You guys have just saved my life!!!!
I've been trying to solve this problem for HOURS!!!!
I'm using Ubuntu 20.04. I've installed jupyter using "sudo pip3 install jupyter" in the terminal and jupyter notebook was working completely fine in the browser. However, when I tried to create a notebook in VSCode I got the message "Connecting to IPython kernel: Connecting to kernel", and, after some minutes, the message "Unable to start session for kernel python 3.8".
As suggested here, first I exited VSCode.
Then I checked the version of "traitlets" installed, using the following command in ubuntu terminal:
$ pip3 freeze | grep traitlets
And it was installed some 5 version...
Then, I used the following command in ubuntu terminal:
$ sudo pip3 install "traitlets==4.3.3" --force-reinstall
Reopened VSCode and ran a notebook! Worked PERFECTLY!!!!
Thank you very much you all, specially @IanMatthewHuff  !!!!

Worked for me too - python 3.8.5 on 64-bit windows10 (asked on stackoverflow yesterday)

If this works (or doesn't) for you please post back as I have only my data point to work with.

Thanks a lot! this solved my problem:
Unable to start session for kernel Python 3.7.7 64-bit ('venv': venv). Select another kernel to launch with.

Thank you very much! It is working now. Quotation marks are not necessary: python3 -m pip install traitlets==4.3.3 --force-reinstall or pip3 install traitlets==4.3.3 --force-reinstall
…
On Tue, Sep 1, 2020 at 11:56 AM liteform @.***> wrote: Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install: https://pypi.org/project/traitlets/#history In an activated environment that is not working try the following to drop it back to the older version: python -m pip install 'traitlets==4.3.3' --force-reinstall Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start). Confirming that this resolves the issue. Thank you for looking into it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13701 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACM2HQQAJZTBZHEHLI243SLSDURSLANCNFSM4QQ4BE3Q .

This worked - 3.8.3 64bit MacOS, thank you! :)

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Works for me 👍

This worked for me, following the instructions for Pipenv mentioned by @pedrom505
Thank you!!

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Worked for me, thank you! But is there anyone working on a more permanent fix that works with the latest version of traitlets and other things?

Hi,
I tried the solutions above, but they did not work for me. I also tried the solutions here, but they did not work either. I'm very new to visual studio so all help is appreciated. Thank you!

Worked easily and well for me. Many thanks @IanMatthewHuff and team!

python -m pip install 'traitlets==4.3.3' --force-reinstall
Yes it worked for me as well :-)

This should be fixed with latest traitlets 5.0.4, out earlier today. I haven't been able to confirm directly, since I don't know how to trigger the relevant code path myself, but manually executing a similar command-line is fixed with 5.0.4.

But is there anyone working on a more permanent fix that works with the latest version of traitlets and other things?

This extension shouldn't need any updating, but the relevant change is that this b' prefix for configuring Bytes on the command-line is no longer required and support is deprecated (with no plans for removal). The bug was in traitlets 5,<5.0.4 not properly implementing the deprecated support for this prefix. It can be dropped if/when traitlets >=5.0 is required, but until then no changes are necessary. I wouldn't rush, though, as pinning down is likely to be a common practice as bugs are worked out during a transition period.

This should be fixed with latest traitlets 5.0.4, out earlier today. I haven't been able to confirm directly, since I don't know how to trigger the relevant code path myself, but manually executing a similar command-line is fixed with 5.0.4.

But is there anyone working on a more permanent fix that works with the latest version of traitlets and other things?

This extension shouldn't need any updating, but the relevant change is that this b' prefix for configuring Bytes on the command-line is no longer required and support is deprecated (with no plans for removal). The bug was in traitlets 5,<5.0.4 not properly implementing the deprecated support for this prefix. It can be dropped if/when traitlets >=5.0 is required, but until then no changes are necessary. I wouldn't rush, though, as pinning down is likely to be a common practice as bugs are worked out during a transition period.

-This worked for me

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

This worked for me - Thank you!
Python 3.8.5
MacOS 10.15.6

I had traitlets 4.3.3 installed already, so I tried upgrading.  In the respective conda env, I upgraded traitlets to 5.0.4 and still get the kernelspec error unless I open vscode via the anaconda3 command prompt.
Interestingly this issue is not present when I run an interpreter on the host from a remote client via the SSH remote extension
python 3.7.7
vs code 1.49
win10 x64

Worked for me. Thanks!
Python 3.8.5
vscode 1.49
win10 x64

Hope to solve this problem, I spent a long time to solve this problem, but those who did not see this page are not so lucky, maybe they will give up using VSCODE's jupyter notebook function

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

WORKED! Thank You :))

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

This is great! Fixed the issue.
Cheers!

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

traitlets==4.3.3 worked for me also thank you!

This should be fixed with latest traitlets 5.0.4, out earlier today.

I can confirm that upgrade to 5.0.4 fixed it for me:
pip3 install -U traitlets

Not work for me.
Python 3.7.4
Windows 10
vscode 1.49.2

The same problem, nothing works for me.
I´ve tried upgrading traitlets to 5.04, I´ve tried traitlets 4.3.3.
I´m working with Anaconda, I created a new enviroment, where I install  Ipykernel
conda install ipykernel
ipython kernel install --name my_env --user
Python 3.8.3
Windows 10
vscode 1.49.2

@Brelliothe  and @rocooper7 . There are different issues that can manifest as the same session start issues. At this point we have a number of confirmations that the traitlets issue is fixed. Can you please open up new issues for your reports? And please set the setting Python->Logging->Level to 'debug' then copy out the contents of the python output window into a file. You can then post that file attached to your issue and it will greatly help with debugging.

python -m pip install 'traitlets==4.3.3' --force-reinstall
got an error message.
try:
pip uninstall traitlets
pip install traitlets
works for me. thanks.

python -m pip install 'traitlets==4.3.3' --force-reinstall
got an error message.
try:
pip uninstall traitlets
pip install traitlets
works for me. thanks.

This worked for me as well!

Hey folks. In my local testing I believe that it was this update here to 5.0.0, which is picked up as part of our ipykernel install:
https://pypi.org/project/traitlets/#history
In an activated environment that is not working try the following to drop it back to the older version:
 python -m pip install 'traitlets==4.3.3' --force-reinstall
Make sure to have VS Code closed (as we sometimes are starting a kernel in the background, this will make sure that you pick up the install fresh the next time that you start).

Thanks very much. It works perfect now

There is a workaround, you can use dependencies from an older workspace, if you have any. For example this set of requirements works in my case, but the updated ones not any more. I don't know which version exactly causes the problem.

Actually just pip install notebook==6.0.3 works for me
Edit: complete requirements.txt that works, few packages downgraded.
requirements.txt

Works for me

I found that Code (OSS) tries to open the system Python by default, at least in version 1.50.1. If you don't have ipykernel installed to the system Python, then it keeps trying to activate that environment, even if you try to select another.
For me, I installed python-ipykernel on Arch Linux and this fixed the issue. I can now use my Anaconda environment just fine.
yay -S python-ipykernel

It's a workaround for now, at least until the Python plugin stops doing this.

Doesn't work for me. Python 3.9.0 64-bit.
steps:

uninstall ipykernel
reinstall ipkernel
do downgrade
error; Timed out waiting to get a heartbeat from kernel process

Doesn't work for me. Python 3.9.0 64-bit.
steps:

uninstall ipykernel
reinstall ipkernel
do downgrade
error; Timed out waiting to get a heartbeat from kernel process

Hello,
have you tried this (#14274)