Removed dependency on boost if compiler do support it

Fix #122
As proposed in the issue.

Great, I'll look at this next week (sorry, busy till then)!

@eidheim, expected, there's a lot to review in here ;)

@eidheim up ?

@sebt3 sorry for this taking so long, my plan is to finish review the PR Tomorrow or the day after. I also realised I had to read up on CMake since there were some changes there I did not understand 100% right away.

Well FindAsio.cmake is the very standard way to find a library, and since it's a header only, I'm only looking for the header;
Many things from your original CMakeFile was moved to SimpleWebServer.cmake so it could be reused by anyone just by including it. All I did was to add support for c++1y (in a very standard way) which clang require to use experimental::filesystem. Now that everything reusable is in an includable file, the resulting CMakeFiles only contain instruction required to build the examples and tests.
Since you have a way to install your library, a FindSimpleWebServer.cmake (just like the FindAsio.cmake) might be a good idea. Yet I feel like most users of this project just copy the files they need in their sources, so the includable is better imho. You might want to provide both though ;)

My initial thoughts are as follows:

use for instance namespace regex_ns = std; instead of #define REGEX_NS std, somewhat like @314159 suggested.

I know libclang based IDE's such as juCi++ will be able to go to definition on regex_ns then, since macros can be problematic.
namespaces are typically lowercase

According to http://think-async.com/Asio/AsioStandalone there is already a macro ASIO_STANDALONE for using standalone Asio. We should check for this macro definition in the header files. By default though, we should use boost::asio due to backward compability, but later we will probably use c++20 asio by default instead and that would most likely require a major version bump of Simple-Web-Server.

The example cpp files should stay as they are, thus keeping them easy to read, and we do not have to worry about c++17 filesystem yet. I think people will understand that the examples require boost, but the header files might be used without boost, especially those considering using standalone asio

Keep the CMakeLists.txt files as they are. Keeping cmake/Modules/FindAsio.cmake would be nice though for people deciding to use standalone Asio, but the current CMakeLists.txt files are for building the examples that require boost asio. However, those that will use standalone Asio, would use their own CMakeLists.txt with the ASIO_STANDALONE macro set.

Providing cmake/Modules/SimpleWebServer.cmake would be nice, but I think most people will use this library as a git submodule or simply copying the header files. Still, we could add cmake installation exports, but I would like to do this in a separate PR since it require a bit more work. I had a similar PR for this here: https://github.com/eidheim/tiny-process-library/pull/25, but decided to not add cmake installation exports due to added complexity, and because I am not completely convinced that this is something that is needed for smaller libraries (with only header files and/or one library file).

This said, I'm of course open for discussion regarding the above comments! And thank you again for this PR:) If you decide to keep your PR as is, I can do the above changes in a separate commit, but let us discuss it first of course.

Replying dot per dot ;)

