Add flag to disable Type Inference for variables, Force to declare type

Suggestion
I would like to have a flag that would allow me to disable inference of types when declaring variables and assigning the value of a function:
//An error should be shown in this line:
const x = myFunction(); // inferring the type of x from myFunction can cause a lot of problems!!

//And should be corrected to something like this:
const x : string = myFunction(); // type not inferred, we can check now if the function actually returns a string

Use Cases
When I have a variable declaration and assign the value returned by a function, it infers the type of whatever the function returns:
const x = myFunction(); //Maybe myFunction() returns a string, a number, an array, whatever

If I change the return type to a Promise or to a compatible type, it will not show any warning or error, unless I use methods or properties of x that are not on the new type. This may lead to unwanted results.
Examples

For example, when I have to migrate a function that returned a direct value (string, number, object, etc), to a function that returns a promise:

function myFunction() : Promise<string> { //or async myFunction()...
  ....
  return some_promise;   //Maybe before this returned a string
}
const x = myFunction();  //x was a direct value but Now it is a Promise!!, no warning!
if(x != undefined){      //x will never be undefined now because it is a promise!!
  do_something_important;
}

So, in this case, I forgot to change the code that uses the return value and no warning is shown. That will lead to unwanted results.

Another example: fiddler
If I had previously:

function myFunction() : string { return "some string"}

and then change it to:
function myFunction() : string[] { return ["some string"]}

If I was using this as:
const x = myFunction();
console.log(x.length);

then it will again, not show any warning, but the results will be unwanted.
In these cases, if the compiler would have forced me to declare the variable like:
const x : string = myFunction();

instead of inferring the type of x, then I would have gotten the correct warnings.
I created the question for this after a some research in stackoverflow and a fiddler  test case of the second point.
The noImplicitAny is useless in this case unless you do not initialize variables when declaring them, but this would prevent the use of const. I'm having a lot of these issues specially when migrating code to promises.
Thank you very much!!
Checklist
My suggestion meets these guidelines:

[X] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. new expression-level syntax)

It meets all, the suggestion is to add a flag, that would be disabled by default anyway, and would only check code at compile time.

This feels like it would be better suited to a lint rule. I think this works:
typedef
"typedef": [true, "variable-declaration"]
const x = 3;
   // ^ ERROR: 1:7  typedef  expected variable-declaration: 'x' to have a typedef

Well in my case I need to go to a process to add a library, even if it is just a linter, and besides, I really think this should be a feature in the language itself, we have the noImplicitAny, noImplicitReturns, noImplicitThis, etc, flags, why not have this or something similar?
Also, I was talking about inference when declaring variables that take their value from functions, not sure if type inference from constant values like the one in your example is necessary or even helpful, but for functions it can really make a difference and an external linter should not be needed for this in my opinion.

@frank-orellana Then where do you draw the line between simple type defs and complex ones?
The above code could just as easily be declared like:
let i =0;
// ^ ERROR: 1:5  typedef  expected variable-declaration: 'x' to have a typedef
while(i < 5) { ... }

Hey @Toxicable , I don't really understand your question, and I'm not talking about declaring variables and assigning a constant value like in your example, I'm talking about assigning values from functions, and trying not to rely on linters.
I am not saying your example is not one to take into consideration, but my use case, the one I explain is when you assign the value of a function to a variable when declaring it, that's when things can get confusing. did you see the jsfiddle I posted?
Anyway, If the only way to get this is with an external linter library then what can we do. But I really feel this should be something that should be packed into typescript out of the box,
Thanks!

I agree with @jack-williams - if you find value in this check, tslint has a rule for you. Our philosophy is typically that we want to be able to produce the best types possible with as few annotations as possible. The few issues this prevents aren't worth the extra hassle for most people.


Bridge object is always empty.

Printing bridge object always comes out as empty object and cannot access methods by passing the bridge around. Followed the setup given in the docs. Not sure what's going wrong. However, I am able to access the methods by using the useBridge hook.

Hi 👋
If printing results in an empty object, but using useBridge allows it to function correctly, it can be considered to be working properly. The reason an empty object appears is that the value of the bridge is a proxy, which may not display correctly when printed. However, accessing its properties should work as expected.
javascript
Copy code
bridge.yourMethod(); // okay
const { yourMethod } = useBridge(appBridge); // okay
If both of these are working well, then it is likely functioning as intended.

If only the useBridge hook is working, you might be in an SSR environment like Next.js or Remix. In this case, direct access to the bridge object might fail.
If you are in an SSR environment, it should work fine.
Please give me more information about your environment .. !

The issue is being closed because it is stale.


Stays do not always stay

Hi!
So... as discussed on Slack, I have been having trouble with stays not really having the desired effect all of the time. Indeed, quite often, when I add or remove constraints, variables jump around even though they should not. This have driven me crazy for some time and led to resort to all kinds of hacks. Because I use Rhea via aqt-cassowary [1], this has been very hard to reproduce -- this library usually manipulate the solver in non-deterministic, but in theory correct, orders.
So, finally I have been able to write a test that fails sistematically in my machine here. I have two variations of the test, that execute the sames calls in different order. In one it fails, in the other it passes. Funny thing is, the failing test requires only to change the order in which variables are declared just to make it pass.
 There's been some discussion wether stays should be removed or not. Do you have any strong opinions on this matter?

@hfossli There are some cases where I found it necessary. Because of the bugs Stays have in Rhea I ended up simulating them as a feedback loop with a "edit" constraint that is fed back into a variable. There was some discussion about this on Slack some time ago... I remember proposing a different system where instead of edit and stays we split variables into "input variables" and "output variables". The output ones are similar to the ones we have now, input variables have values that are always set explicitly by the programmer. An input plus a constraint is like and edit. A stay can be achieved by binding an input to an output.

Any progress on this? I tried kiwi but without stays it feels risky since "hacking" in stays is not really desirable in my situation... I'm thinking about swopping it out for Nocte but don't wanna put too much effort into it if there might give other issues.
OT: How is the performance compared to kiwi?

@helmesjo I've removed stays from the 0.3 branch. I couldn't get them to work reliably in the same way as Cassowary does, and for many applications they're not needed anyway. The plan was to add them separately, for example like @ghost described.
If I remember correctly, 0.2 is a bit slower than Kiwi, 0.3 is about as fast. If you already have something working with Kiwi, I'd recommend staying with it.


QG checks (Release 24.08)

QG checks
Please open and fill in this issue in your product repository to document the compliance with our Tractus-X Release Guideline (TRGs)
Show compliance with TRGs by referencing to a tagged link in the respective repository where possible, example: TRG 1.01 (see github.com/eclipse-tractusx/example-repo/tree/1.0.0/README.md)
Close this issue once the compliance with the TRGs has been documented
Committer(s):
Helm Chart Version:
App Version:
Release Management Reference Issue:
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[x] TRG 1.03 appropriate CHANGELOG.md
[x] TRG 1.04 editable static files

TRG 2 Git

[x] TRG 2.01 default branch is named main
[x] TRG 2.03 repository structure
[x] TRG 2.04 leading product repository
[x] TRG 2.05 .tractusx metafile in a proper format
[x] TRG 2.06 Dependabot

TRG 3 Kubernetes

[x] TRG 3.02 persistent volume and persistent volume claim or database dependency (subchart) are in place when needed

TRG 4 Container

[x] TRG 4.01 semantic versioning and tagging
[x] TRG 4.02 base image is agreed
[x] TRG 4.03 image has USER command and Non Root Container
[x] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[x] TRG 4.06 separate notice file for DockerHub has all necessary information
[x] TRG 4.07 root file system is set to read access by default, but can be overwritten by the user

TRG 5 Helm

[x] TRG 5.01 Helm chart requirements
[x] TRG 5.02 Helm chart location in /charts directory and correct structure
[x] TRG 5.03 proper version strategy
[x] TRG 5.04 CPU / MEM resource requests and limits and are properly set
[x] TRG 5.06 Application must be configurable through the Helm chart
[x] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[x] TRG 5.08 Product has a single deployable helm chart that contains all components
[x] TRG 5.09 Helm Test running properly
[x] TRG 5.10 Products need to support 3 versions at a time
[x] TRG 5.11 Upgradeability

TRG 6 Released Helm Chart

[x] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[x] TRG 7.01 Legal Documentation
[x] TRG 7.02 License and copyright header
[x] TRG 7.03 IP checks for project content
[x] TRG 7.04 IP checks for 3rd party content
[x] TRG 7.05 Legal information for distributions
[x] TRG 7.06 Legal information for end user content
[x] TRG 7.07 Legal notice for documentation
[x] TRG 7.08 Legal notice for KIT documentation

TRG 8 Security

[ ] TRG 8.01 Mitigate high and above findings in CodeQL
[x] TRG 8.02 Mitigate high and above findings in KICS
[x] TRG 8.04 Mitigate high and above findings in Trivy
[x] TRG 8.03 No secret findings by GitGuardian or TruffleHog

Hints
Information Sharing

