GitOrigin-RevId: 08cf47d33f47ae392e703c12fcedf6b6e5cabefa

GitOrigin-RevId: 5c4433e44b7f2f61e5adc3850f155114d861a518

Quickfix for IDEA-343073 Setting Sync sync failed. couldn't get settings from server: Authentication required: Just show simple message suggesting the reloging and restart

GitOrigin-RevId: 84e405fc5db1693d03e2bf1dc5c411805335ff07

GitOrigin-RevId: 061526ea25aafe92dac5b867332c17560d57c088

(cherry picked from commit 6eb4aa1dcbfe5b13c52d91447778fc7dd8e7c7ae)

GitOrigin-RevId: 87f4c0223b2550ff1c2f7c668da3dd668b466eee

GitOrigin-RevId: d8d2e24dc9032a8dec3a150d08a79769881d42c6

The change is necessary only to pass the tests that check copyrights in files, even though nothing is changed regarding Kotlin support.

The test that requires these changes is `org.jetbrains.kotlin.idea.testGenerator.all.AllTestsGeneratedTest.testAllTestsIsUpToDate`

GitOrigin-RevId: 3b06b99ddeb02df5c8f2d4a0eb103a8e29a9f2fd

The source code of the actual change is there: https://jetbrains.team/p/ij/packages/maven/intellij-dependencies/org.jetbrains.intellij.deps/sshj?v=0.35.0-idea1

(cherry picked from commit 27f07c63275dc5eb0cdff0c9cec74c77b47f443b)

IJ-CR-123106

GitOrigin-RevId: 0a83fa4490e9b0249d29c704f856bca0a1a2b773

GitOrigin-RevId: 4ebb180a8d3e868a6e84439b2037abfb8d138ffc

Use per-requester limits for valid tokens.

(cherry picked from commit 5bd57ec332960d9bbde1c3c1faea7d66dfaef304)

IJ-MR-110089

GitOrigin-RevId: deaef53a85bb0b0ad55d8d58ee9749f847a6de7f

(cherry picked from commit 2de6aebd2bcaee48f395b3060148ea07ea225356)

IJ-MR-110089

GitOrigin-RevId: 8714b4098764c61096f632f9be1b392a36384925

(cherry picked from commit 54c724ad28d5bc206b0d5df281eb6b29fdfb3f59)

GitOrigin-RevId: 7548c4f72e3146a62fb77fd5fb121b889e807c49

(cherry picked from commit e21fb1a6945c38cf97b05a6501e189a92ce57f55)

GitOrigin-RevId: b6363bf63879170f0bb3faf8783f9d1f98531108

(cherry picked from commit f5e0488ebbf4148e5e635e6cf9b0742f3b01f00c)

IJ-CR-111090

GitOrigin-RevId: 128d74ea015d9f3bde47f3ad3627ebb2f3402a8e

[build scripts] dependencies downloader: don't use `content-encoding` since we need `content-length` header

(cherry picked from commit 24d06877b0b54669d3b4c229dba043d93349489d)

IJ-CR-110417

GitOrigin-RevId: 0344f96e40411828a36d59ff689e6efe93798e4d

GitOrigin-RevId: e7eb708f7cac738b15ab30c0da6858932f849f2a

Currently, the IDEA doesn't support evaluation of Gradle property providers which require task execution.

(cherry picked from commit e552a71810615ec87750c6354f592eb1570ff750)

IJ-CR-110076

GitOrigin-RevId: 1bea1cc1e08ff3aebc8467af3210036fb615b733

 Limit checks of jar task inputs. Resolving arbitrary input using Project#files API may throw exceptions. Listed types are safe to resolve

(cherry picked from commit c0a5e7a5c7e82b961071e43b0b386ee1d915c046)
(cherry picked from commit b7d40f3c460961c3abca012e4c9a295f784fdfb1)

IJ-CR-110076

GitOrigin-RevId: 53998355d772cddb555128af3a5b0a00c84223d5

[platform] "Copy Reference" action for non-java modules should copy the path from the content root (IDEA-316752)

WorkspaceFileIndex::getContentFileSetRoot will return the path to the nearest parent content or source root, this is not that people expect for non-java modules. BaseProjectDirectories::getBaseDirectoryFor called below will return the parent (top-level) content root. Files in Java modules are handled by JavaVirtualFileQualifiedNameProvider, so nothing will change for them.

Cherry-picked from 916ce28ba7bf85b44cf19bb8734dcd0e0494fea5, IJ-CR-110021.

GitOrigin-RevId: 43341730cb42e63f09ba88f70cf6638d9f3bb14f

(cherry-picked from commit 3863d63e571b30447eacd2ae1e1f1198782bdfd0)

IJ-CR-109615

GitOrigin-RevId: 43d7ea1a827c4858cd0711ff27233d83774e7c62

The reasoning is that if an interpreter can't be successfully updated, it's better
to fail fast, clearly indicating the current state of resolve, rather that confuse
a user by invisible errors. It might go the other way around, e.g. the update has
been mostly completed before an error occurred, but we still show unresolved references
in the editor, even though all the remote sources and skeletons are already available
for code insight.

In this particular case, a runtime SftpChannelException, caused by an attempt to copy
a file with an illegal name, made highlighting go stale and still report unresolved
imports until the IDE was restarted.

IJ-MR-109009

(cherry picked from commit ee218dd575205de054e7d093ac6635d168449120)

GitOrigin-RevId: 654d8565107ec697671ae2459cf52c9c42c3683f

IJ-MR-109009

(cherry picked from commit 916ac31182d93a8e8f5b960f6e2192121aaff45e)

