Improve generic subclass support

Change Summary

Add parameterised subclasses to __bases__ when constructing new parameterised classes, so that A <: B => A[int] <: B[int].
This helps to facilitate a use case based on abstract classes, and leads to less unexpected behaviour when comparing between concrete versions of classes.
Related issue number

fix #2007
Checklist

[x] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

test fastAPI is failling with:
ImportError: cannot import name 'RowProxy' from 'sqlalchemy.engine.result' (/opt/hostedtoolcache/Python/3.7.10/x64/lib/python3.7/site-packages/sqlalchemy/engine/result.py
As far as I can tell that's not anything I could've incidentally broken.  I'm not sure what the best way to proceed with it would be?

@diabolo-dan Don't worry you can have a rest for the CI! ;)
It's due to fastapi tests that uses databases without pinning sqlalchemy dependency.
I already submitted a fix https://github.com/encode/databases/pull/299 for that

I notice that there was significant generic implementation done by @dmontagu , including the line:
    assert concrete_model.__name__ == 'Model[int, BT][str]'

Which is I believe the only concrete claim about the behaviour of reapplication of partially parameterised generic models. (namely extending from the former).
This behaviour adds complexity to establishing parameterised bases, and makes for less  (because a concrete type could be constructed through arbitrary many type variables).  I also think it's less intuitive than always building from the base, (so that Model[int, BT][str] is Model[int, str]).  The alternative isn't perfect, because there's still the issue of checking issubclass(Model[int, BT][str], Model[int, AT]) which for various assumptions on the TypeVars, should ideally hold, but I don't think it's possible to achieve that (at least through setting __bases__).
I'm just wondering if there was a particular reason for implementing it this way, or if it was just the simplest thing that met the requirements at the time.

please update.

please review.

great, thank you.

Just a note for anyone watching this PR, this changes here I think have caused a memory build up, see #3829.
To mitigate this, I've implemented (and will soon merge) #4083 which limits the size of _generic_types_cache and _assigned_parameters_limit to 1000. These configured by settings generics._generic_types_cache_limit and generics._assigned_parameters_limit.
Feedback on the PR welcome, but in order to include this fix in v1.9.1 I won't being waiting for feedback before merging - any further changes would need to be in another PR.


Unable to query feature by state

Hello, thanks for developing this node library, right now I am using it for query features for our project management, but I can't query feature by a specific state:
restApi.query({
    type : 'portfolioitem/feature',
    fetch : ['FormattedID','ObjectID','State','Owner','Release','Name'],
    start : 1,
    limit : 200,
    query : queryUtils.where('State', '!=', 'Done'),
    scope : {
        workspace : "/workspace/...",
        project : "/project/...",
        up : false,
        down : true
    },
    requestOptions : {}
}).then(function (result) {}).fail(function(error){});

I tried other query condition like 'Name', 'LeafStoryCount', they all work, except State, it might not be a issue, but do you know what is the correct way of querying by feature state? thanks a lot!

I found the solution, the query should be
queryUtils.where('State.Name', '!=', 'Done'),

Cool, glad you figured it out!


Add multipart configuration options to servlet extension

Latest commit should address review feedback.

Setting the PR to draft as there's an odd issue happening on GitHub CI that I cannot replicate locally. Needs more investigation.

Issues are hopefully resolved now. Turns out I cannot count properly. I had set the byte limit in the config props to less than what I was sending in the valid test scenarios.

To move this along I opened https://github.com/apache/camel-quarkus/issues/5830 to follow up on later.


github-terms-of-service: Reference-style links for privacy statement

1. What's the name of the policy?
GitHub Terms of Service
2. Is this issue related to a specific section within one of our policies (e.g. the Terms of Service)? If so, please include a link to the section or subsection.
No
3. Did you already open a pull request? If so, please include a link to the PR.
This is the pull request ;).
4. Sometimes it's easier to just put your feedback text into an issue. If that's how you'd prefer to contribute, this is the section to do that.
Reference-style links make the source a bit easier to read, since the inline label is shorter than the referenced URL.
And the one-off link to the privacy statement's compelled disclosure section currently goes straight to /articles/github-privacy-statement/, while the other privacy links in these terms go to the redirecting https://github.com/site/privacy:
$ curl -sI https://github.com/site/privacy
HTTP/1.1 302 Found
Date: Sun, 06 Aug 2017 04:41:03 GMT
…
Location: https://help.github.com/articles/github-privacy-statement/
…

It seems more consistent to use the canonical link there instead of linking directly to the /articles/ URL.
5. Why do you think this section or language needs improvement?
This PR isn't changing any of the legal language; it's just minor Markdown polishing.

Thank you all for the comments and feedback! @wking Closing this pull request since we haven't made changes to the links in this update.


Set up web analytics Kibana over data coming from Logstash

[ ] Provision a new Kibana instance with the essential settings for web analytics
[ ] Add it into the general project orchestration

@Steven-Eardley tagging you into this one for the final project orchestration #40


Adding port 8443 to port list

I am trying to get Archiva to run with ssl. I have a working stand alone Archive running but thcontinerized version if blocking port 8443. It looks like the docker-compose.yaml is missing a definition for this port. I can share the wrapper.conf, jetty.conf, and jetty-ssl.conf files with you in return for help on this issue.

:wave: @wiscwork - Welcome! A few things on this issue.

The docker-compose.yaml included in this project is for building, testing, and demonstration. You'll want to write your own if you are hosting things yourself in a docker server (and there is a not-really-maintained helm chart if you are running in k8s)
It is not recommended to provide TLS through Jetty and it's not something we provide examples of. There is a helpful example in this project of using nginx to provide TLS, which is a much less painful path.


Fix narrowing by typeof applied to discriminant property

Fixes #51700.

Tests and perf look good. Merging now.


QM square well example added to the fast_fourier.ipynb

Solving the Schrodinger equation for a finite square well potential can be done using Fourier transform. A small piece of code is added at the bottom to the notebook. The plotting of output can be improved.

Awesome! Very nice


custom_error_response when empty list

Description
Terraform produce an error when dealing with empty list on var.custom_error_response because of the way this module evaluate the variable. Because we use cloudfront in a module with validations, we can't have unmatched variables type

[ x ] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Module version [Required]:

3.2.1

Terraform version:

Terraform v1.6.3
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v5.24.0

Provider version(s):

Terraform v1.6.3
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v5.24.0

Reproduction Code [Required]
provider "aws" {}

variable "custom_error_response" {
  description = "Create one or multiples custom error response"
  type        = list(object({
    error_code            = number,
    response_code         = optional(number),
    response_page_path    = optional(string),
    error_caching_min_ttl = number
  }))
  default = []
}

module "cdn" {
  source = "terraform-aws-modules/cloudfront/aws"
  version = "3.2.1"

  enabled               = true
  default_root_object   = "/index.html"
  wait_for_deployment   = false
  custom_error_response = var.custom_error_response

  origin = {
    test = {
      domain_name = "foo.com"
      origin_id   = "test"
      custom_origin_config = {
        http_port              = 80
        https_port             = 443
        origin_protocol_policy = "match-viewer"
        origin_ssl_protocols   = ["TLSv1", "TLSv1.1", "TLSv1.2"]
      }
    }
  }
  default_cache_behavior = {
    target_origin_id       = "test"
    viewer_protocol_policy = "allow-all"
  }
}

Steps to reproduce the behavior:
Simply run terraform apply.
Expected behavior
No errors
Actual behavior
│ Error: Invalid index
│
│   on .terraform/modules/cdn/main.tf line 261, in resource "aws_cloudfront_distribution" "this":
│  261:     for_each = length(flatten([var.custom_error_response])[0]) > 0 ? flatten([var.custom_error_response]) : []
│     ├────────────────
│     │ var.custom_error_response is empty list of object
│
│ The given key does not identify an element in this collection value: the collection has no elements.

