IntelliSense and Snippet Stop working after few saves.

VSCode Version: Code 1.17.0
OS Version: Windows_NT x64 10.0.15063

After recent update, the intelliSense and Snippet stop working on any languages after few saves. Turning off extensions does not solve problems.

i never signed up for this account I would appericate you finding out and getting back to me<PHONE_NUMBER> perior number<PHONE_NUMBER> also mail setting perior were<EMAIL_ADDRESS>i would alsi be greatful to have you help me find the intuder
thanks
C.L

On Oct 8, 2017, at 5:13 PM, APrather<EMAIL_ADDRESS>wrote:
VSCode Version: Code 1.17.0
OS Version: Windows_NT x64 10.0.15063
After recent update, the intelliSense and Snippet stop working on any languages after few saves. Turning off extension does not solve problems.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

someone is using u to hack my accounts
C.L

On Oct 8, 2017, at 5:13 PM, APrather<EMAIL_ADDRESS>wrote:
VSCode Version: Code 1.17.0
OS Version: Windows_NT x64 10.0.15063
After recent update, the intelliSense and Snippet stop working on any languages after few saves. Turning off extension does not solve problems.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

please HELP me
C.L

On Oct 8, 2017, at 5:18 PM, Corey Lendo<EMAIL_ADDRESS>wrote:
i never signed up for this account I would appericate you finding out and getting back to me<PHONE_NUMBER> perior number<PHONE_NUMBER> also mail setting perior were<EMAIL_ADDRESS>i would alsi be greatful to have you help me find the intuder
thanks
C.L

On Oct 8, 2017, at 5:13 PM, APrather<EMAIL_ADDRESS>wrote:
VSCode Version: Code 1.17.0
OS Version: Windows_NT x64 10.0.15063
After recent update, the intelliSense and Snippet stop working on any languages after few saves. Turning off extension does not solve problems.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have same issue. Saving takes a longer time as well. Noticed on 2 different macs.

Could you post the list of extensions you have installed? (code --list-extensions)

I have found that after I try import a file, it just stops working. I stop getting suggestions, and the intellisense stops working, along with the auto format, along with some plugins.
The import suggestions start working, and suddenly stop.
I removed all extensions and it happens anyway.

code --list-extensions
CraigMaslowski.erb
abusaidm.html-snippets
dbaeumer.vscode-eslint
dhoeric.ansible-vault
donjayamanne.githistory
formulahendry.auto-close-tag
formulahendry.auto-rename-tag
haaaad.ansible
joshpeng.theme-onedark-sublime
mjmcloug.vscode-elixir
rebornix.Ruby
robertohuertasm.vscode-icons
xabikos.JavaScriptSnippets
xabikos.ReactSnippets
zhuangtongfa.Material-theme

After recent update, the intelliSense and Snippet stop working on any languages after few saves.

What does that mean? Do you see loading forever and ever? Does it only suggest words and nothing smart? Do other language features, like error squiggles, still work?

Same issue here. IntelliSense (object props, imports, user snippets) stops working after a while in 1.17. If i try to force IntelliSense by ctrl+space "loading..." is displayed but no result.
It's also not possible to navigate to imports using F12, the blue loading indicator is displayed but nothing happens.
No extensions enabled and nothing in the developer tools console.
Squiggles still works. But light bulb for e.g. eslint fixes is not shown.

@Jimbo80 Thanks for the info. It sounds like the language service, that is providing the smarts, stopped responding. Is this in JavaScript/TypeScript or another language?

@jrieken It's JavaScript.
I might figured out how to reproduce this. Seems like it has to do with imports and incorrect paths.
If I try to write an import like:
import SearchInput from 'src/SearchInput';
But misspell the path to something that doesn't exist and hit ctrl+space:
import SearchInput from 'scr/<press ctrl+space for suggestions> ';
This seems to trigger the issue for me.

Are any of VS Code child-process running busy? Can you craft a small sample that reproduces this?

I don't see any increase in process activity for intellisens "loading...", but for F12 navigation to imports one of the child processes is running busy.
I'm trying to create a small sample but I have not been able to reproduce the issue in the sample yet.

Seeing the same issue here. Was able to replicate the issue once using @Jimbo80's steps, but only the first time for some reason. Lock appeared to happen when I hit save.
extensions:
abusaidm.html-snippets
akamud.vscode-theme-onedark
alefragnani.project-manager
be5invis.vscode-custom-css
christian-kohler.npm-intellisense
christian-kohler.path-intellisense
CoenraadS.bracket-pair-colorizer
dbaeumer.vscode-eslint
donjayamanne.githistory
eg2.tslint
eg2.vscode-npm-script
esbenp.prettier-vscode
formulahendry.auto-close-tag
humao.rest-client
ilich8086.classic-asp
leizongmin.node-module-intellisense
lonefy.vscode-JS-CSS-HTML-formatter
mrmlnc.vscode-scss
ms-mssql.mssql
ms-vscode.atom-keybindings
ms-vscode.csharp
ms-vscode.PowerShell
msjsdiag.debugger-for-chrome
patrys.vscode-code-outline
PeterJausovec.vscode-docker
PKief.material-icon-theme
robinbentley.sass-indented
Shan.code-settings-sync
TwentyChung.jsx
wesbos.theme-cobalt2
xabikos.JavaScriptSnippets
zhuangtongfa.Material-theme

I'm experiencing the same behavior Jimbo80 described. I'm using typescript and was doing some refactoring and changing file paths on imports (and renames).
Neither renaming (f2), find reference (f12) nor intellisense worked alter a while (a minute or so) and I found that one of the code.exe processes where using one cpu at something near 80%.
aurelia|Aur|0.3.4
Aurelia|beh|1.2.2
vscode-generate-getter-setter|DSK|0.4.2
gitlens|eam|5.6.0
tslint|eg2|1.0.11
Ionide-fsharp|Ion|3.5.1
Angular2|joh|2.7.0
azure-functions-tools|joh|0.3.1
vscode-JS-CSS-HTML-formatter|lon|0.2.3
vscode-apache|mrm|1.1.1
mssql|ms-|1.2.0
csharp|ms-|1.12.1
PowerShell|ms-|1.4.3
azurerm-vscode-tools|msa|0.3.7
standard|shi|0.2.3
nativescript|Tel|0.7.2
python|tht|0.2.3

@azterix / @patrick-mackay Do this still occur if you disable all extensions? If it does, can you please try getting the full command line arguments of the process that has the high cpu usage. This will help us track down what is causing this issue

@mjbvz , with extensions disabled the issue does not occur. All renamings, find reference and intellisense work as expected.
This is the command line with extensions enabled of the process.
"C:\Program Files\Microsoft VS Code\Code.exe" --type=renderer --js-flags=--nolazy --no-sandbox --primordial-pipe-token=FA4E83C44A93426C4A413550185752D9 --lang=en-US --app-user-model-id=Microsoft.VisualStudioCode --app-path="C:\Program Files\Microsoft VS Code\resources\app" --node-integration=true --webview-tag=true --no-sandbox --background-color=#1e1e1e --disable-blink-features=Auxclick --enable-pinch --device-scale-factor=1 --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553 --service-request-channel-token=FA4E83C44A93426C4A413550185752D9 --renderer-client-id=4 --mojo-platform-channel-handle=2152 /prefetch:1

After enabling all the extensions,
I opened the Developer Tools and found that after renaming the file, adjunting the import accordingly and try a Goto Definition, if failed but this was logged on the console.
[msazurermtools.azurerm-vscode-tools] Cannot read property 'indexOf' of null: TypeError: Cannot read property 'indexOf' of null
at Function.AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (C:\Users\Patrick.vscode\extensions\msazurermtools.azurerm-vscode-tools-0.3.7\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:155:47)
at Function.NativeError.prepareStackTrace (C:\Users\Patrick.vscode\extensions\msazurermtools.azurerm-vscode-tools-0.3.7\node_modules\zone.js\dist\zone-node.js:900:30)
at consoleError (C:\Users\Patrick.vscode\extensions\msazurermtools.azurerm-vscode-tools-0.3.7\node_modules\zone.js\dist\zone-node.js:420:240)
at _loop_1 (C:\Users\Patrick.vscode\extensions\msazurermtools.azurerm-vscode-tools-0.3.7\node_modules\zone.js\dist\zone-node.js:449:25)
at drainMicroTaskQueue (C:\Users\Patrick.vscode\extensions\msazurermtools.azurerm-vscode-tools-0.3.7\node_modules\zone.js\dist\zone-node.js:453:21)
at
e.onUnexpectedError @ shell.ts:454
(anonymous) @ shell.ts:414
e.onUnexpectedError @ errors.ts:119
o @ errors.ts:138
e.$onUnexpectedError @ mainThreadErrors.ts:26
e.invoke @ abstractThreadService.ts:41
e._invokeHandler @ rpcProtocol.ts:109
e._receiveOneMessage @ rpcProtocol.ts:96
(anonymous) @ rpcProtocol.ts:32
(anonymous) @ rpcProtocol.ts:157
e.invoke @ callbackList.ts:36
e.fire @ event.ts:123
(anonymous) @ ipc.net.ts:82
emitOne @ events.js:96
emit @ events.js:191
readableAddChunk @ _stream_readable.js:178
Readable.push @ _stream_readable.js:136
onread @ net.js:560
I disabled that extension, reloaded, and tried it again. Now it logged this on the console, but the renaming, gotos and intellisense worked as usual.
shell.ts:454 Cannot read property 'length' of undefined: TypeError: Cannot read property 'length' of undefined
at DefinitionProvider.containsItem (C:\Users\Patrick.vscode\extensions\DSKWRK.vscode-generate-getter-setter-0.4.2\out\src\provider.js:52:48)
at C:\Users\Patrick.vscode\extensions\DSKWRK.vscode-generate-getter-setter-0.4.2\out\src\bulb.js:10:56
at Promise ()
at CompleteActionProvider.provideCodeActions (C:\Users\Patrick.vscode\extensions\DSKWRK.vscode-generate-getter-setter-0.4.2\out\src\bulb.js:7:16)
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:372505
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:66174
at new n.Class.derive._oncancel (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:51364)
at Object.t.asWinJsPromise (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:66137)
at e.provideCodeActions (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:372459)
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:383686
e.onUnexpectedError @ shell.ts:454
(anonymous) @ shell.ts:414
..... (removed)
I disabled that extension, reloaded, and tried it again. Now it logged this on the console, but the renaming, gotos and intellisense worked as usual.
shell.ts:454 [eamodio.gitlens] this is not defined: ReferenceError: this is not defined
at GitUri (C:\Users\Patrick.vscode\extensions\eamodio.gitlens-5.6.0\out\src\git\gitUri.js:32:13)
at GitContextTracker. (C:\Users\Patrick.vscode\extensions\eamodio.gitlens-5.6.0\out\src\git\gitContextTracker.js:73:60)
at Generator.next ()
at C:\Users\Patrick.vscode\extensions\eamodio.gitlens-5.6.0\out\src\git\gitContextTracker.js:7:71
at Promise ()
at __awaiter (C:\Users\Patrick.vscode\extensions\eamodio.gitlens-5.6.0\out\src\git\gitContextTracker.js:3:12)
at Timeout.setTimeout [as _onTimeout] (C:\Users\Patrick.vscode\extensions\eamodio.gitlens-5.6.0\out\src\git\gitContextTracker.js:70:26)
at ontimeout (timers.js:386:14)
at tryOnTimeout (timers.js:250:5)
at Timer.listOnTimeout (timers.js:214:5)
e.onUnexpectedError @ shell.ts:454
(anonymous) @ shell.ts:414
e.onUnexpectedError @ errors.ts:119
o @ errors.ts:138
e.$onUnexpectedError @ mainThreadErrors.ts:26
e.invoke @ abstractThreadService.ts:41
e._invokeHandler @ rpcProtocol.ts:109
e._receiveOneMessage @ rpcProtocol.ts:96
(anonymous) @ rpcProtocol.ts:32
(anonymous) @ rpcProtocol.ts:157
e.invoke @ callbackList.ts:36
e.fire @ event.ts:123
(anonymous) @ ipc.net.ts:82
emitOne @ events.js:96
emit @ events.js:191
readableAddChunk @ _stream_readable.js:178
Readable.push @ _stream_readable.js:136
onread @ net.js:560
After many attemps, I can say that having this extension enabled (msazurermtools.azurerm-vscode-tools) was hanging my installation.
In the last hang, this are de processes that are using the CPU.

