zsh: command not found: nvim

Hi guys, I'm relatively new to programming and whilst trying to pick up vim, chanced upon bob as a neovim version manager. I installed bob according to instructions and even ran the "bob use latest" command without any error. But when i typed nvim -v in my terminal, it says "zsh: command not found: nvim". Anyone has any idea why this is happening?
Thanks in advance!

Did you add the neovim executable to your $PATH?

Ah yes, thank you! Including export PATH="$PATH:/path/to/nvim-directory/" into my .zhsrc solve the problem!

I had the same problem on Ubuntu 22.04.3 and solved by adding the following line to my ~/.bashrc:
export PATH="/home/marco/.local/share/bob/v0.9.4/nvim-linux64/bin/:$PATH"

Do I need to update that line every time I switch neovim version with bob?

Did you add the neovim executable to your $PATH?

@MordechaiHadad would you consider adding this information to the installation steps in the README?

You don't add a specific neovim version to $Path but rather /home/user/.local/share/bob/nvim-bin
And once u add this u no longer need to mess with it


making repositioning of context tag and project tag optional

I love to use todo.txt in a natural way of language:

discuss with @George about +superproject concerning the aspect of unicorns

This is in consensus with the todo.txt rules i read: "Contexts and Projects may appear anywhere in the line after priority/prepended date"
In my sleek this will show up like this, the sentence is destroyed

discuss with about concerning the aspect of unicorns @George +superproject

I fully respect that in your perspective this is not a bug but a feature.
I would like to use it without the feature of putting tags at the and of the line - perhaps there could be an option  to switch this behaviour off?
Thanks!

Hi @Tobida . I'm totally with you on this topic and would prefer it the way you describe it too. But this is actually not up to me, as I use a JavaScript library to do the parsing of the text into proper todo.txt objects. And while it does a great job in general, it doesn't persist the position of projects and contexts after generating the object, but sorts these attributes in it's own way.
But in fact there is a feature request for exactly that feature at the project: https://github.com/jmhobbs/jsTodoTxt/issues/5
You can give it a push over there and as soon as they implement it, I will include it into sleek.

A similar repositioning request: is it possible to have a function to sort the projects/contexts inside the todo alphabetically?
For example,
(A) todo +b +a @context_b @context_a

running the function makes it
(A) todo +a +b @context_a @context_b
         ^     ^

+1, super important imho

Agree here - I am never likely to use  to use Slick seriously if it messes with the Todo file and changing the order of the words is a serious problem. One if the points if the protocol is to be  be able to use natural text.

I'm closing here, the issue will further discussed in https://github.com/ransome1/sleek/issues/68

I'm closing here, the issue will further discussed in #68

Isn't this #68? 🧐

Hello @ransome1 ,
since https://github.com/jmhobbs/jsTodoTxt/issues/5 has been getting some attention lately, I wondered if the matter could be addressed in Sleek again. You closed https://github.com/ransome1/sleek/issues/68 in September, but I didn't find an open issue with that problem (https://github.com/ransome1/sleek/issues/92, https://github.com/ransome1/sleek/issues/183, https://github.com/ransome1/sleek/issues/216, https://github.com/ransome1/sleek/issues/220, https://github.com/ransome1/sleek/issues/306, https://github.com/ransome1/sleek/issues/370 and https://github.com/ransome1/sleek/issues/411 are all closed).
Things have been getting better, since ticking of a box now only changes that very line, and not the whole file any more. But the resorting on the ticked todo is still happening unfortunately.
Sleek is getting better and better every week, I am really hoping to be able to use it to tick off todos as well soon : )
Please let me know what you think.
Thanks!

Yes, as soon as jsTodoTxt is finishing the rewrite, sleek will adapt to it and hopefully this will solve these issues.
But for now the latest version of jsTodoTxt is alpha and for almost two weeks there has been no progress. I will start implementing as soon as a stable version has been released and the documentation is complete :)

I'm closing here, the issue will further discussed in #68

Isn't this #68? 🧐

Indeed it is. There was no good reason to close here. I'll reopen.

Wow,
that's a swift response, thanks @ransome1 ! Also thanks for reopening. You have no idea how much I am looking forward to using Sleek as my daily driver.

I think this issue is fixed in the upstream Library. Any word on when this might get integrated?

I think this issue is fixed in the upstream Library. Any word on when this might get integrated?

The author started a complete rewrite and as of mid of October and so far I have only seen a very early alpha.

I'm currently rewriting sleek and during the process I switched to the current Alpha branch of jsTodoTxt. Thanks to the good work upstream, the future implementation will render (C) Lorem +ipsum dolor @amet lorem due:2023-11-11 amet dolor pm:2 lorem ipsum dolor amet like this:

I will soon publish a first developer preview for testing purposes.

Excellent!  Whoohoo! Thank you!

I'm currently rewriting sleek and during the process I switched to the current Alpha branch of jsTodoTxt. Thanks to the good work upstream, the future implementation will render (C) Lorem +ipsum dolor @amet lorem due:2023-11-11 amet dolor pm:2 lorem ipsum dolor amet like this:

I will soon publish a first developer preview for testing purposes.

Oh wow, can't wait! Thank you so much. So looking forward to using Sleek as my one-stop-solution!

@intrepidsilence @Tobida @dnngll @aubreyz @9z0 this should have solved in the very early developer preview of 2.0. Feel free to test it: https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev1

Thank you so much! I just tried sleek-2.0.0-dev1-win.zip, but I am unable to open an existing file:

Only after restarting Sleek, I see this (todo.txt is full of tasks):

I didn't change any settings, just unzipped and started it. Am I doing sth. wrong here?
Thanks!

Awesome! Thank you so much! Works for me (macOS ARM).

I tried the release you picked on my Windows machine and it worked. However I don't think you're doing anything wrong here, it must just work on all systems equally. This version also doesn't touch your current configuration file, so that shouldn't be the problem neither.
I could recreate the view you see, after I renamed/deleted the file I already added. Are you running into the issue with the .exe or Setup release files, as well?

Thank you so much! I just tried sleek-2.0.0-dev1-win.zip, but I am unable to open an existing file:

Only after restarting Sleek, I see this (todo.txt is full of tasks):

I didn't change any settings, just unzipped and started it. Am I doing sth. wrong here?
Thanks!

When you click on "File" in that top bar menu, do you see your todo file listed there?

When you click on "File" in that top bar menu, do you see your todo file listed there?

I do:

I just tried the same as above, but with "sleek-2.0.0-dev3-win.zip". I deleted everything in the folder "Sleek" and copied the contents of the new .zip in there. Right at first start I see this:

I did not tell Sleek (dev3) where to look for the file. I only set this up before in (the now deleted) Sleek (dev1) 🧐
Besides this, the todo is not loading (same as before on dev1)...

@dnngll thanks for looking into again. I was able to recreate it on Windows. I will propably have it fixed with the next developer preview.

@dnngll thanks for looking into again. I was able to recreate it on Windows. I will propably have it fixed with the next developer preview.

@ransome1
you're very welcome - thank you!
And: Were you talking about fixing the "file"-problem, or the "portable app saves settings somewhere else"-problem?

@dnngll thanks for looking into again. I was able to recreate it on Windows. I will propably have it fixed with the next developer preview.

@ransome1
you're very welcome - thank you!
And: Were you talking about fixing the "file"-problem, or the "portable app saves settings somewhere else"-problem?

Why exactly it crashed in the Dev1 I still havn't figured out. But as for the reason why it still doesn't work for Dev 3 is most likely the old config files from Dev 1. In these something essential is missing, which made sleek not start on my Windows machine.
Can you please delete the userData folder, which is located here: C:\Users\YOURUSERNAME\AppData\Roaming\sleek\userData
After doing this, a fresh default configuration will be created, which hopefully solves the issue on your side.

I'll do you one better: Just restored Windows from an image where Sleek has never been started on, plus deleted all files in the portable (dev3) directory and unzipped again.
This is what I get without restarting Sleek:

And this after restarting sleek:

So I guess it'll be best to wait for dev4, huh?

Dev 4 won't solve it, unless we figure out what leads to this behavior on your side.
Do you know your way around PowerShell? I think it comes installed on a Windows machine. If you start sleek from shell, it will most likely throw you an error, with which we could work. You would need to navigate to the folder, in which sleek.exe is located. Then just type .\sleek.exe. This should start the app and in PowerShell you will see some logs.