Additional context
I tried by removing changing for_each = length(flatten([var.custom_error_response])[0]) > 0 ? flatten([var.custom_error_response]) : [] to for_each = length(flatten([var.custom_error_response])) > 0 ? flatten([var.custom_error_response]) : [], and everything is working well.
I can make PR to fix

seeing same issue. thanks for the PR ...

Here is a way to make it works until it's fixed.
In case you don't want a custom_error_response, you can set [{}] as default value.

Here is a way to make it works until it's fixed. In case you don't want a custom_error_response, you can set [{}] as default value.

thanks.
i did a plan and it seems fine. but we have it pinned for now until the fix.


Moving to first slide on setState

Which OS ?
iOS
Version
Which versions are you using:

react-native-swiper v1.5.13
react-native v0.55.4

I use the swiper for card based forms that you swipe between fields. These fields are dynamically created from the server then mapped in to place using two for loops to lay them out.
Expected behaviour
If I enter in a text field on the first slide, move over to the last slide when I choose an option from the select input using:  "react-native-select-input-ios": "^1.2.0", upon changing the option I then update the state at which point the slide should stay on the exact same slide.
Actual behaviour
When I enter in text on the first slide, move over to the last slide and select an option it moves to the first slide but the pagination dot still has the last slide highlighted. If I then begin to enter in to any of the text fields on the first slide, it then moves back to the last slide and repeats the above. If I enter in last slide, it goes to first when I save the state, if I enter in the first slide, it goes to the last slide when saving the state.
I've used  console.log to check this.state.slide which is the given index of the slide in my case and it's comes out expected as normal.
I will create an snack.io to reproduce the issue when I've got a little more time, but here's the code I'm currently running.
Steps to reproduce

Enter into text field on first slide
Move to another Slide
Enter in to another text/field and update the state.

This issue is solved by this pull request as I've modified the file locally and it's gone away! Please merge.


[WorksForYou] Started on new container

[x] Visuals for new WFU container
[x] Notification component
[x] Relay integration
[x] Empty state

The metaphysics response doesn't include the artist image for the avatar, so I'm going to get this tested and ready to merge without it and then get that set up in metaphysics. Also, tests are failing on this branch that I believe are fixed in the main typescript branch, so I will write tests for this as soon as it's merged.

You should add this to the storybooks too 👍

Fails

:no_entry_sign:
No CHANGELOG added.

:no_entry_sign:
Please assign someone to merge this PR, and optionally include people who should review.

  Generated by :no_entry_sign: dangerJS

Ready for review, but I could use some help deciphering the travis failure.

Alright, this looks good on iPhone and iPad! Ready for review if CI passes.

Alright, there's a small bit of work I have to do to get this mergeable. Stay tuned.

Tests are 🍏 ! Ready for review, finally.

Looks good, but no tests (no storybooks) - there's not too much logic in here, so it shouldn't be hard to cover comprehensively

realistically Danger should saying something like this too ^

I agree with @orta that there should be some tests.

I was going to do tests in a new PR since there's a lot more work to be done on this view anyway, but I can add some preliminary ones here. It doesn't make a difference to me.

Cool, then let’s do it here now and start getting into the habit that PRs should be accompanied by tests.

@alloy tests are done

I've started on an artist avatar branch which contains tests for the Notification component

Ace!


Chore: Add additional catalog package.json

Description
Nx will not help to create package.json & README.md in the source of the Next.js package by default,
so the Catalog server needs to add package.json to provide name & version and add README.md for release.
Additional Context

remove default project setting

Codecov Report
Patch and project coverage have no change.

Comparison is base (59b152c) 91.06% compared to head (4abf5b9) 91.06%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #184   +/-   ##
========================================
  Coverage    91.06%   91.06%
========================================
  Files          328      328
  Lines         5393     5393
  Branches       716      716
========================================
  Hits          4911     4911
  Misses         343      343
  Partials       139      139

Flag
Coverage Δ

catalog-server
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


PMID:26776736

decreased number of cells with 1C DNA content

decreased number of cells with 1C DNA content FYPO:0005456
edit file: a928e345fb59b32c28d133e2ea37ed1779a4d8d5
release: 96ebac8c2152a2fe15b9bdc0f73147c9b64d4f36


Failing when update elastic-apm-node

npm_and_yarn
Parsing dependencies information
    Updating elastic-apm-node (from 2.17.3)…Traceback (most recent call last):
        25: from dependabot_orig.rb:85:in `<main>'
        24: from dependabot_orig.rb:85:in `each'
        23: from dependabot_orig.rb:123:in `block in <main>'
        22: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:39:in `updated_dependency_files'
        21: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `updated_lockfiles'
        20: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `each'
        19: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:149:in `block in updated_lockfiles'
        18: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:120:in `package_lock_changed?'
        17: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:187:in `updated_package_lock_content'
        16: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:30:in `updated_lockfile_content'
        15: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:57:in `in_a_temporary_directory'
        14: from /usr/lib/ruby/2.6.0/tmpdir.rb:93:in `mktmpdir'
        13: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:60:in `block in in_a_temporary_directory'
        12: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:60:in `chdir'
        11: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:60:in `block (2 levels) in in_a_temporary_directory'
        10: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:34:in `block in updated_lockfile_content'
         9: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:34:in `chdir'
         8: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:35:in `block (2 levels) in updated_lockfile_content'
         7: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:115:in `run_current_npm_update'
         6: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:137:in `run_npm_updater'
         5: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:170:in `with_git_configured'
         4: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:139:in `block in run_npm_updater'
         3: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:151:in `run_npm_top_level_updater'
         2: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:123:in `run_helper_subprocess'
         1: from /usr/lib/ruby/2.6.0/json/common.rb:156:in `parse'
/usr/lib/ruby/2.6.0/json/common.rb:156:in `parse': 767: unexpected token at '' (JSON::ParserError)
        24: from dependabot_orig.rb:85:in `<main>'
        23: from dependabot_orig.rb:85:in `each'
        22: from dependabot_orig.rb:123:in `block in <main>'
        21: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:39:in `updated_dependency_files'
        20: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `updated_lockfiles'
        19: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `each'
        18: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:149:in `block in updated_lockfiles'
        17: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:120:in `package_lock_changed?'
        16: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:187:in `updated_package_lock_content'
        15: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:30:in `updated_lockfile_content'
        14: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:57:in `in_a_temporary_directory'
        13: from /usr/lib/ruby/2.6.0/tmpdir.rb:93:in `mktmpdir'
        12: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:60:in `block in in_a_temporary_directory'
        11: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:60:in `chdir'
        10: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:60:in `block (2 levels) in in_a_temporary_directory'
         9: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:34:in `block in updated_lockfile_content'
         8: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:34:in `chdir'
         7: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:35:in `block (2 levels) in updated_lockfile_content'
         6: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:115:in `run_current_npm_update'
         5: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:137:in `run_npm_updater'
         4: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:170:in `with_git_configured'
         3: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:139:in `block in run_npm_updater'
         2: from /aea-dependabot/npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:151:in `run_npm_top_level_updater'
         1: from /aea-dependabot/common/lib/dependabot/shared_helpers.rb:87:in `run_helper_subprocess'