TRG 1 Documentation
TRG 1.01: https://github.com/eclipse-tractusx/policy-hub/blob/v1.1.0-rc.2/README.md
TRG 1.02: https://github.com/eclipse-tractusx/policy-hub/blob/v1.1.0-rc.2/charts/policy-hub/README.md
TRG 1.03: https://github.com/eclipse-tractusx/policy-hub/blob/v1.1.0-rc.2/CHANGELOG.md
TRG 2 Git
TRG 2.03: https://github.com/eclipse-tractusx/policy-hub/tree/v1.1.0-rc.2
TRG 2.04: https://github.com/eclipse-tractusx/policy-hub/blob/b4b2179ca510cdcf20f640caf12966a353203772/.tractusx#L21
TRG 2.05: https://github.com/eclipse-tractusx/policy-hub/blob/v1.1.0-rc.2/.tractusx
TRG 2.06: https://github.com/eclipse-tractusx/policy-hub/security/dependabot
TRG 4 Container
TRG 4.05: service, migrations
TRG 4.06: notice files
TRG 4.07: migrations, service
TRG 5 Helm
TRG 5.01: chart-release, chart
TRG 5.02: chart
TRG 5.03: chart
TRG 5.04: migrations, service
TRG 5.07: dependencies
TRG 5.08: chart
TRG 5.09, 5.10, 5.11: chart test
TRG 6 Released Helm Chart
TRG 6.01: chart-release
TRG 7 Open Source Governance
TRG 7.01, 7.05: LICENSE, LICENSE_non_code, NOTICE, DEPENDECIES, SECURITY, CONTRIBUTING, CODE_OF_CONDUCT


Helm chart : generation of ingress TLS certificates overrides external certificate

Right now, the way the chart is written, if you enable TLS for the ingress, the ingress secrets get populated with self signed certificate. If using an external certificate manager (ex: https://github.com/jetstack/cert-manager), these will be overwritten with an helm update.
Suggested solution: add a generation option toggle for ingress-secret.yaml
Helm Chart Version : 0.1.1

@draeron do you have more details on how to use an external certificate manager in K8s. I'm not familiar with it.
Adding a generation option toggle for ingress-secret.yaml is straightforward.

it's really quite simple, well as simple as tls certificate can be. The service cert-manager (which is installed on the k8s cluster) will connect to acme / let's encrypt to make dns challenge with the authority and once a certificate has been emitted, it will be saved in the secrets specified in the ingress's definition.
The certificate then get renewed automagically when they are close to expire.
More info :
Doc: https://cert-manager.readthedocs.io/en/latest/

Thanks @draeron . BTW, would like to create a Pull Request for this change ?

will do, let me update the readme with some extra infos.

Question @jessehu : i have other various improvements i've been adding the helm chart and i would be happy to push them back to the repository. Would you prefer one pull request with all of them or have them reviewed separately ?
here's the commits :
https://github.com/draeron/harbor/commits/helm-improvement

Fixed by https://github.com/vmware/harbor/pull/4682


A few grammar corrections and an extra loop type.

Added some extra explanation statements, corrected a little grammar and explained another kind of for loop.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi @RujutaKelkar - thank you for catching and fixing these issues! The Guide folder was recently moved and is located under the root repo folder now, so the file you're trying to edit isn't in that location anymore. I'm going to close this and ask if you don't mind, to update your fork and open a new PR with these changes so we can merge. Thanks and happy coding! 🙏


#148476333 nagging feature

What the PR does

Enables user to configure nag time Sends emails to the user when the check is down Adds check on nag mode with a nag icon
Solves the nagging interval for more than one check

How to test it

Run python manage.py sendalerts

Changes Unknown when pulling 2cd42645fdfdde4ece507b961a15ef87c05294a4 on ft-nag-user-148476333 into ** on master**.


feat(go): expose rule's metadata in Go API

Reference issue: #120 & #118

Now that I see an implementation I'm reconsidering the use of JSON as a format for exchanging metadata information. There are some issues with JSON that make it far from ideal:

We lose information about whether a number is actually a float or an integer.
For non-UTF8 strings we are going to get an array of numbers, which will be translated to []float instead of []byte.

When I wrote the tests I noticed that as well, maybe a similar implementation as the original Yara did? Which is what I was originally aiming for when attempting to implement it in the C-API.
struct YR_META
{
  DECLARE_REFERENCE(const char*, identifier);
  DECLARE_REFERENCE(const char*, string);

  int64_t integer;
  int32_t type;
  int32_t flags;
};

I've refactored the C API for obtaining the rule's metadata. See: 9f90eaab37a764cc90c40881fc60e448483bb7bf

There is a slight error with the float variant inside of the YRX_METADATA_VALUE union. When the header file gets generated it makes it into "two or more data types in declared specifier" due to float being a reserved keyword.
While you decide on the new name for the float variant, I shall temporary rename to get the go package working.

There is a slight error with the float variant inside of the YRX_METADATA_VALUE union. When the header file gets generated it makes it into "two or more data types in declared specifier" due to float being a reserved keyword.
While you decide on the new name for the float variant, I shall temporary rename to get the go package working.

Fixed in 497c678cb288dbfdfc12415741e301d724735c97


Adding "stdin" support to upload data to chaos dataset

As of now, chaos client does support file input upload.
chaos -f subdomains.txt

to make it more usable with the flow, I wanted to run other tools like subfinder and upload the output on the go, so next time I can just query those data from chaos dataset instead of running subfinder each time.
subfinder -d ube.com | chaos update

Implemented in #5


feature: Evaluate FUNC6 Binomial Heap

Feature description
CCN: 16 delete_min<EMAIL_ADDRESS>Quite a few tests, but complex enough so as to require more tests likely

Coverage is 93% and just missing lines141-144, 292-294, 368, 391, 399-401
Seems bad.


Reload of https://opennebraska.github.io/landlord/out-of-omaha is 404

Clicking on "Out of Omaha" sends me to https://opennebraska.github.io/landlord/out-of-omaha which loads fine. Then I hit Reload and it's 404. This seems bad, since if we're going to have URLs for each report people will copy and paste those URLs into other websites / emails / whatever, and people who click them will get 404?
Chrome Version 85.0.4183.102 (current)
MacOS 10.15.6 (current)

Trying solution referenced in create react app docs, https://github.com/rafgraph/spa-github-pages

The above solution didn't work. I'll continue looking into it.

Resolved on the second attempt with PR #29


Frequent HTTP 502 Bad Gateway errors from publish.sh

We frequently get publish.sh failures on master. Full context is here:
https://github.com/rubygems/rubygems.org/issues/2074
Linking this issue so we can track it in Sorbet itself.

We changed publishing to be done nightly and from a machine with an elastic IP address, which seems to have made this go away. Going to keep open anyways.


Curious about the status of the Scala API

Thank you for creating this library. I haven't tried it yet but I'm assuming that there is a Scala API for this ?

Hi @redsofa, there is currently no Scala API. Are there any particular parts / workflows that would be useful for you in Scala?

The utility functions to read images and decode them in a distributed fashion sound useful. The fast transfer learning is really neat. I can see that being useful. The UDFS are great. I'm guessing that these are easy enough to write once the other stuff exists in Scala. I would just like to work in Scala and not have to fiddle with PySpark. Am surprised that a Scala API is not the first thing out.

That totally makes sense. The reason a Python API was prioritized was because most deep learning uses happen in Python - e.g. Keras, a popular deep learning framework, is only in Python. However, that is a bit contrary to the usual Spark philosophy of Scala being the core implementation / API, and hence does not serve many of the core Spark users. It really makes sense that things like image handling and transfer learning, which do not expose the underlying deep learning frameworks at all (and thus require no python workflow to use them), should be available in Scala. Thanks so much for bringing this up!

BTW @redsofa feel free to submit a pull request to add support for Scala!

Thank you for open-sourcing this great library! In my view, it absolutely makes sense to develop a Scala API. I actually learned Scala due to Spark, as I considered the language to be preferred by the Spark developers. I would love to see some advances concerning a Scala API for RNNs for NLP, especially Named-Entity Recognition. I guess even the Stanford CoreNLP guys are implementing Tensorflow. So any progress in combining Spark, NLP and Tensorflow in Scala would very, very much appreciated. Thank you for your efforts bringing Deep Learning on Spark to life, hopefully in Scala :-)

A scala API for some of the transformers and estimators is definitely under consideration.
For the high level transformers such as image transformers, or well-known models, it is pretty easy to do if you have some understanding of the scala API of Spark, as the heavy work is done by TensorFrames.
Keras and TensorFlow transformers are much more tied to the python ecosystem though, simply because these libraries are mostly useful in python. For instance, the C++ part of tensorflow does not include automatic derivation and all the optimizers (yet), so a lot of thing would need to be replicated in scala.

Hi guys, any update for Scala APIs at least for parts that don't need any Python packages such as loading images, etc.? Many thanks.

Hello Maziyar, what do you want to do besides loading images? If you just
want to do image manipulation, then you can use Spark 2.4's built-in
support for that, see this ticket for some examples:
https://issues.apache.org/jira/browse/SPARK-22666
Tim
On Fri, Nov 23, 2018 at 6:59 PM Maziyar Panahi<EMAIL_ADDRESS>wrote:

Hi guys, any update for Scala APIs at least for parts that don't need any
Python packages such as loading images, etc.? Many thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/databricks/spark-deep-learning/issues/17#issuecomment-441303947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHPjAZtSWlLm_Xr21ZtREDrkoaqEnHZxks5uyEWGgaJpZM4NzJ5_
.