Sure. This is starting Sleek dev3 (after the userfolder has been deleted), and then opening the "! ToDo.txt":
PS Z:\sleek> .\sleek.exe
PS Z:\sleek>
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: Z:\Sleek\! ToDo.txt
FileWatcher.ts: Initial scan complete. Ready for changes
TypeError: Cannot read properties of null (reading '2')
    at t.Item.parse (Z:\sleek\resources\app.asar\dist\main\main.js:14:248482)
    at new t.Item (Z:\sleek\resources\app.asar\dist\main\main.js:14:248288)
    at Z:\sleek\resources\app.asar\dist\main\main.js:14:326887
    at Array.map (<anonymous>)
    at Z:\sleek\resources\app.asar\dist\main\main.js:14:326866
    at _ (Z:\sleek\resources\app.asar\dist\main\main.js:14:327359)

I hope, that helps?

Not until now.
This is what I get when starting Sleek dev3 (after the userfolder has been deleted), and then creating a new file from within Sleek, and then adding 2 todo's:
PS Z:\sleek> .\sleek.exe
PS Z:\sleek>
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: Z:\Sleek\todo.txt
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
File Z:\Sleek\todo.txt has been changed
ipcEvents.ts: FIX ME!
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files
File Z:\Sleek\todo.txt has been changed
ipcEvents.ts: FIX ME!
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for files

Or as a Screenshot:

Looks better definitely : )

No, I wouldn't say so. I got €äöüÄÖÜß in it, but the file worked on the previous version of sleek (and a couple of other tools I am using.
I will delete half of it and check, then try the other half and so on... will get back to you in a bit!

Thanks for figuring this out together

Nonono thank you for your work!!! 😊
I think we're getting somewhere. ! ToDo 1.txt does not work, ! ToDo 2.txt does. Only difference is the last empty line:

However: Just deleting the last line from my original ToDo won't fix it until I only have 1 ToDo left... Doesn't matter which one. This file:

does not work!

I tried to reproduce it the way you describe it. Created the same file, I have a Windows machine running, I use Sublime Text and the sleek Dev3. But I simply cannot reproduce it :/
If you say "it does not work", you mean the screen stays white and the same error pops up in PowerShell?
Also, would you mind sharing the config.json file in userData folder? It doesn't contain any sensitive data.

Would you like to see my shared screen? Maybe that's a little easier to see
what I'm doing, and if I'm making any mistakes... I'm using Senfcall, it's
browser based, no need to install anything. We could do it right now.
On Wed, Jul 26, 2023, 21:16 ransome @.***> wrote:

I tried to reproduce it the way you describe it. Created the same file, I
have a Windows machine running, I use Sublime Text and the sleek Dev3. But
I simply cannot reproduce it :/
If you say "it does not work", you mean the screen stays white and the
same error pops up in PowerShell?
Also, would you mind sharing the config.json file in userData folder? It
doesn't contain any sensitive data.
—
Reply to this email directly, view it on GitHub
https://github.com/ransome1/sleek/issues/68#issuecomment-1652354160, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADBVOSVUAESV4Z7MA5ZJHWTXSFUIVANCNFSM4ZTEEN4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Would you like to see my shared screen? Maybe that's a little easier to see what I'm doing, and if I'm making any mistakes... I'm using Senfcall, it's browser based, no need to install anything. We could do it right now.

Would you like to see my shared screen? Maybe this way it's a little easier to see what I'm doing, and if I'm making any mistakes... I'm using Senfcall, it's browser based, no need to install anything. We could do it right now.

Would you like to see my shared screen? Maybe this way it's a little easier to see what I'm doing, and whether I'm making any mistakes... I'm using Senfcall, it's browser based, no need to install anything. We could do it right now.

Come to
https://public.senfcall.de/sleek
if you're interested in a quick live demo...

if you're interested in a quick live demo...

Hmm you seem to not have gotten my last message yet. Will leave the room again... We can still do this tomorrow if you think it might help.

If you say "it does not work", you mean the screen stays white and the same error pops up in PowerShell?

I didn't start it with powershell this time. But the result is the same as above (https://github.com/ransome1/sleek/issues/68#issuecomment-1652146774).

Also, would you mind sharing the config.json file in userData folder? It doesn't contain any sensitive data.

Sure. That's the config after deleting the userfolder, starting and closing Sleek:
{
  "sorting": [
    "priority",
    "due",
    "projects",
    "contexts",
    "t",
    "completed",
    "created"
  ]
}

And that's the config after reopening "the Sleek from above" (without deleting the userfolder this time), adding the todo-file and then closing it:
{
	"sorting": [
		"priority",
		"due",
		"projects",
		"contexts",
		"t",
		"completed",
		"created"
	],
	"files": [
		{
			"active": true,
			"path": "Z:\\Sleek\\! ToDo.txt",
			"filename": "! ToDo.txt"
		}
	]
}

I hope this helps?
I will go to bed now, have a good night!

Come to
https://public.senfcall.de/sleek
if you're interested in a quick live demo...

Oh no, sorry. I was already off the computer when you wrote this. But much appreciated!
I think now I have everything you could provide and it's up to me now to reproduce it. I'll keep you posted.

I think now I have everything you could provide

Perfect, let me know if you need anything more!

Hey @ransome1
just a quick info: Using sleek-2.0.0-dev5-win.zip [dad1345a10ef6308a4dbcd65af405068] (on a brand new system, where sleek has never been started on) I still have the same problem as above... The offer about showing you my screen is still there if that helps.

@dnngll It really is a mystery to me.
Although I'm working on a Mac, I have a Windows system here and the Dev5 works without any issue. Same goes for Linux.
With one of the earlier developer previews I ran into a problem, similar to what you were experiencing. That was due to an incompatibility of the config files from different versions.
From Dev4 on this should not be an issue any longer, because for every new developer preview version the config is freshly created and put into its own versionized folder.
If you start sleek.exe from Power Shell, does it give you a new/different error or anything?
Also can I ask you to completely move or delete your config folder, just to make sure it is not the configs' fault?
If you start sleek with the Power Shell it will output the location where the config folder is located. It should be something like: C:\Users\[YOURUSERNAME]\AppData\Roaming\sleek\userData2.0.0-dev5

And one more question: Is there a way you could create a todo file, which crashes sleek on your side and send it to me? One with just bogus data. You can send it here<EMAIL_ADDRESS>

@dnngll if your issue is related to the filewatcher, which is being used in sleek, we should give this latest developer preview a chance: https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev7
I tweaked the configuration a little bit. I'm still curious about a "broken" text file from you, in order to fully reproduce this.

Hey @ransome1
using the now new sleek-2.0.0-dev7-win.zip [ace17a1a2cf7bd4daa08f12dc24205b9].

From Dev4 on this should not be an issue any longer, because for every new developer preview version the config is freshly created and put into its own versionized folder.

Yeah I saw that. Folder C:\Users\YOURUSERNAME\AppData\Roaming\sleek is deleted by me before every new try below.

If you start sleek.exe from Power Shell, does it give you a new/different error or anything?

This is sleek using file 1 working.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev7
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\1 working.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting

This is sleek using file 2 not working.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev7
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\2 not working.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
(node:12152) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading '2')
    at t.Item.parse (B:\sleektest\resources\app.asar\dist\main\main.js:14:228532)
    at new t.Item (B:\sleektest\resources\app.asar\dist\main\main.js:14:228338)
    at B:\sleektest\resources\app.asar\dist\main\main.js:14:456602
    at Array.map (<anonymous>)
    at T (B:\sleektest\resources\app.asar\dist\main\main.js:14:456581)
    at R (B:\sleektest\resources\app.asar\dist\main\main.js:14:458683)
    at async IpcMainImpl.ee (B:\sleektest\resources\app.asar\dist\main\main.js:14:466576)
(Use `sleek --trace-warnings ...` to show where the warning was created)
(node:12152) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

And one more question: Is there a way you could create a todo file, which crashes sleek on your side and send it to me? One with just bogus data. You can send it here<EMAIL_ADDRESS>
Both files [41d7286db70985e7ac05a1a5afa67e3a] are available at https://filetransfer.io/data-package/kLgvrjYA