As you please. As replied to @314159, I only choose the other way because you did already. I'll change this next week (no coding time planned this week)
As per /usr/include/boost/asio/detail/config.hpp, there's also a BOOST_ASIO_STANDALONE that one may want to use to build using boost::asio, yet dont link with boost. So this point require some work to be done right. Beside, currently, I'm not setting this yet I'm still able to link without boost (since I'm only using the part not requiring boost). As I understand it, setting any of these 2 macros (depending if you include boost/asio or asio) only disable all the functions that takes boost typed arguments. Yet ASIO_HEADER_ONLY is the default behaviour...
well std::experimental::filesystem is part of c++11 as far as I get it, it's going to be std::filesystem in c++17. c++1y is "preliminary" support for c++2017, just like c++0x was "preliminary" support for c++ 2011. The issue is while gcc implemented it in it's c++11 support, clang choose to not to (it wasnt mandatory to support those thing, being "experimental"), but provide an implementation in c++1y since they will provide an implementation in c++17 (as per spec). Anyway, what you suggest is actually removing features in an example :(
That's actually the point of providing a SimpleWebServer.cmake instead of a FindSimpleWebServer.cmake. So the git submodule user can easily include the file and so if the MACRO requirement change keep being updated on that front too. My changes doesnt look to be in the same idea as the PR you linked. If you want me to bring this in a different PR, then, I'll want this PR 1st. I've only done within this PR, because my patch made it clear having no way to change the macro definitions on the users is a big problem : Anyone just updating the headers without changing his buildsystem to reflect the macro requirement will be at a surprise : non-boost is the default code wise, so my patch is not backward compatible as-is...

I really like this move to standalone asio. Good job @sebt3!

@sebt3 In hindsight I should have numbered the points. But regarding the two last points:

since boost::property_tree is used in the examples and thus boost is needed anyway, thus I do not see the need to add additional complexity here through additional ifdefs. When we move to c++17, on the other hand, we can also move to std::filesystem (skipping std::experimental::filesystem altogether). But this is some years into the future. I do not see that I suggest removing features in the examples here?
I think maybe we can keep FindSimpleWebServer.cmake, your argument of making it easier for people using this library as a git submodule is quite valid. However, for the time being, boost::asio should be the default option, so that we do not need to bump the major version just yet. There are a couple more things I plan to do before that would happen. That is why I suggest that the asio library should be used in the header files if ASIO_STANDALONE is set, and the boost::asio library otherwise. Not sure if we need to take into account BOOST_ASIO_STANDALONE too? Not yet maybe, as we should focus on standalone asio and boost::asio first and foremost.

Ok, I'll work on a new PR based on your ideas. I'll try to split my commit in a more readable way though.
This will need wait until next week at best.


Access validator wrapper fields in validator function

Hi,
I am trying to find a way to access the fields in the validator wrapper so I can avoid duplicating code. Here's the scenario:
I have a class based on BaseModel which contains bytes fields that represent percentage values from 0 to 100 ('soc' = state of charge). I wrote a validator function to check that the provided byte value is between 0 and 100.
@validator('current_soc', 'minimum_soc', 'target_soc', allow_reuse=True)
def soc_value_range(cls, value):
    if validate_bytes_value_range([the validator field name], value, 0, 100):
        return value

The validate_bytes_value_range function takes 4 parameters as input: the field name, the given value, the minimum allowed value and the maximum allowed value, as I'm resuing that validator function in several places.
Now instead of repeating the def soc_value_range(cls, value) function three times, each time with a different soc field (so I can put that field name as the first parameter for validate_bytes_value_range), I'd like to somehow access each field of @validator('current_soc', 'minimum_soc', 'target_soc', allow_reuse=True). It just seems more elegant to me.
Is there such a solution or do I really need to repeat the code for each field, given that I want the error message to reflect the field name for clarity's sake?

Hi @MarcMueltin
Quoting the doc
you can also add any subset of the following arguments to the signature (the names must match):

    values: a dict containing the name-to-value mapping of any previously-validated fields
    config: the model config
    field: the field being validated

So in your case you can use field.name (or field.alias if needed)
@validator('current_soc', 'minimum_soc', 'target_soc', allow_reuse=True)
def soc_value_range(cls, value, field):
    if validate_bytes_value_range(field.name, value, 0, 100):
        return value
    ...

Hope it helps!

Thank you so much @PrettyWood for the quick and crystal clear answer! Sorry, but I must have overlooked that part of the documentation somehow.


fix: separate inference output formatting for each detection model; [issues #330, #254]

Fix issues: #254 #330

@bhavikapanara look closer at the error again and see which method should have been caught by the test suite before, but it wasn't. That's the one you should write new tests for to ensure it does not fail from now on.
Hint: _save_sample
Make sure that the tests exercise the code and check whether it produces the desired outcome on disk.

Hello @bhavikapanara! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/ambianic/pipeline/ai/fall_detect.py:

Line 229:80: E501 line too long (84 > 79 characters)
Line 230:80: E501 line too long (97 > 79 characters)
Line 230:82: E231 missing whitespace after ','
Line 246:80: E501 line too long (86 > 79 characters)
Line 247:80: E501 line too long (91 > 79 characters)
Line 392:17: E128 continuation line under-indented for visual indent
Line 457:80: E501 line too long (80 > 79 characters)

In the file src/ambianic/pipeline/ai/image_boundingBox_detection.py:

Line 57:80: E501 line too long (82 > 79 characters)

In the file src/ambianic/pipeline/ai/pose_engine.py:

Line 148:80: E501 line too long (81 > 79 characters)

In the file tests/pipeline/test_store.py:

Line 22:37: W291 trailing whitespace
Line 42:1: W293 blank line contains whitespace

@bhavikapanara There is 7.3% regression in code coverage in store.py. We should be increasing code coverage with each PR to prevent production bombs like the one this week.
src/ambianic/pipeline/store.py | 92.70% <41.66%> (-7.30%)

Codecov Report

Merging #332 (4b0c350) into master (ee79c40) will decrease coverage by 0.23%.
The diff coverage is 91.89%.

@@            Coverage Diff             @@
##           master     #332      +/-   ##
==========================================
- Coverage   94.53%   94.30%   -0.24%
==========================================
  Files          23       23
  Lines        2197     2230      +33
==========================================
+ Hits         2077     2103      +26
- Misses        120      127       +7

Impacted Files	Coverage Δ
src/ambianic/pipeline/store.py 92.70% <41.66%> (-7.30%)	⬇
src/ambianic/pipeline/ai/fall_detect.py 97.27% <96.22%> (+0.11%)	⬆
src/ambianic/pipeline/ai/face_detect.py 100.00% <100.00%> (ø)
...mbianic/pipeline/ai/image_boundingBox_detection.py 100.00% <100.00%> (ø)
src/ambianic/pipeline/ai/object_detect.py 100.00% <100.00%> (ø)
src/ambianic/pipeline/ai/pose_engine.py 97.93% <100.00%> (ø)

Yes
On Tue, Feb 23, 2021 at 2:53 AM bhavika panara<EMAIL_ADDRESS>wrote:

@bhavikapanara commented on this pull request.
In tests/pipeline/test_store.py
https://github.com/ambianic/ambianic-edge/pull/332#discussion_r580859600
:

   json_inf = json.load(f)

   print(json_inf)

   img_fname = json_inf['image_file_name']

   rel_dir = json_inf['rel_dir']

   img_fpath = os.path.join(out_dir, rel_dir, img_fname)

   assert img_fpath == str(store._img_path)

   json_inf_res = json_inf['inference_result']

   assert len(json_inf_res) == 1

   json_inf_res = json_inf_res[0]

   assert json_inf_res['label'] == 'person'

   assert isinstance(json_inf_res['confidence'], float)

   assert isinstance(json_inf_res['box']['xmin'], float)

   assert isinstance(json_inf_res['box']['ymin'], float)

   assert isinstance(json_inf_res['box']['xmax'], float)

   assert isinstance(json_inf_res['box']['ymax'], float)

@ivelin https://github.com/ivelin Did you mean to delete the created
directory (i.e tmp/detections/20210223-140610.026448) after finishing the
test?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ambianic/ambianic-edge/pull/332#discussion_r580859600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARBUFJZT45F5VH46G7UPF3TANUHHANCNFSM4X4S6KLA
.


qrcp: renamed from qr-filetransfer, unstable-2018-10-22 -> 0.6.4

Motivation for this change
Things done

[ ] 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.

/marvin opt-in
/status needs_reviewer

/status needs_work

/status awaiting_changes

Rebased.

/status awaiting_changes

Result of nixpkgs-review pr 98494 run on x86_64-darwin 1

1 package built:

qrcp

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

1 package built:

qrcp


multiple pages not shown in entries table

if an entry  have multiple pages selected, none of them shows up in entries table.

This is definitely an issue in Symphony 2.5.x

@designermonkey I never works ? I was not even able to reproduce it...
Is it only when the field is the first visible one ?

Example:

All of those 'None' pages have all pages attached to them.

Got this, curious to know if it impacts #21 at all for you @designermonkey? Having trouble reproducing the missing entries!

Yeah, I just said the same thing to @psychoticmeow, I think it may be related. Will pull this now.


Messagedata

Hi,
This PR lifts the restriction on usage of MessageData in message contracts to interface only. It now supports a message contract specified as a class to participate.
I copied an existing unit test (InitializerMessageData_Specs.cs) and modified it so that the scenarios exercised for an interface defined contract were also ran for a class defined contract.
I am unfamiliar with this area so happy for any feedback on additional testing required due to me missing requirements.

Merged.


Add hyperterm-alternatescroll package

Checklist for submitting an awesome plugin, theme, or resource:

[x] The title for my package or theme uses its npm title (hyperterm-plugin-example)
[x] The link for my package or theme uses the npmjs.com link (https://www.npmjs.com/package/hyperterm-plugin-example)
[x] There is a visual representation of what my plugin or theme does in the repo. (Plugin: screenshot or gif || Theme: screenshot of the theme applied to HyperTerm)
[x] Put your awesome item at the BOTTOM of the correct (plugin, theme, or resource) list.
[x] VERY IMPORTANT: I've written a short (one sentence) description for my package or theme as the description of the awesome plugin, theme, or resource in the README.md file I'm submitting in the PR.

This plugin enables hyperterm to be able to use scroll wheel to scroll in git diff, nano etc.
This useful feature is available in terminal.app and iTerms, but not in hyperterm.
So I believe this is a must have plugin for people using hyperterm.

Awesome - used this all the time! Merged!


Use the correct SHA for dependency snapshots from pull requests

👋🏽 from the Dependency Graph team at GitHub!
I've been working on some functionality related to dependency snapshots on pull requests, and I've discovered an unfortunate fact about the behavior of github.context.sha/$GITHUB_SHA in that context.
Evidently, github.context.sha is not always what you might consider the "current commit" in a given context. In most GitHub pull request event types, github.context.sha will be the "Last merge commit on the GITHUB_REF branch" (See Actions documentation here). In those cases, the commit SHA that should be associated with the snapshot is github.event.pull_request.head.sha.
This PR adds a helper function, getSha, which will return the correct SHA for the current context, and uses that function to find the right SHA to add to the dependency snapshot.

@juxtin could you sign off the commits, though, please?


Does this work on JupyterHub?

I am using JupyterHub -- and the screenshot in the README is not for JupyterHub. It doesn't seem to be working.
Just want to check if it's actually unsupported or I'm doing something wrong.

As we are just modifying the DOM of the notebook, it is possible that it does not work for jupyter lab.
I will investigate and let you know


kong miss return uris

Summary
kong miss return uris
Steps To Reproduce
1.use docker to deploy a vue project
2.set upstream on kong dashboard
3.set uris in apis on kong dashboard
4.while view http(s)://domain-name/uris/homepage
error, the return js or css miss uris
for example:
the js url should be http://domain-name/uris/dist/xxxx.js
but now the url is http://domain-name/dist/xxxx.js
so url is wrong, the browser cant find right js and css directory
Additional Details & Logs

Kong version 0.13.1

I think it is not an issue with Kong per se, but that your web site uses perhaps a root-relative references. Kong by default does not transform the payload your upstream is sending.

As nothing has happened here, I feel we don't have enough information to pursue this any further.


Generator expects fromDocument which isn't available

Describe the bug
When using a standard nswag file, the file generator fails since.
Steps to reproduce the bug
Use this library with the example .nswag above and you'll get an exception in this line:
https://github.com/HavenDV/H.NSwag.Generator/blob/019ab78ff4043fef49dc5d62a5fe755e28dba265/src/libs/H.NSwag.Generator/NSwagGenerator.cs
Expected behavior
No response
Screenshots
No response
NuGet package version
No response
IDE
Visual Studio 2022-preview
Additional context
No response

I guess I just didn't expect this use case. I will try it when I have free time


feat: add label

This pull request adds the label component to the design system. Further more, it also replaces the default HTML Label in the Input and TextArea component with our own.

:tada: This PR is included in version 1.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


test_calculate_grade.py issues has NO test for the calculate_grade()

test_calculate_grade.py has NO test for the calculate_grade() function. Chen, you only tested for the properties of the input data frame.
We should also test for OUTPUT of the calculate_grade() function.

Test case for running calculate_grade() added per here


IOS-3202: Feature/Adapting URL Requests

Issue Link
https://spothero.atlassian.net/browse/IOS-3202
Description
This is the first half of changes that will eventually allow for the ability to handle tasks such as renewing access tokens upon receiving a 401 from the server and retying a request with a refreshed access token before failing completely.
To achieve this, I'm planning the following:

Create a RequestAdapter protocol which will allow clients to make changes to a request before it is sent to the server (e.x. add an Authorization header to the request with the proper credentials)
Create a RequestRetrier protocol which will allow clients to see why a request failed and tell the HTTPClient whether or not it should retry to request (e.x. If the status code was 401, try renewing our access token and storing it. Then, when the request is retried, it'll call the RequestAdapter which can add the updated access token to the headers.)

This PR covers the first bullet point, in which I:

Added the RequestAdapter protocol
Changed the return type of our HTTPClient methods to use a new Request object. This is due to adapting the request being an async process and eventually become retrying will result in a new URLSessionTask being created
Give the client the opportunity to adapt the URLRequest prior to starting the task

Note: This is going into an aggregate branch until the retry logic is completed as well.

Just for confirmation on tests:


Finalize and Submit User Stories

We've submitted these user stories but @jbinvnt still needs to add them to the repository. Note to self, in the future write the user stories in Markdown for easier reading once we're out of Google Docs and back to GitHub


Moulinette FilePicker generates "stack size exceeded" errors

I have (sometimges) trouble accessing the default filepicker when I enabled to use the moulinette one and get this in the console:

only only happens to filepickings where I sucessfully selected an object in my s3 storage earlier. If I use a filepicker on an item where the image for instance still resides on the server the default filepicker still works
it still works with some files/places on s3. could it be that the place the default fp is pointed at has to many objects for mounlinette to handle in what ever stack your are using there @Dorgendubal | Moulinette
the bad directory has indeed a few items, its the place I stuffed the wow icons away from wowhead, which are roughly 22k
oh just disabled everything and the error still persists, so I guess its a core problem. I will go over to that discord then and bug someone there 🙂

For me, it seems to happen over time when rendering large numbers of scenes with base64 thumbnails.

I'll close this issue because it is not happening frequently (I cannot reproduce it) and it doesn't affect many people.


Swap pg_authid for pg_roles

Doing this again as I accidentally deleted my repo for #380

As far as I know, these tables are equivalent apart from the password column, however managed database services (Digital Ocean, and RDS) don't allow access to pg_authid

@adnathanail thanks


Update webhooks.md

Documentation for "Allowed IP addresses and domain URLs", has the ADO IPs to be allow listed when connecting to Service Hooks.
But the Service Hooks documentation link has example with only Public service and customers are creating cases requesting a way to connect to a service behind a private network.
Added the documentation link which specifies the ADO IPs to be allow listed to connect to Services:
https://learn.microsoft.com/en-us/azure/devops/organizations/security/allow-list-ip-url?view=azure-devops&tabs=IP-V4#inbound-connections

@aaronhallberg
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

accepting @chcomley 's sign off.


style(landing-page): Improve responsiveness of the landing page

We should improve the responsiveness of the landing page right now it doesn't look good on mobile devices!
Screenshot:

Discussed in #112

Hey @Lalit3716 are you working on this? If not, then I want to work on this

Sure @Preet-Sojitra, I haven't started working on this you can go ahead if @ayoayco agrees!

yes go ahead guys 👍

yes go ahead guys 👍

Will start working on this 🚀


Add clisops tests to cope with case: time-invariant field selected with time range...need to raise Exception "there is no time coordinate in the input data - cannot extract time subset"

closed with pr #120


Trying out tags for more streamlined publishing

Manual Bumping: Any commit message that includes #major, #minor, #patch, or #none will trigger the respective version bump.


False "should use copy() instead of a loop" positive on copy from slice to map

Hi !
Here is an example of code triggering a false-positive:
mySlice := []string{"testValue"}
myMap := make(map[int]string, len(mySlice))
for k,v := range mySlice {
        myMap[k] = v
}

Using a freshly go get -u'd version of gosimple, I get the "should use copy() instead of a loop" on this.
But copy() cannot be used with a map.

Working on a pull request, coming soon

Closed by 264f25f0dbb049dd9e46440044816cda39ba0343


Absolutist focus tree fix

Solving definitely https://github.com/Idhrendur/paradoxGameConverters/issues/367

Thanks!


Run all DateTimeFormat tests by default

These were previously omitted because the tc39/proposal-temporal reference code didn't provide a spec-compliant DateTimeFormat object. Now (most of) those compliance issues have been fixed, let's run those tests.

I guess we need to land an update to the ignore file in js-temporal/temporal-polyfill before we can land this?

Yep, that's correct. @ptomato

Done, at https://github.com/js-temporal/temporal-polyfill/pull/282.


Removes glob import of ErrorKind within Display

Recently I learned about glob imports of enums and how they interact with match statements. Basically, glob imports of an enum that are used with a match can be a footgun. Refer to this playground:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=9f0ce5f074f7b4a71f487ae8c6a1902d
So instead of a glob import, create a short alias of ErrorKind.

Thanks!


Automatically detect possible responses

Hello, currently it seems that this package is only able to auto-detect my models/DTOs and the different endpoints. But the relation between endpoints and models and the possible response codes have to be manually set by attributes on the several functions.
With Swashbuckle and the SwaggerGen on ASP .NET Core all these things got detected automatically.
Am I missing something or doesn't this package support all features from the official Swashbuckle?

Closing this, as not relevant, please reopen if needed


FooterList component

Epic https://github.com/x-team/auto/issues/573

Create new component.

Props
title: string,
items: [
  {
    label: string,
    handleClick: function,
  }
]

Behaviour
None specific behaviour.

@bernardodiasc do you think we need handleClick for each item? Or would url suffice?

@bernardodiasc I'd reckon, providing url endpoint would be sufficient to handle generic item click.

Sure thing, if the render uses  then it does make sense.


Ipython 8.16.0 is breaking the CI

Release notes: https://ipython.readthedocs.io/en/stable/whatsnew/version8.html

do you have the traceback?

https://github.com/ploomber/jupysql/actions/runs/6350675691/job/17250770253

ok, are we certain IPython is breaking it?
If so, please open a PR and let's pin IPython so we can fix this and an issue so we can dig up later
@nooodle-soup: this looks similar to what you encountered in your PR

I'll change the ipython version to check and give an update

There's a discrepancy in the jupysql setup.py and our integration tests.
The setup.py has ipython<=8.12.0 and the integration test uses the latest ipython verison (check here)

I made a change (here) to the setup file in my PR and the tests that were failing before are now passing.

I made a change (here) to the setup file in my PR and the tests that were failing before are now passing.
Matplotlib tests in test_magic_plot are now failing instead

All the tests now pass when using pkgmt==0.7.3 instead of the latest pkgmt. You can have a look here

@edublancas @neelasha23  My tests just passed with the latest IPython version.

They might have fixed in yesterday's release !

Seems so!


Basic Javascript 121: Stand in line

Challenge Stand in Line has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function nextInLine(arr, item) {
  // Your code here
  arr=arr.push(item);
  var removed=arr.shift();

  return removed;  // Change this line
}

// Test Setup
var testArr = [1,2,3,4,5];

// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(nextInLine(testArr, 6)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));

@nsaimadhusudanan2801  Thank you for reporting this issue. Your code is incorrect. Please use the Gitter chat rooms linked below for asking for help. GitHub issues are not for coding help.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on freeCodeCamp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.

Hi,
Thanks for reporting this issue.
Here are some next steps that you should follow before we can help you with your query:

Check these troubleshooting steps first.
Please use the Chat Rooms or try looking through our forum for help with a specific challenge and any coding assistance.

IMPORTANT:
Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only.
Happy Coding!

Thank you all for your comments. I was actually using Mozilla Firefox, which was not able to solve that challenge. I tried the same thing with Microsoft Edge and was able to solve it. The issue was with the browser.
Again thank you all.

This worked for me
`
function nextInLine(arr, item) {
var addToEnd= arr.push(item); //Add the parameter "item" to the end of "array"
return arr.shift(); //Removes the first element of the array
}
// Test Setup
var testArr = [1,2,3,4,5];
// Display Code
console.log("Before: " + JSON.stringify(testArr));
console.log(nextInLine(testArr, 6)); // Modify this line to test
console.log("After: " + JSON.stringify(testArr));
`

@shoxton
Please do not post your solution on here. You could help people at FreeCodeCamp Chat Room or Forum. GitHub Issues are for reporting bugs on the website only.
Happy Coding!


Regression: missing TESSERACT_VERSION

Tesseract API changed with almost each release.
TESSERACT_VERSION  was implement to help programmers (or tesseract library user) to support multiple version of tesseract APIs.
In current code (for 4.0 release) this part of API was removed.
I appreciate work to simplify storage of info version but missing TESSERACT_VERSION is showstopper for me for release 4.0 version.
4.0.beta1 (where TESSERACT_VERSION is included) is included new Ubuntu release and therefore there should be no API changes between 4.0 final release and 4.0.beta1 (at least there should be very good reason for such change).

I'll prepare a pull request which adds TESSERACT_VERSION again (derived from PACKAGE_VERSION) as it can be useful for external software which supports different versions of the Tesseract API.

Thank you, @zdenop.


feat: 🎸 add result to successfully ran transactions

Description
Adds a getter result to PolymeshTransactionBase class. this will have the result resolved from run() so it can be accessed later
Breaking Changes

JIRA Link
✅ Closes: DA-407
Checklist

[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 17.1.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 19.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 19.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 19.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature/http watcher

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature

What is the new behavior (if this is a feature change)?
Adds httpWatcher device which polls endpoint to see if it is active.

Other information:

I am not sure if it is best to merge this to master, or to rebase onto developmen when it becomes stable.

This is already merged in.


[Bug]: When user try to edit the goal , on Edit Goal Section there retrieve Target Name but not retrieve Target Details

Contact Details
<EMAIL_ADDRESS>What happened?
[Bug]: When user try to edit the goal , on Edit Goal Section there retrieve Target Name but not retrieve Target Details , but you need to retrieve the target details also and put into the edit text .
Relevant log output
No response
Code of Conduct

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

I want to contribute to this issue under JWOC


How to use Memory-mapping bpf map by libbpfgo

I found out that the Linux kernel supports memory-mapping BPF maps, but I'm not sure how to use it in libbpfgo, are there any examples. Thanks

@dbfancier best place for your to learn is from our selftests at:
https://github.com/aquasecurity/libbpfgo/tree/main/selftest
You're probably referring to how you can transmit events from kernel to userland:
https://github.com/aquasecurity/libbpfgo/tree/main/selftest/perfbuffers
or
https://github.com/aquasecurity/libbpfgo/tree/main/selftest/ringbuffers
but you may also be referring to how to access shared data among kernel and userland (through eBPF maps):
https://github.com/aquasecurity/libbpfgo/tree/main/selftest/map-update
I'll close this as this is not an issue in libbpfgo.


Remove or update logo in distribution

I suggest updating or removing the logo.gif file from the distribution. Example here:
https://www.dnnsoftware.com/images/branding/logo.gif
Description of solution
Update to current branding or remove entirely.
Description of alternatives considered
Alternative is to leave it as is. However it cheapens the brand and provides a vector for hackers.
Screenshots
See kink above.
Additional context
It's been reported by me many times over the past few years.
Affected version

[x] 9.3.2
[x] 9.3.1
[x] 9.2.2
[x] 9.2.1
[x] 9.2
[x] 9.1.1
[x ] 9.1
[x ] 9.0
And previous versions.

Affected browser

ALL browsers

[x] Chrome
[x] Firefox
[x] Safari
[x] Internet Explorer
[x] Edge

Thank you John for pointing out this - but this old logo could also lead astray the hackers as they try to hack a DNN 5.x site :-)
No, back to serious: that should really be deleted, as it is an excessive disclosure about the system - and when I may give my two cents, I would also remove the copyright message and the default keywords ("dnn", "dotnetnuke") by design.

It looks like this file is not referenced anywhere else in the solution, so it should be safe to remove.

I will happy take assignment of this issue and process a PR.  Thanks for finally reporting it here @Roylej


Build status on main page

Is your feature request related to a problem? Please describe.
Add our build status to the main page

Fixed with PR #37


mpi-crayxc failure in megampi

Original issue: https://charm.cs.illinois.edu/redmine/issues/1445

megampi fails on mpi-crayxc build on Edison on the first run with multiple PEs, with +p2 +vp2. Possibly due to migration?

Original author: Karthik Senthil
Original date: 2017-02-28 19:26:02

The following is a trace of the crash on Edison:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: MPI_THREAD_SINGLE (desired: MPI_THREAD_SINGLE)
Charm++> Running in non-SMP mode: numPes 2
Converse/Charm++ Commit ID: [New Thread 0x2aaaaacca700 (LWP 5994)]

Program received signal SIGSEGV, Segmentation fault.
__longjmp () at ../sysdeps/x86_64/__longjmp.S:56
56	../sysdeps/x86_64/__longjmp.S: No such file or directory.

I also verified that the program does not reach AMPI initialization functions like ampiNodeInit and ampiProcInit. It crashes even before these functions are executed.

Original date: 2017-02-28 19:31:07

The stack trace looks like a failure during a context switch but is pretty opaque. What is weird is that the other AMPI tests/examples pass manual testing...

Original date: 2017-03-06 14:25:12

Fixed by making context threads the default on mpi-crayxc: ~~https://charm.cs.illinois.edu/gerrit/#/c/2282/~~ https://github.com/UIUC-PPL/charm/commit/2ed0f878ab41eaf766ab0fed8f9546d601a278a5


fix: authentication check failure for gcr.io

Signed-off-by: Matej Vasek<EMAIL_ADDRESS>Cherry picked from main 6c282e77c2ffc6c6485fd4760b1738b11a2189eb

/lgtm


App has stopped no error are showing on run android

I have upgrade my project v 0.55.4 to 0.59.9 then I migrate it to androidX because of some issue with old android support.
I have followed this url to upgrade 0.59.9
https://react-native-community.github.io/upgrade-helper/?from=0.55.4&to=0.59.9
Now, after that successfully upgrade I'm had issue with new androidX support as my all library are in old android support so I have manfully update all library to androidX just to build apk.
After solving all the bugs and migration, when I run react-native run-android, App not starting I'm getting following error.

React Native version:  0.59.9
react-native info:

React Native Environment Info:
System:
OS: Linux 5.0 Ubuntu 19.04 (Disco Dingo)
CPU: (4) x64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Memory: 169.34 MB / 7.66 GB
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/bin/node
npm: 6.9.0 - /usr/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29
Build Tools: 23.0.1, 25.0.0, 25.0.2, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2, 28.0.3
System Images: android-27 | Google Play Intel x86 Atom
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.9 => 0.59.9
npmGlobalPackages:
create-react-native-app: 2.0.2
react-native-cli: 2.0.1

android/app/build.gradle
apply plugin: "com.android.application"
apply plugin: 'io.fabric'
import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = true

android {
	purgeBackgroundGeolocationDebugResources(applicationVariants)
    compileSdkVersion rootProject.ext.compileSdkVersion
     compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    dexOptions {
      javaMaxHeapSize "4g"
    }
    defaultConfig {
        renderscriptTargetApi 19
        renderscriptSupportModeEnabled true
        multiDexEnabled true
        applicationId "com.smarttransitio"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
        }
    }
    buildTypes {
        debug {
            minifyEnabled enableProguardInReleaseBuilds
            shrinkResources true
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release

        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2, "arm64-v8a": 3, "x86_64": 4]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {
    implementation project(':@react-native-mapbox-gl_maps')
    implementation project(':react-native-background-fetch')
    implementation project(':react-native-nfc-manager')
    implementation project(':react-native-background-timer')
    implementation project(':react-native-background-geolocation')
    implementation project(':react-native-keep-awake')
    implementation project(':react-native-smartwifi')
    implementation project(':react-native-smartnfc')
    implementation project(':react-native-imei')
    implementation project(':react-native-splash-screen')
    implementation project(':react-native-branch')
    implementation 'com.android.support:multidex:1.0.3'
    implementation 'com.google.firebase:firebase-core:16.0.9'
    implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'
    implementation project(':react-native-fused-location')
    implementation project(':react-native-vector-icons')
    implementation project(':react-native-shimmer')
    implementation project(':react-native-linear-gradient')
    implementation project(':react-native-image-picker')
    implementation project(':react-native-i18n')
    implementation(project(":react-native-device-info"), {
        exclude group: "com.google.android.gms"
    })
    implementation "com.google.android.gms:play-services-gcm:16.0.0"
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation "com.facebook.react:react-native:0.59.9"  // From node_modules
}

// Run this once to be able to run the application with BUCK
// puts all implementation dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}
apply plugin: 'com.google.gms.google-services'

// [Added by react-native-background-geolocation] Purge debug sounds from release build.
def purgeBackgroundGeolocationDebugResources(applicationVariants) {
    if ((rootProject.ext.has("removeBackgroundGeolocationDebugSoundsInRelease")) && (rootProject.ext.removeBackgroundGeolocationDebugSoundsInRelease == false)) return
    applicationVariants.all { variant ->
        if (variant.buildType.name == "release") {
            println("[react-native-background-geolocation] Purging debug resources in release build")
            variant.mergeResources.doLast {
                delete(fileTree(dir: variant.mergeResources.outputDir, includes: ["raw_tslocationmanager*"]))
            }
        }
    }
}

React Native 0.59 is not compatible with AndroidX, that's why you may encounter issues. Please update to 0.60 where it's supported natively.

Error still exists with 0.61


No Archival Objects selected to export SIP error

the 2.0.0-rc.2 version fixed the "unable to move file" error message. I opened the existing carp file with the new version, then exported SIPs without minting ARKs (just to see how the files would get moved/copied.) Carpenters created the SIPs and they looked great in the filesystem, and Carpenters created the "Files" folder at that time, BUT... the filenames disappeared from the files tab in Carpenters. Since I couldn't go back to the previous version of the carp file, I deleted the exported SIPs and added the files back again in Carpenters in order to export with ARKs. But this time when I try to export with ARK minting enabled, I get the error message "No Archival Objects selected to export SIP."

@librarycard was the project a standard project or archival project?

This was a standard project.


Intellisense stops working for python files when using the new 'Outline' feature

Environment data

VS Code version: 1.24 insiders
Extension version (available under the Extensions sidebar): latest
OS and version: Win10
Python version (& distribution if applicable, e.g. Anaconda): 3.6.5 - standard distribution
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: XXX

Actual behavior
using network drive as project is hosted on a shared drive.
intellisense becomes un-responsive after a few python files are opened.
snippets also stops working
intellisense will work fine for other file types.
using process explorer i kill "python completion.py".
intellisense becomes responsive and works correct.
Expected  behavior
intellisense always work.
Steps to reproduce:

initially things seem to work fine.
The new Outline  also works.
The after a few minutes it all stops working.
The new OUTLINE does not refresh when you select a different file.

selecting a new file should at a minimum clear the OUTLINE. but it stays with the value from some previous file which is very misleading.

killing the python completion.py sometimes works...

Please check if there are any errors logged in the Python output window (View->Output, select Python from the dropdown)
Please check if there are any errors logged in the console window Help-> Toggle Developer Tools

Can this be related with this question I did in SO? If this comment violate de rules, I'll remove. Thanks.

In the Developer Tools - Console i am seeing this. All my Extensions are no longer listed

In the View Output  , Python is not listed

I need to restart COde now due to the 1st error seems to periodically appear as a notification.
Its a large project with N x individual python applications.
1 does use numpy (installed on Win10) and matplotlib (not installed on Win10)
Im not using a 3rd party SDK. I do have Atom, Sublime, PyCharm installed, WIngIDE (all part of an attemtp to find a good editor for Python development).
Im using VSCode on Windows. Im not using it for debug. just as a code editor (code complete, symbol Outline , highlighting etc..). All the python is executed on linux and hence i have a network drive to make the linux shared disk visible on windows.

As a further note.

ive Python linting disabled (in case its interferring with performance). ultimatly i want to turn this on.
In my workspace ive setup the Code to ignore some folders from Explorer. This is in theory to minimize the number of files.
the workspace has < 10K files, of which 1346 are python

thx
Derek

Does Jedi leave a DB file behind.
is it something you can inspect.
What i also notice is that the Outline in insiders also stops working.
It is like it gets "stuck" and no longer updates.
I assume this is implemented via Jedi
If i close all the open editors, open a new file, then the outline for the newly opened file is identical from to when it stopped working.
In following diagram you can see the open file is ccconfig_mod.py.
the outline is showing outline for a different file.

This is also happening to me, and it's incredibly frustrating. VScode-Python kills all intellisense for me.

A better solution to get intellisense back working is to just disable the extension Python.
With it disabled, intellisense seems to be working.
My code snippets are working.
Colour coding of Python still seems to work.
Obviously now ive lost

Linting
Outline

Extremely disappointing that it has come to this.
i want to use VSCode. I can live without the linting. but the Outline for symbols in the current file is so useful. at a glance you see all the methods.
i cant understnad why it cant work simply. Ive come from Notepad++ and it just works.

That's where I'm at as well– it's incredibly frustrating and seems like a massive oversight to have something so critical not work on the canonical extension for python language support in VSCode.
How is this not a top-priority fix for this package?

@joristaglio Please respect the devs, they're doing great work you're not paying for and they only have so many hands.
If you want to have this resolved earlier, contribute your time and help the Microsoft team reproduce this issue. I'm using Python in my everyday work yet I never managed to stumble upon this problem so it's likely that it only affects a small fraction of the community.

appreciate the devs and the effort.
im trying my best as well to convey the problem and provide as much information as i can to aid you guys. ive spent days trying to get this to work, to no avail.
what type of diagnostics can i do to help you out to debug the issue?

This depends on type of the project and source code. Completion process basically runs Jedi out of process. There is a shallow wrapper there over Jedi to handle out of process requests from the extension for the completion, tooltips etc. One way to try and repro (and maybe report directly in Jedi GH) is to import Jedi (it is in Python) and write short code that asks Jedi to return completions for a given file and location. Just see if it works as is.

@derekwallace - no, Jedi does not appear to cache results of persist a database.

I installed Jedi on PC.
I created a simple .py script to read one of the files in my workspace on my p:
Here is the script (del.py)
sFile = r'P:\perforce_Playground\derekw_de02-1777_rce_dev\tools\iipregr\bin\iipregrpkg\cascript_mod.py'
with open(sFile, "r") as fh:
   s = fh.read()

script = jedi.Script(source=s, line=50, column=1, path='MYFILE')
print(script.goto_definitions())

names = jedi.names(source=s)
for x in names:
   print(x)

I ran it locally outside VSCode in a Command shell.
Took about 2 sec to run
C:\derek\Python\Jedi>python del.py
Example2
[]
<Definition module collections>
<Definition module getpass>
<Definition module logging>
<Definition module os>

In VSCcde, i tried to run via "Run Python in terminal"
And it behaved the same.

For the record, here is a screen shot of del.py in VSCode and the outline is frozen with content from launch.json.

Close VSCOde, reopen, and you can see that Outline has del.py

Select cascript_mod.py (which i analyzed with del.py and Jedi).
Its now frozen and doesnt update.

at this point intellisense etc. is dead.
Is it in ANY way related to ripgrep running ?
Could this "block" other things running ....

I get similar reports in https://github.com/patrys/vscode-code-outline/issues/134 (this is older than the built-in Outline mentioned above but works in the same way) which suggests that over time the SymbolProvider stops working.

I decided to create a brand new workspace (on network p: drive).
it consists of about 30 .py files. So small. This eliminates my concerns re size of my project workspace.
I have the same issue with Outline and symbols. Initially work for a few mins and then stop.
Never refresh. Intellisense stops working.
As a note, i have another issue open wrt performance of the Debugger. See  https://github.com/Microsoft/vscode-python/issues/1744
I have this resolved and it came down to something in the launcher.json file .
I then created exact same workspace on c:
And outline, intelli all work fine.

@derekwallace  We've had other reported issues with network drives. Could you provide the sample files that triggers the issue for you?

HI,
Ive created a small workspace. with 4 python files and a .yml file.
They were originally my project files, but ive trimmed them back to almost nothing, and removed all meaningful names etc. The files are not functional, but have imports, class , methods etc.
Attached the workspace
attached the workspace file
attached the user settings file
a_vscode_project_p.zip
settings.zip
a_vscode_project.zip
below , when i use the word "freeze" it means

Outline stops updating for Python files
Intellisense stops working in Python files

Here is what i do to trigger the issue.

Open the workspace

Open all 5 files

In, Open Editors select the files one by one randomly ...
Initially the Outline updates for each file. can take 1-2 sec, can take 5 sec.
Occasionally this alone can trigger the "freeze". But in this very small design it seems to rarely cause it.

now i start to edit some files.
i normally go to a file and type "def" to see will intellisense pop up.
I sometimes have to jump to one or more files and in each type "def".
i might save file, i might not.
eventually it will freeze (1-2 mins)

I cant find a specific pattern that causes it. but i can always get it to happen.

at this point selecting different .py files in Open Editors will not refresh the Outline
intellisense is frozen

if i select the wal.yml file, the outline will refresh and show this docs outline
if i select any .py file the outline does not update.

while doing the above repeatedly (i.e. close workspace, open workspace, and repeat)..... ive noticed that the outline can sometimes re-start working.
The intellisense rarely restarts (if ever)

I hope this is of use.
Derek

I just realized something: where is that outline coming from? Do you have another extension installed to show that? If so can you disable all extensions but ours and see if this is still a problem?

@brettcannon I removed all extensions and the behavior continued with only the Python extension.

@brettcannon Both outline implementations (my extension and the one built into VSCode) call "executeSymbolProvider" to obtain a list of symbols and their ranges.

@brettcannon disabled all extensions. Same behaviour.
A further note. Disable the Python extension, reload, and now intellisense is working (without Python knowledge, and outline etc...). But at least i get some code completion and my snippets work.
Enable Python and reload. Outline starts working,  and quickly it stops and intellisese becomes unresponsive.
Its clearly the Python extension.

@patrys I see https://github.com/Microsoft/vscode/pull/49917 shows that one has landed in the insiders build which I didn't know about. That should help in trying to replicate the issue.

@brettcannon  Ive been using the insiders build in all my testing. Initially i used Code Outline extensions and thought it was the issue. but at this point we know its something related to the Python extension.

@derekwallace Thanks for providing the samples and information required to replicate this issue. I'll try to replicate this at my end.

@joristaglio

I removed all extensions and the behavior continued with only the Python extension– and the behavior was not also triggered by any of my other extensions if I enabled them each one at a time.

Are you using VS Code Insiders?

If you've answered No to all of the above, then please create a separate issue for the issue you are experiencing.

@DonJayamanne Opened workspace and disabled the Outline view in the Explorer. I tried editing the project files  for about 5 minutes. The Intellisense and global snippets worked flawlessly.
I then turned on the Outline in Explorer. The outline refreshed with the current file. Started editing file. Straight away i noticed the intellisense seems way more laggy. Sometimes its responsive and sometimes it falls asleep for 1-2 sec  and eventually it becomes un-responsive. At this point if i select a different file in Open Editors, the Outline does not refresh.
Developer tools has this error. Ive previoulsy looked in this console for errors. this is the 1st time ive seen anything that looks like an error wrt Python.

/C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1336  INFO standard startup Object
/C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:269 [Extension Host] vscode-icons is active! (at activate (C:\Users\derekw\.vscode-insiders\extensions\robertohuertasm.vscode-icons-7.23.0\out\src\index.js:41:13))
/C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:269 [Extension Host] Python Extension: stderr jediProxy, Error (stderr) Traceback (most recent call last):
  File "completion.py", line 634, in watch
    response = self._process_request(rq)
  File "completion.py", line 570, in _process_request
    sys_path=sys.path, environment=self.environment)
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\jedi\api\__init__.py", line 119, in __init__
    cache_path=settings.cache_directory
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\jedi\evaluate\__init__.py", line 383, in parse_and_get_code
    return self.grammar.parse(code=code, path=path, **kwargs), code
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\parso\grammar.py", line 76, in parse
    return self._parse(code=code, **kwargs)
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\parso\grammar.py", line 126, in _parse
    new_lines=lines
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\parso\python\diff.py", line 163, in update
    % (last_pos, line_length, ''.join(diff))
Exception: There's an issue (32 != 28) with the diff parser. Please report:
---
+++
@@ -24,9 +24,5 @@

    def Aaaa2(self):
       self.Aaaa1()
-
-
-
-
-
-+      for x in [1,2,3]:
+         print

 (at Logger.logError (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\logger.js:17:21))
t.log @ /C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:269

  ERR Cannot read property 'id' of undefined: TypeError: Cannot read property 'id' of undefined
	at responses.forEach (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\providers\jediProxy.js:393:54)
	at Array.forEach (native)
	at SafeSubscriber.result.out.subscribe.output [as _next] (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\providers\jediProxy.js:387:31)
	at SafeSubscriber.__tryOrUnsub (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:242:16)
	at SafeSubscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:189:22)
	at Subscriber._next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:129:26)
	at Subscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:93:18)
	at sendOutput (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\process\proc.js:59:32)
	at Socket.on (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\process\proc.js:62:47)
	at emitOne (events.js:96:13)
	at Socket.emit (events.js:191:7)
	at readableAddChunk (_stream_readable.js:178:18)
	at Socket.Readable.push (_stream_readable.js:136:10)
	at Pipe.onread (net.js:560:20)

I then disable the Outline in Explorer. Intellisense is still not responding.
Close VSCOde. Reopen workspace. Intellisense is behaving flawlessly again.

@DonJayamanne Opened workspace and disabled the Outline view in the Explorer. I tried editing the project files  for about 5 minutes. The Intellisense and global snippets worked flawlessly.
I then turned on the Outline in Explorer. The outline refreshed with the current file. Started editing file. Straight away i noticed the intellisense seems way more laggy. Sometimes its responsive and sometimes it falls asleep for 1-2 sec  and eventually it becomes un-responsive. At this point if i select a different file in Open Editors, the Outline does not refresh.
Developer tools has this error. Ive previoulsy looked in this console for errors. this is the 1st time ive seen anything that looks like an error wrt Python.

/C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1336  INFO standard startup Object
/C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:269 [Extension Host] vscode-icons is active! (at activate (C:\Users\derekw\.vscode-insiders\extensions\robertohuertasm.vscode-icons-7.23.0\out\src\index.js:41:13))
/C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:269 [Extension Host] Python Extension: stderr jediProxy, Error (stderr) Traceback (most recent call last):
  File "completion.py", line 634, in watch
    response = self._process_request(rq)
  File "completion.py", line 570, in _process_request
    sys_path=sys.path, environment=self.environment)
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\jedi\api\__init__.py", line 119, in __init__
    cache_path=settings.cache_directory
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\jedi\evaluate\__init__.py", line 383, in parse_and_get_code
    return self.grammar.parse(code=code, path=path, **kwargs), code
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\parso\grammar.py", line 76, in parse
    return self._parse(code=code, **kwargs)
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\parso\grammar.py", line 126, in _parse
    new_lines=lines
  File "c:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\pythonFiles\parso\python\diff.py", line 163, in update
    % (last_pos, line_length, ''.join(diff))
