[okteta] [Bug 371790] Increase array limit >10000
https://bugs.kde.org/show_bug.cgi?id=371790 Alex Richardson changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/okt ||eta/ceaff5549038e60d1e180a1 ||200d15fe76880772c Resolution|--- |FIXED --- Comment #4 from Alex Richardson --- Git commit ceaff5549038e60d1e180a1200d15fe76880772c by Alex Richardson. Committed on 08/06/2019 at 15:42. Pushed by arichardson into branch 'master'. Use 64K as the maximum number of array entries This is still an arbitary limit to avoid excessive memory consumption. 1 is not enough for some use cases. Hopefully 64K works better. Patch by Staffan Palmroos! M +2-1 kasten/controllers/view/structures/datatypes/array/arraydatainformation.hpp https://commits.kde.org/okteta/ceaff5549038e60d1e180a1200d15fe76880772c -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 371790] Increase array limit >10000
https://bugs.kde.org/show_bug.cgi?id=371790 --- Comment #3 from Alex Richardson --- Sorry, completely forgot about this bug report. I'll apply the change now. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 211654] Calling KLocale::formatNumber() with very high precision takes forever
https://bugs.kde.org/show_bug.cgi?id=211654 Alex Richardson changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #8 from Alex Richardson --- Since KLocale is now only in kdelibs4support and the function in question only calls the Qt code I think we should report this as an upstream bug if it still applies. I don't have access to my dev environment right now to test but if I can see if it still happens with Qt5.12 and if so report it upstream. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 228236] Kopete settings dialogue takes a long time to open
https://bugs.kde.org/show_bug.cgi?id=228236 --- Comment #2 from Alex Richardson --- I no longer have kopete installed so I can't reproduce this anymore. I don't think this is particularly important even if it still exist so feel free to close this. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 374913] Open does not use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913 --- Comment #27 from Alex Richardson --- Sorry about that, I didn't test that case. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 393920] Migrate structures system to use Kaitai library
https://bugs.kde.org/show_bug.cgi?id=393920 Alex Richardson changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Alex Richardson --- This does sound very promising especially considering there seems to be quite a lot of definitions available already. However, I'm not sure this works from a dependency point of view since I can't find any packages in default distribution repositories. Also I currently don't have much time to work on this but I would really like to add this feature. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 374913] Open does not use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913
Alex Richardson <arichardson@gmail.com> changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla
|sma-integration/bfd41a95530 |sma-integration/cc064e81c6e
|f90ee8d44cbcfd1fa8c62978334 |d51f3b4422c2f2347e5f4e090e6
|a2 |28
--- Comment #23 from Alex Richardson <arichardson@gmail.com> ---
Git commit cc064e81c6ed51f3b4422c2f2347e5f4e090e628 by Alex Richardson.
Committed on 08/04/2018 at 14:05.
Pushed by arichardson into branch 'Plasma/5.12'.
KDEPlatformFileDialog: Fix initial directory selection for remote files
Summary:
Previously KDEPlatformFileDialogHelper::selectFile() would change
options()->initialDirectory() unconditionally even if it was already
set by the QFileDialog code. Since Qt 5.7.1 it is no longer necessary
to derive initialDirectory from the selectFile() call. In fact it is
actuall harmful since it will now override the correct initial directory
that was set by Qt. Without this patch I got the following debug output:
```
KDEPlatformFileDialogHelper::setDirectory
QUrl("sftp://server/home/alr48/cheri/build_sdk.sh;)
KDEPlatformFileDialogHelper::setDirectory
QUrl("sftp://server/home/alr48/cheri/build_sdk.sh;)
KDEPlatformFileDialogHelper::selectFile QUrl("file:///home/alex/build_sdk.sh")
KDEPlatformFileDialogHelper::setDirectory QUrl("file:///home/alex/)
```
The final setDirectory() call is actually a call to
`setDirectory(options->initialDirectory())` which was set in `selectFile()`.
We now depend on Qt 5.9 so we can remove this code without a check for
version >= 5.7.1.
Test Plan: Remote directory is now opened correctly (tested with Qt 5.10.0)
Reviewers: #plasma, elvisangelaccio
Reviewed By: elvisangelaccio
Subscribers: ngraham, krzyc, anthonyfieroni, elvisangelaccio, graesslin,
plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D4193
M +0-5src/platformtheme/kdeplatformfiledialoghelper.cpp
https://commits.kde.org/plasma-integration/cc064e81c6ed51f3b4422c2f2347e5f4e090e628
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-integration] [Bug 374913] Open does not use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913
Alex Richardson <arichardson@gmail.com> changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/pla
||sma-integration/bfd41a95530
||f90ee8d44cbcfd1fa8c62978334
||a2
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #22 from Alex Richardson <arichardson@gmail.com> ---
Git commit bfd41a95530f90ee8d44cbcfd1fa8c62978334a2 by Alex Richardson.
Committed on 08/04/2018 at 10:06.
Pushed by arichardson into branch 'master'.
KDEPlatformFileDialog: Fix initial directory selection for remote files
Summary:
Previously KDEPlatformFileDialogHelper::selectFile() would change
options()->initialDirectory() unconditionally even if it was already
set by the QFileDialog code. Since Qt 5.7.1 it is no longer necessary
to derive initialDirectory from the selectFile() call. In fact it is
actuall harmful since it will now override the correct initial directory
that was set by Qt. Without this patch I got the following debug output:
```
KDEPlatformFileDialogHelper::setDirectory
QUrl("sftp://server/home/alr48/cheri/build_sdk.sh;)
KDEPlatformFileDialogHelper::setDirectory
QUrl("sftp://server/home/alr48/cheri/build_sdk.sh;)
KDEPlatformFileDialogHelper::selectFile QUrl("file:///home/alex/build_sdk.sh")
KDEPlatformFileDialogHelper::setDirectory QUrl("file:///home/alex/)
```
The final setDirectory() call is actually a call to
`setDirectory(options->initialDirectory())` which was set in `selectFile()`.
We now depend on Qt 5.9 so we can remove this code without a check for
version >= 5.7.1.
Test Plan: Remote directory is now opened correctly (tested with Qt 5.10.0)
Reviewers: #plasma, elvisangelaccio
Reviewed By: elvisangelaccio
Subscribers: ngraham, krzyc, anthonyfieroni, elvisangelaccio, graesslin,
plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D4193
M +0-5src/platformtheme/kdeplatformfiledialoghelper.cpp
https://commits.kde.org/plasma-integration/bfd41a95530f90ee8d44cbcfd1fa8c62978334a2
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 380024] Opening a remote file and clicking "Open" resets the file picker's location to the user's home directory
https://bugs.kde.org/show_bug.cgi?id=380024 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||arichardson@gmail.com --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- This should hopefully fix it, but it still needs to be approved: https://phabricator.kde.org/D4193 *** This bug has been marked as a duplicate of bug 374913 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374913] Open does use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added CC||kde_b...@multiwebinc.com --- Comment #4 from Alex Richardson <arichardson@gmail.com> --- *** Bug 380024 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377768] Symbolic links are not handled correctly for SFTP://
https://bugs.kde.org/show_bug.cgi?id=377768
--- Comment #1 from Alex Richardson <arichardson@gmail.com> ---
A quick grep points me at:
```
KTextEditor::Document *KateDocManager::findDocument(const QUrl ) const
{
QUrl u(url.adjusted(QUrl::NormalizePathSegments));
// Resolve symbolic links for local files (done anyway in KTextEditor)
if (u.isLocalFile()) {
QString normalizedUrl = QFileInfo(u.toLocalFile()).canonicalFilePath();
if (!normalizedUrl.isEmpty()) {
u = QUrl::fromLocalFile(normalizedUrl);
}
}
```
Possibly replacing this with KIO::stat() could resolve the issue?
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 377768] New: Symbolic links are not handled correctly for SFTP://
https://bugs.kde.org/show_bug.cgi?id=377768 Bug ID: 377768 Summary: Symbolic links are not handled correctly for SFTP:// Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: arichardson@gmail.com Target Milestone: --- If I edit a file that is a symbolic link over sftp://, on saving kate will not modify the target of that symbolic link but instead replace the symbolic link with the changed file. It works as expected for local files. Possibly kate is using QFileInfo() instead of KIO? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374913] Open does use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913 --- Comment #3 from Alex Richardson <arichardson@gmail.com> --- I have submitted https://codereview.qt-project.org/#/c/182661/ and https://phabricator.kde.org/D4193 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374913] Open does use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913
--- Comment #2 from Alex Richardson <arichardson@gmail.com> ---
Seems like the problem might be in Qt. I added some debug output and it seems
Qt is calling KDEPlatformFileDialogHelper::selectFile(const QUrl ) by
simply concatenating filename with the CWD because it does
QUrl::fromLocalFile("myfile.cpp") which results in "CWD/myfile.cpp"
I'll see if I can work around this in plasma-integration
https://code.woboq.org/qt5/qtbase/src/widgets/dialogs/qfiledialog.cpp.html#1048
```
if (!d->usingWidgets()) {
QUrl url = QUrl::fromLocalFile(filename);
if (QFileInfo(filename).isRelative()) {
QDir dir(d->options->initialDirectory().toLocalFile());
url = QUrl::fromLocalFile(dir.absoluteFilePath(filename));
}
d->selectFile_sys(url);
d->options->setInitiallySelectedFiles(QList() << url);
return;
}
```
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 374913] Open does use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- I just updated my openSUSE tumbleweed system and it is broken there now. So it is definitely a regression in Kate and not a packaging issue. new version (tumbleweed snapshot 20170112): ``` Kate Version 16.12.0 KDE Frameworks 5.30.0 Qt 5.7.1 (built against 5.7.1) The xcb windowing system ``` Old version was a snapshot sometime in December still with 16.08 and Frameworks 5.29 or 5.28 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374913] New: Open does use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913 Bug ID: 374913 Summary: Open does use directory for currently open file with sftp:// Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: arichardson@gmail.com Target Milestone: --- Instead it opens the file dialog in the CWD. The same thing happens for KWrite but strangely it works fine in KDevelop so I don't think it is related to the integration plugin. The only change that I can see affecting opening files is 2daae41a3738cc319f5925a96d3938779b3bd09b but that doesn't look like it should break this. It seems to be working fine on my openSUSE Tumbleweed laptop but is broken in Ubuntu neon. Not sure if this is packaging issue or they are just using different versions. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363365] button "open" clicked from active remote sftp file tries to open nonexistent directory.
https://bugs.kde.org/show_bug.cgi?id=363365 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added CC||arichardson@gmail.com Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Alex Richardson <arichardson@gmail.com> --- This should be fixed in the latest kate versions (it works for me on openSUSE Tumbleweed). Should have been fixed by 5420b5752a30c294486fbaf967187c8a6f64fe42 in frameworkintegration.git -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 372915] New: Pressing refresh on a deleted folder does not work
https://bugs.kde.org/show_bug.cgi?id=372915 Bug ID: 372915 Summary: Pressing refresh on a deleted folder does not work Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: arichardson@gmail.com Target Milestone: --- When I have dolphin open in folder /tmp/foo and then externally run rmdir /tmp/foo, dolphin displays /tmp/foo (deleted). When I then later run mkdir /tmp/foo I would expect that pressing F5 in dolphin should show the new folder contents but instead it attempts to show "/tmp/foo (deleted)" which obviously doesn't exist. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 371790] Increase array limit >10000
https://bugs.kde.org/show_bug.cgi?id=371790 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- Yes the 1 is a rather arbitrary limit. I just chose it because I had a few structures that would attempt to allocate e.g. 4 million items with an invalid layout. 64K sounds like a more reasonable limit. I currently don't have access to my development system but I'll apply it I get back. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 371800] Automatically adjust the headers in the structures view (w/ patches)
https://bugs.kde.org/show_bug.cgi?id=371800 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- I agree this is annoying. Initially I used QHeaderView::ResizeToContents but once you have a few hundred items it gets extremely slow (even if they aren't visible). It's quite possible that this issue has been fixed since I initially wrote the code so maybe I should adjust it to use that by default. I'm not sure we should add a setting for this, ideally the view should just do the right thing. I am currently travelling but I'll look into this once I'm back (in two weeks). Thank you very much for the patch! -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 367863] add string encoding="ebcdic"
https://bugs.kde.org/show_bug.cgi?id=367863 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added Latest Commit||http://commits.kde.org/okte ||ta/b455b93cb15fb3af078c48e7 ||0f326aa6efe6275e Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Alex Richardson <arichardson@gmail.com> --- Git commit b455b93cb15fb3af078c48e70f326aa6efe6275e by Alex Richardson, on behalf of Aaron Bishop. Committed on 27/10/2016 at 17:15. Pushed by arichardson into branch 'master'. add encoding="ebcdic" to string structures fix bug 367863 structures string encoding ebcdic Testing Done: builds, tested example from bug 367863 and it behaves as expected. ctest passes 100% of 54 tests. I only added one test condition to commonparsertest. REVIEW: 128795 M +2-0kasten/controllers/CMakeLists.txt M +2-0kasten/controllers/test/commonparsertest.cpp A +160 -0 kasten/controllers/view/structures/datatypes/strings/ebcdicstringdata.cpp [License: LGPL] A +55 -0 kasten/controllers/view/structures/datatypes/strings/ebcdicstringdata.h [License: LGPL] M +5-0 kasten/controllers/view/structures/datatypes/strings/stringdatainformation.cpp M +3-2 kasten/controllers/view/structures/datatypes/strings/stringdatainformation.h M +3-0kasten/controllers/view/structures/parsers/parserutils.cpp http://commits.kde.org/okteta/b455b93cb15fb3af078c48e70f326aa6efe6275e -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 367863] add string encoding="ebcdic"
https://bugs.kde.org/show_bug.cgi?id=367863 --- Comment #3 from Alex Richardson <arichardson@gmail.com> --- Thank you very much for the patch. Unfortunately I can't see the review request, it says "You don't have access to this review request. This review request is private. You must be a requested reviewer, either directly or on a requested group, and have permission to access the repository in order to view this review request." Possibly you didn't click publish yet? -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 367863] add string encoding="ebcdic"
https://bugs.kde.org/show_bug.cgi?id=367863 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- Added to my to do list. However, I am quite busy at the moment and probably won't have time to work on okteta for the next 2 months. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 367864] Specify Big or Little Endian for multi-byte structure primitives
https://bugs.kde.org/show_bug.cgi?id=367864
Alex Richardson <arichardson@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Alex Richardson <arichardson@gmail.com> ---
You can use to get the
desired result.
Or do you want to be able to have type aliases so that type="uint32-be" refers
to that? That is not implemented yet and I'm not sure it makes sense. You could
achieve that when using javascript structure definitions
(https://userbase.kde.org/Okteta/Writing_structure_definitions):
function uint32_be() {
var ret = uint32()
ret.byteOrder = "big-endian"
return ret;
}
function init() {
var mm_example = struct({foo: uint32_be()}
return mm_example;
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 361692] Clock doesn't update while compositing is off
https://bugs.kde.org/show_bug.cgi?id=361692 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added CC||arichardson@gmail.com --- Comment #3 from Alex Richardson <arichardson@gmail.com> --- For me the panel also sometimes stops updating (openSuSE Tumbleweed git snapshot packages). Not sure if it is related to disabling compositing as the only programs I had running at the time were KDevelop, Chromium and Konsole. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360854] New: Wrong file opened when double clicking on CMake error in outputview
https://bugs.kde.org/show_bug.cgi?id=360854 Bug ID: 360854 Summary: Wrong file opened when double clicking on CMake error in outputview Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Output Views Assignee: kdevelop-bugs-n...@kde.org Reporter: arichardson@gmail.com I discovered that some CMake errors would just open an empty editor whenever I double clicked on it. It turns out that this happens whenever the error is reported with a relative path because this path is interpreted relative to the build dir and not the source dir: CMake Error at foo/bar/CMakeLists.txt:27 (target_link_librariess): Unknown CMake command "target_link_librariess". This will open foo/bar/CMakeLists.txt in the build dir which doesn't exist so I get an empty editor instead. Should be an easy fix but I couldn't find the outputview file opening code in a quick search. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356231] Build not respecting "ranlib" and "ar" binaries
https://bugs.kde.org/show_bug.cgi?id=356231 Alex Richardson <arichardson@gmail.com> changed: What|Removed |Added CC||arichardson@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- I recall having a similar problem with CMake not wanting to use my custom ar binary in a different project. In the end I put an ar wrapper script into a new directory and prepended that to $PATH. Closing as this as an upstream CMake problem . -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 360577] New: Applying a project filter only removes files from background parser after restart
https://bugs.kde.org/show_bug.cgi?id=360577 Bug ID: 360577 Summary: Applying a project filter only removes files from background parser after restart Product: kdevplatform Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: language Assignee: kdevelop-bugs-n...@kde.org Reporter: arichardson@gmail.com When I add a project filter the files will still be parsed by the background parser until I restart. [19:26] thing is, we batch up all project files into the background parser, and probably don't remove those files when a filter is applied later on Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 --- Comment #19 from Alex Richardson <arichardson@gmail.com> --- Git commit bba0f034c4bdfdf9375b7532d134ef05214ce51b by Alex Richardson. Committed on 12/02/2016 at 12:48. Pushed by arichardson into branch '5.0'. Don't add HintedType instances to UnsureType if the target type exists But only do this if the HintedType also has the same context, otherwise they might be invalidated at separate times and removing one of them removes the still valid other HintedType. If we don't deduplicate here we still get UnsureTypes which have lots of entries like this: found potential duplicates when adding N6Python10HintedTypeE int(index = 774764) -> 67278 - int of type N8KDevelop13StructureTypeE 102814 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 139700 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 140778 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 191576 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 206348 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 346692 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 351636 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 362174 (aka 351724: int of type N6Python10UnsureTypeE) - int of type N6Python10HintedTypeE 386886 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 408898 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 533652 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 540306 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 573586 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 614644 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 618548 (aka 66042: bool of type N8KDevelop12IntegralTypeE) - bool of type N6Python10HintedTypeE 648374 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 665250 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 709684 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 750432 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 89504 (aka 66548: str of type N8KDevelop13StructureTypeE) - str of type N6Python10HintedTypeE 765024 (aka 90024: str of type N6Python10UnsureTypeE) - str of type N6Python10HintedTypeE 774764 (aka 403436: int of type N6Python10UnsureTypeE) - int of type N6Python10HintedTypeE REVIEW: 127039 M +6-0duchain/types/hintedtype.cpp M +2-0duchain/types/hintedtype.h M +38 -8duchain/types/unsuretype.cpp http://commits.kde.org/kdev-python/bba0f034c4bdfdf9375b7532d134ef05214ce51b -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 --- Comment #18 from Alex Richardson <arichardson@gmail.com> --- Thank you for fixing this! However there are still a lot of types being added that in my opinion don't need to exist: found potential duplicates when adding N6Python10HintedTypeE int(index = 774764) -> 67278 - int of type N8KDevelop13StructureTypeE 102814 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 139700 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 140778 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 191576 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 206348 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 346692 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 351636 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 362174 (aka 351724: int of type N6Python10UnsureTypeE) - int of type N6Python10HintedTypeE 386886 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 408898 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 533652 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 540306 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 573586 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 614644 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 618548 (aka 66042: bool of type N8KDevelop12IntegralTypeE) - bool of type N6Python10HintedTypeE 648374 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 665250 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 709684 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 750432 (aka 67278: int of type N8KDevelop13StructureTypeE) - int of type N6Python10HintedTypeE 89504 (aka 66548: str of type N8KDevelop13StructureTypeE) - str of type N6Python10HintedTypeE 765024 (aka 90024: str of type N6Python10UnsureTypeE) - str of type N6Python10HintedTypeE 774764 (aka 403436: int of type N6Python10UnsureTypeE) - int of type N6Python10HintedTypeE I'll submit a patch shortly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 359265] New: Lots of "No language dictionaries for the language: "foo" " messages when editing files
https://bugs.kde.org/show_bug.cgi?id=359265
Bug ID: 359265
Summary: Lots of "No language dictionaries for the language:
"foo" " messages when editing files
Product: frameworks-ktexteditor
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: arichardson@gmail.com
I get lots of stderr messages like
No language dictionaries for the language: "en"
No language dictionaries for the language: "en"
No language dictionaries for the language: "de"
No language dictionaries for the language: "de"
whenever I open a file in Kate or KDevelop and I think also sometimes during
editing.
The error is printed in Sonnet::Loader::createSpeller() because there is only
/usr/share/hunspell/de_DE.aff, /usr/share/hunspell/de_DE.dic,
/usr/share/hunspell/en_US.aff, /usr/share/hunspell/en_US.dic, etc.
Symlinking /usr/share/hunspell/de_DE.{aff,dic} to
/usr/share/hunspell/de.{aff,dic} and the same with en_GB -> en silenced the
message, but to me it seems ktexteditor should not keep trying to open the "en"
or "de" Speller if it was not found the first time. (possibly fall back to the
first en_* and de_* file it finds? And of course similarly for other languages
that have multiple variants.
For now the symlink fixes it for me, but I think we should somehow guess the
right variant (or not have the no variant option at all for spell checking)
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 --- Comment #14 from Alex Richardson <arichardson@gmail.com> --- I added some debug output into UnsureType::addType() and get the rather confusing: "unsure (str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str)" + "int" -> "unsure (str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int, str, int)" UnsureType::addType() checks if a type as already contained, so the int should not be added. Similarly I also get this: "unsure (Path, str, Path, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path)" + "str" -> "unsure (Path, str, Path, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, str, Path, st
[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 --- Comment #15 from Alex Richardson <arichardson@gmail.com> --- I am also getting some of these messages: kdevplatform.language: invalid item for index 35 1478 0 In case it helps: This is the huge unsure type that is being created (it is now so large that outputting the debug info is starting to cause noticeable lags): "unsure (str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declaration), Path, str), str, list of unsure (str, int), unsure (list of void, list), list of str, list of unsure ((unknown direct declara
[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 --- Comment #12 from Alex Richardson <arichardson@gmail.com> --- Created attachment 97119 --> https://bugs.kde.org/attachment.cgi?id=97119=edit debug output Still happening, here is some debug output -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 358563] Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 --- Comment #4 from Alex Richardson <arichardson@gmail.com> --- I was editing the script here: https://github.com/RichardsonAlex/cheri-scripts Hasn't happended the last two days, but I have only done minor edits, so I guess the number of UnsureType instances haven't grown enough. I'll post a backtrace next time the freeze happens. Any suggestions where I should add some qDebug() calls to make this easier to debug? -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 358563] New: Possible infinite loop in UnsureType::toString()
https://bugs.kde.org/show_bug.cgi?id=358563 Bug ID: 358563 Summary: Possible infinite loop in UnsureType::toString() Product: kdev-python Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@svenbrauch.de Reporter: arichardson@gmail.com CC: m...@svenbrauch.de When I open subprocess.py kdevelop freezes. The process is stuck in UnsureType::toString() (stack traces points to outline view trying to call toString() on the return type of subprocess.check_call(). This only happens after editing python code kdevelop for a while. Possibly every time a new UnsureType is created this is distinct from all others (even though the the types should be the same) so that the is_new_type() check returns false. It might not be an infinite loop, but I decided to kill KDevelop after about 2 minutes. When I attached a debugger the types list had over 500 entries, it seems to me like that should not happen. Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 356870] Okteta doesn't support table files/custom character encodings.
https://bugs.kde.org/show_bug.cgi?id=356870 --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- Are these all 1byte = 1 character encodings? Do you want them displayed in the main view next to the hex bytes? Or would a workaround using the structures tool be acceptable? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356781] Yakuake tab bar looks bad on High DPI monitors
https://bugs.kde.org/show_bug.cgi?id=356781 --- Comment #3 from Alex Richardson <arichardson@gmail.com> --- Good to hear that you already have plans. If you have any code that needs testing, I'd be happy to do it. It probably makes sense to test it on multiple monitors with different DPI (mine is 157 DPI). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356781] New: Yakuake tab bar looks bad on High DPI monitors
https://bugs.kde.org/show_bug.cgi?id=356781 Bug ID: 356781 Summary: Yakuake tab bar looks bad on High DPI monitors Product: yakuake Version: Git (Frameworks 5) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: arichardson@gmail.com I recently got a HighDPI monitor and noticed that the tab bar of Yakuake is too small. Looking at the code it appears that it is using hard-coded pixel sizes for the themes. Ideally it should be based on the size of the fonts and possibly use SVG for theming. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356781] Yakuake tab bar looks bad on High DPI monitors
https://bugs.kde.org/show_bug.cgi?id=356781 --- Comment #1 from Alex Richardson <arichardson@gmail.com> --- Created attachment 96130 --> https://bugs.kde.org/attachment.cgi?id=96130=edit screenshot of the tab bar -- You are receiving this mail because: You are watching all bug changes.
