Typing with No answer

The problem
I don't know how it happened, but it doesn't answer any of my questions. And it keeps saying typing. Here is the logs:

Version of python
3.10.7
Version of EdgeGPT-Telegram-Bot
v1.0.2 - d90e118 (git)
Operating system running EdgeGPT-Telegram-Bot
Linux
Running on your machine? Running on docker?
with nohup command
Additional information & file uploads
No response

What was the prompt?

did not work independently of prompt, then I reset and typed hello, when I typed prompt after that the problem was solved. but in case you're still wondering, it was this: "Quorum sensing nedir"

Why are you using 1.0.2? I've added lot of fixes between 1.0.2 and 1.3.0.
P.S: I don't have that problem, I've tested the same prompt without problem

Because I added a few features that are important to me, actually I update manually. I don't always have this problem either, but sometimes it's annoying when it happens, so I wanted to open an issue in case you think of something

I think this problem happens when i send multiple prompts in a row. it freezes after a while. It seems to be "writing" forever but does nothing

Does anyone else have this problem, I have this problem all the time, it's very annoying, I have to reset the bot every time, I think this is the one and only thing that bothers me the most about this bot

I think this error occurs when bing responds with things like images.

and as a result, as it seems, it no longer responds:

This is a problem with EdgeGPT. I need bot logs to at least know what was the error that crashed the bot.

Ok, I've got this error after asking for an image in the query. I'll open an Issue in EdgeGPT repo.


About FLOPs

When I print the flops of generator, there is an error. I found the 'self.attn' on line 356 is a list. In fact there are 2 attns to be calculated. How can I fix it? When I change 'self.attn' to 'self.attn[0]', the flops shows<PHONE_NUMBER>4.0 (68B), larger than 50.9B than paper.

Hi, thanks for pointing out this bug. We report the FLOPS of 1024 resolution with channel multiplier of generator set to 1, which is 46.44B after fixing the bug. And I will also update the paper in arxiv with the correct FLOPS.


New version: Wesnoth.BattleForWesnoth version 1.17.4

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.1 schema?


Themes: Consistency on name colors

Refs: #23294
Example: Foreground vs panelActiveTitleColor
The second one should also have a foreground so there is some consitency in naming

Did some renames:

panelBorderTopColor => panelTopBorder
panelActiveTitleColor => panelActiveTitleForeground
panelInactiveTitleColor => panelInactiveTitleForeground

@aeschli the only remaining inconsistent color is editorSelectionHighlightColor

Here's the current state:

activeTabActiveGroupForeground: Active tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabBackground: Active tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabInactiveGroupForeground: Active tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activityBadgeBackground: Activity notification badge background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBadgeForeground: Activity notification badge foreground color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarBackground: Activity bar background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarDragAndDropBackground: Drag and drop feedback color for the activity bar items. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
debugExceptionWidgetBackground: Exception widget background color
debugExceptionWidgetBorder: Exception widget border color
debugToolBarBackground: Debug toolbar background color.
editorActiveLinkForeground: Color of active links
editorBackground: Editor background color
editorCursor: Color of the editor cursor
editorDragAndDropBackground: Background color when dragging editors around.
editorFindMatch: Color of the current search match
editorFindMatchHighlight: Color of the other search matches
editorFindRangeHighlight: Color the range limiting the search
editorFindWidgetBackground: Find widget background
editorForeground: Editor default foreground color
editorGroupBackground: Backgrouund color of an editor group. Editor groups are the containers of editors.
editorGroupBorder: Color to separate multiple editor groups from each other. Editor groups are the containers of editors.
editorGuide: Color of the editor indentation guides.
editorHoverBackground: Background color of the editor hover.
editorHoverBorder: Border color of the editor hover.
editorHoverHighlight: Highlight below the word for which a hover is shown.
editorInactiveSelection: Color of the selection in an inactive editor
editorLineHighlight: Background color for the highlight of line at the cursor position
editorLineHighlightBorder: Background color for the border around the line at the cursor position
editorLineNumbers: Color of editor line numbers
editorLinkForeground: Color of links
editorMarkerNavigationBackground: Editor marker navigation widget background
editorMarkerNavigationError: Editor marker navigation widget error color
editorMarkerNavigationWarning: Editor marker navigation widget warning color
editorPeekBorder: Editor peek view borders
editorPeekEditorBackground: Background color of the peek view editor
editorPeekEditorMatchHighlight: Match highlight color in the peek view editor
editorPeekResultsBackground: Background color of the peek view result list
editorPeekResultsFileForeground: File entry foreground in the peek view result list
editorPeekResultsMatchForeground: Match entry foreground in the peek view result list
editorPeekResultsMatchHighlight: Match highlight color in the peek view result list
editorPeekResultsSelectedBackground: Selected entry background in the peek view result list
editorPeekResultsSelectedForeground: Selected entry foreground in the peek view result list
editorPeekTitle: Editor peek view title color
editorPeekTitleBackground: Editor peek view title area background
editorPeekTitleInfo: Editor peek view title info color
editorRangeHighlight: Background color of highlighted ranges, like by quick open and find features
editorSelection: Color of the editor selection
editorSelectionHighlight: Color for regions with the same content as the selection
editorSideBySideBorder: Border color to separate the details from the master side for side by side editors.
editorWhitespaces: Color of whitespace characters in the editor
editorWordHighlight: Background color of a symbol during read-access, like reading a variable
editorWordHighlightStrong: Background color of a symbol during write-access, like writing to a variable
focus: Overall outline/border color for focused elements. This color is only used if not overridden by a component.
foreground: Overall foreground color. This color is only used if not overridden by a component.
highContrastBorder: Border color to separate components when high contrast theme is enabled.
highContrastOutline: Outline color for active components when high contrast theme is enabled.
inactiveTabActiveGroupForeground: Inactive tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabBackground: Inactive tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabInactiveGroupForeground: Inactive tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inputActiveOptionBorder: Border color of activated options in input fields
inputBackground: Input field background
inputBorder: Input field border
inputForeground: Input field foreground
noTabsContainerBackground: Background color of the editor title container when no tabs are enabled.
panelActiveTitleBorder: Border color for the active panel title. Panels are shown below the editor area and contain views like output and integrated terminal.
panelActiveTitleForeground: Title color for the active panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelBackground: Panel background color. Panels are shown below the editor area and contain views like output and integrated terminal.
panelInactiveTitleForeground: Title color for the inactive panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelTopBorder: Panel border color on the top separating to the editor. Panels are shown below the editor area and contain views like output and integrated terminal.
selectBackground: Select field background
selectBorder: Select field border
selectForeground: Select field foreground
sideBarBackground: Side bar background color. The side bar is the container for views like explorer and search.
sideBarTitleForeground: Side bar title foreground color. The side bar is the container for views like explorer and search.
statusBarBackground: Standard status bar background color. The status bar is shown in the bottom of the window
statusBarDebuggingBackground: Status bar background color when a program is being debugged. The status bar is shown in the bottom of the window
statusBarForeground: Status bar foreground color. The status bar is shown in the bottom of the window
statusBarInfoItemBackground: Status bar info item background color. The status bar is shown in the bottom of the window
statusBarInfoItemHoverBackground: Status bar info item background color when hovering. The status bar is shown in the bottom of the window
statusBarItemActiveBackground: Status bar item background color when clicking. The status bar is shown in the bottom of the window
statusBarItemHoverBackground: Status bar item background color when hovering. The status bar is shown in the bottom of the window
statusBarNoFolderBackground: Status bar background color when no folder is opened. The status bar is shown in the bottom of the window
tabBorder: Border to separate tabs from each other. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
tabsContainerBackground: Background color of the tabs container. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
terminalAnsiBlack: 'Black' ansi color in the terminal
terminalAnsiBlue: 'Blue' ansi color in the terminal
terminalAnsiBrightBlack: 'BrightBlack' ansi color in the terminal
terminalAnsiBrightBlue: 'BrightBlue' ansi color in the terminal
terminalAnsiBrightCyan: 'BrightCyan' ansi color in the terminal
terminalAnsiBrightGreen: 'BrightGreen' ansi color in the terminal
terminalAnsiBrightMagenta: 'BrightMagenta' ansi color in the terminal
terminalAnsiBrightRed: 'BrightRed' ansi color in the terminal
terminalAnsiBrightWhite: 'BrightWhite' ansi color in the terminal
terminalAnsiBrightYellow: 'BrightYellow' ansi color in the terminal
terminalAnsiCyan: 'Cyan' ansi color in the terminal
terminalAnsiGreen: 'Green' ansi color in the terminal
terminalAnsiMagenta: 'Magenta' ansi color in the terminal
terminalAnsiRed: 'Red' ansi color in the terminal
terminalAnsiWhite: 'White' ansi color in the terminal
terminalAnsiYellow: 'Yellow' ansi color in the terminal
titleBarActiveBackground: Title bar background when the window is active. Note that this color is currently only supported on macOS.
titleBarActiveForeground: Title bar foreground when the window is active. Note that this color is currently only supported on macOS.
titleBarInactiveBackground: Title bar background when the window is inactive. Note that this color is currently only supported on macOS.
titleBarInactiveForeground: Title bar foreground when the window is inactive. Note that this color is currently only supported on macOS.

Latest list:

activeTabActiveGroupForeground: Active tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabBackground: Active tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabInactiveGroupForeground: Active tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activityBadgeBackground: Activity notification badge background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBadgeForeground: Activity notification badge foreground color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarBackground: Activity bar background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarDragAndDropBackground: Drag and drop feedback color for the activity bar items. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
debugExceptionWidgetBackground: Exception widget background color
debugExceptionWidgetBorder: Exception widget border color
debugToolBarBackground: Debug toolbar background color.
editorActiveLinkForeground: Color of active links.
editorBackground: Editor background color.
editorCursor: Color of the editor cursor.
editorDragAndDropBackground: Background color when dragging editors around.
editorFindMatch: Color of the current search match.
editorFindMatchHighlight: Color of the other search matches.
editorFindRangeHighlight: Color the range limiting the search.
editorFindWidgetBackground: Find widget background.
editorForeground: Editor default foreground color.
editorGroupBackground: Background color of an editor group. Editor groups are the containers of editors.
editorGroupBorder: Color to separate multiple editor groups from each other. Editor groups are the containers of editors.
editorHoverBackground: Background color of the editor hover.
editorHoverBorder: Border color of the editor hover.
editorHoverHighlight: Highlight below the word for which a hover is shown.
editorInactiveSelection: Color of the selection in an inactive editor.
editorIndentGuides: Color of the editor indentation guides.
editorLineHighlight: Background color for the highlight of line at the cursor position.
editorLineHighlightBorder: Background color for the border around the line at the cursor position.
editorLineNumbers: Color of editor line numbers.
editorLinkForeground: Color of links.
editorMarkerNavigationBackground: Editor marker navigation widget background
editorMarkerNavigationError: Editor marker navigation widget error color
editorMarkerNavigationWarning: Editor marker navigation widget warning color
editorRangeHighlight: Background color of highlighted ranges, like by quick open and find features.
editorSelection: Color of the editor selection.
editorSelectionHighlight: Color for regions with the same content as the selection.
editorSideBySideBorder: Border color to separate the details from the master side for side by side editors.
editorWhitespaces: Color of whitespace characters in the editor.
editorWordHighlight: Background color of a symbol during read-access, like reading a variable
editorWordHighlightStrong: Background color of a symbol during write-access, like writing to a variable
focus: Overall outline/border color for focused elements. This color is only used if not overridden by a component.
foreground: Overall foreground color. This color is only used if not overridden by a component.
highContrastBorder: Border color to separate components when high contrast theme is enabled.
highContrastOutline: Outline color for active components when high contrast theme is enabled.
inactiveTabActiveGroupForeground: Inactive tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabBackground: Inactive tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabInactiveGroupForeground: Inactive tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inputActiveOptionBorder: Border color of activated options in input fields.
inputBackground: Input field background.
inputBorder: Input field border.
inputForeground: Input field foreground.
noTabsContainerBackground: Background color of the editor title container when no tabs are enabled.
panelActiveTitleBorder: Border color for the active panel title. Panels are shown below the editor area and contain views like output and integrated terminal.
panelActiveTitleForeground: Title color for the active panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelBackground: Panel background color. Panels are shown below the editor area and contain views like output and integrated terminal.
panelInactiveTitleForeground: Title color for the inactive panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelTopBorder: Panel border color on the top separating to the editor. Panels are shown below the editor area and contain views like output and integrated terminal.
peekViewBorder: Color of the peek view borders and arrow
peekViewEditorBackground: Background color of the peek view editor.
peekViewEditorMatchHighlight: Match highlight color in the peek view editor.
peekViewResultsBackground: Background color of the peek view result list.
peekViewResultsFileForeground: File entry foreground in the peek view result list.
peekViewResultsMatchForeground: Match entry foreground in the peek view result list.
peekViewResultsMatchHighlight: Match highlight color in the peek view result list.
peekViewResultsSelectionBackground: Background color of the selected entry in the peek view result list.
peekViewResultsSelectionForeground: Foreground color of the selected entry in the peek view result list.
peekViewTitle: Color of the peek view title.
peekViewTitleBackground: Background color of the peek view title area.
peekViewTitleInfo: Color of the peek view title info.
selectBackground: Select field background.
selectBorder: Select field border.
selectForeground: Select field foreground.
sideBarBackground: Side bar background color. The side bar is the container for views like explorer and search.
sideBarTitleForeground: Side bar title foreground color. The side bar is the container for views like explorer and search.
statusBarBackground: Standard status bar background color. The status bar is shown in the bottom of the window
statusBarDebuggingBackground: Status bar background color when a program is being debugged. The status bar is shown in the bottom of the window
statusBarForeground: Status bar foreground color. The status bar is shown in the bottom of the window
statusBarInfoItemBackground: Status bar info item background color. The status bar is shown in the bottom of the window
statusBarInfoItemHoverBackground: Status bar info item background color when hovering. The status bar is shown in the bottom of the window
statusBarItemActiveBackground: Status bar item background color when clicking. The status bar is shown in the bottom of the window
statusBarItemHoverBackground: Status bar item background color when hovering. The status bar is shown in the bottom of the window
statusBarNoFolderBackground: Status bar background color when no folder is opened. The status bar is shown in the bottom of the window
tabBorder: Border to separate tabs from each other. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
tabsContainerBackground: Background color of the tabs container. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
terminalAnsiBlack: 'Black' ansi color in the terminal
terminalAnsiBlue: 'Blue' ansi color in the terminal
terminalAnsiBrightBlack: 'BrightBlack' ansi color in the terminal
terminalAnsiBrightBlue: 'BrightBlue' ansi color in the terminal
terminalAnsiBrightCyan: 'BrightCyan' ansi color in the terminal
terminalAnsiBrightGreen: 'BrightGreen' ansi color in the terminal
terminalAnsiBrightMagenta: 'BrightMagenta' ansi color in the terminal
terminalAnsiBrightRed: 'BrightRed' ansi color in the terminal
terminalAnsiBrightWhite: 'BrightWhite' ansi color in the terminal
terminalAnsiBrightYellow: 'BrightYellow' ansi color in the terminal
terminalAnsiCyan: 'Cyan' ansi color in the terminal
terminalAnsiGreen: 'Green' ansi color in the terminal
terminalAnsiMagenta: 'Magenta' ansi color in the terminal
terminalAnsiRed: 'Red' ansi color in the terminal
terminalAnsiWhite: 'White' ansi color in the terminal
terminalAnsiYellow: 'Yellow' ansi color in the terminal
titleBarActiveBackground: Title bar background when the window is active. Note that this color is currently only supported on macOS.
titleBarActiveForeground: Title bar foreground when the window is active. Note that this color is currently only supported on macOS.
titleBarInactiveBackground: Title bar background when the window is inactive. Note that this color is currently only supported on macOS.
titleBarInactiveForeground: Title bar foreground when the window is inactive. Note that this color is currently only supported on macOS.

activeTabActiveGroupForeground: Active tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabBackground: Active tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabInactiveGroupForeground: Active tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activityBadgeBackground: Activity notification badge background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBadgeForeground: Activity notification badge foreground color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarBackground: Activity bar background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarDragAndDropBackground: Drag and drop feedback color for the activity bar items. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
debugExceptionWidgetBackground: Exception widget background color.
debugExceptionWidgetBorder: Exception widget border color.
debugToolBarBackground: Debug toolbar background color.
editorActiveLinkForeground: Color of active links.
editorBackground: Editor background color.
editorCursor: Color of the editor cursor.
editorDragAndDropBackground: Background color when dragging editors around.
editorFindMatch: Color of the current search match.
editorFindMatchHighlight: Color of the other search matches.
editorFindRangeHighlight: Color the range limiting the search.
editorFindWidgetBackground: Find widget background.
editorForeground: Editor default foreground color.
editorGroupBackground: Background color of an editor group. Editor groups are the containers of editors.
editorGroupBorder: Color to separate multiple editor groups from each other. Editor groups are the containers of editors.
editorHoverBackground: Background color of the editor hover.
editorHoverBorder: Border color of the editor hover.
editorHoverHighlight: Highlight below the word for which a hover is shown.
editorInactiveSelection: Color of the selection in an inactive editor.
editorIndentGuides: Color of the editor indentation guides.
editorLineHighlight: Background color for the highlight of line at the cursor position.
editorLineHighlightBorder: Background color for the border around the line at the cursor position.
editorLineNumbers: Color of editor line numbers.
editorLinkForeground: Color of links.
editorMarkerNavigationBackground: Editor marker navigation widget background.
editorMarkerNavigationError: Editor marker navigation widget error color.
editorMarkerNavigationWarning: Editor marker navigation widget warning color.
editorRangeHighlight: Background color of highlighted ranges, like by quick open and find features.
editorSelection: Color of the editor selection.
editorSelectionHighlight: Color for regions with the same content as the selection.
editorSideBySideBorder: Border color to separate the details from the master side for side by side editors.
editorWhitespaces: Color of whitespace characters in the editor.
editorWordHighlight: Background color of a symbol during read-access, like reading a variable.
editorWordHighlightStrong: Background color of a symbol during write-access, like writing to a variable.
focus: Overall outline/border color for focused elements. This color is only used if not overridden by a component.
foreground: Overall foreground color. This color is only used if not overridden by a component.
highContrastBorder: Border color to separate components when high contrast theme is enabled.
highContrastOutline: Outline color for active components when high contrast theme is enabled.
inactiveTabActiveGroupForeground: Inactive tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabBackground: Inactive tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabInactiveGroupForeground: Inactive tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inputActiveOptionBorder: Border color of activated options in input fields.
inputBackground: Input field background.
inputBorder: Input field border.
inputForeground: Input field foreground.
noTabsContainerBackground: Background color of the editor title container when no tabs are enabled.
panelActiveTitleBorder: Border color for the active panel title. Panels are shown below the editor area and contain views like output and integrated terminal.
panelActiveTitleForeground: Title color for the active panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelBackground: Panel background color. Panels are shown below the editor area and contain views like output and integrated terminal.
panelInactiveTitleForeground: Title color for the inactive panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelTopBorder: Panel border color on the top separating to the editor. Panels are shown below the editor area and contain views like output and integrated terminal.
peekViewBorder: Color of the peek view borders and arrow
peekViewEditorBackground: Background color of the peek view editor.
peekViewEditorMatchHighlight: Match highlight color in the peek view editor.
peekViewResultsBackground: Background color of the peek view result list.
peekViewResultsFileForeground: File entry foreground in the peek view result list.
peekViewResultsMatchForeground: Match entry foreground in the peek view result list.
peekViewResultsMatchHighlight: Match highlight color in the peek view result list.
peekViewResultsSelectionBackground: Background color of the selected entry in the peek view result list.
peekViewResultsSelectionForeground: Foreground color of the selected entry in the peek view result list.
peekViewTitle: Color of the peek view title.
peekViewTitleBackground: Background color of the peek view title area.
peekViewTitleInfo: Color of the peek view title info.
selectBackground: Select field background.
selectBorder: Select field border.
selectForeground: Select field foreground.
sideBarBackground: Side bar background color. The side bar is the container for views like explorer and search.
sideBarTitleForeground: Side bar title foreground color. The side bar is the container for views like explorer and search.
statusBarBackground: Standard status bar background color. The status bar is shown in the bottom of the window.
statusBarDebuggingBackground: Status bar background color when a program is being debugged. The status bar is shown in the bottom of the window
statusBarForeground: Status bar foreground color. The status bar is shown in the bottom of the window.
statusBarInfoItemBackground: Status bar info item background color. The status bar is shown in the bottom of the window.
statusBarInfoItemHoverBackground: Status bar info item background color when hovering. The status bar is shown in the bottom of the window.
statusBarItemActiveBackground: Status bar item background color when clicking. The status bar is shown in the bottom of the window.
statusBarItemHoverBackground: Status bar item background color when hovering. The status bar is shown in the bottom of the window.
statusBarNoFolderBackground: Status bar background color when no folder is opened. The status bar is shown in the bottom of the window.
tabBorder: Border to separate tabs from each other. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
tabsContainerBackground: Background color of the tabs container. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
terminalAnsiBlack: 'Black' ansi color in the terminal.
terminalAnsiBlue: 'Blue' ansi color in the terminal.
terminalAnsiBrightBlack: 'BrightBlack' ansi color in the terminal.
terminalAnsiBrightBlue: 'BrightBlue' ansi color in the terminal.
terminalAnsiBrightCyan: 'BrightCyan' ansi color in the terminal.
terminalAnsiBrightGreen: 'BrightGreen' ansi color in the terminal.
terminalAnsiBrightMagenta: 'BrightMagenta' ansi color in the terminal.
terminalAnsiBrightRed: 'BrightRed' ansi color in the terminal.
terminalAnsiBrightWhite: 'BrightWhite' ansi color in the terminal.
terminalAnsiBrightYellow: 'BrightYellow' ansi color in the terminal.
terminalAnsiCyan: 'Cyan' ansi color in the terminal.
terminalAnsiGreen: 'Green' ansi color in the terminal.
terminalAnsiMagenta: 'Magenta' ansi color in the terminal.
terminalAnsiRed: 'Red' ansi color in the terminal.
terminalAnsiWhite: 'White' ansi color in the terminal.
terminalAnsiYellow: 'Yellow' ansi color in the terminal.
titleBarActiveBackground: Title bar background when the window is active. Note that this color is currently only supported on macOS.
titleBarActiveForeground: Title bar foreground when the window is active. Note that this color is currently only supported on macOS.
titleBarInactiveBackground: Title bar background when the window is inactive. Note that this color is currently only supported on macOS.
titleBarInactiveForeground: Title bar foreground when the window is inactive. Note that this color is currently only supported on macOS.