Exception: There's an issue (32 != 28) with the diff parser. Please report:
---
+++
@@ -24,9 +24,5 @@

    def Aaaa2(self):
       self.Aaaa1()
-
-
-
-
-
-+      for x in [1,2,3]:
+         print

 (at Logger.logError (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\logger.js:17:21))
t.log @ /C:/Program Files/Microsoft VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:269

  ERR Cannot read property 'id' of undefined: TypeError: Cannot read property 'id' of undefined
	at responses.forEach (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\providers\jediProxy.js:393:54)
	at Array.forEach (native)
	at SafeSubscriber.result.out.subscribe.output [as _next] (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\providers\jediProxy.js:387:31)
	at SafeSubscriber.__tryOrUnsub (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:242:16)
	at SafeSubscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:189:22)
	at Subscriber._next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:129:26)
	at Subscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:93:18)
	at sendOutput (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\process\proc.js:59:32)
	at Socket.on (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\process\proc.js:62:47)
	at emitOne (events.js:96:13)
	at Socket.emit (events.js:191:7)
	at readableAddChunk (_stream_readable.js:178:18)
	at Socket.Readable.push (_stream_readable.js:136:10)
	at Pipe.onread (net.js:560:20)

I then disable the Outline in Explorer. Intellisense is still not responding.
Close VSCOde. Reopen workspace. Intellisense is behaving flawlessly again.