I guess that the gpu process is consuming 3% since it's displaying that horizontal line scrolling

After switching windows, the CPU goes normal again... but the issue stills occurs.

"C:\Program Files\Microsoft VS Code\Code.exe" --type=renderer --js-flags=--nolazy --no-sandbox --primordial-pipe-token=CA2B0A01A28AAC351C7E721157CCE6B1 --lang=en-US --app-user-model-id=Microsoft.VisualStudioCode --app-path="C:\Program Files\Microsoft VS Code\resources\app" --node-integration=true --webview-tag=true --no-sandbox --background-color=#1e1e1e --disable-blink-features=Auxclick --enable-pinch --device-scale-factor=1 --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553 --service-request-channel-token=CA2B0A01A28AAC351C7E721157CCE6B1 --renderer-client-id=20 --mojo-platform-channel-handle=4588 /prefetch:1

I finally been able to reproduce the issue in "small" sample, but only after including all dependencies from one of our large projects in package.json.
Further more we are only able to reproduce the issue when using yarn, using npm will not trigger this for us!? 😕
Repo: https://github.com/Jimbo80/35847.git
Steps:

Use yarn to install dependencies.
Hammer the import in src/index.js. It's not super easy to trigger, you must save + type + save + ctrl+space + save.... and so on. Sometimes it's triggered immediately, sometimes you need to work for it :) Feels like the faster you type and save etc, the easier it is to reproduce.

We have been able to reproduce this on three different computers (win10 and server 2016) using this repo. Extensions does not seem to matter for us.

Not sure if it's related but I'm using yarn as well. I haven't tested without extensions yet, but I did notice that when triggered the condition just now and I mouse over what I just imported the ~tooltip popup is stuck on a 'Loading...' message:

This is also a project with a lot of dependencies pulled in directly under node_modules (946 items).

Having the same issue with mine. It seems to occur when trying to run Intellisense on import statements in local relative paths. Working in an existing file without touching imports everything was working fine. I created a new .jsx file and did:
import React from 'react';
import moment from 'moment';
import styled from 'styled-components';

import {InputGroup, Label} from './field-wrap';

and the intellisense blew up. Trying to invoke it with ctrl+space just presents "Loading...".
I've been able to duplicate this multiple times with these lines. Sometimes it blows up on the second line, sometimes not until the last one. Like @Jimbo80 said, it seems like the faster you type the import statements the easier it is to blow up.
I'm running on Win10 using yarn for package management, and have gotten this to break with extensions enabled as well as disabled. I'm not seeing any error messages in the dev tools console.

Seems like multiple separate issues are being reported in this thread. Please try out vscode insiders to see if your issue has been resolved. If it has not,  open a new issue so that we better track the individual problems being hit

@aprather51 Do you still see this bug on VS Code insiders?


Access ZITADEL APIs guide outdated

With v2 the following guide needs to be updated:
https://docs.zitadel.com/docs/guides/api/access-zitadel-apis
The scope urn:zitadel:iam:org:project:id:69234237810729019:aud changes for every instance. To find out the correct ID, a user must navigate to the domain-org and select the project ZITADEL.

Also references to zitadel.ch should be removed.

IMO we should also take a look at it in #3573 and we'll have to change this the following section anyway so we could as well state it there

I think @livio-a is right we should display that info directly to the user.
Btw. Some of that info is already present in the env.json

update the scopes / guides in #4112

Since #4112 was merged I think we can /close this


[BUG] Error on import with new release

Ever since the recent release, one of our CI pipeline fails with this error:
ImportError while importing test module '/Users/runner/work/polars/polars/py-polars/tests/unit/io/test_delta.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/unit/io/test_delta.py:10: in <module>
    from deltalake import DeltaTable
../.venv/lib/python3.12/site-packages/deltalake/__init__.py:1: in <module>
    from ._internal import __version__ as __version__
E   ImportError: dlopen(/Users/runner/work/polars/polars/.venv/lib/python3.12/site-packages/deltalake/_internal.abi3.so, 0x0002): symbol not found in flat namespace '_PyPyBaseObject_Type'

Link to the job:
https://github.com/pola-rs/polars/actions/runs/9407528634/job/25914397270
I cannot reproduce this locally, but perhaps you know what's going on?

Sorry, wrong repo. Will move this to delta-rs.


Updated the Write Dataframe function to change the order as per cube dimension Order

Updated the Write Data frame function to change the order as per cube dimension Order by passing the parameter of Change_the_order flag as True so function will rearrange the data frame order

Closed in favour of #1142


Use PasswordProvider, fix info on initial passwords in basic security extension docs

Use PasswordProvider for the initial passwords and adds a missing "not" to the docs for the initial password properties.

@jon-wei  this is failing tests


fix typo in schema-directives.md

TODO:

[ ] If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
[ ] Make sure all of the significant new logic is covered by tests
[ ] Rebase your changes on master so that they can be merged easily
[ ] Make sure all tests and linter rules pass
[x] Update CHANGELOG.md with your change. Include a description of your change, link to PR (always) and issue (if applicable). Add your CHANGELOG entry under vNEXT. Do not create a new version number for your change yourself.

Thanks!


Fix the plane_offset() function of BlockOffset struct for chroma planes

Currently,  plane_offset() function of BlockOffset struct for chroma cannot be used since it gives wrong results due to partitions occurring inside a SB.
Prior to introducing partition of 64x64 SB, it worked correct. However, once partition occur the blockoffset of luma cannot be used to derive the offset for chroma block.

Fix is ready at:
https://github.com/ycho/rav1e/commit/b66fb54723b4edc4a75e83255ec1e69601004715
but it bases on PR https://github.com/xiph/rav1e/pull/425, so waiting for it lands.


Escape Characters

In the XML parser, handle the standard XML escape characters: &, ', ", <, >

Please add test(s) for escape characters to the parsexml module

These tests are in the conformance suite, so ignore previous comment


Asynchronize prefix predicates

Currently prefix predicates take a return type of int, and thus have to run synchronously. This prevents using asynchronous code inside them. They should be changed to return Task<int> instead, allowing for easy use of asynchronous code.
This is mildly breaking, thus should be released for 2.3.

Done in v2.3.


Clicking actions sometimes not works.

Hi, when player creates shop, sometimes he can't remove it, and admin can't remove it too. Admin can only selling / buying items on right or left click, when is entered command "/shop remove". Player (the owner of the shop) getting no action when is right/left clicked.
Same for "/shop info" and "/shop create"
Sometimes it works well, sometimes not, where is error?

Please enable debug log in the config, reload or restart the server, wait until the error appears again and send me the content of the debug.txt file found in this plugin's folder.


Go To Definition not working for private functions

My project have a class with private and public functions like:
class MyClass {
public function __construct() {
echo $this->pub();  // -> Go to definition work
echo $this->priv();  // -> Go to definition doesnt work
}
public function pub() {}
private function priv() {}
}
Is that correct?

It worked. Thanks


Add more unit tests covering the pgsql db relation part

Unit tests for the PostgreSQL database are currently missing due to the ops-lib-pgsql lib needs hook-tools commands.
Add the necessary patch to work around that and add some unit tests for the pgsql db relation.

Bump up the overall test coverage to 90%

LGTM. Unfortunatelly, you'll have to rebase once the linting fix gets merged

Looks like you've got some lint failures there:
tests/unit/_patched_charm.py:4:1: D205 1 blank line required between summary line and description
tests/unit/_patched_charm.py:4:1: D415 First line should end with a period, question mark, or exclamation point
tests/unit/_patched_charm.py:6:100: W505 doc line too long (100 > 99 characters)

Looks like you've got some lint failures there:
tests/unit/_patched_charm.py:4:1: D205 1 blank line required between summary line and description
tests/unit/_patched_charm.py:4:1: D415 First line should end with a period, question mark, or exclamation point
tests/unit/_patched_charm.py:6:100: W505 doc line too long (100 > 99 characters)

Yes, the rules are very strict, checking right now

Sorry about all the error messages, I have created a GitHub action using GitHub Script to add a comment about the test coverage status in evert pull request. Due to the Github repository permission issues, this action will not success unless it was merged into this repo's main branch.
Please see this GitHub Action's result and check the comment message example in my forked repo.

Sorry about all the error messages, I have created a GitHub action using GitHub Script to add a comment about the test coverage status in evert pull request. Due to the Github repository permission issues, this action will not success unless it was merged into this repo's main branch.
Please see this GitHub Action's result and check the comment message example in my forked repo.

Are you sure PRs from a fork will work? Maybe we'd need to specify the permissions in the WF:
permissions:
      issues: write

Sorry about all the error messages, I have created a GitHub action using GitHub Script to add a comment about the test coverage status in evert pull request. Due to the Github repository permission issues, this action will not success unless it was merged into this repo's main branch.
Please see this GitHub Action's result and check the comment message example in my forked repo.