GitOrigin-RevId: a8f7b1e95a9101b3983f6d48e7b63697a39bf7ce

Otherwise, we end up generating syntactically invalid skeletons or, if
a large module gets transformed into a package where each class stub is
declared in its own file with the same name, some of the class names might
be illegal even for the target file system.

In this particular issue, the "shyft" package declared a class named
"ComputeNodeInfoVectorA strongly typed list of ComputeNodeInfo as returned
from the dstm server\012", which couldn't be copied to a Windows host from
a Linux remote.

IJ-MR-109009

(cherry picked from commit 0eed4ee5bb8fab85104297107a7f26150e390824)

GitOrigin-RevId: 2b0cc87db012f8b6d5b82882bdedace15115db4e

dispose vfs & indexes as soon as possible when termination signal received because OS may not wait until completed app shutdown and kill it

(cherry picked from commit d539fa7d1db5c8762ac317b93ea82e204f24c78d)

IJ-CR-109768

GitOrigin-RevId: 47bb0874a63f3dc6ed41dde9887e8316100c5d0d

The difference now is that there is path to the executable, and IDE verifies that Toolbox is still present there.

(cherry picked from commit 45fa8b2e7ae17f3d3386865e8f56438f21fc4af3)

IJ-CR-109521

GitOrigin-RevId: d69c734ffe89dd98adad31dd435569a669df5340

Fixes IDEA-323505 can't remove @NotNull annotation from configuration
Fixes IDEA-323547 @jakarta.validation.constraints.NotNull is being incorrectly interpreted for Nullability Problems

(cherry picked from commit 07fd30deed72546762a37c79d894ea5188df4917)

IJ-CR-109516

GitOrigin-RevId: 25f60abd2f9fe1b02de9f911298be39f8c4c326f

* Revert the previous NPE fix
* Split init and read from data holder operations
* Add more debug logging
* Drop parent scheme name when loading, it's never used in code style schemes

(cherry picked from commit e98d4552534b885e3d75799e54257563b84f9a49)

IJ-CR-109148

(cherry picked from commit 01c1f1d9ddcea15f9ff72100ab8a9e824be72bf2)

GitOrigin-RevId: e5061ddcfebd9a77d631e51d04f78b720abb37d6

GitOrigin-RevId: c4e9bb6429161b101362a14057d2ff30b78a9a10

(cherry picked from commit b49adfd771513577c08ee276728db7dbb02d32b3)

IJ-CR-109290

GitOrigin-RevId: dbec7fe04af79badfcee85734ba9d4e629016e6e

(cherry picked from commit 78ac7924f5527dd77389d4bd69e6485d78a9048c)

IJ-CR-108345

GitOrigin-RevId: fb4e5daf2f633383712872c3dae782d3800e36fe

IDEA-319871 Logging breakpoints make debugger evaluation hangs with "Collecting data..." - newInstance should not be called directly

(cherry picked from commit fabe0ff8aa31c0ad07d0edb41c056ae8e097fe93)

IJ-CR-108116

GitOrigin-RevId: a69fc4e347027a183bf141083ac627e359ac108d

(cherry picked from commit e5cd46a6da51b8928fc88695b2d0d14390f088b1)

GitOrigin-RevId: 31a18e803efd229c7f75cffc21eee7a6742e2a6e

close #2435

(cherry picked from commit 42ff0b1cdceadb7cb05eebd8fcce2b439a8d2fd1)

GitOrigin-RevId: 5f6c4847504a3e847ff1b7f1f7491c55ae4e8b0a

(cherry picked from commit bf4f1794896abd6c12a3cb65f35b196c0abfd0c5)

GitOrigin-RevId: df7b9cf8d3f4628ed41da2c8fd000b8bb3bbe08a

GitOrigin-RevId: f0e17390220c38b244eb4f82be3df0ae74c1c8c7

(cherry picked from commit 64d364763d6ae53baeb985afe4aa8a318893b58d)

IJ-CR-108760

GitOrigin-RevId: 689d7253929267b8b7fc1e6b9cc151c29ade6ad6

(cherry picked from commit 18cfb8ed16e607d60dfea8c844e8e8bf7a0fab0a)

IJ-CR-108760

GitOrigin-RevId: 5d044cfba6e722cc0c7bf4e988315f306771297a

The IDE collects a handful of sensitive aspects of the execution to ensure it's possible to try and reproduce the exception. So, some attachments, like the code, are by default excluded from the report. If an external user wants to share such details, they should manually set the checkbox in the IDE Internal error form.

However, even in that case, we may not have a chance to reproduce the exception, as we may not have access to the external code, let alone means to recreate the same execution. So all that comprehensive and sensitive information may give us nothing to work with.

Many internal users work with Kotlin, and we receive many exceptions from them, so this group should be enough to sort out possible problems.

(cherry picked from commit da517ead64d0b3427d4addb76d2ff1d71c9ed5f8)

IJ-CR-108808

GitOrigin-RevId: 2be69817b713f8747b37470af73ee14ef4b42d6c

If the project is known, having session help may further help with figuring out what exactly was being executed (i.e., what configuration or what test was launched).

(cherry picked from commit 01643873e69b888ac023ad892c77de6ccd283ac7)

IJ-CR-108808

GitOrigin-RevId: a718f65c802732e027c30bc687c796f85d42b6bc

The exact stack trace may also help with reproducing errors, as it gives more understanding where the execution of the current frame comes from.

(cherry picked from commit a7ea778abde1a127bcf73c3f37935b264d7c97dd)

IJ-CR-108808

GitOrigin-RevId: b581f417c175a3b59622f6598933219e8a51453d