Could this resolve the issue. Is there a way to use latest jedi ?
https://github.com/davidhalter/jedi/issues/1126

We're already using Jedi 0.12.0, but what I think you're suggesting is we upgrade our copy of parso 0.2.1, which we can do for the June release (we're in code freeze for May).

When will it get into the insiders edition. I can try.

Looks like the outline view is not throttling requests to the symbol provider, VSC is sending two requests to the symbol provider for each character typed in the editor window https://github.com/Microsoft/vscode/issues/51096

@DonJayamanne  would the lack of throttling explain the issues i am experiencing? Would a network disk with slower r/w access be more susceptible to issues due to this ?
i manually updated parso to 0.2.1. The error message wrt diff parser no longer appears.
Original  issues persist

outline stops working
intellisense stops working
global snippets stop working.

This error appear in the console
  ERR Cannot read property 'id' of undefined: TypeError: Cannot read property 'id' of undefined
	at responses.forEach (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\providers\jediProxy.js:393:54)
	at Array.forEach (native)
	at SafeSubscriber.result.out.subscribe.output [as _next] (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\providers\jediProxy.js:387:31)
	at SafeSubscriber.__tryOrUnsub (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:242:16)
	at SafeSubscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:189:22)
	at Subscriber._next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:129:26)
	at Subscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\node_modules\rxjs\Subscriber.js:93:18)
	at sendOutput (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\process\proc.js:59:32)
	at Socket.on (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.4.0\out\client\common\process\proc.js:62:47)
	at emitOne (events.js:96:13)
	at Socket.emit (events.js:191:7)
	at readableAddChunk (_stream_readable.js:178:18)
	at Socket.Readable.push (_stream_readable.js:136:10)
	at Pipe.onread (net.js:560:20)

