text:
Code Helper (Renderer) using over 100% of CPU.

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

VS Code Version: 1.84.2
OS Version: 2018 intel i7 MacBook Pro Sonoma 14.1.1

Steps to Reproduce:

open a 440MB .ipynb file
observe how slowly the file is opened

I have disabled all extensions, apart from the few I have relevant to just running a Jupyter notebook. when opening my file my laptop freezes for a while. once the file is open I cannot edit it or run any of the code.

Can you share the performance profile following the steps at https://github.com/microsoft/vscode/wiki/Performance-Issues#visual-studio-code-is-sluggish, thanks!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
Project folder locked and not updating date modified

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Create project in VS code. Modify files. See folder date modified doesnt update.
To get the folder to change i can modify files without vs code open. Its a vs code problem.

/confirmPlease

Please diagnose the root cause of the issue by running the command F1 > Help: Troubleshoot Issue and following the instructions. Once you have done that, please update the issue with the results.
Happy Coding!

dug around a bit more and realized VS isnt locking the file from updating. It appears to be a windows bug.

source: gharchive/issue

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Collapsed diff should also collapse the diff when there are no changes at all (happens in clean rename and other events)

Now that we have collapsed diff as per #3562 what I want is that if a diff has no changes at all, it should just collapse completely, showing nothing but a helpful message in the dead center of the editor pane (I think it's called a skeleton screen or an empty state):

At present, it shows the entire file by default, which is a little confusing when I'm browsing the diff of each file in the repository side panel. The above suggestion will hide the file contents by default, and only show it when the "View entire file" link is clicked.
Currently this happens when any of the following happens:

The staged changes are committed while a collapsed diff from the index is open. (In this case, the diff suddenly expands to show the whole file. It's jarring.)
The staged changes are unstaged while a collapsed diff from the index is open. (See above.)
The unstaged changes are staged while a collapsed diff from the working tree is open. (See above.)
A file is renamed and the rename is staged, with no changes in the file's contents. View the diff of the rename from the staged changes list.

NOTE: If the "Toggle Collapse Unchanged Regions" option is turned OFF, it can show the whole file by default, since that is the expected behavior anyway. But when it is turned ON, we should collapse in all conditions, including a total collapse.
NOTE: One thing to be careful of: When I'm actively editing a diff from the working tree, if the diff becomes a "no-change" diff due to my typing, it shouldn't suddenly collapse to this empty state. The collapse should only happen when the diff is updated by an external event.
I think I couldn't find a duplicate, but this topic can also be really hard to search in the Issues list. If you know of a duplicate or a similar issue, please mention it. We can move the discussion there.

NOTE: One thing to be careful of: When I'm actively editing a diff from the working tree, if the diff becomes a "no-change" diff due to my typing, it shouldn't suddenly collapse to this empty state. The collapse should only happen when the diff is updated by an external event.

I think this might be tricky to get right.
I like the idea though!

Should "View entire file" be temporary or toggle the "Collapse Unchanged Regions"?

Temporary. Just for the current instance of editor. A new instance will start out collapsed.
We can always click the little icon in the top toolbar to change the toggle permanently.

I think this might be tricky to get right.

Having temporary states in the open editor may help solve this tricky challenge.
Thank you @hediet

authors: ADTC hediet


text:
Speech: allow auto setting for language to derive from display language

Fyi @TylerLeonhardt

Verification:

install the speech extension: https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-speech
make sure accessibility.voice.speechLanguage is configured to auto (it should be by default)
switch VS Code display language to another language such as german or portuguese
start voice dictation in a text editor via "Start Dictation in Editor"
verify you get prompted to install the related language pack for the display language you picked


text:
Debug NPM Script hangs

Type: Bug
Reproduction available at: https://github.com/f8k8/VSCodeNPXBug
When running the project linked above using Debug NPM script, the first call to execSync doesn't seem to clean up properly and the second call hangs and is unable to be debugged. This only happens when the script is run from within VS Code. Running the script from the command prompt completes correctly.
Steps to reproduce:

Run npm i to install dependencies
From a command prompt, run npm run run. The script will complete correctly.
Open the project in VS Code.
Open the command pallette, and run Debug: Debug NPM script.

Expected results:
When running in VS Code, both calls to execSync should complete correctly.
Actual results:
The first call to execSync returns after completion, but there is still another process, displayed as Node.js Process 2 in the Call Stack window. This process doesn't have any debug controls. The only option is to disconnect. The second call to execSync is then attempted but doesn't seem to do anything. In the terminal, done format is printed and then there is no more displayed. If you press CTRL-C in the terminal window, the Process 2 process ends, but the main process is still active, even though you are returned to the command prompt.
VS Code version: Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4200)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.93GB (6.68GB free)

Process Argv
--crash-reporter-id 2825093d-42ce-4844-9043-fb109aceb08c

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

vscode-eslint
dba
3.0.10

prettier-vscode
esb
10.4.0

vscode-react-native
msj
1.13.0

prisma
Pri
5.16.1

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
legacy_priority:31082724

Thanks for the good repro


text:
Improved Search Functionality for Relative Paths in VS Code

When searching for files in VS Code, the search functionality should include the ability to recognize and prioritize relative paths, even when a / character is not included.
Example:
In the top screenshot, when I enter the relative path, the search returns the correct file. However, as shown in the second screenshot, if I omit the / character, the search doesn't provide the desired file.
Desired Feature:
When searching for a file, VS Code's search should automatically include and prioritize relative paths, even if the user does not explicitly type the / character. This would help in quickly locating files, such as definitionPrinterDefinitions/index.ts, without having to include the / character.
Screenshots:

Correct Search Result with /:

Incorrect Search Result without /:

/duplicate https://github.com/microsoft/vscode/issues/133438

I take it back. This isn't related to that.

authors: TylerLeonhardt myagizmaktav


text:
Name of temporary table (SQL Server) show up like commentary

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

VS Code Version: 1.92.0
OS Version:  Windows 10 Pro 22H2

Steps to Reproduce:

I'm using Sql Server with PHP in VS Code, when I need to create temporary tables as in the example below, part of the SQL looks like it was commented out.  $sql = "SELECT * INTO #g2 FROM my_table";

This part here #g2 FROM my_table is all grayed out, as if it were a normal comment, is there any way to disable this just for the SQL context?

when using language MS SQL or installing the sql server extension
I'm not seeing anything commented out

authors: RedCMD helisoncruz


text:
Outline view: collapsed by default (introduce optional setting?)

Very simple request: I'd like the outline view tree to be collapsed by default. It'd be great if there were a configuration setting for this. To be clear, I'm referring to the items in the tree, not the panel itself.
Good:

Bad:

Yeah, that's a tricky one. The current logic reveals one level down and that should work well with one-file-one-type languages like Java. In language like JavaScript that might not be ideal. Needs some thinking

Yeah, we can always have a setting

A configuration settings option for the other outline options like 'Follow cursor' or the sort order would be great as well.

@thorstenc Not a configuration, but the sort order can be set via the menu (choice is persisted)

I would enhance this a bit further by saying that outline view should remember the collapsing state. In other words, if I collapse all, then change to Source control view, when I get back into Explorer view the items are expanded again.
This should also work if I collapse all, then expand just one item, then change views. When I come back to explorer view, only that item should be expanded.

@jrieken One thing I have often wished for was a way to organise my code without the constraints of a rigid file structure. Code is a graph, and I often wish there was a way to present me with the bits of code I care about (pinned, adjacent, degrees-of-separation, etc.). When I'm prototyping and doing R&D in general, I end up with large amounts of code I don't want in focus, but creating new files constantly, and managing imports and exports between those files, is extremely inefficient when I don't even know if I'll need to keep a large amount of the code I'm fleshing out. Being able to see a higher-level overview via the outline panel is at least something in the absence of a solution to the above, but when it behaves like a wall of text that doesn't even remember the state of collapsed/expanded nodes, or have any form of contextual link to what I'm doing in the moment, it feels like a missed opportunity to be a really useful tool.

I agree the ideal solution to this problem is to have a configuration setting, which can be customized by file type or project. I'd go farther and say that the ideal configuration isn't just "expanded" vs "collapsed", but instead a depth level, e.g., expand to level 3 of nested structure.

@jrieken - Any updates?

Has this been solved?

@Antisunny - You can see that the issue is still open

In the mean time <Ctrl> + <LeftArrow> will collapse the entire list

@blowsie - That's good to know, but since you have to focus on the outline window first it's no easier than just clicking the "collapse all" button

@jrieken - Why did you delete my comment?

Collapsing items is actually fair easy - the question is what to do when "Follow Cursor" mode is on? That mode always reveal and hence expands the current item and it will leave many expanded items behind. Not sure if auto-closing those elements that where already expanded is in reach...

