[JetBrains Toolbox Recent Projects] Plugin not working after updated JetBrains Toolbox to 2.0.x

Extension
https://www.raycast.com/gdsmith/jetbrains
Description
Error:
TypeError: Cannot read properties of undefined (reading 'find')

pd:util.ts:244:43

---
241:   if (channel.tool.toolName === undefined) {
242:     return undefined

Steps To Reproduce
I updated JB Toolbox to 2.0.2 and found this plugin not working. Upon checking https://github.com/raycast/extensions/pull/7799, I updated my raycast to the latest 1.57.1, and still not working.
Current Behaviour
No response
Expected Behaviour
No response

Sounds like it could be two separate issues here from the descriptions. Can you please check for extension updates to ensure you have the most recent version of the toolbox extension and then let me know which tools you have installed via toolbox.

Toolbox:

Version: JetBrains Toolbox <IP_ADDRESS>60, macOS 13.4.1
Tools Install location: /Users/xxx/Applications
Tools installed: IntelliJ (2023.2.1) and Fleet (1.22.113)

Rycast:

Version 1.57.1
Jetbrains Toolbox Recent Projects
Configured with Tool Install location /Users/xxx/Applications
Not sure how to check explicitly the version downloaded of the extension, but the package.json un ~/.config/raycast/extensions folder looks like updated to last version.

Please let me know if I can run any action locally to help here :)

Toolbox:

Version: JetBrains Toolbox <IP_ADDRESS>60, macOS 13.5.1
Tools Install Location: /Users/xxx/Applications
Tools Installed: Goland(2023.2), PhpStorm(2023.2), and more(but I mainly use these two)

Raycast:

Version: 1.57.2(updated today, formerly 1.57.1)
Jetbrains Toolbox Recent Projects(checked updated to the latest version via "Check For Extension Updates" command)
Configured the extension as below: (and if I don't configure it, it says something went wrong)

Shell scripts location: ~/Library/Application Support/JetBrains/Toolbox/scripts
Tools Install location: ~/Applications

Not sure if it is relavent, I deleted the old files after the Toolbox update via the clean something button in Toolbox. It is supposed to clean up configurations of some sort for the older versions of golands, phpstorms I guess.

What is the output of:
find "$HOME/Library/Application Support/JetBrains" -name recentProjects.xml

The output is
❯ find "$HOME/Library/Application Support/JetBrains" -name recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PyCharm2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/GoLand2023.1/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PhpStorm2023.1/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/IntelliJIdea2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/AppCode2023.1/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PyCharm2023.1/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/GoLand2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PhpStorm2023.2/options/recentProjects.xml

And the Search Recent Projects windows behave exactly as @Inmovilizame . It's been a week, any update on this?

Seems like it's not picking up that it needs to run the V2 code. What is the output of:
defaults read "$(mdfind kMDItemCFBundleIdentifier = "com.jetbrains.toolbox")/Contents/Info.plist" CFBundleShortVersionString

(just trying to get the version string of Toolbox according to the bundle ID com.jetbrains.toolbox)

Seems like it's not picking up that it needs to run the V2 code. What is the output of:
defaults read "$(mdfind kMDItemCFBundleIdentifier = "com.jetbrains.toolbox")/Contents/Info.plist" CFBundleShortVersionString

(just trying to get the version string of Toolbox according to the bundle ID com.jetbrains.toolbox)

❯ defaults read "$(mdfind kMDItemCFBundleIdentifier = "com.jetbrains.toolbox")/Contents/Info.plist" CFBundleShortVersionString
<IP_ADDRESS>60

The same for me
defaults read "$(mdfind kMDItemCFBundleIdentifier = "com.jetbrains.toolbox")/Contents/Info.plist" CFBundleShortVersionString
<IP_ADDRESS>60

It's strange, it's acting like it's not picking up the V2. Can you maybe try removing and re-installing the extension? Can you please confirm if you are getting any errors at all?

I tried removing and re-installing the extension, after the re-install, the error on my first comment show up.
TypeError: Cannot read properties of undefined (reading 'find')

pd:util.ts:244:43

---
241:   if (channel.tool.toolName === undefined) {
242:     return undefined

Only after manually set the Shell scripts location and Tools Install location would this error go away. And it won't show again no matter how I change these two paths.
And btw, I tried re-installing the JB Toolbox and even some of the IDEs, no help. Re-installing raycast won't help either.

Okay, so what do you have set for shell scripts and tools install location?

and is the location you have set something you set or is it the default for toolbox?

My case:

Reinstalled extension: "There was a problem finding the JetBrains shell scripts"
Change configuration to be in sync with my current JetBrains toolbox setup

Shell script location: ~/Applications
Shell scripts location: ~/bin

Same result, no results while trying to invoke the "Search recent projects".

Okay, after a bit of debugging I can see issues with missing config values I am looking for that disappeared for me when I re-installing Toolbox. I'm going to assume that can happen during upgrades.
What is the output of:
grep -r 'idea.config.path' ~/Library/Application\ Support/JetBrains/Toolbox/channels

If you don't get any output can you please try uninstalling and reinstalling your tools in JetBrains Toolbox (you shouldn't lose any config for the tool).

If that works I will add some detection for this issue with something like the following:

🤞

Tried grep -r 'idea.config.path' ~/Library/Application\ Support/JetBrains/Toolbox/channels, here is the result.
❯ grep -r 'idea.config.path' ~/Library/Application\ Support/JetBrains/Toolbox/channels
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/b26a623d-91a6-4930-aa76-19c19d784b80.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/b26a623d-91a6-4930-aa76-19c19d784b80.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/CLion2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/1f32e8ab-8521-475a-98fb-f00119d81440.json:                                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/1f32e8ab-8521-475a-98fb-f00119d81440.json:                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/IntelliJIdea2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/1f32e8ab-8521-475a-98fb-f00119d81440.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/1f32e8ab-8521-475a-98fb-f00119d81440.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/IntelliJIdea2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/2e1e5ecb-ab80-4fca-bebb-ddd956173482.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/2e1e5ecb-ab80-4fca-bebb-ddd956173482.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/AppCode2023.1",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/d7a62294-e7a1-4dad-a13e-efeede474dd3.json:                                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/d7a62294-e7a1-4dad-a13e-efeede474dd3.json:                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/PyCharm2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/d7a62294-e7a1-4dad-a13e-efeede474dd3.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/d7a62294-e7a1-4dad-a13e-efeede474dd3.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/PyCharm2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/b99d4ee2-3dd0-4ea0-98c8-d5b66fe2b3d6.json:                                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/b99d4ee2-3dd0-4ea0-98c8-d5b66fe2b3d6.json:                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/PhpStorm2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/b99d4ee2-3dd0-4ea0-98c8-d5b66fe2b3d6.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/b99d4ee2-3dd0-4ea0-98c8-d5b66fe2b3d6.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/PhpStorm2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/f84d2a37-cab7-45c9-a6f2-40e1c29ee544.json:                                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/f84d2a37-cab7-45c9-a6f2-40e1c29ee544.json:                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/DataGrip2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/f84d2a37-cab7-45c9-a6f2-40e1c29ee544.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/f84d2a37-cab7-45c9-a6f2-40e1c29ee544.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/DataGrip2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/264461cf-8ad4-46cd-a09c-9a2418eb98da.json:                                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/264461cf-8ad4-46cd-a09c-9a2418eb98da.json:                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2",
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/264461cf-8ad4-46cd-a09c-9a2418eb98da.json:                                "name": "idea.config.path"
/Users/leslieleung/Library/Application Support/JetBrains/Toolbox/channels/264461cf-8ad4-46cd-a09c-9a2418eb98da.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2",

Still not popping up any result...I already tried reinstalling CLion, won't work.

What is the output of:
find "$HOME/Library/Application Support/JetBrains" -name recentProjects.xml

What is the output of:
find "$HOME/Library/Application Support/JetBrains" -name recentProjects.xml

❯ find "$HOME/Library/Application Support/JetBrains" -name recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PyCharm2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/CLion2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PhpStorm2023.1/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/IntelliJIdea2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/AppCode2023.1/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/GoLand2023.2/options/recentProjects.xml
/Users/leslieleung/Library/Application Support/JetBrains/PhpStorm2023.2/options/recentProjects.xml

I used the latest Toolbox to uninsall and re-install CLion. Is it posible that I have to uninstall and re-install all JB products? I could try that during weekend, or maybe @Inmovilizame could try this uninstall and re-install trick since he just got IntellijIdea.
Come to think of it, I should have been more careful when upgrading a "BREAKING CHANGE" version of software.

I checkouted the debug tutorial for raycast here. But I don't know much about ts and nodejs and such, not to mention debugging.

For me:
grep -r 'idea.config.path' ~/Library/Application\ Support/JetBrains/Toolbox/channels

/Users/roi/Library/Application Support/JetBrains/Toolbox/channels/91730260-8484-481c-bb67-7c0cd5ab5800.json:                                                "name": "idea.config.path"
/Users/roi/Library/Application Support/JetBrains/Toolbox/channels/91730260-8484-481c-bb67-7c0cd5ab5800.json:                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/IntelliJIdea2023.2",
/Users/roi/Library/Application Support/JetBrains/Toolbox/channels/91730260-8484-481c-bb67-7c0cd5ab5800.json:                                "name": "idea.config.path"
/Users/roi/Library/Application Support/JetBrains/Toolbox/channels/91730260-8484-481c-bb67-7c0cd5ab5800.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/IntelliJIdea2023.2",

I then proceed to remove both IntelliJ and Fleet IDEs and JB Toolbox. Reinstall Toolbox using brew install jetbrains-toolbox and reinstall IntelliJ and Fleet through Toolbox UI. After that grep command looks like this:
grep -r 'idea.config.path' ~/Library/Application\ Support/JetBrains/Toolbox/channels

/Users/roi/Library/Application Support/JetBrains/Toolbox/channels/0c1f5147-faf9-4752-a279-0ed0c0b7a6a2.json:                                "name": "idea.config.path"
/Users/roi/Library/Application Support/JetBrains/Toolbox/channels/0c1f5147-faf9-4752-a279-0ed0c0b7a6a2.json:                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/IntelliJIdea2023.2",

But no luck... same result when invoking search recent projects in Recast :(

One thing worth mentioning, it seems to me the GLOB search can be failing. As the way Toolbox 2.x works with the installed tools differs from previous versions:
const ICON_GLOB = resolve(homedir(), "Applications/JetBrains Toolbox/*/Contents/Resources/icon.icns");
const HISTORY_GLOB = resolve(toolsInstall, "apps/**/.history.json");
const CHANNEL_GLOB = resolve(toolsInstall, "channels/*.json");
const APP_GLOB = resolve(toolsInstall, "apps/**/*.app");
const SETTINGS_GLOB = resolve(toolsInstall, ".settings.json");

console.log(toolsInstall)
console.log(ICON_GLOB)
console.log(HISTORY_GLOB)
console.log(CHANNEL_GLOB)
console.log(APP_GLOB)
console.log(SETTINGS_GLOB)

# Output:

# 00:29:38.627 /Users/roi/Applications
# 00:29:38.627 /Users/roi/Applications/JetBrains Toolbox/*/Contents/Resources/icon.icns
# 00:29:38.627 /Users/roi/Applications/apps/**/.history.json
# 00:29:38.627 /Users/roi/Applications/channels/*.json
# 00:29:38.628 /Users/roi/Applications/apps/**/*.app
# 00:29:38.628 /Users/roi/Applications/.settings.json

I was able to fix it while debugging the extension locally by adjusting the CHANNEL_GLOB to the proper path:
const CHANNEL_GLOB = resolve("/Users/roi/Library/Application Support/JetBrains/Toolbox", "channels/*.json");

I would say that an easy fix would be to add a third configuration option pointing to ~Library/Application Support/JetBrains/Toolbox folder. Worth mentioning too, Fleet has a very different folder layout and thus not gonna be compatible

Okay, can you just try resetting tools install to the default (just in Raycast Extensions) which should be ~/Library/Application Support/JetBrains/Toolbox and seeing if that works? I think the way the tools install stuff works is different again for v2 so doesn't need to match up with what is in the config in the same way now.

Okay, can you just try resetting tools install to the default (just in Raycast Extensions) which should be ~/Library/Application Support/JetBrains/Toolbox and seeing if that works? I think the way the tools install stuff works is different again for v2 so doesn't need to match up with what is in the config in the same way now.

Raycast complaints "Something went wrong" and here is the error log. Is it a dependency problem?
TypeError: Cannot read properties of undefined (reading 'find')

pd:util.ts:244:43

---
241:   if (channel.tool.toolName === undefined) {
242:     return undefined;
243:   }
244:   const defaults = channel.tool.extensions.find((extension: Extension) => extension?.type === "shell");
245:   return defaults?.baseName;
246: };
247:
---

recent.js:20:1235
    at async Promise.all (index 3)
async Ec:recent.js:20:1089

Can you post the contents of your ~/Library/Application Support/JetBrains/Toolbox/channels/{uuid}.json files? It seems like one of these might not have the expected values.

{
    "channel": {
        "updateFilter": {
            "application_type": "Goland",
            "quality_filter": {
                "description": "For the prudent. A stable version with reliable performance",
                "name": "Release",
                "order_value": 10000
            }
        },
        "installationDirectory": "/Users/leslieleung/Applications/GoLand.app",
        "autoUpdate": true,
        "history": {
            "toolBuilds": [
                {
                    "tool": {
                        "applicationType": "Goland",
                        "name": "GoLand",
                        "supersedes": [
                            {
                                "id": "Goland-ARM"
                            }
                        ],
                        "description": "An IDE for Go and Web",
                        "orderValue": 200000,
                        "homeUrl": "https://www.jetbrains.com/go?utm_source=product&utm_medium=link&utm_campaign=TBA",
                        "activation": {
                            "hosts": [
                                "goland"
                            ]
                        },
                        "languages": [
                            {
                                "id": "JavaScript"
                            },
                            {
                                "id": "CoffeeScript"
                            },
                            {
                                "id": "TypeScript"
                            },
                            {
                                "id": "CSS"
                            },
                            {
                                "id": "HTML"
                            },
                            {
                                "id": "Go"
                            },
                            {
                                "id": "SQL"
                            }
                        ],
                        "productOverview": {
                            "html_description": "GoLand makes it easy to read, write, and edit more than just Go code. It is fully equipped to handle web, frontend, and backend development, as well as work with databases. GoLand offers a host of smart features such as intelligent code completion, safe refactorings with one-step undo, a powerful built-in debugger, and on-the-fly error detection with quick-fixes. GoLand helps all Go developers, from novices to experienced professionals, create fast, efficient, and reliable code – and have more fun doing it.

Supported languages and technologies
Go, JavaScript, TypeScript, HTML, CSS, Dart, React, SASS, LESS, SQL and databases, Docker, Git, GitHub, and more",
                            "additional_links": [
                                {
                                    "type": "youtube",
                                    "name": "Take a video tour",
                                    "link": "https://youtu.be/DlF6EJurb88"
                                },
                                {
                                    "type": "homepage",
                                    "name": "More about GoLand",
                                    "link": "https://www.jetbrains.com/go/?utm_source=product&utm_medium=link&utm_campaign=TBA"
                                },
                                {
                                    "type": "whatsnew",
                                    "name": "What's new in GoLand",
                                    "link": "https://www.jetbrains.com/go/whatsnew/?utm_source=product&utm_medium=link&utm_campaign=TBA"
                                },
                                {
                                    "type": "documentation",
                                    "name": "Get started",
                                    "link": "https://www.jetbrains.com/go/learn/?utm_source=product&utm_medium=link&utm_campaign=TBA"
                                },
                                {
                                    "type": "documentation",
                                    "name": "Help",
                                    "link": "https://www.jetbrains.com/help/go/installation-guide.html?utm_source=product&utm_medium=link&utm_campaign=TBA"
                                },
                                {
                                    "type": "slack",
                                    "name": "Slack",
                                    "link": "https://gophers.slack.com/archives/C3FJ8M2PN"
                                },
                                {
                                    "type": "blog",
                                    "name": "Blog",
                                    "link": "https://blog.jetbrains.com/go/?utm_source=product&utm_medium=link&utm_campaign=TBA"
                                },
                                {
                                    "type": "twitter",
                                    "name": "GoLand on Twitter",
                                    "link": "https://twitter.com/GoLandIDE"
                                }
                            ]
                        },
                        "intelliJProperties": {
                            "productCode": "GO",
                            "shellScriptName": "goland",
                            "directoryPatterns": [
                                "$HOME/Library/Caches/GoLand*",
                                "$HOME/Library/Logs/GoLand*",
                                "$HOME/Library/Preferences/GoLand*",
                                "$HOME/Library/Application Support/GoLand*",
                                "$HOME/Library/Caches/JetBrains/GoLand*",
                                "$HOME/Library/Logs/JetBrains/GoLand*",
                                "$HOME/Library/Application Support/JetBrains/GoLand*"
                            ],
                            "recentProjectsFilenames": [
                                "recentProjectDirectories.xml",
                                "recentProjects.xml"
                            ],
                            "showSingleProject": true
                        },
                        "uninstall": {
                            "feedback": {
                                "url": "https://www.jetbrains.com/go/uninstall/?edition=2022.1.3&utm_source=product&utm_medium=link&utm_campaign=TBA",
                                "text": "Understanding the experience you had with our product will help us to make it better.",
                                "confirm_text": "Provide feedback…",
                                "cancel_text": "No, thanks"
                            }
                        }
                    },
                    "version": {
                        "name": "2023.2.1",
                        "quality": {
                            "description": "For the prudent. A stable version with reliable performance",
                            "name": "Release",
                            "order_value": 10000
                        },
                        "majorVersion": {
                            "name": "2023.2",
                            "order_value": 232000
                        },
                        "icon": "2df678aef370fe7b59cd449bb64147318af1b61fcbe9dac933e4a92308df6ec5",
                        "whatsNew": {
                            "full_html": "
 This build includes several bug fixes and other improvements.
",
                            "link": {
                                "url": "https://youtrack.jetbrains.com/articles/GO-A-231735815/?utm_source=product&utm_medium=link&utm_campaign=TBA",
                                "text": "Release Notes"
                            }
                        }
                    },
                    "build": {
                        "id": "232.9559.64",
                        "whatsNew": {
                            "full_html": "
 This build includes several bug fixes and other improvements.
",
                            "link": {
                                "url": "https://youtrack.jetbrains.com/articles/GO-A-231735815/?utm_source=product&utm_medium=link&utm_campaign=TBA",
                                "text": "Release Notes"
                            }
                        },
                        "type": "dmg",
                        "stripDirectories": 0,
                        "downloadUrl": "https://download.jetbrains.com/~urlswitch/go/goland-2023.2.1-aarch64.dmg?fromJetBrainsToolbox",
                        "downloadSize": 642935772,
                        "checksums": [
                            {
                                "alg": "sha-256",
                                "value": "08310be67b03a0f36cebf28fddfe0886d96f7446f04d25fec69beaaf222daf9e"
                            }
                        ],
                        "arguments": [
                        ],
                        "requirements": {
                            "cpu_arch": {
                                "$eq": "arm64",
                                "error_message": "This product is only available on arm64 platforms."
                            },
                            "os_version": {
                                "$gte": "10.15",
                                "error_message": "This version only supports macOS 10.15 or newer."
                            }
                        },
                        "dotAppIsSubdir": true,
                        "dotDesktopExtraEntries": {
                        },
                        "fileAssociationsSupport": {
                            "extensionsWithoutDot": [
                                "md",
                                "markdown",
                                "yaml",
                                "yml",
                                "htm",
                                "html",
                                "xhtml",
                                "css",
                                "js",
                                "js.map",
                                "jsx",
                                "json",
                                "json5",
                                "ts",
                                "cts",
                                "mts",
                                "svg",
                                "tsx",
                                "scss",
                                "sass",
                                "less",
                                "vue",
                                "pug",
                                "feature",
                                "go",
                                "gohtml",
                                "http",
                                "sh",
                                "s"
                            ]
                        },
                        "postInstall": {
                            "steps": [
                                {
                                    "id": "intellij.plugins.update",
                                    "progress": {
                                        "visible": true,
                                        "message": "Updating plugins…"
                                    },
                                    "required": false,
                                    "commands": [
                                        {
                                            "arguments": [
                                                "update"
                                            ]
                                        },
                                        {
                                            "arguments": [
                                                "update"
                                            ],
                                            "intellij": {
                                                "additional_vmoptions_content": "-Didea.force.plugin.updates=true"
                                            }
                                        }
                                    ],
                                    "intellij": {
                                        "temporary_copy_directories": [
                                            {
                                                "name": "idea.config.path"
                                            }
                                        ],
                                        "temporary_new_directories": [
                                            {
                                                "name": "idea.system.path"
                                            }
                                        ],
                                        "vmoptions_environment_variable": "GOLAND_VM_OPTIONS"
                                    }
                                }
                            ]
                        },
                        "released": "2023-08-28T00:00",
                        "intelliJProperties": {
                            "userVmOptionsPath": "",
                            "incompatibleVmOptions": [
                                "-agentlib:yjpagent",
                                "-XX:MaxJavaStackTraceDepth",
                                "-agentpath"
                            ],
                            "defaultConfigDirectories": {
                                "idea.system.path": "$HOME/Library/Caches/JetBrains/GoLand2023.2",
                                "idea.config.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2",
                                "idea.log.path": "$HOME/Library/Logs/JetBrains/GoLand2023.2",
                                "idea.plugins.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2/plugins"
                            },
                            "localizationPlugins": {
                                "ja": {
                                    "url": "https://plugins.jetbrains.com/pluginManager?action=download&id=com.intellij.ja&build=GO-232.9559.64"
                                },
                                "ko": {
                                    "url": "https://plugins.jetbrains.com/pluginManager?action=download&id=com.intellij.ko&build=GO-232.9559.64"
                                },
                                "zh-CN": {
                                    "url": "https://plugins.jetbrains.com/pluginManager?action=download&id=com.intellij.zh&build=GO-232.9559.64"
                                }
                            }
                        }
                    }
                }
            ],
            "source": "Migrated",
            "installedAt": "2023-08-23T09:00:14.774904Z"
        },
        "extensions": [
            {
                "type": "intellij",
                "xmx": "2048m"
            }
        ]
    },
    "tool": {
        "toolId": "Goland",
        "toolName": "GoLand",
        "icon": "2df678aef370fe7b59cd449bb64147318af1b61fcbe9dac933e4a92308df6ec5",
        "versionName": "2023.2.1",
        "majorVersion": {
            "name": "2023.2",
            "order_value": 232000
        },
        "buildNumber": "232.9559.64",
        "launchCommand": "Contents/MacOS/goland",
        "javaPath": "Contents/jbr/Contents/Home/bin/java",
        "propertiesDetected": false,
        "fileAssociationsSupport": {
            "extensionsWithoutDot": [
                "md",
                "markdown",
                "yaml",
                "yml",
                "htm",
                "html",
                "xhtml",
                "css",
                "js",
                "js.map",
                "jsx",
                "json",
                "json5",
                "ts",
                "cts",
                "mts",
                "svg",
                "tsx",
                "scss",
                "sass",
                "less",
                "vue",
                "pug",
                "feature",
                "go",
                "gohtml",
                "http",
                "sh",
                "s"
            ]
        },
        "postInstall": {
            "steps": [
                {
                    "id": "intellij.plugins.update",
                    "progress": {
                        "visible": true,
                        "message": "Updating plugins…"
                    },
                    "required": false,
                    "commands": [
                        {
                            "arguments": [
                                "update"
                            ]
                        },
                        {
                            "arguments": [
                                "update"
                            ],
                            "intellij": {
                                "additional_vmoptions_content": "-Didea.force.plugin.updates=true"
                            }
                        }
                    ],
                    "intellij": {
                        "temporary_copy_directories": [
                            {
                                "name": "idea.config.path"
                            }
                        ],
                        "temporary_new_directories": [
                            {
                                "name": "idea.system.path"
                            }
                        ],
                        "vmoptions_environment_variable": "GOLAND_VM_OPTIONS"
                    }
                }
            ]
        },
        "extensions": [
            {
                "type": "intellij",
                "defaultConfigDirectories": {
                    "idea.system.path": "$HOME/Library/Caches/JetBrains/GoLand2023.2",
                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2",
                    "idea.log.path": "$HOME/Library/Logs/JetBrains/GoLand2023.2",
                    "idea.plugins.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2/plugins"
                },
                "defaultXmx": "2048m"
            },
            {
                "type": "shell",
                "baseName": "goland",
                "name": "goland"
            }
        ]
    }
}

Are there any of those files without the last extensions block?
        "extensions": [
            {
                "type": "intellij",
                "defaultConfigDirectories": {
                    "idea.system.path": "$HOME/Library/Caches/JetBrains/GoLand2023.2",
                    "idea.config.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2",
                    "idea.log.path": "$HOME/Library/Logs/JetBrains/GoLand2023.2",
                    "idea.plugins.path": "$HOME/Library/Application Support/JetBrains/GoLand2023.2/plugins"
                },
                "defaultXmx": "2048m"
            },
            {
                "type": "shell",
                "baseName": "goland",
                "name": "goland"
            }
        ]

Actually, yes.
{
    "channel": {
        "updateFilter": {
            "application_type": "Space",
            "quality_filter": {
                "description": "For the prudent. A stable version with reliable performance",
                "name": "Release",
                "order_value": 10000
            }
        },
        "installationDirectory": "/Users/leslieleung/Applications/Space Desktop.app",
        "autoUpdate": true,
        "history": {
            "builds": [
                "2023.1.2"
            ],
            "source": "Migrated",
            "installedAt": "2023-08-23T09:00:20.560460Z"
        },
        "extensions": [
            {
                "type": "intellij"
            }
        ]
    },
    "tool": {
        "toolId": "Space",
        "toolName": "Space Desktop",
        "icon": "c915986ab8ca494c2c8637c3bac3b05b23d3526b09d8a8a6737c97fedd54665f",
        "versionName": "2023.1.2",
        "majorVersion": {
            "name": "2023.1",
            "order_value": 231000
        },
        "buildNumber": "2023.1.2",
        "propertiesDetected": false
    }
}

That's great, thanks so much for helping debug that. I'll get a release sorted that handles that properly. I see the issue with Space, Fleet and dotTrace, so the fix above applies for those three applications until I get that out.

Ok,
Local debug setup with the following values didn't work:

Shell scripts location: ~/bin
Tools Install location: `` # leave it blank

If I set explicitly to be the same hinted, it fails showing cannot find the shell scripts:

Shell scripts location: ~/bin
Tools Install location: ~/Library/Application Support/JetBrains/Toolbox

I was debugging a little bit more, and without uninstalling Fleet I was able to make it work with the following changes
# src/util.ts#330

export const getV2History = async (): Promise<AppHistory[]> => {
-  const scriptDir = (await getSettings())?.shell_scripts.location ?? bin;
+ const scriptDir = (await getSettings())?.shell_scripts.location.replace("~", homedir()) ?? bin;
  return (

Inside the getV2History function the shell_scripts location is not properly transformed :)

Okay, the same thing happens in V1 and it hasn't ever done the replacement. Perhaps people figured that out and never reported it. Regardless will add that fix to the updates, thanks for the extra debug effort there.

So, for me to make it work without any fix I had to ensure that in ToolBox the paths are set without using ~, as that value is the one used in getHistory and getV2History functions.

Thanks to all for the investigation and findings!

@Inmovilizame @LeslieLeung can you test if #8045 fixes your issues with the rogue apps installed?


Support Request: Hide Light Sensor Capability from Switchbot Curtain

Describe Your Problem
I am looking for documentation on the feature that was added into version 1.1.0 which allows hiding of the light sensor from HomeKit on a Switchbot Curtain as I can't see how to configure it in Homebridge
Relevant log output
No response
Config for homebridge-switchbot
No response
Screenshots
No response
Device & Model
Switchbot Curtain
Node.js Version
v14.17.6
NPM Version
v6.14.15
Homebridge Version
v1.3.9
Homebridge SwitchBot Plugin Version
v1.7.0
Homebridge Config UI X Plugin Version
v4.41.5
Operating System
Docker

Check out the Configuration wiki. If you still need help, reach out on discord.

Thanks! Just realised I needed to add the curtain device in 'Settings' which then gives all the config parameters, doh! 👍


Auto downsize images for thumbnails and previews.

Possibly https://github.com/EyalAr/lwip as a light weight solution.

Done.


Pass along "extra" correctly on InsertAll

Seems like "extra" was forgotten in the non-transactional path and only passed along when running in a transaction

Oops. Great catch, thank you!


Wrong StartupWMClass for DBeaver Enterprise

Hello,
When using DBeaver Enterprise under Ubuntu the dbeaver.desktop entry is not working. Even if the application launch, the icon I see is "unknown" and I can not attach it to the dock.
To make it work, you need to edit the dbeaver.desktop file => StartupWMClass=DBeaver Enterprise
Could it be patch in the debian package ?
I tried to make a pull request but could not find this particular file in your repo.

Fixed.
Could you check this in EA version (https://dbeaver.com/files/ea/) ?


Fixing QLNet.Old build.

This should get the QLNet.old sln building on the last few versions of Visual Studio.

Old project removed , closing PR


May I ask what this string of code means? I noticed that it will generate 64x64 images

in ddm.py 202 row
May I ask what this string of code means? I noticed that it will generate 64x64 images

这是ddp的问题


Disconnecting does not release lock file in dockdb

Describe the bug
Disconnecting does not release lock file in dockdb file.
To Reproduce
Steps to reproduce the behavior:

Add duckdb connection
Click on connect on the duckdb connection
Disconnect duckdb connection
Run external command(dbt) that will read and write to the duckdb file.
You will get an error that another process still has the lock file and you can only do write operations

Expected behavior
After disconnection, lock file should be released.
Screenshots

Desktop (please complete the following information):

SQLTools Version: v0.28.3
VS Code Version: 1.94.2
OS: Fedora 40 Workstation Edition
Driver:

[ x] duckdb v1.6.0

Database version: Duckdb

Additional context
I need to close VSCode to be able to run my external command(dbt).

Please report this to the author of the duckdb driver extension.


CMake: (fix) OpenMP dependency.

Hello,
In the original implementation the OpenMP libraries has been added
to the INTERFACE_LINK_LIBRARIES in the zfp-targets.cmake file using
an absolute path. This works but it is not portable. Using CMake
version 3.9 and latter the find_package(OpenMP ...) has been
significantly improved which allows for a relocatable solution of the
CMake config files. In addition, added ZFP_WITH_OPENMP variable to the
config file zfp-config.cmake to indicate if the zfp library has
been built with OpenMP support. If true, load the OpenMP package
using find_package(OpenMP ...).
Maybe a similar thing can be done for CUDA. Unfortunately, I do not
have access to both CUDA and nVidia GPU therefore I cannot investigate
how this should be done in your CMake configuration.
Best regards,
Jan-Willem

I noticed osx 2 tests of the Travis CI build failed. My guess that the reason they fail is due to fact Xcode 7.3 has been used. According to the Travis documentation this Xcode version makes use of CMake 3.5.2 which lower than the required CMake version 3.9.
Now the question is what is more important for you. Having a relocatable solution of the CMake config files or keep osx tests with Xcode 7.3 working.

You're right:
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
  CMake 3.9 or higher is required.  You are running version 3.6.2

It's probably OK to require CMake 3.9, but we'll have to update our Travis build matrix, which is something we're already in the process of doing.  Let's put this PR on hold for now until we're done with updates on our end.

I am glad to hear this CMake 3.9 requirement will most likely not be a problem.
Is it possible to give me an estimation when your updates are done? This gives me the possibility to manage the expectations of my colleagues.

This may be a bigger issue than I first thought as we're debating whether to move off Travis CI altogether.  That said, I think we can drop the Xcode 7 tests now just to get your PR to pass cleanly, which shouldn't take more than a day or so to address.  Of course, this fix will limited to the develop branch until the next release, which likely is several weeks away.

The develop branch is fine me. I can easy explain it to them that you have your own release cycle just like the software we here at Shell are deploying.

I dropped xcode7.3 from our Travis build matrix on develop.  Can you please rebase your PR?

Thanks. Sure no problem to rebase to the latest status of the develop branch.

Codecov Report

Merging #137 (2fba7f6) into develop (f25982a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #137   +/-   ##
========================================
  Coverage    94.84%   94.84%
========================================
  Files          268      268
  Lines        15216    15216
========================================
  Hits         14431    14431
  Misses         785      785

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f25982a...2fba7f6. Read the comment docs.

LGTM


[B11] Server stuck on "Stopping aura thread for dim 0" after I tried to shut it down

My server froze up with the last message being [03:57:51] [Thread-26/INFO] [THAUMCRAFT]: Stopping aura thread for dim 0, when I tried to shut it down via the quit command in the server console.
I can't say for sure that this is a Thaumcraft issue, but I played a lot of Thaumcraft today so it's hard to believe it would be a coincidence.
Here is the log: debug.log
Minecraft: 1.12.2
Forge: 2669
Thaumcraft: B11
Mods: list.txt

How do you solve it??


Implement session ticket support in case mbedtls is used as ssl library (IDFGH-5288)

This PR implements session ticket support in case mbedtls is selected as the ssl library and sever side session ticket support is enabled.
We're still using 4.2 and consider upgrading to 4.3. Is there any chance this change could get into 4.3?

Thanks for your contribution.

Hi @dbahrdt, Thank you for the contribution.
I had a few questions/suggestions on this one.

I think it would be a good idea to create a new config option for session tickets and have the support depend on that instead on the mbedtls config option.

Instead of giving functions out to users to initialise the session context, can we just keep a boolean in the esp_tls_cfg_server_t, something like 'use_session_tickets', and then depending on the boolean ( + esp_tls cfg option for session tickets ) initialise the
session_tickets_context inside the set_server_config function of esp_tls_mbedtls.c. As done for ALPN
That way we won't have to call any function and only set something like use_session_tickets = true in the esp_tls_cfg_server_t.

I think we can use the tls->ctr_drbg instead of defining a new one.

I think it would be a good idea to create a new config option for session tickets and have the support depend on that instead on the mbedtls config option.

I'll add the config option.

2. Instead of giving functions out to users to initialise the session context, can we just keep a boolean in the esp_tls_cfg_server_t, something like 'use_session_tickets', and then depending on the boolean ( + esp_tls cfg option for session tickets ) initialise the
session_tickets_context inside the set_server_config function of esp_tls_mbedtls.c. As done for ALPN
That way we won't have to call any function and only set something like use_session_tickets = true in the esp_tls_cfg_server_t.

The way I understand it esp_tls_t is used per session (https://github.com/espressif/esp-idf/blob/c13afea635adec735435961270d0894ff46eef85/components/esp_https_server/src/https_server.c#L104).
The rng is also initialized for each session (https://github.com/espressif/esp-idf/blob/c13afea635adec735435961270d0894ff46eef85/components/esp-tls/esp_tls_mbedtls.c#L77).
However I think we need to have the session ticket context to be persistent across sessions since we need to keep the key that is used to encrypt the session ticket.
I'm not really happy with the current solution either since I'm storing state data in a cfg struct.

Hi @dbahrdt sorry for the late reply, I was looking for any alternate implementation, but I think this is possibly the only way we can keep it persistent across the connections.
I have a few suggestions with this code which have been raised above.
Also, since it is related, do you plan to add the support for session tickets for client as well, otherwise I would be happy to add that !
Thank you

Hi @AdityaHPatwardhan,
Thank you for your comments. Hopefully I can address them tomorrow and push an improved version.
I'd be delighted if you implemented the client side part since I'm quite busy at the moment and client session tickets are not a priority for my company.

Hi @AdityaHPatwardhan,
sorry for the extremely long delay. I've addressed your comments and added the ability to dynamically enable the session ticket support. The API should now be compatible to the old API. Users of session tickets now need to call additional functions.
Users of the esp_https_server only need to set a configuration option.

Hi @dbahrdt No problems, It got delayed on my side as well ( sorry for that). Actually last week I had made required changes and was going to add the session tickets support for the client side. I see that you have made certain improvements to this. please have a look into my changes about moving the code to  esp_tls_mbedtls.c ?. I will rebase my changes on your new changes and submit a patch some time today so it will be easy to add them for you.
server_session_tickets.patch.zip
and once again thank you for your contribution.

Hi @AdityaHPatwardhan,
I had a look at your patch and I'll merge your (new) patch as soon as you publish it.
However you may also push directly to the source branch of this PR.

session_tickets_pr_changes.patch.zip
This is the patch, please check it once if it works in your case. Thanks
Umm, I don't think I can push directly to your branch in this PR. Maybe I need to push it to my GitHub first and then create a different  PR in your branch.

Hi @AdityaHPatwardhan,
I've checked the box Allow edits and access to secrets by maintainers.
To be honest I have no idea how you could push to my branch. I guess you could add my repository as another remote?
Anyway, I have applied your patch and pushed the changes.
I had to remove the references to mbedtls_print_error_msg since that function does not exist. Did you intend to print a human-readable error message?
Some timings with openssl s_time (esp32 rev1):
No session ticket support (disabled on runtime):
Collecting connection statistics for 30 seconds
**************

14 connections in 0.06s; 233.33 connections/user sec, bytes read 0
14 connections in 31 real seconds, 0 bytes read per connection

Now timing with session id reuse.
starting
***************

15 connections in 0.06s; 250.00 connections/user sec, bytes read 0
15 connections in 33 real seconds, 0 bytes read per connection

With session tickets:
Collecting connection statistics for 30 seconds
***************

15 connections in 0.07s; 214.29 connections/user sec, bytes read 0
15 connections in 32 real seconds, 0 bytes read per connection

Now timing with session id reuse.
starting
rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr

565 connections in 0.47s; 1202.13 connections/user sec, bytes read 0
565 connections in 31 real seconds, 0 bytes read per connection

The difference is tremendous. In my view this is an important building block for the usage of tls/https connections on iot devices.
A connection setup of 2 seconds to switch a lightblub is just too much. Persistent connections are not a good option either due to the memory usage (it's better with dynamic receive/send buffers).

@dbahrdt Thanks for applying the changes,
Actually the mbedtls_print_error_message is a new API added in the master branch of the idf. for printing the debug info for the error messages.
I think you will need to rebase your current branch over master since it points to a very old master.
Thanks for sharing the results of your test case.  I agree this  is a good improvement

Hi @AdityaHPatwardhan,
that is strange. I've recently rebased to the current master branch. My fork says so too (https://github.com/dbahrdt/esp-idf/tree/mbedtls-session-tickets-in-master: This branch is 9 commits ahead of espressif:master.)
Searching for the function in the espressif/esp-idf repository does not yield a result (https://github.com/espressif/esp-idf/search?q=mbedtls_print_error_msg&type=code).
Could you point me to the file where that function is declared? Thanks.

ohh, I understand. I am using our internal codebase in which the MR is merged on 28 June, But I think it has not been updated on GitHub till now so that's why you are unable to view it.
Never-mind, I will do that when I will open an internal MR for merging this PR

Thanks for your contribution, and sorry for late reply, we have put the changes into our internal review queue, and the PR will be updated once the changes are available on GitHub. Thanks.

Hi @AdityaHPatwardhan,
unfortunately my code contained several bugs. I did not check the validity of the session ticket context pointer in the free functions.
This resulted in a crash if session ticket support was enabled in Kconfig but not during runtime.
I also ported all changes to 4.3 (https://github.com/dbahrdt/esp-idf/tree/patch/4.3%2Fsession-tickets).
The only difference to this PR is the location of the error codes which are defined in an extra file in master but not in relase 4.3.

@dbahrdt Thank you very much for fixing the issue.
I understand this MR has been long due for merge. This was blocked on a discussion where we would implement this in alternative along with the client. But that seems to be very complicated for the user and this is indeed an easier approach.
Thank you for your patience.
As for adding this feature in release/v4.3. I don't think this will be added in release/v4.3 since this is a new feature and contains considerable amount of code change.


How display only owned data to user's

This is  a help request.
Description

Logged in user show only his department's data and edit only his created data. How check this in controller. how implement
Steps to Reproduce

Expected behavior

Display only filtered some data
Actual behavior

Displaying all data

Start by reading everything here
I’m closing this because it’s not related to enso.


Master

Resolved.  However, I still think you might want to revert this merge.  The changes are pretty drastic.  I think the only code that should be merged is the port to python 3.5.2.

Hi there.  It just occurred me to that you merged the code as a result of a pull request.  Except I didn't initiate one--it looks like one of my students initiated it by accident.  I'm so sorry.  I recommend reverting the merge, and with your permission, I'll do it.

Hmm, guess I should have looked at it more closely.  I'll just go ahead and give you permission to help manage pull requests.

Thanks!  Reverting now.


Remove global allocator

System allocator has been used by default since Rust v.1.32.

Closed in favor of #1759 .


Getting field names out of Prisma validation errors

Problem
Prisma throws validation errors that are difficult to parse and use:
{
  "error": "\nInvalid `prisma.employer.create()` invocation:\n\n{\n  data: {\n+   label: String,\n?   id?: String,\n?   contracts?: {\n?     create?: EmployeeContractsCreateWithoutEmployerInput | EmployeeContractsCreateWithoutEmployerInput | EmployeeContractsUncheckedCreateWithoutEmployerInput | EmployeeContractsUncheckedCreateWithoutEmployerInput,\n?     connectOrCreate?: EmployeeContractsCreateOrConnectWithoutEmployerInput | EmployeeContractsCreateOrConnectWithoutEmployerInput,\n?     connect?: EmployeeContractsWhereUniqueInput | EmployeeContractsWhereUniqueInput\n?   }\n  }\n}\n\nArgument label for data.label is missing.\n\nNote: Lines with + are required, lines with ? are optional.\n"
}

Suggested solution
It would be nice to have a map of errors attached to error objects. For example this can be useful to highlight submitted form inputs with error state from server-side validation.
// data shape of this error property could look like a map:
{
  [ target ]: {
    code: string // Prisma error code
    target: string // path to offending field
    message: string // error string excluding field name
  }
}
// example
{
  "data.label": {
     code: "P2002",
     target: "data.label",
     message: "unique constraint violation"
  }
}

Alternatives
I tried to parse Error objects and their multiline error message but that is super-cumbersome approach.
Additional context
null

Hi!
I think this would be a great addition to Prisma. PrismaClientValidationError is not very useful as it is, and with the latest 5.0 upgrade it is harder to parse the offending fields and respective errors:
    Invalid `prismaObject.create()` invocation in
    /opt/app/src/prisma/api.ts:370:41

      367 let result;
      368
      369 try {
    → 370     result = await prismaObject.create({
                data: {
                  m12F1: "Bleh",
                  m12F2: 100,
                  m13: {
                    create: {
                      m13F2: 200,
              +       m13F1: String
                    }
                  }
                },
                select: {
                  id: true,
                  m12F1: true,
                  m12F2: true
                }
              })

    Argument `m13F1` is missing.

      at buildRelationalQueryError (src/prisma/error.ts:107:17)
          at async Promise.all (index 0)

Before (<= 4.16) it would report the field path in the error message: "Argument data.m13.create.m13F1 is missing.".
I was unsure whether to report this as an error but I believe that instead of relying on a message in an Error object, it makes more sense to extend the PrismaClientValidationError so developers have the validation data already parsed
This is a good improvement for Prisma integration layers and frameworks. I'm sure I'm not part of the very few that needs proper error handling on their apps.
Thanks!

Hi ! Is there any improvement planned on this yet ?


Binned survival data

Suppose I have continuous survival data, but some instrument ends up binning it. How do I model that?

Interval censoring is one solution


_sanitize_path fails on Python 3.12

Traceback
    def _sanitize_path(filepath):
        try:
            path_root = Path(getattr(settings, 'SENDFILE_ROOT', None))
        except TypeError:
            raise ImproperlyConfigured('You must specify a value for SENDFILE_ROOT')

        filepath_obj = Path(filepath)

        # get absolute path
        # Python 3.5: Path.resolve() has no `strict` kwarg, so use pathmod from an
        # already instantiated Path object
>       filepath_abs = Path(filepath_obj._flavour.pathmod.normpath(str(path_root / filepath_obj)))
E       AttributeError: module 'posixpath' has no attribute 'pathmod'

Fix

actions & readme needs updating so we start testing on 3.12
code (obviously!) needs updating

Who?
I don't have a PR ready yet, this is a simple fix but some time needs to be spent. Currently I'm not working on this, but if anything changes I'll let you know.
Thanks for maintaining django-sendfile!

Fixed in #60


IPostprocessComposer.With, perhaps, should allow me to read properties from the object being created.

E.g.:
fixture.Customize<MyThing>(c => c
    .With(o => o.End, o => o.Start.AddDays(2)));

So, this is adding the following member to the interface:
IPostprocessComposer<T> With<TProperty>(Expression<Func<T, TProperty>> propertyPicker, Expression<Func<T, TProperty>> valuePicker);

Then, I can look at other properties on the object to determine what my current property should be set to. This is assuming that auto-property-filling happens before manual-property-filling.

Thank you for your interest in AutoFixture. As explained in #544, I don't want to add more members to the fluent DSL, so I'm going to close this suggestion.


Allow to typing before the response finished

Is your feature request related to a problem? Please describe.
Currently, we have to wait the response finished, even we've found some things in the response that we want to respond, we can't type in the input box, but need to wait for the response finished, which somehow could waste some time.
Describe the solution you'd like
Allow user to use the input box, just deny user to send it before the response finished.
(or even more awesome, allow user to virtually send the message, and the program will automatically send to once the response received)
Additional context
Official ChatGPT web interface also allow this feature.

That's a good idea. I think I need to adjust the UI, for example, add a stop/send button and then disable the button only when generating the answer

Hi there!
I have submitted a new pull request that addresses this issue. You can find it here: #268.
@josStorer  Please let me know if it's good to you. Thank you!

Thanks to @tang-ji 's contribution! The latest version now supports this feature


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.441

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.441


I don't known which file is modifed in your source code ?

❓ Questions and Help
Hello ! You really did a good job. But I don't  known which file is modifed in your  source code  ?

I think there are source fairseq codes.

I mainly modify the "label_cross_entropy_contrastive" file under the criterion folder.

Sorry for the inconvenience caused， I mainly modify the "label_cross_entropy_contrastive.py" file under the criterion folder.


Change http URL to https

Deploy preview processing.
Built with commit 95f7c12025dc8ab331d11ed76e8a8bbb192116fa
https://app.netlify.com/sites/theme-ec3raf3m5t/builds/57b0b8b971e20a1101949305


Add librespeed/speedtest-cli

https://github.com/librespeed/speedtest-cli

Thank you for your contribution!
Basically, you don't have to create an Issue before sending a Pull Request in this repository.
I'll update CONTRIBUTING.md.

https://github.com/aquaproj/aqua-registry/pull/7389


Added support for timeOffset and timeWindow options across the board

Hi Matt,
Really useful module, thanks. I needed support for timeOffset and timeWindow options which didn't seem to be implemented yet so I've added this in.
At the same time I was able to streamline the code a bit and remove some duplication.
Thought I might as well share it back.
Ben

Hi Ben,
Thanks for using the module and thanks for submitting your improvements back! Those extra options should be useful. If you don't mind me asking, what are you using the module for? It's the first one I've pushed to npm and I'm curious about how people are using it?
The simplification looks good. I spotted a typo and a console.log line that snuck in there. If you can sort those out I'll merge it.
Cheers,
Matt

Hi Matt,
I've fixed those. Wow... Its like I'm living the open source dream! I have
written one NPM module ( npmjs.com/package/frameworx ) but this kind of
collaborative open source working is new to me too.
As for what I'm doing with it... I'm hoping to build an application to
provide voice based rail information off the back of Google Actions i.e.
"OK Google, when's the next train to London?" would give a reply like "If
you can get to Brighton station by 18:45 you can catch the 18:40 departure
from platform 2 which is running 5 minutes late. This is the train for
Gatwick Airpoort, it should get you in to London for 19:30. Let me know if
you want a later or earlier train that this."
Ultimately there would be scope for more that just "next train to X" but
that's my initial goal.
I think I now have all the building blocks I need:

Database of all UK train stations codes and locations
Checked that Google Actions can provide user's location
Checked I can do a "find closest" search using MySQL spatial data
Access to the live departure information
Basic "hello world" Google Actions app up and running
So... now I just have to start bolting it all together.

Hope you agree it would be a cool thing to be able to do.
Ben
On 2 June 2017 at 08:43, Matthew Salt<EMAIL_ADDRESS>wrote:

@mattsalt commented on this pull request.
In index.js
https://github.com/mattsalt/national-rail-darwin/pull/2#discussion_r119798246
:

requestXML = requestXML.replace('$$FROM$$', station)

if (options && options.destination) {
requestXML = requestXML.replace('$$FILTER$$', options.destination)
} else {
requestXML = requestXML.replace('$$FILTER$$', '')
}
this.thenablePOST(requestXML).then(function (result) {
callback(null, parser.parseArrivalsBoardResponse(result))
}).catch(function (err) {

Typo, should be callback.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mattsalt/national-rail-darwin/pull/2#pullrequestreview-41710089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuBXVlBX-kqVE6lU3iVj0UxRlh9zI-Cks5r_70qgaJpZM4NtsoV
.

That does sounds cool! I would definitely use that. Good luck bolting it all together :)
Ha, I know what you're talking about. I'm always slightly surprised when this open source thing works.
Thanks for making those changes. I'm on holiday at the moment so it will take me a few days to publish this as a new version to npm. I'll let you know when its live.
Cheers,
Matt

I've just published version 1.0.2 with your changes in it so you should be able to pick it up from the registry now. Feel free to add details of these two new options to the readme if you get time.


How to enforce creator earnings on seadrop contract?

My seadrop deployment is showing all tokens without royalty paid to the creator.
https://github.com/ProjectOpenSea/seadrop/assets/30054030/5b16c01b-e80d-4a54-9f34-b9369a4342a1
How do I make it so that the sale of an NFT always pays 5% to the creator?

The royalty also shows up as optional whereas seadrop does implement royaltyInfo. I want to make it so that it is enforced. How do I do that?

seadrop has no secondary royalty enforcement mechanism, the token simply provides ERC-2981
creator earnings are only optional and can no longer be enforced on OpenSea for new collections. see the announcement here: https://opensea.io/blog/articles/creator-fees-update
also, please stop opening issues and instead use discussions


When using SELECT * all FUNC() are returned as a distinct columns even if they are defined "as col_name"

If we give it this data and this query:
var data = [{a:1,b:1,c:1},{a:1,b:2,c:1},{a:1,b:3,c:1}, {a:2,b:1,c:1}];
var res = alasql('SELECT *, COUNT(a) AS d FROM ? GROUP BY a', [data] );

the result is:
[{
  a: 1,
  b: 1,
  c: 1,
  COUNT(a): 3, <--- ???
  d: 3
}, {
  a: 2,
  b: 1,
  c: 1,
  COUNT(a): 1, <--- ???
  d: 1
}]

Hi @mathiasrw would like to work on this if nobody's picked it up yet.

Hello @mathiasrw found the issue. There's a flaw in how the selectgfn method for Query is formed behind the scenes specifically for the current issue. When there's a select * in addition to there being column(s) with alias in the query, the selectgfn looks something like this:
(function anonymous(g,params,alasql) {
    var y;
    var r = {};
    for(var k in g)
    {
        r[k]=g[k]
    };

    r['d']=(y=g['COUNT(a)'],y===y?y:undefined);
    delete r['COUNT(a)']
    return r
})

Let's consider the above example provided in the issue:
at the stage where gfn or selectgfn is called for the query in queryfn3,

the object for query.group[i] will be of the format : {a:"", b:"", c:"", 'COUNT(a)':"" } . Also, we have an alias for COUNT(a) which is d. Calling the function above with this data would result in an object of the form {a:"", b:"", c:"", 'COUNT(a)':"", d:"" } .
Clearly this signifies that Select * that should pull in all the columns of the data source, rather pulls in all columns of the current state of data which doesn't work in this case.
Based on my preliminary investigations, here are some of the possible solutions:

Find out a way to identify whether a specific column is from the data source (can probably use the keys of of query.params[i] or source.data to identify this). This solution could have a significant impact and could potentially have some side effects. So, we need to be careful with this.

After calling selectgfn, remove those entries from the data for which the key and value don't match in the query.groupColumns. Something like this:

This gives the expected output:

The second solution doesn't seem to have any side affects when I ran the test cases.

Very very nice work diving to the core of this issue. Would you be OK to make a pull request with your proposed fix? Have a look in https://github.com/AlaSQL/alasql/blob/develop/CONTRIBUTING.md if you have any doubts, or ping me here.

Hi @mathiasrw, have raised the PR with fix as well as test cases. Do let me know in case you see any issues.

Released as part of v4.1.10


changes to protobuf services for gRPC, few other fixes

code generated for services needed a few changes to have gRPC work with it.

service name prefixed with package name
call_method made aware of ServiceDescriptor

upgraded tests, some code clean up
changes to make it work on Julia 0.6

Coverage increased (+1.8%) to 71.989% when pulling 8bb681013e7da7b569e95560e613cf0b5b7e1227 on tan/testsvc into 53c124e87d6b146b31e0fd43cea6057c206de337 on master.

Current coverage is 71.98% (diff: 84.21%)

Merging #82 into master will increase coverage by 1.80%

@@             master        #82   diff @@
==========================================
  Files            17         17
  Lines          1117       1121     +4
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            784        807    +23
+ Misses          333        314    -19
  Partials          0          0

Powered by Codecov. Last update 53c124e...8bb6810


Black all code and add pre-commit hooks

#6

@samwebster the pre-commit hook should take care of formatting any changed files when you create a commit. (Assuming you use git from a command line, not sure how it works if you interact with git from within VS. I know there's a plugin to format python files using black in VS Code, perhaps there's something similar for VS?)


Added login / register page

Describe the feature
Create a login/sign-up page
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

please assign me this issue.  it's not getting updated in leaderboard even after being merged.

@Kalivarapubindusree  please assign me its already merged.


socket.recv() waits infinite when the connection is lost

If the connection is already established, a new call to read() will never finished in case the connection to the heat pump is lost inbetween.
It seems to resume if the heat pump is available again.
Is this a bug or a feature?

We could set _socket.setdefaulttimeout() to a sensible value, e.g., 5 seconds.
What shall we do when the timeout occurs? Raise an error? Try to reconnect?

Normally I would close the socket and return the error status using the return parameter. The user then has to handle the error.
But that's almost like an "API change".


How to store issued credentials

Hi! I am new to learn hyperledger.
I have played around with the demo agents (faber and alice) and get it running. I changed the code to create my own credential definition. I am also running a local von-network.
I can issue a credential by using the swagger API and alice gets the credential.
But when i restart the agents, the credentials are lost.
What i have to do, to get the agents to store the credentials?
I think i have to start the agents in provision mode?
But i have not figured out to do it right.
Is there any tutorial out there with detailed steps?

Hopefully you found out about this.


Fix blend shapes

Fixes #55812 for real now that i actually understood the blend shape math.
reduz was right in https://github.com/godotengine/godot/pull/60814 and tangent was wrong. With this #60814 is no longer needed

I'm not familiar with this code, but is there a way to describe what this fix does in a somewhat more verbose way? "Fix blend shapes" is pretty generic, does it really fix everything about blend shapes, or does it fix a specific bug in the blend shapes implementation that would be worth naming in the commit?

Thanks!


Code Signing Issues

Ive installed AudioKit Via Cocoapods. I am having code signing issues which have been discussed in previous posts on here.
Following the install.md guide I have
created a new run script phase
pasted the following run command
"$BUILT_PRODUCTS_DIR/$FRAMEWORKS_FOLDER_PATH/AudioKit.framework/fix-framework.sh"
dragged the run script phase below  the  "Embed pods Frameworks" phase
then cleaned  and archived the product
I get the following errors :-
Showing Recent Issues
fatal error: lipo: -remove i386 specified but fat file: ./AudioKit.framework/AudioKit does not contain that architecture
Showing Recent Issues
fatal error: lipo: -remove x86_64 specified but fat file: ./AudioKit.framework/AudioKit does not contain that architecture
Showing Recent Issues
Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure
Any ideas?
Thanks

just needed to add the architects to the "Valid Achitectures"


Parse supported verbs, only process types that support list/watch for informer/listergen

closes #40

/retest

addressed (other than the sets one)


Blocking version of esp_a2d_sink_connect (IDFGH-9241)

Is your feature request related to a problem?
esp_a2d_sink_connect returns immediately without a clear indication of when the a2dp connection attempt has finished (whether success or failure). There is a callback for ESP_A2D_CONNECTION_STATE_EVT but it isn't clear from the code that it could be used to build one's own blocking connection attempt (for example, there is not a "not found" conn_state). It would be wonderful to have a blocking version of this function so that the application's auto-connect logic can be more reliable and simpler
Describe the solution you'd like.
Ideal example:
void app_main() {
// ...
// Try to connect to a Bluetooth device
esp_err_t result;
do
{
    result = esp_a2d_sink_connect_blocking(a_bluetooth_addr, portMAX_DELAY);
} while (result != ESP_OK);
// ESP_OK = successfully connected. ESP_ERR_TIMEOUT or ESP_ERR_NOT_FOUND if device wasn't found. etc.
// ...
}

Describe alternatives you've considered.
For example (some long parts omitted in comments for brevity):
// Keep track of connection state to Bluetooth device
volatile int connected = 0;

void app_main() {
// ...
// Try to connect to a Bluetooth device
while (connected == 0)
{
    esp_a2d_sink_connect(a_bluetooth_addr);
    // 5 second delay or wait for task notification
}
// ...
}

static void bt_a2d_sink_cb(esp_a2d_cb_event_t event, esp_a2d_cb_param_t *param)
{
// ...
    switch (event) {
        case ESP_A2D_CONNECTION_STATE_EVT:
            // ... depending on the conn_state, set connected = 0 or 1
            // ... notify task
     }
// ...
}

I've considered trying this (e.g. to see if I get a DISCONNECTED event when it fails), but I feel with the lack of distinction between a connected device disconnecting, and an outgoing connection attempt failing, the callback logic could get kind of messy. Especially if more than one device is connected.
Additional context.
No response

This would still be helpful

Hi @ftab,
Thanks for your suggestion. The ESP32 Bluetooth stack is designed to be non-blocking, so you can implement your own blocking mechanism by using events in callbacks. You can use esp_bt_gap_start_discovery to see if the peer device is in the range. However, it does appear to be more complex than your feature request. Maybe we can provide a simple discovery API like esp_a2d_sink_discovery to see if the a2dp source is in the range.

Thanks for the reply @boblane1
If I understand correctly, esp_bt_gap_start_discovery only works when the device is in pairing mode (e.g. phone is at Bluetooth settings screen)
I wanted to make my own blocking version of esp_a2d_sink_connect but a failed attempt to connect does not bubble up to the layer that esp_a2d_sink_connect works at (additionally: it is sometimes hung up for a full minute due to #13154 ). I only get "disconnecting", "disconnected", "connecting", "connected" -- there is no "failed to connect" status, and I'm not entirely sure how to get to the lower layer to get, for example, the result of the "hcif conn complete" event to try to guess myself. So my current method is just blindly attempt every 5 seconds until I receive the "connected" callback.

If I understand correctly, esp_bt_gap_start_discovery only works when the device is in pairing mode (e.g. phone is at Bluetooth settings screen)

Yes, you are right.
How about not issuing the second connection process before the first connection result comes("disconnected",  "connected") to implement blocking connection? In fact, the stack will ignore the redundant connection requests when it is already in connecting state.


Standard python print doesn't work

Seems the standard python print function stopped working with the newest hub version.

Seems issue was with using an old version of the plugin/vscode.


Jsc apple

I get the box rendered. Many things to fix on the javascriptcore side(reference, private objects, ...). I also have  a crash in bgfx and it needs improvements on the metal shader loading. I didn't find anything in the shadercompiler to change the structure names. I'll look at shaderc. Anyway, it's in a state that allows me to spend some time on iOS compilation/CI.

I managed to remove the std::map for externals using a dummy class. I tried without success for the other 2 as the objectref are functions and not data


Create CB22_flask

fixes #

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

do not open garbage PRs like this one in other people's projects.


error to run

please help. I have this error.
/usr/lib/node_modules/homebridge/lib/api.js:64
throw new Error("The requested accessory '" + name + "' was not registered by any plugin.");
^
Error: The requested accessory 'GPIODevice' was not registered by any plugin.
at API.accessory (/usr/lib/node_modules/homebridge/lib/api.js:64:13)
at Server._loadAccessories (/usr/lib/node_modules/homebridge/lib/server.js:286:42)
at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:87:38)
at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object. (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (internal/modules/cjs/loader.js:799:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:810:10)
at Module.load (internal/modules/cjs/loader.js:666:32)
at tryModuleLoad (internal/modules/cjs/loader.js:606:12)
at Function.Module._load (internal/modules/cjs/loader.js:598:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:862:12)
at internal/main/run_main_module.js:21:11

Can you post the entire log error and your config please.
Thanks

This is an homebridge error you have to check homebridge-gpio-device is installed or if error launched by this plugin

Homebridge-gpio-device is installed. And this error only happens after add this accessory to config.json.

So you must have another loading error before/after this one.
Search homebridge-gpio-device in your logs.

Where log is located?

sudo journalctl | grep homebridge


Issue in loading of control

We have been using “Multiselect_Records_PCF” control in our CRM Application. We have facing a issue in the control after implementation.
Issue: Selected records are not showing in the control when record opened the first time.
Scenario:

User selected multiple options in PCF control from Create Form and created the record.
When user again opened the record, selected values in PCF control is not shown.
User tries to refresh the page.
Values are visible in the PCF control.

It will be very helpful if you can spare some time to look into it.

Hey @shivamagarwal10
I am trying to replicate your issue, however that's not happening for me.
I am attaching a couple of GIFs.
First of them is:

Creating a new account, set the name and select names. Click Save.
Refresh the page
Values are still there

https://user-images.githubusercontent.com/11043789/115993293-75066280-a5d2-11eb-88e6-5747f92d1e95.mp4
Second of them:

Creating a new account, set the name and select names. Click Save.
Click on the left on entity Accounts and select "New Account 2"
Values are still there

https://user-images.githubusercontent.com/11043789/115993556-aaf81680-a5d3-11eb-90db-17f15f68028c.mp4
Is there something that I am not replicating exactly as you are doing?
Thank you

Hi @victorsolaya ,
Below are the steps we are using :-

Create record from the powerapps portal.
Open the record in CRM after creation. ( check 1.png)

Refresh the record. ( Check 2.png)

Records are visible. (check 3.png)

Thanks,
Shivam

Hi @shivamagarwal10
So you are creating the record from Power Apps Portals, therefore the PCF Control is inside the Portals, is that right?
I think that was the information I didn't have, since I thought you were creating the record from the Model Driven App.
To be fair, I haven't checked the control inside the Portals, but worth taking a look.
Thank you!

Hi @victorsolaya,
PCF control is not inside the portal form. We have just kept the text-area field inside the portal and filling the value in the text-area. But we are rendering the PCF control only in CRM form.
Thanks.

Hi @shivamagarwal10 So you are filling the whole JSON by hand or with some Javascript?
Sorry for all the questions but I want to try as similar as you have so I can get to the point
Thanks!

All right, I see now what you mean. I will try to fix that bug and let you know once it's done.
Good catch 😄

Hi @shivamagarwal10 I think your bug has been fixed within the latest release v<IP_ADDRESS>. It was due to the setvalue of the fields, it was not reflecting the changes.
I have done a video to show you how this works now.
Let me know if this release fixes the bug you were having.
Thanks!
https://user-images.githubusercontent.com/11043789/116809695-9241b080-ab3f-11eb-9aaf-d545f891a711.mp4

Hi @shivamagarwal10
Could you let me know if your issue was fixed with this release?
Thank you!

Close as no activity was found


2.1.0-preview1

This issue is meant to collect feedback about the 2.1.0-preview1 package.
For information on how to use this package see: https://developers.redhat.com/blog/2018/07/24/improv-net-core-kestrel-performance-linux/
If you encounter an issue, please create a new issue and we'll keep an overview in this comment.

There is no data that suggests this Transport offers a significant benefit compared to the Libuv/Sockets Transport for real workloads.
For this reason we won't publish a supported version to nuget.org.


[query] Can an LXD client run a desktop environment?

The examples given for LXD [1] [2] centre around terminal-based server use-cases. Can an LXD client run a graphical desktop environment in the same way as, for example, GNOME Boxes or VirtualBox?
https://askubuntu.com/questions/907385/can-an-lxd-client-run-a-desktop-environment

Short answer is "no". Containers don't have virtual graphic cards so there's nothing for them to render to.
There are some alternatives though:

Run Xephyr or similar on the host, then pass the X socket to the container and run things against that
Run some kind of VNC/RDP based server in the container and connect to that from the host
Give the container full access to your host's devices (GPU and terminal), this would let you have your desktop environment in a container with a mostly blank host


Template not there

[Enter feedback here]
On the Active Users in O365 admin panel, there are no Templates link anywhere to click on.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d0a03342-9a4b-cf1d-9a3b-7bdee0fe6b09
Version Independent ID: 260c8359-f319-0647-ab77-a594ec872b2b
Content: Create and use a template to add users - Microsoft 365 admin
Content Source: microsoft-365/admin/add-users/create-and-use-a-template-to-add-users.md
Service: microsoft-365-business
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@GTAdoum Thank you for your feedback. I was able to find the option under users-->active users

If you continue to have this problem, I'd recommend you contact Microsoft support via the need help link so that a support engineer can assist you.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @GTAdoum Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

I discovered that it depends on the user, the access that have been defined for it.  My admin user did not have access to templates, I had to use another admin user that had all the access.


Support raft for HA storage

I saw issue #197 about adding Vault's Integrated Storage for HA, and wanted to try it.
I am not certain that using the $instance_ip_address is the best thing for the node_id, but wasn't sure what else to use (and it works...).
I added two flags: --enable-raft-backend and --raft-dir.  --raft-dir should work identically to the --config-dir type flags, and the default direction is created by the install-vault script too.
I don't see any tests to verify this, other than it is working in my test aws account.

Thanks for the PR! We need to resolve https://github.com/hashicorp/terraform-aws-vault/issues/196 first and can then take a look at this PR. Hoping to get to that in the next week or two. If anyone has cycles to look into it before then, help is very appreciated!

One thing I have noticed with the raft ha storage is that if I stop Vault on a node, or terminate the node (gracefully), the Vault instance never leaves the raft list of peers when checked on other nodes.

I might have some time to do that later this week - I have just done the rebase for now.
Thanks

Is there an update on this?  @Pondidum

Is there an update on this?  @Pondidum

This had completely slipped my mind (I switched to using the dynamodb backend for my deployment), but I think I will have some time over the next week - I have some demos on Wednesday, so it would be after that I think.
I'll set a reminder this time...

This had completely slipped my mind (I switched to using the dynamodb backend for my deployment), but I think I will have some time over the next week - I have some demos on Wednesday, so it would be after that I think.
I'll set a reminder this time...

@jboero I've added an example which uses the raft backend, but there is an issue, which I also hit when trying to write the test for it too:  The raft version needs the certificate on each machine to be valid for the machine's private IP, not just <IP_ADDRESS> and vault.service.consul, as otherwise the machines fail to cluster due to TLS errors.
I am not sure how to go about generating the right certificates ahead of time, as the private IP is unknown until the machines boot.

@jboero I've added an example which uses the raft backend, but there is an issue, which I also hit when trying to write the test for it too:  The raft version needs the certificate on each machine to be valid for the machine's private IP, not just <IP_ADDRESS> and vault.service.consul, as otherwise the machines fail to cluster due to TLS errors.
I am not sure how to go about generating the right certificates ahead of time, as the private IP is unknown until the machines boot.

@jboero I've added an example which uses the raft backend, but there is an issue, which I also hit when trying to write the test for it too: The raft version needs the certificate on each machine to be valid for the machine's private IP, not just <IP_ADDRESS> and vault.service.consul, as otherwise the machines fail to cluster due to TLS errors.
I am not sure how to go about generating the right certificates ahead of time, as the private IP is unknown until the machines boot.

I have a similar issue with integrating Vault plugin.
The plugin uses api_add (default is private IP) to communicate with the vault server.

Yes it seems like this is a pickle.  We shouldn't be using direct IPs when possible.  Other than a nasty wildcard cert I'm not sure what the answer is.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.


Update README.md

oops, merged too fast
(thought i assume it was already fine for you)

Yes, I should have approved the first time.


Sublattices without explicitly specified executors don't inherit the parent lattice's executor.

Description
When users do not specify an executor in a lattice decorator, the lattice's executor is intended to be automatically set as follows:

If the lattice is top-level, use the default executor from the Covalent config.
If the lattice is a sublattice, use its parent lattice's executor.

Consider the following simple lattice consisting of a single sublattice. The top-level lattice's executor is set to "dask", whereas the sublattice's executor is unspecified.
@ct.electron
def task(x):
    return x*x

@ct.electron
@ct.lattice
def subworkflow(x):
    return task(x)

@ct.lattice(executor="dask")
def workflow(x):
    return subworkflow(x)

dispatch_id = ct.dispatch(workflow)(5)
result_object = ct.get_result(dispatch_id, wait=True)
sub_result_object = result_object.lattice.transport_graph.get_node_value(0, "sublattice_result")

Since the sublattice does not specify an executor, it should inherit its parent lattice's executor. However, this is not what happens; the sublattice's executor is set to "local", the default executor:
print(result_object.lattice.metadata["executor"])
print(sub_result_object.lattice.metadata["executor"])

dask
local

Acceptance criteria

[ ] If a sublattice does not specify an executor, it should inherit its parent lattice's executor.
[ ] Explicit executor settings for a sublattice shall be honored.
[ ] If a top-level lattice (not a sublattice) does not specify an executor, it should use the Covalent default executor -- "local" if Covalent is started with the --no-cluster option and "dask" otherwise.
[ ] Add tests to verify executor settings for lattices and sublattices in all three of the above scenarios.

Some suggestions to start debugging:

The lattice decorator
The server's internal logic for running sublattices; see also _build_sublattice_graph.
The related issue #1284 for automatically setting electron executors.

Hello Covalent,
I am Rishabh Singh, Computer Engineer and Quantum Developer. I am interested in this issue. Skills in Quantum Computing - Qiskit, Pennylane and Cirq. Past contributions - Pennylane, Cirq, and Scikit-Learn.
Best Regards
Rishabh Singh

go for it @anonymousr007! thanks for contributing 😄

Hi @cjao , @scottwn
I have solved the issue, checked all three conditions mentioned, wrote the unit tests, and created PR. Please let me know if changes to be made.
Thanks for providing this opportunity.

Hey @RaviPsiog, can you link the PR?


[semantic-dom-diff] needs preprocessor for partial dom (like tr)

when comparing "parts" of a dom e.g. only tr of a table
expect(el.shadowRoot.querySelector('table thead')).lightDom.to.equal(`

     foo
     bar

`);

then the browser parser will say tr is not allows on it's own so these tags will be ignored and you will compare only foo\n    bar so there is missing information and the indentions are wrong..,
Possible solution:
pass on a preprocessor
expect(el.shadowRoot.querySelector('table thead')).lightDom.to.equal(`

     foo
     bar

`, { preProcessor: html => `
${html}
` });

Couldn't you just do:
const dom = el.shadowRoot.querySelector('table thead');
expect(`<table>${dom}</table>`).lightDom.to.equal(`

     foo
     bar

`);

I'm afraid no...

string + dom nodes don't mix that well (only works with lit-html => but even then we would need to render a new fixture and pass the resulting node)
.lightdom takes a dom node and not a string
the right side also gets parsed so you need "valid" browser dom there as well

I tested it adding preProcesser is like 4 lines of additional code :grimacing:
const processedHtml = typeof options.preProcessor === 'function' ? options.preProcessor(html) : html;
// then replace usage of html with processedHtml

You wouldn't use .lightDom in this case, but just .dom. get-diffable-html does support a string now: https://github.com/open-wc/open-wc/blob/master/packages/semantic-dom-diff/get-diffable-html.js#L204
So it would be:
const dom = el.shadowRoot.querySelector('table thead').innerHTML;
expect(`<table>${dom}</table>`).dom.to.equal(`

     foo
     bar

`);

But we could add a preprocessor as well I'm fine with that.


Head not rendering on main menu with MenuMobs

more info: superbas11/MenuMobs#29

This is in fact with Mo' Bends and More Player Models, and seems to be working great in the upcoming release 😄. I consider this issue as closed.

I guess this is still an issue as I am having the same problem:
https://github.com/superbas11/MenuMobs/issues/29
MoBends : 0.24
Menu Mobs: 1.21
Forge: <IP_ADDRESS>68


Trim ShortDescription and Description manifest fields

[x] Have you signed the Contributor License Agreement?
[ ] Are you working against an Issue?

This avoids the blank line after short and long descriptions in winget show when the manifest uses the
Description: >
    REAPER is a complete...

    REAPER supports...

syntax for multi-line values. See e.g. https://github.com/microsoft/winget-pkgs/blob/master/manifests/c/Cockos/REAPER/6.28/Cockos.REAPER.locale.en-US.yaml and the output of winget show reaper:
Gefunden REAPER [Cockos.REAPER]
Version: 6.28
Publisher: Cockos Incorporated
Description: REAPER is a complete digital audio production application for computers, offering a full  multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset.
REAPER supports a vast range of hardware, digital formats and plugins, and can be comprehensively extended, scripted and modified.

Homepage: https://www.reaper.fm/
License: Copyright © 2005-2021 Cockos Incorporated
Installer:
  Type: Nullsoft
  Download Url: https://www.reaper.fm/files/6.x/reaper628_x64-install.exe
  SHA256: 64560f45cec4ceca26b30d17d7f78c72503a89333ff8537864e5341b0948eb2d

Microsoft Reviewers: Open in CodeFlow

/azp run


Black meshes and broken vertices after export

I run blender 4.0.2 from steam.
I open my model, I export in gltf. After export is finished, the model is broken in view, with black parts and strange faces (see images)
Exported gltf has the same problem as the blender post export rendering. ctrl + z seems to resolve the problem in blender view.
This bug occurs even without material.
I tried quickly on another PC and strangely I had no problems.
I'm going to try to cut part of this proprietary mesh and add to the outcome to be able to reproduce as quickly as possible, if no one has an idea in the meantime already.

OS: windows 10
Blender Version 4.0.2

Hello,
Waiting a file to be able to reproduce.
If you have the same issue after rendering, the problem probably comes from your mesh, not from the glTF export.
Maybe report it on https://projects.blender.org/blender/blender will be a better place.
glTF I/O can't manage your export correctly if data are corrupts.

Confirmed that your mesh is not valid.
Check in export log :

WARNING: Mesh SM_Stone_Wall_Arc.054 is not valid, and may be exported wrongly

You can also check it by open your file, and type in blender console

bpy.context.object.data.validate()

=> Return True, indicates that the mesh is not valid, and see that your mesh is now also broken in 3D View
Closing this ticket, as we can't export correctly a not valid mesh that Blender itself is not able to manage.
Please open a Blender ticket, explaining how you generated your mesh


Use anyio in the main package instead of trio

Tests still have trio - it has more developed testing utilities, and the ASGI server we use (hypercorn) does not yet support anyio (see https://gitlab.com/pgjones/hypercorn/-/issues/183)
Fixes #13

Codecov Report

Merging #27 (94ce2b3) into master (02b62d9) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 94ce2b3 differs from pull request most recent head 7896ada. Consider uploading reports for the commit 7896ada to get more accurate results

@@            Coverage Diff            @@
##            master       #27   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          940       940
  Branches       170       170
=========================================
  Hits           940       940

Impacted Files
Coverage Δ

pons/_client.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 02b62d9...7896ada. Read the comment docs.


Remove internal Microsoft properties from public metadata

removed properties "glyphAsUtfInEmoticons" and "mappedToEmoticons" from metadata
updated repository disk requirements in README.md file

@willchavez


Login to Home assistant stopped working remotely with tailscale - was working properly for about two weeks

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)