This project is mirrored from https://gitee.com/mirrors/intellij-community.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 07 Jul, 2023 1 commit
-
-
Nikolay Sandalov authored
GitOrigin-RevId: e7eb708f7cac738b15ab30c0da6858932f849f2a
-
- 04 Jul, 2023 3 commits
-
-
Sergei Vorobyov authored
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
-
Nikita.Skvortsov authored
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
-
Nikolay Chashnikov authored
[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
-
- 30 Jun, 2023 5 commits
-
-
Roman Shevchenko authored
(cherry-picked from commit 3863d63e571b30447eacd2ae1e1f1198782bdfd0) IJ-CR-109615 GitOrigin-RevId: 43d7ea1a827c4858cd0711ff27233d83774e7c62
-
Mikhail Golubev authored
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
-
Mikhail Golubev authored
IJ-MR-109009 (cherry picked from commit 916ac31182d93a8e8f5b960f6e2192121aaff45e) GitOrigin-RevId: a8f7b1e95a9101b3983f6d48e7b63697a39bf7ce
-
Mikhail Golubev authored
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
-
Dmitry Batkovich authored
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
-
- 29 Jun, 2023 2 commits
-
-
Victor Kropp authored
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
-
Tagir Valeev authored
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
-
- 28 Jun, 2023 2 commits
-
-
Rustam Vishniakov authored
* 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
-
Yuriy Artamonov authored
GitOrigin-RevId: c4e9bb6429161b101362a14057d2ff30b78a9a10
-
- 26 Jun, 2023 3 commits
-
-
Egor Ushakov authored
(cherry picked from commit b49adfd771513577c08ee276728db7dbb02d32b3) IJ-CR-109290 GitOrigin-RevId: dbec7fe04af79badfcee85734ba9d4e629016e6e
-
Egor Ushakov authored
(cherry picked from commit 78ac7924f5527dd77389d4bd69e6485d78a9048c) IJ-CR-108345 GitOrigin-RevId: fb4e5daf2f633383712872c3dae782d3800e36fe
-
Egor Ushakov authored
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
-
- 23 Jun, 2023 4 commits
-
-
Alexander Bubenchikov authored
(cherry picked from commit e5cd46a6da51b8928fc88695b2d0d14390f088b1) GitOrigin-RevId: 31a18e803efd229c7f75cffc21eee7a6742e2a6e
-
Sergey Chernov authored
close #2435 (cherry picked from commit 42ff0b1cdceadb7cb05eebd8fcce2b439a8d2fd1) GitOrigin-RevId: 5f6c4847504a3e847ff1b7f1f7491c55ae4e8b0a
-
Alexander Bubenchikov authored
(cherry picked from commit bf4f1794896abd6c12a3cb65f35b196c0abfd0c5) GitOrigin-RevId: df7b9cf8d3f4628ed41da2c8fd000b8bb3bbe08a
-
Alexander Bubenchikov authored
GitOrigin-RevId: f0e17390220c38b244eb4f82be3df0ae74c1c8c7
-
- 22 Jun, 2023 2 commits
-
-
Egor Ushakov authored
(cherry picked from commit 64d364763d6ae53baeb985afe4aa8a318893b58d) IJ-CR-108760 GitOrigin-RevId: 689d7253929267b8b7fc1e6b9cc151c29ade6ad6
-
Egor Ushakov authored
(cherry picked from commit 18cfb8ed16e607d60dfea8c844e8e8bf7a0fab0a) IJ-CR-108760 GitOrigin-RevId: 5d044cfba6e722cc0c7bf4e988315f306771297a
-
- 21 Jun, 2023 12 commits
-
-
Aleksander Kuznetsov authored
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
-
Aleksander Kuznetsov authored
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
-
Aleksander Kuznetsov authored
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
-
Tagir Valeev authored
(cherry picked from commit 42ab23e8312466553238ce80e53870d8df6adcf8) IJ-CR-108993 GitOrigin-RevId: 1402a1263d042ce86c704afefb4b0a16ca26358e
-
Aleksander Kuznetsov authored
(cherry picked from commit ec9016f395afecbdf47e610f2e6c2362ace359bb) IJ-CR-108099 GitOrigin-RevId: 46234488c7136ed84aedf42ee1785fac233ce34a
-
Aleksander Kuznetsov authored
Log project, file name where the program is suspended at, and a suspension line. Attach the evaluated expression and file contents (not included by default for external users) as well. As we expect fewer bug reports now, when we automatically fall back to the old evaluation, such context should help us address the cause of the issues. (cherry picked from commit fafd4dc3875f373438100b4e0ff8c358215b4604) IJ-CR-108099 GitOrigin-RevId: 347a147d9a3926ce5ffac1f0f5a2f1b14885b6f6
-
Aleksander Kuznetsov authored
It's needed for testing purposes. IDEA restricts handling frequent exceptions (cherry picked from commit 9b2e75a7d64873d08aa63ebb66c8936ceb6f4908) IJ-CR-108099 GitOrigin-RevId: ac6a20472a799b5b6ed3eb1d147cccac2d1f6534
-
Aleksander Kuznetsov authored
Log an error with its cause when switching to the old evaluator. This way, users will get real evaluation results (albeit at a slower pace sometimes), as well as have means to report new evaluator errors. As a minor bonus goes one less usage of a registry key -- aspects of certain evaluators (what files to compile and what codegen to use) are now combined in one place. (cherry picked from commit 6092baca0a097b07c9773f86c29869fd1009ae82) IJ-CR-108099 GitOrigin-RevId: c87b3a30e0f241cd2c4dfcfb6f5d74554eecdb8b
-
Nikita.Skvortsov authored
(cherry picked from commit 80cc45ef9376b38d7feb8e8cc01d4ccb702469d3) IJ-CR-106542 GitOrigin-RevId: 329ea2b30326c4b096e58fb52f8c72ff1b79d730
-
Nikita.Skvortsov authored
Make sure only owning sourceset will register jar as an artifact. (cherry picked from commit ee4a8f842034da34c0da63f4cb77b546b00a2707) IJ-CR-106542 GitOrigin-RevId: 4f86ae9e663640b2ef5bfe92e8380e067600a3d6
-
Nikita.Skvortsov authored
Allows to reproduce an issue. (cherry picked from commit 341072cdafe988b1bbc072c32bd07d135f758098) IJ-CR-106542 GitOrigin-RevId: ce45c9cd0bc2c75ce7ddb9328b69c0db1b68c81a
-
Nikita.Skvortsov authored
Process all jar task inputs with project.files(...) API - the same way it is done when running the task itself. (cherry picked from commit a7fba55e97ee2dacbc83fe44f4a74dc6153c7e03) IJ-CR-106542 GitOrigin-RevId: 396a68cdde35163f59b5766767b84d28281ad95b
-
- 20 Jun, 2023 1 commit
-
-
Ilya.Kazakevich authored
GitOrigin-RevId: a0816f3c2854c91cfab9da5363a56fc8c0e9987d
-
- 16 Jun, 2023 1 commit
-
-
Egor Ushakov authored
(cherry picked from commit 38029bf91bd09c054f51d4611fad3ed8931671d0) IJ-CR-108750 GitOrigin-RevId: 6cf378645daf26ce3307f4490f46fae18d37cc32
-
- 13 Jun, 2023 4 commits
-
-
Tagir Valeev authored
Document.stripTrailingSpaces behavior depends on whether the document is committed, which looks to be racy. (cherry picked from commit bdc8b46e9a968782ac7630102b5393460d113061) IJ-CR-108253 GitOrigin-RevId: 84aa8583c63dd4dacc28fc901cf7be4a89e72e32
-
Dmitry Kichinsky authored
(cherry picked from commit 80c8d26024130963b9ea7cc1244f20f158962e45) IJ-CR-106740 GitOrigin-RevId: e6c086ab2e4f566d399c51c6f3bcd881d9483dd6
-
Dmitriy.Panov authored
build scripts: 'Uninstall.exe' is ignored while comparing Windows distributions because it's already being ignored by com.intellij.updater.Runner itself (cherry picked from commit 9313992ad49bd930f03a6de0bf5aca71fe42b035) IJ-CR-108423 GitOrigin-RevId: f43ba13c2776a5970453b1b8f2752d7a29f8da7f
-
Artem Bochkarev authored
and also remove unnecessary fillMenu() from menuWillOpen (cherry picked from commit f7bf20c03fb629c08f66da2d21eb200cfdf728ad) IJ-CR-107824 GitOrigin-RevId: 8a625b70b011ea2e45ec8647a7277bea200891da
-