The difference between 1 working.md and 2 not working.md: "1" only has one line (one ToDo)... 🙄

I hope that helps? Thanks again for your effort!

@dnngll if your issue is related to the filewatcher, which is being used in sleek, we should give this latest developer preview a chance: https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev7
I tweaked the configuration a little bit. I'm still curious about a "broken" text file from you, in order to fully reproduce this.

Funny you just posted this... But I did use dev7 above, phew 😇

Hehe :)
The good news is, I can reproduce the issue with the non working file in my working environment. Let's see if I can find the root cause here.

Hehe :)
The good news is, I can reproduce the issue with the non working file in my working environment. Let's see if I can find the root cause here.

PERFECT!!!
Looking at how you've handled issues in the past, I think it is safe to say that sleek will becomes my daily driver very soon 😊🥳
You have no idea how long I've been hoping for this to happen! Thank you so much!

PERFECT!!!
Looking at how you've handled issues in the past, I think it is safe to say that sleek will become my daily driver very soon 😊🥳
You have no idea how long I've been hoping for this to happen! Thank you so much!

Hehe :)
The good news is, I can reproduce the issue with the non working file in my working environment. Let's see if I can find the root cause here.

PERFECT!!!
Looking at how you've handled issues in the past, I think it is safe to say that sleek will become my daily driver very soon 😊🥳
You have no idea how long I've been hoping for this to happen! Thank you so much!

Thank you for looking into it! That's so weird, I can't be the only one having this problem...

I cannot find anything in that line, which looks unusual.

That's what I mean... Nothing special to the file :(

That's something I will pass on to the jstodotxt project.

Thanks. So that's nothing you can fix on our side, right?

As for now I added an error handling, which, will catch errors, when jstodotxt cannot parse a line and will skip that line. This doesn't solve our problem, as it would simply cut out your broken todo line. But at least render the rest.

I'll try my "real" todo-file in dev8 and will let you know how many lines are skipped.

I don't know if you already mentioned it, but can you tell me what other apps (Todo apps, editors, or anything which manipulates the files) you use to work on your todo files?

On Windows I am using todotxt.net (https://github.com/jdckr/todotxt.net), Sublime Text portable, a self-made batch to add todos, a self-made ahk-script to add todos, Obsidian and Windows notepad.exe.
On Android I am using Simpletask and Obsidian

I think if I find out what exactly it is, that is making jsTodoTxt throw the error, I can intercept it. If it's some hidden character, I can cut it out. I will investigate it.

Okay, thanks!

I havn't found a solution yet, but I think I can say with some certainty, that the problem lies in the last character of the 1st line in 2 not working.md

It is something read by JavaScript as a whitespace character. If I simply cut the last character out of the string, this does not cut out the z, which should be the last character. And if I then send it to the jstodotxt module, the todo is being parsed.
I tried to find out what this character is, but were not successful yet. It is not a new line \n neither is it an empty space.
Could you check, if your custom script does add some unique character at the end of the line? Maybe it tries to enforce a new line or something like that.

@dnngll although it won't really help you, you can try out the latest developer preview: https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev8
If a line in the file contains something, which jstodotxt cannot 'digest', sleek will skip it.
But I assume, that all the lines in your file will contain this mysterious character and it might cut out all your todos :/

Hey @ransome1 ,
thank you for your reply. I just got back and tried something new, which will address your point in https://github.com/ransome1/sleek/issues/68#issuecomment-1703192637 .

I created a new file through the Windows context menu "New | Text Document" and named it 3 working notepad.md. I used Windows Notepad and typed the content by hand. This is the content of file 3 working notepad.md:
2121-09-13 +dede +frfr gtgt @hzhz

Or as a screenshot, cursor on end:

Then I duplicated that file, renamed it into 4 not working notepad.md, opened it with Notepad again and added a new line at the end (just by pressing enter). This is the content of file 4 not working notepad.md:
2121-09-13 +dede +frfr gtgt @hzhz

Or again as a screenshot, cursor on end:

These are the results of Powershell on 3 working notepad.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev7
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\3 working notepad.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting

These are the results of Powershell on 4 not working notepad.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev7
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\4 not working notepad.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
(node:14588) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading '2')
    at t.Item.parse (B:\sleektest\resources\app.asar\dist\main\main.js:14:228532)
    at new t.Item (B:\sleektest\resources\app.asar\dist\main\main.js:14:228338)
    at B:\sleektest\resources\app.asar\dist\main\main.js:14:456602
    at Array.map (<anonymous>)
    at T (B:\sleektest\resources\app.asar\dist\main\main.js:14:456581)
    at R (B:\sleektest\resources\app.asar\dist\main\main.js:14:458683)
    at async IpcMainImpl.ee (B:\sleektest\resources\app.asar\dist\main\main.js:14:466576)
