magento2 baseURL and version extraction

Magento 2 BaseURL extraction (covered by unit and integration tests)
Magento 2 Version extraction (covered by unit tests)
Github action for unit/integration tests.
Stubbing M1/Presta methods.

👍


Clarify note

Previous wording of note 1 did not make it clear whether arrow up & down keys worked

Hmm, I agree with rewording it, but I feel that only referring to "increment/decrement" doesn't make it clear what the expected forms of supporting that should be, which seems worth mentioning.

Excellent, thanks!


ScatterPlot narrows the horizontal display range coordinate names overlapping issue

Question: (Narrow down the landscape display, and if there is a lot of data, the tick names on the X-axis will overlap,This is also the case in official examples)
ScottPlot Version: (4.1.69)
Code Sample:
double[] dataV = new double[ListY.Length];
double[] yArr = new double[ListY.Length];

ScatterPlot V_ScatterPlot = null;
V_ScatterPlot = V_Plot.Plot.AddScatter(dataV, yArr, Color.Red, 2, markerSize: 2);
V_ScatterPlot.OnNaN = ScatterPlot.NanBehavior.Gap;
V_Plot.Refresh();

It looks like this issue relates to ScottPlot 4 which is no longer a target for active development, so I'll close this issue. If someone fixes this and creates a pull request, I'd be happy to review it though 👍

Confirmed ScottPlot 5 does not have this issue


Dont set PYTHONNOUSERSITE unless explicitly asked

Fixes #9995
Tested this with

global kernel
venv kernel
conda kernel
same with using jupyter instead of raw

Codecov Report

Merging #10124 (6ce07d5) into main (c5882ac) will increase coverage by 0%.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           main   #10124   +/-   ##
=====================================
  Coverage    55%      55%
=====================================
  Files       203      203
  Lines      9243     9244    +1
  Branches   1492     1492
=====================================
+ Hits       5092     5093    +1
  Misses     3747     3747
  Partials    404      404

Impacted Files
Coverage Δ

src/platform/common/types.ts
100% <ø> (ø)

src/platform/common/configSettings.ts
80% <100%> (+<1%)
:arrow_up:


Set up Prometheus alerting on Discord in Ansible

We need to configure our Alertmanager to send us alerts on Discord such that we
can be informed of anything not being right as part of the monitoring setup on
lovelace.

As discussed in the dev-ops channel, I think we can reach a configuration here that utilizes our existing High-Availability AlertManager setup.
We can set up token access for Prometheus on Ansible machines to push alerts through to the Kubernetes HA AlertManager.
Some notes:

This does not mean we cannot route alerts differently, push to different areas based on different severity or anything like this, we still maintain full granular control over alert routing, even more so since we centralise it.
We can write a small healthcheck (systemd timer, cronjob, etc.) to check whether the alertmanager server is healthy and responding to requests, if it is not then we can trigger a rudimentary alert from netcup reporting that the AlertManager is down. I don't think this needs to be a separate instance of AlertManager as that feels overcomplex and leads to duplication of routing configuration.

Just to clarify this from a discussion on Discord, this is about adding a "dead
man's switch" alert that will route to Discord in case the Netcup Prometheus
instance can't contact the Alertmanager in Kubernetes properly. To cover this
case we want to:

add alerts in Prometheus in case it cannot talk to Alertmanager properly
(there are built-in metrics for this exported by Prometheus)
add a local alertmanager configured to send alerts to Discord
configure the local alertmanager & Prometheus instances such that only the
newly added alerts from above are routed to the local alertmanager and
everything else is still routed to the Kubernetes alertmanager.


⚠ Bofrost.lu has degraded performance

In 42fba17, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1363 ms

Resolved: Bofrost.lu performance has improved in 7f00a6f after 13 minutes.


fix: Fix reference key

closes #60

Codecov Report

Merging #62 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #62      +/-   ##
==========================================
+ Coverage   96.77%   96.79%   +0.01%
==========================================
  Files          11       11
  Lines         621      624       +3
==========================================
+ Hits          601      604       +3
  Misses         20       20


Update test for issue #48

Coverage remained the same at 93.525% when pulling 753495dc2087cbb1e43fbcb3227271ec8a71b45c on edgarmueller:master into 1f2e30701c444f4fbfb2e9ad6574da9a82248296 on eclipsesource:master.


Fix wire damage detector error

Prevents this error from spamming:
Wire damage detector error: addons/wire/lua/entities/gmod_wire_damage_detector.lua:26: attempt to index field 'key_ents' (a nil value)
stack traceback:
addons/wire/lua/entities/gmod_wire_damage_detector.lua:26: in function <addons/wire/lua/entities/gmod_wire_damage_detector.lua:15>
[C]: in function 'xpcall'
addons/wire/lua/entities/gmod_wire_damage_detector.lua:38: in function 'func'
addons/ulib/lua/includes/includes/modules/hook.lua:260: in function <addons/ulib/lua/includes/includes/modules/hook.lua:253>

Also removes the unnecessary pcall that prevent this error from being found earlier.

The current changes are just whitespace changes

The current changes are just whitespace changes

It was just showing last commit

Why not just add self.key_ents = {} in the Initialize function? Less overhead and seems to be what was intended in the first place.

Why not just add self.key_ents = {} in the Initialize function? Less overhead and seems to be what was intended in the first place.

Good point, i've applied your suggestion


Heavy lag on website

On https://editor.superlist.com/

Please include your browser, your OS, and a video showing what you're doing on the website that's lagging.


adding sparalic

Thanks @sparalic, good job!
Would you mind adding a picture to the README file in a separate pull request, before I merge this? I think would be nice to have a page that looks a bit fancier. Thanks!

@datapythonista absolutely! I’ll create a branch and add a pic, I’ll make us a nice header!!


fix: properly check if a member can be nullable

Description of changes
Change the way we compute the nullability of members. Before we were only looking at the box trait in the target type for the box trait and ignoring the trait on the member itself. See for instance the test can read box trait from member which has the following model:
        namespace com.test
        structure MyStruct {
           @box
           foo: MyFoo
        }
        long MyFoo

The code was incorrectly assuming that the foo member was not nullable. This change accounts for this by using the NullableIndex which correctly computes whether or not the member or the target type are nullable. This change in turn was also required in several places that were making the same mistake and assuming that computing the Symbol for the target and testing for isBoxed() was enough to know if the member is itself boxed.
After this change several models from the aws-sdk-swift generate different code, I checked and all the changes seems legit.
NOTE this is a draft change as the smithy release 1.25.0 is still pending.
Scope

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I just realized that this PR is made from the fork. @sugmanue can you push the PR to https://github.com/awslabs/smithy-swift and create a PR again?
downstream CI doesn't work with forks.

@ganeshnj I will cancel this one and create a new PR.


Open Storeman from other app

Good evening and thank you for your work for Storeman.
I'd like to link it to my UI Themer to make easier to find new themes.
In a nutshell, clicking on a menu would open Storeman with the result page for a particular tag search.
Is it possible somehow?
Br,
Francesco