Are you sure PRs from a fork will work? Maybe we'd need to specify the permissions in the WF:
permissions:
      issues: write

I just did some experiments, it seems like the forked repository will not have write permission in anyway, so I think I will just scratch this feature.

Sorry about all the error messages, I have created a GitHub action using GitHub Script to add a comment about the test coverage status in evert pull request. Due to the Github repository permission issues, this action will not success unless it was merged into this repo's main branch.
Please see this GitHub Action's result and check the comment message example in my forked repo.

Are you sure PRs from a fork will work? Maybe we'd need to specify the permissions in the WF:
permissions:
      issues: write

I just did some experiments, it seems like the forked repository will not have write permission in anyway, so I think I will just scratch this feature.

It would certainly be useful to post the cause of the PR breaking as a comment. Perhaps we can try in the near future if there's any way to do it

Sorry about all the error messages, I have created a GitHub action using GitHub Script to add a comment about the test coverage status in evert pull request. Due to the Github repository permission issues, this action will not success unless it was merged into this repo's main branch.
Please see this GitHub Action's result and check the comment message example in my forked repo.

Are you sure PRs from a fork will work? Maybe we'd need to specify the permissions in the WF:
permissions:
      issues: write

I just did some experiments, it seems like the forked repository will not have write permission in anyway, so I think I will just scratch this feature.

It would certainly be useful to post the cause of the PR breaking as a comment. Perhaps we can try in the near future if there's any way to do it

I think a bot / service account like Juju bot can certainly do that, but I think that would be too complicated for today.


[CI] QNN Compilation Error During Bionic Docker Update

In the past week I attempted to upgrade the docker image CPU to bionic(ubuntu 18.04), during the time, a new unittest error occurs(note that the master CI was fine) in the int8 intrinsic test,
it would be great it we can look into it. To reproduce, use the docker image tvmai/ci-cpu:v0.62-t0
http://ci.tvm.ai:8080/job/temp-ci-docker-staging/job/ci-stage/30/execution/node/131/log/

cc @anijain2305

self = <tvm.runtime.packed_func.PackedFunc object at 0x7fe439b9f630>
args = (IRModuleNode( {GlobalVar(main): FunctionNode([Var(x, ty=TensorType([1, 1, 64, 64], uint8))], TensorType([1, 16, 64, 6...Type([1, 1, 64, 64], uint8), TensorType([16, 1, 3, 3], int8)]), [], (nullptr))}), {1: llvm -mcpu=skylake-avx512}, None)
temp_args = [{1: llvm -mcpu=skylake-avx512}]
values = <tvm._ffi._ctypes.packed_func.TVMValue_Array_3 object at 0x7fe43985c510>
tcodes = <tvm._ffi._ctypes.packed_func.c_int_Array_3 object at 0x7fe43986fea0>

    def __call__(self, *args):
        """Call the function with positional arguments

        args : list
           The positional arguments to the function call.
        """
        temp_args = []
        values, tcodes, num_args = _make_tvm_args(args, temp_args)
        ret_val = TVMValue()
        ret_tcode = ctypes.c_int()
        if _LIB.TVMFuncCall(
                self.handle, values, tcodes, ctypes.c_int(num_args),
                ctypes.byref(ret_val), ctypes.byref(ret_tcode)) != 0:
>           raise get_last_ffi_error()
E           tvm._ffi.base.TVMError: Traceback (most recent call last):
E             [bt] (8) /workspace/build/libtvm.so(+0x95e727) [0x7fe426761727]
E             [bt] (7) /workspace/build/libtvm.so(+0x96e3b4) [0x7fe4267713b4]
E             [bt] (6) /workspace/build/libtvm.so(+0x969334) [0x7fe42676c334]
E             [bt] (5) /workspace/build/libtvm.so(+0x96fd39) [0x7fe426772d39]
E             [bt] (4) /workspace/build/libtvm.so(+0x95e727) [0x7fe426761727]
E             [bt] (3) /workspace/build/libtvm.so(+0x96e1e9) [0x7fe4267711e9]
E             [bt] (2) /workspace/build/libtvm.so(+0x940f54) [0x7fe426743f54]
E             [bt] (1) /workspace/build/libtvm.so(+0x94c913) [0x7fe42674f913]
E             [bt] (0) /workspace/build/libtvm.so(+0xa9f52b) [0x7fe4268a252b]
E             File "/workspace/python/tvm/relay/backend/_backend.py", line 49, in lower
E               f = tvm.driver.lower(sch, inputs, name=func_name)
E             File "/workspace/python/tvm/driver/build_module.py", line 215, in lower
E               mod = optimize(mod)
E             File "/workspace/python/tvm/ir/transform.py", line 141, in __call__
E               return _ffi_transform_api.RunPass(self, mod)
E             File "/workspace/python/tvm/_ffi/_ctypes/packed_func.py", line 219, in __call__
E               raise get_last_ffi_error()
E             [bt] (8) /workspace/build/libtvm.so(tvm::tir::ExprVisitor::VisitExpr_(tvm::tir::LoadNode const*)+0x16) [0x7fe4261e0cf6]
E             [bt] (7) /workspace/build/libtvm.so(+0x4bf027) [0x7fe4262c2027]
E             [bt] (6) /workspace/build/libtvm.so(tvm::arith::ConstIntBoundAnalyzer::operator()(tvm::PrimExpr const&, std::unordered_map<tvm::PrimExprNode const*, tvm::arith::ConstIntBound, std::hash<tvm::PrimExprNode const*>, std::equal_to<tvm::PrimExprNode const*>, std::allocator<std::pair<tvm::PrimExprNode const* const, tvm::arith::ConstIntBound> > >*)+0x1b) [0x7fe42600882b]
E             [bt] (5) /workspace/build/libtvm.so(+0x20da92) [0x7fe426010a92]
E             [bt] (4) /workspace/build/libtvm.so(+0x20f1a9) [0x7fe4260121a9]
E             [bt] (3) /workspace/build/libtvm.so(+0x20da92) [0x7fe426010a92]
E             [bt] (2) /workspace/build/libtvm.so(+0x20e27b) [0x7fe42601127b]
E             [bt] (1) /workspace/build/libtvm.so(+0x20dd2f) [0x7fe426010d2f]
E             [bt] (0) /workspace/build/libtvm.so(+0x12a65c) [0x7fe425f2d65c]
E             File "/workspace/src/arith/const_int_bound.cc", line 157
E             File "/workspace/python/tvm/_ffi/_ctypes/packed_func.py", line 78, in cfun
E               rv = local_pyfunc(*pyargs)
E             File "/workspace/python/tvm/relay/backend/_backend.py", line 57, in lower
E               raise RuntimeError(msg)
E             File "/workspace/python/tvm/relay/backend/_backend.py", line 49, in lower
E               f = tvm.driver.lower(sch, inputs, name=func_name)
E             File "/workspace/python/tvm/driver/build_module.py", line 215, in lower
E               mod = optimize(mod)
E             File "/workspace/python/tvm/ir/transform.py", line 141, in __call__
E               return _ffi_transform_api.RunPass(self, mod)
E             File "/workspace/python/tvm/_ffi/_ctypes/packed_func.py", line 219, in __call__
E               raise get_last_ffi_error()
E             [bt] (8) /workspace/build/libtvm.so(tvm::tir::ExprVisitor::VisitExpr_(tvm::tir::LoadNode const*)+0x16) [0x7fe4261e0cf6]
E             [bt] (7) /workspace/build/libtvm.so(+0x4bf027) [0x7fe4262c2027]
E             [bt] (6) /workspace/build/libtvm.so(tvm::arith::ConstIntBoundAnalyzer::operator()(tvm::PrimExpr const&, std::unordered_map<tvm::PrimExprNode const*, tvm::arith::ConstIntBound, std::hash<tvm::PrimExprNode const*>, std::equal_to<tvm::PrimExprNode const*>, std::allocator<std::pair<tvm::PrimExprNode const* const, tvm::arith::ConstIntBound> > >*)+0x1b) [0x7fe42600882b]
E             [bt] (5) /workspace/build/libtvm.so(+0x20da92) [0x7fe426010a92]
E             [bt] (4) /workspace/build/libtvm.so(+0x20f1a9) [0x7fe4260121a9]
E             [bt] (3) /workspace/build/libtvm.so(+0x20da92) [0x7fe426010a92]
E             [bt] (2) /workspace/build/libtvm.so(+0x20e27b) [0x7fe42601127b]
E             [bt] (1) /workspace/build/libtvm.so(+0x20dd2f) [0x7fe426010d2f]
E             [bt] (0) /workspace/build/libtvm.so(+0x12a65c) [0x7fe425f2d65c]
E             File "/workspace/src/arith/const_int_bound.cc", line 157
E           TVMError: Check failed: (val->second->min_value == res.min_value && val->second->max_value == res.max_value) || (val->second->min_value == everything.min_value && val->second->max_value == everything.max_value): Detected bound for 15conflicts with memorization
E           During handling of the above exception, another exception occurred:
E
E           TVMError: Check failed: (val->second->min_value == res.min_value && val->second->max_value == res.max_value) || (val->second->min_value == everything.min_value && val->second->max_value == everything.max_value): Detected bound for 15conflicts with memorization
E           Error during compile function
E           -----------------------------
E           v0.0.4
E           fn (%p0: Tensor[(1, 1, 64, 64, 4), uint8], %p1: Tensor[(1, 1, 3, 3, 1, 16, 4), int8], Primitive=1) -> Tensor[(1, 1, 64, 64, 16), int32] {
E             nn.contrib_conv2d_NCHWc(%p0, %p1, padding=[1, 1, 1, 1], channels=16, kernel_size=[3, 3], data_layout="NCHW4c", out_layout="NCHW16c", out_dtype="int32") /* ty=Tensor[(1, 1, 64, 64, 16), int32] */
E           }

The error has things to do with constant int bound rebound to a different result.

also cc @yongfeng-nv @hzfan since both of you have touched/reviewed the const int bound recently

I also saw this error when running test_op_level2.py locally. It happens randomly.

Ran the test in tvmai/ci-cpu:v0.62-t0, but couldn't reproduce the failure.
I cloned and built TVM by myself, as I I didn't find TVM in the docker image.

I was able to reproduce the failure. I have not been able to solve it yet. The only pointer that I have till now is that if I disable tensorize (this test uses tensorize to use Intel VNNI), the test progresses.
I am not familiar with const int bound. I will try to get familiar with it and see how tensorize impacts const int bounds.