@derekwallace yes, the Outline view is hammering the extension after every keystroke.

@derekwallace
We've believe we have fixed this issue, please could you download and install the latest development build of the extension (instructions can be found here)
Please let us know if the problem has been resolved.

@DonJayamanne i downloaded and installed the developer version of the python extension. Unfortunately the issue remains. Same/similar behavior as before.
I notice that the intellisense can be responsive, then it can start to become laggy to the point it becomes unresponsive. it very much feels like that as you type a set of changes overwhelms intellisense that it cannot keep up and hence becomes laggy.

Error message in console. This seems to happen when intellisense becomes unresponsive and outline completely stops refreshing.
ERR Cannot read property 'id' of undefined: TypeError: Cannot read property 'id' of undefined
   at responses.forEach (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\providers\jediProxy.js:393:54)
   at Array.forEach (native)
   at SafeSubscriber.result.out.subscribe.output [as _next] (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\providers\jediProxy.js:387:31)
   at SafeSubscriber.__tryOrUnsub (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:242:16)
   at SafeSubscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:189:22)
   at Subscriber._next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:129:26)
   at Subscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:93:18)
   at sendOutput (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\common\process\proc.js:51:32)
   at Socket.on (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\common\process\proc.js:54:47)
   at emitOne (events.js:96:13)
   at Socket.emit (events.js:191:7)
   at readableAddChunk (_stream_readable.js:178:18)
   at Socket.Readable.push (_stream_readable.js:136:10)
   at Pipe.onread (net.js:560:20)