/aea-dependabot/common/lib/dependabot/shared_helpers.rb:133:in `rescue in run_helper_subprocess': Dependabot::SharedHelpers::HelperSubprocessFailed

Sorry for the slow response time, we've been very focused on a number of internal infrastructure changes and only now starting to catchup on issues.
Looking at this traceback, it doesn't provide enough info to debug further without knowing the manifest file that generated this in the first place. It looks like it calls out npm and that returned an empty response instead of what we expected...
Given that this is over a year old, I'm guessing that either this issue was already fixed or you no longer have the original file that was causing problems, so I'm going to close this. If you're still experiencing the problem with the current dependabot, then post here including a copy of the manifest file and I can re-open.


#4 Members clock diff

#4 Add information about clock difference between members

@rosik Why anti-entrypy shouldn't send time delta? It looks fine.

Because it's local parameter - time difference between my clock and yours. An a third person has nothing to do with this information.

We can then use the difference between our clock and the third person's clock to adjust the offsets in their table. This will help propagate time drifts faster and more reliably.

Anyway, I suggest there should be a "generation" counter in time drifts anyway, because otherwise it's impossible to know in which direction to adjust offsets in our table.

Well, I think there is a way to to it. But can we proceed in a separate PR?

send_anti_entropy
As I can understand, send_anti_entropy use members.pack to add member information, which is not affected by this PR

send_anti_entropy
As I can understand, send_anti_entropy use members.pack to add member information, which is not affected by this PR

You're right, I didn't notice that


fix version navigation in release v1.9

In release v1.9, navigating to version v1.10 disappears
modified _config.yml in branch release-1.9
Issue: #8967

/assign @zacharysarah

@zacharysarah
I re-raised a fresh PR.
Closed PR : #8968

@zacharysarah is anything else to be added/modiy?

Interesting--Travis started to fail when I updated the 1.10 section to point correctly to release-1.10.
FAIL	k8s.io/website/test [build failed]
The command "go test -v k8s.io/website/test" exited with 2.
2.03s$ ./verify-docs-format.sh
The command "./verify-docs-format.sh" exited with 0.

I suspect it may be because release-1.10 is Hugo-based and doesn't verify with a Jekyll-based build. If that's the case, there's no easy fix to Jekyll-based (>=1.9) version selection, and would probably require updates to build tests and scripts.

@mistyhacks CC for visibility. Previous to Hugo, releases required separate PRs to update release-1.<X> branches with updates to the version selector. It looks like there may not be an easy way to update Jekyll-based branches to look forward.

So @zacharysarah are you suggesting, this is not the right way to correct the version selector to point correctly?

@harshvkarn Initially I wondered whether was even possible to update the version selector to point forward from pre-Hugo versions. (In other words, versions 1.9 and earlier might not be able to point to 1.10 and later.) Travis fails due to a Jekyll validation test. (Travis can't verify that 1.10 is correctly configured for Jekyll because it's not, it's configured for Hugo.)
The more I look at it though, Netlify builds correctly and acts more or less correctly, which is the most important bit here. I think we may be able to merge it--but it would have to be merged manually, and I'd want to get another set of eyes on this PR before proceeding. (We'd also need separate PRs for release-1.8 and release-1.7.
/cc @mistyhacks in reference to #9253

@zacharysarah So should I raise the PR for release-1.8 and release-1.7 for the same?

@harshvkarn Yes, please do. 👍

All right, I'm going ahead and merging these changes manually for the reasons outlined above. ☝


Password Protected Smart Folder Support

Password Protected Smart Folder Support
We have password protected folders on macOS , Linux (using Cryptkeeper or some other ways) with simpler interactions. But we do not have this feature on Windows 10. It would be very great if have this feature through PowerToys.
Proposed technical implementation details
We need to encrypt the directory/folder content using some algorithm like AES or something . Also whenever we're accessing the data it should ask for passcode for decrypting . But if you use this approach, It would look like a zip with a password. So we need to have a specific extension for the directory is will be handled in different way.

Also I would like other contributors opinions on this Feature Request and implementation

This sounds like the "vault" folder that OneDrive uses. Good idea to have the possibility for any "random" folder.

Bitlocker can encrypt the drive or Onedrive has this as well with Personal Vault
What is the use case that either of these can't do.  The nice thing with the onedrive solution as well is it roams with you

OneDrive is online solution & BitLocker is like disk utility that completely encrypt the disk images.

I just wanted a simple folder feature that will prompt me a password when I click on it

So I can call it as smart folder.

What is the use case that either of these can't do. The nice thing with the onedrive solution as well is it roams with you.

Porn? 🤭😆 Haha, kidding


DAT being Flagged as Wildfire Malware

Infosec will not let me install DAT <IP_ADDRESS> anymore. is there anyway we can get this verified

can we get new MD5 hashes

Unfortunately the issue is someone started sharing copies with a serial generator for the tool (http://insesilest.over-blog.com/2020/03/Driver-Automation-Tool-643-Crack-Serial-key-Latest-2020.html) obviously including malware. This sent AV detection's my way...
I'll post the MD5 hashes today for you.


Correct example for counter-clockwise rotation

This change should have been done a while ago, for version 2.0b1 (see #25).
Did we miss anything else?

Coverage remained the same at 100.0% when pulling a55ce424d82041f41fb77e8a4d5dede4834392e6 on mwtoews:readme into b125a6397c2a0ff4d7587a43b8678ee5f54765ed on sgillies:master.


Login page, signUp page and Github's Compiler page navbar doesnot update even if the user is logged in

Even after login:

Related commit: https://github.com/himanshu010/onlineIDE/commit/72b37a9dbaf87ede792af296f27674cdf1bf6a03


Update font-mplus-nerd-font to 2.0.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thanks for the PRs @Thammachart! 🥇


PMO - Allow people to enter their github and other accounts in the guide.

It would be really nice if I could say my github username is "justinbmeyer" and then all other places in the guide would be filled out.
I'll file this under pipe dream.

This would make for a cool bit-docs plugin.


Register the Mongo driver through the make function instead of resolving functiong

Laravel-mongodb Version: 4.1
PHP Version: 8.3
Database Driver & Version: 4

Description:
Register the Mongo driver through the make function instead of resolving functiong
If db is instantiated in another package, then the callback function registered through resolving function will not be executed, which is a hidden BUG.
This problem does not occur stably, only if a package is sorted by the composer and executes its own provider before the laravel-mongodb provider, and exactly instantiates db.
The core code is:

In my project, the following code exists in other packages, which can lead to problems. Because db is instantiated in advance：

Problems caused by，there is an error:
Unsupported driver [mongodb]. - InvalidArgumentException

Hello @zyz954489346, do you have any idea how we can fix this issue?

Hello @zyz954489346, do you have any idea how we can fix this issue?

I temporarily solved the problem by rewriting Provider, but this is really not an elegant solution.

As far as I can see, there are actually some packages that don't quite conform to the specification. This leads to problems.

I agree. The specification says to not request dependencies in register, as not all services have been registered at that point. If other tools ignore that, that's on them and should be reported (and fixed) there.

Another thing I don't understand is why you register through the resolving function instead of the make function.

The make method actually resolves a dependency, which isn't what we need. We need to call the extend method on the DatabaseManager service to inject a custom extension for the mongodb database driver. We can't use the extend method of the service container for this, but instead need to inject this when the db service is resolved. The only way to achieve this is by using resolving.
Like I said: if tools break because do what a bolded sentence in the docs tells them not to do, that's not on us, that's on them. I'm closing this as won't fix.

i  hit the same problem until i close the laravel-sql-logger package, thx


hiersumm

Hi, as for hiersumm, how did you prepare your data, did you use his sentencepiece model, how did you encode your text, I noticed he didn't release the code for preparing data. Thanks in advance.
Also for evaluation, do you think which one is better, replace cite_2 with @cite or just remove cite_2.

I use their sentencepiece model for the encoding. You can mimic their format, it is not difficult to do so. You can take a look at this https://github.com/google/sentencepiece about how to use it.
For evaluation, just replace @cite_2 with @cite.

Hi, I refer to sentencepiece, and use the sentencepiece model as he released in hiersumm. But when I try to find his preprocess process in MultiWiki dataset, I find it works when I try to convert 'tgt_str' to 'tgt' with "spm.DecodeIds(example['tgt']).split(' ')". But I fails when I try to convert 'tgt_str' to 'tgt', it's quite different.( with spm.encode(example['tgt_str']) or spm.EncodeAsIds(example['tgt_str'])).
Also I fint I can't convert back by spm.DecodeIds(spm.EncodeAsIds(example['tgt_str'])).split()
I wonder how did you preprocess by sentencepiece, or maybe I have to give up his sentencepiece model or try another tokenizer

Not sure if I understand your question. Here is my code snippet for the tgt_str to tgt transformation.
SOS = "<S>"
EOS = "</S>"
QOS = "<Q> "

tokenizer = load_tokenizer('spm9998_3.model')

def get_tgt(tgt_text_list: list, tokenizer):
    tgt_text_list = [' '.join(word_tokenize(tgt_text)) for tgt_text in tgt_text_list]
    tgt_str = SOS + " " + QOS.join(tgt_text_list) + EOS
    tgt = tokenizer.encode_as_ids(tgt_str)
    return tgt, tgt_str

Thanks so much for your reply.
I try to encode by this:
spm = sentencepiece.SentencePieceProcessor(model_file=vocab_path)
word_padding_idx = spm.PieceToId('<PAD>')
symbols = {'BOS': spm.PieceToId('<S>'), 'EOS': spm.PieceToId('</S>'), 'PAD': word_padding_idx,
    'EOT': spm.PieceToId('<T>'), 'EOP': spm.PieceToId('<P>'), 'EOQ': spm.PieceToId('<Q>')}
print(spm.EncodeAsIds(example['tgt_str']))
print(spm.decode(spm.encode(example['tgt_str'])))    #I find this is quite different from tgt_str

I will try your code, by the means, what is load_tokenizer as I can't find this in sentencepiece. Is word_tokenize from nltk?

Try this.
import sentencepiece as spm

def load_tokenizer(spm_model_path):
    tokenizer = spm.SentencePieceProcessor()
    tokenizer.load(spm_model_path)
    return tokenizer

Hi I try your code in dataset wiki in hiersumm, I meet the same problem as I meet with my own code. Can you decode back by tokenizer.decode(tgt) to tgt_str?
In wiki dataset, I can decode tgt in dataset back to tgt_str
But I can't get back by first encode tgt_str then decode.
Here is my result:
example['tgt_str']:
"`` The Essential Marcia Hines '' is a compilation album released on 30 July 2007 by Australian singer Marcia Hines .   It was released following Hines ' induction into the ARIA Hall of Fame on 18 July 2007 .   The album contains five top 10 singles taken from the albums , Marcia Shines , Shining , Ladies and Gentlemen and Ooh Child ."
decode frm example['tgt']:
" `` the essential marcia hines '' is a compilation album released on 30 july 2007 by australian singer marcia hines . it was released following hines ' induction into the aria hall of fame on 18 july 2007 . the album contains five top 10 singles taken from the albums , marcia shines , shining , ladies and gentlemen and ooh child ."
first encode then decode:
" The  ⁇ ssential Marcia  ⁇ ines is a compilation album released on 30  ⁇ uly 2007 by  ⁇ ustralian singer Marcia  ⁇ ines . ⁇ t was released following  ⁇ ines ' induction into the  ⁇   ⁇ all of  ⁇ ame on 18  ⁇ uly 2007 .The album contains five top 10 singles taken from the albums , Marcia  ⁇ hines ,  ⁇ hining ,  ⁇ adies and  ⁇ entlemen and  ⁇ oh  ⁇ hild ."

Hi, I did not try to run hiersumm's wikisum dataset. In Multi-XScience project, the system decoding output looks good.

Hi, you mean you can decode back from your encoded tokens by spm9998_3.model?
My main problem is first encode then decode is quite different from initial str

Yes, I can confirm that. I preprocess and convert multi-xscience dataset into the *.pt format required by hiersumm using spm9998_3.model. Then use the same command as hiersumm for training and decoding. The output is normal.
If you want to work on multi-xscience, I can provide you with the preprocessed *.pt file. If you want to work on hiersumm+wikisum, maybe you should ask hiersumm author about wikisum issue?

Feel free to reopen.

Hi @yaolu I'm facing a similar problem. I first used the spm9998_3.model provided by the hierrsum author. In a lot of places the decoded output had '??'. It wasn't recognising the symbols. These are some of the symbols where the error occurred
{^, ≥ ≤ © & ≃ ⨁ θ ’ – “ ” = }  — Δ ∞ → ∈ ± °}. I passed these as user_defined_symbols while running spm.train() on your dataset. Could you provide me with a link of the .pt files of your dataset that you used to run hierrsum? Thanks.


[issue] Uncaught TypeError: workflows.workflows is not iterable

Description
Installed as usual according to the instructions: git clone https://github.com/pythongosssss/ComfyUI-Custom-Scripts.git

Windows 10 21H2
Python 3.11.0

Problems

⚙ settings won't open after installing custom-scripts:

can't use "Save to workflows" option in Save:

custom nodes are missing:

I've tried updating comfyui, its dependencies and node itself, but no result;
I've tried reinstalling comfyui (both standalone and regular), no result;
I've tried reinstalling custom-scripts, still no result.

I suspect the node fails to download the rest of the files, as the node folder takes less than 1 MB:

Do you have an error in the ComfyUI console window when you start up? Looks like the route arent being added to the server correctly

Do you have an error in the ComfyUI console window when you start up? Looks like the route arent being added to the server correctly

I checked the logs and found nothing. The problem still persists. Any suggestions, please?
comfyui.log

I would recommend using the new beta menu & workflow management in ComfyUI. This feature has been deprecated by the comfyui core feature.


How to read docx in turn ( eg: paragraph, table, table; paragraph, table )

How to read docx in turn ( eg: paragraph, table, table; paragraph, table )
read in turn ,because paragraph is ralated to table which is under its paragraph...
eg:
paragraph 1
table 1
table 2
paragraph 2
table 3
as:
below is a group data
paragraph 1
table 1
table 2
...
paragraph 2
table 3

Duplicate of #40


adds support & api for pump and valve actuators

I am not that clear what are the physical actuators exactly but it works, when you turn both on it grabs things xD

It gets a little problematic when trying to actually use it as I just realized, since these are executed immediately instead of being queued it does not work that well ^^

yes, I realized that after having implemented laser control. that required slightly different command representation in firmware and slightly different handling + make sure that everything still fits in the allowed time frame to not miss to send next byte via SPI to the FPGA.
That said, let's still consider merging this (after we decide whether we want two commands or just one for the pump) and improve later. Incremental improvements.
FYI, you can still use time.sleep() to delay execution of this command, though it would be horribly inconvenient and a dirty workaround.

The ideal would be to have all the commands queued but I haven't looked at your code too deep so I can't comment on this, the problem is that you need to enable the pump at a precise point otherwise there is not much use to it and it will be the same problem with the claw.

There will be no problem with the gripper as it will be a part of movement command that is sent to FPGA. FPGA is in charge of PWM pins on the top board that controls the gripper.
The pump will be fixed by extending the command structure in the firmware and being appropriately queued along with the movement commands.
Please create a separate issue to fix laser/pump commands (after this PR is merged) and I'll plan it for the upcoming release.

Merged as I got some time to make them queued.
Please create another PR to add description to those commands. Thanks.

Queueing implemented. See #14

great :)


Refactor terminal reporter

Description
This is a substantial change to the reporters framework. It:

Ensures all reporters take the same arguments.
Moves some common code into the base class.
Merges the "ProgressReporter" and "TerminalReporter" subclasses into the same class.
Makes heavy use of the rich library for text formatting, simplifying the layout.
Improves the progress bar by making it a separate rich renderable, kept as a "live display" at the bottom of the terminal.
Splits the rendering of events into one method per event type.
Makes the --succinct flag truly succinct, just showing checks, arguments and their status codes on a single line.
Removes some unused methods.

Probably does some other things too. :-)
Checklist

[x] update CHANGELOG.md
[x] wait for the tests to pass
[x] request a review

@felipesanches I have more (separate) changes which I'd like to make, but if I do, they will start to conflict with this one. Can I suggest you review this in terms of what you think about it in principle, and we deal with any small formatting nits in the output etc. later? Alternately, we could merge it to a dev branch or similar, so I can work on the other things there as well and then merge it all when we think it is production-ready.

FB stops when an ERROR is raised. I personally preferred ERRORs to be caught and the program continues executing.

I don't think (from your error message, in particular the bit that's just at the bottom of the screen) that's related to this change. When certain dependencies are not installed, you get an immediate exit with installation instructions, e.g.
    try:
        import axisregistry
    except ImportError:
        exit_with_install_instructions()

Padding has been removed for each check result. Formatting imo was better before.

I agree this is bad. rich has the ability to format Markdown, but I can't see a sensible way to left-pad the output of a rich renderable.

I don't think (from your error message, in particular the bit that's just at the bottom of the screen) that's related to this change. When certain dependencies are not installed, you get an immediate exit with installation instructions

Currently, it will carry on if dependencies are missing. However, I don't mind it aborting if deps are missing.

The major thing that I noticed was that content stopped being limited to a box of a certain fixed-width. I understand that we may want to let the width match the user's terminal window width, and it seems to be what this PR does. But this is not filling a rectangular area with a background color. The background color is only being used on the printed strings, but not on the remainder of space that was supposed to be part of the rectangular area.

When certain dependencies are not installed, you get an immediate exit with installation instructions

I think it is better to emit the install instructions in an ERROR message when a dep is missing, but still let the other checks provide useful results if they do not need the missing dependency.

Scratch that, main branch does the same.
Yeah. That's fine. Let's move on then.

OK. This is looking good enough:

But, as @m4rc1e mentioned, it would be better to have the block indentations. And I would add some vertical space between "more info" and the first log message (WARN in this case).

@simoncozens, I'm happy to merge this to main now and then fine tune the last few formatting details later.

Thank you!


replace chrono with newer time

This is to avoid a potential security issue:
https://rustsec.org/advisories/RUSTSEC-2020-0071 AKA CVE-2020-26235

Ah I missed that time was already removed in https://github.com/slog-rs/term/pull/37 , this just needs a new release.

Also can you please push the missing tags since 2.5.0?

It's still useful to remove chrono as a dependency, so that cargo audit does not flag this crate under RUSTSEC-2020-0159. What needs to happen for this to merge and release?

Does release 2.8.1 addresses your problem with chrono sufficiently? I would think 79bfa8cf17d8f99600e9e7370d5b7f0d30f554bf addresses the security concerns 😉
Besides this specific security issue (which is now fixed), are there any other advantages in switching from chrono to time?

2.8.1 does avoid https://rustsec.org/advisories/RUSTSEC-2020-0071 . But from my quick peek there is no version of chrono available that has https://rustsec.org/advisories/RUSTSEC-2020-0159  fixed and there is no useful feature set of chrono that avoids both. Switching to time does avoid both. An alternative would be to fix the chrono issue, but that is not a quick thing for me. A downside of this PR might be that it uses time 0.2.x while it is already at 0.3.7, but finding the same functionality in the newer version of time was also not quick.

Blegh. Sounds like chrono is not well maintained right now 😦
I guess this probably should be a priority for us.

Interestingly enough, when using time = "0.3" the average binary sizes of the examples actually decrease compared to the latest master.
Binary sizes with time: 0.3: 798KB
Binary sizes with master (using chrono): 816KB

Okay. I updated to time 0.3 and fixed the exception.
Before this upgrade, cargo run --example "full" threw an exception for me.

thread '' panicked at 'Invalid specifier .', /Users/techcable/.cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.27/src/format/parse_items.rs:11:21

@JanZerebecki let me know what you think about the upgrade to slog 0.3 and the new format specifier.


BUG Enables downloads for sdist

Fixes https://github.com/ogrisel/wheelhouse-uploader/issues/35

@ogrisel In the near feature we are going to have travis build ARM, which means we will still need to use a temporary location to store the wheels.
At this point, I am thinking of using https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/ to have a button we can push to "download wheels/sdist from anaconda and upload the to pypi".

Thanks @thomasjpfan ! Indeed it would be great to have a workflow trigger to fetch all artifacts.


Add test of REST API in a test_api.py file.

Basically just run the client fixture, do a get request, and assert that the inputs and outputs are what you expect them to be.

test_model_output_api_schema() should test that the keys are a particular way and the values are of a particular type.
test_model_output_api_parameters() should test that hours=10 returns 10 rows of data, that setting the reach returns only that reach.

The test func names are long to accommodate the name-space when we additional APIs we'll add to this file, and we'll be testing their parameters and schemas as well.

I'll take a look at this.

First pass on this issue here: https://github.com/codeforboston/flagging/compare/dev2...dfe325:dev2
Tests don't work as of yet, need to do some fiddling but just wanted to make sure I'm on the right track. Have to step away now but will be working on this later today. Thx

Good job so far.
Re the first one: Right idea, but I'd do it more explicitly like this:
schema = {
    'some_key': str,
    'some_other_key': list
}

res = some_api_function()
for key, val in res.items():
    assert key in schema
    assert isinstance(val, schema[key])

This is a far less cryptic way to present the problem because you can see every single thing that's being tested against with your own two eyes; it doesn't hide anything.
In Python, assert type(obj) == some_type is less preferable compared to isinstance(obj, some_type) in the majority of contexts. isinstance takes into account inheritance, and in Python a subclassed object is considered to be OK. (That's what the whole duck-typing thing is about.)
Small note: Docstrings use triple-double quotes, not triple-single quotes. https://github.com/codeforboston/flagging/wiki/Code-Style-Guide#1-use-pep-8 As per the Google Style Guide however, we still use 3x double quotes for docstrings.
Re: the second one:
The point of this sort of test is to test that the input-output relationship is what we think it should be. Right now you have no inputs, though.
Also, I prefer len(df) to df.shape[0] because it looks more like normal python so it should be easier for people to read.

Ok, took a second pass.

Docstrings to 3 “s
df.shape[0] changed to len(df)

This currently doesn't pass one of the tests, it returns a string when it should return a list. I tweaked the code you gave to parse what looks to be a pretty complicated dictionary/dictionary of lists coming out of the get request... not sure if  model_api() is the right way to go, which might explain it.

Update: Got the last test to work but it's super ugly. Will be working on refactoring tonight.

This is still open because test_api.py doesn't work.

Done!


Problems compiling

Hi,
I was trying to compile the project in order to generate the zip file. Everything was going fine, but then I started to experience issues. This is part of the resulting log:

Getting org.scala-sbt sbt 0.13.2 ...
:: problems summary ::
:::: WARNINGS
module not found: org.scala-sbt#sbt;0.13.2
==== local: tried
/root/.ivy2/local/org.scala-sbt/sbt/0.13.2/ivys/ivy.xml

-- artifact org.scala-sbt#sbt;0.13.2!sbt.jar:

/root/.ivy2/local/org.scala-sbt/sbt/0.13.2/jars/sbt.jar

==== activator-launcher-local: tried
file:/root/typesafe-activator-1.3.12/activator-dist-1.3.12/repository/org.scala-sbt/sbt/0.13.2/ivys/ivy.xml

==== Maven Central: tried
https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.pom

-- artifact org.scala-sbt#sbt;0.13.2!sbt.jar:

https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.jar

==== typesafe-releases: tried
https://repo.typesafe.com/typesafe/releases/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.pom

-- artifact org.scala-sbt#sbt;0.13.2!sbt.jar:

https://repo.typesafe.com/typesafe/releases/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.jar

==== typesafe-ivy-releasez: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13.2/ivys/ivy.xml

  ::::::::::::::::::::::::::::::::::::::::::::::

  ::          UNRESOLVED DEPENDENCIES         ::

  ::::::::::::::::::::::::::::::::::::::::::::::

  :: org.scala-sbt#sbt;0.13.2: not found

  ::::::::::::::::::::::::::::::::::::::::::::::

:::: ERRORS
Server access Error: No existe ninguna ruta hasta el `host' url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.pom
Server access Error: Expiró el tiempo de conexión url=https://repo1.maven.org/maven2/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.jar
Server access Error: No existe ninguna ruta hasta el `host' url=https://repo.typesafe.com/typesafe/releases/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.pom
Server access Error: No existe ninguna ruta hasta el `host' url=https://repo.typesafe.com/typesafe/releases/org/scala-sbt/sbt/0.13.2/sbt-0.13.2.jar
Server access Error: No existe ninguna ruta hasta el `host' url=https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt/0.13.2/ivys/ivy.xml

I was quite puzzled about this. I checked the path  /root/.ivy2/local/org.scala-sbt/sbt/0.13.2, but first of all,
/root/.ivy2/local does not exist, it is /root/.ivy2/cache. And second, in /root/.ivy2/cache/org.scala-sbt/sbt I find some versions, but 0.13.2 is not one of them.
In addition, I checked the repos from these urls, and the problem is quite obvious. If you check it out, you'll notice that version 0.13.2 is missing. It doesn't exist. So my question is: Where can I change this path? I cannot find the config file, or the code where it is hardcoded (if it is). I believe it is possible to specify a new repo by setting it up in the compile.conf file. However, I'm not sure how to specify it, and I don't have an example to follow. Please, can you help me with this? Thanks a lot in advance.
Regards,
Dani.

Well, for those who may experience this issue. Since no one from the development team is replying back...
It might sounds silly, but be careful about how do you set your proxy in the HTTP_PROXY and HTTPS_PROXY env. variables. This scala package (sbt) requires you to include the protocol itself (http for HTTP_PROXY, https for HTTPS_PROXY) before the url of your proxy. If it is not included, the compilation process will fail. Hope this helps. The issue can be closed.


Update hdash to look for new manifest naming pattern

As part of the transfer from storing clinical and biospecimen entries as entities to rows in tables, all manifests have been transfered from the previous synapse_storage_manifest.csv files to new files with the pattern synapse_storage_manifest_[component].csv,
For example synapse_storage_manifest_biospecimen.csv or synapse_storage_manifest_imaginglevel2.csv
The HTAN dashboard needs to be updated to look for these, possibly through a regex, as currently I think it looks only for synapse_storage_manifest.csv
https://github.com/ncihtan/hdash/blob/9dc6bb2359811d16bc18394d020c29d8e80064d2/hdash/synapse/htan_project.py#L61
This is a critical issue as all metadata is now stored in these new files and new metadata will be submitted into them.

@ecerami I think we have everything now moved over.... Could you now deploy the update to look at the new manifests - at least for a first test!
FYI @GiaJordan @aclayton555

sure, adding to my list.  will ping back once I have new info.

@adamjtaylor code fix now deployed at http://htan_dashboard.surge.sh/.  Seems ok, but you may want to poke around to make sure.

@ecerami @adamjtaylor Please note: TNP - TMA is not showing metadata on the dashboard, but is likely due to the fact that this project has not been migrated because of the fileview issue we discussed before on slack. I'm still aware and can migrate this project once we decide how to handle the view
cc @milen-sage

Thanks Ethan. Looks ok for now. TMA has been migrated as well so should now show up.
Closing this issue


Intellisense and code navigation don't work well when webpack has modules

VSCode Version: Version 1.14.0-insider (1.14.0-insider)
OS Version: macos sierra 10.12.5

Steps to Reproduce:

clone this repo (it's an almost clean react boilerplate)
yarn or npm i
open app/containers/HomePage
intellisense for react and other modules is not working
it's possible to navigate toSimpleDiv
sometimes for no reason intellisense stops to resolve module starting from app, restarting tsserver does not resolve the problem

Reproduces without extensions: Yes
I have tried a lot of combinations in the tsconfig.json but I was not able to make it works with code completion from npm (react, PropTypes, lodash) and from my code from app
if I use the path options and put node_modules inside it kinda works.
Also if I am doing something wrong let me know.
Thanks in advance

Try adding: "moduleResolution": "node" to your tsconfig.json compilerOptions. That should ensure module names like components/SimpleDiv are resolved
Also, if you are only working with JavaScript, try changing your tsconfig.json to a jsconfig.json. When you use a TypeScript project, you have to manually manage typings files. JavaScript projects do much of this automatically: https://code.visualstudio.com/Docs/languages/javascript#_automatic-type-acquisition

Thanks for the response and sorry for the delay.
I tried to change the file from tsconfig to jsconfig but it work way worse (don't resolve anything at all)
if I use moduleResolution: node and indeed code navigation works for components/SimpleDiv, code completions doesn't work.
looking at the documentation of typescript i found this block about baseUrl and I have updated the example repo and with the following tsconfig.
{
  "compilerOptions": {
    "target": "ES6",
    "allowSyntheticDefaultImports": true,
    "jsx": "react",
    "allowJs": true,
    "moduleResolution": "node",
    "baseUrl": ".",
    "paths": {
      "*": [
        "*",
        "app/*"
      ]
    }
  },
  "include": [
    "app/*"
  ]
}

My issues are:
Code Completion (ctrl+space) doesn't works at all, not for SimpleComponent, SimpeDiv and npm modules[it display a list of words from the document]. It doesn't works with messages either (it's a relative import).
Code navigation (cmd+click) works for SimpleComponent and Simplediv but not for npm modules
if I completely remove tsconfig and restart code I have code completion for npm packages but not for my code inside app
Any other suggestions that I can try?

Try changing the include section to:
"include": [
    "app/**/*.js"
  ]

The include paths are globs so app/* will only expand to files directly under app. You can check if a file is part of your jsconfig project by running the JavaScript: Go to Project Configuration command in the file
Here's the jsconfig.json I used:
{
  "compilerOptions": {
    "target": "ES6",
    "allowSyntheticDefaultImports": true,
    "jsx": "react",
    "module": "commonjs",
    "baseUrl": ".",
    "paths": {
      "*": [
        "*",
        "app/*"
      ]
    }
  },
  "include": [
    "app/**/*.js"
  ]
}

Thanks for the response, with my example repo it work flawlessly 😄  (nice trick the Go  to project configuration)
Sadly if I open my App, which is considerably larger and with more files it will function for a brief moment but after that doesn't works
if I open tsserver.log it raises this exception
Info 38   Received response: {"projectName":"/Users/simonepicciani/dev/clients/neat-webapp/jsconfig.json","typeAcquisition":{"enable":true,"include":[],"exclude":[]},"compilerOptions":{"allowJs":true,"maxNodeModuleJsDepth":2,"allowSyntheticDefaultImports":true,"skipLibCheck":true,"target":2,"jsx":2,"module":1,"baseUrl":"/Users/simonepicciani/dev/clients/neat-webapp","paths":{"*":["*","app/*"]},"configFilePath":"/Users/simonepicciani/dev/clients/neat-webapp/jsconfig.json","allowNonTsExtensions":true},"typings":["/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/chalk/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/compression/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/express/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/fontfaceobserver/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/immutable/dist/immutable-nonambient.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/invariant/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ip/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/minimist/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-dom/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-helmet/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-intl/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-motion/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-redux/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-router/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-router-redux/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/redux/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/redux-immutable/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/redux-saga/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/reselect/src/reselect.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/styled-components/typings/styled-components.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/warning/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babel-core/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/cheerio/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/copy-webpack-plugin/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/enzyme/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/html-webpack-plugin/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/jest/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-addons-test-utils/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/rimraf/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/shelljs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/sinon/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/webpack/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/webpack-dev-middleware/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/webpack-hot-middleware/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/ajv/lib/ajv.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/html-minifier/node_modules/camel-case/camel-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/change-case/change-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/param-case/param-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/constant-case/constant-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/dot-case/dot-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/iconv-lite/lib/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/is-lower-case/is-lower-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/is-upper-case/is-upper-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/lower-case/lower-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/lower-case-first/lower-case-first.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/no-case/no-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/pascal-case/pascal-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/path-case/path-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/postcss/d.ts/postcss.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/pretty-error/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/raf/node_modules/performance-now/src/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/rxjs/Rx.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/sentence-case/sentence-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/snake-case/snake-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/swap-case/swap-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/symbol-observable/index.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/title-case/title-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/upper-case/upper-case.d.ts","/Users/simonepicciani/dev/clients/neat-webapp/node_modules/upper-case-first/upper-case-first.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/accepts/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/acorn/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ansi-styles/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/app-root-path/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/are-we-there-yet/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/argparse/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/array-find-index/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/array-uniq/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/assert-plus/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/async/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/autoprefixer/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/aws4/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/glob/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babel-code-frame/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babel-generator/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babel-template/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babel-traverse/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babel-types/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/babylon/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/base64-js/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/big.js/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/semver/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/bl/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/bluebird/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/boom/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/brorand/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/browser-resolve/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/resolve/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/buffers/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/bytes/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/camelcase/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/camelcase-keys/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/object-assign/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/supports-color/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/chokidar/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/circular-json/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/classnames/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/clean-css/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/commander/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/source-map/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/clone/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/color/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/colors/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/combined-stream/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/concat-stream/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/content-disposition/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/content-type/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/convert-source-map/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/cookie/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/cookie-signature/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/core-js/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/dateformat/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/debug/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/decamelize/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/through2/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/vinyl/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/deep-equal/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/deep-extend/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/del/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/depd/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/detect-indent/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/diff/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/doctrine/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/duplexer2/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ejs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/once/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/enhanced-resolve/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/entities/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/error-stack-parser/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/es6-weak-map/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/escape-html/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/escape-string-regexp/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/escodegen/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/estraverse/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/strip-bom/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/memory-fs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/tapable/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/esprima/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/extend/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/fast-levenshtein/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/file-type/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/finalhandler/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/findup-sync/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/form-data/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/fs-extra/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/node-uuid/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/get-stdin/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/glob-base/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/glob-stream/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/graceful-fs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/gulp-rename/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/gulp-sourcemaps/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/gulp-util/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/handlebars/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/he/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/history/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/hoek/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/html-entities/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/html-minifier/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/htmlparser2/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/http-errors/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/indent-string/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/inherits/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ini/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/inquirer/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/intl-messageformat/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ip-regex/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-absolute-url/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-binary-path/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-finite/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-my-json-valid/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-path-cwd/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-path-in-cwd/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-plain-object/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-promise/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-url/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/is-windows/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/isomorphic-fetch/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/js-yaml/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ms/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/minimatch/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/js-base64/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/jsbn/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/jsdom/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/qs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/request/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/sax/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/uuid/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/jsesc/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/json-schema/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/json-stable-stringify/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/json5/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/klaw/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/leven/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/load-json-file/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/loader-runner/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/path-exists/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash-es/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.assignin/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.assignwith/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.bind/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.camelcase/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.defaults/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.escape/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.filter/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.flatten/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.foreach/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.get/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.indexof/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.isarguments/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.isarray/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.isempty/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.isequal/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.isplainobject/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.isstring/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.keys/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.mapvalues/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.merge/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.pick/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.pickby/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.reduce/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.reject/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.some/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lodash.template/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lolex/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/lru-cache/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/meow/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/merge-descriptors/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/merge-stream/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/micromatch/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/mime/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/mime-db/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/mime-types/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/mkdirp/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/mkpath/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/node-dir/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/node-fetch/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/node-int64/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/node-notifier/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/nopt/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/number-is-nan/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/on-finished/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/on-headers/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/optimist/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ora/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/os-homedir/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/os-locale/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/os-tmpdir/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/pako/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/parse-glob/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/parseurl/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/path-is-absolute/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/path-parse/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/pify/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/pluralize/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/prelude-ls/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/progress/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/prop-types/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/q/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/query-string/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/range-parser/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/rc/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/react-side-effect/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/relateurl/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/replace-ext/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/resolve-from/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/rx/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/rx-lite/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/send/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/serve-static/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/shallowequal/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/source-list-map/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/source-map-support/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/sprintf/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/sprintf-js/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/sshpk/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/statuses/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/strip-ansi/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/strip-json-comments/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/swiper/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/table/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/tar/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/tempfile/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/text-encoding/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/through/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/tmp/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/touch/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/tough-cookie/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/traverse/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/type-check/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/ua-parser-js/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/uglify-js/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/window-size/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/yargs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/uniq/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/url-regex/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/user-home/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/utils-merge/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/verror/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/vinyl-fs/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/watch/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/watchpack/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/webpack-sources/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/which/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/wrap-ansi/index.d.ts","/Users/simonepicciani/Library/Caches/typescript/2.4/node_modules/@types/xtend/index.d.ts"],"unresolvedImports":["!file-loader?name=[name].[ext]!.","!file-loader?name=[name].[ext]!.","!file-loader?name=[name].[ext]!.","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","assets","file-loader?name=[name].[ext]!.","sanitize.css","utils","utils","utils","utils","utils","utils","utils","utils","utils","utils","utils"],"kind":"action::set"}
Err 39    Exception on executing command unknown:
Project '/Users/simonepicciani/dev/clients/neat-webapp/jsconfig.json' does not contain document<EMAIL_ADDRESS>Error: Project '/Users/simonepicciani/dev/clients/neat-webapp/jsconfig.json' does not contain document<EMAIL_ADDRESS>    at Object.ThrowProjectDoesNotContainDocument (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:75718:23)
    at ConfiguredProject.Project.getScriptInfoForNormalizedPath (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:77238:42)
    at ConfiguredProject.Project.getScriptInfo (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:77243:29)
    at ModuleBuilder.AbstractBuilder.getOrCreateFileInfo (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:76551:51)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:76679:84
    at Object.map (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:1483:29)
    at ModuleBuilder.getReferencedFileInfos (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:76679:31)
    at ModuleBuilder.updateFileReferences (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:76708:42)
    at ModuleBuilder.ensureProjectDependencyGraphUpToDate (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:76693:30)
    at ModuleBuilder.onProjectUpdateGraph (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:76684:22)

I tried on my linux machine with the stable and it works so it's the insider version for sure. (same result if i disable all the extensions)

Hmm, can you please check to see if the file<EMAIL_ADDRESS>exists?
Also, as workaround, try disabling automatic type acquisition by adding:
  "typeAcquisition": {
        "enable": false
    }

to your jsconfig.json or by setting  "typescript.disableAutomaticTypeAcquisition": true in your vscode user settings.
A final step to try is deleting the entire /users/simonepicciani/library/caches/typescript/ directory. Perhaps the typings cache got into a bad state?

The file exists, I erased all of the ts cache library without any luck, disabled type acquisition in the json file, nothing seems to works.
Then I tried starting vscode without extension and it worked! 🎉  Even the type acquisition 😄
Now it's working with the extensions. (Maybe I have some extension that sometimes breaks the type acquisition?)
Anyway thanks for the invaluable help.

@mjbvz I have an update.
I don't know why but if i install with yarn it doesn't works, if I use npm i it does work.
with npm i I don't have the error in the tsserver.log about @types/node
node: v8.1.3
npm: v5.2.0
yarn: v0.27.5

In my case, the problem was I had installed eslint only locally through yarn. After installing it also globally, it worked.

Too complicated. Can I ask the same thing, but in the short?
I added an resolve option to webpack.config.js to get a shortened imports work:
import TestService from ‘services/test-service’
instead of:
import TestService from ‘../../../../services/test-service’
But now VSC autocomplete not work when I type TestService later.
How to fix that without applying entire another's jsconfig.json?
What is the one-two line/option solution?
Thanks.

Yes, configuring the paths in the tsconfig or jsconfig is our current story for supporing webpack alaises. If you do not already have a tsconfig or jsconfig, try searching online for a starting one and then modify it as needed.
The @types error is a duplicate of #30425. Should be fixed in VSCode 1.14.2


update readme

Now package main is ./lib, and lib is only use babel to handle components. sass files only copy to  ./lib.
Because many apps will ignore 'node_modules' when using babel-loader. For customization(such as React Toolbox Loader ), we will retain sass files.

+1 (we need +2 for accept this pull request)

+1


ci(patch): add lz4 for iOS [sc-11176]

mobile-dependencies-xcf should be public then, isn't it?

It is only fetched on iOS builds, and does not affect build of distributed-system; so don't think that it is a must to be made public.

Yeah, I also think it is not must have to make it public. @ser-0xff any special reason why you want it ? May be we miss something ?


Synchronizing models with posts

According to the documentation I defined a customized custom post type in the model to be able to synchronize posts and models. The post type gets added to the backend and if I create such a post manually everything works as expected. As soon as the post gets synchronized to a model (either by adding a new model object or by adding the post id to an existing model in the database), it loads the corresponding view from the model. So syncing to the model works well.
However the rendered page is not related to an actual WP post anymore. There is no post id given in the HTML, no css classes of the post type are added to the body, the page title set in the post is missing, the menu item is not marked as active and the url also doesn’t match the definition of the post type. The post only seems to forward to the public route of the model (which is the default /controller/id).
Is this an issue or is it just the way synchronizing models with posts is supposed to work in WP MVC?
Thank you!

@tombenner do you have a POV on this?

From what I recall, the original intent was to simply sync the model with posts at the data level, and then use the WP MVC-generated public route ({:controller}/{:id:[\d]+} by default, as you mention) as the show route for those records. The thinking for using WP MVC's routing was that it'd make it easier to add other RESTful routes for that model. So, the behavior you're seeing is the intended behavior.
We might consider supporting WP's native routing for these custom post types. There should only be a single show route for any given resource, and I'd lean towards using WP MVC's RESTful, flexible routing over WP's routing as the default, but we could consider supporting opt-in use of WP's native routing instead if there's enough motivation for it. What's your use case, @waalzer?

Thank you @tombenner! In terms of REST this behavior totally makes sense.
We use WP MVC for some of our pages, that are heavily data-driven. Since MVP rendered pages don’t represent a WP post, WordPress doesn’t take care of various things (especially in the HTML header). So at the moment we would need to customize some parts of these pages in order to keep consistency among mvc and non-mvc pages. In our case this means adjusting meta tags, inserting css classes for HTML body and active menu items, manipulating the output of seo plugins (which usually rely on post data as title and excerpt), rewriting urls instead of using the post's permalinks etc.
So native routing would reduce customization and help to keep consistency throughout the website.

Anything actionable on this, gents?


Construct a dag with triangle

I would like to know that is it possible to construct dag like the one in the figure? I had tried the following code but got some error:

class BranchFlow(FlowSpec):
    @step
    def start(self):
        self.next(self.a, self.c)

    @step
    def a(self):
        self.x = 1
        print("A")
        self.next(self.b)

    @step
    def c(self):
        print("C")
        self.next(self.b, self.d)

    @step
    def b(self, inputs):
        self.next(self.d)

    @step
    def d(self, inputs):
        self.next(self.end)

    @step
    def end(self):
        print("END")
        pass

if __name__ == '__main__':
    BranchFlow()

I also encountered this problem. It seems that metaflow does not allow a branch to have multiple child nodes @jfernandez

If we need such dependencies, how do we construct the code

@savingoyal

@tanzeyy @LennieGuy is there a reason to have an edge between C and D. If there was no edge between them then it would be a valid DAG for Metaflow - D would only execute after C and you would have access to any intermediate data generated by C in D.

Thanks for your reply. The dag shown in the figure is only a demo of our target workflow, actually there are several steps between C and D and we would like them to be executed immediately after C is finished.

At the same time, we have more complex dags to construct, but it seems that metaflow is a little inadequate

You can create such a DAG perfectly fine. Every step has access to all the information from all its ancestors.

You can create such a DAG perfectly fine. Every step has access to all the information from all its ancestors.

But the absence of the edge between C and D makes the sequential dependency infeasible, and we wouldn't want D to execute before C is finished.

This structure would work then.

Please reopen the issue if you would like to discuss further or ping me in chat.metaflow.org if that's quicker.


Issue with Opening ONLYOFFICE Version History Function

Hi all,
I am encountering an issue with the ONLYOFFICE version history function that I cannot open. My current deployment environment is as follows:

ONLYOFFICE/DocumentServer: 7.3.2
Redmine: 5.0.4-bullseye
ONLYOFFICE Redmine plugin: tag 2.1.0
MariaDB: 10.7.1-focal

In this environment, I am able to successfully open and edit documents, but the version history function is not working. Any assistance or guidance to resolve this issue would be greatly appreciated.
I have attached screenshots for reference.

I have the same problem as yours.
According to https://github.com/ONLYOFFICE/DocumentServer/issues/1085 ,
It seems that ONLYOFFICE/DocumentServer over v7.0.0 supports version history for both docx and xlsx.

Opening a file's history in the editor is not yet implemented in the Redmine ONLYOFFICE integration plugin.


Batch size

For fine tune llama-3-8b-bnb-4bit on powerfull gpu than T4 what is good batch size(per_device_train_batch_size = 2)

Oh 2 / 4 are fine - tbh all trial and error


[Task]: Change to syncing on a per-account basis

Task description
Currently the application is syncing all accounts at once when a user logs in, which in some cases can take a frustratingly long time if a user has many accounts, many addresses, or both.
Product requirements:

User can switch accounts immediately on login (if user switches to account B before account A is finished syncing, we can...)

:x: Stop syncing account A

Will (likely) waste API requests (only if wallet.rs doesn't store / cache data from the node)

:x: Continue syncing account A

Will (likely) cause longer sync time

:heavy_check_mark: Pause syncing account A

Does NOT waste API requests
Does NOT cause longer sync time

User can switch accounts while initiating a normal transaction (UI is updated for account B, account A's transaction is processed in the background)
User can switch accounts while initiating a participation transaction (UI is updated for account B, account A's transaction is processed in the background)
User can make internal transfer with only having one wallet synced (opt. sync the recipient wallet beforehand)
User cannot switch while using the balance finder
User cannot switch while adding a new node (b/c client options are per-account)

Requirements
TBD
Acceptance criteria
Meets the above requirements.
Creation checklist

[X] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Duplicate of https://github.com/iotaledger/firefly/issues/2548, we should close 2548 as it has more info here


library/navigation.php

Is it okay to edit the library/navigation.php file or is there a better way to adjust the breakpoints for the navigation?

Seems like something that could be accomplished using only CSS.

You're right. I removed the inline visibility classes from navigation.php and added breakpoint mixins for navigation in _navigation.scss
https://github.com/olefredrik/FoundationPress/pull/698

Struggling to make the top bar and title bar breakpoint to behave as expected. Latest fresh FoundationPress install shows both .vertical and .dropdown menus on medium and up. On small, the title bar appears with hamburger menu link, but when clicked nothing happens.
Commenting out .main-navigation {   @include show-for(medium); } from _navigation.scss gets the hamburger link to work on small, but doesn't fix both mobile and desktop menus showing on medium and up.
Ideally there's a simple way to choose the breakpoint for the mobile menu. I wonder if I'm missing something obvious.


Instructions in the Stata blog post re the installation of Python libraries don't work in all cases

Computers with version 2.x of Python install will probably need to use pip3 instead of pip to install Pandas and Openpyxl. We should note this in our README

Here is a good summary on pip/pip3 differences: https://www.pythonpool.com/pip-vs-pip3/. Mac seems to be more picky to use the exact right name compare to Windows.