fix: sqlite always not work and another things

this is a huge pr.. before I think this project won't maintain anymore
so I work myself, and follow another fork.. but that one also inactive

I will pr for this

This pr induced typos ci, dependabot, bump a lot of dependencies, make
format, remove deperate function and etc

Author: Decodetalkers

.github/ISSUE_TEMPLATE/tracking-issue.md

@@ -0,0 +1,41 @@
+---
+name: Tracking issue
+about: Tracking issues are used to track progress on massive efforts (refactoring
+  or massive new feature)
+title: ''
+labels: tracking
+assignees: ''
+
+---
+
+# State of art
+
+<!-- 
+
+Describe how things work now. How overall architecture of the current solution works. If possible, try to dig for why this solution was employed.
+
+-->
+
+# Why to change? 
+
+<!--
+
+Describe, why current solution is not good enough. Discuss what drawbacks it has and how they affect KLSP. 
+
+-->
+
+#  Implementation considerations
+
+<!--
+
+Provide your ideas and insights on how the solution can be implemented in a better way. This includes describing new architecture, highlighting important differences from the old one. You should also mention benefits the new solution brings in.
+
+-->
+
+# Task
+
+<!-- 
+
+Formulate a task as clean as possible. The task should be precise and limited in scope. If issue can't be described within single task, present tasks as a list with checkboxes. Each task MAY has its own issue associated to track it separately 
+
+-->

.github/dependabot.yml

@@ -0,0 +1,33 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+# docs
+# https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+version: 2
+updates:
+  - package-ecosystem: "gradle"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      # We release on Tuesdays and open dependabot PRs will rebase after the
+      # version bump and thus consume unnecessary workers during release, thus
+      # let's open new ones on Wednesday
+      day: "wednesday"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
+    groups:
+      # Only update polars as a whole as there are many subcrates that need to
+      # be updated at once. We explicitly depend on some of them, so batch their
+      # updates to not take up dependabot PR slots with dysfunctional PRs
+      polars:
+        patterns:
+          - "polars"
+          - "polars-*"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "wednesday"

.github/workflows/build.yml

@@ -3,7 +3,7 @@ name: Build
 on:
   push:
     branches:
-      - main
+      - master
   pull_request:
   workflow_dispatch:
 
@@ -17,12 +17,14 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Setup JDK
-        uses: actions/setup-java@v3
+        uses: actions/setup-java@v4
         with:
           distribution: 'temurin'
           java-version: ${{ matrix.java }}
       - name: Setup Gradle
-        uses: gradle/gradle-build-action@v2
+        uses: gradle/actions/setup-gradle@v3
+        with:
+          cache-disabled: ${{ contains(matrix.os, 'windows') }}
       - name: Build
         run: ./gradlew :server:build :shared:build -PjavaVersion=${{ matrix.java }}
       - name: Detekt

.github/workflows/typos.yml

@@ -0,0 +1,19 @@
+---
+# yamllint disable rule:line-length
+name: check_typos
+
+on:  # yamllint disable-line rule:truthy
+  push:
+  pull_request:
+    branches:
+      - '**'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: typos-action
+        uses: crate-ci/typos@v1.29.4

.gitignore

@@ -16,9 +16,6 @@ build
 target
 out
 
-# Kotlin
-.kotlin
-
 # Python
 __pycache__
 
@@ -32,3 +29,4 @@ node_modules
 !.vscode/tasks.json
 *.vsix
 kls_database.db
+.kotlin

CHANGELOG.md

@@ -3,9 +3,6 @@ All notable changes to the language server will be documented in this file.
 
 Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
 