Latest ids:

activeTabActiveGroupForeground: Active tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabBackground: Active tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activeTabInactiveGroupForeground: Active tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
activityBadgeBackground: Activity notification badge background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBadgeForeground: Activity notification badge foreground color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarBackground: Activity bar background color. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
activityBarDragAndDropBackground: Drag and drop feedback color for the activity bar items. The activity bar is showing on the far left or right and allows to switch between views of the side bar.
debugExceptionWidgetBackground: Exception widget background color.
debugExceptionWidgetBorder: Exception widget border color.
debugToolBarBackground: Debug toolbar background color.
dropdownBackground: Dropdown background.
dropdownBorder: Dropdown border.
dropdownForeground: Dropdown foreground.
editorActiveLinkForeground: Color of active links.
editorBackground: Editor background color.
editorCursor: Color of the editor cursor.
editorDragAndDropBackground: Background color when dragging editors around.
editorFindMatch: Color of the current search match.
editorFindMatchHighlight: Color of the other search matches.
editorFindRangeHighlight: Color the range limiting the search.
editorFindWidgetBackground: Find widget background.
editorForeground: Editor default foreground color.
editorGroupBackground: Background color of an editor group. Editor groups are the containers of editors.
editorGroupBorder: Color to separate multiple editor groups from each other. Editor groups are the containers of editors.
editorHeaderBackground: Background color of the editor title header when no tabs are enabled.
editorHoverBackground: Background color of the editor hover.
editorHoverBorder: Border color of the editor hover.
editorHoverHighlight: Highlight below the word for which a hover is shown.
editorInactiveSelection: Color of the selection in an inactive editor.
editorIndentGuides: Color of the editor indentation guides.
editorLineHighlight: Background color for the highlight of line at the cursor position.
editorLineHighlightBorder: Background color for the border around the line at the cursor position.
editorLineNumbers: Color of editor line numbers.
editorLinkForeground: Color of links.
editorMarkerNavigationBackground: Editor marker navigation widget background.
editorMarkerNavigationError: Editor marker navigation widget error color.
editorMarkerNavigationWarning: Editor marker navigation widget warning color.
editorRangeHighlight: Background color of highlighted ranges, like by quick open and find features.
editorSelection: Color of the editor selection.
editorSelectionHighlight: Color for regions with the same content as the selection.
editorSideBySideBorder: Border color to separate the details from the master side for side by side editors.
editorWhitespaces: Color of whitespace characters in the editor.
editorWordHighlight: Background color of a symbol during read-access, like reading a variable.
editorWordHighlightStrong: Background color of a symbol during write-access, like writing to a variable.
focusedElementOutline: Overall outline/border color for focused elements. This color is only used if not overridden by a component.
foreground: Overall foreground color. This color is only used if not overridden by a component.
highContrastBorder: Border color to separate components when high contrast theme is enabled.
highContrastOutline: Outline color for active components when high contrast theme is enabled.
inactiveTabActiveGroupForeground: Inactive tab foreground color in an active group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabBackground: Inactive tab background color. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inactiveTabInactiveGroupForeground: Inactive tab foreground color in an inactive group. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
inputBoxActiveOptionBorder: Border color of activated options in input fields.
inputBoxBackground: Input box background.
inputBoxBorder: Input box border.
inputBoxForeground: Input box foreground.
panelActiveTitleBorder: Border color for the active panel title. Panels are shown below the editor area and contain views like output and integrated terminal.
panelActiveTitleForeground: Title color for the active panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelBackground: Panel background color. Panels are shown below the editor area and contain views like output and integrated terminal.
panelInactiveTitleForeground: Title color for the inactive panel. Panels are shown below the editor area and contain views like output and integrated terminal.
panelTopBorder: Panel border color on the top separating to the editor. Panels are shown below the editor area and contain views like output and integrated terminal.
peekViewBorder: Color of the peek view borders and arrow.
peekViewEditorBackground: Background color of the peek view editor.
peekViewEditorMatchHighlight: Match highlight color in the peek view editor.
peekViewResultsBackground: Background color of the peek view result list.
peekViewResultsFileForeground: File entry foreground in the peek view result list.
peekViewResultsMatchForeground: Match entry foreground in the peek view result list.
peekViewResultsMatchHighlight: Match highlight color in the peek view result list.
peekViewResultsSelectionBackground: Background color of the selected entry in the peek view result list.
peekViewResultsSelectionForeground: Foreground color of the selected entry in the peek view result list.
peekViewTitle: Color of the peek view title.
peekViewTitleBackground: Background color of the peek view title area.
peekViewTitleInfo: Color of the peek view title info.
sideBarBackground: Side bar background color. The side bar is the container for views like explorer and search.
sideBarTitleForeground: Side bar title foreground color. The side bar is the container for views like explorer and search.
statusBarBackground: Standard status bar background color. The status bar is shown in the bottom of the window.
statusBarDebuggingBackground: Status bar background color when a program is being debugged. The status bar is shown in the bottom of the window
statusBarForeground: Status bar foreground color. The status bar is shown in the bottom of the window.
statusBarInfoItemBackground: Status bar info item background color. The status bar is shown in the bottom of the window.
statusBarInfoItemHoverBackground: Status bar info item background color when hovering. The status bar is shown in the bottom of the window.
statusBarItemActiveBackground: Status bar item background color when clicking. The status bar is shown in the bottom of the window.
statusBarItemHoverBackground: Status bar item background color when hovering. The status bar is shown in the bottom of the window.
statusBarNoFolderBackground: Status bar background color when no folder is opened. The status bar is shown in the bottom of the window.
tabBorder: Border to separate tabs from each other. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
tabsContainerBackground: Background color of the tabs container. Tabs are the containers for editors in the editor area. Multiple tabs can be opened in one editor group. There can be multiple editor groups.
terminalAnsiBlack: 'Black' ansi color in the terminal.
terminalAnsiBlue: 'Blue' ansi color in the terminal.
terminalAnsiBrightBlack: 'BrightBlack' ansi color in the terminal.
terminalAnsiBrightBlue: 'BrightBlue' ansi color in the terminal.
terminalAnsiBrightCyan: 'BrightCyan' ansi color in the terminal.
terminalAnsiBrightGreen: 'BrightGreen' ansi color in the terminal.
terminalAnsiBrightMagenta: 'BrightMagenta' ansi color in the terminal.
terminalAnsiBrightRed: 'BrightRed' ansi color in the terminal.
terminalAnsiBrightWhite: 'BrightWhite' ansi color in the terminal.
terminalAnsiBrightYellow: 'BrightYellow' ansi color in the terminal.
terminalAnsiCyan: 'Cyan' ansi color in the terminal.
terminalAnsiGreen: 'Green' ansi color in the terminal.
terminalAnsiMagenta: 'Magenta' ansi color in the terminal.
terminalAnsiRed: 'Red' ansi color in the terminal.
terminalAnsiWhite: 'White' ansi color in the terminal.
terminalAnsiYellow: 'Yellow' ansi color in the terminal.
titleBarActiveBackground: Title bar background when the window is active. Note that this color is currently only supported on macOS.
titleBarActiveForeground: Title bar foreground when the window is active. Note that this color is currently only supported on macOS.
titleBarInactiveBackground: Title bar background when the window is inactive. Note that this color is currently only supported on macOS.
titleBarInactiveForeground: Title bar foreground when the window is inactive. Note that this color is currently only supported on macOS.