@jrieken - The issue is that many VS Code users would like an option to have the items in the outline panel collapsed by default so we don't have to click "collapse all" for every file we open when we're browsing through many files in a library

Here's my use case, which may present a proposed behaviour.
I have a javascript file with a number of functions.
I don't want to know about the contense of the functions, but I want to always know what function I'm actually in at a glance.
I guess my request COULD be served by being able to lock the tree so it doesn't expand or contract, but still follow cursor. I'm forever clicking "collapse all"

I would love for a setting where VS Code would collapse all other folders except the currently active file.
Currently as you go through files, it will expand the folders to each of the files and then keep them expanded as you switch files again.
I want VS Code to auto collapse all folders except the current active file.
To have this:

Instead of:

@nikitavoloboev This issue is related to the outline, not the files list. Maybe file a new issue if one doesn't already exist? =]

How can this simple, so logical and requested feature take so long and a myriad of mostly useless or strictly specific things get in updates???

@Rusenec You could re-channel that complaining energy to writing the PR which makes it do what you want. =/ It's free, don't complain. The team that work on this bring HUGE numbers of updates all the time. If you want it to go faster, help.

@Relequestual - This has been assigned to someone for over a year. How do we know we wouldn't be duplicating effort with a branch that's nearly complete?

@Relequestual  ^This

@v-kydela You can add a custom keybinding for Collapse All that works without having to first focus the outline window.
For example using the Commander extension to chain multiple commands together you can add the following to keybindings.json:
{
    "key": "alt+o",
    "command": "commander.runCommands",
    "args": ["outline.focus", "list.collapseAll", "workbench.action.focusFirstEditorGroup"]
}

The macros extension also works. If you'd rather not install an extension, it's possible to chain commands together using tasks: https://github.com/microsoft/vscode/issues/871#issuecomment-488355245.

@johnmellor - That's good to know, but it doesn't solve the issue

It's a nightmare.
I'm editing reactjs files.
Outline gets expanded up to the calls like _.map.
I have to collapse it.
Outline restores its expanded state after git pull.
Very annoying.

This is really annoying; I am using the outline to quickly navigate through (Python) functions, and dont need all the arguments shown.
Ideally, the collapsing can be configured to be by default done to a certain level, so that we can choose to either collapse to the topmost, or e.g. one below.

It says it's resolved here: https://github.com/microsoft/vscode/pull/74026
It just says it looks great but can't see what the actual shortcut is

@Bulletninja Looks like the command is list.collapseAll. See https://github.com/microsoft/vscode/pull/74026/files, line 306.

@johnmellor already said that. And again, it doesn't resolve the issue. That's a one-time action, not a persistent behavior.

@v-kydela yes, you're right. It is still better than nothing though.

I also think this feature would improve my workflow!

Why is the Outline showing me const/let statements, method calls and inline (e.g: anonymous) functions within TypeScript class methods? I would expect this to only show class properties and methods; nothing within those.
Could somebody please give this some JavaScript and TypeScript love and make it work reasonably well for common use cases within those? Right now as other people have indicated this is worthless because it doesn't provide an outline, just a huge scrolling mess of irrelevant details.

Aware that it does not answer the initial question, but here is what I used as a workaround.
multi-command extension with this settings.json config below:
"multiCommand.commands": [
    {
        "command": "multiCommand.collapseSourceControl",
        "sequence": [
            "workbench.actions.treeView.gitlens.views.remotes.collapseAll",
            "workbench.actions.treeView.gitlens.views.repositories.collapseAll",
            "workbench.actions.treeView.gitlens.views.tags.collapseAll",
            "workbench.actions.treeView.issues:github.collapseAll",
            "workbench.actions.treeView.pr:github.collapseAll",
            "workbench.actions.treeView.gitlens.views.branches.collapseAll",
            "workbench.actions.treeView.gitlens.views.commits.collapseAll"
        ]
    }
]

and this Commands extension with the settings.json config below to add some sexy button in the status bar:
"commands.commands": [
    {
        "alignment": "left", // Should the item be placed to the left or right?
        "priority": 0, // The priority of this item. Higher value means the item should be shown more to the left
        "color": "#FFCC00", // The foreground color for this item
        "text": "$(checklist) SourceControl", // The text to show for the entry
        "tooltip": "Collapse some SourceControl menus", // The tooltip text when you hover over this item
        "command": "multiCommand.collapseSourceControl",
        "arguments": [], // Arguments to pass to the command handler
        // "filterLanguageRegex": "markdown", // Show only if current file's language matches this regex. Requires double escaping
        // "filterFileRegex": ".*\\.ext", // Show only if the current file's path matches this regex. Requires double escaping
        // "filterWorskspaceFileRegex": "**/.*\\.ext" // Show only if a file's path that matches this regex is found in the workspace. Requires double escaping
    }
]

For a key binding, you can still use the VSCode native keybindings.json and reference the multiCommand.collapseSourceControl custom command.

@adjogahm: I'm sorry but I don't understand how Source Control and gitlens etc. relate to this issue (Outline) at all?

You can hide all the variables & constants in the outline and have it only show methods/functions.
In settings. Go to Settings > Features > Explorer and turn off the Outline: Show ____.

Cool! I've also disabled Show Functions since that doesn't make sense (at least to me) for JS/TS where you use anonymous callbacks.

Thanks a lot @bwaindwain ! I had no idea that these settings existed!
It makes the outline much lighter and more digest.
Thus, for me the main point of this issue is almost solved :rocket:

I'd like to jump on this bandwagon too. The few times I've used the outline to trace through something it was an extremely helpful tool but since it doesn't remember state and always has to be collapsed manually it's not my go-to but it could be.

If anyone from the VS Code team ever looks at this, I don't want them to deprioritize it because they think workarounds have been provided in the discussion. I want to make it clear @bwaindwain has provided some useful and interesting information, but it does not solve the issue because it does not allow us to have the outline collapsed by default. Some users (like me) still want to have variables and properties show up in the outline anyway.

The use case for this very common developer workflow is as follows:
User is working on function foo as well as bar in file game.py, and has customized the expansion of the outline tree to work between the functions quicky.  The user then needs to reference function zoro in file library.py.  The user switches focuses back to game.py, checks the reference, and use the outline to quickly get to function bar.
The current problem is that when you switch focuses, everything re-expands and the user has to re-customize the outline tree.
When a user switches focus to a different file, and then returns, the outline should be in the same state as when the user left.  It appears that the outline tree is currently being re-built between focuses.  The solution is that the outline window should be persistent between focus changes, including any customization made to the expansions/collapses.

Why not somehow serialize the expanded/closed state of the tree an re-read that when coming back?
The serialized data could even be stored onto disk, just like the list of open editors. This way, the expanded/closes state would survive restarting VS Code.

@difosfor my bad, I confused with 2 different threads

@AndrewKnauss , are you sure what you describe is the case? I don't see that. In tab A I can expand the outline to the depth I need, then switch to tab B and expand tab B's outline. When I go back to tab A, the outline is exactly in the state it was before switching tabs.

@themighty1 , I just tried to reproduce the issue it has been resolved in a recent update.  The outline tab is now working as expected.  Either that or the issue was intermittent.  Here's the latest version I tested with where the issue appears to be resolved.
Version: 1.58.2 (user setup)
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:10:15.214Z

+1
I need outline view to be closed by default or opened at 1 level:

Class/object
-- Method
-- Method
Current "all open" default view makes me to many click to navigate to a certain function:

Click "-" button
Clock ">" box of class
Browse for a function/method of the class
If it is closed by default, it will save me one click :)

Some brilliant comments in here. I haven't seen any extensions perform what's listed here, but I'm free to suggestions.
Always collapsed
Imagine going through a spreadsheet made into a table in html. Each cell contains an image. Image url's can vary from 10-500 characters. Here's an example of a 2x5 table.

You're on one row and want to quickly go 4 rows down using just the outline. In this scenario, having the outline always expanded limits its usefulness.  The image above was created by collapsing the entire outline, Selecting Follow Cursor as seen below, then clicking on a cell.

I would enhance this a bit further by saying that outline view should remember the collapsing state. In other words, if I collapse all, then change to Source control view, when I get back into Explorer view the items are expanded again.
This should also work if I collapse all, then expand just one item, then change views. When I come back to explorer view, only that item should be expanded.

Add an option above the bar in the above screenshot "Always Collapsed" or "Collapsed by Default" or "Remain Collapsed". What this function does is assure the user 'vscode will never expand the outline unless you explicitly tell me'. This function will collapse the entire outline for the file by collapsing the root node, so \/ html  becomes > html.
If Follow Cursor is selected however! Then that closed outline works exactly as if you did what I did above, collapse the root node, then click the code, and it'll look like the image above. If moving through the code, it will auto-collapse all nodes not relevant, and only expand what's needed to Follow Cursor.
My problem before, jumping down 4 rows in html. This is the best way I know howto do this with the outline/breadcrumbs:

For viewing files with less complicated structure, it is rather handy to have the outline to be expanded by default.
Any chance to add setting for this, or at least have a list.expandAll command?

Is there a setting now in end of 2021?

Is there a setting now in end of 2021?

Apparently not :( I was also hoping for that.

You can hide all the variables & constants in the outline and have it only show methods/functions.
In settings. Go to Settings > Features > Explorer and turn off the Outline: Show variables and Outline: Show properties.

seems outline.showTypeParameters checkbox not work with python3 outline.
local variables aways stay in outline.

current:
// outline with too many details (at default view) is not really outline.

ideal look:

I have disabled outline.showVariables in settings. It's good for PHP, outline now shows only classes and their member functions, without inner local variables.
But it's bad for JavaScript. Outline shows empty panel, because JS classes is object variables:
let myPanel = {
func1(){
...}
}

It works well only with class declarations in JS:
class MyClass {
static func2(){
..
}

I need as well a collapsed outline per default. So please devs provide us a function. It is now request since nearly 4 years.

+1

I use the vim integration, and I have a temporary workaround that works for my usage. I focus the outline with <leader>+o and then navigate the outline with j and k.
By adding outline.collapse to my key bind (in vim.normalModeKeyBindings in settings.json), the outline is collapsed when I want to navigate it.
{
    "before" : ["<leader>","o"],
    "commands" : [
        "outline.collapse",
        "outline.focus"
    ]
},

I've probably spent longer reading this thread than I will actually clicking the Collapse All button every time I go to the Outline view, but it would still be nice if there was a setting that made collapsed the default.

+1
A config like 'outline depth = n' would make 90% happy. Quick win... then you can address edge cases

+1, I want an optional setting to default collapsed outline.

I need it too.

Is there still no settings option for collapse all? Loved to have it...

+1

Yes, indeed. This would still be great. :)

You can hide all the variables & constants in the outline and have it only show methods/functions.
In settings. Go to Settings > Features > Explorer and turn off the Outline: Show variables and Outline: Show properties.

Best solution so far, thanks! Really anoying that this things expands all the time.

You can hide all the variables & constants in the outline and have it only show methods/functions.
In settings. Go to Settings > Features > Explorer and turn off the Outline: Show variables and Outline: Show properties.

Best solution so far, thanks! Really anoying that this thing expands all the time.
Unfortunately it doesn't suit for JavaScript objects, declared as variables.

A default: collapsed setting would make studying large source files easier. It would also be nice if the outline window centered symbols when possible. Often, the outline scrolls the minimum amount to bring a symbol into view at the bottom of the screen. When that happens, I have to manually scroll the outline up to see the symbol's context.

I'm so confused. I have the exact opposite problem - the C++ outline is collapsed by default, so the only thing it shows is a namespace. Worse still, it re-collapses every time I switch tabs, and there is no expand all button, only a collapse all button. Am I missing something? Only sirius0xff made a similar comment:

For viewing files with less complicated structure, it is more handy to have the outline to be expanded by default. Now all I can see is c++ namespace after switching between c++ files, which is useless and very annoying.
Any chance to add toggle setting for this, or at least have a list.expandAll command?

I have the exact opposite problem - the C++ outline is collapsed by default, so the only thing it shows is a namespace. Worse still, it re-collapses every time I switch tabs

@taranu while implementing PR #158650 to add a setting that loads outlines collapsed rather than expanded I found and fixed the bug that's probably biting you. To reproduce it:

Start VS Code fresh.
Open two files whose language mode is able to populate the Outline view, For example, tasks.json and launch.json from a .vscode folder.
Initially their outlines will display fully expanded,, but if you switch back and forth between them a couple of times they will suddenly collapse, and will re-collapse on subsequent switches.

@jrieken I'm hoping this PR isn't too late to be considered for 1.71, particularly as it fixes the bug described above.

This will be part of 1.73.x and next insiders and is this setting: outline.collapseItems

authors: AmeliaBR AndrewKnauss Antisunny Bulletninja DanielTrommel HardCode4All Nikratio PetrusZ Relequestual Rusenec SergeyBeloglazovRL TdyP adjogahm alexanfl axefrog bblaette blowsie bwaindwain cgebbe cha0s cipri-tom crazy-matt db6edr dcraig327 difosfor frontrangerider2004 gjsjohnmurray johnmellor jontwo jrieken langert nikitavoloboev pianocomposer321 pop1989bb ramdrop rickstaa sirius0xff swch01 taranu themighty1 thorstenc v-kydela waj-vx wijjj yaalaa yurenchen000


text:
Mark file or folder with color

In the explorer tab, it will be nice if i could mark some specific file or folder to be always highlighted with the color of my choice so that i could find the file i use often faster.
In the file right-click menu, add additional button - "mark" ---> opens color-picker.
After color is applied the file always has a colored bg.
The bg looks the same as current selected file bg, but with custom color:

If the marked file is selected, the bg should still contain mark color somehow (increased brightness?), but current behavior can also be left without changes - it is not so critical.
And thanks! VSCode is awesome!

Extensions can add context menu actions to the explorer. So that would be step 1.
And I believe that extensions can also add decorations (like Git is doing making things orange).
So putting those two together could produce what you are looking for via an extension.


text:
Shell task not called correctly when using custom shellArgs on Windows

VSCode Version: August 2019 (version 1.38)
OS Version: Windows 10.0.18362 build 18362

Steps to Reproduce:

Create a custom workspace terminal in settings.json which use shellrgs:

{
    "terminal.integrated.shell.windows": "C:\\WINDOWS\\system32\\cmd.exe",
    "terminal.integrated.shellArgs.windows": [
        "/k cd myfolder"
    ]
}

Try to launch a simple task :

{
    "version": "2.0.0",
    "tasks":
    [
        {
            "label": "TEST",
            "type": "shell",
            "command": "dir",
            "problemMatcher": []
        }
    ]
}

Expect the process to be :

Launch terminal
CD to "myfolder"
List files (DIR command)

The actual result is :

Launch terminal
Le chemin d'accès spécifié est introuvable (In english : The system cannot find the file specified)

If I add \r\n to my /k shellArgs, the output is silent, (like if nothing happended):
> Executing task: dir <

C:\myfolder>

Does this issue occur when all extensions are disabled?: Yes
What is the correct way to excute a shell command in a task with my custom terminal ?
EDIT:
I also tried to enclose the command in quotes, with the same result. I also tried to add a & at the end to check if it could be that the command is appended to the shell args, but it did not work.

Tasks adds -c to the shell arguments, but if you specify shell args then we use those instead. If you specify an automation shell we will ignore your shell args:
	"terminal.integrated.automationShell.windows": "cmd.exe",

Ok. But if I want my tasks to execute with my shellArgs, what should I do then?

https://code.visualstudio.com/Docs/editor/tasks#_can-a-task-use-a-different-shell-than-the-one-specified-for-the-integrated-terminal

Also, please ask questions on stack overflow :)


text:
source control not working

Issue Type: Bug
Changes number is shown, but blank window after click source control button
VS Code version: Code 1.39.1 (88f15d17dca836346e787762685a40bb5cce75a8, 2019-10-10T23:31:28.683Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 3.10.0-957.10.1.el7.x86_64

fyi @joaomoreno

authors: ccellhb isidorn


text:
Errors from evaluateRequest should be red in the debug console

If evaluateRequest sends an error response, it's coloured red in the Watch window, but just white in the Debug Console. I think it should also be read in the debug console so it's clear it was an error response.

protected evaluateRequest(response: DebugProtocol.EvaluateResponse, args: DebugProtocol.EvaluateArguments) {
	response.success = false;
	response.message = message;
	this.sendResponse(response);
}

@DanTup you can try it out in tomorrow's vscode insiders and let us know if this is now fixed for you. Thanks!

Fix LGTM, thanks!
(the directional arrows here are really nice too!)

Thanks, adding verified label.

authors: DanTup isidorn


text:
Prettier

Issue Type: Bug
Prettier not showing in status bar anymore
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T17:09:34.601Z)
OS version: Darwin x64 18.2.0

/causedByExtension https://github.com/prettier/prettier-vscode/issues/1044

authors: troyacodes usernamehw


text:
View: Toggle Panel removes scrollbar from the panel.

Issue Type: Bug
Then I hotkey on "View: Toggle Panel", panel appears without a scrollbar but I can scroll with mouse wheel.
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:50:36.977Z)
OS version: Linux x64 5.3.0-40-generic snap