(Use `sleek --trace-warnings ...` to show where the warning was created)
(node:14588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

That's so weird, isn't it? You could simply create these files yourself, however I uploaded then just in case you want to check them out: https://filetransfer.io/data-package/EjleeshY

I used dev7 (sleek-2.0.0-dev7-win.zip [ace17a1a2cf7bd4daa08f12dc24205b9]), because I didn't want the errors to be cut out.
Also, I always deleted the userfolder before.

I hope you can make any sense of this? I will try the same with the current dev now - just in case! Will get back to you asap...

That took forever, since I'm on a very slow connection currently :(

Using dev9 (sleek-2.0.0-dev9-win.zip [214ead1e2e776184a55da23d1812a5a9]), always deleting userfolder, using the files from above (https://github.com/ransome1/sleek/issues/68#issuecomment-1717859605):

These are the results of Powershell on 3 working notepad.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev9
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set isNavigationHidden to false
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\3 working notepad.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs

Plus, a screenshot:

These are the results of Powershell on 4 not working notepad.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev9
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set isNavigationHidden to false
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\4 not working notepad.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
TypeError: Cannot read properties of null (reading '2')
    at t.Item.parse (B:\sleektest\resources\app.asar\dist\main\main.js:14:228532)
    at new t.Item (B:\sleektest\resources\app.asar\dist\main\main.js:14:228338)
    at B:\sleektest\resources\app.asar\dist\main\main.js:14:457396
    at Array.map (<anonymous>)
    at D (B:\sleektest\resources\app.asar\dist\main\main.js:14:457371)
    at j (B:\sleektest\resources\app.asar\dist\main\main.js:14:459144)
    at async IpcMainImpl.ne (B:\sleektest\resources\app.asar\dist\main\main.js:14:468003)
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationHidden
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState

Plus, a screenshot again:

Does that help?

Uh and just for shits and giggles I opened my real todo.txt in dev9 (sleek-2.0.0-dev9-win.zip [214ead1e2e776184a55da23d1812a5a9]).
Here's the file in Sublime (obfuscated):

And here's the file in Sleek:

Like you said, everything is filtered out... 😢

TLDR: IT'S WORKING!!! 🎉

I see you just released dev10 - wow! Here are the results using dev10 (sleek-2.0.0-dev10-win.zip [2c5a9b8e21d8472e5021e36cd0df1950]), always deleting userfolder, using the files from above (https://github.com/ransome1/sleek/issues/68#issuecomment-1717859605):

These are the results of Powershell on 3 working notepad.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev10
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\3 working notepad.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs

These are the results of Powershell on 4 not working notepad.md:
PS B:\sleektest> .\sleek.exe
PS B:\sleektest>
config.ts: sleek userdata is located at: C:\Users\d21\AppData\Roaming\sleek\userData2.0.0-dev10
main.ts: Main window has been created successfully
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Set accordionOpenState to true,true,true,false,false,false,false,false,false
ipcEvents.ts: Set drawerWidth to 500
ipcEvents.ts: Set sorting to [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
ipcEvents.ts: Set isDrawerOpen to false
ipcEvents.ts: Set isSearchOpen to false
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
File.ts: File watchers created
File.ts: File added, restarting file watchers
ipcEvents.ts: Received config value for files
FileWatcher.ts: New file added: B:\sleektest\4 not working notepad.md
FileWatcher.ts: Initial scan complete. Ready for changes
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs
ipcEvents.ts: Received config value for appendCreationDate
ipcEvents.ts: Received config value for convertRelativeToAbsoluteDates
ipcEvents.ts: Received config value for notificationsAllowed
ipcEvents.ts: Received config value for drawerWidth
ipcEvents.ts: Received config value for accordionOpenState
ipcEvents.ts: Received config value for files
ipcEvents.ts: Received config value for isDrawerOpen
ipcEvents.ts: Received config value for isSearchOpen
ipcEvents.ts: Received config value for sorting
ipcEvents.ts: Received config value for isNavigationOpen
ipcEvents.ts: Received config value for colorTheme
ipcEvents.ts: Received config value for shouldUseDarkColors
ipcEvents.ts: Received config value for showFileTabs

I'm really curious - what was the issue?
Again, thank you so much. I am really looking forward to using Sleek now 😁

I see! I find it really weird that I am the only one who was complaining about this. Seems no one else is on Windows... Or trying out the dev-versions...
I am just playing around with the (broken) dev10 (sleek-2.0.0-dev10-win.zip [2c5a9b8e21d8472e5021e36cd0df1950]) that I downloaded before, but will update to the newer version later as soon as you release it.

You're doing something with the settings, right? Hardly anything there until dev7 (I didn't test dev8)

(dev7)
and not much more there in dev9 or the defective dev10...

(dev9)

Totally disregard my last message. After playing around with that version for a bit, I realized that hardly anything is working yet.
I should have considered your info about the nightlies: "This is an early developer preview with some basic functionality implemented, although many features are still missing."
Looking forward to all the new features making it into the stable 👐 and will of course keep on testing future dev-versions.
Thanks

I hope I didn't offend you by saying this, sorry if I did, didn't mean to. Here's what did not work:

After ticking off a ToDo, all other ToDos are not shown anymore (yet are still in the file). Maybe that has to do with the fact, that the ToDo was saved using CRLF before. After Sleek touches the file, it is saved using LF. When manually saving the file using CRLF again in another editor, all ToDos are displayed again in Sleek
Only 4 options available in Settings
Dark Theme will only apply to the title bar
Applying Dark Theme is not saved, it will only work the first time. After restarting Sleek it will not show and cannot be set again. To set again one has to cheat: Sleek-Folder and User-Folder have to be deleted
Can't filter by "has no" Project- or Context (or I can't find it)

So it was not really usable for me right now, which is why I thought that not everything has been implemented in these builds...
Hope I could help!

So it was not really usable for me right now, which is why I thought that not everything has been implemented in these builds...

It is not suppose to be usable for production use: https://github.com/ransome1/sleek/discussions/501
I updated the release description texts to further clear up, what is happening in this project right now.
Also let me close this thread for now, since we more or less hijacked it a little bit for something not related to the initial requirement. The line break issue should be resolved in the upcoming developer preview 10 and if it is not we should rather open a separate bug task.

It is not suppose to be usable for production use: #501
I updated the release description texts to further clear up, what is happening in this project right now.

Yeah, my bad. I was so excited that you fixed https://github.com/ransome1/sleek/issues/68 and wanted to use Sleek as my daily driver right away. So in my fantasy it was more of a "test new features in an upcoming version", than a complete rewrite. I know better now 😊
Really looking forward to "Once this foundational work is complete, there is room for new features. Hopefully developed not just by me. I sincerely hope that this endeavor will attract a broader range of contributors who will support me in achieving these goals." from your https://github.com/ransome1/sleek/discussions/501

Also let me close this thread for now, since we more or less hijacked it a little bit for something not related to the initial requirement.

Definitely, thanks

The line break issue should be resolved in the upcoming developer preview 10 and if it is not we should rather open a separate bug task.

Yes, it was already resolved in the defective dev10 that I was able to download before you deleted it. I think however, the CRLF / LF problem after Sleek touches the file (first point from my https://github.com/ransome1/sleek/issues/68#issuecomment-1718090704 ) might be related, but I'm sure you've got it covered. Which brings me to my last point:
I suppose I will not create new issues about what I mentioned in https://github.com/ransome1/sleek/issues/68#issuecomment-1718090704 (using the defective dev10), until the new dev10 comes out? To save you some time and to not hijack this thread any more, please only reply, if you want me to create new issues right away. If I don't hear anything from you here, I would wait for the final dev10.
Thanks again @ransome1 !

I suppose I will not create new issues about what I mentioned in #68 (comment) (using the defective dev10), until the new dev10 comes out? To save you some time and to not hijack this thread any more, please only reply, if you want me to create new issues right away. If I don't hear anything from you here, I would wait for the final dev10.

I hadn't seen this particular issue on my side, but I would propose once the Dev 10 uploaded, you give it another try on your system. And if anything weird happens, I would appreciate a separate bug report.

@dnngll I tested the latest implementation on a Windows machine and couldn't reproduce the error any more. So please feel free to test it out yourself and if it still throws the error or shows some other unwanted behavior, let's open a dedicated bug report for it.
https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev10

Hey @ransome1
last week I did test all 4 files from above plus my 3 main todo-files, using sleek-2.0.0-dev13-win.zip [87e66bcb3f29fdd7c7bd776d30221fa6]. Every file worked flawlessly, and I did a lot of testing (check todo, new todo, delete todo, archive ticked todos, change todo-file from somewhere else) with all 7 files. Thank you so much!
I am on dev-13 still, but will test dev-14 (sleek-2.0.0-dev14-win.zip [146e01e975161180a4064256c459c672], which somehow can't be found on https://github.com/ransome1/sleek/releases) from now on.

@dnngll the win.zip should be there, here is the direct link: https://github.com/ransome1/sleek/releases/download/v2.0.0-dev14/sleek-2.0.0-dev14-win.zip

Yeah I know, thanks. I've been using it since last week. I got the link through the Email GitHub sends automatically when subscribed.
I just wanted to point out that dev-14 (still) can't be found on the official release-page https://github.com/ransome1/sleek/releases for some reason.
Very much looking forward for the final 🙌

Yeah I know, thanks. I've been using it since last week. I got the link through the email GitHub sends automatically when subscribed.
I just wanted to point out that dev-14 (still) can't be found on the official release-page https://github.com/ransome1/sleek/releases for some reason.
Very much looking forward for the final 🙌


Add workaround for issue 1238

Issue 1238: https://issues.dlang.org/show_bug.cgi?id=1238
This request fixes Issue 14405 which was introduced by #1414

Looks good to me.
It's sad that it's required because of the module naming visibility problem we have but at least this works around it.

LGTM

Auto-merge toggled on

Thanks!

This works, but wow it is ugly. Are we ever going to get the fix for https://issues.dlang.org/show_bug.cgi?id=1238 ? :-(


PhantomJS identifies Promises as [object Object] instead of [object Promise]

I'm running PhantomJS version 2.1.1 with Mocha and Chai for unit testing.

What steps will reproduce the problem?

var promise = new Promise(function() {
return true;
});

var test = Object.prototype.toString.call(promise)

console.log(test) // returns [object Object]

In desktop Safari 10 and Chrome 54 this returns [object Promise]

In node this returns [object Promise].

Which operating system are you using? I'm on macOS Sierra.

Did you use binary PhantomJS or did you compile it from source? NPM install.

Please provide any additional information below.
I use this technique to test for native promises. Since I'm using PhantomJS with Mocha and Chai for unit tests, all test that rely on testing for promises fail because they appear to be generic objects.

Fixed in 2.5 beta


Add matplotlib animated GIF demo to aligned UMAP doc

Related to PR #687.

Animation feels like a natural way to view aligned UMAP results, so I thought it made sense to include a demo for creating a GIF in the aligned UMAP basic usage docs. Please let me know if this is not the appropriate place to include such a demo.

I added a GIF demo to the very end of the doc, since I think it works better both organizationally and visually. Using the interpolation from the 3D plot allows for very smooth motion in the animation. (I also updated both the related prior plots so that they all have a consistent random state)

Coverage remained the same at 87.85% when pulling 69db51a4d2bd9b8c2a347b11f5a8658a3e32aa8b on chrismbryant:doc/aligned_gif_demo_v2 into ceaa8f4d6853494a7a086bb4b9cb40ff8f84ec56 on lmcinnes:master.

Thanks! I had been using animations myself, but hadn't found a good clean way to insert them in the docs. This looks like a very effective approach.


fix: linting errors

Summary

fixed linting errors in all files
changed a couple of properties in .eslintsrc.json

@MaestroDagan Please read the Contribution Guidelines first before raising a pull request.

@thieleju Sorry, that i broke those, but what did i do wrong? Is this 'random', because there's no issue for it? If that's the case i'd like to say that i can only make issues for new commands and all those linting errors are pretty annoying, but now i know that this is considered as 'random'. I'll stop doing it!

No worries, its fine :)


bug(overflow): good_lp default solver creates cycles and stack overflow

Bug Report
Cairo Version:
Latest
Bug (Overflow): The Default Solver in good_lp Creates Cycles and Stack Overflow
Problem
Currently, the good_lp dependency imports its default solver, minilp, as follows:
good_lp = { version = "1.7.0", features = ["minilp"], default-features = false }

However, minilp has been archived since September 22, 2022, with a warning that states:

Warning: this is an early-stage project. Although the library is already quite powerful and fast, it may cycle, lose precision, or panic on some harder problems. Please report bugs and contribute code!

In my current project, Deoxys, I'm involved in class retrieval and conversion inside a Tokio worker, which leads to the following error:
Thread ‘tokio-runtime-worker’ has overflowed its stack

⚠ This means that any iterative program manipulating sierra definitions via the Cairo lib will crash after overflowing its stack.
Solution
The solution is quite straightforward and does not introduce breaking changes. The good_lp library can be imported with different solvers as features:

Solver Feature Name
Integer Variables
No C Compiler*
No Additional Libs**
Fast

[coin_cbc][cbc]
✅
✅
❌
✅

[highs][highs]
✅
❌
✅+
✅

[lpsolve][lpsolve]
✅
❌
✅
❌

[minilp][minilp]
❌
✅
✅
❌

[lp-solvers][lps]
✅
✅
✅
❌

[scip][scip]
✅
✅
❌
✅

[cplex-rs][cplex]
✅
❌
✅++
✅

[clarabel][clarabel]
❌
✅
✅
✅

Therefore, the solution is to import a different solver (which may require upgrading the good_lp version to 1.8.1). I tested the following configuration using Clarabel, as it is maintained, powerful, fulfills our needs, and works perfectly on my side:
good_lp = { version = "1.8.1", features = ["clarabel"], default-features = false }

Source: https://github.com/rust-or/good_lp

This definitely is not compatible - the suggested solution consistently fails on tests.
do note that for new sierra versions - the solver isn't actually being ran at all.  it is only being ran for backwards compatility reason (so it is still required for old classes)

Yes we need backward compatibility to sync our full node. We just runned into another overflow, I think that there is simply recursivity in the CasmContractClass::fom_contract_class implementation that cant be avoided. Our apologies we'll try to identify deeper the problem and solutions and get back to you.


Fullscreen fix + drag space tweak

Two pretty simple changes that should be self explanatory.

Drag space above tabs reduced to 8px, to match chrome, edge, etc.
(Revert to 16px by setting userChrome.DragSpaceAboveTabsWindowedMode-Increased to true)
-moz-win-glass applied only to non-fullscreen windows. Not only the main window now, so PIP windows get rounded corners and some dialogs also receive mica/acrylic

Drag space of 16px is needed for Windows. If set to 8px, the window will be almost impossible to capture with the mouse. You can check yourself. Although for Linux and MacOS this will not be a problem. However, such an option can be added, for variety.
As for -moz-win-glass, this will lead to the use of transparency where it is not desired. On Windows 7 everything is transparent and the fonts are hard to read. Same for Windows 8. I can't make such a change.


Support net_mgmt events from userspace

Instead of modifiying net_mgmt API directly for userspace support, create a AF_NET_MGMT socket address family and use the socket API to receive network management events in userspace application. This version only implements the event listening support, but in the future we can add a way to set values in the system via network management socket implementation.

At least a commit indicates that this is a bug-fix, @jukkar , so I wonder if this needs to be backported to 1.14.

At least a commit indicates that this is a bug-fix, @jukkar , so I wonder if this needs to be backported to 1.14.

No, this is not a bug fix but a new feature and for 2.0 only.

I will reorganize the commits and split the PR after @tbursztyka has reviewed the code. Some of the fixes we might be able to backport to 1.14.

resolved merge conflict
added userspace support to generic getsockopt() and setsockopt() calls
added support for getsockopt() and setsockopt() calls in AF_NET_MGMT
implemented setting and getting of Ethernet Qav parameters
added more unit tests

Rebased against latest master.

I removed the controversial code from net_mgmt in order to proceed. We can test things without those but I think in the future we need to figure out some changes in order to use the net-mgmt sync interface efficiently.

@pfalcon I missed the reason why you gave -1 to this one, can you re-check?

My comment was at https://github.com/zephyrproject-rtos/zephyr/pull/16743#pullrequestreview-248953430, hopefully it's fixed. Removing my -1, as I'm going on vacation.


GroupBy in OrderDetailsReport

In OrderDetailsReport.cs
var od = OrderDetailRow.Fields;
data.Details = connection.List(q => q
.SelectTableFields()
.Select(od.ProductName)
.Select(od.LineTotal)
.Where(od.OrderID == this.OrderID));
I needed to remove validation from OrderDetailsEditor.ts for the same product, now I wanted to group the same products and show the total and count,
I tried
var od = OrderDetailRow.Fields;
data.Details = connection.List(q => q
.SelectTableFields()
.Select(od.ProductName)
.Select(Sql.Count("ProductName"))
.Select(od.LineTotal)
.Where(od.OrderID == this.OrderID));
.GroupBy(od.ProductName)
the list obtained isn't grouped by ProductName

I don't think that's possible, there is a GroupBy, so it will be grouped, results may not be what you expect, turn debugging and try it directly in SQL.

Yes that works fine in SQL,
Got another solution I just grouped them in view
Thank you for reply 👍


Add basic docker-compose support for development

This change adds very basic Dockerfile and docker-compose.yml files
for running cartography against a local neo4j.
Usage:
docker build -t lyft/cartography
docker-compose run cartography ...

I've purposely not included an entrypoint, so that custom sync
scripts can be called through run.
Configuration is possible via the .compose directory, which is
git ignored. Environment for cartography is in
.compose/cartography/cartography.env. neo4j config, logs, etc is
located at .compose/neo4j/...
Note that on initial start of the compose stack, it's necessary to
change the neo4j user's password through the neo4j UI.

I wasn't fully sure where in the docs we should stick this, so I didn't update them yet. Let me know!

Thanks for working on this!

I wasn't fully sure where in the docs we should stick this, so I didn't update them yet. Let me know!

Let's make a new doc in docs/setup/docker.md to describe how to use this, and then we can link to it in README.md by making a ##-heading called "Docker" placed right after the ## Install and configure heading.

Ok. Done!

Hey @kmcquade, hope you've been well :), been a while since we talked about using docker to test this tool. What do you think about this test setup?

Thanks for working on this!
@marco-lancini, what do you think? The container basically only makes Neo4j available and the docs make it clear that this is only for testing.

@achantavy I'm personally not a fan of storing credentials/tokens within the folder of a repo itself.
What I would probably do is mount the .aws folder as a volume and then reference the profile I need as environment variable

Changed docs to use passed in environment, changed the user it runs as, and updated the docs.

This will play fantastic with localstack where we can check how the system works with a fake local aws!


Is there any way to disable  "hide" button fuinctionality

How would the Hover menu work if the user can't exit the menu?

by clicking on hover button.. or whenever dev wants. This issue is interlinked to #30


#82 - Meaningful jfr dump file names

Should fix https://github.com/moditect/jfrunit/issues/82 and provide better file names in Spock.

Applied; thx, @phejl!


Proposal for changing sub and adding more claims

What feature do you want to see added?
Hi and thanks for maintaining this plugin. It's been super useful!
I'd like to propose to slightly change the sub to

do not include the jenkins address (is this useful for other use cases?)
Have it in a format similar to gh or gitlab (examples below)

GitLab (ref)
project_path:mygroup/myproject:ref_type:branch:ref:main

GH (ref)
repo:octo-org/octo-repo:environment:prod

This way we might use one openid token to serve multiple multiple requests for multiple branches (matching against different SAs)
Following their model it might also be convenient to add more claims, although I don't see it urgent as modifying the sub.
What do you think? Should I send a patch for it? Happy to discuss more!
Upstream changes
No response

Hi All!
I'd start with repo_name:branch
I put together some info to get the repo name and the branch name in Jenkins, depending on the plugin used. Nothing final or fully experimented yet. Unfortunately, Jenkins doesn't make this really easy, as it seems both params change, depending on the Jenkins version or plugin used.
For repo name:

the environment variable GIT_URL (with proper replacement, still need to experiment with it more)
for the SCM plugin: return scm.getUserRemoteConfigs()[0].getUrl().tokenize('/').last().split("\\.")[0]

For the branch name:

$BRANCH_NAME (both the env var or the newer BRANCH_NAME property)
${params.GIT_BRANCH} - that a user would define manually in single branch pipelines, if needed
${GIT_BRANCH} coming from the git plugin

I'll start experimenting a bit these and I'll let you know how it goes.
Happy to receive suggestions or discuss further.

I have a mild preference for keeping sub as a URL for the job (something which is unconditionally available) and adding claims for specific pieces of information (e.g. https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMRevisionAction.html for branch info from multibranch Pipeline builds) where applicable & available.

This way we might use one openid token to serve multiple multiple requests for multiple branches (matching against different SAs)

Can you elaborate? How do you plan to configure services to grant or deny permissions based on the claims in the id token? I have come across very different configuration styles and levels of flexibility in GCP and AWS.

Hi @jglick. Thanks for getting back!
I guess having the branch name in a claim only would also absolutely work.
I think having the sub formed as suggested would

make it just easier imho to map to the provider subject (you could use directly sub instead of a concatenation of sub and claims)
probably help to create easier attribute conditions (again, for example we could simply put one conditions against the sub, instead of putting in end multiple conditions)

Also, as per here (for what concerns GCP) the sub should be unique and immutable. It's what forms the principalSet and what is used in logs. If we'll need to manage the infra from IaC (i.e. Terraform), it would also help to don't have urls with columns or double slashes (i.e. //) in it.

the sub should be unique and immutable

Which is accomplished by using the job URL I think? I suppose a URI relative to the Jenkins root (e.g., jobs/my%20first%20project/) would also work, since the Jenkins identity is implied by the issuer.

one conditions against the sub, instead of putting in end multiple conditions

Perhaps. It comes down to seeing some examples of what sorts of conditions you are actually working with, in which audience system. For example https://cloud.google.com/iam/docs/using-workload-identity-federation#gcloud the attribute.*/* variant looks reasonable but I have not personally tried it. Conversely, if multiple pieces of information are packed into the subject with (say) :-separated fields, do you expect to do an exact string match on the result? Some sort of regexp? Different audiences would have different abilities to match claims, and the OIDC spec does not cover this CI use case at all so everyone is making something up.

@jglick thanks for getting back. While the field is a little bit different from other major providers I don't have strong feelings to change necessarily the sub.
We can definitely start adding claims!
Working on the PR and getting back asap :)

Hello again @jglick .
The patch should be "ready". Anyway I have unit tests failing.
Weird thing is that unit tests are failing also in the plain master (please see file attached).
Clearly, I must be missing something. Any thought?
Thanks,
-Luca
unit-tests-failure.txt

I do not recognize those failures. Make sure you are running a current Maven release, from the command line (do not trust some IDE), and a current JDK (8 or newer; 11 recommended), and
mvn clean verify

(By the way I will be unavailable for a couple weeks.)

Hey, thanks for replying. No worries, I'll also be OOO from the end of next week to Sept 5th.
So, interesting enough mvn clean verify "works". Before I was executing either mvn test or mvn clean test and it wasn't.
When I say it works, there are of course some expected failures, given I still haven't modified the tests. Now I can advance on this and submit the PR.
Thanks again and happy holidays!


DOC: spatial.distance: add missing optional param markers

Reference issue
n/a
What does this implement/fix?
adds missing markers for optional parameters to scipy.spatial.distance.{pdist, directed_hausdorff}
Additional information

Thanks Lucas 😃


boot2_generic_06b.S

Hi,
I have a boot2 driver that supports the Winbond W25Q128JW, and potentially other flash chips that do not support Continuous Read mode but do support Quad Fast Read (6B) commands.  This gives a major performance boost over the generic read command (3H) implemented in boot2_generic_03h, which is the only driver in the distro that doesn't require Continuous Read.
Can I submit a PR?
Thanks,
-mykle-

sure

closing awaiting PR


Updating pipeline

This PR is aimed at addressing two issues, I found it tricky to sensibly separate them.
Pipeline update to work with latest version of EpiAware

Fixes where prepended missing data were causing errors.
Update of observation model so that the latest helper version of day of week effect on ascertainment was involved.

This closes #287 .
Modify setting observation model for pipeline
Given we are changing the observation model to reflect changes in EpiAware it was easier to refactor so the observation model wasn't hardcoded but rather a default constructor option (as per other aspects of pipeline).
This closes #288 .
Minor changes

Fixing a fix in #283; this highlights need for resolution to #206, #209, #240
Renaming functions e.g. when only latent models are used I've renamed to latentmodel in constructors.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.85%. Comparing base (e506f7d) to head (0ff4dc1).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #290   +/-   ##
=======================================
  Coverage   92.85%   92.85%
=======================================
  Files          47       47
  Lines         490      490
=======================================
  Hits          455      455
  Misses         35       35

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


make security context optional for openshift

@kahootali Chart: grafana Dry Run successful

@kahootali Chart: grafana-storage Dry Run successful


Prevent infinite loops in editor help search

See https://github.com/godotengine/godot/issues/63129#issuecomment-1218310026
#54406 introduced some method returns that, according to this comment, can cause infinite loops. I'm not 100% sure how it works, but the methods are supposed to increment some iterator, which did not happen in the early returns. So I think my changes probably make sense, but not sure if they fix the issue, as I can't reproduce it reliably to test.

Thanks!

I think I've got a reproduction case, and that these changes revert to the crashes that occurred pre-#54406. See https://github.com/godotengine/godot/issues/63129#issuecomment-1248759466.


Bump WdCuration version on PyPI

Already bumped on PyPI, this is just to sync the repo.

fix: Add double quotes to bumpversion cfg
Bump version: 0.1.3 → 0.2.0

@lubianat this should be merged before #17

By the way, my workflow for bumping and releasing this to PyPI is just two simple commands:
bump2version minor

make release

You might need to install a few dependencies (wheels, twine), but it should work for you too.


policy: Fix Key stringer port range output

Do not add the range start port to the end port when formatting it.

/test


Flexible authN between API-X and repository

CLAW is now using JWT for authentication, and a valve for Tomcat8 named Syn that accepts JWT. In order to use API-X together with CLAW as proposed here it is necessary to account for authN in API-X's interactions with the repository.
Am I right in supposing that the appropriate points at which to deal with such authN would be here and here?

Hi @ajs6f ,
I don't think either of those need updating.  As mentioned in my recent comment to the CLAW issue, API-X would need to authenticate itself when maintaining its own internal state in registries it persists in Fedora.  That's an interaction solely between API-X and Fedora, and API-X needs its own credentials if it wants to write to Fedora.
As far as the other referenced places in code, those are part of the mechanism of where API-X reverse-proxies requests from the client to Fedora.   API-X is just a passive party here, and will dutifully pass along any authentication headers that happen to be in the http requests from the client, but otherwise doesn't care and isn't involved.  So in theory, the client will provide whatever credentials it has/needs, and those will be proxied along unmodified to Fedora.  Fedora then can allow or disallow the request in whatever way it sees fit.

Okay, that's fine by me! :) I had assumed that API-X routed all interaction with the repository via the same channels for simplicity/DRYness, but all I care about is indeed the actions initiated by API-X itself.


added lighttpd example

Added lighttpd as an example in freebsd

Not that interesting example, since there is just a single module and no interfaces to
specialize across. Also it needs to be updated to the new manifesto.


Integrate with generated protobuf struct in param body

When I use  struct data type within param for request or data for response, everything is fine. But when I change the handl made struct to proto struct(generated by proto compiler) and then swag init, it just produce a plain object like this:
    "definitions": {
        "handler.SwaggerCreateProjectRequest": {
            "type": "object"
        }
    }

all of the proto struct details lost.
I don't know it's posilble to integrate proto struct with swaggo or I do something wrong with it.

If you look at the code swag init scan and parse definitions from all go files except from "vendor" and "internal" folder staring (from current folder, the folder you are invoking swag command) and use them to generate the OpenApi "definitions".
Depending where your handler is , you may need to use "--parseDependency" flag if you need to load them from external package like "github.com/youruser/yourproject" or to invoke swag command from upper directory .
See swag init --help for more details.

I try swag init with --parseDependency, but it seems not the case that I described in this issue.
I just want to use protobuf generated go file with swag, not external package.

@navono since you have no clue what is happening can you be nice to share with us the struct definition of handler.SwaggerCreateProjectRequest and hopefully we will figure out for you.
As more details you provide will increase the chance to get/find the right answer.

@ubogdan Thanks for response.
I create a demo from scratch, it works. Maybe I missed something when I first use swaggo. here is example go-pb-swagger.


The Ubuntu 20.04 Actions runner image will begin deprecation on 2025-02-01 and will be fully unsupported by 2025-04-01

Breaking changes
We will soon start the deprecation process for Ubuntu 20.04. While the image is being deprecated, you may experience longer queue times during peak usage hours. Deprecation will begin on 2025-02-01 and the image will be fully unsupported by 2025-04-01.
To raise awareness of the upcoming removal, we will temporarily fail jobs using Ubuntu 20.04. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:
GitHub Actions\Azure DevOps::

To be updated in place here, before 2025-02-01 (brownouts will not start immediately)

Target date
2025-04-01
The motivation for the changes
We maintain the latest two stable versions of any given OS version. Ubuntu 24.04 is going GA on 2025-02-01 so we start deprecating the oldest image at that time.
Possible impact
Workflows using the ubuntu-20.04 image label should be updated to ubuntu-latest, ubuntu-22.04, ubuntu-24.04 .
Platforms affected

[x] Azure DevOps
[x] GitHub Actions

Runner images affected

[x] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] macOS 15
[ ] macOS 15 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Mitigation ways
N/A

Could you please use ISO standard for dates. It is not clear what this is 2025-04-01

That is ISO 8601.
https://www.iso.org/iso-8601-date-and-time-format.html

This does not https://github.com/actions/runner-images/issues/10721
The confusion is real. It should not be a puzzle for a community to decipher the public announcements.

Then maybe post the ISO complaint under the right issue? The dates in this issue's description are correct.


"next_alarm" not updated

Describe the bug
After a alarm fire, value show past data, like "2 hours ago".
To Reproduce
Steps to reproduce the behavior:

Set a recurring alarm
Wait for it to fire
HA shows "1 hour ago"

Expected behavior
After a alarm fire, I would epect "next_alarm" to show the next one.
I think this is down to the way refresh is done.
Screenshots
If applicable, add screenshots to help explain your problem.

System details

Home-assistant (version): 0.105.2
Hassio (Yes/No): No
alexa_media  (version from const.py or HA startup): 2.5.5
alexapy (version from pip show alexapy or HA startup):

Please provide logs (check wiki for info). We'll be looking for the following lines:
2020-02-20T09:10:39.014678506Z 2020-02-20 01:10:39 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/notifications returned 200:OK:application/json
2020-02-20T09:10:39.018985876Z 2020-02-20 01:10:39 DEBUG (MainThread) [custom_components.alexa_media] a******e@g*******m: Found 10 devices, 10 bluetooth
2020-02-20T09:10:39.020897547Z 2020-02-20 01:10:39 DEBUG (MainThread) [custom_components.alexa_media] a******e@g*******m: Updated 14 notifications for 6 devices at 2020-02-20 01:10:39.019570-08:00

We'll also need to see the json output from https://alexa.amazon.com/api/notifications (fix the region) for the specific alarm that isn't updating.

Accessing the site gives me the following page:

Simone

First, you'll need to update the url to the domain you are using to connect to Amazon (e.g., alexa.amazon.it if you're in Italy). Second, if you are seeing that on the correct domain, you have connectivity issues to Amazon and of course the component won't work.