I tried to follow your directions but I'm a bit lost. Would you mind giving here an hint?
I got here in my qml page (I've imported Nemo.DBus 2.0)
    DBusInterface {
        id: openStore
         service: 'harbour.storeman.service'
         path: '/harbour/storeman/service'
         iface: 'harbour.storeman.service'

         signalsEnabled: true

         function openPage() {
             call('initialSearch', themepack)
         }

     }

and I trigger it with
        MenuItem { text: qsTr("Download more themes"); onClicked: openStore.openPage() }
but when I run the Item I get
[W] unknown:0 - QDBusMarshaller: type `QObject*' (39) is not registered with D-BUS. Use qDBusRegisterMetaType to register it
[W] unknown:0 - QDBusConnection: error: could not send message to service "harbour.storeman.service" path "/harbour/storeman/service" interface "harbour.storeman.service" member "initialSearch": Marshalling failed: Unregistered type QObject* passed in arguments
[W] unknown:75 - file:///usr/share/sailfishos-uithemer/qml/components/themepacklistview/ThemePackListView.qml:75:5: QML DBusInterface: QDBusError("org.freedesktop.DBus.Error.Failed", "Marshalling failed: Unregistered type QObject* passed in arguments")

Sorry for a late reply. If it's still actual, your interface should look like this
DBusInterface {
    id: openStore
    service: 'harbour.storeman.service'
    path: '/harbour/storeman/service'
    iface: 'harbour.storeman.service'

    function openPage() {
        call('openPage', ['SearchPage', {initialSearch: 'theme'}])
    }
}

If you call openPage in one place then there is no need to define it as a function - just call
openStore.call('openPage', ['SearchPage', {initialSearch: 'theme'}])

where necessary.

No need to apologize :) Thank you so much for your help, it works like a charm!


Make sun attributes datetime objects

Description:
Sun attributes as datetime objects instead of being converted to ISO8601 strings. Thanks to @dale3h and @jumpkick for pointing this out to me.
Checklist:
If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

This is not allowed. All attributes have to be valid JSON. That this gets valid JSONified is not enough.
This is a requirement because we will otherwise have differences from events/states that originate local vs remote.


prove: Add RemovePositions()

RemovePositions() allows for the removal of desired slice of positions
from the proof. This is useful for un-caching of leaves after they're
deleted. For Bitcoin wallets, this will be useful when deleting stxos
from the cached proof.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

109 of 175 (62.29%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.5%) to 77.426%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

prove.go
109
175
62.29%

Totals

Change from base Build<PHONE_NUMBER>:
-1.5%

Covered Lines:
1516

Relevant Lines:
1958

💛  - Coveralls


Migration of https://github.com/aiven/devportal/pull/new/aws-privatelink-step-by-step

This is the article being migrated from help.aiven.io:
"5858370-aws-privatelink-setup-step-by-step-using-aiven-and-aws-web-console"
What changed, and why it matters

Hi @fmanimali the PR still contains errors and warnings.
The error in the image is due to a missing :alt: tag

I would discuss this article: we currently have https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks.html for the usage of AWS Privatelinks with Aiven, what has this article on top of it? Maybe for @dewan-ahmed ? Once we confirm the need I can work on fixing the shape of it if needed

@fmanimali from my understanding, https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks.html serves the purpose of the CLI version of "How to use AWS privatelink with Aiven" and this PR brings in the web (Aiven console) version.
Since we focus mostly on the Aiven console for docs/platform/howto, my suggestion is to update https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks.html to include the unique contents from https://help.aiven.io/en/articles/5858370-aws-privatelink-setup-step-by-step-using-aiven-and-aws-web-console rather than creating a separate article.
Suggested format:

Include the diagram from https://help.aiven.io/en/articles/5858370-aws-privatelink-setup-step-by-step-using-aiven-and-aws-web-console
Include the steps to create the privatelink using Aiven console from https://help.aiven.io/en/articles/5858370-aws-privatelink-setup-step-by-step-using-aiven-and-aws-web-console
Under a separate section of the same page, add the contents from https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks.html as the steps to do the same using Aiven CLI

@fmanimali pinging to request your 👀 on this PR. Let's try to move this forward 🙏🏽

@ftisiot @fmanimali I propose we close this PR due to inactivity. What's your thoughts?

This was identified as a high priority migration article, we do need this content and the pull request should not be closed. If @fmanimali isn't available to lend his expertise, please find someone else who can help, or work through the steps yourself and see if you can get the issue to a publishable state.

(also the branch is very stale, please let me know if you'd like me to rebase to give this a new lease of life)

Hi @lornajane, yes please, rebasing would be great.
The main reason I couldn't tech review is because I don't have sufficient permission on the internal shared AWS account. For another PR, someone from the security team validated the steps when I opened a ticket to request more access. I have created one more ticket requesting access to be able to create/modify AWS VPC, TGW resources. Since there is only one shared project, I believe that there's strict control on allowing access.

Update: as of today, DevRel doesn't have required access to test this PR. A Halp ticket remains open and the team is aware of our need.

Rebased to bring the article into the current version of the docs platform. This was identified as a key article, but I now have questions about how it compares to https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks which looks similar.

@fmanimali what's your take on

how it compares to https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks which looks similar

@TibsAtWork to take a look at this and see if it's combine-able with the page mentioned.

@TibsAtWork Build error

I propose to close this PR: we already have https://docs.aiven.io/docs/platform/howto/use-aws-privatelinks available in the Aiven public docs.

Closing this as we have an AWS Private Link article and can add other information on a fresh branch later as needed.


Install plugins into subdirectories

Use the same directory structure as mixins and install plugins in their own subdirectory.
~/.porter/plugins/PLUGIN/PLUGIN
https://github.com/deislabs/porter/pull/874 which implements install needs them in this location.

/azp run porter

/azp run porter-azure-plugins

/azp run

/azp run


WhenRepeatedFilter - Filtering of identical LogEvents

Useful if having a permanent error condition.

@304NotModified Have changed it from a MostRecentlyUsed (mru)-list to a Dictionary. Also improved performance by using StringBuilder.Equals, though it requires some special capacity-conditions.

great feature!!

needs some docs I guess?

@304NotModified Have added some docs:
https://github.com/NLog/NLog/wiki/WhenRepeated-Filter


Very enhance

Enhancement Request
Desired Behavior
asdf
Today's Behavior
qwer
The Value Add
zxcvzxcv
The Tradeoffs
qwe

test


update Amazon OpenSearch. Add Link to patch info

Added OpenSearch Patch link for AWS OpenSearch

🗣 Description

💭 Motivation and context

🧪 Testing

📷 Screenshots (if appropriate)

✅ Checklist

[ ] This PR has an informative and human-readable title.
[ ] Changes are limited to a single goal - eschew scope creep!
[ ] All future TODOs are captured in issues, which are referenced
in code comments.
[ ] All relevant type-of-change labels have been added.
[ ] I have read the CONTRIBUTING document.
[ ] These code changes follow cisagov code standards.
[ ] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

This is related to #24


fix issue #82: Header values cannot contain semicolons

this is to fix issue #82 "Header values cannot contain semicolons" by introducing new repeatable option -H.
People can specify as many as needed by repeating the flag, for example:
boom -readall -n 1 -c 1 -H "cookie:foo=1;bar=2" -H "X-My-Header: xyz" -m GET 'http://localhost:8080'

it uses the the value of the header as it is, which means it won't be processing as -h does.

Hi @rakyll
do you have any feedback on this PR?
thanks

+1

Left some comments, happy to merge this change.

updated, thanks

Thanks!


Better check for if Xcode is properly installed

Problem
If Xcode install fails after the download but before Xcode is completely installed, subsequent Chef runs won't properly reinstall Xcode.
Change
This change adds an additional check to the installed? definition, ensuring that /usr/bin/xcodebuild -showsdks returns an exit code of 0 to consider Xcode properly installed.

FYI this'll fail the chef exec rspec check until #269 is merged to fix that check.


Acronym

I have an issue with Acronym excercise. I provided a solution, but I get an error if I use an exception class which seems it is unknown in exercism. The solution works fine in an on-prem system.

You provided a solution that apparently raises an error.  That error is not expected, though.
Do the tests pass locally?
You may want to request mentoring so that a mentor can help you work through the exercise.  If there is an issue, then they may direct you here to open one.
I suspect that it is simply that the tests are not expecting to have the try/catch performed, or not result in the way that it is used here.

yea, the exception class is probably missing in the runtime
https://help.sap.com/doc/abapdocu_731_index_htm/7.31/en-US/abensegment_functions.htm

You provided a solution that apparently raises an error. That error is not expected, though.
Do the tests pass locally?
You may want to request mentoring so that a mentor can help you work through the exercise. If there is an issue, then they may direct you here to open one.
I suspect that it is simply that the tests are not expecting to have the try/catch performed, or not result in the way that it is used here.

Locally the tests pass. The exception is the expected behaviour when the appropriate index is not found.
I think it would work when the exception class has been added to the runtime.

https://github.com/abaplint/transpiler/pull/954

Hi Lars, thanks it works now.


TF Keras sequence_test additional test cases covers

1- remove_long_seq api test case added

@pavithrasv  Could you PTAL and approve or suggest changes(if required).


1938 titles possibly not indexed (example: Angel)

Users tried searching for terms that appear in the 1938 titles, but no results.

Test this now and see if it is expected results


pdf.js relies on urls to contain the 'pdf' extension

When the server doesn't provide the Content-Disposition header, pdf.js relies on urls to contain the 'pdf' extension. But URLs are locators, not names.
Steps to reproduce:
mv web/compressed.tracemonkey-pldi-09.pdf web/compressed.tracemonkey-pldi-09
sed -i 's/compressed.tracemonkey-pldi-09.pdf/compressed.tracemonkey-pldi-09/g' web/viewer.js
firefox web/viewer.html

Now click on download. You will be offered a 'document.pdf' file. The name should be something more meaningful.
The bug also happens when I leave out the pdf extension on my apache web server.
Proposed solution:
Use the title of the pdf. (as this viewer.js code). The title is also used by firefox for the File -> "save page as" functionality when displaying a HTML page like http://en.wikipedia.org/wiki/Internet_media_type .
Not every html web page ends in .html. Instead by the extension, a document's type is specified by its MIME-type.
However, most pdf files have the pdf extension, and most pdfs online also have a good-to-store name in the url.
I don't know whether the new retrieval method should overwrite the url retrieval, or be a fallback to it.
See also #3455.

@timvandermeij
Any update on this? It has been open for more than two years now. Because my file param is a server call that sends a pdf file back, the pdf viewer is not able to detect the name of the file because it seems to be looking for a .pdf extension and so I'm stuck with "document.pdf" when downloading and "untitled.pdf" in the window bar when viewing.
It would be handy if we could also specify a "title" in the URI as well as the "file" such as .../pdf-viewer/viewer.html?file="..."&title="..."

I know that currently work is being done in #7554 to support the Content-Disposition header, which is a way to solve this issue. I do agree, however, that document.pdf is not the best possible name and we might need to improve the function for getting the (file)name. Patches for this are welcome, so I'm labeling this as a good beginner bug as it should not be too hard to implement.

@timvandermeij Excellent thank you, I believe supporting Content-Disposition would actually fix my issue.
I agree, as I was going through the code I noticed it should not be too difficult to just add another URL param for the filename. I'll give it a try in the next few days, Thanks.

Patches for this are welcome, so I'm labeling this as a good beginner bug as it should not be too hard to implement.

@timvandermeij Please remember that in PR #4956 we purposely moved away from letting various hash parameters affect the viewer (unless debugging is enabled, see https://github.com/mozilla/pdf.js/wiki/Debugging-pdf.js).
Hence I do not think that we should make it possible to specify the title using a hash parameter!
Especially considering that it would be non-standard (in the context of http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_open_parameters.pdf), and compared to the Content-Disposition approach in PR #7554, it really doesn't add much value.

Sorry, I should have been more clear. I meant that patches are welcome for improving the function that determines the file name from the URL. I think we can do better there instead of only relying on the file extension. I agree that we should not add more hash parameters.

What's the status of this issue? Is this still open?

What's the status of this issue? Is this still open?

@anirudhrb still opened, there was an attempt to implement that at #7554, would you like contribute to that?

@yurydelendik Yes, I would like to contribute. What is expected in a PR for this issue?

@anirudhrb, you may just take the above PR as a base since it has remoting of data somewhat right -- we would expect small patch with a unit tests. We don't need spec Content-Disposition parsing, but enough to get filename.

@yurydelendik I have started working on this. This is my first attempt at contributing to an open-source project. I'll need some time to get comfortable with the codebase. :)


Added Cybersecurity roadmap

I've added cybersecurity roadmap.

Added communities
Added open-source security projects
Added security job boards

#84

If needed I can create a visual roadmap for the website as well.

@ctnkaan thank you so much for this. Once we have the roadmap ready for this we will merge this PR.
__
  Summary: :ok_hand: This code looks good

What about this PR? How far is it done @ctnkaan?

What about this PR? How far is it done @ctnkaan?

It's done from my view. It's just waiting for a cybersecurity roadmap to be added to the website.

Ok @ctnkaan.
@kaiwalyakoparkar Please add the roadmap in commclassroom website and then merge this PR.

@SaptarshiSarkar12 Yup, that's the plan

@ctnkaan will you be able to create the roadmap for cyber security in readme, like we are doing it now?

Hey again. Yea I can. I'll try to make one this next week. But in my opinion the roadmap should be just practiting and learning the paths from tryhackme.com

@ctnkaan yes you are correct about that. In my opinion the roadmap should provide just enough information to be a beginner pentester. Nothing too advanced due to obvious security-related reasons. Perhaps all the topics covered under certifications like CySA+


Add Monochrome Mode and other fixes

Thank you for all the work you've put into this tool!
Add a monochrome output mode which does not use any escape sequences for colors (-b for basic output).
Update the color tagging to use BAD for warnings, rather than RED
Update output text & color handling for consistency:

Only the "OK!" text is colored on OK items
Entire line is colored for WARNING and NOTICE items
All WARNING and OK items include those words at the beginning of the line

Update Check 1.16 to show OK  when appropriate
Fix Check 2.4 to handle case when API region is not the bucket's HomeRegion.
FIxes #49

I liked more to have the entire OK line in green. But now looks cleaner with and without colors. Thanks for this and the other fixes.


Unlock Java CI, disable Java tests which rely on mangled names

This should bring us to a working Linux CI for Java as well.
The way we load libraries is platform dependent it turns out, so this needed some adjustments. Also fixed some paths and disabled tests which we cannot do until we merge https://github.com/swiftlang/swift-java/pull/27

We're not in great shape yet but I'm trying to get us some level of soundness and at least not breaking basic compilation and things like that.
This now has a separate java tests target and also checks make which tries to use Java2Swift/JavaToSwift (which explodes on linux currently still).

Handled in a different PR which took pieces from here.


Update scribe-slf4j to 3.2.1

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.outr", artifactId = "scribe-slf4j" } ]

labels: library-update, semver-minor

Superseded by #145.

Superseded by #145.


Update Matomo Java Tracker to 3.0.2

Hey @thanvanlong,
Just wanted to give your project a little boost with the latest and greatest from Matomo Java Tracker! 🚀
Changes in a Nutshell:

Bug Fixes & Performance Boosts: Say goodbye to some pesky bugs and enjoy a faster, smoother tracking experience.

Security Makeover: We're getting the latest security swag to keep our project locked down.

Stay Cool with Compatibility: Now we're best buddies with Matomo versions up to 5, so no more awkward compatibility issues.

Less Baggage: Matomo Java Tracker 3.0.2 is lean and mean with fewer dependencies. Less stuff, more speed!

New Toys: Check out the cool new dimension parameter for super-customizable tracking.

Java 11 Party: We're upgrading to the latest Java 11 implementation. It's like giving our project a cool new set of wheels.

Smooth Moves: If you're coming from version 2, no worries! There's a handy migration guide here to make the switch painless.

How to Test:

Update to Matomo Java Tracker version 3.0.2.
Make sure our project still builds like a champ.
Double-check that our Matomo tracking mojo is still on point.
Test out any new features and give that dimension parameter a spin.

Where to Get Help:

Dive into the Javadoc for the nitty-gritty details.
Got issues or bright ideas? Hit up the Matomo Java Tracker GitHub.

Your Feedback Matters:
Give it a whirl and let us know how it goes! Your feedback is like gold to us. 🌟
Cheers,
Daniel

@thanvanlong ping


Imprementation of high-sensitive mode

📋 Description
The current DAJIN2 is designed to avoid classifying too finely during clustering. While this improves interpretability, it does not achieve sufficient precision in clustering for experimental systems where alleles are expected to split very finely, such as in cellular systems.
Therefore, in experiments where alleles are expected to split finely, it is desirable to add an option for a high-sensitive mode as a countermeasure.
🔍 Environment
- DAJIN2 version: 0.5.5

📎 Anything else?
No response

This issue can be addressed using preprocess.sv_handler.
Separating SV alleles during preprocessing and then performing mapping and clustering for each allele results in more accurate clustering. Proper preprocessing is likely a more straightforward and effective strategy than solely focusing on refining clustering methods.


Local tunnel

Hacky and unfinished.
BAsically what it does is open tunnel(s) for the relations (currently hardcoded).
I put local.platform.sh <IP_ADDRESS> in my /etc/hosts file but it would be much cooler to resolve local.platform.sh to <IP_ADDRESS> through dns...
There is some stuff to be done around configuration still for Drupal and probably Symfony (solr config in db?).
A host has been configured as local.platform.sh

A tunnel to environment mybranch has been created (ssh -N -L 18080:solr.internal:8080 -L 16379:redis.internal:6379 -L 13306:database.internal:3306<EMAIL_ADDRESS>Connect to solr through local.platform.sh:18080Connect to redis through local.platform.sh:16379Connect to database through local.platform.sh:13306
Set your settings to connect local.platform.sh: for mysql (do not use localhost !)

You can see the site on http://local.platform.sh:8000

This is stale most everything was integrated somewhere else. This is now basically a documentation issue.  We probably also need better output for platform relationships will open a ticket for that.


include: remove incorrect UV__ERR() for EPROTO

https://github.com/libuv/libuv/pull/2979 negated the value of
UV__EPROTO on platforms that don't define EPROTO, but it didn't
remove the surrounding UV__ERR() call. This was causing numerous
test failures in Node.js.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/2068/


Adding ability to add ASSETS_PREFIX ENV value.

Same change that was applied to collections-publisher: https://github.com/alphagov/collections-publisher/commit/44cd9ccabeb51e4ef45947104de747352c193c8d
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

Sorry to butt in.
I'm wondering if we gain anything by having this by env var configured. I think everything would still work in all environments if we just set config.assets.prefix = "/assets/manuals-publisher" which would save the complexity of this becoming part of environmental configuration.
I'd also somewhat wonder if it was slightly neater to keep the path as the Rails defaults "/assets" and use the web-server config to proxy that to your bucket location, but I'm guessing the horse might have bolted on that?

Sorry to butt in.
I'm wondering if we gain anything by having this by env var configured. I think everything would still work in all environments if we just set config.assets.prefix = "/assets/manuals-publisher" which would save the complexity of this becoming part of environmental configuration.
I'd also somewhat wonder if it was slightly neater to keep the path as the Rails defaults "/assets" and use the web-server config to proxy that to your bucket location, but I'm guessing the horse might have bolted on that?

Sorry as my Ruby knowledge is not great - changing the default to config.assets.prefix = "/assets/manuals-publisher" will mean a change to the way the current EC2 gets its assets, from:
https://manuals-publisher.integration.publishing.service.gov.uk/assets/application-718198c0533914125bdeb775e5500631bad6333ddf463ac4c89af5eae51dcefa.js
to
https://manuals-publisher.integration.publishing.service.gov.uk/assets/colleections-publisher/application-718198c0533914125bdeb775e5500631bad6333ddf463ac4c89af5eae51dcefa.js
personally io would like to avoid that with this change.

Yup would mean that the asset URLs change in EC2 but would save us having two sets of URLs. What would your concern be about changing them in EC2?
My concern is that by not changing it everywhere we actually make things more complicated by having something configurable and different between environments, which - based on past precedent - could get left around as a complication for years.

Yup would mean that the asset URLs change in EC2 but would save us having two sets of URLs. What would your concern be about changing them in EC2?
My concern is that by not changing it everywhere we actually make things more complicated by having something configurable and different between environments, which - based on past precedent - could get left around as a complication for years.

My concern is around changing the default behaviour which may impact in away i can't tell from initials tests and may not be covered by our test suite(Smokey) etc, baring in mind i am unsure how the current EC2 platform works with Assets.
You concern is totally valid one - if you are happy to test the change in ec2 alongside me  then i would be happy to try your suggestion.

Yup would mean that the asset URLs change in EC2 but would save us having two sets of URLs. What would your concern be about changing them in EC2?
My concern is that by not changing it everywhere we actually make things more complicated by having something configurable and different between environments, which - based on past precedent - could get left around as a complication for years.

My concern is around changing the default behaviour which may impact in away i can't tell from initials tests and may not be covered by our test suite(Smokey) etc, baring in mind i am unsure how the current EC2 platform works with Assets.
You concern is totally valid one - if you are happy to test the change in ec2 alongside me then i would be happy to try your suggestion.

Yup sure. I'm happy to help you test it.

I'm wondering if we gain anything by having this by env var configured. I think everything would still work in all environments if we just set config.assets.prefix = "/assets/manuals-publisher" which would save the complexity of this becoming part of environmental configuration.

That's a great suggestion! If we can just set assets.prefix without any side effects in Puppet land then yeah let's ditch the env var - sounds like a win to me 👍 (Now that you mention it, I vaguely remember we chatted about this ages ago but I must have forgotten in the meantime 😅)

I'd also somewhat wonder if it was slightly neater to keep the path as the Rails defaults "/assets" and use the web-server config to proxy that to your bucket location, but I'm guessing the horse might have bolted on that?

Ah I think I can see where you're coming from on this one, but there are some compelling reasons for configuring this in Rails rather than further upstream in the request path.

Rewriting these URLs upstream in order not to change the Rails default adds a little bit of unnecessary complexity to system vs. the least-surprise option of having the paths stay the same all the way through (manuals-publisher.publishing.service.gov.uk/assets/manuals-publisher/this-is-fine.gif goes to the same path on the backend and the same path on the app pod. Not a big deal by itself, though it does make it just that little bit harder to understand and faultfind the serving path. The real downside is that this fluffy gremlin would multiply when we come to put the publisher apps behind the CDN and serve assets via the CDN->S3 fast path instead of going via the origin LB and app nginx. So there's also some loss of generality/flexibility, which leads to accretion of more complexity over time.
nginx config is notoriously hard to debug, test and reason about (because the language has more than its fair share of quirks and foot-cannons and there's little in the way of observability / debugging tools in the OSS version). It therefore pays to keep a tight rein on complexity there and avoid introducing any logic unless we're pretty convinced that it's the lesser of evils.
This use case seems to me a good fit for Rails's assets.prefix and friends, whose purpose is presumably to provide the flexibility to support things like having multiple apps behind a CDN or other shared L7 routing components, or indeed any scenario where Rails isn't directly involved in serving assets.
We don't have any to gain by not making use of Rails's assets.prefix setting, as far as I can tell. Am I missing something?

That's a great suggestion! If we can just set assets.prefix without any side effects in Puppet land then yeah let's ditch the env var - sounds like a win to me 👍 (Now that you mention it, I vaguely remember we chatted about this ages ago but I must have forgotten in the meantime 😅)

Yup. Puppet currently configures nginx to set files in /assets to have long expiry times and gzip encoding. As this change is just a different specificity within that directory they'll continue to be served with the same header.

Ah I think I can see where you're coming from on this one, but there are some compelling reasons for configuring this in Rails rather than further upstream in the request path.

Rewriting these URLs upstream in order not to change the Rails default adds a little bit of unnecessary complexity to system vs. the least-surprise option of having the paths stay the same all the way through (where e.g. manuals-publisher.publishing.service.gov.uk/assets/manuals-publisher/this-is-fine.gif goes to the same path on the backend and the same path on the app pod). Not a big deal by itself, though it does make it just that little bit harder to understand and faultfind the serving path. The real downside is that this small fluffy gremlin would multiply when we come to put the publisher apps behind the CDN and serve assets via the CDN->S3 fast path instead of going via the origin LB and app nginx. So there's also some loss of generality/flexibility, which leads to accretion of more complexity over time.
nginx config is notoriously hard to debug, test and reason about (because the language has more than its fair share of quirks and foot-cannons and there's little in the way of observability / debugging tools in the OSS version). It therefore pays to keep a tight rein on complexity there and avoid introducing any logic unless we're pretty convinced that it's the lesser of evils.
This use case seems to me a good fit for Rails's assets.prefix and friends, whose purpose is presumably to provide the flexibility to support things like having multiple apps behind a CDN or other shared L7 routing components, or indeed any scenario where Rails isn't directly involved in serving assets.
As far as I can tell, we don't have anything to gain by not making use of Rails's assets.prefix setting. (Do we? Am I missing something?)

Sure, that all sounds quite reasonable 👍 And can see how it's more 12 factor.
My concerns were rather modest: felt like a lower level part of stack was dictating a higher level which felt like a potentially delicate coupling and, on the extremely modest, it just looks a bit weird that you have path that then repeats a chunk of the hostname, which feels like superfluous information.

This can now be closed due to:
https://github.com/alphagov/govuk-puppet/pull/11945
https://github.com/alphagov/manuals-publisher/pull/2004#pullrequestreview-1227877337


Add document pandoc-coressref dependency

This came up as an undocumented dependency in our tutorial run through today
Signed-off-by: Shon Feder<EMAIL_ADDRESS>

Addresses https://github.com/informalsystems/themis-contract/issues/83#issuecomment-705768312


BUG: question is not visible on FAQ page and also logo is not visible

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
question is not visible on FAQ page. Background color and font color is same. Also logo is not visible.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Sayak-Bhunia Kindly assign me this issue under GSSOC'24


Implementation class of the Memory interface, does not support serialization and deserialization.

Please do a quick search on GitHub issues first, there might be already a duplicate issue for the one you are about to create.
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:
Bug description
deserialization. Currently, ChatMemory only implements a memory-based dialogue cache storage. I wanted to implement a Redis-based cache for Memory in my project, but I encountered a problem: the implementation classes of the Memory interface do not implement the Serializable interface, which causes failures in accessing Redis.
Environment
Spring AI 1.0.0-SNAPSHOT
Steps to reproduce
step1 :
`@Slf4j
public class RedisChatMemory implements ChatMemory {
private static final String PREFIX = "chat:";

@Override
public void add(String conversationId, List<Message> messages) {
    messages.forEach(message -> RedisUtils.lSet(PREFIX + conversationId, message, CommonConst.CHAT_EXPIRE_TIME));
}

@Override
public List<Message> get(String conversationId, int lastN) {
    List<Message> messages = RedisUtils.lGet(PREFIX + conversationId, -lastN, -1);
    log.info("history conversation :{}", JSONObject.toJSONString(messages));
    return messages;
}

@Override
public void clear(String conversationId) {
    RedisUtils.del(PREFIX + conversationId);
}

}`
Step2:
Runtime error
Expected behavior
Support for Redis-based session storage

i also got this issue

@lvchzh @canonxu has this issue been resolved in the current milestone release of Spring AI?

Hi.  There is an implementation of the ChatMemory interface for Cassandra and there is a PR for pgvector.  That said, we would like to provide an impelmentation that delgates to Spring's Cache abstraction along the lines of what was done in llamaindex.  I'll create a new issue and post it back here.


HDH 178 removed undefined warnings

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[

] Optional Screen Shoot.

Ty!

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


CI: Increased flannel wait

Description
This PR increase the flannel wait time

/rebase test=true

/merge


AttributeError: 'LossScaleOptimizerV3' object has no attribute '_variables'

Issue
With TF 2.11, the mixed precision and model-checkpoint callback don't work properly in combined.
import tensorflow as tf
from tensorflow import keras
keras.mixed_precision.set_global_policy("mixed_float16")

def get_model():
    model = keras.Sequential()
    model.add(keras.layers.Dense(1, input_dim=784))
    model.compile(
        optimizer=keras.optimizers.RMSprop(learning_rate=0.1),
        loss="mean_squared_error",
        metrics=["mean_absolute_error"],
    )
    return model

# Load example MNIST data and pre-process it
(x_train, y_train), (x_test, y_test) = tf.keras.datasets.mnist.load_data()
x_train = x_train.reshape(-1, 784).astype("float32") / 255.0
x_test = x_test.reshape(-1, 784).astype("float32") / 255.0

model = get_model()
model.fit(
    x_train,
    y_train,
    batch_size=128,
    epochs=3,
    verbose=1,
    validation_split=0.5,
    callbacks=[keras.callbacks.ModelCheckpoint(filepath='model.h5')],
)

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[8], line 2
      1 model = get_model()
----> 2 model.fit(
      3     x_train,
      4     y_train,
      5     batch_size=128,
      6     epochs=3,
      7     verbose=1,
      8     validation_split=0.5,
      9     callbacks=[keras.callbacks.ModelCheckpoint(filepath='model.h5')],
     10 )

File /opt/conda/lib/python3.10/site-packages/keras/utils/traceback_utils.py:70, in filter_traceback.<locals>.error_handler(*args, **kwargs)
     67     filtered_tb = _process_traceback_frames(e.__traceback__)
     68     # To get the full stack trace, call:
     69     # `tf.debugging.disable_traceback_filtering()`
---> 70     raise e.with_traceback(filtered_tb) from None
     71 finally:
     72     del filtered_tb

File /opt/conda/lib/python3.10/site-packages/keras/optimizers/optimizer_experimental/optimizer.py:775, in _BaseOptimizer.variables(self)
    773 def variables(self):
    774     """Returns variables of this optimizer."""
--> 775     return self._variables

AttributeError: 'LossScaleOptimizerV3' object has no attribute '_variables'

The code works in TF 2.10, 2.12. But to use TF 2.11, what are the fixes can be used here?

@innat,
Have you got the chance to take a look at this related https://github.com/keras-team/keras/pull/17225 where the PR delegates finalize_variable_values() in LossScaleOptimizerV3 to the wrapped optimizer and also it fixes the exponential moving averages when used together with mixed precision. Also please  take a look at this issue for reference.
https://github.com/keras-team/keras/issues/17275
Thank you!

@tilakrayal
Thanks for the update. https://github.com/keras-team/keras/issues/17275 and https://github.com/horovod/horovod/issues/3807 are similar. Both are closed as the issue don't appear in TF > 2.11. But to use TF 2.11, what are the fixes here?

@innat
Workarounds would be either:

Use the saved model format
Save the weights only


fix: update eventarc storage name

Uses "Cloud Storage" instead of "GCS" for Eventarc Audit quickstart per branding guidelines.
See internal b/180109929

(+ Averi who reviewed similar PRs)


Fix component in erlang repository

IMHO this is an Obvious Fix

@sagikazarmark Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@sagikazarmark This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.

Breaking Travis seems unrelated?

There is no CI for this repo although at some point there was an attempt, so I disabled PR checks.

Thank you!


IntelliSense / AutomaticTypeAcquisition  / tsserver / AutoImportSuggestions broken

VSCode Version: Code 1.19.1 (0759f77bb8d86658bc935a10a64f6182c5a1eeba, 2017-12-19T09:46:23.884Z)
OS Version: Windows_NT x64 6.1.7601
Extensions: none

Steps to Reproduce:

Start VS Code .
Type name of Component to auto import. / Hoover over React Element to show IntelliSense.

Suddenly the IntelliSense, AutomaticTypeAcquisition  and AutoImportSuggestions features are broken on all my VS Code installations and react/nodejs projects.
As workaround to fix AutomaticTypeAcquisition and IntelliSense I am using manual type import via "npm install --save @types/enzyme @types/jest @types/react".
VS Code Settings
"typescript.autoImportSuggestions.enabled": true,
"typescript.disableAutomaticTypeAcquisition": false,

VS Code TypeScript debug log
[Info  - 21:50:29] Using tsserver from: c:\DevProgramme\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib
[Info  - 21:50:29] TSServer log file: C:\Users\Simon\AppData\Local\Temp\vscode-tsserver-log-HEHJ3W\tsserver.log
[Info  - 21:50:29] Forking TSServer
PATH: C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;D:\DevProgramme\nodejs\;C:\Program Files\nodejs\;C:\DevProgramme\Microsoft VS Code\bin;C:\Users\Simon\AppData\Roaming\npm
[Info  - 21:50:30] Started TSServer

tsserver.log
Info 0    [21:50:32.33] Provided types map file "c:/DevProgramme/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/tsserver.js/../typesMap.json" doesn't exist
Info 1    [21:50:32.39] Binding...
Info 2    [21:50:32.127] request:
    {"seq":0,"type":"request","command":"configure","arguments":{"hostInfo":"vscode"}}
Info 3    [21:50:32.133] Host information vscode
Info 4    [21:50:32.134] response:
    {"seq":0,"type":"response","command":"configure","request_seq":0,"success":true}
Perf 5    [21:50:32.136] 0::configure: async elapsed time (in milliseconds) 12.3566
Info 6    [21:50:32.138] request:
    {"seq":1,"type":"request","command":"compilerOptionsForInferredProjects","arguments":{"options":{"module":"CommonJS","target":"ES6","allowSyntheticDefaultImports":true,"allowNonTsExtensions":true,"allowJs":true,"jsx":"Preserve","checkJs":false,"experimentalDecorators":false}}}
Info 7    [21:50:32.143] Scheduled: *refreshInferredProjects*
Perf 8    [21:50:32.144] 1::compilerOptionsForInferredProjects: elapsed time (in milliseconds) 5.4012
Info 9    [21:50:32.144] response:
    {"seq":0,"type":"response","command":"compilerOptionsForInferredProjects","request_seq":1,"success":true,"body":true}
Info 10   [21:50:32.145] request:
    {"seq":2,"type":"request","command":"open","arguments":{"file":"c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js","fileContent":"import React from 'react';\r\nimport { NavLink } from 'react-router-dom';\r\nimport classes from './NavigationItem.css'\r\n\r\nconst navigationItem = (props) => (\r\n    <li className={classes.NavigationItem}>\r\n        <NavLink\r\n            activeClassName={classes.active}\r\n            to={props.link}\r\n            exact={props.exact}\r\n        >\r\n            {props.children}\r\n        </NavLink>\r\n        \r\n    </li>\r\n);\r\n\r\nexport default navigationItem;","scriptKindName":"JS","projectRootPath":"c:\\Projekte\\React\\my-nodejs-backend"}}
Info 11   [21:50:32.152] Search path: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem
Info 12   [21:50:32.156] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/tsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 13   [21:50:32.157] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/jsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 14   [21:50:32.157] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/tsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 15   [21:50:32.158] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/jsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 16   [21:50:32.158] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/tsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 17   [21:50:32.159] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/jsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 18   [21:50:32.159] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/tsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 19   [21:50:32.159] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/jsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 20   [21:50:32.160] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/tsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 21   [21:50:32.160] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/jsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 22   [21:50:32.161] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json Currently impacted open files: RootsOfInferredProjects:  OtherOpenFiles: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js Status: File added to open files impacted by this config file
Info 23   [21:50:32.161] For info: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js :: Config file name: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json
Info 24   [21:50:32.324] Opened configuration file c:/Projekte/React/my-nodejs-backend/client/tsconfig.json
Info 25   [21:50:32.568] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Config file for the program
Info 26   [21:50:32.573] DirectoryWatcher recursive:: Added: PathInfo: c:/projekte/react/my-nodejs-backend/client Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Wild card directory
Info 27   [21:50:32.574] c for path c:/projekte/react/my-nodejs-backend/client not found in cache...
Info 28   [21:50:32.574] Starting C:\DevProgramme\Microsoft VS Code\Code.exe with args:
    ["c:\\DevProgramme\\Microsoft VS Code\\resources\\app\\extensions\\node_modules\\typescript\\lib/watchGuard.js","c:/projekte/react/my-nodejs-backend/client"]
Info 29   [21:50:33.252] WatchGuard for path c:/projekte/react/my-nodejs-backend/client returned: OK
Info 30   [21:50:33.261] Starting updateGraphWorker: Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json
Info 31   [21:50:33.382] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Directory of Failed lookup locations in module resolution
Info 32   [21:50:33.382] watchDirectory for c:/Projekte/React/my-nodejs-backend/client uses cached drive information.

Info 43   [21:50:35.414] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/node_modules Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Directory of Failed lookup locations in module resolution
Info 44   [21:50:35.414] watchDirectory for c:/Projekte/React/node_modules uses cached drive information.
Info 45   [21:50:35.449] FileWatcher:: Added: PathInfo<EMAIL_ADDRESS>Project:  WatchType: Closed Script info
Info 46   [21:50:35.472] FileWatcher:: Added: PathInfo<EMAIL_ADDRESS>Project:  WatchType: Closed Script info
Info 47   [21:50:35.579] FileWatcher:: Added: PathInfo<EMAIL_ADDRESS>Project:  WatchType: Closed Script info
Info 48   [21:50:35.618] FileWatcher:: Added: PathInfo<EMAIL_ADDRESS>Project:  WatchType: Closed Script info
Info 49   [21:50:35.659] FileWatcher:: Added: PathInfo: c:/DevProgramme/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.d.ts Project:  WatchType: Closed Script info
Info 50   [21:50:37.394] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/node_modules/@types Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Type root directory
Info 51   [21:50:37.394] watchDirectory for c:/Projekte/React/my-nodejs-backend/client/node_modules/@types uses cached drive information.
Info 52   [21:50:37.395] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/node_modules/@types Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Type root directory
Info 53   [21:50:37.395] watchDirectory for c:/Projekte/React/my-nodejs-backend/node_modules/@types uses cached drive information.
Info 54   [21:50:37.395] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/node_modules/@types Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json WatchType: Type root directory
Info 55   [21:50:37.395] watchDirectory for c:/Projekte/React/node_modules/@types uses cached drive information.
Info 56   [21:50:37.397] Finishing updateGraphWorker: Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json structureChanged: true Elapsed: 4136ms
Info 57   [21:50:37.400] Starting updateGraphWorker: Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json
Info 58   [21:50:37.418] Finishing updateGraphWorker: Project: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json structureChanged: false Elapsed: 18ms
Info 59   [21:50:37.425] event:
    {"seq":0,"type":"event","event":"telemetry","body":{"telemetryEventName":"projectInfo","payload":{"projectId":"8fc63d458a21889a79d7c094ee75568c","fileStats":{"js":0,"jsx":0,"ts":0,"tsx":0,"dts":13},"compilerOptions":{},"typeAcquisition":{"enable":false,"include":false,"exclude":false},"extends":false,"files":false,"include":false,"exclude":false,"compileOnSave":false,"configFileName":"tsconfig.json","projectType":"configured","languageServiceEnabled":true,"version":"2.6.2"}}}
Info 60   [21:50:37.429] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 61   [21:50:37.430] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 62   [21:50:37.430] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 63   [21:50:37.431] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 64   [21:50:37.431] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 65   [21:50:37.431] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 66   [21:50:37.432] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 67   [21:50:37.432] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 68   [21:50:37.432] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 69   [21:50:37.432] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 70   [21:50:37.432] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 71   [21:50:37.433] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 72   [21:50:37.433] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 73   [21:50:37.433] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 74   [21:50:37.433] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 75   [21:50:37.434] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 76   [21:50:37.434] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 77   [21:50:37.434] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 78   [21:50:37.434] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 79   [21:50:37.434] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 80   [21:50:37.434] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 81   [21:50:37.435] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/components/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 82   [21:50:37.435] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/components/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 83   [21:50:37.436] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/components/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 84   [21:50:37.436] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 85   [21:50:37.436] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 86   [21:50:37.437] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 87   [21:50:37.437] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/src/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 88   [21:50:37.437] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/src/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 89   [21:50:37.438] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/src/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 90   [21:50:37.438] ConfigFilePresence:: Current Watches: Config file for the program:: File: c:/Projekte/React/my-nodejs-backend/client/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 91   [21:50:37.438] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/client/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 92   [21:50:37.438] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/client/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 93   [21:50:37.439] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/client/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 94   [21:50:37.439] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 95   [21:50:37.439] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 96   [21:50:37.440] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 97   [21:50:37.440] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/my-nodejs-backend/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 98   [21:50:37.440] FileWatcher:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 99   [21:50:37.440] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/my-nodejs-backend/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 100  [21:50:37.441] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 101  [21:50:37.441] FileWatcher:: Added: PathInfo: c:/Projekte/React/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 102  [21:50:37.441] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 103  [21:50:37.442] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/React/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 104  [21:50:37.442] FileWatcher:: Added: PathInfo: c:/Projekte/React/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 105  [21:50:37.442] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/React/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 106  [21:50:37.442] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 107  [21:50:37.443] FileWatcher:: Added: PathInfo: c:/Projekte/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 108  [21:50:37.444] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 109  [21:50:37.444] ConfigFilePresence:: Current Watches: :: File: c:/Projekte/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 110  [21:50:37.444] FileWatcher:: Added: PathInfo: c:/Projekte/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 111  [21:50:37.445] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/Projekte/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 112  [21:50:37.445] ConfigFilePresence:: Current Watches: :: File: c:/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 113  [21:50:37.445] FileWatcher:: Added: PathInfo: c:/tsconfig.json Project:  WatchType: Config file for the inferred project root
Info 114  [21:50:37.446] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/tsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 115  [21:50:37.446] ConfigFilePresence:: Current Watches: :: File: c:/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Open file was set as Inferred root
Info 116  [21:50:37.446] FileWatcher:: Added: PathInfo: c:/jsconfig.json Project:  WatchType: Config file for the inferred project root
Info 117  [21:50:37.446] ConfigFilePresence:: Current Watches: Config file for the inferred project root:: File: c:/jsconfig.json Currently impacted open files: RootsOfInferredProjects: c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js OtherOpenFiles:  Status: Updated the callback
Info 118  [21:50:37.448] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 119  [21:50:37.489] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/my-nodejs-backend Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 120  [21:50:37.490] watchDirectory for c:/Projekte/React/my-nodejs-backend uses cached drive information.
Info 121  [21:50:37.530] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 122  [21:50:37.531] watchDirectory for c:/Projekte/React/node_modules uses cached drive information.
Info 123  [21:50:37.534] DirectoryWatcher recursive:: Added: PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 124  [21:50:37.534] watchDirectory for C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules uses cached drive information.

Info 140  [21:50:40.368] DirectoryWatcher recursive:: Added: PathInfo: c:/Projekte/React/node_modules/@types Project: /dev/null/inferredProject1* WatchType: Type root directory
Info 141  [21:50:40.368] watchDirectory for c:/Projekte/React/node_modules/@types uses cached drive information.

Info 168  [21:50:40.406] Project '/dev/null/inferredProject1*' (Inferred) 0
Info 168  [21:50:40.407] 	Files (23)
	c:/DevProgramme/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es6.d.ts
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>	c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Info 168  [21:50:40.407] -----------------------------------------------
Info 168  [21:50:40.407] Open files:
Info 168  [21:50:40.407] 	c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js
Info 168  [21:50:40.408] got projects updated in background, updating diagnostics for c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js
Info 169  [21:50:40.411] event:
    {"seq":0,"type":"event","event":"projectsUpdatedInBackground","body":{"openFiles":["c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js"]}}
Info 170  [21:50:40.644] Sending request:
    {"projectName":"/dev/null/inferredProject1*","fileNames":["c:/DevProgramme/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es6.d.ts","c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js","c:/Projekte/React/my-nodejs-backend/node_modules/@types/node/inspector.d.ts","c:/Projekte/React/my-nodejs-backend/node_modules/@types/node/index.d.ts","c:/Projekte/React/my-nodejs-backend/node_modules/@types/mime/index.d.ts","c:/Projekte/React/my-nodejs-backend/node_modules/@types/express/index.d.ts","c:/Projekte/React/my-nodejs-backend/node_modules/@types/body-parser/index.d.ts"],"compilerOptions":{"module":1,"target":2,"allowSyntheticDefaultImports":true,"allowNonTsExtensions":true,"allowJs":true,"jsx":1,"checkJs":false,"experimentalDecorators":false,"noEmitForJsFiles":true,"maxNodeModuleJsDepth":2},"typeAcquisition":{"enable":true,"include":[],"exclude":[]},"unresolvedImports":["child_process","crypto","dns","events","fs","http","net","querystring","readline","stream","tls","url"],"projectRootPath":"","kind":"discover"}
Info 171  [21:50:40.652] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 172  [21:50:40.652] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* structureChanged: false Elapsed: 0ms
Info 173  [21:50:40.659] event:
    {"seq":0,"type":"event","event":"syntaxDiag","body":{"file":"c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js","diagnostics":[]}}
Info 174  [21:50:40.664] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 175  [21:50:40.707] DirectoryWatcher recursive:: Elapsed: 43ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 176  [21:50:40.707] request:
    {"seq":3,"type":"request","command":"geterr","arguments":{"delay":0,"files":["c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js"]}}
Perf 177  [21:50:40.710] 3::geterr: async elapsed time (in milliseconds) 2.6832
Info 178  [21:50:40.711] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 179  [21:50:40.711] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* structureChanged: false Elapsed: 0ms
Info 180  [21:50:40.712] event:
    {"seq":0,"type":"event","event":"syntaxDiag","body":{"file":"c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js","diagnostics":[]}}
Info 181  [21:50:40.713] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 182  [21:50:40.714] DirectoryWatcher recursive:: Elapsed: 1ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 183  [21:50:40.714] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/README.md PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 184  [21:50:40.714] DirectoryWatcher recursive:: Elapsed: 0ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/README.md PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 185  [21:50:40.715] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/index.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 186  [21:50:40.736] DirectoryWatcher recursive:: Elapsed: 21ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/index.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 187  [21:50:40.736] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/package.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 188  [21:50:40.746] DirectoryWatcher recursive:: Elapsed: 10ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/package.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 189  [21:50:40.747] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/package.json.1156306425 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 190  [21:50:40.747] DirectoryWatcher recursive:: Elapsed: 0ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/package.json.1156306425 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 191  [21:50:40.747] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/package.json.1156306425 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 192  [21:50:40.747] DirectoryWatcher recursive:: Elapsed: 0ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351/package.json.1156306425 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 193  [21:50:40.748] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry/index.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 194  [21:50:40.758] DirectoryWatcher recursive:: Elapsed: 10ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry/index.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 195  [21:50:40.758] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry/README.md PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 196  [21:50:40.759] DirectoryWatcher recursive:: Elapsed: 0ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry/README.md PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 197  [21:50:40.759] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry/package.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 198  [21:50:40.766] DirectoryWatcher recursive:: Elapsed: 7ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry/package.json PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 199  [21:50:40.766] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 200  [21:50:40.784] DirectoryWatcher recursive:: Elapsed: 18ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 201  [21:50:40.785] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 202  [21:50:40.785] DirectoryWatcher recursive:: Elapsed: 0ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging/types-registry-33b27351 PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 203  [21:50:40.786] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 204  [21:50:40.851] DirectoryWatcher recursive:: Elapsed: 65ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/types-registry PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 205  [21:50:40.851] DirectoryWatcher recursive:: Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 206  [21:50:40.867] DirectoryWatcher recursive:: Elapsed: 16ms Trigger: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/.staging PathInfo: C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules Project: /dev/null/inferredProject1* WatchType: Directory of Failed lookup locations in module resolution
Info 207  [21:50:40.871] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 208  [21:50:40.871] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* structureChanged: false Elapsed: 0ms
Info 209  [21:50:40.872] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 210  [21:50:40.872] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* structureChanged: false Elapsed: 0ms
Info 211  [21:50:40.887] event:
    {"seq":0,"type":"event","event":"semanticDiag","body":{"file":"c:/Projekte/React/my-nodejs-backend/client/src/components/Navigation/NavigationItems/NavigationItem/NavigationItem.js","diagnostics":[]}}
Info 212  [21:50:40.887] event:
    {"seq":0,"type":"event","event":"requestCompleted","body":{"request_seq":3}}
Info 213  [21:50:41.20] Received response:
    {"projectName":"/dev/null/inferredProject1*","typeAcquisition":{"enable":true,"include":[],"exclude":[]},"compilerOptions":{"module":1,"target":2,"allowSyntheticDefaultImports":true,"allowNonTsExtensions":true,"allowJs":true,"jsx":1,"checkJs":false,"experimentalDecorators":false,"noEmitForJsFiles":true,"maxNodeModuleJsDepth":2},"typings":["C:/Users/Simon/AppData/Local/Microsoft/TypeScript/2.6/node_modules/@types/node/index.d.ts"],"unresolvedImports":["child_process","crypto","dns","events","fs","http","net","querystring","readline","stream","tls","url"],"kind":"action::set"}
Info 214  [21:50:41.23] Scheduled: /dev/null/inferredProject1*
Info 215  [21:50:41.23] Scheduled: *refreshInferredProjects*
Info 216  [21:50:41.273] Running: /dev/null/inferredProject1*
Info 217  [21:50:41.273] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 218  [21:50:41.286] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* structureChanged: false Elapsed: 13ms
Info 219  [21:50:41.286] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 220  [21:50:41.288] FileWatcher:: Added: PathInfo<EMAIL_ADDRESS>Project:  WatchType: Closed Script info
Info 221  [21:50:41.834] FileWatcher:: Added: PathInfo<EMAIL_ADDRESS>Project:  WatchType: Closed Script info
Info 222  [21:50:42.223] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* structureChanged: true Elapsed: 936ms
Info 223  [21:50:42.223] Running: *refreshInferredProjects*
Info 224  [21:50:42.224] refreshInferredProjects: updating project structure from ...

 @SimonScheidler Do you still see this issue in the latest vscode insiders

@mjbvz Seems to be fixed in the latest vscode insiders.

Thanks. Let me know if you see this again


error when connect and try to publish

FatalErrorException in Client.php line 208: Call to undefined method LibMQTT\Client::writeString()

This problem is hopefully now fixed on 0.2.1 version. Atleast it works (tm) on rabbitmq @ travis-ci  :)