@DonJayamanne To be sure i re-tried and i saw the same behaviour. At the moment that intellisense became un-responsive the below error appeared in console.
ERR Cannot read property 'id' of undefined: TypeError: Cannot read property 'id' of undefined
	at responses.forEach (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\providers\jediProxy.js:393:54)
	at Array.forEach (native)
	at SafeSubscriber.result.out.subscribe.output [as _next] (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\providers\jediProxy.js:387:31)
	at SafeSubscriber.__tryOrUnsub (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:242:16)
	at SafeSubscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:189:22)
	at Subscriber._next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:129:26)
	at Subscriber.next (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\node_modules\rxjs\Subscriber.js:93:18)
	at sendOutput (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\common\process\proc.js:51:32)
	at Socket.on (C:\Users\derekw\.vscode-insiders\extensions\ms-python.python-2018.5.0-rc\out\client\common\process\proc.js:54:47)
	at emitOne (events.js:96:13)
	at Socket.emit (events.js:191:7)
	at readableAddChunk (_stream_readable.js:178:18)
	at Socket.Readable.push (_stream_readable.js:136:10)
	at Pipe.onread (net.js:560:20)

@derekwallace

Please could you uninstall that extension
Delete all of the ms-python.python-* directories
Download and install the development version once again & test this out.

@DonJayamanne  Uninstalled and deleted the folders. Installed .vsix and the same behavior. Also get lots of errors from parso as its still 0.2.0

Installed

saw this error while testing again.
[IPC Library: Watcher] Uncaught Exception:  Service shutdown unexpectedly
t.log @ console.ts:136
(anonymous) @ ipc.cp.ts:157
e.fire @ event.ts:140
i @ event.ts:535
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104

@DonJayamanne Why is the issue closed?

@derekwallace because we updated to Parso 0.2.1 in master which you can test in either our development build or wait until our 2018.6.0 release.

I tested the development build of the python extension and it doesn't
resolve the issue. I was asked to test it and provide feedback . I have
done this and report that the issue persists. I don't see how the issue can
be closed.
On Tue, 5 Jun 2018, 21:56 Brett Cannon<EMAIL_ADDRESS>wrote:

@derekwallace https://github.com/derekwallace because we updated to
Parso 0.2.1 in master which you can test in either our development build
or wait until our 2018.6.0 release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-python/issues/1721#issuecomment-394857388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUOVpmTSFu74Ra3HosOeQM5f2qxqGHaks5t5vCUgaJpZM4UJPik
.

Is there any update? Did the dev build include more than the parso update? Did it have something to denounce the outline update.
Thx.

@derekwallace
Please understand that we are doing our best to resolve issues. Also, at this stage you seem to be the only user experiencing this issue.
I understand this can be quite frustrating for you as well, hence can I suggest you just turn off the Outline view for the moment.

Is there any update?