Realm with Mapper

Hi,
I am trying to use Mappable with Realms object. Previously, I had struct and it was subclassed from the Mappable and I implemented init function. For Realm, I converted my struct to class and conform Object protocol. Now issue is, our model contains optional Int? but in Realm Optional Int can be defined by 'RealmOptional; but when change type, I start getting errors in Mapper init function since that type is unknown to the compiler. Can you please send me any example how to use it with Mapper?
Thanks,
Amir

anyone guys? @mleventi

@keith

It sounds like you'll need to create a custom transformation function, or make RealmOptional conform to Convertible to make this work. Can you post an abridge example of your class and struct?

Feel free to submit a new issue if this is still a problem!


Show Only Installed Apps

I'm not sure if I've missed this in the app.
It would be convenient to have a toggle to show only the installed apps.

:) Done.


[Discussion] Could the help text for the VNet create command be a little clearer?

Could the behavior of the az network vnet create command's --subnet-prefix parameter be clarified any further? It's help text states that it will reserve a portion of the vnet's address space, but in my experience, it seems to use the following specific heuristic: <vnet-prefix>/max(24, <vnet-cidr-block>).
Maybe the behavior isn't this simple, but if it is, it would be cool if the help text stated this, that way a user would know exactly when they do or don't need to explicitly set it (e.g. If omitted, automatically reserves a /24 (or as large as available) block within the VNet address space, .).
This isn't that high-pri, and maybe I'm just being nit-picky, but I had to try the az network vnet create command with and without the --subnet-prefix parameter in order to see how it worked.

You are absolutely correct--that's what it does. I'll update the help with your recommended wording. Thanks for the feedback!


Remove styleResizable

Resolves #43

@wtgtybhertgeghgtwtg I looked at the source code of style resizeable and it has this:
var hasWarned = void 0;
var warn = function warn() {
  process.env.NODE_ENV !== "production" ? (0, _warning2.default)(hasWarned, 'The \'material-ui/utils/styleResizable.js\' mixin has been deprecated.' + ' Please do not use this mixin as it will be removed in an upcoming release.') : void 0;
  hasWarned = true;
};

I am not on board with using it instead of withWidth, since both in the thread on github, as well as in the code, the MUI team indicates that it will be deprecated.
Am I missing something?

This PR did use withWidth over styleResizable.  But it's been resolved anyway, so I'm closing this PR.

Sorry about the confusion, I must have read it wrong :(


Whenever I am visiting a detail page of a record and start editing, superfluous information becomes less prominent.

Story
Whenever I am visiting a detail page of a record and start editing, superfluous information becomes less prominent.
Success criteria

[ ] The vertical scrollable space on my page takes up the most prominent space when editing.
[ ] I still have a few indicators left that show me where I am in a subtle way.
[ ] I can still execute the most prominent actions (publishing, saving, navigating ...)
[ ] The focus lies on the task at hand: editing (and actions).

Open questions
It works, but there is a small bug. TBD.

Probably when using the window height, defined with the "vh" css element – we can calculate the minimum height. Vanilla JS would work best.

Design will be reviewed in a different round, now there not a lot of info at the top anyways.


[Storage File Share] CodeGen Bug - isXML: true vs isXML: false

Issue

Autorest generated code has isXML: true for createPermissionOperationSpec as opposed to the expected isXML: false.
Had to manually revert this specific change.
(Both with the Xstore swagger and the unified swagger)

Reference

https://github.com/Azure/azure-sdk-for-js/pull/6032#discussion_r342782823

To do

Either fix the swagger/autorest and get the expected isXML: false
Or add a transform in the swagger/readme if possible
Or update the generated code

/cc - @jeremymeng @XiaoningLiu @willmtemple @joheredi

The related autorest plugin issue: https://github.com/Azure/autorest.typescript/issues/465

Closing this.  Before the autorest.typescript issue is fixed, there isn't anything we could do other than manual patch the generated code.

@jeremymeng Do we have any comments/records for this manually fix after every generation? Especially for new devs.


nz-tree case insenstive search

What problem does this feature solve?
Currently nzSearchValue of nz-tree only search case sensitive value, case insensitive search would be more convenient
 <nz-tree
      [nzData]="nodes"
      [nzSearchValue]="searchValue"
      (nzClick)="nzEvent($event)"
      (nzExpandChange)="nzEvent($event)"
      (nzSearchValueChange)="nzEvent($event)"
    >
    </nz-tree>

What does the proposed API look like?
 <nz-tree
      [nzData]="nodes"
      [nzSearchValue]="searchValue"
      [nzSearchCaseSentitive]="false"
      (nzClick)="nzEvent($event)"
      (nzExpandChange)="nzEvent($event)"
      (nzSearchValueChange)="nzEvent($event)"
    >
    </nz-tree>

Has PR in https://github.com/NG-ZORRO/ng-zorro-antd/pull/4498

close via #4869


Update ubuntu VMImage to ubuntu-20.04

Should resolve https://github.com/Azure/azure-sdk-tools/issues/1321

This only resolves a small part of #1321. The larger work item is to move everything across all our repos.


Can you make peer to peer call example this is not working for me in latest version of flutter.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@maheshbhattaraai please share here the output for command flutter doctor

Its working now. But we call from the website(one user) to mobile app(another user) call can not be initiated .


Specific song not recognized despite being recognized in earlier spotdl versions

System OS
Windows
Python Version
3.11 (CPython)
Install Source
pip / PyPi
Install version / commit hash
v4.1.2
Expected Behavior vs Actual Behavior
For the song to be recognized, downloaded, & not produce an error
Steps to reproduce - Ensure to include actual links!
Run:
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e

Traceback
Processing query: https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
LookupError: No results found for song: Kado - Tired Eyes'

Other details
The song is available on Youtube Music at https://music.youtube.com/watch?v=DKu9fWMpK3A

Hi @Forever-A-Hermit, make sure YouTube Music is available for your IP address (area). I got the same problem you described. Following the YouTube Music song link you posted I got the YouTube Music is not available in your area fallback page. Switching a VPN service on with a proper IP address fixed the issue – successfully downloaded the song you mentioned.

YouTube Music is available for my IP address & I can properly listen to the song manually at the specified YouTube URL without using a VPN. I can also download additional songs in my Spotify playlist using the 'sync' command, just not this one. Is it possible something went wrong in my '{filename}.spotdl' file?

Hard to tell what's wrong with your particular setup. But my experience with your song URL on a freshly cloned project on macOS is like:

Is it possible something went wrong in my '{filename}.spotdl' file?

I guess that was silly for me to say, as I can't even get it to work with just the download command.
I uninstalled spotdl using this to start fresh:
pip uninstall spotdl
Found existing installation: spotdl 4.1.2 Uninstalling spotdl-4.1.2:   Would remove:     c:\users\name\appdata\local\programs\python\python311\lib\site-packages\spotdl-4.1.2.dist-info\*     c:\users\name\appdata\local\programs\python\python311\lib\site-packages\spotdl\*     c:\users\name\appdata\local\programs\python\python311\scripts\spotdl.exe Proceed (Y/n)? Y
Successfully uninstalled spotdl-4.1.2
Reinstalled using this:
pip install spotdl
Successfully installed spotdl-4.1.2
Then, once again, ran:
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Issue persists.
Screenshot of Youtube Music URL https://music.youtube.com/watch?v=DKu9fWMpK3A without using a VPN:

Youtube search results aren't consistent, and can vary across different countries. They can even change even after sending the exact same search request.
That's why some song can be found and some can not.
I will try to patch this for the next release.

spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e

Works fine for me Polish IP, try using vpn with US IP

What's interesting, & I didn't even realize it until now, is that the song downloaded in earlier spotdl versions had a  very weak match on Youtube Music--almost as if the old song was an original (audibly slower) & the one on Spotify now that I linked to is a remix/updated copy.
I cannot test with a US VPN currently, unfortunately. I'm from the US, though.

Should be fixed in v4.1.4

Should be fixed in v4.1.4

Issue persists.
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Processing query: https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
LookupError: No results found for song: Kado - Tired Eyes

spotdl -v
4.1.4

Should I try with a VPN now, or would that be rather pointless?

Yeah you can give it a try

From USA VPN, which fails
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Processing query: https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Failed to get results for Tired Eyes - Kado, Powfu, Promoting Sounds, vict molina: Expecting value: line 1 column 1
(char 0)
LookupError: No results found for song: Kado - Tired Eyes

From Poland VPN, which works, but with errors
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Processing query: https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Failed to get results for Tired Eyes - Kado, Powfu, Promoting Sounds, vict molina: Expecting value: line 1 column 1
(char 0)
Downloaded "Kado - Tired Eyes": https://www.youtube.com/watch?v=DKu9fWMpK3A

From USA VPN, which fails
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Processing query: https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Failed to get results for Tired Eyes - Kado, Powfu, Promoting Sounds, vict molina: Expecting value: line 1 column 1
(char 0)
LookupError: No results found for song: Kado - Tired Eyes

From Poland VPN, which works, but with errors
spotdl download https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Processing query: https://open.spotify.com/track/0MSLJOWljfQr067PYyndK9?si=259dacb8a475409e
Failed to get results for Tired Eyes - Kado, Powfu, Promoting Sounds, vict molina: Expecting value: line 1 column 1
(char 0)
Downloaded "Kado - Tired Eyes": https://www.youtube.com/watch?v=DKu9fWMpK3A

Can you upload more logs with --log-level DEBUG? I haven't seen this error before o.O

Not sure if I should've used Pastebin or similar software, but here is the log file output here.
[09:57:16] DEBUG    MainThread - Downloader settings:         downloader.py:114
                    {'audio_providers': ['youtube-music'],
                    'lyrics_providers': ['genius',
                    'azlyrics', 'musixmatch'],
                    'playlist_numbering': False,
                    'scan_for_songs': False, 'm3u': None,
                    'output': '{artists} -
                    {title}.{output-ext}', 'overwrite':
                    'skip', 'search_query': None, 'ffmpeg':
                    'ffmpeg', 'bitrate': None, 'ffmpeg_args':
                    None, 'format': 'mp3', 'save_file': None,
                    'filter_results': True, 'threads': 4,
                    'cookie_file': None, 'restrict': False,
                    'print_errors': False, 'sponsor_block':
                    False, 'preload': False, 'archive': None,
                    'load_config': True, 'log_level':
                    'DEBUG', 'simple_tui': False,
                    'fetch_albums': False, 'id3_separator':
                    '/', 'ytm_data': False,
                    'add_unavailable': False, 'geo_bypass':
                    False, 'generate_lrc': False,
                    'force_update_metadata': False}
[09:57:16] DEBUG    MainThread - FFmpeg path: ffmpeg          downloader.py:132
[09:57:16] DEBUG    MainThread - Found 0 known songs          downloader.py:157
[09:57:19] DEBUG    MainThread - Archive: 0 urls              downloader.py:192
[09:57:19] DEBUG    MainThread - Downloader initialized       downloader.py:194
[09:57:19] INFO     MainThread - Processing query:                search.py:123
                    https://open.spotify.com/track/0MSLJOWljfQr06
                    7PYyndK9?si=259dacb8a475409e
[09:57:19] DEBUG    MainThread - Found 1 songs in 0 lists         search.py:249
[09:57:19] DEBUG    MainThread - Downloading 1 songs          downloader.py:241
[09:57:20] ERROR    asyncio_0 - Failed to get results for Tired Eyes base.py:82
                    - Kado, Powfu, Promoting Sounds, vict molina:
                    Expecting value: line 1 column 1 (char 0)
[09:57:20] DEBUG    asyncio_0 - Genius failed to find lyrics  downloader.py:358
                    for Kado - Tired Eyes
[09:57:20] DEBUG    asyncio_0 - AzLyrics failed to find       downloader.py:358
                    lyrics for Kado - Tired Eyes
[09:57:20] DEBUG    asyncio_0 - MusixMatch failed to find     downloader.py:358
                    lyrics for Kado - Tired Eyes
[09:57:20] DEBUG    asyncio_0 - No lyrics found for Kado -    downloader.py:482
                    Tired Eyes, lyrics providers: Genius,
                    AzLyrics, MusixMatch
[09:57:20] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] Searching  base.py:163
                    for kado, powfu, promoting sounds, vict molina
                    - tired eyes