-## [1.3.13]
-- Bump Kotlin to 2.1.0
-
 ## [1.3.12]
 - Make code generation for Java interop opt-in (#585)
 

CONTRIBUTION.md

@@ -0,0 +1,126 @@
+
+# Project workflow and Guidelines
+
+## Conventional commits
+
+We love and therefore use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
+
+Conventional commits requires next commit types:
+- `feat`
+- `fix`
+
+
+Additionally we introduce the next ones:
+- `refactor` - for changes, which heavily modifies the code with the sole goal to simplify the code. The change MUST NOT introduce any new features, but MAY introduce fixes occasionally.
+- `chore` - for small changes, such as variable/file renaming, changes to comments, import organisation, formatting
+
+## Feature based workflow
+
+We use feature based workflow, which implies branch per feature/bug/issue
+
+## Guidelines
+
+Project has a lot of old code. It heavily relies on side-effects. Whenever working on project, try to spot usage of side effects and rewrite them with pure code.
+
+## SCRUM
+
+SCRUM appreciates initiative from every project participant. You can choose and create tasks for your self, define your focus as long, as this aligns with major project goals.
+
+## ~~Tracking issues~~
+
+> ### ⚠️Tracking issues are canceled.
+> We are using epics, user stories and tasks for the same purpose on our Taiga board. Please, use [this](./.github/ISSUE_TEMPLATE/tracking-issue.md) template.
+
+~~If you want to introduce massive change, please create a corresponding tracking issue and pull-request.~~
+
+## Project-wise requirements
+
+> These requirements apply to the project as a whole.
+
+KLSP:
+- ***MUST NOT* create any system files in user's project folder, and user's home folder.**
+  - It clogs user's project with unnecessary information which can be stored in more appropriate place. Such files can be modified, deleted or corrupted in other way.
+  - Consider using temp files or placing files according to XDG specs (`~/.config/<program-name>/config`)
+  - Temporary files, such as logs and databases, are allowed to be stored in OS's temp directory.
+- *SHOULD NOT* rely on editor specific features
+- *SHOULD* have dedicated class for server configuration. sourcepath, etc.
+- ***SHOULD NOT* rely on command line tools even if they are a part of POSIX standard.**
+  - Command line tools are mainly designed for humans, not programs. Their usage involves text parsing which is error prone approach. Usage of CLI tools via ProcessBuilder or any other means of process spawning is considered a crutch and should be replaced with a proper API calls.
+
+
+# Development
+
+## New to Kotlin?
+
+Check out these links:
+- [Kotlin Function features](https://kotlinlang.org/docs/functions.html)
+- [infix notation](https://kotlinlang.org/docs/functions.html#infix-notation)
+- [Kotlin lambdas](https://kotlinlang.org/docs/lambdas.html)
+- [Scope functions](https://kotlinlang.org/docs/scope-functions.html)
+
+While working with kotlin, you are likely to encounter concepts from the above list
+
+## How to Setup Custom Kotlin Language Server
+
+> Custom version of [`vscode-kotlin`](#custom-vscode-kotlin) required
+
+While working on this project, it may be useful to try it out right away! Luckily for us, `vscode-kotlin` extension supports custom versions for kotlin-language-server.
+
+Check out [kotlin.languageServer.path](vscode://settings/kotlin.languageServer.path) in vscode settings (if link does not work, use above setting id to search for it). The setting requires a path to `kotlin-language-server` bash script. The script is auto generated by Gradle. The script is useless by itself and requires full `kotlin-language-server` installation to be present. To make such installation from sources, run:
+```
+gradlew installDist
+```
+
+> The command generates unpacked ready to be used `kotlin-language-server` installation.
+
+> Installation consists of all required dependencies, the server itself and the script
+
+Set [kotlin.languageServer.path](vscode://settings/kotlin.languageServer.path) to `<workspaceRoot>/server./server/build/install/server/bin/kotlin-language-server`. Replace `<workspaceRoot>` with the actual path tp `kotlin-language-server` repository on your local filesystem.
+
+## Launch Kotlin Language Server in Debug mode
+
+> **⚠️ All setting mentioned in this section should be set for *WORKSPACE* profile only!**
+
+![workspace-settings](./images/workspace-settings.png)
+
+Kotlin language server supports debugging in next [connection modes](vscode://settings/kotlin.languageServer.transport):
+ - `tcp-attach`
+ - `stdio`
+
+### STDIO Connection
+
+In `stdio` mode `vscode-kotlin` extension completely manages server lifecycle. That is you can't manually restart on completely stop the server. To restart the server do the following: `Ctrl + Shift + P` to open vscode command prompt -> `Developer: Reload Window`. This will reload window and restart extension host, so the kotlin server would be restarted too.
+
+Then activate these settings:
+- [kotlin.languageServer.debugAttach.enabled](vscode://settings/kotlin.languageServer.debugAttach.enabled)
+- [kotlin.languageServer.debugAttach.autoSuspend](vscode://settings/kotlin.languageServer.debugAttach.autoSuspend)
+
+### TCP Attach
+
+On the other hand, `tcp-attach` mode allows *you* to manage lifecycle of the server. `vscode-kotlin` automatically connect/reconnects to the server when server becomes available. When server is killed, extension automatically disconnects and waits for new instance of the server.
+
+In this mode, you manage the server. To start it, use the next command from the root of `kotlin-language-server` workspace:
+
+```
+./server/build/install/server/bin/kotlin-language-server --tcpClientPort 7721
+```
+
+This launches the server in `TCP Client` mode. The server will connect to the specified `tcpClientPort`.
+
+Default port is `7721`
+
+#### Implementation details
+
+`vscode-kotlin` launches tcp server to accept new connections. Once `vscode-languageclient` requests new connection, `vscode-kotlin` starts to listen for new connections on the [kotlin.languageServer.port](vscode://settings/kotlin.languageServer.port). When single connection is accepted, `vscode-kotlin` stops to listen for new connections. Once connections is closed and `vscode-languageclient` requests new connection, `vscode-kotlin` starts to listen for connections again.
+
+## Custom `vscode-kotlin`
+
+We have fork of `fwcd/vscode-kotlin` in our organisation: `Kotlin-Language-Server/vscode-kotlin`. Our fork is the *custom* version of the extension. If you are a part of the team, you can download custom builds from github.
+
+1. Proceed to [Build and Publish Devs Only](https://github.com/Kotlin-Language-Server/vscode-kotlin/actions/workflows/build.yml)
+2. Click on the latest run
+3. Scroll down until **Artifacts** section appears
+4. Press download button on the right side of `vscode-kotlin-<short_sha>`
+5. Unzip the downloaded artifact
+6. Install `kotlin.vsix`
+7. Reload vscode

EDITORS.md

@@ -84,29 +84,6 @@ require'lspconfig'.kotlin_language_server.setup{
 ## Monaco Editor
 See [kotlin-monaco-language-server](https://github.com/yahorbarkouski/kotlin-monaco-language-server).
 
-## Helix
-
-Using [languages.toml](https://github.com/helix-editor/helix/blob/master/book/src/languages.md)
-
-```toml
-[language-server.kotlin-language-server]
-command = "kotlin-language-server"
-
-[[language]]
-name = "kotlin"
-scope = "source.kotlin"
-file-types = ["kt", "kts"]
-roots = ["settings.gradle", "settings.gradle.kts"]
-comment-token = "//"
-block-comment-tokens = { start = "/*", end = "*/" }
-indent = { tab-width = 4, unit = "    " }
-language-servers = [ "kotlin-language-server" ]
-
-[[grammar]]
-name = "kotlin"
-source = { git = "https://github.com/fwcd/tree-sitter-kotlin", rev = "a4f71eb9b8c9b19ded3e0e9470be4b1b77c2b569" }
-```
-
 ## Other Editors
 Install a [Language Server Protocol client](https://microsoft.github.io/language-server-protocol/implementors/tools/) for your tool. Then invoke the language server executable in a client-specific way.
 

README.md

@@ -5,18 +5,35 @@
 [![Downloads](https://img.shields.io/github/downloads/fwcd/kotlin-language-server/total)](https://github.com/fwcd/kotlin-language-server/releases)
 [![Chat](https://img.shields.io/badge/chat-on%20discord-7289da)](https://discord.gg/cNtppzN)
 
+## Notice and status
+
+This is fork of currently almost unmaintained upstream repo: https://github.com/fwcd/kotling-language-server
+
+*This fork* is being maintained in developers' spare time. Our goal is to make this extension usable and feature complete. We *do not* aim for full feature parity with JetBrains ide's Kotlin support.
+
+> We do support only Linux and MacOS. Windows is not tested but still may work. Windows only        issues has least priority.
+
+## Kotlin Language Server
+
 A [language server](https://microsoft.github.io/language-server-protocol/) that provides smart code completion, diagnostics, hover, document symbols, definition lookup, method signature help and more for [Kotlin](https://kotlinlang.org).
 
 ![Icon](Icon128.png)
 
 Any editor conforming to LSP is supported, including [VSCode](https://github.com/fwcd/vscode-kotlin) and [Atom](https://github.com/fwcd/atom-ide-kotlin).
 
+### Scope of the project
+
+This project is strictly limited by Language Server Protocol capabilities. We aim to provide complete language server experience.
+
+Some features, that our users may expect, lies outside of our responsibility. We won't deliver any features related to code and test running, project building. These tasks should be performed by other means. We offload these features to editor specific extensions.
+
 ## Getting Started
 
+* See [CONTRIBUTION.md](CONTRIBUTION.md) for development guidelines
+* See [Taiga board](https://tree.taiga.io/project/owl-from-hogvarts-kotlin-language-server/timeline) for ongoing and planed work. Core team uses it as main tool for cooperation and project's status tracking
 * See [BUILDING.md](BUILDING.md) for build instructions
 * See [Editor Integration](EDITORS.md) for editor-specific instructions
 * See [Troubleshooting](TROUBLESHOOTING.md) for tips on troubleshooting errors
-* See [Roadmap](https://github.com/fwcd/kotlin-language-server/projects/1) for features, planned additions, bugfixes and changes
 * See [Kotlin Quick Start](https://github.com/fwcd/kotlin-quick-start) for a sample project
 * See [Kotlin Debug Adapter](https://github.com/fwcd/kotlin-debug-adapter) for editor-agnostic launch and debug support of Kotlin/JVM programs
 * See [tree-sitter-kotlin](https://github.com/fwcd/tree-sitter-kotlin) for an experimental [Tree-Sitter](https://tree-sitter.github.io/tree-sitter/) grammar
@@ -27,6 +44,8 @@ Any editor conforming to LSP is supported, including [VSCode](https://github.com
 
 ## This repository needs your help!
 
+> See [CONTRIBUTION.md](./CONTRIBUTION.md)
+
 [The original author](https://github.com/georgewfraser) created this project while he was considering using Kotlin in his work. He ended up deciding not to and is not really using Kotlin these days though this is a pretty fully-functional language server that just needs someone to use it every day for a while and iron out the last few pesky bugs.
 
 There are two hard parts of implementing a language server:
@@ -114,5 +133,12 @@ The Kotlin language server supports some custom initialization options via the `
 
 
 ## Authors
+
+### Current maintainers team
+* [owl-from-hogvarts](https://github.com/owl-from-hogvarts)
+* [localPiper](https://github.com/localPiper)
+* [Zerumi](https://github.com/zerumi)
+
+### Original authors
 * [georgewfraser](https://github.com/georgewfraser)
 * [fwcd](https://github.com/fwcd)