You can see all of the updates to this issue here, please scroll up and you'll have the answers to all of your questions.
Also VS Code have added some additional fixes at their end (see here https://github.com/Microsoft/vscode/issues/51096#issuecomment-394982635).
Again all of this information you see are on this issue (including the links to the VS Code issue).
Once again, please consider turn off (hiding) the Outline view for the moment.

I appreciate the support trying to resolve the issues. My colleagues have
the same issue. I'd be confident others do as well.
I have the developer build of python extension with parso update.
I looked at the vscode update. Is this in the insiders build? How do I know
I have this update?
I see from other issues that you seem to be working on another python
analysis extension. Is there any early access to this that I could try?
Thx.
Derek.
On Wed, 6 Jun 2018, 19:11 Don Jayamanne<EMAIL_ADDRESS>wrote:

@derekwallace https://github.com/derekwallace
Please understand that we are doing our best to resolve issues. Also, at
this stage you seem to be the only user experiencing this issue.
I understand this can be quite frustrating for you as well, hence can I
suggest you just turn off the Outline view for the moment.
Is there any update?
You can see all of the updates to this issue here, please scroll up and
you'll have the answers to all of your questions.
Also VS Code have added some additional fixes at their end (see here Microsoft/vscode#51096
(comment)
https://github.com/Microsoft/vscode/issues/51096#issuecomment-394982635
).
Again all of this information you see are on this issue (including the
links to the VS Code issue).
Once again, please consider turn off (hiding) the Outline view for the
moment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-python/issues/1721#issuecomment-395163202,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUOVjGBTUyP3EJ583ixkC4BgR-h4se2ks5t6BtFgaJpZM4UJPik
.

The parso update is in the latest public release of 2018.5.0. If you are installing the development build of the extension then the version would be 2018.6.0-alpha.
The new analysis engine is available for testing if you know the hidden setting to switch it on, but I'm not ready to give that out for this instance as we have not tested it yet with the Outline view.

This seems to have been fixed as I can't reproduce at least with a checkout build.

I don't think it should be closed.
With OUTLINE enabled, python code auto-complete takes 10-15 seconds to produce a suggestion, then even longer to show function/method input arguments. Disabling Outline, makes everything normal again.
this is for VCcode 1.24.0  on Ubuntu 16.04, with python 3.6 over Anaconda (with all the latest packages, including parso 0.2.1)

I don't think it should be closed either.
The updates have improved behaviour. In general I've found that the micro
test project both outline and intellisense work.
However on my large network drive project the outline is unusable and when
enabled makes the intellisense completely unresponsive. Disabling and
intellisense is just about workable. Sometimes responsive, Sometimes it's
laggy,
So there is still something going on that is interfering with normal
behaviour.
On Tue, 12 Jun 2018, 18:38 myron<EMAIL_ADDRESS>wrote:

I don't think it should be closed.
With OUTLINE enabled, python code auto-complete takes 10-15 seconds to
produce a suggestion, then even longer to show function/method input
arguments. Disabling Outline, makes everything normal again.
this is for VCcode 1.24.0 on Ubuntu 16.04, with python 3.6 over Anaconda
(with all the latest packages, including parso 0.2.1)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-python/issues/1721#issuecomment-396756879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUOVrpgY6mobqFcdkP1ba-hdWJbyTJkks5t8ELtgaJpZM4UJPik
.

"there is still something going on that is interfering with normal behaviour", and that behaviour is the outline view. 😉 VS Code is basically hammering Jedi every 250 ms to re-parse the file and analyze it for symbols. IOW there's not much we can do here short of throttling even more or magically making Jedi faster (also realize the Outline view is in preview for VS Code for a reason 😉; we actually had to provide the feedback to even have the 250 ms throttle added as originally it was every key press triggering a re-scan).
We are hoping to have the Outline view supported by our experimental analysis engine soon which should help alleviate this performance bottleneck. Once #1934 is merged and we have verified the new analysis engine works with the outline view I can provide instructions here on how to flip it on.

The latest build of the new language server should have the Outline functioning as expected. You can download a development build of the extension to test it out.


Moved some actions from components constructors to componentDidMount

I will send more components on the next week, thanks!

Thanks for starting this. Be sure to run tests and make sure they're passing and the linter is happy. We'll wait until they're all handled before merging.

Closing due to inactivity.


Some downloaded image files are empty.

TODO: Add file size control.

ah, actually, those files are not empty, they are 43 bytes long and start with GIF89a.

Resolved by using alternative image source in case of the empty or small image file.


Prepare for cortex-m-rt 0.7.5

Fixes #532.

Before we do the releases, have we checked that the new macro works as expected and rejects mismatched hard fault signatures?

Before we do the releases, have we checked that the new macro works as expected and rejects mismatched hard fault signatures?

Tests were added: https://github.com/rust-embedded/cortex-m/blob/master/cortex-m-rt/tests/compile-fail/hard-fault-bad-signature-3.rs
There are more too.
It doesn't pick up on unreleased macro crate releases because it defines the dependency with a path:
https://github.com/rust-embedded/cortex-m/blob/4395baee03d57a4e1763c427073da5f33ec3b17e/cortex-m-rt/Cargo.toml#L21-L22
This is probably the correct way in this crate, but yeah it does make it easy to forget to release any new version of it.

I think one solution for this is for the main branch to be changed to have the version number N + 1 right after version N is released, and for any dependencies within the same repo to also use N + 1 as a version number.

Also noting that @newAM successfully yanked v0.7.4 - we should probably note this in the release docs that we are fixing those regression(s).

I rebased this branch to fix CI and resolve conflicts.

I've rebased and updated the changelog with the various changes. Should be ready to go now.


[WIP] Show error overlay even after browser refresh

Currently, if you refresh the client whilst the compilation is in an error state you don't get any feedback (and if using the NoErrorsPlugin you actually get a working app; albeit using the last working bundle) -- you need to check the terminal window to be sure this hasn't happened.
This PR aims to solve the problem by publishing the 'built' event based on the last known compilation stats as soon as a client is registered with the middleware meaning the client script will show the overlay if appropriate.

NOTE: This is just a POC, I've just done it the quickest way possible to gauge whether it's something you'd be open to including?

Coverage increased (+0.5%) to 76.51% when pulling 0c9aabf82c612ff284fd970b5916ee2be202a2d9 on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

Coverage increased (+0.5%) to 76.51% when pulling 0c9aabf82c612ff284fd970b5916ee2be202a2d9 on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

@glenjamin I think it's actually desirable to have the rest of the hot reloading code run because as soon as you fix the error it'll just continue as if you hadn't ever refreshed.

Coverage decreased (-0.2%) to 75.839% when pulling 22d1f1b6ecc0574afb265cc8caf2bc6d2afae0d4 on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

Coverage increased (+0.5%) to 76.51% when pulling 443ffa9e4afef433cb025ee087716afc8dd7a8cd on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

Coverage increased (+0.5%) to 76.51% when pulling 443ffa9e4afef433cb025ee087716afc8dd7a8cd on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

@glenjamin I've tidied it up with the following improvements:

Added a 'sync' action to enable the client to differentiate it from the  'built' action; this allows the browser console logs to be nicer, i.e. it won't log [HMR] bundle rebuilt in 6649ms every time you refresh the client of an already built bundle.
No longer logs webpack built e484f8b43f0bc5beada4 in 32151ms whenever a request is received on the server -- i.e. the server already knows about this from the 'built' event so it doesn't log on the 'sync' event.
Added tests

Let me know your thoughts.

Coverage increased (+0.5%) to 76.51% when pulling b94bf7335b231e5b048070890567363b9c39b858 on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

Coverage increased (+0.5%) to 76.51% when pulling cd2ababcc248a511b93e899771e1e219e9bf4252 on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

Coverage increased (+0.5%) to 76.51% when pulling cdc3c345447a76e504c27ddc0714161990b19e3b on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

Coverage increased (+0.5%) to 76.51% when pulling 0ea45282153821fa224fb629f348130937682d2b on 60frames:refresh into ca9871daeac34a947512e573c022fe29f4c8d7bd on glenjamin:master.

@glenjamin 👍  let me know when you next publish

Released as 2.13.0


Hi I love your design. Can you make C, C++ and Haskell please. Thank you very much.

I'd like to have a new badge.
---Request Info:
Hi I love your design. Can you make C, C++ and Haskell please. Thank you very much.

Working on that...

Added C, C++, and Haskell


NuGet Packaqe is in Debug Configuration

I tried downloading the zip and building it myself, but the dll's built gave me an error when I tried to add them to my project. Any ideas? Can you build the package in release configuration and update the NuGet package?
This project is great!
Thanks!

I double checked and the NuGet package should only contain Release binaries:

In the pack.sln solution used to create the package there are only Release configurations:
https://github.com/mmaitre314/MediaReader/blob/master/MediaCaptureReader/Package/pack.sln
In Dependency Walker the DLL depends on the Release CRT DLLs:

For Debug binaries the CRT DLLs are vccorlib12d_app.dll, msvcp120d_app.dll, and msvcr120d_app.dll
Could you copy/paste the error logs you got?
Did you use "Add > Reference > Projects" to add the DLL?

I'm getting this error when doing the Windows App Certification Test for my Windows Phone 8.1 app:

Ah, right, I must have missed to #ifdef-out a call to that method in Release builds. Looking into it.

NuGet 2.1.4 is out with a fix. I didn't run the certification kit (it does not like my long paths...) but the method does not show up in Dependency Walker anymore.

Thanks. I've updated, but now I'm getting this message when I run the certification kit.

Ok, one more attempt. MSDN says the attribute is ignored, so I removed it. 2.1.6 is out.

Passed! Thank you so much!!!


write_image hangs

I'm using kaleido 0.2.1 with plotly 4.14.3 on Python 3.8.1 and RHEL Linux 7.9. I'm trying to run the below example notebook but the write_image() calls never return:
https://plotly.com/python/static-image-export/
I tried multiple image formats and nothing seems to work. Is this a known issue?
Thanks!

Hi @adammclaurin,  Kaleido shold be compatible with that configuration.  Does your system have SELinux running? If so, https://github.com/plotly/Kaleido/issues/37 might be helpful.
If not, try the instructions in https://github.com/plotly/Kaleido/issues/36#issuecomment-756676527 to see if we can get a little more logging info.

Thanks for the feedback @jonmmease . I confirmed that SELinux is not running.
Here's a screenshot of the backtrace that gets printed when I stop the Jupyter kernel while write_image() is hung:

And here's a screenshot of the output of the debugging command you suggested:

Any suggestions?

Huh, that logging info is all normal.
Previously, some folks had an issue with Kaleido hanging while working behind a proxy that hung kaleido's attempt to pull MathJax from a CDN. So you can try two things from (https://github.com/plotly/Kaleido/issues/36#issuecomment-766704225)

Fully disconnect any internet connection and try the export
Try disabling mathjax support according to instructions in the linked issue.

Just FYI, kaleido 0.2.1 does bundle MathJax, but plotly.py still overrides the local MathJax path to point to the CDN location. In plotly.py 5, plotly.py will let kaleido use its local offline MathJax, so this won't be an issue any more.

Thanks @jonmmease, that was exactly the issue. I'm working in a private JupyterHub environment that doesn't have direct access to the internet. Disabling MathJax as you suggested fixed the issue.
Do you have an estimate of when plotly.py 5 will be generally available?

Without committing strongly to any timeline, my hope is that plotly v5 will be available in late April/early May.

It seems that I ran into the same error, however, the proposed solution does not work. I tried the code snipped below and it remains hanging indefinitely. My setup is a Python 3.8.5 venv on Ubuntu (through WSL). Kaleido is version 0.2.1 and Plotly 4.14.3. Downgrading to kaleido 0.1.0 works.
import plotly.io as pio
pio.kaleido.scope.mathjax = None
import plotly.graph_objects as go
import json

# Figure
fig = go.Figure(
    data=[go.Bar(x=[1, 2, 3], y=[1, 3, 2])],
    layout=go.Layout(
        title=go.layout.Title(text="A Figure Specified By A Graph Object")
    )
)

# Display original figure
# fig.show()  # Works
fig.write_image("original_figure.png", format="png", engine="kaleido")  # Works

In Windows on Python 3.8 the code snippet does work. Also without setting mathjax to None.

The temporary solution I posted above did not work on another setup. Now I am wondering if the problem is actually the same. On the bottom of this post the traceback after I run a KeyboardInterrupt (when it keeps hanging). It seems to be hanging in response = self._proc.stdout.readline(), does this mean that is the same issue?
Note: I installed plotly from jonmmease's branch 'kaleido_v5_updates'. Besides that, kaleido 0.2.1 is now installed. The reference to MathJax.js is correct through this version:
>>> import plotly.io as pio
>>> scope_pio = pio.kaleido.scope
>>> scope_pio.mathjax
'file:///ScratchProject/TestPlotlyUpdateInstallV1/uenv/lib/python3.8/site-packages/kaleido/executable/etc/mathjax/MathJax.js'

(uenv) chris@Notebook:/ScratchProject/TestPlotlyUpdateInstallV1$ python export_figure.py
^CTraceback (most recent call last):
  File "export_figure.py", line 18, in <module>
    fig.write_image(file=export_path, width=1280, height=720, scale=1.0, engine="kaleido", format="png")
  File "/ScratchProject/TestPlotlyUpdateInstallV1/uenv/lib/python3.8/site-packages/plotly/basedatatypes.py", line 3806, in write_image
    return pio.write_image(self, *args, **kwargs)
  File "/ScratchProject/TestPlotlyUpdateInstallV1/uenv/lib/python3.8/site-packages/plotly/io/_kaleido.py", line 258, in write_image
    img_data = to_image(
  File "/ScratchProject/TestPlotlyUpdateInstallV1/uenv/lib/python3.8/site-packages/plotly/io/_kaleido.py", line 144, in to_image
    img_bytes = scope.transform(
  File "/ScratchProject/TestPlotlyUpdateInstallV1/uenv/lib/python3.8/site-packages/kaleido/scopes/plotly.py", line 103, in transform
    response = self._perform_transform(
  File "/ScratchProject/TestPlotlyUpdateInstallV1/uenv/lib/python3.8/site-packages/kaleido/scopes/base.py", line 297, in _perform_transform
    response = self._proc.stdout.readline()
KeyboardInterrupt

Hi @chrispijo,
Would you mind opening a new issue and copying this info over there?  My guess is that this is related to running on WSL, rather than the MathJax issue discussed in this thread.
In that new issue, could you please include the output of running the following command after using Ctrl+C to interrupt the write process:
import plotly.io as pio
scope = pio.kaleido.scope
print(scope._std_error.getvalue().decode())

Thanks!

Happy to do so.

It seems that I ran into the same error, however, the proposed solution does not work. I tried the code snipped below and it remains hanging indefinitely. My setup is a Python 3.8.5 venv on Ubuntu (through WSL). Kaleido is version 0.2.1 and Plotly 4.14.3. Downgrading to kaleido 0.1.0 works.
import plotly.io as pio
pio.kaleido.scope.mathjax = None
import plotly.graph_objects as go
import json

# Figure
fig = go.Figure(
    data=[go.Bar(x=[1, 2, 3], y=[1, 3, 2])],
    layout=go.Layout(
        title=go.layout.Title(text="A Figure Specified By A Graph Object")
    )
)

# Display original figure
# fig.show()  # Works
fig.write_image("original_figure.png", format="png", engine="kaleido")  # Works

In Windows on Python 3.8 the code snippet does work. Also without setting mathjax to None.

Thanks a lot, it is working fine for me now.

It seems that I ran into the same error, however, the proposed solution does not work. I tried the code snipped below and it remains hanging indefinitely. My setup is a Python 3.8.5 venv on Ubuntu (through WSL). Kaleido is version 0.2.1 and Plotly 4.14.3. Downgrading to kaleido 0.1.0 works.
import plotly.io as pio
pio.kaleido.scope.mathjax = None
import plotly.graph_objects as go
import json

# Figure
fig = go.Figure(
    data=[go.Bar(x=[1, 2, 3], y=[1, 3, 2])],
    layout=go.Layout(
        title=go.layout.Title(text="A Figure Specified By A Graph Object")
    )
)

# Display original figure
# fig.show()  # Works
fig.write_image("original_figure.png", format="png", engine="kaleido")  # Works

In Windows on Python 3.8 the code snippet does work. Also without setting mathjax to None.

I have the same questions

Downgrading kaleido also worked for me, although 0.1.0 caused a different error, so I had to use 0.0.3

Thanks for your interest in Kaleido. We are currently working on an overhaul that might address your issue - we hope to have news in a few weeks and will post an update then. Thanks - @gvwilson


Adding section based ring generator

Added a class to generate ring resonators based on specifying different sections with a certain angular extent. This should be useful for interleaved junction rings or in general any ring with a non-standard junction design.

@simbilod check it out, might be useful

Nice!
I would just change the logic to place the bus at the end to consider the position of the ring and bus waveguiding layers instead of component.
A lot of the more fun cross_sections have big offset that throw off the component coordinates:

With my fix it gets the gap right:

I'm having issues pushing to this PR because I don't seem to have write access to the main branches of this or your repo, but here is the code you can change to do what I show:
`

Rotate so that the first section is centered at the add bus
if init_cross_section is not None:
    ring = ring.rotate(
        -init_angle / 2
    )  # also change the component for later bound extraction
    r.rotate(-init_angle / 2)
else:
    ring = ring.rotate(-cross_sections_angles[0] / 2)
    r.rotate(-cross_sections_angles[0] / 2)

# Add bus waveguides

# Figure out main waveguiding layer of the ring at the ring-bus interface
input_xs_layer = (
    gf.get_cross_section(init_cross_section).layer
    if init_cross_section
    else gf.get_cross_section(cross_sections[cross_sections_sequence[0]]).layer
)
ring_guide = ring.extract([input_xs_layer])

print(ring_guide.ymin)

# Add bus waveguides
s = straight(length=ring.xsize, cross_section=bus_cross_section)

# Figure out main waveguiding layer of the bus at the ring-bus interface
input_xs_width = gf.get_cross_section(bus_cross_section).width

s_add = c << s
s_add.x = r.x
s_add.ymax = ring_guide.ymin - gap + s.ysize / 2 - input_xs_width / 2

if add_drop:
    s_drop = c << s
    s_drop.x = r.x
    s_drop.ymin = ring_guide.ymax + gap - s.ysize / 2 + input_xs_width / 2

return c

`

Made a new commit with your code. Thanks @simbilod, this definitely makes it better!

Thank you Simon and Marc,
I also add you directly to the repo with write access, so you can now push directly to the PRs and branches
I will merge it and release a new version


Define type for variable settings

Defined type "map" for variable "settings". This change adds compatibility for TF 1.0+ and resolves this issue:
helm_release.cloudwatch_logs[0]: Modifying... [id=aws-for-fluent-bit]
╷
│ Error: ---> error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go value of type map[string]interface {} "{\"cloudWatch.logRetentionDays\":7}"

Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING.md doc.
[x] I have added necessary documentation (if appropriate).
[x] Any dependent changes have been merged and published in downstream modules.

Any update on this?

@caiovfernandes @adenot @mosampaio ^

@maiconrocha @caiovfernandes ^

(I also need to update the versions.tf file to have aws        = ">= 3.13, < 5.0" in order for this to work. At least it works for me for the looks of it I don't know if there are any other issues)