Please provide logs (check wiki for info). We'll be looking for the following lines:
2020-02-20T09:10:39.014678506Z 2020-02-20 01:10:39 DEBUG (MainThread) [alexapy.alexaapi] static GET: https://alexa.amazon.com/api/notifications returned 200:OK:application/json
2020-02-20T09:10:39.018985876Z 2020-02-20 01:10:39 DEBUG (MainThread) [custom_components.alexa_media] a******e@g*******m: Found 10 devices, 10 bluetooth
2020-02-20T09:10:39.020897547Z 2020-02-20 01:10:39 DEBUG (MainThread) [custom_components.alexa_media] a******e@g*******m: Updated 14 notifications for 6 devices at 2020-02-20 01:10:39.019570-08:00

I see the GET (with 200 OK) but not the "udpated notifications" in my debug log.
Simone

Can you please provide the json from the notifications page for the missing alarm?

Can you please provide the json from the notifications page for the missing alarm?

Sure, how should I capture it ?
Simone

@chemelli74

We'll also need to see the json output from https://alexa.amazon.com/api/notifications (fix the region) for the specific alarm that isn't updating.

taken at 09:36 (Rome)
{"notifications":[{"alarmTime":1584057600000,"automationId":null,"createdDate":1583795024866,"deferredAtTime":null,"deliveryType":null,"deviceName":null,"deviceSerialNumber":"xxxxxxxxxx","deviceType":"A1RABVCI4QCIKC","extensibleAttribute":null,"geoLocationTriggerData":null,"id":"A1RABVCI4QCIKC-xxxxxxxxx-8a3e70ce-c774-4909-98b6-082681e25c4b","lastOccurrenceTimeInMilli":0,"lastUpdatedDate":0,"musicAlarmId":null,"musicEntity":null,"notificationIndex":"8a3e70ce-c774-4909-98b6-082681e25c4b","originalDate":"2020-03-13","originalTime":"08:00:00.000","personProfile":null,"provider":null,"rRuleData":null,"recurrenceEligibility":false,"recurringPattern":"XXXX-WD","remainingTime":0,"reminderAppLabel":null,"reminderLabel":null,"reminderSubLabel":null,"skillInfo":null,"snoozedToTime":null,"sound":{"displayName":"Simple Alarm","folder":null,"id":"system_alerts_melodic_01","providerId":"ECHO","sampleUrl":"https://s3.amazonaws.com/deeappservice.prod.notificationtones/system_alerts_melodic_01.mp3"},"status":"ON","targetPersonProfiles":null,"timeZoneId":null,"timerLabel":null,"tmwNotificationProperties":null,"triggerTime":0,"type":"Alarm","version":"19"},{"alarmTime":1583798400000,"automationId":null,"createdDate":1581459338506,"deferredAtTime":null,"deliveryType":null,"deviceName":null,"deviceSerialNumber":"xxxxxxxxx","deviceType":"A1RABVCI4QCIKC","extensibleAttribute":null,"geoLocationTriggerData":null,"id":"A1RABVCI4QCIKC-xxxxxxx-9ef5918c-06ba-4a54-ba93-b7f1ab9d538f","lastOccurrenceTimeInMilli":0,"lastUpdatedDate":0,"musicAlarmId":null,"musicEntity":null,"notificationIndex":"9ef5918c-06ba-4a54-ba93-b7f1ab9d538f","originalDate":"2020-03-10","originalTime":"07:00:00.000","personProfile":null,"provider":null,"rRuleData":null,"recurrenceEligibility":false,"recurringPattern":"XXXX-WD","remainingTime":0,"reminderAppLabel":null,"reminderLabel":null,"reminderSubLabel":null,"skillInfo":null,"snoozedToTime":null,"sound":{"displayName":"Simple Alarm","folder":null,"id":"system_alerts_melodic_01","providerId":"ECHO","sampleUrl":"https://s3.amazonaws.com/deeappservice.prod.notificationtones/system_alerts_melodic_01.mp3"},"status":"OFF","targetPersonProfiles":null,"timeZoneId":null,"timerLabel":null,"tmwNotificationProperties":null,"triggerTime":0,"type":"Alarm","version":"81"},{"alarmTime":0,"automationId":null,"createdDate":1581717987717,"deferredAtTime":null,"deliveryType":null,"deviceName":null,"deviceSerialNumber":"xxxxxxx","deviceType":"A1RABVCI4QCIKC","extensibleAttribute":null,"geoLocationTriggerData":null,"id":"A1RABVCI4QCIKC-xxxxxx-ac4f1bee-cd90-33b4-bbbe-4c20c1d191f1","lastOccurrenceTimeInMilli":0,"lastUpdatedDate":0,"musicAlarmId":null,"musicEntity":null,"notificationIndex":"ac4f1bee-cd90-33b4-bbbe-4c20c1d191f1","originalDate":"2020-02-15","originalTime":"09:00:00.000","personProfile":null,"provider":null,"rRuleData":null,"recurrenceEligibility":false,"recurringPattern":null,"remainingTime":0,"reminderAppLabel":null,"reminderLabel":null,"reminderSubLabel":null,"skillInfo":null,"snoozedToTime":null,"sound":{"displayName":"Simple Alarm","folder":null,"id":"system_alerts_melodic_01","providerId":"ECHO","sampleUrl":"https://s3.amazonaws.com/deeappservice.prod.notificationtones/system_alerts_melodic_01.mp3"},"status":"OFF","targetPersonProfiles":null,"timeZoneId":null,"timerLabel":null,"tmwNotificationProperties":null,"triggerTime":0,"type":"Alarm","version":"3"},{"alarmTime":1583798400000,"automationId":null,"createdDate":1582700396167,"deferredAtTime":null,"deliveryType":null,"deviceName":null,"deviceSerialNumber":"xxxxxxxx","deviceType":"A1RABVCI4QCIKC","extensibleAttribute":null,"geoLocationTriggerData":null,"id":"A1RABVCI4QCIKC-xxxxxxx-f76fc3fc-768d-490d-afb0-a9ec92ce0e4f","lastOccurrenceTimeInMilli":0,"lastUpdatedDate":0,"musicAlarmId":null,"musicEntity":null,"notificationIndex":"f76fc3fc-768d-490d-afb0-a9ec92ce0e4f","originalDate":"2020-03-10","originalTime":"07:15:00.000","personProfile":null,"provider":null,"rRuleData":null,"recurrenceEligibility":false,"recurringPattern":"XXXX-WD","remainingTime":0,"reminderAppLabel":null,"reminderLabel":null,"reminderSubLabel":null,"skillInfo":null,"snoozedToTime":null,"sound":{"displayName":"Simple Alarm","folder":null,"id":"system_alerts_melodic_01","providerId":"ECHO","sampleUrl":"https://s3.amazonaws.com/deeappservice.prod.notificationtones/system_alerts_melodic_01.mp3"},"status":"OFF","targetPersonProfiles":null,"timeZoneId":null,"timerLabel":null,"tmwNotificationProperties":null,"triggerTime":0,"type":"Alarm","version":"81"}]}