Hi @thunterdb,
Thanks for the reply. I understand loading images now is possible in Spark 2.4 (or with some workarounds even in 2.3), but most of the Hadoop vendors (Hortonworks, Cloudera, etc.) move to new versions of Spark after a few months.
However, my concerns when it comes to any package/library of Spark are not just supporting some small functionalities for Scala. Is more about not abandoning the language that started it all!
Current situation
The Python language has started to be dominated over Scala in the Spark ecosystem simply because of many packages and libraries most data scientists and researches been using for years. I understand it is easier to build upon that for starting a new project for Spark in the same domain of data science (ML, DL, etc.). However, failing to do the same for Scala the very same language that the entire ecosystem of Spark is built upon and has the fastest performance and most updated APIs is something not acceptable.
Future of Scala in Spark
If everyone keeps doing this and rely on what it was developed before so let's lock down the entire project for Python and give some small functionalities to Scala (which is not the point and it's pretty much useless), pretty soon the Scala is going to be only used for ETL/data engineering and everything related to ML, DL, and AI in the field of data science will be only for Python and R (this is what we see today, but it will be an established fact in future).
I think treating Scala like this is unfortunate and a company like Databricks has some responsibilities to not let the language such as Scala just to be used for only some small data engineering operations in Spark.
PS: Sorry if this sounds unpleasant. I do appreciate all the efforts in an Open Source community no matter what.  I really love Spark/Scala (I learned Scala for Spark!). Also, I am doing Machine learning, deep learning, scientific visualizations in Spark. Though, recently I realized Scala is not the language for any of them compare to Python/R and it doesn't feel good to see it may never be. :)
Thanks again @thunterdb for the reply and I appreciate it. "My comment is not about you, it's more about me :)"

@maziyarpanahi thanks for your expressing your concerns, I had a number of questions along the same line at the Spark Summit. The fact that these questions are being raised is a testament of the universal appeal of Spark across different communities that work with different pieces of the API.
To clarify: Scala is the language with which Spark is written. There is no question that it is here to stay, and the core innovations inside Spark (project hydrogen, continuous processing, data source V2) are all written in scala first, simply because of performance reasons.
That being said, Spark strives at adopting the customs of the different communities it caters to, and at being as transparent as possible in the work of the users. In the space of Deep Learning, as you point out, most of the libraries are accessed in python, which is why the focus of the API has been on serving users who were already proficient in the python ecosystem. There are already some efforts underway for java/scala, such as DeepLearning4J and TensorFrames, and with the stabilization of the hydrogen API, I expect to see some good progress in that area.

@thunterdb Thanks for your reasonable response, I really appreciate it. What you have said absolutely makes sense. I have also seen the efforts by Intel, Microsoft, and others in entering Scala into Machine Learning and Deep Learning that take advantage of Spark ecosystem. To be honest, I have always looked up to Databricks as a leading company when it comes to the roadmap of Spark. Although, Spark is entirely Open Source and can/will go in any direction, Databricks has done a great job to direct the Spark community towards a unified analytics engine since the inception of the company itself.
I think if we can have some sort of awesome-spark-scala list on GitHub to see all the efforts and undergoing projects in ML and DL would be heartwarming and reassure that transforming Scala in Data Science community is a plan for sure.
I feel a lot better now that I heard this from you. It's a long road to go, but as long as we are going down that road I am perfectly fine. (I am by no means a Scala developer compare to pure Scala developers. But there is something about the language that makes me happy!)
Again Timothy, thanks for your time and sorry if I sounded a bit melodramatic.


PHP 5.x support

Just wondering what the plan is re: end of life versions of PHP 5.3/4/5, none of which are supported by PHP. I got caught out by the long array syntax on a PR

I can only repeat that raspberry pi is still on 5.6 as long as stretch-based raspbian has not been released. Don't see any need for versions prior than that though.

I personally encourage every single user of this library to use PHP7+ for a various reasons (performance, security, support) :+1:
That being said, how much would be gained by dropping support for older versions? Note that this is BC break which will have the effect that a non-zero number of users will not be able to upgrade anymore. This leaves us with the question which version we should upgrade to?
Our current focus is on releasing a stable v1.0.0 ASAP, so afaict there are no immediate plans to drop support for older versions any time soon. However, this is something that we may look into for a future release if it provides substantial value :+1:

I believe this has been answered, so I'm closing this for now. Please come back with more details if this issue persists and we can reopen this :+1:
See also https://github.com/reactphp/react/issues/374


Allow kicking off expert for one and manual control for another in MARL env

I wish to press T to kick off an expert running agent 0 and manually control agent 1, but this bug happen!
(By the way, key T is not shown in helper message, but that's OK, please don't add it to helper message until formally release PGDrive v0.2)

Solved in #272


Gardener reconcile/readiness shoot status doesn't reflect the working VPN

What happened:
If the shoot cluster VPN is not reachable and the vpn-seed container inside the kube-apiserver pod produces error logs:
[Wed Jul  3 14:59:19 UTC 2019]: trying to identify the endpoint (load balancer name of vpn-shoot service) myself...
[Wed Jul  3 14:59:19 UTC 2019]: found endpoints: [ <IP_ADDRESS> ]
[Wed Jul  3 14:59:19 UTC 2019]: checking whether port 4314 is open on <IP_ADDRESS> ...
[Wed Jul  3 14:59:22 UTC 2019]: error: port 4314 on <IP_ADDRESS> is not open, can not use it
[Wed Jul  3 14:59:22 UTC 2019]: No tunnel endpoint found

This error is not reflected in the overall shoot cluster status:
$ kubectl -n garden-cluster get shoot
NAME         CLOUDPROFILE   VERSION   SEED           DOMAIN                                 OPERATION   PROGRESS   APISERVER   CONTROL   NODES   SYSTEM   AGE
wir5xvwkm5   region1        1.15.0    seed-region1   wir5xvwkm5.rtr-prblm.shoot.my.domain   Succeeded   100        True        True      True    True     3h47m

And when user want to use kubectl logs or kubectl exec, this operation will timeout and user won't be able to understand why.
What you expected to happen:
I expect to see PROGRESS: 99%, SYSTEM: false, OPERATION: Creating. In addition the gardener dashboard should display the VPN connection issue with logs inside the status modal window.
Environment:

Gardener version: 0.26.1
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration: openstack
Others: dashboard 1.33.0

@adracus WDYT about enhancing the SystemComponents condition to make it only True if the VPN works?

The SystemComponents condition only reflects what the various system component Deployments, StatefulSets and DaemonSets report back - I think that this means that probably our health checks for the VPN are not good enough so its Deployment does not report that it's not working. We'll have to improve that I guess.

Hm, not sure whether that's the correct way. The vpn-shoot deployment itself is fine (it functions as OpenVPN server and is ready and ready to accept incoming connections). It's just that the vpn-seed cannot (yet?) connect to it. I don't think we should include this information in the Deployment status of the vpn-shoot.

I mean I'm just looking at the health-checking code: This code does not have any client to do real checks in the cluster and that's by design - it should see 'declaratively' whether there's an issue or not. In the case of the VPN, I'd probably then rather recommend to have an operator that takes care of setting up the 'network bridge' between Seed and Shoot and that this one is the one thing that can write proper health information into the status of its resource that is then reflected back in the health check.

Hm, I didn't get the motivation for such an "operator". Why should we do this? The VPN is a core component in the Gardener architecture. IMHO there is nothing bad in compiling the health checking logic in the regular care controller. Did I miss something?

This code does not have any client to do real checks in the cluster

I don't get this as well - we have the shoot client when checking the system components. The only thing we need to do is trying to open a port-forward connection (this code exists already as part of the shoot reconciliation flow, we can directly re-use it).

we also don't reflect the state of all extensions in the Shoot, so that also may be a problem with our health checks

Which extensions are you talking about? The addons are part of the health check, right? The newly introduced OS/provider/... extensions are running in the seed and their health should probably be part of the ControllerInstallation status, but that's a different topic anyways.


[5.1] Proposal for handling multiple database slave

Please apply the diff from StyleCI.

Done. Thanks

Sorry, didn't get that. Are you talking about this modification not adding any value ?
Motivation: 1 master - X slaves. At run time, pick a slave at random for all read queries. Very common scenario. Can do the same is config/databases.php , but not sure how php artisan config:cache will behave then.

Please squash to one commit. ;)