Dug little bit deeper, but still not able to root cause.
I think the const int bounds are good.
https://github.com/apache/incubator-tvm/blob/7e88030a804357421b766d7309f9085ca2b83378/src/arith/const_int_bound.cc#L149-L161
The problem here is that two different PrimExpr have same PrimExprNode* at L150
tvm/src/arith/const_int_bound.cc:166: Expr --> 63, op = 0x3b73800
tvm/src/arith/const_int_bound.cc:154: Expr --> 15, op = 0x3b73800

And therefore, Expr(63) whose ConstIntBound is set correctly to [63, 63] is used to compare the bounds for Expr(15), causing failure. Will pursue this direction, please let me know of any suggestions @tqchen

@tqchen I verified locally. This is resolved now. You can close this.


Fails to build when using a uClibc toolchain

It fails to build because it tries to use eventfd_read and eventfd_write which are not implemented in uClibc:
../../libwinpr/synch/libwinpr-synch.so.0.1.0: undefined reference to `eventfd_read'
../../libwinpr/synch/libwinpr-synch.so.0.1.0: undefined reference to `eventfd_write'

That could be fixed by adding this to winpr/libwinpr/synch/event.c:
#if defined(__UCLIBC__)
int eventfd_read(int fd, eventfd_t* value) {
       return (read(fd, value, sizeof(*value)) == sizeof(*value)) ? 0 : -1;
}

int eventfd_write(int fd, eventfd_t value) {
       return (write(fd, &value, sizeof(value)) == sizeof(value)) ? 0 : -1;
}
#endif