Thanks, can you identify which ones wasn't showing up that should've been showing up?

Thanks, can you identify which ones wasn't showing up that should've been showing up?

Alarm was 8:00 am for working days
Simone

Can you please provide the attributes for the next_alarm sensor in HA for that item? Is sorted_active empty?

Never mind. Was able to reproduce it and have a fix.

As a further note, Amazon does update the alarm json at midnight so any timers will show the next day's timers.


C and C++ should not be lumped together

C and C++ are different languages, and people who are interested in working in one are rarely interested in working in the other. They should have separate entries in the list.

@tcbrindle Yes, you right. If you can do it right now, then i accept your PR without any questions, but if you're cannot, then  i separate them as soon as it possible.

@tcbrindle It's done!


Fix RList remove with count response when multiple items are removed

There appears to be a bug in how the response from RList.remove(object, count) is parsed when more than 1 object is removed. Previously BooleanReplayConvertor was used where it appears that BooleanAmountReplayConvertor should be used since the LREM response can be greater than 1 (if multiple items are removed).
Here's a fix & accompanying unit test - please let me know if I should make any changes or if you have any suggestions.
Example code that shows the problem:
redissonClient.getList("one_item").clear();
redissonClient.getList("two_items").clear();

redissonClient.getList("one_item").add("item");
redissonClient.getList("two_items").addAll(Arrays.asList("item", "item"));