Having trouble :( will close this and open new pull :(


how to work with fixed region inpainting

hello, how to work with fixed region inpainting, such as the logo with the fixed position on the video.  I follow your instruction:
CUDA_VISIBLE_DEVICES=0 python tools/video_inpaint.py --frame_dir ./demo/lady-running/frames \
--MASK_ROOT ./demo/lady-running/mask_bbox.png \
--img_size 448 896 --DFC --FlowNet2 --Propagation \
--PRETRAINED_MODEL_1 ./pretrained_models/resnet50_stage1.pth \
--PRETRAINED_MODEL_2 ./pretrained_models/DAVIS_model/davis_stage2.pth \
--PRETRAINED_MODEL_3 ./pretrained_models/DAVIS_model/davis_stage3.pth \
--MS --th_warp 3 --FIX_MAS

But it still does Iter for many minutes. Why it so slow...

I provide several ways for reducing running time:

using single stage model
get th_warp much higher like 10
decrease the resolution of input

However, these tricks will harm the final performance. The running speed depends on many things, like CPUs, memory bus. I'm still working on the more efficient versioin and welcome to any kind of suggestions.


Update ProductOrderItemTest.php

set $beachBall variable to lowercase. Thanks.

Hi @AntonyThorpe thanks for that PR ;)
Do you think, mp3player should also be convertet into mp3Player?

Hi @wernerkrauss, depends on the coding convention followed by this Repository. PSR-1 recommends a consistent way of declaring properties so one way needs to be chosen.  Using camelCase would be consistent when shifting back and forth between PHP & javascript so that would help.  To answer your questions, yes.  Thanks.

Thanks @AntonyThorpe sorry yes I was trying to clean these up over the weekend to fix the lint errors in VSCode.
Looks like we have tests working again! Yay. Looking at the logs, I think fixing Onimay is next on my list, there is a few warnings and errors in PHP 8+


fix path string error

lead to "--preinclude" parameter in xxx.c_opts file error while generate keil/iar project

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: use TextDecorationStyle for SkTextStyle.decorationStyle

I found SkTextStyle.decorationStyle is currently typed as TextDecoration, which should be TextDecorationStyle actually.
This PR just fixes the type and incorrect values used in paper/src/Examples/API/Paragraphs.tsx.

thanks a lot for this, can you sign the CLA?


Randao random extension

Extension implementing a random generator using RANDAO.
I tried to build this as simple and generic as possible, to keep in mind this can be used for different applications that need some randomness.
It's working on Foundry now (Foundry does not set the withdrawalsRoot header) but the random number generated is always the same because the mixHash field from the header (where the randomness is taken from) is always zero.
To install the extension on Foundry you have to use the new create-eth version, which has not been released yet.

Really cool extension @damianmarti !! Only added a couple of nitpicks on the Readme 🙏

Thanks!!


Create an MSBuild SDK for Yardarm projects

Motivation
Allow the creation of projects that dynamically build Yardarm SDKs as
part of an MSBuild pipeline with other projects.
Modifications

Combine Yardarm.Build.Tasks with the new SDK project to generate a
single NuGet package.
Define the SDK props and targets file
Add a test project and include in CI build

Results
Yardarm projects support NuGet restore, build, pack, multi-targeting,
loading in Visual Studio, etc. The SDK may be packaged and uploaded to
NuGet for easy reference.

/merge


UTF-8 error, but bot still run normally

Expected Behavior
Bot run normally without any errors.
Actual Behavior
Sometimes bot throws an UTF-8 error, but still run normally
Your FULL config.json (remove your username, password, gmapkey and any other private info)
http://pastebin.com/4feZt242
Output when issue occurred
http://pastebin.com/7cD9CccT
Steps to Reproduce
Just run the bot
Other Information
OS:
Arch Linux ARM
Branch:
master
Git Commit:
42d670a411b4f8dc9a6206dd10a88cc51744026d
Python Version:
Python 2.7.12

@kureijir Which issue is current #5053 or #5054 ? One or the other is a duplicate, please close the issue your experiencing or don't reuse the same output for both issues


Add icons to Navbar and Add Rate us Option

Is your feature request related to a problem? Please describe.
Hello, my name is A.A.D.Sailaja. I am a Tech Enthusiastic and i'm looking forward to contribute in open source projects. Here in this project i would like to add a rate us option it will allow the user to rate our website and also she can suggest us to improve if any.i would also like to add icons to nav item to make website look Attractive
Can you please assign me this issue under gssoc'24
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

assigning to you @sailaja-adapa, you can start working on it. Also share reference image for your solution before starting to work on it.

yeah okk @Yash636261 Thank you

i would like to make the rate us page in this way i will change it according to our website

try something like this:

Yeah okk i will try my level best

@Yash636261 I want to work on it, can you assign this to me?

@Yash636261 I want to work on it can you please assign it me. I have already worked on such projects and my technical skills include Node , React, Tailwind Css, Bootstrap ,Javascript, MongoDB.

@Yash636261 I would  like to work on this issue please assign it to me

Hi @Yash636261,  could you please assign this issue to me?
Thank you!

@Yash636261 Taral let me fixed this issue.
Assign me


Missing Groups in Fabric FAST

Describe the bug
Required/used Fabric FAST groups are no longer aligned with the Google Cloud setup checklist (https://cloud.google.com/docs/enterprise/setup-checklist).
The following roles are missing:
gcp-logging-admins
gcp logging viewers
gcp-monitoring-admins
gcp developers
I'm fairly new to Fabric FAST. I don't know if it's okay or not. If this is normal, it should probably be mentioned in the bootstrap documentation (at least to avoid issue ticket creation).
Environment
Documentation
To Reproduce
Read https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/blob/master/fast/stages/0-bootstrap/README.md#customizations
Result
Documentation and Source code should be aligned with the official recommandations (https://cloud.google.com/docs/enterprise/setup-checklist).

Yes, we don't use all the roles defined in the checklist.
As an example, in our experience there's no centralized logging or monitoring function, but those are managed for specific contexts (network team has their own dashboards on their part of the org, etc.).  The checklist uses a different approach, where segmentation of contexts via folders is not used but functions are centralized and assigned organization-level roles.
Having those groups created is fine, and they can already be used in FAST via the iam_ variables exposed in several stages like any other normal identity. We only define groups in vaariables when they are actually needed as principals in our IAM bindings, so adding the extra groups would just force more information or edits on users with little actual benefit.
Mentioning this in the README as you suggest on the other hand, is useful and would prevent users puzzling on the differences. :) Would you care to send a PR to the stage 0 README to mention this? Or we can do it of course if you're short on time. Thanks for raising this!

Thank you for the update!


Allow importing of maps as scenes

This needs research. But it would be great if maps could be imported as scenes, probably with matching journal entries on the scene map where PINs were placed.

Great idea, they can be loaded as gridless/no token vision for simplicity.


Segmentation fault

I am trying the solo miner setup with https://github.com/nginnever/zogminer/commit/aa33f140b81a53b03393761763bd448e82636a27
crash is 100% reproducible:
$ ./src/zcash-miner -G
Running the test miner
[OPENCL]:Found suitable OpenCL device [GeForce GTX 960] with<PHONE_NUMBER> bytes of GPU memory
[OPENCL]:Using platform: NVIDIA CUDA
[OPENCL]:Using device: GeForce GTX 960(OpenCL 1.2 CUDA)
[OPENCL]:Printing program log
[OPENCL]:
[OPENCL]:Running Solver...
Step: 1...
Step: 2...
Step: 3...
Step: 4...
Step: 5...
Step: 6...
Step: 7...
Step: 8...
Segmentation fault (core dumped)

sorry. with https://github.com/nginnever/zogminer/commit/aa33f140b81a53b03393761763bd448e82636a27 it doesn't crash.


Phaser.Cameras.Controls.FixedKeyControl is not a constructor

An error in the TypeScript defs

Not sure if this is related to TypeScript definitions or actual implementation in JS.
            var cursors = this.input.keyboard.createCursorKeys();

            var controlConfig = {
                camera: this.cameras.main,
                left: cursors.left,
                right: cursors.right,
                up: cursors.up,
                down: cursors.down,
                speed: 0.5
            };
          this.controls = new Phaser.Cameras.Controls.FixedKeyControl(controlConfig);

gives
Phaser.Cameras.Controls.FixedKeyControl is not a constructor

It's exported as Controls.Fixed in 3.3 (and the full version for 3.4)


example of dynamically changing the definiotn

Is this possible? can you add a sample of how to dynamically change the definition and thus causing a refresh of the text nodes in all of the children.
thanks.

If you use the IntlProvider component to provide the definition file, anytime you (re)render the IntlProvider it will (re)render its tree, which will update any child components with the new definitions.  Thus, in order to have dynamic definitions on the screen, you just need the definition prop to IntlProvider to itself be dynamic.  For example, here is a trivial example that would alternate "Hello" and "Ciao" on the screen every second:
const English = {hello: 'Hello'};
const Italian = {hello: "Ciao"};

class App extends Component {
  state = {
    definition: English
  }

  componentDidMount() {
    setInterval(() => this.setState({definition: this.state.definition === English ? Italian : English}), 1000);
  }

  render(props, {definition}) {
    return (
      <IntlProvider definition={definition}>
        <Text id="hello" />
      </IntlProvider>
    );
  }
}

In a more real-world scenario, you would get the desired language file "key" from something like a users preferences or the browsers language preference, dynamically lazy-load/require the language file, and update state appropriately with the new language file, triggering a rerender.  Something like this:
import defaultLanguage from '../languages/en-us.json';

class App extends Component {

  state = { definition: defaultLanguage };

  componentWillMount() {
    let key = ??? //get preferred language file key somehow

    //use webpack dynamic import if you have all of your language files at build time - could also use fetch or another mechanism to get a remote file if you don't have them at build time
    import(`../languages/${key}.json`).then(definition => this.setState({definition}));
  }

  render(props, {definition}) {
      <IntlProvider definition={definition}>
        <Text id="hello" />
      </IntlProvider>
  }

}

See more about webpack dynamic imports here: https://webpack.js.org/guides/code-splitting/#dynamic-imports

This would be good to add to the README.  If anyone wants to clean it up and update it, that would be helpful

thanks @billneff79 , great example.
Although, this is a bit of simplistic example.
In my case I have complex tree structure that doesn't get re-rendered all the time.
Currently I have one top-level <IntlProvider /> for my entire app, which worked OK for initial one time init.
Should I use multiple <IntlProvider /> so parts which dynamically get's re-rendered will use their own scoped provider?

@OrenMe - you can have nested <IntlProvider /> components at different levels in the tree.  The current behavior of that nesting is that it is purely additive: if a higher-up IntlProvider has key a with value foo and a lower IntlProvider has key a with value bar, then the resulting merge will have key a with value foo.  If the lower IntlProvider has keys that the higher IntlProvider does not have, then they will be added to the merged definition for components to use.
The typical pattern that we use is that each widget we export from a repo is wrapped in an IntlProvider that provides the default language in that repo.  That makes it easy to test the base functionality of a widget.  We then have an Application level repo that imports all of the necessary named widgets and it is itself wrapped in an IntlProvider.  It does not provide anything for our default language, as the base widgets already have that, but it provides all language updates for every widget in alternative languages (e.g Spanish).  Any components that selective render through something like shouldComponentUpdate listen for updates to the language definition file - it's so rare that it's not a big burden.
An alternative you could pursue is a publish-subscribe mechanism (e.g. using mitt for something simple or redux for something more complex if you already have that in your codebase) to reach deep into the your tree structure to inform certain components that they need to re-render because of intl language file changes.
Either way, if you find something that works for you, we'd love to hear about it.  Good luck!

thanks @billneff79 !


Triggering migrations for first time

Background
Earlier in easyengine, all the tables were created from core. When the EE_DB class was initialized, we used to check if ee.sqlite file exists, if not we used to create all tables.
Now since we've moved package specific code to the respective packages, we also moved table creation logic to individual packages in form of migrations. So we now need to run migration after installing ee and after each upgrade.
The problem is in triggering migrations first time after installing ee.
The problem
Triggering migration first time is a problem since we don't know if ee is being run first time.
Unfeasible solutions already thought of

Trigger migrations after installation script

We cannot do that as if someone uses the phar directly, things will break

Trigger migrations when the EE_DB class is initialized(as was done before)

This too cannot be done as migrations now contain logic for both filesystem based migrations and database migrations. So if a command is executed which does not invoke EE_DB but expects the filesystem migrations to be ran, than that command would fail.

Trigger migration if ee.sqlite file is not found

If migrations have been ran previously then ee.sqlite file would be present. There's a case where if the migration was running previously but somehow the process got terminated while executing, then ee.sqlite file would be present but the migrations might not have been ran completely

Possible solutions
So the only solution it seems is to somehow check if migrations are run or not on each ee invoke.
However it can be expensive operation to do as we check migrations from each package and see if it's present in database or not.

One simple solution would be to use a filesystem cache(EE already has this) to store if migrations have been ran. So on each ee run, we'll check in this file if there's a key value pair that indicates ee's migration has been ran. If it has, it'll skip triggering migrations else it will trigger it.
Instead of keeping on filesystem cache, we can create a ee_options table and track if migration has been ran in there.

These are the steps we'll take to handle the triggering of migrations.

[ ] Create options table
[ ] On invocation compare version with version in options table
[ ] Upon successful run of migrations, write new version in options table.

With reference to call taken with all the team members.

Completed in PR https://github.com/EasyEngine/easyengine/pull/1224/


Add --secrets-file option to exec command

This adds a flag to drone exec to pass a yaml file with plaintext secrets, file follows this convention:
secrets:
  SLACK_URL: https://hooks.slack.com/services/whatever/floats/yourboat
  AWS_ACCESS_KEY_ID: loremipsum
  AWS_SECRET_ACCESS_KEY: blahblahblahblah
  AWS_DEFAULT_REGION: us-east-1

I'm introducing a new type directly in the exec file, not sure if it warrants its own type in the drone/yaml package

It definitely makes sense to give the ability to load from file.
I'm using the following library in all the plugins to load environment variables:
https://github.com/joho/godotenv
Which allows the following:
envs, err := godotenv.Read(filename)
for key, val := range envs {

}

I don't have strong opinions on an environment file vs yaml file, but I figured I throw it out there as an option @frapposelli do you have a strong opinion either way? cc @benschumacher since I know you were loading secrets from files in 0.4. Any strong preference?

@bradrydzewski I've just tried to port the same experience I had with the 0.4 client, in my workflow I was loading secrets directly from the YAML plaintext file used to build .drone.sec with drone exec -E <filename>.
I wouldn't mind using an environment file, but I like the fact that I don't have to update all the YAML files I've used on 0.4.

FWIW, docker run has a --env-file param that we refer to in the install docs. I could see copying that over and continuing the pattern as being consistent, but this is not something I feel strongly about. Figured I'd mention the --env-file thing in passing.

I wouldn't mind using an environment file, but I like the fact that I don't have to update all the YAML files I've used on 0.4.

I definitely can sympathize here since it is a pain updating stuff, but at the same time, I'm not sure we should carry the legacy 0.4 yaml format into 0.5 if it can be avoided. The more I think about it, the more I'm in favor of using the environment file.
I should point out that the CLI will automatically look for a .env file in the working directory. So you can already do something like this (just make sure to add .env to your .gitignore)
$ cat .env

DRONE_SECRET=foo=bar,baz=boo

For sourcing secrets from a central file I would therefore recommend we alter the --secret-file  to use the environment file format instead:
envs, err := godotenv.Read(filename)
for key, val := range envs {

}

@bradrydzewski sounds good, I'll update the PR to reflect that.

Just updated the PR and realized that godotenv actually support YAML-style environment file, I've tested the code change with this file format:
SLACK_URL: https://hooks.slack.com/services/whatever/floats/yourboat
AWS_ACCESS_KEY_ID: loremipsum
AWS_SECRET_ACCESS_KEY: blahblahblahblah
AWS_DEFAULT_REGION: us-east-1

and worked flawlessly.

I wouldn't mind using an environment file, but I like the fact that I don't have to update all the YAML files I've used on 0.4.

Yeah, I'm just not sure that we should be making design decisions based on not having to update old files.
Also, is there any need to separate environment vars from secrets during the build process? --env-file would match existing Docker conventions and would set any environment variables, secrets or not.

@gtaylor I would keep the secrets separate from generic environment variables, the --secrets-file option loads the file content into a model.Secret struct, which mimics exactly how the build is run on drone server.

thanks!

🎉 🎉 🎉 🎉 🎉 🎉


typescript-resolvers - Type mismatch with apolloClient's resolvers

Describe the bug
After generating types from my resolvers the resolvers field in new apolloClient() complains for types being mismatched:
Error:(92, 5) TS2322: Type 'Resolvers' is not assignable to type 'Resolvers | Resolvers[] | undefined'.
Type 'Resolvers' is not assignable to type 'Resolvers'.
Property 'Mutation' is incompatible with index signature.
Type 'MutationResolvers<any, {}> | undefined' is not assignable to type '{ [field: string]: Resolver; }'.
Type 'undefined' is not assignable to type '{ [field: string]: Resolver; }'.
To Reproduce
Steps to reproduce the behavior:
Create an apollo client instance with resolvers and a generated resolvers type from codegen.

My GraphQL schema:

directive @client on FIELD

type Mutation {
  sayHi: String!
}

My GraphQL operations:

mutation sayHi {
  sayHi @client
}

My codegen.yml config file:

config:
  withHOC: false
  withHooks: true
  withComponent: false
  hooksImportFrom: "@apollo/react-hooks"
generates:
  src/types/resolvers.ts:
    overwrite: true
    schema: ./local.graphql
    plugins:
      - typescript
      - typescript-resolvers

Expected behavior
The resolver types should match to the apollo one without errors
Environment:

OS:
@graphql-codegen/...:
NodeJS:

Additional context
Apollo's type definition is here: https://github.com/apollographql/apollo-client/blob/version-2.6/packages/apollo-client/src/core/types.ts#L50

Would that work for you?
https://graphql-code-generator.com/docs/plugins/typescript-resolvers#integration-with-apollo-server

As @ardatan said, please try with useIndexSignature: true.
The typescript-resolvers generates a generic resolvers signature, that matches the requirements of graphql.js. Some adjustments needs to be done in order to integrate it with Apollo-server due to differences in the signature. Adding this configuration flags solves that.

Beautiful! thanks!


NOTHING on this page about "Deploying ARM templates" actually EXPLAINS HOW TO DEPLOY ARM templates !!!

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 13086a23-13ee-bea9-c04b-39d8d1d3bc8d
Version Independent ID: 13f6b3cf-b946-cc46-2c15-b01e9d40a634
Content: Templates overview - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/overview.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@markvogt Thank you for your feedback . We will have this reviewed and update the thread.

@markvogt Could you please elaborate your requirement and concerns about the documentation?

@markvogt Looking forward to your response.

@markvogt - thanks for this feedback. I have added links to the articles about deploying templates.


It would be great if it supports various clients, such as grpc, redis, mysql..

Hah..it's nearly an impossible thing. :D.

gRPC had been talked before, but there were no actual needs. gRPC has async client/server API, which might be working with Photon together.
Do you know if the other two have the equivalents?

gRPC had been talked before, but there were no actual needs. gRPC has async client/server API, which might be working with Photon together.
Do you know if the other two have the equivalents?

If we use gRPC async api, then we go back callback mechanism..
redis-plus-plus have async api and partially support c++20 coroutine

gRPC had been talked before, but there were no actual needs. gRPC has async client/server API, which might be working with Photon together.
Do you know if the other two have the equivalents?

Or you mean, call gRPC async then suspend photon and later resume photon in gRPC callback?

gRPC had been talked before, but there were no actual needs. gRPC has async client/server API, which might be working with Photon together.
Do you know if the other two have the equivalents?

Or you mean, call gRPC async then suspend photon and later resume photon in gRPC callback?

Yes, you can use eventfd to communicate between Photon thread and gRPC loop thread, by using Photon's wait_for_fd API.
Or you can pass a Photon semaphore into gRPC's call back and do semaphore.Wait in your caller thread.
The main reason is that gRPC does not allow to run on an external event loop by far.

@jiangdongzi https://github.com/alibaba/PhotonLibOS/pull/424 can be potentially used for redis-cpp


[Templating] SAP react-redux

Describe the bug
watch : Started
info: Microsoft.AspNetCore.SpaServices[0]
      Starting create-react-app server on port 61171...
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
      User profile is available. Using '/Users/lqqu/.aspnet/DataProtection-Keys' as key repository; keys will not be encrypted at rest.
Hosting environment: Development
Content root path: /Users/lqqu/dotnet/mangostano/login
Now listening on: https://localhost:5001
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.
npmfail: Microsoft.AspNetCore.SpaServices[0]
      There might be a problem with the project dependency tree.
      It is likely not a bug in Create React App, but something you need to fix locally.

      The react-scripts package provided by Create React App requires a dependency:

        "eslint": "^6.1.0"

      Don't try to install it manually: your package manager does it automatically.
      However, a different version of eslint was detected higher up in the tree:

        /Users/name/dotnet/mangostano/login/ClientApp/node_modules/eslint (version: 5.16.0)

      Manually installing incompatible versions is known to cause hard-to-debug issues.

To Reproduce
Steps to reproduce the behavior:

SDK 3.0.100
dotnet new reactredux -n login cmd to create a project
using dotnet watch run

Expected behavior
update the eslint version to same with react-scripts.
Screenshots

Additional context
Add any other context about the problem here.
Include the output of dotnet --info

and also fix eslint version mismatch and exec dotnet run and open localhost:5000 will get a another error Failed to compile

@1483523635 Thanks for contacting us.
I can't repro this with RTM bits

I tried this using the RTM container mcr.microsoft.com/dotnet/core/sdk:3.0.100-alpine3.9 for 3.0.100.
I would suggest you do dotnet --info and include the results here, as it is likely you are using the wrong SDK version.
If the problem still persists, let us know.

the problems still exist  and I am not using docker
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.15
 OS Platform: Darwin
 RID:         osx.10.15-x64
 Base Path:   /usr/local/share/dotnet/sdk/3.0.100/

Host (useful for support):
  Version: 3.0.0
  Commit:  7d57652f33

.NET Core SDKs installed:
  3.0.100-preview7-012821 [/usr/local/share/dotnet/sdk]
  3.0.100-preview9-014004 [/usr/local/share/dotnet/sdk]
  3.0.100 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.0-preview7.19365.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview9.19424.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.0-preview7-27912-14 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview9-19423-09 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

@1483523635 Can you include also include the output from node -v and npm -v?
That might help us narrow down your problem.
Does it provide more info if you go to /ClientApp and run react-scripts start from there?

@1483523635 I tried on a Mac and couldn't repro it either. Other things to try are, cleaning the npm cache (this will be somewhat disruptive, as it will force you to download all npm packages you had cached again)

node -v
v12.10.0
npm -v
6.10.3
yarn -v
1.10.1

I goto the ClientApp folder and exec npm run  start , the below is error detail
➜  ClientApp npm run start

><EMAIL_ADDRESS>start /Users/lqqu/dotnet/mangostano/login/ClientApp
> react-scripts start

There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

  "eslint": "^6.1.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:

  /Users/lqqu/dotnet/mangostano/login/ClientApp/node_modules/eslint (version: 5.16.0)

Manually installing incompatible versions is known to cause hard-to-debug issues.

If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.

To fix the dependency tree, try following the steps below in the exact order:

  1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
  2. Delete node_modules in your project folder.
  3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
  4. Run npm install or yarn, depending on the package manager you use.

In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:

  5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
     This may help because npm has known issues with package hoisting which may get resolved in future versions.

  6. Check if /Users/lqqu/dotnet/mangostano/login/ClientApp/node_modules/eslint is outside your project directory.
     For example, you might have accidentally installed something in your home folder.

  7. Try running npm ls eslint in your project folder.
     This will tell you which other package (apart from the expected react-scripts) installed eslint.

If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.

P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/lqqu/.npm/_logs/2019-10-16T10_08_39_815Z-debug.log

@1483523635 Thanks for providing those details.
Are you using yarn in some way here? I believe the templates are setup to use npm and using yarn can have unknown side-effects.
The main reason I'm saying this is because the package.lock.json is included in the template creation and that should fix the dependencies. This is part of our E2E tests, so based on this and the fact that I can't repro it on a Mac nor on a Linux instance, makes me think there's something different in your machine setup.

@javiercn thanks a lot, after removing all npm packages cache and yarn packages cache the problems disappeared👏, everything worked well.
I actually using yarn to install packages in ClientApp   folder, maybe has some side effects
and also I check the react-scripts 3.0.1 package.jsonfile, found that: eslint version same with the template generated


False Warnings: Not Recognizing System Path on Windows

Hi guys, when I tried to install the Python extension, the log showed warings reading that the python scripts path is not in PATH. While I truly know the python scripts path is in the system path variable, and this extension does work well after installation. Can these false warnings be fixed? because they are really annoying. Thanks for your great work.

What is the exact warning you are seeing?

@brettcannon Hi Brett, those warnings didn't occur again during following installation. I will close this issue and thank you.


botocore.exceptions.ConnectTimeoutError and lots of DEBUG outputs

The bug
Running hyp3-isce2 (0.9.2) locally I'm seeing a lot of initial logging messages related to botocore looking for cloud credentials. It looks like there is a traceback related to looking for instance metadata (would only work on AWS), but in any case the code ultimately succeeds successfully.
To Reproduce
docker run -it --rm \
    -e EARTHDATA_USERNAME=$EARTHDATA_USERNAME \
    -e EARTHDATA_PASSWORD=$EARTHDATA_PASSWORD \
    -e ESA_USERNAME=$ESA_USERNAME \
    -e ESA_PASSWORD=$ESA_PASSWORD \
    ghcr.io/asfhyp3/hyp3-isce2:0.9.2 \
        ++process insar_tops_burst \
        S1_136231_IW2_20200604T022312_VV_7C85-BURST \
        S1_136231_IW2_20200616T022313_VV_5D11-BURST \
        --looks 20x4 \
        --apply-water-mask False

Additional context
2024-01-11 03:07:22,367 - botocore.credentials - DEBUG - Looking for credentials via: iam-role
2024-01-11 03:07:22,368 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): <IP_ADDRESS>:80
2024-01-11 03:07:23,370 - botocore.utils - DEBUG - Caught retryable HTTP exception while making metadata service request to http://<IP_ADDRESS>/latest/api/token: Connect timeout on endpoint URL: "http://<IP_ADDRESS>/latest/api/token"
Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
TimeoutError: timed out

full traceback
/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/hyp3_isce2/__main__.py:40: DeprecationWarning: SelectableGroups dict interface is deprecated. Use select.
  eps = entry_points()['hyp3']
2024-01-11 03:07:22,348 - botocore.hooks - DEBUG - Changing event name from creating-client-class.iot-data to creating-client-class.iot-data-plane
2024-01-11 03:07:22,351 - botocore.hooks - DEBUG - Changing event name from before-call.apigateway to before-call.api-gateway
2024-01-11 03:07:22,352 - botocore.hooks - DEBUG - Changing event name from request-created.machinelearning.Predict to request-created.machine-learning.Predict
2024-01-11 03:07:22,355 - botocore.hooks - DEBUG - Changing event name from before-parameter-build.autoscaling.CreateLaunchConfiguration to before-parameter-build.auto-scaling.CreateLaunchConfiguration
2024-01-11 03:07:22,356 - botocore.hooks - DEBUG - Changing event name from before-parameter-build.route53 to before-parameter-build.route-53
2024-01-11 03:07:22,357 - botocore.hooks - DEBUG - Changing event name from request-created.cloudsearchdomain.Search to request-created.cloudsearch-domain.Search
2024-01-11 03:07:22,357 - botocore.hooks - DEBUG - Changing event name from docs.*.autoscaling.CreateLaunchConfiguration.complete-section to docs.*.auto-scaling.CreateLaunchConfiguration.complete-section
2024-01-11 03:07:22,359 - botocore.hooks - DEBUG - Changing event name from before-parameter-build.logs.CreateExportTask to before-parameter-build.cloudwatch-logs.CreateExportTask
2024-01-11 03:07:22,360 - botocore.hooks - DEBUG - Changing event name from docs.*.logs.CreateExportTask.complete-section to docs.*.cloudwatch-logs.CreateExportTask.complete-section
2024-01-11 03:07:22,360 - botocore.hooks - DEBUG - Changing event name from before-parameter-build.cloudsearchdomain.Search to before-parameter-build.cloudsearch-domain.Search
2024-01-11 03:07:22,360 - botocore.hooks - DEBUG - Changing event name from docs.*.cloudsearchdomain.Search.complete-section to docs.*.cloudsearch-domain.Search.complete-section
2024-01-11 03:07:22,363 - botocore.utils - DEBUG - IMDS ENDPOINT: http://<IP_ADDRESS>/
2024-01-11 03:07:22,365 - botocore.credentials - DEBUG - Looking for credentials via: env
2024-01-11 03:07:22,365 - botocore.credentials - DEBUG - Looking for credentials via: assume-role
2024-01-11 03:07:22,365 - botocore.credentials - DEBUG - Looking for credentials via: assume-role-with-web-identity
2024-01-11 03:07:22,365 - botocore.credentials - DEBUG - Looking for credentials via: sso
2024-01-11 03:07:22,365 - botocore.credentials - DEBUG - Looking for credentials via: shared-credentials-file
2024-01-11 03:07:22,365 - botocore.credentials - DEBUG - Looking for credentials via: custom-process
2024-01-11 03:07:22,366 - botocore.credentials - DEBUG - Looking for credentials via: config-file
2024-01-11 03:07:22,366 - botocore.credentials - DEBUG - Looking for credentials via: ec2-credentials-file
2024-01-11 03:07:22,366 - botocore.credentials - DEBUG - Looking for credentials via: boto-config
2024-01-11 03:07:22,366 - botocore.credentials - DEBUG - Looking for credentials via: container-role
2024-01-11 03:07:22,367 - botocore.credentials - DEBUG - Looking for credentials via: iam-role
2024-01-11 03:07:22,368 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): <IP_ADDRESS>:80
2024-01-11 03:07:23,370 - botocore.utils - DEBUG - Caught retryable HTTP exception while making metadata service request to http://<IP_ADDRESS>/latest/api/token: Connect timeout on endpoint URL: "http://<IP_ADDRESS>/latest/api/token"
Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
TimeoutError: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/httpsession.py", line 464, in send
    urllib_response = conn.urlopen(
                      ^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connectionpool.py", line 799, in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/retry.py", line 525, in increment
    raise six.reraise(type(error), error, _stacktrace)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/packages/six.py", line 770, in reraise
    raise value
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connectionpool.py", line 715, in urlopen
    httplib_response = self._make_request(
                       ^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/awsrequest.py", line 96, in request
    rval = super().request(method, url, body, headers, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 244, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 1286, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 1332, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 1281, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/awsrequest.py", line 123, in _send_output
    self.send(msg)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/awsrequest.py", line 223, in send
    return super().send(str)
           ^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 979, in send
    self.connect()
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 205, in connect
    conn = self._new_conn()
           ^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 179, in _new_conn
    raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError: (<botocore.awsrequest.AWSHTTPConnection object at 0x7f88cc7e5c10>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=1)')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/utils.py", line 460, in _fetch_metadata_token
    response = self._session.send(request.prepare())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/httpsession.py", line 499, in send
    raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://<IP_ADDRESS>/latest/api/token"
2024-01-11 03:07:23,375 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (2): <IP_ADDRESS>:80
2024-01-11 03:07:24,377 - botocore.utils - DEBUG - Caught retryable HTTP exception while making metadata service request to http://<IP_ADDRESS>/latest/meta-data/iam/security-credentials/: Connect timeout on endpoint URL: "http://<IP_ADDRESS>/latest/meta-data/iam/security-credentials/"
Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
TimeoutError: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/httpsession.py", line 464, in send
    urllib_response = conn.urlopen(
                      ^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connectionpool.py", line 799, in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/util/retry.py", line 525, in increment
    raise six.reraise(type(error), error, _stacktrace)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/packages/six.py", line 770, in reraise
    raise value
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connectionpool.py", line 715, in urlopen
    httplib_response = self._make_request(
                       ^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/awsrequest.py", line 96, in request
    rval = super().request(method, url, body, headers, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 244, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 1286, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 1332, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 1281, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/awsrequest.py", line 123, in _send_output
    self.send(msg)
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/awsrequest.py", line 223, in send
    return super().send(str)
           ^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/http/client.py", line 979, in send
    self.connect()
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 205, in connect
    conn = self._new_conn()
           ^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/urllib3/connection.py", line 179, in _new_conn
    raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError: (<botocore.awsrequest.AWSHTTPConnection object at 0x7f88cc5cc890>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=1)')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/utils.py", line 515, in _get_request
    response = self._session.send(request.prepare())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/httpsession.py", line 499, in send
    raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://<IP_ADDRESS>/latest/meta-data/iam/security-credentials/"
2024-01-11 03:07:24,380 - botocore.utils - DEBUG - Max number of attempts exceeded (1) when attempting to retrieve data from metadata service.
2024-01-11 03:07:24,381 - botocore.loaders - DEBUG - Loading JSON file: /opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/data/endpoints.json
2024-01-11 03:07:24,396 - botocore.loaders - DEBUG - Loading JSON file: /opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/data/sdk-default-configuration.json
2024-01-11 03:07:24,397 - botocore.hooks - DEBUG - Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f88cc718900>
2024-01-11 03:07:24,411 - botocore.loaders - DEBUG - Loading JSON file: /opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/data/s3/2006-03-01/service-2.json
2024-01-11 03:07:24,427 - botocore.loaders - DEBUG - Loading JSON file: /opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/data/s3/2006-03-01/endpoint-rule-set-1.json
2024-01-11 03:07:24,431 - botocore.loaders - DEBUG - Loading JSON file: /opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/data/partitions.json
2024-01-11 03:07:24,433 - botocore.hooks - DEBUG - Event creating-client-class.s3: calling handler <function add_generate_presigned_post at 0x7f88cc878e00>
2024-01-11 03:07:24,433 - botocore.hooks - DEBUG - Event creating-client-class.s3: calling handler <function lazy_call.<locals>._handler at 0x7f88ccc20220>
2024-01-11 03:07:24,447 - botocore.hooks - DEBUG - Event creating-client-class.s3: calling handler <function add_generate_presigned_url at 0x7f88cc878b80>
2024-01-11 03:07:24,447 - botocore.configprovider - DEBUG - Looking for endpoint for s3 via: environment_service
2024-01-11 03:07:24,447 - botocore.configprovider - DEBUG - Looking for endpoint for s3 via: environment_global
2024-01-11 03:07:24,447 - botocore.configprovider - DEBUG - Looking for endpoint for s3 via: config_service
2024-01-11 03:07:24,447 - botocore.configprovider - DEBUG - Looking for endpoint for s3 via: config_global
2024-01-11 03:07:24,447 - botocore.configprovider - DEBUG - No configured endpoint found.
2024-01-11 03:07:24,460 - botocore.endpoint - DEBUG - Setting s3 timeout as (60, 60)
2024-01-11 03:07:24,462 - botocore.loaders - DEBUG - Loading JSON file: /opt/conda/envs/hyp3-isce2/lib/python3.11/site-packages/botocore/data/_retry.json
2024-01-11 03:07:24,462 - botocore.client - DEBUG - Registering retry handlers for service: s3
2024-01-11 03:07:24,463 - botocore.utils - DEBUG - Registering S3 region redirector handler
2024-01-11 03:07:24,463 - botocore.utils - DEBUG - Registering S3Express Identity Resolver
2024-01-11 03:07:25,524 - hyp3_isce2.insar_tops_burst - INFO - Begin ISCE2 TopsApp run
2024-01-11 03:07:30,789 - hyp3_isce2.burst - INFO - Download attempt #1 for https://sentinel1-burst.asf.alaska.edu/S1A_IW_SLC__1SDV_20200604T022251_20200604T022318_032861_03CE65_7C85/IW2/VV/7.xml

@scottyhq I agree the volume of debug output is rather annoying and caused by importing ISCE2 which sets the logging level to DEBUG for everything:

https://github.com/isce-framework/isce2/blob/main/__init__.py#L37-L39
https://github.com/isce-framework/isce2/blob/main/defaults/logging/logging.conf#L11

and I just haven't been sufficiently annoyed by it to work around/fix it yet :rofl: Happy to take PRs for that, though!
For botocore, I believe that call to http://<IP_ADDRESS>/latest/api/token is only something that will succeed in AWS and is expected to fail outside of it, so non-fatal. botocore is reasonably expecting you to not see the the botocore debug logs unless you're actively debugging botocore.


Adds support for Pest php

This fix will expands the "nunomaudor/collision" package to support version ^5.0, since it's required in the testing framework Pest.
Fixes #752

Any reason this has been open for so long?

This library is essentially un-maintained 🙂

This library is essentially un-maintained 🙂

ah that's a shame. Hopefully @mpociot picks it up at some point.

@wardy484 former maintainer here. I work on a separate fork now https://github.com/knuckleswtf/scribe/. It supports Pest and a bunch of other stuff. I think you'll find it even better.

@wardy484 former maintainer here. I work on a separate fork now https://github.com/knuckleswtf/scribe/. It supports Pest and a bunch of other stuff. I think you'll find it even better.

Ah thanks I'll take a look at that.


in-project directory filename colours (Not VCS related) - remove noisy files

I would like to be able to specify some filenames as being a different foreground colour than the typical filename foreground colour. As an example in a python project many directories may contain a init.py file purely for the ability to be read as a module, it would be nice to determine a muted colour for these so that they may be seen but not the same as the others. The benefit is the project tree would look less busy and the ubiquitous init.py wouldn't be taking up eye space

you can see a mock example there (naturally without the borders, you get the idea

Would using files.exclude to not show them at all suffice?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Segmentation fault when performing read_verilog on large file

When trying to perform read_verilog on a file that contains approx. 115000 lines, yosys crashes with an unspecific segmentation fault. As this file only contains very primitive verilog constructs (no functions, no systemverilog etc.), I assume the crash happens mainly because of the file size. The specialty of the file is the fact that it not only contains one module but rather many module instances and definitions. As it is part of delivered IP, I cannot easily modify it or publish it here. The file contains actual RTL, no netlist.
Maybe it is possible for you to recreate this anyway, let me know if you need further input.

Here is a large Verilog file that I created using rocket-chip: test_v.zip
It is 11 MB in size, 357784 lines, 323 modules (288 used by ExampleRocketTop). On my machine Yosys completes reading this in less than 6 seconds, no problem. I'm gonna need more information that simply "it's a large file".
I understand if you cannot share the design you are having problems with. But without an example to reproduce the problem I'm not going to be able to do anything about it.
Maybe you can debug this on your own using the file you have and use your findings to generate an artificial test case that you are allowed to share.

Maybe it is possible for you to recreate this anyway, let me know if you need further input.

Any reason in particular why you did not try this yourself before posting?
I'm closing this issue for now. I'll reopen it if and when someone posts a test case.

Hi, I just dropped you an e-mail containing a stripped-down version of the file with mangled names, which I was allowed to share with you personally.

Thanks for the test case per email!
This test case contains single expressions that are >40 kB in size and in the order of 1k parenthesis levels deep. The read_verilog command runs out of stack space when trying to traverse the AST for this huge expressions. Simply running Yosys with a larger stack (e.g. ulimit -s 32768) seems to fix the issue.

I can confirm that this works.
Thanks very much for the extraordinary quick help!


Downgrades syntax for PHP 7.3 compatibility

I realize you probably don't wish to support PHP 7.3. But as far as I can tell, Ray seems to work great with PHP 7.3 projects with this patch applied to remove the class property typing and rewrite arrow functions in the throwback style. I completely understand if you choose to reject this PR, but I hope you consider merging it for those poor souls like us who have to support older codebases.

Related PR in spatie/backtrace https://github.com/spatie/backtrace/pull/2

Related PR in spatie/backtrace https://github.com/spatie/backtrace/pull/2

Like expected, I'm going to reject this. I'm hoping that all poor (lost?) souls will upgrade their projects to PHP 7.4
Should you want to maintain a PHP 7.3 version of Ray, feel free to fork our the package. I'll be more than happy to link to it in our docs.
Thanks for your work on this.

Like expected, I'm going to reject this. I'm hoping that all poor (lost?) souls will upgrade their projects to PHP 7.4
Should you want to maintain a PHP 7.3 version of Ray, feel free to fork our the package. I'll be more than happy to link to it in our docs.
Thanks for your work on this.


LayoutContraints Error with Swift 2.0 and iOS9

I am running my app on iOS7 and iOS8 without any problems. When I switch to iOS9 I get the following layout errors:
2015-09-21 02:50:59.554 TestApp[35286:707642] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#98 UIView:0x7fd4e3c0a200.top == UIView:0x7fd4e3c0a0a0.top + 64.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#98 UIView:0x7fd4e3c0a200.height == 60.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#131 NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.centerY == UIView:0x7fd4e3c0a200.centerY>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#131 NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.height == 29.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#143 UIView:0x7fd4e3acfd90.top == NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.bottom + 28.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#143 UIView:0x7fd4e3acfd90.height ==<PHONE_NUMBER>49609>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#165 UIView:0x7fd4e1edb650.bottom == UIView:0x7fd4e3c0a0a0.top>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#165 UIView:0x7fd4e1edb650.top == UIView:0x7fd4e3acfd90.bottom>"
)

Will attempt to recover by breaking constraint
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#131 NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.height == 29.0>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.
2015-09-21 02:50:59.555 TestApp[35286:707642] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#98 UIView:0x7fd4e3c0a200.top == UIView:0x7fd4e3c0a0a0.top + 64.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#98 UIView:0x7fd4e3c0a200.height == 60.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#131 NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.centerY == UIView:0x7fd4e3c0a200.centerY>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#143 UIView:0x7fd4e3acfd90.top == NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.bottom + 28.0>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#143 UIView:0x7fd4e3acfd90.height ==<PHONE_NUMBER>49609>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#165 UIView:0x7fd4e1edb650.bottom == UIView:0x7fd4e3c0a0a0.top>",
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#165 UIView:0x7fd4e1edb650.top == UIView:0x7fd4e3acfd90.bottom>"
)

Will attempt to recover by breaking constraint
<EMAIL_ADDRESS>Demo/TestApp/App/ServiceSelection/ServiceSelectionController.swift#131 NSKVONotifying_TestApp.DGRunkeeperSwitch:0x7fd4e1d38fe0.centerY == UIView:0x7fd4e3c0a200.centerY>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.

There might be a problem with snp_bottomLayoutGuide...

Yea it looks like iOS 9 has breaking API for layout guides. Unfortunately unless we're actually creating invalid constraints it's inside the layout engine which we have no control over.
I'm unsure at the moment what the solution is for layout guides and iOS 9.

It works fine if you do not use the layout guides.

Should be fixed on develop now. Waiting for release.

Released with 0.15.0

thank you

I use latest develop source codes. But there are the same problem
2015-10-30 12:33:18.033 investor[86201:42493345] Unable to simultaneously satisfy constraints.
	Probably at least one of the constraints in the following list is one you don't want.
	Try this:
		(1) look at each constraint and try to figure out which you don't expect;
		(2) find the code that added the unwanted constraint or constraints and fix it.
(
<EMAIL_ADDRESS>UIButton:0x7ff11e141ed0.top == investor.DocumentCell:0x7ff11e139d60.top>",
<EMAIL_ADDRESS>UIButton:0x7ff11e141ed0.bottom == investor.DocumentCell:0x7ff11e139d60.bottom>",
<EMAIL_ADDRESS>UIImageView:0x7ff11e143f80.top == UIButton:0x7ff11e141ed0.top>",
<EMAIL_ADDRESS>UIImageView:0x7ff11e143f80.height == UIButton:0x7ff11e141ed0.height * 0.5>",
    "<NSLayoutConstraint:0x7ff11bfb1e30 UIImageView:0x7ff11e143f80.centerY == UIButton:0x7ff11e141ed0'BELGE EKLE'.centerY>",
    "<NSLayoutConstraint:0x7ff11bfcd0d0 'UIView-Encapsulated-Layout-Height' V:[investor.DocumentCell:0x7ff11e139d60(134.034)]>"
)

Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x7ff11bfb1e30 UIImageView:0x7ff11e143f80.centerY == UIButton:0x7ff11e141ed0'BELGE EKLE'.centerY>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.


feat: drawer footer standard props

Description
This PR follows the Drawer component introduction PR and introduces the following changes:
Drawer component
New features:

Drawer footer can now be a custom node or can leverage standard properties (button, extra) for a predefined look.
Drawer now has a closeIcon

Improvements:

Drawer types have been moved to a separate file
Drawer stories and mocks have been refactored to be more meaningful and usable; Drawer stories now correctly show the drawer props in the Show Code tab
Drawer styles are now imported from a CSS module

Checklist

[x] commit message and branch name follow conventions
[x] tests are included
[x] changes are accessible and documented from components stories
[ ] typings are updated or integrated accordingly with your changes
[ ] all added components are exported from index file (if necessary)
[ ] all added files include Apache 2.0 license
[x] you are not committing extraneous files or sensitive data
[x] the browser console does not have any logged errors
[x] necessary labels have been applied to this pull request (enhancement, bug, ecc.)

Can we consider adding a docLink prop to show the doc icon in the title like in the Modal?

Can we consider adding a docLink prop to show the doc icon in the title like in the Modal?

This makes sense, do other components have a standard prop definition for this? If so let's do this following the same prop-defnition, if not I'd open a PR to define such standard prop and then open another PR

Can we consider adding a docLink prop to show the doc icon in the title like in the Modal?

Can we consider adding a docLink prop to show the doc icon in the title like in the Modal?

This makes sense, do other components have a standard prop definition for this? If so let's do this following the same prop-defnition, if not I'd open a PR to define such standard prop and then open another PR

yes, the Modal has it. I can add it


Apply scripts and snippets without reloading Obsidian

I think hot-reload plugin can help, at least as an inspiration.
https://github.com/pjeby/hot-reload

@vanadium23  Sure, thanks. I'll probably add this improvement next week.


Implementing a "re-flipper"...

This would also tie in with the "combining several pdf into one"
I got some expansions for one game which consist of only one card. So the author made them foldable but placed the single cards front side long edge to long edge with the backside. I also have one game were 4 cards are on one page but they are also arranged long edge to long edge in a 2x2 card pattern. If we could get a "backside is on the same page" option and then the appending of several pdf into one that would be great!

Ironically I just came across a game like this myself yesterday (Bury me in the Rift) and wondered if that should be added 😬