siren186

Results 11 issues of siren186

cppjieba::Jieba构造函数如下,参数为std::string ``` Jieba(const string& dict_path, const string& model_path, const string& user_dict_path, const string& idfPath, const string& stopWordPath) ``` 读取文件时,因为中文是以UTF-8编码存储在std::string中的,所以会造成找不到指定的文件,打开文件失败。 ``` ifstream ifs(filePath.c_str()); ```

enhancement

**Describe the bug** Each thread in `Poco::ActiveThreadPool` has its own `Poco::NotificationQueue`. If I have 2 types of Runnable like this: ```cpp class LongTimeTask : public Poco::Runnable { void run() {...

enhancement

**Describe the bug** `Poco::Manifest` class has `STL` member, It will crash if DLL and EXE use different Run-Time Library (MT/MD) **To Reproduce** Build options: VS2019 + debug_static_**mt** + x64 (...

wontfix

**Describe the bug** `Poco::Logger` can not output `__FILE__` and `__LINE__` **To Reproduce** ```cpp // Here is the problem, It's very strange in my Visual Studio 2019 (with Qt5.15.2) // I...

enhancement

**Describe the bug** [A clear and concise description of what the bug is.](https://github.com/pocoproject/poco/commit/d5a5ebc2d7af2cba520c29cc29075b3982eb099c#r141975904) ```cpp NestedDiagnosticContext& NestedDiagnosticContext::current() { static NestedDiagnosticContext ndc; return ndc; } ``` It should use `Thread Local Storage`...

bug

1. Fixed #4544 2. Fixed #4634 3. Support dynamic manages and recycles individual `Poco::Thread` objects. 4. Support priority queue tasks

enhancement

`ActiveThreadPool.cpp` file is not in `Threading` folder. ![2024-08-26_140412](https://github.com/user-attachments/assets/a3538ca8-6972-47a7-9140-34c4174e2133)

**Describe the bug** ```cpp class A { public: A(int n) {} }; int main(int argc, char** argv) { std::optional a1; // ok Poco::Optional a2; // compile error !!! return 0;...

bug

```cpp void test_std() { std::mutex m; std::unique_lock guard(m); guard.unlock(); // OK guard.lock(); // OK } void test_poco() { Poco::Mutex m; Poco::ScopedLockWithUnlock guard(m); guard.unlock(); // OK guard.lock(); // Failed !!! }...

If a thread in the pool finised its **first task**, than it will call `_targetCompleted.set()`, And than the thead will continue to run its **second task** without calling `_targetCompleted.reset()`. If...

bug