assertEquals(1, redissonClient.getList("one_item").size());
assertEquals(2, redissonClient.getList("two_items").size());

assertFalse(redissonClient.getList("not_exist").remove("something"));
assertTrue(redissonClient.getList("one_item").remove("item"));
assertTrue(redissonClient.getList("two_items").remove("item", 2)); // This should be true, but returns false

Thanks for contribution!


Display boost for KEEP-only pool

Closes: #2328
Displays the reward boost for he KEEP ONLY pool:

Ready for another round of review @r-czajkowski


Dropout value fix to 0.0 and 0.5 in fully connected and softmax layers

Hi guys, I just discovered there is a bug in the public version of the code. Dropout rates in the fully connected and softmax layers are fix and set to 0.0 and 0.5, respectively. (LiviaNET.py file). As soon as I can I will correct this so that dropout rates can be read from the config file, and commit the new files with these modifications.

Just fix it!


Possible race condition in exec_helpers.Subprocess

Hey,
I found a possible issue, that happened to me in a very slow VM. So it could be that the race condition doesn't happen often if the system is fast:
import exec_helpers

def test():
    with exec_helpers.Subprocess() as executor:
        apiserver = executor.check_call('sleep 1; echo bla bla')
        if apiserver:
            return apiserver.stdout_str
    raise AbortException("Could not start subprocess")