[09:57:21] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] Found 0    base.py:175
                    results for ISRC SE6QE2296773
[09:57:22] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] Found 60   base.py:210
                    results for search query kado, powfu, promoting
                    sounds, vict molina - tired eyes with options
                    {'filter': 'songs', 'ignore_spelling': True,
                    'limit': 50}
[09:57:22] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] Filtered   base.py:241
                    to 0 results
[09:57:22] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] Found 31   base.py:210
                    results for search query kado, powfu, promoting
                    sounds, vict molina - tired eyes with options
                    {'filter': 'videos', 'ignore_spelling': True,
                    'limit': 50}
[09:57:22] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] Filtered   base.py:241
                    to 0 results
[09:57:22] DEBUG    asyncio_0 - [0MSLJOWljfQr067PYyndK9] No results base.py:271
                    found
[09:57:22] DEBUG    asyncio_0 - YouTubeMusic failed to find   downloader.py:334
                    Kado - Tired Eyes
[09:57:22] ERROR    asyncio_0 - Traceback (most recent  progress_handler.py:358
                    call last):
                      File
                    "C:\Users\chad\AppData\Local\Progra
                    ms\Python\Python311\Lib\site-packag
                    es\spotdl\download\downloader.py",
                    line 541, in search_and_download
                        download_url =
                    self.search(song)
                                       ^^^^^^^^^^^^^^^^
                    ^
                      File
                    "C:\Users\chad\AppData\Local\Progra
                    ms\Python\Python311\Lib\site-packag
                    es\spotdl\download\downloader.py",
                    line 336, in search
                        raise LookupError(f"No results
                    found for song:
                    {song.display_name}")
                    LookupError: No results found for
                    song: Kado - Tired Eyes

                    +- Traceback (most recent call la-+
                    | C:\Users\chad\AppData\Local\Pro |
                    | grams\Python\Python311\Lib\site |
                    | -packages\spotdl\download\downl |
                    | oader.py:541 in                 |
                    | search_and_download             |
                    |                                 |
                    |   538                           |
                    |   539         try:              |
                    |   540             if song.downl |
                    | > 541                 download_ |
                    |   542             else:         |
                    |   543                 download_ |
                    |   544                           |
                    |                                 |
                    | C:\Users\chad\AppData\Local\Pro |
                    | grams\Python\Python311\Lib\site |
                    | -packages\spotdl\download\downl |
                    | oader.py:336 in search          |
                    |                                 |
                    |   333                           |
                    |   334             logger.debug( |
                    |   335                           |
                    | > 336         raise LookupError |
                    |   337                           |
                    |   338     def search_lyrics(sel |
                    |   339         """               |
                    +---------------------------------+
                    LookupError: No results found for
                    song: Kado - Tired Eyes

Failed to get results for Tired Eyes - Kado, Powfu, Promoting Sounds, vict molina: Expecting value: line 1 column 1
(char 0)

I meant this one Failed to get results for Tired Eyes - Kado, Powfu, Promoting Sounds, vict molina: Expecting value: line 1 column 1 (char 0) (Poland VPN)

I cannot reproduce the error using a Poland VPN.

I have the exact same problem so should I mix and match vpns and check if some of them work

I have the exact same problem so should I mix and match vpns and check if some of them work

For now that's the best option

That was a debug log indicating that the lyrics provider failed to get the lyrics. You won't see it again.

Ah, it seems like you're right. I got the error message to appear again using a Poland VPN, but the file downloaded just fine.
Poland VPN debug log:
https://privatebin.net/?37b4d4e4d0476584#caAFyYTFPCznEaKz4e4ef9J3QBzj5cotgdR8R4CsVEK
I guess the VPN option will have to do for now. Hopefully this is able to be resolved in future versions, but it's such a rare occurrence that I can't complain much. Thank you for all your support on this. I really appreciate it.

I guess the VPN hopping option will have to do for now regarding audio download completion. Hopefully this is able to be resolved in future versions, but it's such a rare occurrence that I can't complain much. Thank you for all your support on this. I really appreciate it.

Let's pray that youtube finally fixes their shitty search results


Feature request: activate otter in LaTeX math blocks

Was wondering if it would be possible to activate otter when you are either in:
$$
...
$$

or
This is my equation:

\begin{...}
...
\begin{...}

Not yet, but a couple of days ago the markdown treesitter grammar got support for latex chunks (https://github.com/MDeiml/tree-sitter-markdown/commit/7e7aa9a25ca9729db9fe22912f8f47bdb403a979). This will make it straightforward to write a query to get the latex content. But in order to use that I will have to make some internal changes in https://github.com/jmbuhr/otter.nvim/blob/8b46caf113918c26a9247031d6482709078ec907/lua/otter/keeper.lua#L20
because right now it only supports one query per buffer and that captures both the language and the content (e.g. a code chunk in markdown).
That being said, if you are just after completion for math symbols I find that it is convenient to enable them for the whole document anyways, so there is not need for a separate treatment of math blocks. Here are some examples: https://www.youtube.com/watch?v=Lc_kMYVIS5I

This should be solved with the latest update that can use injections to find code chunks.

@jmbuhr do you have a sample configuration? I can't get this to work :/


使用docker部署到本地服务器，如何做到整个团队共享哦，谢谢

使用docker部署到本地服务器，如何做到整个团队共享哦，前段时间部署服务器上，自己试用一下，几天后打开发现没有当时建的项目了，其他团队成员进去也看不到，请问是部署的原因还是什么的哦，谢谢!

目前数据信息是保存在操作者的浏览器的indexedDB中的，这个无法共享。

也希望有这个功能，可以团队共享

感谢支持，目前在考虑开发支持团队共享的版本，但是受限于可投入时间会推进会比较慢。

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 6, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
mauvieira, @AscenX, @gjeanmart, @PilotDebug, @alexpozdnyakof, @abhineettandon, @jistro, @waheya, @reubensebastian8, @Dev317, @jrfrantz, @alephao, @alvaroraminelli, @unimu-cic, @NGMIF, @2358326540, @GuruDev0807, @MuckT, @legomushroom, @TingChiehLin


[canary] Type 'ImgSrc' is not assignable to type 'string'.ts(2322)

I was trying to use the canary version with an SVG image and typescript. Getting the following error:
Type 'ImgSrc' is not assignable to type 'string'.ts(2322)
Svg.d.ts(3, 5): The expected type comes from property 'src' which is declared here on type 'IntrinsicAttributes & SvgProps'

The code looks like this:
import { Svg } from 'react-optimized-image';
import Arrow from './arrow-forward-outline.svg';

<Svg src={Arrow} className="arrowforward" />

Seems like the typing is wrong somehow?

I was going to open an issue about it too. I had the exact same problem here.

@JannikZed there was indeed a wrong typing in the Svg component, thank you very much for reporting it! The version 3.0.0-canary.8 should fix this problem.
@LucasMallmann The typing of the Img component should be correct. Did you add /// <reference types="optimized-images-loader" /> to your next-env.d.ts file? Or do you have any custom typings for image files (maybe from version 2)? If so, you can remove them to use the ones shipped by next-optimized-images.

There's an issue with typescript and the Img src prop.

I did with

I figured this out. I forgot to require the image src. Using require(ImgSrc) fixes the types issue.

Hi! How did you did that?

{URL.createObjectURL(file?.[0])}

Isn't it a bad way to do this. I seem to have heard that we should revokeObjectURL after createObjectURL otherwise there ll memory leak. Am i right?

require(ImgSrc)

How did you do this? Because I have the same problem

I Just update my code from
import image from './assets/image.jpg'

to
import image from './assets/image.jpg';

this working for me

Did you figure why it works?

I Just update my code from
import imageX from './assets/image.jpg'

to
import imageX from './assets/image.jpg';

this working for me

Yo typescript is weird af 💀


VSCode 1.40 crash after startup with segmentation fault

After upgrading the VSCode Snap package to 1.40, the app crashes immediately after startup with an segmentation fault.
If I revert the snap to 1.39.2, it is working fine.

VSCode Version:
1.40
Snap version 86405ea2 2019-11-07
OS Version:
Linux Mint 19.2 Cinnamon
Kernel 4.15.0-66-generic

Steps to Reproduce:

Start VSCode
Wait about 4 second (with/without user interaction)

Does this issue occur when all extensions are disabled?: Yes
Screenshot of journalctl

Can you please follow the steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks!

@bpasero I have the same issue.
Ubuntu 19.04 x64 kernel 5.0.0-32-generic
I have tried to follow the instructions in Native-Crash-Issues, but the stack trace is not very readable:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/snap/core/current/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/snap/code/19/usr/share/code/code --no-sandbox'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fb6f2c4f75c in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
[Current thread is 1 (Thread 0x7fb6e0e6f700 (LWP 7337))]
(gdb) bt
#0  0x00007fb6f2c4f75c in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#1  0x00007fb6f2c58861 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#2  0x00007fb6f2c53574 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#3  0x00007fb6f2c57db9 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#4  0x00007fb6ec2b75ad in ?? () from /snap/core/current/lib/x86_64-linux-gnu/libc.so.6
#5  0x00007fb6f2c53574 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
#6  0x00007fb6ec2b7664 in __libc_dlopen_mode () from /snap/core/current/lib/x86_64-linux-gnu/libc.so.6
#7  0x00007fb6ec289a85 in ?? () from /snap/core/current/lib/x86_64-linux-gnu/libc.so.6
#8  0x00007fb6f2424a99 in __pthread_once_slow () from /snap/core/current/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x00007fb6ec289ba4 in backtrace () from /snap/core/current/lib/x86_64-linux-gnu/libc.so.6
#10 0x000055a00363e2c9 in ?? ()
#11 0x00007fb6e0e6e390 in ?? ()
#12 0x000055a0035a2da3 in ?? ()
#13 0x0000000000000000 in ?? ()

dump.txt
GNU gdb (Ubuntu 8.1-0ubuntu3.2) <IP_ADDRESS>80409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /snap/code/19/usr/share/code/code...(no debugging symbols found)...done.
[New LWP 29858]
[New LWP 29864]
[New LWP 29861]
[New LWP 29862]
[New LWP 29871]
[New LWP 29856]
[New LWP 29870]
[New LWP 29866]
[New LWP 29875]
[New LWP 29874]
[New LWP 29892]
[New LWP 29880]
[New LWP 29857]
[New LWP 29877]
[New LWP 29884]
[New LWP 29853]
[New LWP 29882]
[New LWP 29879]
[New LWP 29878]
[New LWP 29873]
[New LWP 29872]
[New LWP 29869]
[New LWP 29894]
[New LWP 29854]
[New LWP 29867]
[New LWP 29863]
[New LWP 29859]
[New LWP 29865]
[New LWP 29868]
[New LWP 29881]
[New LWP 29860]
warning: File "/snap/core/8039/lib/x86_64-linux-gnu/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path /snap/core/8039/lib/x86_64-linux-gnu/libthread_db-1.0.so
line to your configuration file "/home/mat/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/mat/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
warning: File "/snap/core/8039/lib/x86_64-linux-gnu/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
Core was generated by `/snap/code/19/usr/share/code/code --no-sandbox .'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f66c9da975c in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2
[Current thread is 1 (LWP 29858)]
(gdb)

Ok, let's wait for Deepak to comment on the crash and how to proceed.

I am experiencing this same segfault as well after the upgrade to 1.40, running Arch Linux Kernel 5.3.8

Are people seeing this when running the archive'd version of VSCode too? Download: https://az764295.vo.msecnd.net/stable/86405ea23e3937316009fc27c9361deee66ffbf5/code-stable-1573064450.tar.gz
From the command line run: code --no-sandbox

Running that archive looks fine here, while the snap crashes indeed.
Dmesg also contains:
[ 1993.813733] Chrome_IOThread[26090]: segfault at 38 ip 00007fd1fb66275c sp 00007fd1e9c51d20 error 4 in ld-2.23.so[7fd1fb656000+26000]
[ 1993.813738] Code: 41 c1 e1 02 81 e2 ff 7f 00 00 41 09 c1 4d 89 bc 24 f8 03 00 00 48 8d 14 52 45 89 8c 24 00 04 00 00 4c 8d 04 d6 4d 85 c0 74 0f <41> 8b 40 08 85 c0 b8 00 00 00 00 4c 0f 44 c0 41 8b 3f 48 8b 8d 40
[ 2346.762302] Chrome_IOThread[27366]: segfault at 38 ip 00007fabccccd75c sp 00007fabbb2bcd20 error 4 in ld-2.23.so[7fabcccc1000+26000]
[ 2346.762309] Code: 41 c1 e1 02 81 e2 ff 7f 00 00 41 09 c1 4d 89 bc 24 f8 03 00 00 48 8d 14 52 45 89 8c 24 00 04 00 00 4c 8d 04 d6 4d 85 c0 74 0f <41> 8b 40 08 85 c0 b8 00 00 00 00 4c 0f 44 c0 41 8b 3f 48 8b 8d 40

Adding @joaomoreno and @Tyriar given this seems to be a crash in Snap only?

cc @flexiondotorg

I get a similar thing with v1.40 on Windows 10. I think this may be an electron 6 issue (has similar happen in my own electron app which triggered update to v7 😄 )
PS C:\Users\UserName> & 'C:\Users\UserName\AppData\Local\Programs\Microsoft VS Code\Code.exe'                                                                                PS C:\Users\UserName>
 [main 2019-11-11T20:15:16.355Z] update#setState idle
Windows PowerShell[5136]: ../../third_party/electron_node/src/inspector_agent.cc:810: Assertion `(client_) != nullptr' failed.
 1: 00007FF6C954C9E2 node::EmitAsyncDestroy+11839202
 2: 00007FF6C89D9A96 node::Abort+22
 3: 00007FF6C89D9623 node::Assert+131
 4: 00007FF6C89E44BD node::inspector::Agent::Connect+253
 5: 00007FF6C960C829 uv_udp_set_multicast_loop+457321
 6: 00007FF6C960DAA7 uv_udp_set_multicast_loop+462055
 7: 00007FF6C89FA294 uv_loop_delete+6724
 8: 00007FF6C89FD2E4 node::BootstrapEnvironment+52
 9: 00007FF6C89FD24C node::CreateEnvironment+268
10: 00007FF6C89F9875 uv_loop_delete+4133
11: 00007FF6C89EF185 uv_key_set+28101
12: 00007FF6C9591409 uv_translate_sys_error+206665
13: 00007FF6C896155D uv_fs_get_statbuf+5917277
14: 00007FF6C7C51879 uv_cond_broadcast+62537
15: 00007FF6C82CF879 node::AsyncResource::get_async_id+2248441
16: 00007FF6C7C7ACD0 uv_cond_broadcast+231584
17: 00007FF6C7C57FB5 uv_cond_broadcast+88965
18: 00007FF6C7C582E8 uv_cond_broadcast+89784
19: 00007FF6C833B962 node::AsyncResource::get_async_id+2691042
20: 00007FF6C958FE4B uv_translate_sys_error+201099
21: 00007FF6C895BF67 uv_fs_get_statbuf+5895271
22: 00007FF6C90466CF node::EmitAsyncDestroy+6570959
23: 00007FF6C8699144 uv_fs_get_statbuf+2999876
24: 00007FF6C8695708 uv_fs_get_statbuf+2984968
25: 00007FF6C8694964 uv_fs_get_statbuf+2981476
26: 00007FF6C869754B uv_fs_get_statbuf+2992715
27: 00007FF6C86A5C66 uv_fs_get_statbuf+3051878
28: 00007FF6C83414FF node::AsyncResource::get_async_id+2714495
29: 00007FF6C895572B uv_fs_get_statbuf+5868587
30: 00007FF6C899D1F1 uv_fs_get_statbuf+6162161
31: 00007FF6C899D039 uv_fs_get_statbuf+6161721
32: 00007FF6C8954C5C uv_fs_get_statbuf+5865820
33: 00007FF6C8954430 uv_fs_get_statbuf+5863728
34: 00007FF6C5AB6A12 node::InternalCallbackScope::Failed+312674
35: 00007FF6C899C68A uv_fs_get_statbuf+6159242
36: 00007FF6C7478FB0 GetHandleVerifier+635376
37: 00007FF6C8B24AF1 node::EmitAsyncDestroy+1189873
38: 00007FF6C8B24B74 node::EmitAsyncDestroy+1190004
39: 00007FF6C7376BB0 uv_cond_signal+11648
40: 00007FF6C7385D26 uv_cond_signal+73462
41: 00007FF6C73859CC uv_cond_signal+72604
42: 00007FF6C73393BC uv_loadavg+855692
43: 00007FF6C73865E6 uv_cond_signal+75702
44: 00007FF6C735C2CE uv_os_getpid+66926
45: 00007FF6C898B38D uv_fs_get_statbuf+6088845
46: 00007FF6C5EC24DC v8::String::Value::operator*+331020
47: 00007FF6C7B4668A IsSandboxedProcess+204602
48: 00007FF6C5EC1CE6 v8::String::Value::operator*+328982
49: 00007FF6C56E13BF Ordinal0+5055
50: 00007FF6CA35D342 node::AsyncResource::CallbackScope::CallbackScope+4046130
51: 00007FFF3F077BD4 BaseThreadInitThunk+20
52: 00007FFF401CCED1 RtlUserThreadStart+33
[main 2019-11-11T20:15:16.685Z] [VS Code]: render process crashed!
Windows PowerShell[8684]: ../../third_party/electron_node/src/inspector_agent.cc:810: Assertion `(client_) != nullptr' failed.
 1: 00007FF6C954C9E2 node::EmitAsyncDestroy+11839202
 2: 00007FF6C89D9A96 node::Abort+22
 3: 00007FF6C89D9623 node::Assert+131
 4: 00007FF6C89E44BD node::inspector::Agent::Connect+253
 5: 00007FF6C960C829 uv_udp_set_multicast_loop+457321
 6: 00007FF6C960DAA7 uv_udp_set_multicast_loop+462055
 7: 00007FF6C89FA294 uv_loop_delete+6724
 8: 00007FF6C89FD2E4 node::BootstrapEnvironment+52
 9: 00007FF6C89FD24C node::CreateEnvironment+268
10: 00007FF6C89F9875 uv_loop_delete+4133
11: 00007FF6C89EF185 uv_key_set+28101
12: 00007FF6C9591409 uv_translate_sys_error+206665
13: 00007FF6C896155D uv_fs_get_statbuf+5917277
14: 00007FF6C7C51879 uv_cond_broadcast+62537
15: 00007FF6C82CF879 node::AsyncResource::get_async_id+2248441
16: 00007FF6C7C7ACD0 uv_cond_broadcast+231584
17: 00007FF6C7C57FB5 uv_cond_broadcast+88965
18: 00007FF6C7C582E8 uv_cond_broadcast+89784
19: 00007FF6C833B962 node::AsyncResource::get_async_id+2691042
20: 00007FF6C958FE4B uv_translate_sys_error+201099
21: 00007FF6C895BF67 uv_fs_get_statbuf+5895271
22: 00007FF6C90466CF node::EmitAsyncDestroy+6570959
23: 00007FF6C8699144 uv_fs_get_statbuf+2999876
24: 00007FF6C8695708 uv_fs_get_statbuf+2984968
25: 00007FF6C8694964 uv_fs_get_statbuf+2981476
26: 00007FF6C869754B uv_fs_get_statbuf+2992715
27: 00007FF6C86A5C66 uv_fs_get_statbuf+3051878
28: 00007FF6C83414FF node::AsyncResource::get_async_id+2714495
29: 00007FF6C895572B uv_fs_get_statbuf+5868587
30: 00007FF6C899D1F1 uv_fs_get_statbuf+6162161
31: 00007FF6C899D039 uv_fs_get_statbuf+6161721
32: 00007FF6C8954C5C uv_fs_get_statbuf+5865820
33: 00007FF6C8954430 uv_fs_get_statbuf+5863728
34: 00007FF6C5AB6A12 node::InternalCallbackScope::Failed+312674
35: 00007FF6C899C68A uv_fs_get_statbuf+6159242
36: 00007FF6C7478FB0 GetHandleVerifier+635376
37: 00007FF6C8B24AF1 node::EmitAsyncDestroy+1189873
38: 00007FF6C8B24B74 node::EmitAsyncDestroy+1190004
39: 00007FF6C7376BB0 uv_cond_signal+11648
40: 00007FF6C7385D26 uv_cond_signal+73462
41: 00007FF6C73859CC uv_cond_signal+72604
42: 00007FF6C73393BC uv_loadavg+855692
43: 00007FF6C73865E6 uv_cond_signal+75702
44: 00007FF6C735C2CE uv_os_getpid+66926
45: 00007FF6C898B38D uv_fs_get_statbuf+6088845
46: 00007FF6C5EC24DC v8::String::Value::operator*+331020
47: 00007FF6C7B4668A IsSandboxedProcess+204602
48: 00007FF6C5EC1CE6 v8::String::Value::operator*+328982
49: 00007FF6C56E13BF Ordinal0+5055
50: 00007FF6CA35D342 node::AsyncResource::CallbackScope::CallbackScope+4046130
51: 00007FFF3F077BD4 BaseThreadInitThunk+20
52: 00007FFF401CCED1 RtlUserThreadStart+33

Possibly related:

https://github.com/electron/electron/issues/18872
https://github.com/nodejs/node/pull/21182

The new version 1.40.1 is still crashing

I tested on Ubuntu 18.04 with the snap package, from terminal did
> /snap/code/20/usr/share/code/code somefolder
waited for sometime with no interactions but didn't see a crash as reported. Is there something else I need to perform for the crash to happen ?

No, not really. It's even enough to open code without a folder parameter.
It also seems that the failure is also dependent on your hardware/OS.
On my private Dell XPS13 with Linux Mint 19.2 it is working fine. My colleague has a Lenovo P51 with Debian and there it is working fine too. On the other hand, on my business P51 with Mint 19.2 it is always crashing.

I also experience crashes of VS Code version 1.40.1 on Ubuntu 19.10. Here is output of syslog:
Nov 22 21:20:49 kernel: [ 7644.047173] Chrome_IOThread[29938]: segfault at 38 ip 00007f56629e675c sp 00007f565098ad20 error 4 in ld-2.23.so[7f56629da000+26000]
Nov 22 21:20:49 kernel: [ 7644.047187] Code: 41 c1 e1 02 81 e2 ff 7f 00 00 41 09 c1 4d 89 bc 24 f8 03 00 00 48 8d 14 52 45 89 8c 24 00 04 00 00 4c 8d 04 d6 4d 85 c0 74 0f <41> 8b 40 08 85 c0 b8 00 00 00 00 4c 0f 44 c0 41 8b 3f 48 8b 8d 40

The same version of VS code doesn't crash if installed via .deb package.

I will try with Ubuntu 19 today if it doesn't work will try to create a snap package with debug version of vscode , so that we can get better stack trace from your end. Also electron just fixed generating debug symbols for linux https://github.com/electron/electron/pull/18676, if I can that in 6.1.x version of our release that will also help.

I tried 1.40.1 snap package with Ubuntu 19.10 on parallels vm, but I couldn't see any crash even after using the editor for a while. I will get the debug symbols as next step to investigate further.

Can confirm that it neither crashes on fresh Ubuntu 19.10  installation to Virtualbox. I found some recommendations to run VS Code with disabled GPU, but it doesn't resolve the issue.

The new version 1.40.2 is still crashing

@deepak1556  Any updates to this issue?

The new version 1.41 is still crashing

@deimi sorry for the delay, we are updating to a newer version 6.1.6 https://github.com/microsoft/vscode/pull/86837 which will be available in the next insiders and has better debug symbols support from electron, I am hoping that will get this issue moving forward.

v1.41 no longer crashes for me on Arch Linux Kernel v5.4.2

It still crashes for me instead :(

The new version 1.42 is still crashing

Still an issue for me as well.

Confirm crashes continues.
Also, nor --disable-extensions or --disable-gpu works
Attaching the --verbose logging  with both the snap (code-verbose-snap.log) and the tar.gz (code-verbose-tar-gz.log)  versions.
The snap ends with something like
[16970:0212/155343.582711:ERROR:nss_util.cc(748)] After loading Root Certs, loaded==false: NSS error code: -8018
Server response: <?xml version="1.0" encoding="UTF-8"
[17075:0212/155351.020577:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
[17075:0212/155351.020612:FATAL:memory.cc(22)] Out of memory. size=262144
[17015:0212/155351.038297:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
[17015:0212/155351.038331:FATAL:memory.cc(22)] Out of memory. size=262144

Not sure the nss error is the one bringing the fatal issue though, while the "Out of memory" thing doesn't seem to be possible to be muted by using --max-memory either with some bigger number.

It seems that 1.43 is working fine. At least for me.
The others (@askvortsov1 @3v1n0 @tasmanianfox) should check as well, so we can close this issue.
@deepak1556 either it was the update to Electron 7.0 or any other change

I can confirm this works, you can close the issue from my POV.

Works for me too.


Implemented DirAccess get_drive and get_drive_count for OS X

File dialog will now show the volumes on OS X.

Congrats for the nice PR number :smiley:

Haha thanks!

I don't really know what MacOS users expect to see or if it's common for a MacOS user to have permanently mounted separate partitions.
Assuming that this is idiomatic for MacOS users: LGTM 😄

This is an example of the file dialog with this PR:

I believe this is what's expected on Mac. At least it's what I would expect :).

I know nothing about MacOS so this is probably a dumb question: but what is '/net'? Is that a useful thing where you may want to save/load data from as a Godot user?

I've never used /net myself but it seems to be useful if you have a NFS server (ref: https://apple.stackexchange.com/questions/72762/what-are-the-home-and-net-folders-i-see-within-finder)

This seems like it could do with some field-testing regardless. If MacOS users complain in a2 we can change it, but we'll never know if we don't try 👍


refactor(iroh-base)!: reduce dependencies

Description

ensure zeroize is used for SecretKey
remove unused dependencies and features from iroh-base

Breaking Changes

iroh_base::SecretKey::generate now takes an rng
removed iroh_base::SecretKey::generate_with_rng, use generate directly
removed iroh_base::SecretKey::to_openssh
removed iroh_base::SecretKey::from_openssh
anyhow::Error is replaced with explicit errors for RelayUrl::from_str
anyhow::Error is replaced with explicit errors for SharedSecret::open

Notes & open questions
As a follow up, all usage of SecretKey::generate in tests should be changed to use a seeded rng, like chacha8, instead of thread_rng
Change checklist

[ ] Self-review.
[ ] Documentation updates following the style guide, if relevant.
[ ] Tests if relevant.
[ ] All breaking changes documented.

Hm. I would argue the SecretKey::generate function change may not be justified. This increases the burden on the library user. We need to at least have a doctest that shows them how to use the right rng with Secret::generate (I'd say for most cases that's likely rand::thread_rng()).
I suspect that removing the rand dependency from iroh-base only makes iroh-base lighter, not iroh itself, does it?

add an actually running doctest


Compare the memory consumption

it also nice to see

Sure will do that. Thanks for mentioning this.

Hey @kokizzu , For just the KV store, Treds takes less memory as compared to Redis for keys having user: as the common prefix. So I have put 10 Million Keys in Redis and Treds, each key starts with user: and is of pattern user:%d where the part after : is replaced by number from 1 to 10 Million.
Here is the screenshot of the memory by htop command

Althought I am afraid the Sorted Maps store will take more memory as compared to Sorted Sets store in Redis.


gitblame.delayBlame triggers for each character typed

The delay in its current state is only useful (accurate) the moment you click on a line. Once you start typing, it creates a new timer for the next X seconds, per character typed. You'll notice that the inline blame keep appearing much sooner than the delay value set.
Thanks.
v10.5.1

Hey redactedscribe. Thanks for the bug report.
I'll see what I can do. Sadly it is not possible to know what type of text change or selection change the user does with the vscode extensions API.

I was not able to reproduce the issue but I saw some possible changes to mitigate the behavior you are describing. Attached to this post is a pre-release build. If you could test it and verify that the issue is resolve that would be very appreciated!
gitblame-10.6.0-pre-release.zip

    "gitblame.inlineMessageEnabled": true,
    "gitblame.delayBlame": 3000,

Click on a line and wait 3 seconds. Blame appears.
Type a letter every second for 10 seconds. Notice blame appears on the line after 3 seconds, and keeps disappearing and reappearing after every letter typed even though only 1 second is passing between presses.

Blame should only appear 3 seconds after the last letter typed.

Sorry for the way. A new version with the change has been pushed to the marketplaces. It should become available in the next hours/days.
Thank you for the bug report and feedback!

And thank you for the fix!


syntax error corrected

Prisma-client
Reading Data

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Educational : How to find out any fix is done on which release

git tag helps us find these :
Sometimes git sha's change on merge if github does a rebase which some people do, so:
looking at https://github.com/chef/knife-windows/pull/500/commits, I see the commit text for this fix was "Fixed Exception: NameError: uninitialized constant Chef::Knife::Winrm"
I look at git log for knife-windows and see in master that commit was c66c7b6 (is the same commit sha from the branch)

git tag --contains c66c7b6
v3.0.17
v4.0.0
v4.0.1
v4.0.2

So I can say to someone that bug was fixed in v3.0.17+
Looking at https://rubygems.org/gems/knife-windows, I can see all 4 of those version numbers were released as gems. (promoted using expeditor).
git blame components/gems/Gemfile.lock in chef-workstation lets me see when different gems were updated in workstation.
I can see this line:
b6a5b3106 (Tim Smith        2020-06-01 08:44:17 -0700  596)     knife-windows (4.0.2)
If I git show b6a5b3106 I can see what the previous version was, which was 3.0.17, which did have the fix as well.
So then I git blame b6a5b3106^1 -- components/gems/Gemfile.lock  in workstation again. The ^1 after the SHA is a shortcut that means "I want the commit before this work" so what we're staying here is showing me that file before that commit. The -- tells git that what comes after is the filename
Now I see:
809b0caaf (Tim Smith        2020-05-17 12:13:22 -0700  596)     knife-windows (3.0.17)
If I git show 809b0caaf , I see that the previous version was 3.0.16, which was before the fix. but to be clear 809b0caaf, bumped it to 3.0.17 which has the fix. so 809b0caaf "fixed" knife-windows in the workstation.
Now I use git tag --contains 809b0caaf in workstation.

git tag --contains 809b0caaf
20.5.42
20.5.43
...

 I snipped them. sometimes the sorting isn't numeric so you have to be careful to find the latest version. (*note below)
So in this case any build of chef-workstation 20.5.42 and later should fix https://github.com/chef/chef-workstation/issues/1180.
The fastest way to see good builds is to look at https://downloads.chef.io/chef-workstation/current.
20.5.44
20.5.41
from that list, I can see that 20.5.42 did not build, so 20.5.44 is the first build that has that fix.
so then on https://github.com/chef/chef-workstation/issues/1180 I would post something like "This was fixed in knife-windows#500, and in chef-workstation releases 20.5.44 and later"
Thanks!!

This really needs to be turned into either a PR against https://github.com/chef/chef/tree/master/docs/dev or a PR against https://github.com/chef/chef-web-docs/, as an issue here its not so helpful and creates noise that makes it hard to track all the other issues coming into the repository.

Tags are hard, but the changelog has a version by version comment in it though.


Add custom MV PNs to every component

Designate an MV PN to each component using personal database, then assign each component in design its MV PN.

Added


Error: obsidian-icon-folder TypeError: Cannot read properties of undefined (reading 'get')

Describe the bug
I started using syncthing to synchronize with my mobile device (iOS) via Mobius Sync and MacOS. Everything was fine for the first time, but then I noticed that on Mac the icons in the desktop app were missing. I opened the console and now I see this error.
I have completely uninstalled the plugin, deleted all the folders of this plugin from .obsidian and this error still persists.
Maybe it is not related to synchronization but to some other plugin? But it started after the start of synchronization.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Current Error
loading iconize
app.js:1 Plugin failure: obsidian-icon-folder TypeError: Cannot read properties of undefined (reading 'get')
at retrieveLookupItem (plugin:obsidian-icon-folder:5411:41)
at eval (plugin:obsidian-icon-folder:5430:13)
at Array.forEach ()
at BookmarkInternalPlugin.computeNodesWithPath (plugin:obsidian-icon-folder:5429:15)
at BookmarkInternalPlugin.onMount (plugin:obsidian-icon-folder:5435:14)
at eval (plugin:obsidian-icon-folder:6603:32)
at Array.forEach ()
at IconizePlugin.handleChangeLayout (plugin:obsidian-icon-folder:6601:38)
at eval (plugin:obsidian-icon-folder:6396:57)
at t.onLayoutReady (app.js:1:2340282)

Ah yeah I wrote about that in the other post a couple hours ago, go here to this forum that says what to do: #566
Next time I think it is better for us to both read the other forums :100:

Ах да, я писал об этом в другом посте пару часов назад, зайдите на этот форум, там написано, что делать: #566
В следующий раз, я думаю, нам обоим лучше почитать другие форумы 💯

Thank you! Resolve!


Deckselection: change copy to include desktop controls tip.

Currently, the only way for a player on the desktop site to change the deck is to "swipe" a click with their mouse, which is awkward.

Lets just add "use arrows keys" before "swipe right/left to change decks"
arrow keys should work on all browsers to change carousel items.


Ionic V2 generator: parent directory

The generator of pages is a very interesting tool for this V2 version.
I understand the concept of 'Page' but how do you see future big projects architectures with lot of specific modules and pages (nesting could become interesting for master/details pattern or to group inside specific module)
We could imagine something like that:
ionic g page myPage --parent page1 (a parent flag could allow to handle all types of architectures Ionic devs want)

It's an interesting question, as right now generators don't allow that much flexibility.  That being said, because each component is modular, it's pretty trivial to generate a page and then move it to wherever you need.
I believe angular-cli has blueprints similar to ember-cli, which would allow more customization at the cost of a little added complexity. How the angular-cli and Ionic will interact is still something we need to look into.
For the time being, there are no plans to add flags or added customization to keep things simple, but that may change going forward.

Great !
Yea, it's not a blocking feature, I was just wondering if it was hard to implement with your cli
Let me know if one day, you had such customization :)

Thanks for opening the issue. It seems that issue has been resolved. I am going to close this issue but please feel free to reopen another issue if this occurs again.


ColorRef can't be used as a Color in Flutter 3.27.0.

After upgrading to Flutter 3.27.0, all instances of ColorRef will not resolve to the actual Color it represents.
This forces me to use the 'color' property on the ColorRef instance for the real color, which is not const.
Container(color: MyTheme.primary); // This container will act like it was passed null for color

Container(color: MyTheme.primary.color); // This gets the color correctly, but the value is no longer const

The Flutter team is intending on marking the Color class as sealed, and it seems like that will affect the functionality of this package.

I'll have a look into that issue.

@mhorn00 Version 8.0.0 is compatible with Flutter 3.27.0 and up:
dependencies:
  themed: ^8.0.0

However, you said the Flutter team is intending on marking the Color class as sealed. How do you know about this? Could you please give me as much information as you can about this, so that maybe I can talk to them and ask them not to do it?

Thanks for the fix, I'll be able to try it out soon.
In the breaking changes and migrations notes of the 3.27.0 release, they details many changes to the Color class in the "Color wide gamut support" section. The relevant change is mentioned in a note under the "Implementations of Color" header.

@mhorn00 I’ve opened a Flutter issue, asking them not to seal the Color class. If you agree, please consider upvoting it here: https://github.com/flutter/flutter/issues/160613


Add option for detection of stashes and refs, etc.  [feature request]

Not sure what you mean?
Could you elaborate on git status parameters to get that information?

I don't understand Git refs enough, but when using my new git checker and investigating an old repo that showed dirty with uncommitted changes, I stashed them and reran the checker and it showed clean.
Then I thought about suggesting some enhancements to you module such as:
showing brances
refs and stashes
I don't know if that's possible given your concept of the scope of your module, but it would be handy to know if (1) there stashes and (2) all branch names (current and other).
If not of interest to or in scope for you, I'll do it in my module, OR I can work on a PR for yours.

Okay, I think I'm awake now. I can study the 'git help status' more and suggest specifics.

So maybe there should be separate modules, say, Git::Branch and Git::Stash to keep in scope.

I guess a Git::Branch module would make sense   :-)

So, I think copying this module's design and modifying it for the desired Git command would be fairly straight forward. I'll put that on my TODO list if you aren't interested.

I'm interested, but currently focused on RakuAST and pod :-)

Oh, yes, please keep that focus!


NIFI-8722: Updated Quest DB to account for newly added connection sta…

…tus metrics
Co-authored-by: Bence Simon

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Code provided in the PR came from work done by @simonbence and attached to Jiras a patch. I just created the PR to make it easier to run Github Actions, etc. before merging. All looks good to me so will merge. +1. Thanks for putting up the patch @simonbence