But, it's also using futimes in channels/drive/client/drive_file.c, which is not implemented in uClibc either:
[100%] Building C object client/X11/cli/CMakeFiles/xfreerdp-cli.dir/xfreerdp.c.o
Linking C executable ../xfreerdp
../../common/libfreerdp-client.so.1.1.0: undefined reference to `futimes'

Fixed on master.


Minor formatting update for internal/writing-a-blog-post.md, so that numbered list appears correctly

Observed:

Hm, that didn't resolve it, so I just created an issue for now https://github.com/mattermost/mattermost-developer-documentation/issues/234


WIP: Adding description of locked roles

In the place of "Global Admin" should we say just "Admin" user?

LGTM

Say “default admin”. Use the name listed on the Users page.
From: Sangeetha Hariharan<EMAIL_ADDRESS>Reply-To: rancher/docs<EMAIL_ADDRESS>Date: Tuesday, June 5, 2018 at 3:35 PM
To: rancher/docs<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [rancher/docs] WIP: Adding description of locked roles (#208)
In the place of "Global Admin" should we say just "Admin" user?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/rancher/docs/pull/208#issuecomment-394882328, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkDxfClKZIE03OcDCRC4ITaCyq98wibbks5t5wfLgaJpZM4UboNF.

Technically it's any user with the Administrator permission, I misspoke earlier.

@MBishop17 ready for you!


Default version need to follow official Version Priority

When multiple versions are described in the CRD and no --api-version flag is given it may be better to use the one that is specified in storedVersion of the status, rather than just the first one.

Well, after giving this more thoughts - no, it is not better.

IMO, this should either align with kubectl (whatever its behaviour is, I'll admit I haven't tried this yet) or always be required.

Ah, here we go - Version Priority

And here seems to be the Golang implementation

As a side-note, we do have code for the version policy in kube-client/discovery, but it's private: https://github.com/kube-rs/kube-rs/blob/master/kube-client/src/discovery/version.rs

Oh, had no idea. Looks pretty similar and doesn't use regex, which is advantage. So let me know what you want to do with that.


Not able to bundle favicon.ico into build folder

Hello,
My file structure is as follows:
build
dev
-app.js
-public
--favicon.ico
webpack.config.js

And my webpack config file has the following loader:
  {
    test: /\.ico$/,
    loader: "url-loader",
    query: { mimetype: "image/x-icon" }
  }

And my app.js has a require to that ico file:
  var icoFile = require("./public/favicon.ico");

However, after the project is built, there is no favicon.ico file in my public folder. So, how can I tell webpack to include my favicon.ico file inside my build folder?

url-loader base64-encodes the icon. Add limit: 0 to the query, or just use the file-loader

ok, but the file is not being included inside the build/public/ folder

In my webpack config use
{
   test: /\.(jpg|jpeg|gif|png|ico)$/,
   exclude: /node_modules/,
   loader:'file-loader?name=img/[path][name].[ext]&context=./app/images'
}
And my app.js has a require all images

require.context('../images', true, /^\.\//);

This implementation works correctly

@Dindaleon Is this relevant still?

I'm closing this issue because of inactivity. Feel free to comment, and we can always re-open it again.

FYI, here's what I ended up doing in my webpack config (note limit 1, not 0):
      {
        test: /favicon\.ico$/,
        loader: 'url',
        query: {
          limit: 1,
          name: '[name].[ext]',
        },
      },

And in my main.js:
import './favicon.ico'


Add cppcheck

@maoo, I included cppcheck for C++ static code analyses. I am not sure if semgrep it makes sense for us as our java and javascript files are only example projects to use SymphonyMediaBridge
https://github.com/RicardoMDomingues/SymphonyMediaBridge/actions/runs/3496537854/jobs/5854562455

@maoo, I included cppcheck for C++ static code analyses. I am not sure if semgrep it makes sense for us as our java and javascript files are only example projects to use SymphonyMediaBridge

I'll let you and the team to decide; my personal opinion is that it doesn't hurt to give it a try; if and when you feel that semgrep generates noise and doesn't bring any value, you can simply delete the action.
Just merged your action.

@maoo, I included cppcheck for C++ static code analyses. I am not sure if semgrep it makes sense for us as our java and javascript files are only example projects to use SymphonyMediaBridge

I'll let you and the team to decide; my personal opinion is that it doesn't hurt to give it a try; if and when you feel that semgrep generates noise and doesn't bring any value, you can simply delete the action.
Just merged your action.

👍


nextcloud23: 23.0.8 -> 23.0.9, nextcloud24: 24.0.4 -> 24.0.5

Description of changes
https://nextcloud.com/changelog/#23-0-9
https://nextcloud.com/changelog/#24-0-5
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The with-mysql-and-memcached test failed: nextcloud.log

Will look later today.

OK, so I managed to fix the test by reverting https://github.com/nextcloud/server/pull/33513/commits locally.
Will try to find out later what's exactly wrong with the patch.

So... since I'm procrastinating anyways, I just found the cause: Nextcloud tries to recreate a custom DB user with the supplied DB user and generates a secure DB password. Apparently, the commit I linked above always alters the DB password for the MySQL user and because we set the "old" db password in override.config.php, so the db connection fails.
I think it was sheer luck that we haven't encountered this before because the regeneration (AFAIU) would've always happened if the DB user had elevated rights. Hence I'm inclined to patch away the entire behavior since it's inherently incompatible with how we manage Nextcloud in our module.
Also, I guess I'll report this as a bug to Nextcloud because always altering the db password of a user seems wrong to me.

@yayayayaka should be fixed now :)

Good point, done!

Filed https://github.com/nextcloud/server/issues/34123 for the mysql problem.


video player not working on android 12 oppo devices

api not working on android 12 devices specially access live cams

It can work on Android 12

Dear you need to update latest dependency which work on Android Version 12 which is below
implementation 'com.shuyu:GSYVideoPlayer:8.1.2'


Made EaseIn/EaseOut animation default

I made EaseIn/EaseOut anmation default.
It is awesome, beautiful and natural.
reference:
https://www.google.com/design/spec/animation/authentic-motion.html

great :]  i forget to optimize the details such as animations.   thank u


I'm new to GDX, coming into a project using it, and suffered lots of confusion over the SpriteBatch objects, which the documentation says do batching. Although they are a batch, they perform no batching; as any state changes other than vertex streaming simply cause a flush.

They batch to the best of their ability. If you break the batching in a way that SpriteBatch can't recover from, it will flush.

@Tom-Ski I spent the last hour looking at the code, and the 2d batches simply flush upon any texture or shader change.
ModelBatch batches blend state but nothing else.
The SpriteBatch documentation that "The class will batch the drawing commands and optimize them for processing by the GPU." The documentation is claiming the presence of unimplemented features.

@NathanSweet

Yes. It batches each sprite draw call into one big mesh, and submits that draw call together. This is exactly what the docs state. On the wiki the documentation is even more extensive. What feature exactly is the documentation claiming it does, which it doesn't?
ModelBatch does not just batch blend state, and what you linked is the sorting for draw order for blending, not the batching.

I seem to have misunderstood the definition of batching, I thought it was for minimizing overall render state changes via state sorting instead of just mesh combination.
So in that sense the 2d batchers are grammatically correct. However ModelBatch does have vertex combining functionality, as thats mutex with the prebuilt VBOs it accepts.

For that you want something like ModelCache. It handles merging of sepearate meshes where compatible (materials and vertex layout/blending compatible) Its an expensive operation and shouldn't be done every frame for most use cases.

We will not rename these classes. Sorry.
On Mar 27, 2018 10:37 PM, "khlorghaal"<EMAIL_ADDRESS>wrote:
I seem to have misunderstood the definition of batching, I thought it was
for minimizing overall render state changes via state sorting instead of
just mesh combination.
So in that sense the 2d batchers are grammatically correct. However
ModelBatch does have vertex combining functionality, as thats mutex with
the prebuilt VBOs it accepts.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/libgdx/libgdx/issues/5146#issuecomment-376666858, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAfYBMtxmFXv-gC3xPRlMRkzZ8Dn4o9jks5tiqMigaJpZM4S9ez6
.


scripts to reproduce results

Thanks for your great work and code!
May I ask if you will release the scripts to reproduce the results of 17 datasets? The code covers the core idea but misses the information on specific datasets.
For example, the promote used for each dataset should have a large influence on the results.
            prompt_list.append([k,'a centered satellite photo of '+sentence])
Thanks again!

Solved. Thanks!


⚠ Bofrost.nl has degraded performance

In a6e0c65, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 939 ms

Resolved: Bofrost.nl performance has improved in 34377e1.


Add a new FAQ on tenant restrictions

FAQ item something like below in this page Troubleshooting B2B collaboration - Microsoft Entra | Microsoft Learn
An error similar to "External access blocked by policy" appears in home tenant(partner) login screen or more specifically you see a message "Your network administrator has restricted what organizations can be accessed. Contact your IT department to unblock access."
Follow the instructions provided at https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/tenant-restrictions
Relevant UAT: https://dev.azure.com/unifiedactiontracker/Unified Action Tracker/_workitems/edit/176122?src=WorkItemMention&src-action=artifact_link

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

ID: 3f76cc85-8dc0-9be3-4071-217589ddef56
Version Independent ID: e7bdba65-bacc-7fef-2c27-b3425f697b12
Content: Troubleshooting B2B collaboration - Microsoft Entra
Content Source: articles/active-directory/external-identities/troubleshoot.md
Service: active-directory
Sub-service: b2b
GitHub Login: @csmulligan
Microsoft Alias: cmulligan

@nasir-uddin-msft
Thanks for your feedback! We will investigate and update as appropriate.

@nasir-uddin-msft thank you for reaching out. I've moved this issue to an internal work item for tracking. I'll go ahead and close this issue, but changes to the article are in the works. Thanks again!
#please-close


[Input] Add size

Add the same behaviour as the original component: https://semantic-ui.com/elements/input.html#size
Please have a look at contributing.md for instructions on how to contribute and submit a PR.

got this one


FAQ : Contributing: Donation added. Glitch corrected

I do not understand why travis-ci failed...

Thanks for pointing this. Change done.


#961 support flow variance syntax

Fixes #961
It looks like getKeyValue was naively grabbing the first token for 'ObjectTypeProperty', which was sometimes a '+'.  There's probably a more robust solution, but I've just opted to account for '+' and '-' as possible tokens that might be encountered.

LGTM, can you rebase your branch and resolve the conflicts? Then I think we should be good to go.

Cool, updated.

Merged, thanks!


Generate a fuse index for search

This PR makes voodoo generate a search index by traversing the .odocl files, outputting a javascript file creating an index for the fuse-js library.
When this is ultimately done by odoc itself, we can remove this code.
Made with @sabine!

Thank you, this is an excellent addition to give people on ocaml.org a basic search until the feature is ready in odoc!


SharedFunctions - Move all to individual files

Moved SharedFunctions functions to \internal

How to test

[ ] Compare functions found in the old SharedFuntions.ps1 to the functions found in the new directory; \internal, ensuring all of them are there
[ ] Compare that the function names are the same inside the file as the filename itself
[ ] See that two functions have been moved to public - Test-SqlConnection and Update-dbatools
Run a couple commands that require a bunch of internal commands such as Copy-SqlDatabase and Sync-SqlLoginPermissions

@ctrlbold has asked for this to go through before anything else. Need to see if any other PR's are making changes to ShareFunctions.
Quick look through the code only one things looks suspect.


Improve test coverage for Remove and SaveChanges

There have been a number of issues(#1111, #1371, #2890) relating to removing entities from the context and saving changes. While there is fairly extensive coverage for DbSet<T>.Add, (Explicitly and through test model seeding) the coverage for DbSet<T>.Remove is relatively low.
Investigations have been showing these issues being resolved as a side effect of other changes/fixes, but we should avoid regressions in this area by adding tests to cover removing from models with various shapes and relationships, i.e. the Gears Of War model.

Have you looked at GraphUpdatesTest? That's where most of the coverage for removing entities is. It would be useful to know which scenarios are missing from here.

Waiting to triage until question from @ajcvickers is answered.

I missed the GraphUpdateTest tests when I was initially investigating, but it looks like these tests provide appropriate coverage. The history indicates that many of the Remove tests were added between beta7 and beta8, and it's likely the related changes resolved #2890.


Document lock duration doesn't work

Describe the Bug
If user 1 opens and starts editing a collection item and then closes the window. Other users will get an "Document Locked" modal forever (unless they take over) even if there is a duration set
Link to the code that reproduces this issue
Payload template
Reproduction Steps
Create a new page using the website template. Add locking to the pages collection
lockDocuments: {
    duration: 60,
  },

And remove autosave but keep drafts
 versions: {
    drafts: true,
    maxPerDoc: 50,
  },

Then seed the database. Make sure you have at least 2 users. Open a page, make a change without saving and then close the window. The database should now contain one locked document.
After 60 seconds open that document using another user. You will still get a warning. And also an "Edited since" date that is wrong. It's always right now instead of the "updatedAt" date from the payload-locked-documents item.
I've attached a screenshot where 15 minutes have elapsed but I'm still getting the warning

Which area(s) are affected? (Select all that apply)
Not sure
Environment Info
Binaries:
Node: 20.17.0
npm: 10.8.2
Yarn: N/A
pnpm: 9.0.2
Relevant Packages:
payload: 3.0.0-beta.116
next: 15.0.0-canary.173
@payloadcms/db-mongodb: 3.0.0-beta.116
@payloadcms/email-nodemailer: 3.0.0-beta.116
@payloadcms/graphql: 3.0.0-beta.116
@payloadcms/live-preview: 3.0.0-beta.116
@payloadcms/live-preview-react: 3.0.0-beta.116
@payloadcms/next/utilities: 3.0.0-beta.116
@payloadcms/plugin-cloud: 3.0.0-beta.116
@payloadcms/plugin-form-builder: 3.0.0-beta.116
@payloadcms/plugin-nested-docs: 3.0.0-beta.116
@payloadcms/plugin-redirects: 3.0.0-beta.116
@payloadcms/plugin-search: 3.0.0-beta.116
@payloadcms/plugin-seo: 3.0.0-beta.116
@payloadcms/richtext-lexical: 3.0.0-beta.116
@payloadcms/translations: 3.0.0-beta.116
@payloadcms/ui/shared: 3.0.0-beta.116
react: 19.0.0-rc-3edc000d-20240926
react-dom: 19.0.0-rc-3edc000d-20240926
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
Available memory (MB): 15970
Available CPU cores: 12

Hey @stofolus - thanks for bringing this to our attention!
I have a PR for this linked above - adding some tests right now and then we'll get this fix merged up asap.

Fixed with PRs:

#8899
#8914


Improve note on "Manage TLS Certificates": Replace "custom CA certificate" with "root CA certificate" for clarity

in the note:

Note:
Even though the custom CA certificate may be included in the filesystem (in the ConfigMap kube-root-ca.crt),

I think "custom CA certificate" should be better rewritten as "root CA certificate" for clarity.

Page reported in issue (based on the title):  https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/
/language en

/retitle Improve note on "Manage TLS Certificates": Replace "custom CA certificate" with "root CA certificate" for clarity
/sig auth cluster-lifecycle

@dipesh-rawat This is not related to auth or cluster lifecycle SIGs, those aren't cluster certificates but application. "These CA and certificates can be used by your workloads to establish trust." I think the only SIG involved is documetation

Even though the custom CA certificate may be included in the filesystem (in the ConfigMap kube-root-ca.crt),

“custom” is not a synonym for “root”. We might want to write “custom trust anchor (the root certificate)”, or something like that. Although the ConfigMap is named kube-root-ca.crt, its key role is to provide a trust anchor (and, despite the name, I think that it can actually be an intermediate CA).
Which web page needs amending?

/triage needs-information


exceptions thrown from boost::asio::basic_dir_monitor_serviceboost::asio::dir_monitor_impl::work_thread() cannot be caught from the main thread

I encountered uncaught exceptions be thrown from boost::asio::basic_dir_monitor_serviceboost::asio::dir_monitor_impl::work_thread() Line 218 in Windows. As enlightened by this link, and study the the current implementation, work_thread()  is running in its own thread, thus the exceptions being thrown cannot be caught from any other thread. Can you please confirm this is correct? If yes, I'd like to fix it as the above link suggest. I'll be better if you have test cases for exceptions.

Hi, I will try and add exceptions test cases when I have some time.

I've been thinking about how to transfer the exceptions in work_thread() to the main thread so as to catch them, but could not find a way.
If you have any specific ideas in mind,  I might find time to get it implemented and send it for your review.

I will take a closer look at this today then.

FWIW I'm interested in this as well. Will help if there's anything to assist with.

Thanks. While I am typing, It occurred to me that we could expose the thread handle(e.g. get_work_thread()) so that it could joined later from the caller site, then the exceptions could be caught following the pattern in this link. However I do not like this idea much as it's more a hack to facilitate the implementation itself rather than a natural need/facility/interface of directory monitoring.

hello collegues. my recently attempts of using this project has given me the similar result.
i don't think that "exceptions between threads propagation" is best solution for this class. let's explain why.
consider the following example
there are N+1 folders for monitoring task: remote temp (shared via smb) and local temp1, temp2, ... , tempN.

in windows command line console type "net use {url_to_remote_temp} {password} /USER:{login}"
start for execution something like

boost::asio::dir_monitor monitor(io_service);
monitor.add_directory(<path_to_shared_temp>);
monitor.add_directory(<path_to_local_temp1>);
monitor.add_directory(<path_to_local_temp2>);
...
monitor.add_directory(<path_to_local_tempN>);

for (;;)
{
    monitor.async_monitor(some_handler);
    io_service.run();
}

3.in windows cmd type "net use {url_to_remote_temp1} /DELETE"
and we have an exception from Line 218 caused by ERROR_OPERATION_ABORTED code returned from GetQueuedCompletionStatus function from Line 213.
What can we conclude?

Unhandled exception leads to app crash
One problem directory leads fail on whole monitoring task.

so, my conclusions are:

work_thread() must not throw any exception and it should continue to work
we can process ERROR_OPERATION_ABORTED return code. In this case GetQueuedCompletionStatus set ck with proper completion port value and bytes_transferred with 0. So at least we will come to Line 225.

in addition, i'm going to share my solution with pull request soon.

CMake Error at CMakeLists.txt:6 (cmake_minimum_required):
  CMake 3.1 or higher is required.  You are running version 2.8.7

in CI build :disappointed_relieved:

Yeah, CI has problems still.. Couldn't find time to configure it all correctly there.

FWIW, there's still the value of throwing when something goes wrong with the directories be monitored, so that I know what going on.
I am wondering if we can put the io_service.run() into dir_monitor.  and the client code looks something like this:

try
{
    boost::asio::dir_monitor monitor(io_service);
    monitor.add_directory(<path_to_shared_temp>);
    monitor.add_directory(<path_to_local_temp1>);
    monitor.add_directory(<path_to_local_temp2>);
    // ...
    monitor.add_directory(<path_to_local_tempN>);

    monitor.async_monitor(some_handler);

    // internally it delegates to io_serivce.run(),
    // and **collects  and re-thows** all exceptions from spawned threads
    monitor.run();
}
catch (/*all exceptions*/)
{
   // handlers or even recreate a new boost::asio::dir_monitor object
}

the down

@rockonedege the main downside of your "run" offer is that it doesn't match asio conceptions.
in addition to my previous arguments throwing exception doesn't give us a chance to deallocate memory for ck in case of error or remove_directory calling.

@sbelsky, sorry for the late response. Your points against my previous wild thoughts are valid.
I finally succeed in achieving 3 goals:

keep the throwing mechanism
stick to asio conventions on exception handling
keep the io service and its work_thread() method in good health after exceptions.

The main idea being:

transfer the exceptions inside basic_dir_monitor_service::work_thread() to basic_dir_monitor_service::thread_exception_ptr_
add basic_dir_monitor_service::throw_me() to rethrow basic_dir_monitor_service::thread_exception_ptr_
post basic_dir_monitor_service::throw_me() to the owner(i.e. base class) of basic_dir_monitor_service.

then at the client,  the code would be like this:

	io_service io_service;

	dir_monitor monitor(io_service);
	monitor.add_directory(...);
    monitor.async_monitor(some_handler);

	for (;;)
	{
		try
		{
			cout << "Monitoring service started:\n";
			io_service.run();
		}
		catch (const boost::system::system_error& e)
		{
			// do whatever with the exceptions thrown from basic_dir_monitor_service::work_thread()
		}
	}

The code has been committed to my fork.
I haven't figure out how to write the test.  However,  if you replace the committed basic_dir_monitor_service::work_thread() with the following the code, you'll see it works perfectly.

    // this code throws at first run and then goes back to normal to show that
    // the service can actually survive exceptions and continues to work
    void work_thread()
    {
        static int i = 0;
        while (running())
        {
            try
            {
                if (i == 0)
                {
                    ++i;

                    boost::system::system_error e(boost::system::error_code(0x40, boost::system::get_system_category()), "hello moto");
                    boost::throw_exception(e);

                }

                work();
            }
            catch (...)
            {
                thread_exception_ptr_ = std::current_exception();
                this->get_io_service().post(boost::bind(&boost::asio::basic_dir_monitor_service<DirMonitorImplementation>::throw_me, this));
            }
        }
    }

@berkus, if you are ok with this implementation, I can create a pull request.

Please, make a PR and I'll review, will be more handy like that.

@rockonedege ooo I didn't assume that it is possible to do
boost::bind(&boost::asio::basic_dir_monitor_service<DirMonitorImplementation>::throw_me, this));

generally it seems to me this is a good approach.


Resizing Dual Grid after initialization

Hopefully this is possible, but how do you change the Grid A vs Grid B display ratio after it has already been built? I have tried accessing the display from the state, but it is not possible to reassign a value. Changing the value passed into the widget also does not work since it is final:
display: new PlutoDualGridDisplayRatio(ratio: _subGridData.isNotEmpty ? 0.5 : 0.75),
As a side note, before we upgraded to the latest patch (we were behind about 2 major versions) the above code worked to programatically change the ratio

There is no function. should be added.


JAX implementation of scipy.stats.multinomial pmf & logpmf

fix https://github.com/google/jax/issues/11817
Implementation originally made by @harryjulian.
I just made minor changes and am making a separate PR for cleaner review as @jakevdp has suggested.
I will make improvements upon review asap.
Hope you have a great week ahead :) Thanks!

@jakevdp I think I addressed the problems you have pointed out, sir. May you please review my updated code?

I triggered the test runs, I believe they will fail because you're still doing implicit type promotion between ints and floats. We need explicit conversions.

You should try running those tests locally, because it will make the iteration time much faster! There's some info here: https://jax.readthedocs.io/en/latest/developer.html?highlight=pytest#using-pytest

Hello @jakevdp,

Finally passed the type conversion test. May you please run the workflow to test the code? Thank you so much for all your guidance!

Looks great! Thanks for sticking with this. The last thing we need is to squash all the commits into one, and force push to this branch (see https://jax.readthedocs.io/en/latest/contributing.html#single-change-commits-and-pull-requests) Let me know if you have any questions

I think we're ready to merge this, but we still need all the commits squashed. Let me know if you need help with that process; alternatively if I have write access to your branch I could take care of it for you.

Dear @jakevdp,
Hello sir! I really wanted to try rebasing this on my own, so I asked friends and watched a LOT of tutorials. I've learned to definitely keep my branches tidy from now on, but still need help with this spaghetti I've conjured up (ramen). May you please help me? https://github.com/wonhyeongseo/jax/invitations
Love and best regards,
@wonhyeongseo

Hi - thanks, I'm happy to help you get this merged, but there are still a few test failures to look into. In particular, the test case is problematic because for integer inputs, np.sum may not return the same dtype. So I think you need to use n = np.sum(x, dtype=x.dtype).

That sounds good, thanks!

Working on unravelling your branch's commit history... it's impressive


Page 68 line 29 typo in version 2022-07-01

This is covered in detail in Section 4.6.2 of the sequel to this book, should be prequel.

fixed, thanks


Replace 'false' as default return value with Unit

Unit should be a symbol. This will avoid a lot of confusion.

Fixed!


Thumbia based on gumlet/php-image-resize

https://github.com/jenstornell/thumbia
Problem
A problem I have with all libraries like this is that they are using paths. I often have a HTML string containing images with urls.
Solution
With my library, you send a string of HTML containing images and it will make thumbnails of the images. Then it will replace the urls with the new thumbnail urls.

It's unclear what kind of action you're expecting. Do you want gumlet/php-image-resize to include this feature too? It doesn't look like a good fit for the library in its current form.

@gronostajo I removed it.


Give errors with some torch models

i have tried the mentioned test.t7 files and it works correctly but when i tried it with this model it gives me errors when load it
Traceback (most recent call last):   File "code.py", line 2, in <module>     o = torchfile.load('colornet.t7')   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 415, in load     return reader.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 375, in read_obj     obj = torch_readers[className](self, version)   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 201, in reader     obj = reader.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 375, in read_obj     obj = torch_readers[className](self, version)   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 201, in reader     obj = reader.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 375, in read_obj     obj = torch_readers[className](self, version)   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 201, in reader     obj = reader.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 386, in read_obj     v = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 385, in read_obj     k = self.read_obj()   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 373, in read_obj     obj = TorchObject(className, self.read_obj())   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 405, in read_obj     raise T7ReaderException("unknown object") torchfile.T7ReaderException: unknown object
Note: the mentioned model works correctly when run it.

Are you using any non-built-in nn modules or other torch classes? If so,
which?
On Feb 18, 2017 18:12, "Ahmed-Mohamed15"<EMAIL_ADDRESS>wrote:
i have tried the mentioned test.t7 files and it works correctly but when i
tried it with this model
https://github.com/satoshiiizuka/siggraph2016_colorization it gives me
errors when load it
Traceback (most recent call last): File "code.py", line 2, in  o =
torchfile.load('colornet.t7') File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 415, in load return reader.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 375, in read_obj obj = torch_readers[className](self, version) File
"/usr/local/lib/python2.7/dist-packages/torchfile.py", line 201, in reader
obj = reader.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 375, in read_obj obj = torch_readers[className](self, version) File
"/usr/local/lib/python2.7/dist-packages/torchfile.py", line 201, in reader
obj = reader.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 375, in read_obj obj = torch_readers[className](self, version) File
"/usr/local/lib/python2.7/dist-packages/torchfile.py", line 201, in reader
obj = reader.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 386, in read_obj v = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 385, in read_obj k = self.read_obj() File
"/usr/local/lib/python2.7/dist-packages/torchfile.py",
line 373, in read_obj obj = TorchObject(className, self.read_obj()) File
"/usr/local/lib/python2.7/dist-packages/torchfile.py", line 405, in
read_obj raise T7ReaderException("unknown object")
torchfile.T7ReaderException: unknown object
Note: the mentioned model works correctly when run it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bshillingford/python-torchfile/issues/7, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACOA3dxNX5F8Glhe4b7q7Db0_CgBlqtLks5rdzSAgaJpZM4MFM2C
.

if you mean in the python code so all the code is
import torchfile o = torchfile.load('colornet.t7')
and if you mean in the model so it depends on nn image && nngraph packages

Should be fixed now, try master.

okey it is fixed now but it gives me another errors when tried to print the model, so what is the problem ? it may be it can't print the wholo model, so can i see what is the model consists of ? (some thing like help command or a guide ) so that i can access only what i want because i don't know what is the actual code inside it.
o = torchfile.load('colornet.t7')
print (o)
The errors
Traceback (most recent call last):   File "code.py", line 3, in <module>     print o   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 181, in __repr__     return "TorchObject(%s, %s)" % (self._typename, repr(self._obj))   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 181, in __repr__     return "TorchObject(%s, %s)" % (self._typename, repr(self._obj))   File "/usr/local/lib/python2.7/dist-packages/torchfile.py", line 181, in __repr__     return "TorchObject(%s, %s)" % (self._typename, repr(self._obj)) MemoryError

You're trying to print the entire model, and you're running out of memory.
To see elements, use o.keys() if it's a dict, or dir(o) if it's a torch
class instance.
Please keep in mind that this module is simply for reading .t7 files and
inspecting them, e.g. if you wanted to inspect a training checkpoint or
extract weights as numpy arrays. Thus you're not able to run a forward
pass, but of course you could manually copy the weights into a model in the
framework of your choice. Consider using the original Lua code if you just
want to run the model.

i want is to access the trained weights of the layers , that's all i try to get. @bshillingford

Then use dir and keys as mentioned, as usual in Python.


feat(clerk-js,types,backend): Use EIP-4361 message spec for Web3 wallets

Description

In this commit we are updating our Web3 flows logic to use the new 'message' property of a Web3 verification, which follows the EIP-4361 spec, to sign a new request. This message format provides a better experience to the end user by let them know additional information for the application they are about to use
Before

After

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Is there a link for the spec that you can add to the description ?

Sure thing added!


@azure/ai-form-recognizer breaks Nuxt3 on netlify (Cannot find package 'tslib')

Package Name: @azure/ai-form-recognizer
Package Version: 5.0.0
Operating system:netlify
[18.x ] nodejs

version:

[ chrome/119.0.6045.159] browser

name/version:

[ 5.0.3] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Nuxt3 site with @azure/ai-form-recognizer deployed to netlify breaks site
To Reproduce

Add @azure/ai-form-recognizer as an npm dependency to a nuxt3 site
deploy to netlify using automated deployment
Error....

Dec 10, 11:04:47 PM: 35d00016 ERROR  [nuxt] [request error] [unhandled] [500] Cannot find package 'tslib' imported from /var/task/.netlify/functions-internal/server/chunks/app/server.mjs
  at new NodeError (node:internal/errors:405:5)
  at packageResolve (node:internal/modules/esm/resolve:895:9)
  at moduleResolve (node:internal/modules/esm/resolve:988:20)
  at moduleResolveWithNodePath (node:internal/modules/esm/resolve:939:12)
  at defaultResolve (node:internal/modules/esm/resolve:1181:79)
  at nextResolve (node:internal/modules/esm/loader:163:28)
  at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
  at link (node:internal/modules/esm/module_job:76:36)

Expected behavior
site works.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

This is a tslib issue.  for your ref, discussion and my fix (hack) is here https://github.com/microsoft/tslib/issues/143#issuecomment-1850111578


Extension setting sync

Installation of extension is synced, but settings don't appear to be.  Would be nice not to re-configure on each machine.

Currently we're storing the settings within the browser itself locally, which is why the settings don't sync. The only way to share settings like this would be to store them on a server somewhere and then have some sort of login.
I'd love to have it work in a centralised way, and I can think of some ways to achieve that.

Doesn't Chrome provide a storage sync API for logged in users?

Yes, but we also support Firefox and Safari. :+1:
YNAB actually have an API for this which syncs your account settings across devices when you're logged in, but have politely asked us not to shove random data into their DB for now.

I've gone ahead and added this to the Roadmap here:
https://trello.com/c/bse9h25w/172-sync-toolkit-settings-between-installed-computers
I'm going to go ahead and close this issue so we can track this along with the other feature requests. Thank you for contributing, I think this would be a really cool feature!


Typo in charm library broke our CI

There is a small typo compatiblity => compatibility in the v3.tls_certificates library.
This broke the linter running in our CI (which runs codespell on all files). We're adding this file to the ignorelist, but I figured it might be quicker to just fix it here!
https://github.com/canonical/tls-certificates-interface/blob/5e1ecf09b73be7c1577e186b2743099d89e9d0ca/lib/charms/tls_certificates_interface/v3/tls_certificates.py#L2031

Thank you for reporting this issue, here's the PR to address it:

https://github.com/canonical/tls-certificates-interface/pull/248

Fixed by #248


RedisOM is fatally incompatible with proper JSON path schema for searching fields of objects in an array

Using:

<EMAIL_ADDRESS><EMAIL_ADDRESS>Redis v6.2.6

RediSearch v2.6.9
RedisJSON v2.4.7

Given the following sample JSON structure:
{
    "settings": [
        { "type": 0 },
        { "type": 1 },
        { "type": 2 }
    ]
}

and the following matching schema, currently in the way RedisOM wants it:
const SampleSchemaDefinition = {
    type: { type: 'number', path: '$.settings[*].type[*]' }
};

This works fine for RedisOM's core operations of saving and retrieving the entities, but falls apart as soon as search gets involved should you want to search the type fields. To ensure no possible extra interference from RedisOM internals we use raw search directly on a redis shell to test this:
Note: Sample:index is RedisOM's generated index for the above schema.
> FT.SEARCH Sample:index "@type:[-inf inf]"

This trivial search should naturally have returned every Sample entity, except for ones where the settings array is empty (settings: []) which while there are some empty ones in the real dataset, they are not the majority and there should have been results still, but instead the result is consistently nothing.
After some trial and error I find that changing the original schema to the following:
const schemaDef = {
    type: { type: 'number', path: '$.settings[*].type' }
};

...will fix it on the search front, the same FT.SEARCH command above now yields the expected working results, all non-empty settings get retrieved. So surely that's it right? Problem solved? No, not quite...
While the fixed schema path worked for raw Redis search, RedisOM is unable to handle it when trying to perform any of the core save and retrieval operations, which invalidates the point of having .search() work if it dies on .returnAll() when trying to serialize the entities. The error? It is infact very explicit about this being the cause:
Error: Unexpected value for field 'type' of type 'number' from JSON path '$.settings[*].type' in Redis.

The result from all this ultimately renders searching completely unusable on this schema.
Solutions
RedisOM should support the path without [*], I don't know what the reasons for that restriction are, so I don't know how feasible that might be, so an alternative could also be to provide an additional field to override the path that is used on the RediSearch index compared to the one RedisOM will use.

The first JSONPath you provided—$.settings[*].type[*]—does not match anything in the JSON you provided. This is not a problem with Redis OM but is just how JSONPaths work. The problem is that this path will look for an array of objects—the $.settings[*] part—with a property of type that contains an array—the .type[*] part. The type property does not contain an array—it contains a single value. So, it doesn't match.
If your JSON looked like this, it would work:
{
  "settings": [
    { "type": [ 0, 1, 2 ] },
    { "type": [ 1 ] },
    { "type": [ 2, 4 ] }
  ]
}

However, this is not your JSON.
The second JSONPath that you provided—$.settings[*].type—is the correct one for your JSON. It matches the array of objects part using $.settings[*] and then looks for the type property within that array. It will return an array of the values in those type properties.
The error you are receiving is because the JSONPath returns an array of numbers and not a single number. But the type provided in the Schema is a number, which can only be a single value. You need to change the type in the Schema to a number[] for this to work.
The section of the documentation on overriding JSONPaths talks about this:

To do this, we'll need to specify the path property for the nested fields in the schema:
const albumSchema = new Schema('album', {
  artist: { type: 'string', path: '$.album.artist' },
  title: { type: 'string', path: '$.album.title' },
  year: { type: 'number', path: '$.album.year' },
  genres: { type: 'string[]', path: '$.album.genres[*]' },
  songDurations: { type: 'number[]', path: '$.album.songDurations[*]' },
  outOfPublication: { type: 'boolean' }
})

There are two things to note here:

We haven't specified a path for outOfPublication as it's still in the root of the document. It defaults to $.outOfPublication.
Our genres field points to a string[]. When using a string[] the JSONPath must return an array. If it doesn't, an error will be generated. (emphasis mine)
Same for our songDurations.

It's worth noting that the JSONPath needs to return multiple results (i.e. an array) but not a single result that contains an array. This is why my examples use [*] at the end.
I might have been able to add code to make Redis OM smart enough to figure this specific case out and eliminate the need to add a [*] at the end when the leaf nodes of your tree are arrays. But even if RediSearch would have been happy with it—which I am not 100% sure it would be—this would have have added more complexity than is obvious. Plus, there were more important features to do first. And, I have future plans to add something like an object and object[] type that would obviate the need to specify JSONPaths in these scenarios.

I see, so it appears a misinterpretation of my part which for most common cases had no difference thus no impact ended up being exposed here where it finally made a difference, I was under the impression type was the type of the field in the JSON, as opposed to the reality that it seems to be the type of what the JSONPath returns, and in my defense after re-checking the README to be sure, it is worded in a way that gives off the idea its the type of the field data:

The type property tells Redis OM what sort of data is in that field.

Perhaps the distinction that type is actually the JSONPath return type when working with JSON could be added on there for clarification? (at least until the object type is done, which I'll definitely be looking forward to)
Back to this specific issue itself the given fix indeed works, thank you 👍 Feel free to close the issue.


Cleanup StringIO/cStringIO

There is no need for try/except around this anymore, I think. cStringIO is in all python versions we've used for years. Python3 makes cStringIO the default and it's called io.StringIO.
We should just use import cStringIO as StringIO everywhere in preparation for the transition

Turns out we had an issue for this already.

This should have been closed with #8733


The plugin sms uses a deprecated version of the Android embedding.

The plugin `sms` uses a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

I have same isssue.

Same Issue

Sorry for the inconvenience caused, we'll be looking into this very soon
and will get back to you as soon as possible.
On Mon, Feb 7, 2022, 09:52 Saad Mahboob @.***> wrote:

Same Issue
—
Reply to this email directly, view it on GitHub
https://github.com/JerinFrancisA/flutter_otp/issues/11#issuecomment-1031059804,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKINHQPSGJMMZD4BDIMI4ETUZ5CJLANCNFSM5GHXNVPQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Could tensorflow-java invoke GPU?

Hi:
when I  train the model  build  with tensorflow-java ,only can use cpu,but if I want to use GPU,I don't the deal method.is it support GPU?

Switch tensorflow-core-platform-gpu for your current OS specific platform jar on your classpath and it will default to running on the GPU.

get it,thanks

The TF runtime prefers to place computations on the GPU, so if one is available it will use it in preference to the CPU.

Does it support mac bookpro intel gpu ?


GPU mode with 8gb vram

Readme states that 6.9B model in 8-bit mode uses 7gb of gpu vram, so i decided to test it on 8gb p104-100 (virtually same as gtx1070). In both 16-bit and 8-bit mode, generate.py throws
OutOfMemoryError: CUDA out of memory. Tried to allocate 158.00 MiB (GPU 0; 7.93 GiB total capacity; 7.37 GiB  already allocated; 78.19 MiB free; 7.39 GiB reserved in total by PyTorch)
error. Is readme wrong about minimum vram size or am I doing something wrong? I've tested it with both oig-oasst1-512-6_9b and falcon-7b models.

Hi @mssc89 .  Please give the full command you are running.
Note that for documents, Instruct-large uses more GPU than the Mini one, so if you are limited on ram, I recommend that as in the readme.md, i.e.:
python generate.py --base_model=h2oai/h2ogpt-gm-oasst1-en-2048-falcon-7b-v3 --hf_embedding_model=sentence-transformers/all-MiniLM-L6-v2 --score_model=None --load_8bit=True --langchain_model='MyData'

This also disables the score model that eats GPU too.
This uses 8344MB of GPU on my system to start-up things.
So let's try 6.9B:
python generate.py --base_model=h2oai/h2ogpt-oig-oasst1-512-6_9b --hf_embedding_model=sentence-transformers/all-MiniLM-L6-v2 --score_model=None --load_8bit=True

This uses 8314MB.  So still too much for your 8GB.
So let's try 4-bit:
python generate.py --base_model=h2oai/h2ogpt-oig-oasst1-512-6_9b --hf_embedding_model=sentence-transformers/all-MiniLM-L6-v2 --score_model=None --load_4bit=True

This only uses 5698MB to startup.  And it's not too slow.
So I'd recommend probably 7b model with 4-bit:
python generate.py --base_model=h2oai/h2ogpt-gm-oasst1-en-2048-falcon-7b-v3 --hf_embedding_model=sentence-transformers/all-MiniLM-L6-v2 --score_model=None --load_4bit=True

This uses 5796MB to startup and up to 6046MB to ask a basic question.
Back to langchain, can do:
python generate.py --base_model=h2oai/h2ogpt-gm-oasst1-en-2048-falcon-7b-v3 --hf_embedding_model=sentence-transformers/all-MiniLM-L6-v2 --score_model=None --load_4bit=True --langchain_mode='MyData'

This uses 5796MB to startup, then soon drops to 5074MB after torch cache is cleared.  Asking a simple question uses up to 6046MB again.  Adding a document uses no more new GPU memory.


After a few different repo data requests get data stops requesting

Suspect there is an issue with how some query data is in state.

old


flake8: Set max-line-length instead of ignoring long lines

./manim/manim/grpc/gen/frameserver_pb2.py:21:89: E501 line too long (3454 > 88 characters)
manim/cli/render/commands.py:35:1: C901 'render' is too complex (35)

Overview: What does this pull request change?

Motivation and Explanation: Why and how do your changes improve the library?

Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

$ mv .flake8 was.flake8
$ flake8 --exclude="./.*,manim/grpc/gen/*,manim/mobject/svg*" --max-line-length=283 --select=E501
./manim/mobject/vector_field.py:179:284: E501 line too long (284 > 283 characters)

$ mv was.flake8 .flake8

I don't really see the benefit of enabling the line length check with such a high limit. We currently have about 700 lines that exceed 88 characters (which, theoretically, is the line length suggested by black).
I would be happy to merge this if we reduced the limit down to something a bit more reasonable like 150 characters or so, such that we at least kill the extreme line length violations with this PR. There are not too many of those:
./tests/test_deprecation.py:158:151: E501 line too long (153 > 150 characters)
./tests/test_deprecation.py:160:151: E501 line too long (167 > 150 characters)
./tests/assert_utils.py:24:151: E501 line too long (161 > 150 characters)
./tests/utils/logging_tester.py:40:151: E501 line too long (211 > 150 characters)
./tests/helpers/graphical_units.py:21:151: E501 line too long (187 > 150 characters)
./manim/camera/camera.py:815:151: E501 line too long (156 > 150 characters)
./manim/utils/tex.py:123:151: E501 line too long (205 > 150 characters)
./manim/utils/deprecation.py:299:151: E501 line too long (153 > 150 characters)
./manim/utils/hashing.py:27:151: E501 line too long (166 > 150 characters)
./manim/utils/hashing.py:30:151: E501 line too long (182 > 150 characters)
./manim/utils/hashing.py:45:151: E501 line too long (194 > 150 characters)
./manim/utils/hashing.py:138:151: E501 line too long (160 > 150 characters)
./manim/utils/hashing.py:154:151: E501 line too long (221 > 150 characters)
./manim/utils/hashing.py:196:151: E501 line too long (193 > 150 characters)
./manim/utils/hashing.py:197:151: E501 line too long (184 > 150 characters)
./manim/scene/scene_file_writer.py:504:151: E501 line too long (175 > 150 characters)
./manim/scene/scene_file_writer.py:581:151: E501 line too long (184 > 150 characters)
./manim/scene/scene.py:911:151: E501 line too long (159 > 150 characters)
./manim/mobject/vector_field.py:52:151: E501 line too long (185 > 150 characters)
./manim/mobject/vector_field.py:54:151: E501 line too long (152 > 150 characters)
./manim/mobject/vector_field.py:56:151: E501 line too long (151 > 150 characters)
./manim/mobject/vector_field.py:272:151: E501 line too long (167 > 150 characters)
./manim/mobject/vector_field.py:277:151: E501 line too long (178 > 150 characters)
./manim/mobject/vector_field.py:384:151: E501 line too long (185 > 150 characters)
./manim/mobject/vector_field.py:386:151: E501 line too long (152 > 150 characters)
./manim/mobject/vector_field.py:388:151: E501 line too long (151 > 150 characters)
./manim/mobject/vector_field.py:546:151: E501 line too long (185 > 150 characters)
./manim/mobject/vector_field.py:548:151: E501 line too long (152 > 150 characters)
./manim/mobject/vector_field.py:550:151: E501 line too long (151 > 150 characters)
./manim/mobject/vector_field.py:570:151: E501 line too long (165 > 150 characters)
./manim/mobject/vector_field.py:572:151: E501 line too long (170 > 150 characters)
./manim/mobject/vector_field.py:788:151: E501 line too long (177 > 150 characters)
./manim/mobject/table.py:195:151: E501 line too long (171 > 150 characters)
./manim/mobject/coordinate_systems.py:1601:151: E501 line too long (171 > 150 characters)
./manim/mobject/coordinate_systems.py:1690:151: E501 line too long (159 > 150 characters)
./manim/mobject/coordinate_systems.py:1713:151: E501 line too long (152 > 150 characters)
./manim/mobject/coordinate_systems.py:1719:151: E501 line too long (211 > 150 characters)
./manim/mobject/mobject.py:309:151: E501 line too long (240 > 150 characters)
./manim/mobject/mobject.py:880:151: E501 line too long (210 > 150 characters)
./manim/mobject/mobject.py:882:151: E501 line too long (152 > 150 characters)
./manim/mobject/svg/brace.py:70:151: E501 line too long (929 > 150 characters)
./manim/mobject/svg/brace.py:250:151: E501 line too long (259 > 150 characters)
./manim/mobject/svg/text_mobject.py:4:151: E501 line too long (182 > 150 characters)
./manim/mobject/svg/text_mobject.py:712:151: E501 line too long (329 > 150 characters)
./manim/mobject/svg/tex_mobject.py:9:151: E501 line too long (173 > 150 characters)
./manim/mobject/types/vectorized_mobject.py:583:151: E501 line too long (266 > 150 characters)
./manim/mobject/types/vectorized_mobject.py:594:151: E501 line too long (181 > 150 characters)
./manim/mobject/types/vectorized_mobject.py:942:151: E501 line too long (162 > 150 characters)
./manim/mobject/types/image_mobject.py:30:151: E501 line too long (212 > 150 characters)
./manim/mobject/types/image_mobject.py:54:151: E501 line too long (156 > 150 characters)
./manim/mobject/types/image_mobject.py:55:151: E501 line too long (163 > 150 characters)
./manim/mobject/types/image_mobject.py:59:151: E501 line too long (180 > 150 characters)
./manim/mobject/types/image_mobject.py:71:151: E501 line too long (232 > 150 characters)
./manim/mobject/types/image_mobject.py:100:151: E501 line too long (212 > 150 characters)
./manim/_config/utils.py:1191:151: E501 line too long (177 > 150 characters)

As the title of the PR says, it is better to set a limit to prevent new contributions from adding even longer lines instead of merely ignore all long lines.

I can see where you are coming from. In that case I'm fine with checking for E501, but without the exclusion of manim/mobject/svg*.
Could you change the limit to 930 (or whatever covers brace.py)? We can then merge this and open a new issue for bringing down the limit to something that actually makes sense.


Upgrade the Issue Template to use GitHub Issue forms 📜

Introduction
GitHub has recently rolled out a public beta for their issue forms feature. This would allow us to create interactive issue templates and validate them.
OpenEBS currently uses the older issue template format. The task is to create GitHub issue forms for this repository.
Tasks summary:

[ ] Fork & clone this repository
[ ] Prepare bug report issue form in .github/ISSUE_TEMPLATE/bug.yaml
[ ] Prepare documentation issue form in .github/ISSUE_TEMPLATE/documentation.yaml
[ ] Prepare feature request issue form in .github/ISSUE_TEMPLATE/feature.yaml
[ ] Push changes to master and test issue forms on your fork
[ ] Submit pull request

@kmova Please take a look at it and let me know your thoughts on this. Meanwhile, it would be great if you can add the appropriate hacktoberfest labels to the issue. Thanks.


Cake.Tool - How in the world do I run a specific task?

PS C:\Source\Templates> dotnet cake --help

Usage: Cake.exe [script] [--verbosity=value]
                [--showdescription] [--dryrun] [..]

Example: Cake.exe
Example: Cake.exe build.cake --verbosity=quiet
Example: Cake.exe build.cake --showdescription

Options:
    --verbosity=value    Specifies the amount of information to be displayed.
                         (Quiet, Minimal, Normal, Verbose, Diagnostic)
    --debug              Performs a debug.
    --showdescription    Shows description about tasks.
    --showtree           Shows the task dependency tree.
    --dryrun             Performs a dry run.
    --exclusive          Execute a single task without any dependencies.
    --bootstrap          Download/install modules defined by #module directives
    --version            Displays version information.
    --info               Displays additional information about Cake execution.
    --help               Displays usage information.

I see no way here on how I can specify the task to run.
Not mentioned here either https://cakebuild.net/blog/2018/08/cake-v0.30.0-released

I just answered my question, I had to open the build.ps1 file and find the -target="whatever" which worked. Should this be documented somewhere at least?

it is here

@Insire Yes but the dotnet CLI global tool Cake.Tool bootstrap wrapper for cake does not have any documentation on those.

I've just made  a PR #2605

@VictorioBerra The answer you should have had to your issue post is something like this:
Target is a term unknown to Cake itself.
It is something we usually build into our Cake scripts, beginning with:
var target = Argument("target", "Default");
..and ending with:
RunTarget(target);
So you can choose the target from outside by adding -target=value to your command line.
If you don't, the target 'Default' will be executed (where you can place your own instruction to the user to select a specific task, if there is no logical default).
build.ps1/build.sh should only in very rare cases need modification.


Group character config into a single struct

This makes managing character sets more manageable. As a result we can also add an 'ASCII' character set as well!

Think I might merge the character struct change and leave the ASCII thing for another PR


tests: Increase threads in tests

Looks like a test has failed. Is there are race condition?

Ran it 12 times:

It seems we are good.


feat: add helper function for constructing clean URLs in pagination component

This PR relates to issues #36: Add a helper function for constructing clean URLs for the pagination component on miniyotas.osscameroon.com
Changes

Added a new helper function called removeDomain to handle URL parsing and remove the domain from the given full URL.
Updated the constructUrl helper function to use removeDomain for constructing clean URLs.
Modified the pagination.hbs template to use removeDomain in the href attribute of the page links.

Preview
https://github.com/user-attachments/assets/8688199a-ed0b-4a3a-bcef-c0c4d7aadc32
How to Test

Ensure you have installed dependencies by running yarn install.
Start the application with yarn run dev or yarn start.
Navigate through the pagination component and confirm that URLs are correctly formatted and redirections work as expected.

Tested environments

Github Codespaces
Windows
Microsoft DevContainer

Related Issues

Fixes #36

Hi @pythonbrad, thanks' for your review. I've applied your suggestion and reverted my commit about the helper function.
If you decide not to merge this branch, I’ve also opened a separate PR (#38) that addresses only the suggested changes. I hope you will appreciate it.

Ok good, when I will test it, I will send you a feedback.

@sikatikenmogne, it's not good to push more than one pr who solve the same issue.

@sikatikenmogne, it's not good to push more than one pr who solve the same issue.

I know, I just thought it would be better to summarize the changes in this conversation in a one commit pull request instead of a 3 which looks a bit messy, feel free to close the request sweater that seems like too much.

I've closed the PR #38

@rakici