while True:
    print "1: {}\n".format(test())

This will produce output like this:
1: bla bla

1:

1:

1: bla bla

So it can happen that sometimes the echo is not captured correctly. Running with strace it's visible that the echo did indeed execute, however it's not available in stdout_str.

Nice, looks good to me!


upgrade deltalake for tableMerger

Description
upgrading deltalake version to add new features (tableMerger)
How Has This Been Tested?
tested locally
Checklist

[ ] The PR is tagged with proper labels (bug, enhancement, feature, documentation)
[ ] I have performed a self-review of my own code
[ ] I have added unit tests that prove my fix is effective or that my feature works
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] If new documentation has been added, relative paths have been added to the appropriate section of docs/mint.json

cc: @wangxiaoyou1993

@oonyoontong can you update the deltalake version in this file as well? https://github.com/mage-ai/mage-ai/blob/master/mage_integrations/requirements.txt
What tests did you do locally?

@oonyoontong can you update the deltalake version in this file as well? https://github.com/mage-ai/mage-ai/blob/master/mage_integrations/requirements.txt What tests did you do locally?

updated the test section with evidence


Don't expose EventEmitters in Component public API

Component consumers should not be able to call emit on any internal EventEmitter instance. As such,  components should do something like
@Output('change') private _change = new EventEmitter<void>();
change: Observable;

constructor() {
  this.change = this._change.asObservable();
}

@Output can't be private w/ AoT, so we can't really do anything about this.


feat(tutorial): complete step 2-boeblingen

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

@DanielaImmel You made it 👍 Looks great 🏆! I've recorded your completion of step 2.


corrects mismatched okta ids in seeds

Description
This pull request seeks to fix an authentication issue which prevents both users and engineers on this product to access any data in our database through our API's endpoints due to mismatched Okta IDs in our 001_profiles seed file. This mismatch stems from some work that was done with Okta within the past month that essentially caused each user to receive new ids - this patch assigns those new ids to each of our users except for Test007; this one will come in a later patch.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[ ] I have made corresponding changes to the documentation if necessary (optional)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

Thank you for the update!
That will help a lot. Very useful checklist.

Thank you for the update Paul, now that we have the right okta_id for our accounts, would we be able to access the backend with any of these accounts(002,003,...) or just the<EMAIL_ADDRESS>because before the patch in local environment, with 001 account I was able to get response back from the backend, but not with 002 or 003 account

You'd be able to access our API/database with any of our test users with this update, except for<EMAIL_ADDRESS>

Could you please explain why you chose to remove profiles with ids 9 and 10?

Sure thing! Those were removed because those test users don't exist in Okta anymore, so there's no need to keep them in our DB. 🙂