this is specific to terminal based on my testing.

/duplicate https://github.com/microsoft/vscode/issues/91135

authors: Tyriar alexander-zolkin sbatten


text:
Uncaught Error: Cannot read property 'reprocess' of undefined

Issue Id: 062d2ec3-7ca8-2a57-9c42-a30f669cd58fVersions - 1.45.0Stack Error: Cannot read property 'reprocess' of undefinedTypeError: Cannot read property 'reprocess' of undefined/vs/workbench/services/configuration/browser/configurationService.ts#506:114 (onDefaultConfigurationChanged)/vs/workbench/services/configuration/browser/configurationService.ts#98:136 (call)/vs/base/common/event.ts#587:15 (fire)/vs/platform/configuration/common/configurationRegistry.ts#197:33 (registerConfigurations)/vs/platform/configuration/common/configurationRegistry.ts#184:7 (registerConfiguration)/vs/workbench/contrib/externalTerminal/node/externalTerminalService.ts#372:23/vs/base/common/errors.ts#26:11

/duplicate
https://github.com/microsoft/vscode/issues/79809


text:
reset history offset when finishing session (#200930)

Thanks for this PR but this was already fixed with https://github.com/microsoft/vscode/pull/201056/commits/1df7ff28c16dbb0fba8034607e8db85be5f8c97c

source: gharchive/pull-request

authors: Rikimorty jrieken


text:
[loc][query] Translation question.

Description

IMPORTANT: if the defect is reproduced only in a workflow from within the Visual Studio IDE then do not report the issue here - instead, please report it using Visual Studio's "Send Feedback" option that can be accessed from the Help menu OR using this link https://developercommunity.visualstudio.com.
For a defect reproducable from the vstest command line, describe the issue you've observed.

File: Microsoft.TestPlatform.Extensions.TrxLogger\Resources\xlf\TrxResource.xlf:
String: Cannot get find an available filename for {0} using timestamp format '{2}' at {1}.
String ID: 0; "Common_CannotGetNextTimestampFileName"
Question: Please clarify all placeholders, thank you.
Steps to reproduce

What steps can reproduce the defect?
Please share the setup, commandline for vstest.console, sample project, target
framework etc.

Expected behavior

Share the expected output

Actual behavior

What is the behavior observed?

Diagnostic logs

Please share test platform diagnostics logs. Instructions to collect logs are here.
The logs may contain test assembly paths, kindly review and mask those before sharing.

Environment

Please share additional details about the test environment.
Operating system, Build version of vstest.console

Hi,

Placeholder
Name
Example

{0}
fileName
log.txt

{1}
directoryName
c:\data

{2}
timestampFormat
_yyyyMMddHHmmss

Resource string is used in:
https://github.com/microsoft/vstest/blob/de02d84384541d2fe423720abf6a4ce9d0f97ffc/src/Microsoft.TestPlatform.Extensions.TrxLogger/Utility/TrxFileHelper.cs#L180

repo: microsoft/vstest


text:
Unable to find a datacollector with friendly name 'Screen and Voice Recoder'

I am using dot net 8.0 as targetversion and using specflow+mstest to run test cases. i added .runsetting with this data collector and

when i run it with visual studio its working fine i am able to get the recoding for the test execution. but when i use dotnet vstest "path\to\dll\file\project.dll" /Settings: "path\to\setting\file.runsetting" /Logger: "trx" /TestAdaptor: "path\to\testadaptor"
i am getting Data Collection : Unable to find a datacollector with friendly name 'Screen and Voice Recorder'

The collector is shipped with VS only.

authors: nohwnd sampath-ganesan


text:
Overloads of overrides confusing implement macro

Rust doesn't support function overloads so the Windows crate goes through various steps to name mangle in a sensible manner. The implement macro seems to not handle this correctly when overridable methods are overloaded.

I'm removing support for overrides. The new implement macro will just implement whatever interfaces you specify (including overridable interfaces).

repo: microsoft/windows-rs


text:
Bug: Access violation on Interface cast

Which crate is this about?
windows
Crate version
0.35.0
Summary
I've been attempting to use the debug engine API through the windows crate, however I get an access violation when I try to create an IDebugConctrol out of my IDebugClient.
The following code should reproduce the crash:
Toolchain version/configuration
rustc 1.62.0-nightly (306ba8357 2022-04-05)
Reproducible example
use std::ptr::null_mut;
use windows::{
	core::Interface,
	Win32::System::Diagnostics::Debug::{DebugCreate, IDebugClient5, IDebugControl7},
};

fn main() {
	let mut client = null_mut();
	unsafe { DebugCreate(&IDebugClient5::IID, &mut client).unwrap() };
	let client = unsafe { &*client.cast::<IDebugClient5>() };

	let control = client.cast::<IDebugControl7>().unwrap();
}

Crate manifest
[package]
name = "debug_engine"
version = "0.1.0"
edition = "2021"

[dependencies.windows]
version = "0.35.0"
features = [
    "Win32_System_Diagnostics_Debug",
]

Expected behavior
the cast succeeds
Actual behavior
access violation and crash
Additional comments
No response

This should just be:
let client: IDebugClient5 = DebugClient()?;

But the function's metadata lacks the ComOutPtr attribute. I'll transfer it to the win32 metadata repo for a fix.
In the mean time, you can call it as follows:
use windows::{
    core::*,
    Win32::System::Diagnostics::Debug::*,
};

fn main() -> Result<()> {
    let mut client5: Option<IDebugClient5> = None;
    unsafe { DebugCreate(&IDebugClient5::IID, &mut client5 as *mut _ as _)?; }
    let client5 = client5.unwrap();

    let client7: IDebugControl7 = client5.cast()?;

    Ok(())
}

authors: Ben-Lichtman kennykerr


text:
Powershell ConvertTo-Json Pipe

Description of the new feature/enhancement
It would be nice if the winget list command could be piped to the ConvertTo-Json Powershell Pipe
Current Behavior:
[
    "   \b-\b ",
    "Name                                 ID                                    Version               Verf├╝gbar       Quelle",
    "-----------------------------------------------------------------------------------------------------------------------",
    "Streamlabs OBS                       Streamlabs.StreamlabsOBS              1.0.7                 1.1.2           winget",
    "Inspect 0.6.

Proposed technical implementation details (optional)
winget list | ConvertTo-Json

@danielehrhardt native PowerShell support is on the backlog. We're going to start working on some preview cmdlets. Take a look at the backlog and be sure to 👍 the features you feel are important. I'm going to close this as a duplicate of native PowerShell support.

Duplicate of #221 Add Native PowerShell Support

@danielehrhardt we've identified this Issue as a duplicate of another one that already exists. This specific instance is being closed in favor of tracking the concern over on the referenced Issue. Thanks for your report! Be sure to add your 👍 to the other issue to help raise the priority.

You should comment the duplicated issue here for better search results.

authors: danielehrhardt denelon

repo: microsoft/winget-cli


text:
Visual C++ needs update every upgrade

Brief description of your issue
Whenever winget upgrade --all is run, Visual C++ x64 needs to always be upgraded, from the same version number as it was last time before upgrading.
Name                                                                        Id                    Version        Available   Source
-------------------------------------------------------------------------------------------------------------------------------------
Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.36.32532 Microsoft.VCRedist.2015+.x86 14.36.32532.0  14.38.32919.0  winget

And the id section shows x86 instead of x64.
Note that this DOES NOT happen when Visual C++ is installed with winget itself (and not from the website)
Steps to reproduce

Install Visual C++ 2015-2022 from: https://aka.ms/vs/17/release/vc_redist.x64.exe

Run winget upgrade Microsoft.VCRedist.2015+.x64 or winget upgrade --all

Expected behavior

Show correct, consistent id (x64 when the name is x64)
Visual C++ should upgrade to the version it says is available
OR, If the version inside Visual C++ metadata is incorrect, that should be fixed

Actual behavior

Incorrect, inconsistent id
Stays the same version despite upgrading, and asks for upgrade the next time
Shows x86 in the id column when the name shows x64

Environment
Windows Package Manager v1.6.2721
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.2361
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2721.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

How many copies do you have if you run winget list?
You might try uninstalling the extra versions and then see how it behaves.

I believe the issue is in how the installer is reporting the version to the registry. We don't get a specific architecture value from the registry.

I removed all versions of visual c++, reinstalled vc++ 2015-2022 x64 from the website and running winget upgrade. The problem came up.
I also tested winget upgrade without any vc++ dists and winget worked as expected (vc++ didn't come up in the upgrade list).
The problem seems to be specifically with the visual c++ 2015-2022 package on the official visual c++ website.

I believe the issue is in how the installer is reporting the version to the registry. We don't get a specific architecture value from the registry.

I see, should this issue be closed then? Since the issue seems to be with the installer itself?
Maybe the issue can be forwarded to the relevant team. Although it's a relatively minor issue.

I've been working with the VCRuntime team. We've been discussing the nature of the challenge and working towards a permanent solution. It actually looks like a much bigger challenge than I was hoping it would be. I've started engaging with other teams here to discuss other options.

I removed all versions of visual c++, reinstalled vc++ 2015-2022 x64 from the website and running winget upgrade. The problem came up again.
I also tested winget upgrade without any vc++ dists and winget worked as expected (vc++ didn't come up in the upgrade list).
The problem seems to be specifically with the visual c++ 2015-2022 package on the official visual c++ website.

I also had same issue.
I resolved this by removing vc using winget by the id provided winget uninstall Microsoft.VCRedist.2015+.x64 winget uninstall Microsoft.VCRedist.2015+.x86and then installing it again usinng winget install Microsoft.VCRedist.2015+.x64 winget uninstall Microsoft.VCRedist.2015+.x86

winget install Microsoft.VCRedist.2015+.x64 winget uninstall Microsoft.VCRedist.2015+.x86

Should that last be winget install? Not trying to be pedantic, but this does seem a bit finicky and I want to be sure that the solution isn't uninstalling the x86 version and letting some other mechanism manage it. Might be worth a clarifying edit if so.
Thanks for figuring out a workaround!

Typo. Corrected now.

I removed all versions of visual c++, reinstalled vc++ 2015-2022 x64 from the website and running winget upgrade. The problem came up again.
I also tested winget upgrade without any vc++ dists and winget worked as expected (vc++ didn't come up in the upgrade list).
The problem seems to be specifically with the visual c++ 2015-2022 package on the official visual c++ website.

I also had same issue. I resolved this by removing vc using winget by the id provided winget uninstall Microsoft.VCRedist.2015+.x64 winget uninstall Microsoft.VCRedist.2015+.x86and then installing it again usinng winget install Microsoft.VCRedist.2015+.x64 winget install Microsoft.VCRedist.2015+.x86

This works! Thanks!!

authors: denelon drshtmstry geetmankar trebuh


text:
Add basic synchronization for the install queue to prevent installs from colliding

Remove the temporary error code that was being returned when this scenario hit. Added a static mutex and removed async calls that would cause the mutex to be released too early or on the wrong thread. The mutex needs to be static because Install is a class method and callers can create as many PackageManager's as they want.
Tested multiple simultaneous installs and verified the wait behavior.
I also moved the Queued call down below where the arguments were verified. I noticed in my tests that even though the progress and cancel tokens are co_awaited the Queued event was getting sent so fast that my caller wasn't even receiving it because the event handler wasn't hooked up. This can be fixed on the client side by setting the operation to not start immediately, but that seems overly complex, and I don't like the idea of Queued being returned before it's actually waiting, when the call may still be rejected due to invalid arguments.
Microsoft Reviewers: Open in CodeFlow

I guess I need to let update this to let Cancel through while it's waiting.


text:
How can we help?
I would like someone else to build the manifest.
Please provide the following information
Download Page Url: https://github.com/dsymbol/yt-dlp-gui
Publisher: dsymbol
Package Name: yt-dlp-gui
Description: A cross-platform GUI wrapper for yt-dlp written in PySide6
Package Version: 2024.10.02
Installer URL: https://github.com/dsymbol/yt-dlp-gui/releases/download/2024.10.02/yt-dlp-gui-win64.zip

My bad, reopening since i'm requesting yt-dlp-gui, which is not the same of any of the other issues mentioned

So fast! Thank you!

repo: microsoft/winget-pkgs


text:
new version Zheguisoft.zg_upload version:6.2.0.5

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

close


text:
Wiesemann-Theis.WuTility version 4.81

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109657&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Domain

authors: WilhelmDTM stephengillie


text:
New version: bloznelis.typioca version 2.4.1

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109989&drop=dogfoodAlpha

Closing in favor of https://github.com/microsoft/winget-pkgs/pull/109991


text:
Update version: oxygendioxide.Deepvocal-Hitsuboku-Kumi-CHN version 1.1.0

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115970&drop=dogfoodAlpha

@wingetbot waivers Add Validation-No-Executables

/azp run


text:
Update: Bazelisk v1.18.0

[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] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Executable-Error

authors: FantasqueX stephengillie


text:
New version: Splashtop.SplashtopStreamer.Deployment version 3.6.0.3

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

duplicated. delete it.


text:
New version: Kitware.CMake version 3.28.4

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-03-20T22:02:06.9283147Z ##[error] Manifest Error: DisplayVersion declared in the manifest has overlap with existing DisplayVersion range in the index. Existing DisplayVersion range in index:  [ [3.29.0, 3.29.0]]

(Automated response - build 870.)

authors: PckgrBot stephengillie


text:
schild-report.schild-report version 2.6.125

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Close with reason: No files changed;


text:
New package: Lime3DS.Lime3DS version 2107

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Resolves #148602

Microsoft Reviewers: Open in CodeFlow

Verify:


text:
MartinBlume.Arena version 3.5.1

[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?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

During installation a language selection dialog that requires user input is displayed.

authors: ChuckFerring chausner


text:
New version: Unity.Unity.6000.LinuxMono version 6000.0.14f1

Created by 🥟 Dumplings in workflow run #7196.

Log
Updated: 6000.0.13f1 → 6000.0.14f1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000 version 6000.0.14f1 - https://github.com/microsoft/winget-pkgs/pull/166895
Handling Unity.Unity.6000.Android...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.Android version 6000.0.14f1 - https://github.com/microsoft/winget-pkgs/pull/166896
Handling Unity.Unity.6000.iOS...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.iOS version 6000.0.14f1 - https://github.com/microsoft/winget-pkgs/pull/166897
Handling Unity.Unity.6000.tvOS...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.tvOS version 6000.0.14f1 - https://github.com/microsoft/winget-pkgs/pull/166898
Handling Unity.Unity.6000.visionOS...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.visionOS version 6000.0.14f1 - https://github.com/microsoft/winget-pkgs/pull/166899
Handling Unity.Unity.6000.LinuxIL2CPP...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000.LinuxIL2CPP version 6000.0.14f1 - https://github.com/microsoft/winget-pkgs/pull/166901
Handling Unity.Unity.6000.LinuxMono...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

authors: spectopo stephengillie


text:
New version: Ryujinx.Ryujinx version 1.1.1384

Created by 🥟 Dumplings in workflow run #3946.
Logs
Updated: 1.1.1382 → 1.1.1384
Cannot validate argument on parameter 'ChatID'. The argument is null, empty, or consists of only white-space characters. Provide an argument that contains non white-space characters, and then try the command again.
Submitting WinGet manifests
Cannot validate argument on parameter 'ChatID'. The argument is null, empty, or consists of only white-space characters. Provide an argument that contains non white-space characters, and then try the command again.

Microsoft Reviewers: Open in CodeFlow

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\Ryujinx.exe returned exit code: -532462766

Automated error analysis suggests -532462766 may mean EXCEPTION_COMPLUS (Unhandled Exception)
(Automated response - build 894.)


text:
Remove version: NewBreedSoftware.TuxPaint version 0.9.33

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


text:
Remove version: qBittorrent.qBittorrent version 4.6.4

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


text:
Remove version: YABE.YetAnotherBacnetExplorer version 1.3.2

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://downloads.sourceforge.net/project/yetanotherbacnetexplorer/SetupYabe_v1.3.2.exe
OK
(Automated message - build 923)

Close with reason: Package still available;


text:
ARP: Iterate.Cyberduck version 7.5.1.33324

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Try changing - Architecture: x86 to - Architecture: x64.

Thanks, I was thinking why just two PRs are only having errors and the rest all are passing validation.

/azp run


text:
New version: Tutanota.Tutanota version 3.89.25

[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] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

authors: OfficialEsco zachcarp


text:
COASSoftwareSystemsB.V.SemantaModeler version 6.6.4.5299

[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] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Created a new PR to get rid of commits in history and file renames

new PR: https://github.com/microsoft/winget-pkgs/pull/43781


text:
Kiwix.Wikivoyage version 2.0.9.0

[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] Have you validated your manifest locally with winget validate --manifest <path>?
[x] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@AmelBawa-msft Just like #66581 and #64900, this PR will need a waiver added.
Background for the other MS devs: these three apps (Kiwix JS, WikiMed by Kiwix and Wikivoyage by Kiwix) are all based on the same codebase, and they are all msix/appxbundle UWP apps authored in HTML/JS. Recently (approx since end of June) winget has not been able to validate these app types in Azure, despite their being signed correctly and despite the manifest correctly installing in winget. Please see screenshots below as evidence of this for this Wikivoyage app.

/azp run

@wingetbot waivers Add Validation-Installation-Error

@yao-msft Thank you for adding the waiver for this package.

authors: Jaifroid hackean-msft yao-msft


text:
Init /tmp/.X11-unix is overwritten by mounts

The init order seems to process the creation of /tmp/.X11-unix before processing /etc/fstab. This conflicts with an tabs which set /tmp to be a tmpfs (as is fairly common).
More information in: https://github.com/microsoft/wslg/issues/19#issuecomment-824417912
Example /etc/fstab:
tmpfs /tmp tmpfs rw,nodev,nosuid,size=2G 0 0

As a side note for anyone using genie (<1.38) or one of the other systemd hacks - systemd-tmpfiles, which is run by default on boot, also wipes out the contents of /tmp/.X11-unix . If you're having that problem and find this issue, it's probably not WSLg's fault.

To make it work with systemd, create /etc/tmpfiles.d/wslg.conf with following content:
#  This file is part of the debianisation of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.

# See tmpfiles.d(5) for details

# Type Path           Mode UID  GID  Age Argument
L+     /tmp/.X11-unix -    -    -    -   /mnt/wslg/.X11-unix

@eternalphane Brilliant workaround. I'm using the systemd script https://github.com/DamionGans/ubuntu-wsl2-systemd-script and this works perfectly.

That is a valid workaround, but its not ideal as any subsequent changes or
adds to /tmp we will have to keep track of.
Same could be done on init for non-systemd.
This will likely not be fixed for systemd as it starts after init finishes,
so it might not be fixed under this issue (or in the scope of just changing
the init order). I believe fixing it for genie will require a workaround,
documentation (so we can properly mimic what is required) and ideally
actual systemd support.
On Sat, Apr 24, 2021, 8:09 AM Amir Asyraf @.***> wrote:

@eternalphane https://github.com/eternalphane Brilliant workaround. I'm
using the systemd script
https://github.com/DamionGans/ubuntu-wsl2-systemd-script and this works
perfectly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/wslg/issues/43#issuecomment-826041645, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLS7COZAU7IHZG4CLCSVATTKJOAPANCNFSM43MYCSUQ
.

@pecigonzalo The fix genie (1.39+) is actually using is the one documented by @diddledan here:
https://forum.snapcraft.io/t/wsl-wslg-and-systemd-hacks/24022
That is to say, using systemd-socket-proxy to make the XWayland socket available under .tmp, and using an override for the user-runtime-dir service to mount /mnt/wslg/runtime-dir at /run/usr/$UID. This solution seems to be working pretty well so far.
That said, I do currently have https://github.com/arkane-systems/genie/issues/157 open, which seems to suggest that the latter has some issues when there are user sessions under UIDs other than 1000 involved. Currently being looked at.

@pecigonzalo : Thanks for reporting this.
The issue has been fixed in wsl and will make its way to insider builds.

Using systemd in Rocky Linux 9, I don't get this problem, but in Fedora 40 I do.
@sonook 's fix works a treat for Fedora 40 to get I working, Added file, terminated WSL and then started it again, starts working no problem

authors: FingerlessGlov3s OneBlue amirasyraf cerebrate eternalphane pecigonzalo

repo: microsoft/wslg


text:
Support for signInAudience AzureADMyOrg or AzureADMultipleOrgs

I have a question! Until know it works for any account (AzureADMultipleOrgs --> common Endpoint). Do you know what need to be changed in the code so that it works? On the registration side I already changed it.
Many thanks for your help
Regards,
Joël

Hi Joel,
I'm really sorry, but I don't quite understand your question. MSAL (AzureAD Authentication Library v2) supports multi-tenant by default. If you want users from one tenant only to be able to log into your app, you can filter users by tenantid after the authentication is successful and you get a token. Therefore you should use the common endpoint when using MSAL.
Let me know whether your question was answered! 😊

FYI for a single tenant, getting this error:
Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.
Not sure yet how to fix it based on this sample.

I get the same error as ccit-spence.
Don't know how to fix this
Thanks for any advise
regards Michael

If you are creating the AD app in the Azure portal, click the switch to make the app multi-tenant.

Is there any example to configure my Apps for only one tenant can be authenticated?

Hey @rdantas9 , please have a look over here: https://learn.microsoft.com/en-us/azure/active-directory/develop/single-and-multi-tenant-apps#who-can-sign-in-to-your-app

authors: ccit-spence joelhaslerfhnw mark-szabo mprattinger rdantas9


text:
Adding the quickstart sample links in the code snippets

A suggestion: In addition to download SDK links in the code snippets, that would be also great to offer a quick sample app to test how does this API and the SDK work. Quickstart samples are great when it comes to testing the SDKs. As a start, it would help to link the quick start url, so devs can go ahead, select their prefered language and download a quickstart sample: https://developer.microsoft.com/en-us/graph/quick-start
As a second step it would be much nicer to be able to download the related SDK quickstart sample directly from the code snippets.

Hi @aycabas , Thank you for the suggestion. This is definitely on our radar. We want to leverage the work that Jason and yourself are doing. As a first step, we need to have an effective design to ensure that the user is guided towards those tutorials.

authors: RabebOthmani aycabas


text:
Is there a way to pass Sass options within middleman?

For example, I'd like to set :line_numbers to false, so that line numbers and file paths aren't emitted into the compiled CSS as a comment.

Is there any chance we can re-open this issue, considering Compass itself is no longer maintained and the middleman-compass gem itself has also been archived (presumably due to Compass no longer being maintained)?
It seems completely absurd that I have to keep a no-longer-maintained middleman-compass dependency around purely for there to be a means of setting SASS configuration options in my middleman application.

Well, this ticket is 9 years old.
Sass settings can be set directly in config.rb:
set :sass, { stuff }

https://github.com/middleman/middleman/blob/4.x/middleman-core/lib/middleman-core/renderers/sass.rb#L9-L11

@tdreyno :O :raised_hands:

authors: chanpory iaman tdreyno

repo: middleman/middleman

license: mit

license_source: bigquery


text:
内存分析的疑问

想问问nodeMetrics是用来做什么场景的？跟alinode的内存溢出排查场景一样吗？

基本上来说可以用来分析内存使用情况，基本上也就是内存溢出之类的吧

有截图吗  我看一下

就是 Node.js 一些堆栈的情况丫，可以起到基础的观测。 比较要排查哪个对象造成的泄露，还是要依赖 alinode  一类的产品；

那还需要到阿里云上面才能查看么？还是直接可以看的到？

感谢支持，此项目已完成历史使命，不再更新。

authors: czy88840616 guangwong wadeDra

repo: midwayjs/pandora


text:
Added some example files and merges stylesuxx and jbbr changes

Great library for interfacing with Raspberry Pi and the 595 shift Register.  I though it would be nice to add some example files.

Also added Visual Studio project files.

repo: mignev/shiftpi


text:
eliminate warnings

This patch eliminates all the compiler warninsg I get under Xcode 16.0 beta 4:
PickerNameProviderMacro.swift:58:13
Initialization of immutable value 'types' was never used; consider replacing with assignment to '_' or removing it
RefCounted.swift:24:9
Result of call to 'initRef()' is unused
Array.swift:301:5
@discardableResult declared on a function returning Void is unnecessary
Packed.swift:13:13
'append(value:)' is deprecated: This method signature has been deprecated in favor of append(_:)
Wrapped.swift:143:28
Value 'node' was defined but never used; consider replacing with boolean test
Wrapped.swift:511:17
Result of call to 'retain()' is unused

Forgot to build the test cases before opening the PR. The force push 9c54b78 eliminates the four warnings from the test cases.

Oh, delightful!
I'll review tonight!

authors: mayoff migueldeicaza

repo: migueldeicaza/SwiftGodot


text:
Removing redeclaration of GetScimV2OrganizationsUsersByOrgByScimUserId

It is already declared in line 3145

Hi @renzors ,  the file src/mock/endpointpattern.go is auto generated so changing it wouldn't yield much result.
The ideal fix would be fixing the gen.go script to properly check if a given route was already created.

I'm working on improving the gen.go script and this problem should be fixed with it.

@renzors could you try to use the branch fix-gen-redeclarations and test the changes?

Hi @migueleliasweb, thanks for the quick review! Oh I see, I will use that branch and let you know, thanks!

Hi @migueleliasweb, it works perfect from fix-gen-redeclarations branch. Thanks!

Closing this PR, and waiting for the fix in the main branch :-)

The fix was merged. Thanks @renzors !

authors: migueleliasweb renzors

repo: migueleliasweb/go-github-mock


text:
How to open multiple buffers?

Following the readme I've implemented:
opts = {
  hooks = {
    yazi_opened_multiple_files = function(chosen_files, config, state)
      -- Iterate over the selected files
      for _, file in ipairs(chosen_files) do
        -- Open each file in a new buffer
        vim.api.nvim_command("e " .. file)
      end
    end,
  },
}

But after selecting multiple files in visual mode in yazi and pressing ENTER, only one buffer is opened.

I'm missing something?

The next prints nothing
print(vim.inspect(chosen_files))

With this reproduction script it works for me. Can you try it out?
-- You can use this file to reproduce an issue with your configuration.

---@module "yazi"
---@module "lazy"

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify('./.repro', ':p')

-- set stdpaths to use .repro
for _, name in ipairs({ 'config', 'data', 'state', 'cache' }) do
  vim.env[('XDG_%s_HOME'):format(name:upper())] = root .. '/' .. name
end

-- bootstrap lazy
local lazypath = root .. '/plugins/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    'git',
    'clone',
    '--filter=blob:none',
    'https://github.com/folke/lazy.nvim.git',
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)
vim.g.mapleader = ' '

-- install the following plugins
---@type LazySpec
local plugins = {
  'folke/tokyonight.nvim',
  {
    'mikavilpas/yazi.nvim',
    event = 'VeryLazy',
    keys = {
      {
        '<leader>fy',
        function()
          require('yazi').yazi()
        end,
      },
    },
    ---@type YaziConfig
    opts = {
      open_for_directories = true,
      ---@diagnostic disable-next-line: missing-fields
      hooks = {
        yazi_opened_multiple_files = function(chosen_files)
          vim.notify('Opening ' .. #chosen_files .. ' files')
          for _, file in ipairs(chosen_files) do
            vim.api.nvim_command('e ' .. file)
          end
        end,
      },
    },
  },
}
require('lazy').setup(plugins, {
  root = root .. '/plugins',
})

vim.cmd.colorscheme('tokyonight')
-- add anything else here

https://github.com/user-attachments/assets/bcc5a33c-ba58-4258-9229-6c1e296332ee

Your repro file works as expected. I'm gonna research and document what is interfering on this issue once I find it 👍

mikavilpas I found the issue:
It was not an issue in my config. It happens when the user overrides the ENTER key on ~/.config/keymap.toml.
In my case I had
# Plugin: smart-enter
# ==============================================================================
[[manager.prepend_keymap]]
on   = [ "<Enter>" ]
run  = "plugin --sync smart-enter"
desc = "Enter the child directory, or open the file"

so after deleting that, it works as expected.

@xfzv I'm glad that's the case on your end, but it's confirmed by the author: https://github.com/sxyazi/yazi/issues/1378

It's not an issue per se, they've intentionally decided to disable support for opening multiple files with smart-enter by default.
This only affect smart-enter. If you don't use it you can open multiple files at the same time without problem.
You can also leave the options empty, you don't have to set it to false. Just don't set it to true.

ya.manager_emit(h and h.cha.is_dir and "enter" or "open", { })

authors: Zeioth mikavilpas


text:
Update StyleCop references to work with latest released version of StyleCop

#86

I don't believe this build fail is due to my changes.

repo: mikefourie/MSBuildExtensionPack


text:
angular version 1.3?

Does this work with version 1.3 of angular? Because when I try to install with bower it always tries to downgrade my angulare packages back to 1.2.

We have been using this without issue on Angular 1.3. I'm going to close this for now. If you can provide any additional information, feel free to reopen.

authors: chovy mikefrey


text:
Blocked access to file

Hi,
I'm new with wkhtmltopdf.
Unfortunately, I'm suffering from this error:
Loading pages (1/6) [> ] 0% [======> ] 10% Warning: Blocked access to file Warning: Blocked access to file Warning:
I've tried to set the option "enable-local-file-access"  => true but phpwkhtmltopdf tell me, that this option not exist.
A helping idea, I would appreciate!
Thanks a lot...
Toby

You must pass the options in a wrong way. The library does not restrict any options and enable-local-file-access works fine for me. You should not use true as value, though, but simply pass it like this:
<?php
$pdf = new Pdf([
    'enable-local-file-access',
    // ...
]);

authors: mikehaertl strtob

repo: mikehaertl/phpwkhtmltopdf


text:
OnInit hook called multiple times if entity is loaded by population

Describe the bug
When an entity is initially loaded by population, its @OnInit-hook gets called twice (once before the entity is actually initialized)
To Reproduce
Steps to reproduce the behavior:

Define an entity with a relation to another entity (e.g. parent -> children)
Load the entity and make sure the relation is populated.
Listen to the @OnInit hook, and you will find that it is called multiple times for the same entity (the one that is being loaded through population)

If the entity to be populated is loaded beforehand (e.g. by calling findOne directly), the @OnInit hook is only ever called once, as is expected.
Repo for reproduction: https://github.com/JakobStaudinger/mikro-orm-populate-init-reproduction
Expected behavior
The @OnInit hook should be called exactly once (for each entity), after the entity is fully initialized
Versions
| Dependency | Version |
| node | 12.22.1 |
| typescript | 4.3.5 |
| mikro-orm | 4.5.7 |
| your-driver | mongodb |

I've investigated a bit and it seems that only dispatching the on-init event right here if options.initialized is true leads to the expected behavior, though I don't know the code well enough to know if this would cause problems elsewhere...

This is kinda intentional, we could change it in v5 but for me this is a breaking change. Because it means we won't fire the onInit hook for references (not populated entitities) at all. You can make your hook conditional and just check wrap(this).isInitialized().

Thanks for the quick reply!
To me it seemed like unexpected behavior, since I don't expect an "init" hook to get called multiple times, but I see the reasoning behind it. I tried the workaround and it works perfectly for my situation, thank you very much 😄
I'm closing this issue, as it seems to be invalid now with the workaround.

repo: mikro-orm/mikro-orm


text:
Support de/compress_into(ptr, len)

de/compress directly into a Python buffer

@martindurant will something like this work for you?
>>> import numpy as np
>>> from cramjam import snappy
>>> values = np.zeros(100, dtype=np.uint8)
>>> snappy.compress_into(b"bytes", values)
>>> values
array([255,   6,   0,   0, 115,  78,  97,  80, 112,  89,   1,   9,   0,
         0, 181, 139, 168, 219,  98, 121, 116, 101, 115,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0], dtype=uint8)
>>>

then decompress_into(bytes, array) as well?

Yes, perfect. In practice, I only expect to use decompress_into, although compress_into might have an interesting application with memmapped files. I would have either function return the number of bytes written.
Am I right in assuming that the zero padding you have if the length isn't exactly right would cause the decompress to panic?

Ok, when prototyping that, felt like one might have wanted to compress_into(source_array, dst_array) but it's typically compress_into(bytes, array) then I'm good with that as well. :+1:
and yes, just noticed that myself, should probably return the number of bytes written. Good catch.
Most of the de/compression APIs implement the std::io::Read, meaning that if passed a slice, we can read the input which will de/encode until it reaches the end of the output buffer. While a Vec<u8> would continue to grow until all bytes are de/encoded with read_to_end. The point being, with a reference to the array, we can only have a slice, thus only have the ability to write to the end of the buffer.
So long as it successfully gets the references, it would not panic, regardless if the output buffer was too short, or too long.

The point being, with a reference to the array, we can only have a slice, thus only have the ability to write to the end of the buffer.

There's no particular reason to handle this on the rust side, since making a slice/view/memoryview on the python side is no-copy, almost zero-cost. More a case of idle curiosity. Probably needs just a couple of comments in the eventual test-suite - i.e., we'll get the number of bytes back at compression, and then slice the resultant data for decompression and get the original back.

authors: martindurant milesgranger

repo: milesgranger/pyrus-cramjam


text:
Support propagating c++ exception to python

Signed-off-by: zh Wang zihao.wang@zilliz.com
issue: #383

/lgtm
/approve

repo: milvus-io/knowhere


text:
[ERROR]: The PyMilvus requirements should be Python 3.6 or later

Is there an existing issue for this?

[X] I have searched the existing issues.

Issue
In this page:
https://milvus.io/docs/v2.0.x/install-pymilvus.md
The Requirement section:
Python 3 (3.7.1 or later) is required.
Should be changed to:
Python 3.6 or later is required.
Suggestion
No response
Anything else?
No response

Closed with PR #1592

authors: YiyunNi yhmo

repo: milvus-io/milvus-docs


text:
Karist should use funcml instead of re-implementing it

We should separate the Karist CLI and its mutative engine to let it be useful in other contexts than Kubernetes. Separating this project in two parts:

the mutative language part, called "funcml-lang"
the Karist CLI that can generate examples and apply changes to Kubernetes specifically

Karist would have a new Rubygems.org dependency: "funcml". Unit tests would not perform any test on funcml mutations but should be focus on CLI tasks, such as files generation and exception management.

funcml-lang repository: https://github.com/mimopotato/funcml-lang

repo: mimopotato/karist


text:
The automated release is failing 🚨

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

CircleCI using 'master' not configured publish branch (undefined)
Unfortunately this error doesn’t have any additional information. Feel free to kindly ask the author of the condition-circle plugin to add more helpful information.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

CircleCI using 'master' not configured publish branch (undefined)
Unfortunately this error doesn’t have any additional information. Feel free to kindly ask the author of the condition-circle plugin to add more helpful information.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

CircleCI using 'master' not configured publish branch (undefined)
Unfortunately this error doesn’t have any additional information. Feel free to kindly ask the author of the condition-circle plugin to add more helpful information.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

repo: mindhivefi/ts-mock-firebase


text:
SDXL: transpose text_projection in converting

What does this PR do?

Parameter conditioner.embedders.1.model.text_projection is called differently in MindONE and Diffusers, so it is transposed when pre-trained weight is converted
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline?
[x] Did you make sure to update the documentation with your changes? E.g. record bug fixes or new features in What's New. Here are the
documentation guidelines
[x] Did you build and run the code without any errors?
[x] Did you report the running environment (NPU type/MS version) and performance in the doc? (better record it for data loading, model inference, or training tasks)
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@xxx

diffusers:
pooled_text_embedding = self.text_projection(input), where self.text_projection is a torch.nn.Linear without bias, which means pooled_text_embedding = input @ self.text_projection.weight.T
MindONE (and stability-AI):
pooled_text_embedding = input @ self.text_projection.weight, where no transpose op.
so we transpose this parameter manually when convert weights.

repo: mindspore-lab/mindone


text:
Modify the jailbars recipe to resolve conflict.

castle:jailbars conflicted with default:ladder_steel.

This may lead to other conflicts but for now I think it will work. Merged.

authors: Philipbenr jhcole

repo: minetest-mods/castle


text:
0.0.1 effectiveness

The shot https://github.com/minhducsun2002/just-another-newtab#user-content-screenshots looks nice but I'm not getting it with either Waterfox 56.2.3 or Firefox 63.0 on FreeBSD …
Postscript
Note to self, Simplicity 0.0.1 also known as Just another new tab page.

Please describe the issue you encounter precisely.
I tested with Firefox 62.0.3-1on Debian and I saw no error.

There's blankness when opening the first new tab after installation of the extension:

– and blankness for every new tab thereafter:

A web console view of things:

It looks like I forgot to include JS files.
New release should fix that. Sorry for any convenience.

Issue solved.

Fix confirmed. Thanks!


text:
🛑 MineVN Maven & Resource Pack is down

In 2bc3473, MineVN Maven & Resource Pack (http://app.minevn.net/pack) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MineVN Maven & Resource Pack is back up in 5bedd93.


text:
Fix typo

changed "envrionment" to "environment"

Thanks for catching this @error418 ! Much appreciated.

repo: minio/docs


text:
Is there a way to mock Minio Client in Golang Unit tests?

Hi, I am writing unit tests in Golang. I wonder how can I mock the Minio Client in Golang, any suggestions? Looking forward to your help.

If you need a higher level, create an interface for the functions you need in the client and replace your client use with the interfaces and implement the mocking functionality you need.
If you need lower level, you can override the Transport in the client (low level, complex).

Thanks a lot @klauspost ! I will try it out immediately.

Hi @klauspost , may I please double check, if I want to mock the makeBucket method. shall I define like this in my interface:
MakeBucket(ctx context.Context, bucketName string, opts minio.MakeBucketOptions) (err error) ?
I need to use minio.MakeBucketOptions in my interface parameters, and will this kindof violates the OOP principles. I tried using my self-defined MakeBucketOptions which I copied from Minio-go, but it says that minio Client does not implement this method. Looking forward to ur help! : )

@ziranl16 Great that Go is not an OOP language. To implement an interface you need to implement it with the same types. I will not go into Dependecy Injection and similar Go related stuff, you can google that.
TLDR; Create an interface, inject a *minio.Client or your mock as you see fit:
// Add functions you need to mock.
type ObjectStore interface() {
	MakeBucket(ctx context.Context, bucketName string, opts minio.MakeBucketOptions) error
	PutObject(ctx context.Context, bucketName, objectName string, reader io.Reader, objectSize int64,
	opts minio.PutObjectOptions) (info minio.UploadInfo, err error)
}

// Use to mock:

type moctObjectStore struct {
}

func (m moctObjectStore) MakeBucket(ctx context.Context, bucketName string, opts minio.MakeBucketOptions)  error {
	return nil
}

func (m moctObjectStore) PutObject(ctx context.Context, bucketName, objectName string, reader io.Reader, objectSize int64,
	opts minio.PutObjectOptions) (info minio.UploadInfo, err error) {
	return minio.UploadInfo{/* TODO: Fill */}, nil
}

Thanks a lot for your detailed explanation! Thanks a lot for your help, @klauspost !

repo: minio/minio-go


text:
Stats

This PR implements the first stage of producing a dashboard to track the daily number of claims that are being
submitted.  It models a statistics table to store the results, and the first collector, to store the number of submitted claims.
It does not yet implement the cron job to record this information daily, nor the gecko API.

👍  When building the API endpoints bear in mind please that we may wish to pull this information out in the future with other clients - the LAA have a data store called MI which stores a wide array of performance metrics and their Integration Hub is currently pushing data to it from APIs in existing apps.

authors: slorek stephenrichards


text:
Dependence on xcontour package

I'm opening a new issue here to continue the discussion on the issue of the xcontour dependence that we started here.

The dependence of xcontour is a bit complicated. It is another package I've written here. So the example of reference state, which is newly added, depends on xcontour to prepare the forcing (actually preparing the forcing data is not the core part of xinvert). This is not necessary for other examples. So far, I don't have any plan to get xcontour released as a conda package, so it is not possible to add this to conda dependency. Do you have any suggestion? I really like this example to remain in the problem list.

Is there a way to precompute M(Q) and C(Q) with xcontour and in the https://xinvert.readthedocs.io/en/latest/notebooks/05_reference_SWM.html example, and just load these states from netcdf if xcontour is not available? You could  then adapt the notebook as follows:
try:
    import xcontour
    # do xcontour computation in this notebook, as you do now
except ImportError:
    ds = xr.open_dataset(your_precomputed_dataset)

This is part of the review process at https://github.com/openjournals/joss-reviews/issues/5510.

Oh yes, that's a nice workaround.  I should do this follow your suggestion.

It is fixed now at here

Great! I'm closing this issue.

authors: NoraLoose miniufo

repo: miniufo/xinvert


text:
Fix testresample.c output span; add exit code

Prior to this chance, the "Resample with different factors" test only passed for 60 of the 63 factors, with the 3 failing ones being the largest.

Since only 63 distinct factors were being considered, 100 random samples was overkill.
To support noticing failure in continuous build systems, it's nice if the test exit()s with nonzero when there are failures.
The root cause was a formula error when determining which indices in the resampled output ought be compared. Details are explained in a comment.

@minorninth Just a ping to take a look at this; this PR would fix the testing machinery added in https://github.com/minorninth/libresample/pull/8. If you could merge this and tag a 0.1.5 release on the GitHub repository it’d be great for us and other downstreams :)

authors: emilazy matt-har-vey

repo: minorninth/libresample


text:
Added Github Profile evaristocuesta

Gracias por considerar añadir mi Github Profile.
He desarrollado un profile que se genera dinámicamente con Github Actions, .Net5 y C# donde puedes jugar al Buscaminas.

Gracias por compartir tu perfil! y perdona que hasta ahora lo he aprobado.
Un saludo

Muchas gracias por aceptar el PR.
Un saludo!

authors: evaristocuesta minoveaz


text:
🛑 Matrix is down

In 1236e93, Matrix (https://matrix.mint.lgbt:8448/_matrix/federation/v1/version) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Matrix is back up in 8ccba9d after 15 minutes.

repo: mint-lgbt/status


text:
🛑 Matrix is down

In e287c3c, Matrix (https://matrix.mint.lgbt:8448/_matrix/federation/v1/version) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Matrix is back up in 6ca3607 after 8 minutes.


text:
🛑 Matrix is down

In d86de12, Matrix (https://matrix.mint.lgbt:8448/_matrix/federation/v1/version) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Matrix is back up in 7ffaed8.