License problems with old project

I have been asked to make some changes to an old Visual Studio 2005 project which uses ComponentFactory.Krypton.Navigator.dll and ComponentFactory.Krypton.Toolkit.dll.  Both are version <IP_ADDRESS>.  When I open the project I get "Krypton Navigator Install Licence" pop up asking for a Licence key.  They did not give me this key and I don't believe they can locate it.  However, I am able to click OK past it and build the project and install files.  However, when running a popup occurs about it using unlicensed krypton navigator control.
Can anyone help with this issue?
Thanks

Hi @ygator
What version are you using? Is it possible to upload a zip file containing the binaries or installer? It might be possible to downgrade this project to .NET 2.0.

@Wagnerp,
Thanks for the reply.  I believe I mentioned all the relevant versions in my post.  If that is not the case let me know what you are looking for,
Here are further details for VS2005.
Microsoft Visual Studio 2005
Version 8.0.50727.762  (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727 SP2
Installed Edition: Enterprise
Microsoft Visual Basic 2005   77718-204-0000007-41417
Microsoft Visual Basic 2005
Microsoft Visual C# 2005   77718-204-0000007-41417
Microsoft Visual C# 2005
Microsoft Visual C++ 2005   77718-204-0000007-41417
Microsoft Visual C++ 2005
Microsoft Visual J# 2005   77718-204-0000007-41417
Microsoft Visual J# 2005
Microsoft Visual Studio Tools for Office   77718-204-0000007-41417
Microsoft Visual Studio Tools for the Microsoft Office System
Microsoft Visual Web Developer 2005   77718-204-0000007-41417
Microsoft Visual Web Developer 2005
Microsoft Web Application Projects 2005   77718-204-0000007-41417
Microsoft Web Application Projects 2005
Version 8.0.50727.762
Visual Studio 2005 Team Edition for Architects   77718-204-0000007-41417
Microsoft Visual Studio 2005 Team Edition for Software Architects
Visual Studio 2005 Team Edition for Developers   77718-204-0000007-41417
Microsoft Visual Studio 2005 Team Edition for Software Developers
Visual Studio 2005 Team Edition for Testers   77718-204-0000007-41417
Microsoft Visual Studio 2005 Team Edition for Software Testers
Crystal Reports    AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005
Microsoft Visual Studio 2005 Team Suite - ENU Service Pack 1 (KB926601)
This service pack is for Microsoft Visual Studio 2005 Team Suite - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/926601

Hi @ygator
It should be possible to downgrade my and Simon's version, which includes fixes & new features and yes it can be used in commercial projects. What .NET version are you using, is it 2.0 or 3.0?

Hi @ygator
Sorry for not getting back to you earlier. I was unable to downgrade the newer versions. However, I found the DLLs with the licencing removed
Krypton.zip. It's a much older version, dated January 2017.
Hope this helps!

@Wagnerp ,
Warning	1	Could not resolve this reference. Could not locate the assembly "ComponentFactory.Krypton.Navigator, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxx, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.	MHI-COMM
I get this for toolkit as well.

I removed the licx file and the two references to krypton and added them back by browsing to the dll's from your zip.  It was still looking for the licx file so I moved it back in.  It started up, but when
I build the project I get 82 warnings
Warning	1	Object does not match target type.
The line looks like this:
CType(Me.ch1, System.ComponentModel.ISupportInitialize).BeginInit()
The variable was initialized like this:
Me.ch1 = New ComponentFactory.Krypton.Toolkit.KryptonCheckButton

Hi @ygator
It could be that your project is still referencing version <IP_ADDRESS>. The DLLs in the zip file are 4.x, and may have API changes since <IP_ADDRESS>.

@Wagnerp,
My client says that they have one computer that does not say it is unlicensed when running the program.  Is it possible to retrieve the license from this computer?

Hi @ygator,
You could try copying all the binaries from your client's computer to a thumb drive to use on your machine. However, it may still say that it's still unlicensed. Did I send you the zip file of the open source version?

@Wagnerp , You linked a zip file with version 4.x dlls.  I may resort to seeing if they work with little effort if I bring the project into VS 2010 from VS2005 and switch to ,net 4.  If that does not work I was going to see if loading VS2005 and compiling the project on the client computer that does not pop up a license works.  Unfortunately they had an emergency and will be gone for a few week before I can try that.

Hi @ygator
It shouldn't take much effort to upgrade, but I would make a backup of the original project first before proceeding so that you can revert back if needed.


DeviceProvidesIncompatibleKey exception when 'not' is given as object attribute

@caphrim007 @jlongstaf
Fixes: Issue #835
Any background context?
For LTM Conditions, 'not' is a valid JSON field, and this is a valid
Python keyword. We can get around it (which is what we are doing
currently) by doing a setattr and getattr, but this is not sustainable.
We must brainstorm a few ideas to convert such things that can be
accessible via Python dotted attribute access. (condition._not or
condition.invert).
What's this change do?
Implemented a helper function where python keywords are appended with a
trailing underscore. This change takes care of the outgoing request and
the reverse translation on the response. Implemented a few new tests, but unconvered a new bug #836, which highlights an issue on the device around setting the 'not' attribute.
Where should the reviewer start?
This is a fix needed for running tests for L7 Content Switching in the OpenStack agent and driver.

that we have to do this hack at all makes me a sad panda, but lgtm


samples: buttons: Remove redundant code and documentation

remove redundant GPIO polling code in the main loop,  because this
demo is "showcasing the use of GPIO input with interrupts."
remove description part for "board.h", reference on #10981

Signed-off-by: Aaron Tsui<EMAIL_ADDRESS>

Codecov Report

Merging #14866 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14866   +/-   ##
=======================================
  Coverage   52.49%   52.49%
=======================================
  Files         309      309
  Lines       45056    45056
  Branches    10432    10432
=======================================
  Hits        23651    23651
  Misses      16592    16592
  Partials     4813     4813

Continue to review full report at Codecov.

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

Split into 2 logical commits.

Closing this, can be re-opened if needed.


Doesn't work with self-signed certificates

GIves an error message if you have a self-signed certificate (which I use for testing), so not usable.

Can confirm that, having the same issue.

@Benimautner Should this be fixed in the app or should it work if users import the certificate into android's ca store?

I don't like the idea of importing (temporary) self-signed certificates in the Android CA ...

Some common solution seems to be an option in the settings "dont verify certificates"

@Benimautner, maybe I miss something, but I have to log in first to be able to change options. Right now I still can't log in.

@kdrobnyh True, my mistake. Here you go.
app-main-release.zip

can confirm it's working now. Thank you!

Strange. I had the exact same error message on first try, second try worked wothout an error. Thought it was my mobile phone fooling around...

This is a bug which occurs when two requests happen too close to each other, as discovered by @k9withabone. This needs a fix asap, but we need to think about possible solutions first.

So the temporary workaround is to retry the request every time it fails. This will be fixed in a later release, but as self-signed certs are supported in the newest version, I will close this issue. Feel free to reopen it if you need anything else.

Hi!
I am currently trying to fix the issue where the app does not load every request properly. I have not been able to set up a test instance with a self-signed cert, so it'd be great if you could test whether this still works in the new fix. For that, please download the APK from this comment.
Thanks in advance!

Still have HandshakeException: Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate (handshake.cc:393)). It happens with and without ignore certificates checked.

I think I finally figured it out. I set up my own self-signed cert to debug with, and it works for me. Just one last round of feedback before I create a release would be great.
app-main-release.zip

Looks like the app works now, thanks!

published in v0.0.20-alpha


Rebuild for tests too long

Doesn't look like much single file benefit, rebuild times are high(er) than first build. Also appears to get progressively worse longer it runs.
Single file change:
gobble: build invalidated (1 file changed). restarting
gobble: 02-6to5 done in 341ms
gobble: 03-esperantoBundle done in 1462ms
gobble: 04-sorcery done in 1810ms
gobble: 18-merge done in 5ms
gobble: 07-merge done in 11ms
gobble: 08-bundleTests done in 1273ms
gobble: 09-es6transpiler done in 2099ms
gobble: 10-map done in 42ms
gobble: 16-merge done in 66ms
gobble: 17-moveTo done in 1ms
gobble: 19-merge done in 5ms
gobble: build completed in 7203ms. Listening for changes...

Compare to initial gobble:

~/ractive>npm start

><EMAIL_ADDRESS>start /Users/marty/ractive
> gobble

gobble: server listening on port 4567
gobble: livereload server running
gobble: 02-6to5 done in 6429ms
gobble: 03-esperantoBundle done in 1103ms
gobble: 04-sorcery done in 1344ms
gobble: 01-moveTo done in 2ms
gobble: 05-sorcery done in 4ms
gobble: 18-merge done in 2ms
gobble: 06-moveTo done in 0ms
gobble: 07-merge done in 12ms
gobble: 08-bundleTests done in 1125ms
gobble: 09-es6transpiler done in 6620ms
gobble: 10-map done in 38ms
gobble: 11-moveTo done in 1ms
gobble: 12-include done in 4ms
gobble: 13-esperanto done in 34ms
gobble: 14-es6transpiler done in 313ms
gobble: 15-moveTo done in 1ms
gobble: 16-merge done in 49ms
gobble: 17-moveTo done in 0ms
gobble: 19-merge done in 3ms
gobble: build completed in 17119ms.

Yeah this is a pain point for me too. I tried to fix part of the problem the other day but it turned out to be a less trivial fix than I imagined.
There are (at least?) three things that need to happen:

[ ] Source and test files should be transpiled to ES6 in one go. At the moment, test files are bundled and then transpiled - I forget the reason. (This is also why we're using es6-transpiler for that step - 6to5 babel is excruciatingly slow with large files, but es6-transpiler has certain limitations so I'd rather remove it)
[ ] Esperanto needs to cache transformations where possible - https://github.com/esperantojs/esperanto/issues/72
[ ] Ditto for sorcery if that's possible (I suspect it may not be - it's not possible to state that if a file has unchanged, its sources are also unchanged, I opened an issue for it anyway https://github.com/Rich-Harris/sorcery/issues/2). There may be other performance optimisations for sorcery (or vlq, which does the sourcemap en/decoding) that I haven't yet investigated

Closing this - items 2 and 3 on the list above are still outstanding, but the build is now a good deal faster anyway


RMET-377 Bad store count with store names with same name as plugin tag

Description

Changes in how stores produced by the plugin are counted taking into account some more strict checking to make sure wrongful counts don't pass
Context

Type of changes

[x] Fix (non-breaking change which fixes an issue)
[ ] Feature (non-breaking change which adds functionality)
[ ] Refactor (cosmetic changes)
[ ] Breaking change (change that would cause existing functionality to not work as expected)

Platforms affected

[x] Android

Tests

Screenshots (if appropriate)
Checklist

[x] Pull request title follows the format RNMT-XXXX <title>
[ ] Code follows code style of this project
[ ] CHANGELOG.md file is correctly updated
[ ] Changes require an update to the documentation

[ ] Documentation has been updated accordingly

I may be wrong here, but from what I remember the preferences files created by the old version of the plugin follows this format: packagename-storename_SS.ext. This is what can be found in the name variable.
From what I searched on the Internet, the extension of these files seems to be XML.
So with these 2 statements, can't the logic added by this PR be safely simplified to: if (name.startsWith(ctx.getPackageName()) && name.endsWith("_SS.xml"))?
I'll refer again that I'm not 100% sure both these statements are true.

@usernuno I'll take a look at that :)


Add an abstraction for environment variables

This merge will have the addition of the "_" and "$" environment variables that are automatically managed by Terminal and BaseBuiltinCommand.
These are not really environment variables, they are just items in a dictionary, along with every other environment variable.
The "_" environment variable contains the previous command result. (a number)
The "$" environment variable contains the previous command output (or whatever they decide)
This is for alias commands using arbitrary data for arguments.
Example:
alias cdpwd="pwd & cd {$}"

lgtm


Update document format

Thanks for contributing!

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

如下格式，复制后，不可用。


Avoid -g anti-pattern

It's widely considered to be an anti-pattern to request that people globally install your Node Module. You shouldn't have to have Grunt, Bower, Webpack, Rollup, Storybook, etc, etc, etc, added to your system's global PATH.
Further, it can cause version issues. If the project I am using was written expecting an older version of X, but the newer, globally installed, version doesn't work with the project. Had the project just listed X in the devDependencies and accessed it via a npm run scriptName then when I ran npm install I'd have the correct version downloaded locally, and when I run it via npm run whatever it will use the correct version.
There should be documentation showing how to get start-storybook/build-storybook to run locally without adding anything to the PATH.
In order to run someone else's project, the expectation should be just to run npm install and npm start. If you have to globally install something, you're adding barriers of entry to getting more people to contribute.

Hi @TheJaredWilcurt. As far as I know, there are no global requirements for Storybook. getstorybook is a convenient way to add storybook to any React project, but you can also just edit by hand. The documentation is here:
https://storybooks.github.io/docs/react-storybook/basics/slow-start-guide
Please let me know if that answers your concern!

@shilman I think he might be referring to these instructions:

https://storybooks.js.org/docs/react-storybook/basics/quick-start-guide
https://github.com/storybooks/storybook#getting-started

Ok @avaly @TheJaredWilcurt. Given that there is documentation that describes how to set things up by hand without any global requirement, does that address your concern? And if not, why not?
If you think it can be made better, please feel free to submit a PR to improve the docs!

If you just added in a link to the slow guide next to the other, far easier to find, instructions that said:
"If you want instructions on using Storybook that don't require polluting your PATH, click here."
Feel free to pretty up that language, I'm no wordsmith.

We're working on better documentation, thanks for the notification we should improve on this front.
I agree, less global installs is better.
However to get a project setup from scratch it's very common to have some sort of generator you need to install globally. This is what getstorybook is.

done.


Performance: controllable anisotropic filtering

The engine currently defaults to AF maximum (16), which was due to artist demand for high quality textures. This applies to all models, and is set in totum's glb type.
However, this can negatively affect performance, so we should make it an option in the settings panel, now that there is one.
If it makes a big performance difference we can consider setting it lower by default as well.

https://github.com/webaverse/totum/blob/b2bfeb76299bcdb917cfe513e7cbcd2dc4e94723/type_templates/glb.js#L101
(ignore the fact that it's called anitaliasing; it's not)


Simple Access Token Protection

Because oauth client credentials flow might not be available, a simple token is defined.
The following properties will be used:
application.properties:
metricCA.access.token.enabled=true/false
metricCA.access.token.secret.path=/xyz/accesstoken.properties
accesstoken.properties:
metricCA.access.token.secret=abc
accesstoken.properties should be included in addition to the profile-based property in order to mount it as secret via kubernetes.

Hello Timo, can you please add gituser "eiquanasfiya" into this repo to write.
remote: Permission to devsecopsmaturitymodel/metricAnalyzer.git denied to eiquanasfiya.
fatal: unable to access 'https://github.com/devsecopsmaturitymodel/metricAnalyzer.git/': The requested URL returned error: 403

Hello Timo, can you please add gituser "eiquanasfiya" and "shery9" into this repo to write.
remote: Permission to devsecopsmaturitymodel/metricAnalyzer.git denied to eiquanasfiya.
fatal: unable to access 'https://github.com/devsecopsmaturitymodel/metricAnalyzer.git/': The requested URL returned error: 403


Add spent fuel as byproducts

Looks like no recipe I support really uses this, not quite sure why. It’ll probably become relevant with the energy rework, which is when I should revisit it.
Nullius has about a dozen items that have a burnt_result, but none are currently valid/used. Still, I should just implement support for this.

Implemented sometime


Use symbols for branch and branching identifiers.

This requires @algebraic/ast support.

Fixed by https://github.com/runkitdev/parallel-branch/commit/680bc69d5d5a212751afa1170ea61ba9212dbc4a


[MM-45164]: fix for broken images in opengraph previews

Summary
fixes broken images on opengraph previews.
The image component was not respecting the secure_url property on the imagesMetaData object.

NOTE: skipping UX and second dev review since this is only a minimal change

Ticket Link
MM-45164
Release Note
NONE

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/213354

Thanks @michelengelen
Tested, looks good to merge - pending e2es.

Verified images on opengraph previews are shown as expected

E2E report  looks good, no PR related failures.

Cherry pick is scheduled.


Add a "Migrations" or "Burndowns" section?

A common use case will be seeing what is remaining for a migration that is in progress.  Invert does a good job of surfacing information for a snapshot of time, so "Burndown" (What's remaining) might be best appropriate since we don't have the data about what the starting point was, or what the recent relative numbers were.
One of the goals of Invert is to operate without any database, so if someone wants to see something over time, they could take the metrics and pipe them into some other software to more easily see the results over time.
Adding data persistence outside of a snapshot is out of scope.

Closing as there is a currently supported way to do this.  It may change in the future, but it fulfills this need for now.


Python Warning if ipycytoscape extension is not found?

Hi all,
I would like to suggest the addition of a warning when ipycytoscape fails to find its jupyter notebook extension.
I was unable to run the Cola notebook example (or any other one) as ipycytoscape widget failed to be displayed. There was no Python traceback (nor error, nor warning) when the cell supposed to display the widget was executed (cell 4 with cytoscapeobj in Cola notebook example): no output, like a regular cell. On Binder or any working environment, this cell would return the interactive network widget.
I noticed a bunch of errors in the Javascript console when I ran the notebook. It seemed that the widget failed to instantiate: Could not instantiate widget (anonymous) @ manager-base.js:273. In the Jupyter console too, there was a 404 GET /nbextensions/jupyter-cytoscape/extension.js.
The problem was that I use jupyter_conda extension to manage project-specific kernels within a globally-installed Jupyter notebook: it automatically registers conda environments as suitable kernels to be used by a global jupyter notebook installation. Importantly, Jupyter notebook is not installed within the environment that owns the kernel. This means that ipycytoscape notebook extension was not installed at the right place when I followed the installation steps... which explains why it was not found (no widget displayed).
The obvious solution is to start jupyter notebook from within the conda environment in which ipycytoscape and its extension were installed, or to install ipycytoscape directly the base environment that owns jupyter notebook (which fails the purpose of jupyter_conda).
I believe this kind of problem would be easier to diagnostic if ipycytoscape would display a warning when it cannot find its extension (or a message like bokeh does when output_notebook() is called).
HTH

@bdelepine this is a great summary. We have looked into setting up a placeholder widget when a widget module is missing.
This is currently done in a PR to Voilà, but we think this could become core to ipywidget in 8.0.

So, we shouldn't worry about this now and wait for the ipywidget fix? Or is it worth it to look what you did on voila and reproduce it here?

I don't think this is in scope for ipycytoscape to fix this, as this is a general issue with widget libraries.

I agree that a warning handled at the ipywidget level would fix the issue (and would be more elegant).
In the meantime, maybe we could mention something in ipycytoscape install instructions to make sure users are aware that a jupyter notebook extension will be installed along the ipycytoscape package?  This is kind of obvious in retrospect... but I clearly missed that part when I first installed ipycytoscape.

In the meantime, maybe we could mention something in ipycytoscape install instructions to make sure users are aware that a jupyter notebook extension will be installed along the ipycytoscape package?

That's a great idea @bdelepine, are you interested in making this contribution yourself? Since you had the problem maybe you can explain it better?
It'd be much appreciated.
Thanks for the bug report :)

This looks like it will become part of ipywidgets core: https://github.com/jupyter-widgets/ipywidgets/pull/2960


BSOD on lxcore.sys on LxpSocketInetStreamShutdownInternal

This bug-tracker is monitored by developers and other technical types.  We like detail!  So please use this form and tell us, concisely but precisely, what's up.  Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice.
Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to<EMAIL_ADDRESS>referencing the GitHub bug number. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".

Your Windows build number:  (Type ver at a Windows Command Prompt)
15063.632

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)
Playing local video files with UWP app "ACG Player"

What's wrong / what should be happening instead:
BSOD shouldn't happen

Strace of the failing command, if applicable:  (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)
n/a, minidump will be sent to mailbox above afterwards.

See our contributing instructions for assistance.

Hello BashOnWindows team,
I have met several times BSOD recently when using UWP app “ACG Player” to play local videos on my new Surface Pro. However, when I take a look at the mini dump I found the crash happened on WSL core file lxcore.sys, instead of the app itself.
The stack trace is like:
LXCORE!LxpSocketInetStreamShutdownInternal+0xd0
LXCORE!LxpSocketInetStreamFileReleaseInternal+0x84
LXCORE!LxpSocketInetFileRelease+0x29
LXCORE!LxpSocketFileRelease+0x36
LXCORE!VfsFileNotifyFileDescriptorClose+0x51
LXCORE!LxpFileDescriptorCloseInternal+0x87
LXCORE!LxpFileDescriptorCloseInTable+0x69
LXCORE!LxpFileDescriptorClose+0x3a
LXCORE!LxpSyscall_CLOSE+0x3a
LXCORE!LxpSysDispatch+0x17d
LXCORE!PicoSystemCallDispatch+0x16
nt!PsPicoSystemCallDispatch+0x1f
nt!KiSystemServiceUser+0x82
0x00007f51`fb410560
As requested the mini dump is sent to<EMAIL_ADDRESS>mailbox.
Please kindly check if this is a known issue.
Best Regards,
Alex

The issue is just happen again. And this time, the crash happened on dwm.exe. with current dump class VIDEO_SCHEDULER_INTERNAL_ERROR. So I have no idea why last dump shows the crash on lxcore.sys. I think the latest dump should be the issue. Unfortunately I didn't see any stack due to missing symbolic information. I will turn to the app developer to check. But anyway if there is any finding with my mini dump for lxcore.sys will be very appreciated.

I have confirmed this is a known issue that is fixed in insider build and the fix is being backported to Creators Update.  In the future sending the dump to<EMAIL_ADDRESS>is the only thing required, you do not also need to create a GitHub issue.


Error "Type of […] is partially unknown" is shown when using requests package

Environment data

Language Server version: 2020.7.2
OS and version: macOS 10.15.5
Python version (& distribution if applicable, e.g. Anaconda): 3.8.3

Expected behaviour
No issue is shown in "Problems".
Actual behaviour
The following issue is shown in "Problems":
Type of "get" is partially unknown
Type of "get" is "(url: str | bytes, params: Mapping[str | bytes | int | float, str | bytes | int | float | Iterable[str | bytes | int | float]] | str | bytes | Tuple[str | bytes | int | float, str | bytes | int | float | Iterable[str | bytes | int | float]] | Mapping[Text, str | bytes | int | float | Iterable[str | bytes | int | float]] | Mapping[bytes, str | bytes | int | float | Iterable[str | bytes | int | float]] | Mapping[int, str | bytes | int | float | Iterable[str | bytes | int | float]] | Mapping[float, str | bytes | int | float | Iterable[str | bytes | int | float]] | None = ..., **kwargs) -> Response"

Is this a problem in ~/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/api.pyi?
Logs
[FG] parsing: […]/test.py (6ms)
[FG] binding: […]/test.py (0ms)
[BG] analyzing: […]/test.py ...
[BG]   parsing: […]/test.py (5ms)
[BG]   binding: […]/test.py (0ms)
[BG]   checking: […]/test.py ...
[BG]     parsing: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/__init__.pyi (3ms)
[BG]     binding: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/__init__.pyi (3ms)
[BG]     parsing: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/api.pyi (1ms)
[BG]     binding: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/api.pyi (1ms)
[BG]     parsing: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/models.pyi (6ms)
[BG]     binding: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/third_party/2and3/requests/models.pyi (2ms)
[BG]     parsing: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/stdlib/3/typing.pyi (20ms)
[BG]     binding: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/stdlib/3/typing.pyi (9ms)
[BG]     parsing: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/stdlib/3/abc.pyi (3ms)
[BG]     binding: […]/.vscode/extensions/ms-python.vscode-pylance-2020.7.2/server/typeshed-fallback/stdlib/3/abc.pyi (3ms)
[BG]   checking: […]/test.py (81ms)
[BG] analyzing: […]/test.py (86ms)

Code Snippet / Additional information
import requests

requests.get("https://github.com/microsoft/pylance-release")

Thanks for reporting this.
I presume that you are using strict type checking mode.
The problem here is with the requests/api.pyi typeshed stub file. It is missing type annotations for the kwargs parameters. Most other typeshed stub files include annotations for kwargs (typically Any).
A fix will need to be submitted to the typeshed repo.

This was fixed in typeshed a while ago.


where is the release??

You have already updated master branch but no release
best regards

Still working on validations...
On Apr 25, 2016 6:32 PM, "HatemJerbi"<EMAIL_ADDRESS>wrote:

You have already updated master branch but no release
best regards
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/242


The example app for "Zipline: Stylize Stories on Camper News" is stuck in a loop of fetching a non existing image

Steps to reproduce

Go to the app
Open the console

I can not reproduce this, the story must have been removed or the code fixed or something? Did this make the instructions for the Zipline hard to understand in any way, or did the goal of the challenge still come across clear?

I was also able to reproduce this bug by simply visiting the page

This issue cannot really be fixed as Geoff Storbeck created and still hosts this pen. However it's not an issue as the demo still works perfectly regardless of what the console is doing. This issue can be closed primarily as there is very little that can be done about it I'm afraid

@benmcmahon100 We can fork and replace it here
That error seems to come from here, which we should be able to update/fix. What do you think?

@alexlincoln Go for it if you want to and you know how to do the fix! I can't go and take credit for your idea! If you want/need my to do it I can sort it out though

Yeah so the reason it went in an infinite loop was because each time an error occured, it would always replace the src string with the same one. It's fixed here by replacing bad images with a random 404 image. I'll submit a PR shortly to update it on the zipline.

Awesome work!

wait, @alexlincoln Did you submit a PR to fix this?

@BerkeleyTrue Yes, but it was never merged

You closed the PR after two days, right?


Divergent case: rustfmt increases indentation on each invocation in rustfmt::skip'd block

In the following example, rustfmt increases the indentation of the line with }); by one level each time it is run:
macro_rules! pwm_timer_init {
    ($tim:expr) => {{
        let tim = $tim;
        #[rustfmt::skip]
        tim.ccmr1_output().write(|w| {
            w
                .oc1pe().enabled()
                .oc1m().pwm_mode1()
                .oc2pe().enabled()
                .oc2m().pwm_mode1()
        });
    }};
}

This is also visible in the nightly version of the playground, though I found it with rustfmt 1.5.1-stable (4b91a6e 2022-08-08).

looking into this a little more, and I think this issue might have to do with the #[rustfmt::skip] attribute.
Input
macro_rules! pwm_timer_init {
    ($tim:expr) => {{
        let tim = $tim;
        tim.ccmr1_output().write(|w| {
            w
                .oc1pe().enabled()
                .oc1m().pwm_mode1()
                .oc2pe().enabled()
                .oc2m().pwm_mode1()
        });
    }};
}

Note: the  }); is not indented in the following output after formatting with rustfmt 1.5.1-nightly (ef911542 2022-09-19)
Output
macro_rules! pwm_timer_init {
    ($tim:expr) => {{
        let tim = $tim;
        tim.ccmr1_output().write(|w| {
            w.oc1pe()
                .enabled()
                .oc1m()
                .pwm_mode1()
                .oc2pe()
                .enabled()
                .oc2m()
                .pwm_mode1()
        });
    }};
}

Similar issue (#5489), but might not be the same underlying problem.


ASP.NET Core endpoint definition comments

In the 2nd snippet under https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-3.1#aspnet-core-endpoint-definition-1, there are comments on each endpoint. The comments were removed in #23932
@serpent5  Should they be restored?

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

ID: 32374077-e02e-d6a6-1cea-05e58447b7cd
Version Independent ID: 86aeab13-1c25-9fc1-4e56-0390cb40c242
Content: Routing in ASP.NET Core
Content Source: aspnetcore/fundamentals/routing.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

I don't think it would hurt to add them back. My thinking at the time was that the explanation that followed, along with the sample output, covered it all in detail. I've also been trying to move away from inline comments where possible, as I've seen we have the "should we translate comments" notice on some of them.
What brought this to your attention?

. I've also been trying to move away from inline comments where possible, as I've seen we have the "should we translate comments" notice on some of them.

I'm the one who started that survey. Many folks said, "Why do it survey, it's obvious they would like translated comments.". I was sure that was true but I needed some data to get the translation team interested. It turns out virtually no one wants MT comments.
I used to avoid them, but now when they're useful I add them.

What brought this to your attention?

I stumbled across it and it seemed better with the comments.

Ok, cool. I'll make sure I take those findings into consideration in future then.


More strict testing of handshake behaviour

Motiviation:
We should ensure we not need any extra wrap / unwrap calls during handshake once the handshake was signaled as finished
Modifications:
More strict testing
Result:
Better testing of handshake behaviour

Cherry-picked into 4.1 (1a05463) and 4.0 (e090178)


prevent incorrect escape codes in user and emoji discord ids

Describe the bug
When a user enters their discord player mapping or emoji mapping, they need to use special unicode escape sequences.
This can be problematic if the wrong escape sequence is used.
Fix this by at least validating that the correct escapes are used. Even better, modify the parsing so that the correct sequence is inserted if it's missing.

The reason these escape sequences are necessary appears to be due to how JSON encodes the brackets. The simplest fix is to automatically add the brackets if they are missing. This allows the config file to drop the escape sequences.
Unfortunately, because escape sequences are converted by the JSON parser, it's not easy to detect and warn about incorrect sequences.
The latest code in master has at least enabled automatic insertion of the angle brackets required, so I believe this can be closed.


k3s service error msg "Failed to connect to proxy" error="dial tcp <IP_ADDRESS>:6443: co...ute to host"

Environmental Info:
K3s Version:
v1.21.2+k3s1
Node(s) CPU architecture, OS, and Version:
x86_64, RHEL7.9
Cluster Configuration:
Single node server
Describe the bug:
Installed the k3s server on VM on openstack (with ip <IP_ADDRESS> via dhcp), make an image from the VM.
Create a new instance from the image with a new ip (<IP_ADDRESS> via dhcp).
systemctl status k3s.service shows error message below:
time="2021-06-30T21:18:30.434609851-04:00" level=error msg="Failed to connect to proxy" error="dial tcp <IP_ADDRESS>:6443: co...ute to host"
time="2021-06-30T21:18:30.434687885-04:00" level=error msg="Remotedialer proxy error" error="dial tcp <IP_ADDRESS>:6443: conn...ute to host"
Something requires clean up about the old ip address (<IP_ADDRESS>) before make the image template?
Where is the ip (<IP_ADDRESS>) information stored if a clean up required?
Steps To Reproduce:
Installed the k3s server on VM on openstack (with ip <IP_ADDRESS> via dhcp), make an image from the VM.
Create a new instance from the image with a new ip (<IP_ADDRESS> via dhcp).
systemctl status k3s.service

Installed K3s:

Expected behavior:
systemctl status k3s -- no error message complaining the old ip address which is from the template image
Actual behavior:
k3s service show error message, the cluster has coredns udp i/o timeout.
read udp <IP_ADDRESS>:55701-><IP_ADDRESS>:53: i/o timeout (<IP_ADDRESS>:53 is coredns svc)
Additional context / logs:
A restart of k3s will resolve the coredns udp i/o timeout issue. And other pods which depends on dns query will up running from dead-loop restarting.

I would recommend installing with INSTALL_K3S_SKIP_START=true if you're going to make an image of the host, otherwise every instance you start from that image will essentially be a copy of the same cluster - same root CA, same kubeconfig, same information about the original (but nonexistent) node, etc.

Thank you @brandond for your suggestion!
But I have to start k3s because I need install extra services like docker registry (harbor), httpd (nginx) during the template/image build.
The question is that any extra clean up I missed to clean/remove the ip address in that template VM? My guess is something in etcd? Or I need pass the "--bind-address" explicitly with systemd starting the k3s service?

I should mention that old version (we picked last year) has not an issue.
k3s version v1.0.1 (e94a3c60)```

Our existing template was build a year ago with k3s version v1.0.1. Now I am trying to update it to the latest v1.21.x.

You're building a cluster on one node, and then shutting it down and loading it up on a new node. It's going to go looking for the other node, unless you delete the original node from the cluster after starting it up on the new node.

The scenario is exactly. What is interesting for me is that a restart of the k3s service (systemd restart k3s) will bring up the cluster running correct without any error. What I am doing so for as a workaround is use ansible rescue to restart k3s service after 90s timeout of kubectl wait for pods ready.
Also k3s v1.0.1 (early last year) has no such an issue. I wonder something must changed.

v1.0.1 is from December of 2019 - over a year and a half ago - and includes Kubernetes 1.16. A LOT has changed, both in Kubernetes, and in K3s, since then.
If you're not already doing this, I would probably drain/cordon the original node before you image it, and delete the original node from the Kubernetes cluster when the new node starts up. That should help things get rescheduled sooner.

@brandond Thanks for the suggestion and support. I am going to live with the 'restart' workaround for now.

I'm having this same issue. Also using OpenStack.

So is Icy, over here https://github.com/k3s-io/k3s/issues/535#issuecomment-1020295149

Here is another copy of the same issue (but maybe not with openstack, I've asked):

https://github.com/k3s-io/k3s/issues/4587#issue-1064684164


NLS Enablement (light)

Move texts to properties files to enable translation.
Define message catalogs (enums?) with message codes for error/info messages.
Probably need a helper class for looking up the properties, to avoid duplication in the catalogs.
This is just about texts, no consideration of text direction, and with the server locale only.
However, there should be comments explaining how to handle client-provided locales.

Useful references for the documentation:
http://www.w3.org/International/questions/qa-i18n
http://www.unicode.org/glossary/#internationalization

Now that pityoulish.tutorial uses a message catalog, the Tutorial description needs to be updated. There is an additional utility package pityoulish.i18n, which students should ignore.

Catalogs implemented for the Tutorial. Translated into German, too.

The pityoulish.ticketing package still needs to be NLS-enabled.

The pityoulish.sockets.tlv package contains hard-coded exception messages.


[Improvement][WebSite]Official website construction

[ ] Add contributor guide
please refer https://dolphinscheduler.apache.org/en-us/community/team.html

[ ] Add a Blog page to the navigation bar
Add a blog column to the navigation bar, place user cases and some sharing,

https://interestinglab.github.io/seatunnel-docs/#/zh-cn/case_study/
These contents can be migrated, and the English version needs to be provided by contributors first.

[ ] Document structure adjustment
Documents need to support Chinese and English switching, you can refer to the structure of DolphinScheduler

1.X is kept in the web-site warehouse, 2.x we will parse the documents in the code warehouse, and follow-up documents follow the code warehouse.

[ ] Add FAQ Page
InterestingLab/seatunnel#267
The FAQ page needs to be translated into English. And provide a separate page.

[x] Add a user page
https://skywalking.apache.org/users/

Add a user page in the user column of the navigation bar
Similar to skywalking
Our registered users can be found here Who is using SeaTunnel)

[ ] English page Chinese translation
https://seatunnel.apache.org/

NOTICE: please submit code to https://github.com/apache/incubator-seatunnel-website

@CalvinKirs @wolfboys where should we put blog contents?

@CalvinKirs @wolfboys where should we put blog contents?

such as :https://skywalking.apache.org/blog/ WDYT?

@CalvinKirs @wolfboys where should we put blog contents?

ok, let me deal with it

@CalvinKirs I will deal with the 'Add contributor guide'

@CalvinKirs I will deal with the 'Add contributor guide'

Add contributor guide has been completed https://github.com/apache/incubator-seatunnel-website/pull/27


[BUG] Unable to run desktop applications by using desktop flag

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 11 Family Chinese version 21H2
FiftyOne installed from (pip or source): both pip and source
FiftyOne version (run fiftyone --version): FiftyOne v<IP_ADDRESS>, Voxel51, Inc.
Python version: 3.10.4

Describe the problem
When I started the Fiftyone desktop application in Python, the application raised a FileNotFoundError exception and said that the system could not find the specified file, causing the desktop application to fail to start.
Code to reproduce issue
import fiftyone as fo
import fiftyone.zoo as foz

if __name__ == '__main__':
    dataset = foz.load_zoo_dataset(
        "coco-2017",
        split="validation",
        dataset_name="evaluate-detections-tutorial")
    dataset.persistent = True
    session = fo.launch_app(dataset, desktop=True)
    session.wait()

Other info / logs
First, attach the log output to the terminal when running the program
Downloading split 'validation' to 'C:\Users\batu\fiftyone\coco-2017\validation' if necessary
Found annotations at 'C:\Users\batu\fiftyone\coco-2017\raw\instances_val2017.json'
Images already downloaded
Existing download of split 'validation' is sufficient
Loading existing dataset 'evaluate-detections-tutorial'. To reload from disk, either delete the existing dataset or provide a custom `dataset_name` to use
Desktop App launched.
Uncaught exception
Traceback (most recent call last):
  File "D:\Develop\Python\FiftyOne_test\PIPENV_VENV_IN_PROJECT\FiftyOne_test-EhvB1Jtk\lib\site-packages\fiftyone\service\main.py", line 257, in <module>
    child = psutil.Popen(
  File "D:\Develop\Python\FiftyOne_test\PIPENV_VENV_IN_PROJECT\FiftyOne_test-EhvB1Jtk\lib\site-packages\psutil\__init__.py", line 1358, in __init__
    self.__subproc = subprocess.Popen(*args, **kwargs)
  File "F:\Python\3.10.4\lib\subprocess.py", line 966, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "F:\Python\3.10.4\lib\subprocess.py", line 1435, in _execute_child
    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] 系统找不到指定的文件。

Then I found the problem through the search in the afternoon, and the wrong place is located in the first 447 line of fiftyone/core/service.py . The os.path.join() function is called to return the merged path to the full executable file, but instead of passing in the argument and adding a slash in the middle, it uses the plus to merge the two strings directly, rather than passing in the argument and adding slashes in the middle, resulting in the path being fiftyone\\desktop\\binFiftyOne 0.19.4.exe.
The solution is to replace the 447 line of the fiftyone/core/service.py file with this:
return [os.path.join(pre + path)]  # before

return [os.path.join(pre, path)]     # after

I'm not very good with Github's pull request feature, so I'll just write it here. I was hoping you could help me fix the bug.
P.S. My English is not very good, so I used translation software to write this issue. I would be glad to provide more information if THERE is any unclear expression.
What areas of FiftyOne does this bug affect?

[x]  App: FiftyOne application issue
[ ]  Core: Core fiftyone Python library issue
[ ]  Server: Fiftyone server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[x] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community.
[ ] No. I cannot contribute a bug fix at this time.

thank you so much @benjaminpkane !
have a nice day


Windows CPP_PACKAGE+GPU Build Fails inside python at opwrapper stage under certain conditions (using python version >= 3.8 or having certain GPU)!

This bug is relevant to 2.0-RC0 which I am using, but as far as I understand it, it applies to all previous versions and as people update their python version, all the older versions of the mxnet build will also break.
Description
For about a week I have been pulling out hair trying to get mxnet to build. There are actually several bugs with building on vs2019 that prevent it from completing and I had to make modifications to the source code:

replace floor() with floorf(), ceil with ceilf(), round() with roundf() everywhere (As per a discussion on the blender forums)
https://devtalk.blender.org/t/cuda-compile-error-windows-10/17886/5
instantiate 6 templates as per #17633
sneak lapack.lib into the linker because for some reason the cmake script assumes windows does not have it and excludes it on purpose (I got my OpenBLAS and Lapack from vcpkg if that matters)

I used the same flags as the windows GPU CI script, except I also enabled the USE_CPP_PACKAGE because I require it. After doing those things the libmxnet.dll is produced, but the build fails in python when generating the opwrapper
Three other things that are very important about my system:

Python 3.10
I have a gtx660 installed, which is a device that supports maximum mxnet_30
I have CUDA 11.2 installed, because I am trying to make builds for someone else. This machine is a powerful build machine so we dont have to do builds at home on our laptops. I am not going to use MXNet on my 660, it just happens to be there on the build machine.

Ok so when the build gets to python, it fails in two different ways due to two different problems

python >= 3.8 changed the search path for dlls, it no longer searches PATH so when loading libmxnet.dll, it fails because the cudart DLL is missing.

The error message is
FileNotFoundError: Could not find module 'F:\incubator-mxnet\build\Debug\libmxnet.dll' (or one of its dependencies). Try using the full path with constructor syntax.
The fix to this, a call to  "os.add_dll_directory" MUST be used for python versions >= 3.8
https://docs.python.org/3/library/os.html#os.add_dll_directory
https://issueantenna.com/repo/academysoftwarefoundation/imath/issues/238

after loading the cuda dlls, the code now crashes with a mysterious error about "writing 000000000" when in fact it is trying to load a version of mxnet_xx.dll which does not exist as a file on this computer. During automatically determining the version to use, it arrives at a DLL which does not exist and tries to load it anyways

Error Message
first:
FileNotFoundError: Could not find module 'F:\incubator-mxnet\build\Debug\libmxnet.dll' (or one of its dependencies). Try using the full path with constructor syntax.
after adding cudart_xxx to the search path (this message is from python 3.10, it might vary based on your python version):
OSError: exception: access violation writing 0x0000000000000000
Steps to reproduce

Be on windows 10
Build with CPP_PACKAGE and CUDA enabled
Have a python version >3.8 (bug in mxnet)
OR
Have a GPU installed that is so old the installed CUDA version does not support it (needs documentation in mxnet)

My Solution
The solution for cudart DLL:

if you just need to to work, copy the dll from the CUDA folder to right beside libmxnet.dll
to fix this in the python code the python version has to be detected and then call "os.add_dll_directory" with the cuda folder

The solution to proceed with old hardware:

go into "warp_dll.cpp" and change the code that detects the version of mxnet_xx.dll. Hard-code it to the version that you have built, for example
'wsprintfW(dll_name, L"mxnet_52.dll", version);'
re-run the build, it should rebuild libmxnet.dll, then the python should execute
undo the change to the code, and rebuild again to go back to a normal binary that will detect the correct version of mxnet based on hardware (as long as you HAVE the hardware 🙃)

Better solutions?

the solution to find cudart dll from python is already "better" and should be implemented ASAP, python 3.7 is the oldest version available on the windows store and will soon be deprecated

I think that it should be documented right at the top of the main CPP build instructions that having supported hardware is a hard requirement. It might seem obvious to some people but there are situations where people like me might want to build the code even with no GPU at all. what would happen then? I dont know, someone that knows should write that into the instructions

Mxnet could try a little harder when it is searching for DLLs, after finding out that it is about to load a DLL that does not exist, maybe spit out an error message or something with the name of the dll and a message to get better hardware or rebuild

The build could pull the same screwy crap that i tried to do to enable building on any platform with a non-suitable GPU - but maybe thats complicated?

Mxnet could look at some configuration file when deciding what core DLL to choose and if there is an overriding value it just uses that instead of autodetect.

note: you might have been wondering "why not just build mxnet_30" and the answer is because it was deprecated in cuda 11.2, so when you try to do that, it fails and says "that is fully deprecated". I would have to uninstall it and install cuda 10.

Environment

Environment Information
----------Python Info----------
Version      : 3.10.2
Compiler     : MSC v.1929 64 bit (AMD64)
Build        : ('tags/v3.10.2:a58ebcc', 'Jan 17 2022 14:12:15')
Arch         : ('64bit', 'WindowsPE')

I actually found a much more elegant way to let the build proceed without messing with the C code at all.... just tell the python script to directly load one of the "mxnet_xx.dll" dlls instead of "libmxnet.dll". This can be done from the cmake script. The cuda path will come from there too. In the end only the cmake and python should be modified and it should let the build proceed on systems with insufficient GPUs. Should I make a PR?

Adding onto this I also had similar issues building on windows.

just tell the python script to directly load one of the "mxnet_xx.dll" dlls instead of "libmxnet.dll"

I just had this issue pop up, and thanks for letting me know about the fix; I also ended up rewriting libinfo.py to use the much more robust pathlib (https://pastebin.com/h530XpJ7) and in base.py ; libinfo.find_lib_path() -> libinfo.find_lib_path(prefix="mxnet_75"). It'll only work on windows, but I am leaving it as a reference.

the build fails in python when generating the opwrapper

I ended up having to put all the *.dll files and their dependencies into the cpp-package\scripts folder to past that error, I just wanted to add to the point that something is wrong with the way files are being searched for.
Also, as a final point of reference: this is what worked to get it to build out-of-source inside VS 2022 x64 command line with cmake/ninja using CUDA 11.6, CUDNN 8.3, and vcpkg:
cmake -S "." -B "../build" -DCMAKE_TOOLCHAIN_FILE="C:/vcpkg/scripts/buildsystems/vcpkg.cmake"  -DCMAKE_INSTALL_PREFIX="D:/programs/mxnet/" -DCMAKE_BUILD_TYPE=Distribution -DCMAKE_C_COMPILER="cl.exe" -DCMAKE_CXX_COMPILER="cl.exe" -DMSVC_TOOLSET_VERSION=143 -G "Ninja" -DUSE_CPP_PACKAGE=1 -DUSE_CUDA=1 -DUSE_CUDNN=1 -DUSE_MKLDNN=1 -DUSE_NVRTC=1 -DUSE_OPENCV=1 -DUSE_OPENMP=1 -DBLAS=open -DUSE_DIST_KVSTORE=0 -DMXNET_BUILD_SHARED_LIBS=1 -DUSE_CXX14_IF_AVAILABLE=1

Hi, guys. I have compiled and installed successfully mxnet(v1.9.x) with python3.8 and cuda11.3(RTX 3060) on Windows11 in these days. Performance in a model of D2L is not bad. Actually, I also had the same problems. So, I leave my steps as a reference.

Following the official website and installing all dependencies. https://mxnet.apache.org/get_started/build_from_source
Compiling the mxnet with mxnet/ci/build_windows.py. Before the start, I modify the parameter this line to "Auto", and I modify all folder addresses and add CUDNN_ROOT path to adapt the CMake configuration below this line of code.

        if 'CUTENSOR_ROOT' not in os.environ:
            os.environ["CUTENSOR_ROOT"] = "D:\\libcutensor"

python /ci/build_windows.py, waiting to complete.
The following is important. No Running python setup.py install in windows_package, since it occurs same problems. So, i copy compiled binaries like mxnet_xx.dll and libmxnet.dll tomxnet\python\mxnet. Then Coping all dependencies to the same folder. For many .dll names, please refer to the release in my repository in which u could find all DLL files with  similar names.
Using python -m pip install -e /mxnet/python/ to install the python module of mxnet. And u may test it with some code.


Update HitbtcAdapters.java

There is no delimiter in retrieved order id... Looks like this library has not been used for a long time.

Looks like you broke the unit tests for HitBTC

Sorry for that, I am not home and I failed to commit the tests, will do
tomorrow morning ASAP.
Sorry again.
2017-07-18 23:56 GMT+02:00 Tim Molter<EMAIL_ADDRESS>
Looks like you broke the unit tests for HitBTC
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/timmolter/XChange/pull/1616#issuecomment-316209987,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADg7xq5JEVP_85SzuEg9c3euR6idfzOHks5sPSoIgaJpZM4ObaSb
.

No worries, take your time. It doesn't affect the main code base. Thanks for your contribution.


Start supporting Cairo1 execution

This change is

Current dependencies on/for this PR:

main

PR #448

PR #449

PR #451

PR #450

PR #452

PR #458

PR #459

PR #460

Current dependencies on/for this PR:

main

PR #448

PR #449

PR #451

PR #450

PR #452

PR #458

PR #459

PR #460


Not show list-mark on empty editor

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
10.5.13
Steps to reproduce

Set/unset numbered-list on empty editor.
Set/unset bulleted-list on empty editor.
Set numbered-list on empty editor and then input any characters.(delete them)
Input any characters(just return-key on movie) and then set numbered-list.

Expected results
The list mark(number or bullet) is shown whenever setting numbered-list or bulleted-list.
Actual results
Any mark is not shown when setting numbered-list or bulleted-list on cases of empty editor.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:flutter_quill/flutter_quill.dart' as quill;

class FlutterQuillWidget extends StatefulWidget {
  const FlutterQuillWidget({super.key});

  @override
  State<FlutterQuillWidget> createState() => _FlutterQuillWidgetState();
}

class _FlutterQuillWidgetState extends State<FlutterQuillWidget> {
  late quill.QuillController _controller;

  @override
  void initState() {
    super.initState();

    _controller = quill.QuillController(
        document: quill.Document(),
        selection: const TextSelection.collapsed(offset: 0));
  }

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        resizeToAvoidBottomInset: false,
        appBar: AppBar(
          title: const Text('Flutter Quill'),
        ),
        body: Column(children: [
          quill.QuillToolbar.simple(controller: _controller),
          quill.QuillEditor(
            controller: _controller,
            scrollController: ScrollController(),
            focusNode: FocusNode(),
            configurations: const quill.QuillEditorConfigurations(
                scrollable: true,
                autoFocus: false,
                expands: false,
                placeholder: "Add your data here..."),
          ),
        ]));
  }
}

Additional Context

Screenshots / Video demonstration
https://github.com/user-attachments/assets/7b4b6d62-e9e2-4db8-a48f-de036f424f13

Logs
[Paste your logs here]

I'll fix it.

Thanks to fast fix.
I've confirmed it on the latest version.


Create Contributing.md file

Create Contributing.md file

Please assign me

#5 solved this

Please assign me


Switch back to official LevelDB repo, patch it on build

This pull request is to be applied on top of https://github.com/siddontang/ledisdb/pull/325 - entire diff from that pull request is this commit: https://github.com/siddontang/ledisdb/commit/97ed9d8f25bba48385092b22c85f1d3657bd07de

switches back to using LevelDB from github.com/google/leveldb
updates to the latest version (and even a bit ahead of the 1.20 tag to be able to set max file size)
applies a patch tuning LevelDB (part of the diff in repo used before)
exposes new LevelDB option - you can now configure max file size when launching LedisDB

Note: this is largely untested - preparatory work for the Dockerfile branch I'll be pushing soon.

Rebased & tests passing.

LGTM


Post Install Script Fails in 7.2.0 version due to yarn dependency missing

Post install script fails for 7.2.0 version. It uses yarn. Our source doesn't use yarn to manage its dependencies. 7.1.1. didn't have this script.
Console Output -

<EMAIL_ADDRESS>postinstall /home/ubuntu/xxxxxxxxxx/node_modules/amplitude-js
cd website/ && yarn install
sh: 1: yarn: not found
[?25l[[7m            [27m[90m......[0m] \ postinstall: [32minfo[0m [35mlifecycle[0m<EMAIL_ADDRESS>[37;40mnpm[0m [0m[31;40mERR![0m [0m[35mcode[0m ELIFECYCLE
[0m[37;40mnpm[0m [0m[31;40mERR![0m [0m[35msyscall[0m spawn
[0m[37;40mnpm[0m [0m[31;40mERR![0m [0m[35mfile[0m sh
[0m[37;40mnpm[0m [0m[31;40mERR![0m [0m[35merrno[0m ENOENT
[0m[37;40mnpm[0m [0m[31;40mERR![0m[35m[0m<EMAIL_ADDRESS>postinstall: cd website/ && yarn install
[0m[37;40mnpm[0m [0m[31;40mERR![0m[35m[0m spawn ENOENT
[0m[37;40mnpm[0m [0m[31;40mERR![0m[35m[0m
[0m[37;40mnpm[0m [0m[31;40mERR![0m[35m[0m Failed at the<EMAIL_ADDRESS>postinstall script.
[0m[37;40mnpm[0m [0m[31;40mERR![0m[35m[0m This is probably not a problem with npm. There is likely additional logging output above.

Expected Behavior
Backward compatibility. If yarn is not available use npm.

Current Behavior
Expects Clients to have yarn as a dependency to run its post install script.

Possible Solution
Not use yarn or use npm if yarn not available. Or add yarn as a dependency.

Steps to Reproduce

Run post install script. Don't have yarn as a package manager

Environment
Node

+1

+1

Is it really needed to install documentation dependencies if amplitude-js is transitive dependency

Same, any update?

Looking at it right now

Thanks for the notice guys. Should be fixed in 7.2.1 now.


Switching .vtf textures preview using keyboard arrows.

In the current version 3.3.5 win64.
When using the "down arrow" and "up arrow" keys on the keyboard, there is no switching between textures in the preview.
Texture preview only works when clicked with the mouse.
This complicates navigation and limits the convenience of using the viewer.
https://github.com/craftablescience/VPKEdit/assets/30258996/b57abaef-8a0d-42da-a727-528eecca35c0

This is a good suggestion and I'll look into it


Proxy configuration command doesn't work

The command line script suggested under proxy configuration is missing opening and closing quotes in the true . This happens for all versions of the script (Windows VM, Linux VM, etc.).
This is how the script is currently:
$settingsString = '{"proxy":{"mode":"application","address":"http://[address]:[port]","auth": true}}'; $protectedSettingsString = '{"proxy":{"username":"[username]","password": "[password]"}}'; Set-AzVMExtension -ExtensionName AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion <type-handler-version> -SettingString $settingsString -ProtectedSettingString $protectedSettingsString
and it should be:
$settingsString = '{"proxy":{"mode":"application","address":"http://[address]:[port]","auth": "true"}}'; $protectedSettingsString = '{"proxy":{"username":"[username]","password": "[password]"}}'; Set-AzVMExtension -ExtensionName AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion <type-handler-version> -SettingString $settingsString -ProtectedSettingString $protectedSettingsString
Regards

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

ID: 14a66a45-7f5b-b9c4-c675-bd2cc963b44d
Version Independent ID: 253cc884-5a70-c313-67c7-68f42b6e44c3
Content: Define Azure Monitor Agent network settings - Azure Monitor
Content Source: articles/azure-monitor/agents/azure-monitor-agent-data-collection-endpoint.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@javiersoriano Thanks for your comment. We will review the issue and get back to you shortly.


Consistently name permission settings.

See https://chat.zulip.org/#narrow/channel/101-design/topic/name.20permissions.20settings.20consistently/near/1959774
The last commit doesn't exactly fit the bill of the settings discussed on CZO but I think it would still be good to remove that question mark, we can leave that commit off, if we don't want to remove the question mark.

Screenshots and screen captures:
Organisation settings:

Channel settings:

Group settings:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@shubham-padia could you please add screenshots of the updated setting panels? Skipping help center screenshots is fine.

Updated with screenshots!

All looks good to me, thanks!

Merged, thanks @shubham-padia!


Update backend-pool-management.md

The following fact hasn't been mentioned anywhere in the doc. I've added it for clarity to inform readers about their options.
"You can create more than one backend pool if you want to load balance traffic differently for different sets of resources. By creating multiple load balancing rules, each targeting a different backend pool, you can ensure that traffic is distributed according to your specific requirements across different sets of backend resources."
Note that this and all my PRs follow Microsoft Certification Exam – Candidate Agreement and other relevant NDAs.
PS: @mbender-ms I just noticed that you've closed some of my PRs assuming that I'm violating exam NDAs. Thanks for your concern but I haven't violated any NDA nor have shared any actual exam questions. I take a lot of practice tests (from 3rd party websites). Subsequently, I've noticed gaps in the documentation. I would like to help the community by filling some of the gaps, while following all relevant NDAs.

@azarboon While I appreciate your contributions, please refrain from mentioning that suggestions are based on gaps in exam certification content knowledge in Microsoft Learn. Maybe try "I noticed you don't talk about X in your documents, and I've found this to be a knowledge gap. Please add the following..."
Currently reviewing this and other PRs, and we'll make changes as appropriate. Thanks

@mbender-ms
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi @azarboon thanks for your feedback, closing this PR as we'll incorporate this information into the following article instead: https://learn.microsoft.com/en-us/azure/load-balancer/components#backend-pool
The changes should be made in the following weeks.


[TypeChecker] Fix crash related to chained optionals in case statements

Type checker didn't handle the safe of disjoint optional chaining when trying
to convert such chaining into .Some cases, which leads to dangling
BindOptionalExpr in the AST.
Resolves: rdar://problem/35870863

/cc @CodaFi do you want to take a look since you've worked on switch statement some?

@swift-ci please smoke test

@swift-ci please test source compatibility

LGTM. Could probably fold some logic by giving the rewrite helper a more specific parameter type, but that’s not important.


PropertyChanging and PropertyChanged not fired

Describe the bug
PropertyChanging and PropertyChanged don't fire if you just inherit IReactiveObject.
But surprisingly, WhenAnyValue works!
Steps To Reproduce
class Test : IReactiveObject
  {
      public event PropertyChangedEventHandler PropertyChanged;
      public event PropertyChangingEventHandler PropertyChanging;
      public void RaisePropertyChanging(PropertyChangingEventArgs args)
      {
          //Not fired
          PropertyChanging?.Invoke(this, args);
      }
      public void RaisePropertyChanged(PropertyChangedEventArgs args)
      {
          //Not fired
          PropertyChanged?.Invoke(this, args);
      }

      private string _testProp;
      public string TestProp
      {
          get => _testProp;
          set => this.RaiseAndSetIfChanged(ref _testProp, value);
      }
  }

  public partial class App : Application
  {
      public App()
      {
          Test test = new Test();
          test.PropertyChanged += (sender, args) =>
          {
              //Not fired
          };

          test.WhenAnyPropertyChanged(nameof(Test.TestProp))
              .Subscribe(_ =>
              {
                  //Not fired
              });

          test.WhenAnyValue(q => q.TestProp)
              .Subscribe(_ =>
              {
                  //FIRED!!!
              });

          test.TestProp = "111";
          test.TestProp = "222";
      }

      protected override void OnStartup(StartupEventArgs e)
      {
          base.OnStartup(e);
      }
  }

Environment

OS:       Windows
Version   10

Additional context
This is a WPF project.
ReactiveUI: 13.1.1
ReactiveUI.WPF: 13.1.1

Oh, sorry, I see that the same problem has already been opened earlier. =(

Related To: https://github.com/reactiveui/ReactiveUI/issues/2594

I'll see about doing a point release for this bug on the weekend, closing this as a duplicate of #2594 for the moment


Vaccination Repository Part 1 (EXPOSUREAPP-6729)

Storage logic
Initial drafts stored data (some specs are still TBD)
Additional wiring & structure

Doesn't really do anything yet as server side is not ready yet, but it supplies an initial data set.
Review architecture, comment on potential issues, once all concerns are addressed, we should merge this as other tickets need this to integrate.
Draft:

[x] More unit tests

I'll perform a follow up PR with more logic and unit tests. So this is mostly about structure.


Allow methods on Dir to use Pathname

Motivation
Some of the functions on Dir can take Pathname objects in addition to strings.
Test plan
Just an RBI change so not much to test.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HbGuyRT3iQYtFd


Custom prism theme is overridden by theme-live-codeblock

🐛 Bug Report
custom prism theme configured in docusaurus.config.js will be overridden by theme-live-codeblock.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
in docusaurus.config.js:
themes: ['@docusaurus/theme-live-codeblock'],
themeConfig: {
   prism: {
      theme: require('prism-react-renderer/themes/nightOwl')
    }
}

Expected behavior
The theme of code blocks should be nightOwl
Actual Behavior
The theme of code blocks including live code block will be overridden by the internal theme of theme-live-codeblock.

Upgrade your theme-live-codeblock version to alpha.33
alpha.32 still uses the old prismTheme


Same value for Accuracy, Precision and Recall for MNIST classification with 10 classes

🐛 Bug
When computing torchmetrics Accuracy, Precision, Recall and F1 over MNIST classification, all numbers come up the same.
Also, in this case, torchmetrics Accuracy metric sets the mode to multiclass, not multilabel, so it uses exactly the same formula as Precision.
I've attached a reduced code sample below, and a larger one is available on: https://gist.github.com/lsisoft/e4933683131872976a00be3ae0fc88ea - where I have attempted to rewrite the metrics as inline versions, forcing Accuracy to use the proper formula.
To Reproduce
Steps to reproduce the behavior:

Run the code sample below
Monitor metrics in tensorboard or by debugging in the code

Code sample
import pytorch_lightning as pl
import torch
import torchmetrics
import torchmetrics.functional
from torch import nn
from torch.nn import functional as F
from torch.utils.data import DataLoader
from torch.utils.data import random_split
from torchvision import transforms
from torchvision.datasets import MNIST

class LitCritic(pl.LightningModule):
    def __init__(self):
        super().__init__()

        self.encoder = nn.Sequential(
            nn.Linear(28 * 28, 64),
            nn.ReLU(),
            nn.Linear(64, 64),
            nn.ReLU(),
            nn.Linear(64, 10))

        metrics = torchmetrics.MetricCollection([
            # Accuracy: due to mode multiclass, not multilabel, this uses same formula as Precision
            torchmetrics.Accuracy(num_classes=10),
            torchmetrics.Precision(num_classes=10),
            torchmetrics.Recall(num_classes=10),
            torchmetrics.F1(num_classes=10),
        ])

        self.train_metrics = metrics.clone(prefix='train_')
        self.valid_metrics = metrics.clone(prefix='val_')

    def forward(self, x):
        embedding = self.encoder(x)
        return embedding

    def configure_optimizers(self):
        optimizer = torch.optim.Adam(self.parameters(), lr=1e-3)
        return optimizer

    def training_step(self, train_batch, batch_idx):
        x, y = train_batch
        x = x.view(x.size(0), -1)
        z = self.encoder(x)

        loss = F.cross_entropy(z, y)
        self.log('train_loss', loss)

        z_prob = F.softmax(z, dim=-1)
        output = self.train_metrics(z_prob, y)
        self.log_dict(output)

        return loss

    def validation_step(self, val_batch, batch_idx):
        x, y = val_batch
        x = x.view(x.size(0), -1)
        z = self.encoder(x)

        loss = F.cross_entropy(z, y)
        self.log('val_loss', loss)

        z_prob = F.softmax(z, dim=-1)
        output = self.valid_metrics(z_prob, y)
        self.log_dict(output)

if __name__ == '__main__':
    # data
    dataset = MNIST('', train=True, download=True, transform=transforms.ToTensor())
    mnist_train, mnist_val = random_split(dataset, [55000, 5000])

    batch_size = 32
    train_loader = DataLoader(mnist_train, batch_size=batch_size)
    val_loader = DataLoader(mnist_val, batch_size=batch_size)

    # model
    model = LitCritic()

    # training
    trainer = pl.Trainer()
    trainer.fit(model, train_loader, val_loader)

Expected behavior
Each metric should return a different value.
Environment

PyTorch Version (e.g., 1.0): 1.8.1+cu111
OS (e.g., Linux): Ubuntu
How you installed PyTorch (conda, pip, source): pip
Build command you used (if compiling from source):
Python version: 3.8.10
CUDA/cuDNN version: CUDA 11.3
GPU models and configuration: GTX 1080
Any other relevant information:

Additional context
None

Hi @lsisoft , could you please provide which version of torchmetrics you are using?

torchmetrics==0.3.2

I have reviewed your code snippet and indeed it matches sklearn. I've moved my original code to macro and now the values for all metrics are almost what they should be.
There is a an issue that remains: Accuracy vs Precision.
For Accuracy, torchmetrics/functional/classification/accuracy.py, if I can place a debug breakpoint at line 80, it hits, due to mode=DataType.MULTICLASS
The code there looks like this:
if (mode == DataType.BINARY and average in simple_average) or mode == DataType.MULTILABEL:
numerator = tp + tn
denominator = tp + tn + fp + fn
else:
numerator = tp # <-- breakpoint
denominator = tp + fn
and due to going on the else branch, it uses same formula for Accuracy as for precision.

@lsisoft could you give me an example where the calculated value in torchmetrics deviates from the value in sklearn?

If your criteria is that it has to only match sklearn, than you can close the issue. To my is strange that it uses the wrong formula in torchmetrics and sklearn as well.

Yes our criteria is to match sklearn because they are the trusted standard for calculating these kind of metrics.
That said, I looked more into this and there is actually is no problem with that formula. The typical (tp + tn) / (tp + tn + fp + fn) is ONLY true when we are evaluating binary and multilabel examples. In the multiclass case we basically just need to compute correct/total which is exactly what our code does. Closing this issue.

I don't quite get why this should be correct (both in sklearn and torchmetrics). But maybe I just don't understand the reasoning behind this.  This also led to some confusion in a peer review.
Given the following confusion matrix:
[[105   0   0   4   3]
 [  0  95   0  15   3]
 [  0   0   0   2   0]
 [  1   0   0   2   0]
 [  1   0   0   9   2]]

An example for Class 0 (index 0), given TP = 105, TN = 95 + 15 + 3 + 2 + 2 + 9 + 2 = 128, FP = 2, FN = 7.
Accuracy = (TN + TP) / (N + P) = (128 + 105) / (128 + 7 + 105 + 2) = 0.9628
Recall/Sensitivity = TP / (TN + FN) = 105 / (105 + 7) = 0.9375
So when I calculate:
from torchmetrics.classification import Accuracy
from torch.nn.functional import one_hot

NUM_CLASSES = 7
probability_batch

# -- current implementation (multiclass) --

_target = torch.tensor([y for (_, y) in probability_batch])
_preds = torch.tensor([torch.argmax(p).cpu() for (p, _) in probability_batch])

print("_preds", _preds)
# _preds tensor([0, 0, 0, 5, 0, 0, 3, 0, 0, 0, 1, 1, 1, 3, 3, 1, 1, 1, 0, 0, 1, 3, 1, 1,
#         1, 1, 1, 1, 0, 0, 0, 0, 0, 3, 5, 0, 0, 0, 1, 0, 0, 1, 1, 0, 1, 1, 1, 5,
#         0, 0, 1, 3, 1, 3, 1, 0, 1, 1, 0, 0, 3, 0, 0, 0, 3, 0, 0, 0, 0, 0, 3, 0,
#         0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 1, 0, 0, 0, 3, 1, 1, 0, 0, 1,
#         1, 3, 0, 0, 3, 1, 1, 5, 0, 0, 0, 1, 0, 1, 1, 1, 1, 0, 0, 0, 5, 0, 0, 0,
#         1, 1, 0, 1, 1, 0, 5, 0, 0, 0, 0, 3, 3, 0, 3, 0, 3, 5, 0, 0, 0, 1, 0, 3,
#         0, 0, 0, 1, 1, 0, 3, 1, 1, 1, 0, 1, 1, 1, 3, 1, 0, 0, 0, 0, 0, 1, 1, 3,
#         0, 1, 1, 0, 0, 3, 1, 1, 1, 1, 0, 5, 0, 0, 3, 0, 1, 1, 1, 1, 3, 3, 0, 1,
#         1, 0, 1, 1, 1, 0, 1, 1, 0, 1, 3, 0, 1, 1, 1, 1, 3, 0, 1, 1, 0, 1, 1, 0,
#         3, 1, 0, 1, 0, 0, 1, 0, 1, 0, 1, 1, 1, 0, 0, 1, 3, 3, 1, 0, 0, 0, 1, 3,
#         0, 3])

print("_target", _target)
# _preds tensor([0, 0, 0, 5, 0, 0, 3, 0, 0, 0, 1, 1, 1, 3, 3, 1, 1, 1, 0, 0, 1, 3, 1, 1,
#         1, 1, 1, 1, 0, 0, 0, 0, 0, 3, 5, 0, 0, 0, 1, 0, 0, 1, 1, 0, 1, 1, 1, 5,
#         0, 0, 1, 3, 1, 3, 1, 0, 1, 1, 0, 0, 3, 0, 0, 0, 3, 0, 0, 0, 0, 0, 3, 0,
#         0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 1, 0, 0, 0, 3, 1, 1, 0, 0, 1,
#         1, 3, 0, 0, 3, 1, 1, 5, 0, 0, 0, 1, 0, 1, 1, 1, 1, 0, 0, 0, 5, 0, 0, 0,
#         1, 1, 0, 1, 1, 0, 5, 0, 0, 0, 0, 3, 3, 0, 3, 0, 3, 5, 0, 0, 0, 1, 0, 3,
#         0, 0, 0, 1, 1, 0, 3, 1, 1, 1, 0, 1, 1, 1, 3, 1, 0, 0, 0, 0, 0, 1, 1, 3,
#         0, 1, 1, 0, 0, 3, 1, 1, 1, 1, 0, 5, 0, 0, 3, 0, 1, 1, 1, 1, 3, 3, 0, 1,
#         1, 0, 1, 1, 1, 0, 1, 1, 0, 1, 3, 0, 1, 1, 1, 1, 3, 0, 1, 1, 0, 1, 1, 0,
#         3, 1, 0, 1, 0, 0, 1, 0, 1, 0, 1, 1, 1, 0, 0, 1, 3, 3, 1, 0, 0, 0, 1, 3,
#         0, 3])

acc = Accuracy(task="multiclass", num_classes=NUM_CLASSES, labels=dataset.classes, average='weighted')
# tensor(0.8430)

acc = Accuracy(task="multiclass", num_classes=NUM_CLASSES, labels=dataset.classes, average=None)
# tensor([0.9813, 1.0000, 0.0000, 0.0625, 0.0000, 0.2500, 0.0000])

# -- expected implementation (according to Accuracy = `(TN + TP) / (N + P) = (128 + 105) / (128 + 7 + 105 + 2)`)

_target = torch.tensor([one_hot(torch.tensor(y), num_classes=7).tolist() for y in _target])
_preds = torch.tensor([one_hot(torch.argmax(p).cpu(), num_classes=7).tolist() for p) in _preds])

acc = Accuracy(task="multilabel", num_labels=NUM_CLASSES, labels=dataset.classes, average='weighted')
# tensor(0.9352)

acc = Accuracy(task="multilabel", num_labels=NUM_CLASSES, labels=dataset.classes, average=None)
# tensor([0.9628, 0.9256, 0.9917, 0.8719, 1.0000, 0.9339, 1.0000])

Of course the behaviour between sklearn and torchmetrics is constant, so this is probably me ...
Just for anyone else stumpling upon this issue :sweat_smile:

I don't quite get why this should be correct (both in sklearn and torchmetrics). But maybe I just don't understand the reasoning behind this.  This also led to some confusion in a peer review.
Given the following confusion matrix:
[[105   0   0   4   3]
 [  0  95   0  15   3]
 [  0   0   0   2   0]
 [  1   0   0   2   0]
 [  1   0   0   9   2]]

An example for Class 0 (index 0), given TP = 105, TN = 95 + 15 + 3 + 2 + 2 + 9 + 2 = 128, FP = 2, FN = 7.
Accuracy = (TN + TP) / (N + P) = (128 + 105) / (128 + 7 + 105 + 2) = 0.9628
Recall/Sensitivity = TP / (TN + FN) = 105 / (105 + 7) = 0.9375
So when I calculate:
from torchmetrics.classification import Accuracy
from torch.nn.functional import one_hot

NUM_CLASSES = 7
probability_batch

# -- current implementation (multiclass) --

_target = torch.tensor([y for (_, y) in probability_batch])
_preds = torch.tensor([torch.argmax(p).cpu() for (p, _) in probability_batch])

print("_preds", _preds)
# _preds tensor([0, 0, 0, 5, 0, 0, 3, 0, 0, 0, 1, 1, 1, 3, 3, 1, 1, 1, 0, 0, 1, 3, 1, 1,
#         1, 1, 1, 1, 0, 0, 0, 0, 0, 3, 5, 0, 0, 0, 1, 0, 0, 1, 1, 0, 1, 1, 1, 5,
#         0, 0, 1, 3, 1, 3, 1, 0, 1, 1, 0, 0, 3, 0, 0, 0, 3, 0, 0, 0, 0, 0, 3, 0,
#         0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 1, 0, 0, 0, 3, 1, 1, 0, 0, 1,
#         1, 3, 0, 0, 3, 1, 1, 5, 0, 0, 0, 1, 0, 1, 1, 1, 1, 0, 0, 0, 5, 0, 0, 0,
#         1, 1, 0, 1, 1, 0, 5, 0, 0, 0, 0, 3, 3, 0, 3, 0, 3, 5, 0, 0, 0, 1, 0, 3,
#         0, 0, 0, 1, 1, 0, 3, 1, 1, 1, 0, 1, 1, 1, 3, 1, 0, 0, 0, 0, 0, 1, 1, 3,
#         0, 1, 1, 0, 0, 3, 1, 1, 1, 1, 0, 5, 0, 0, 3, 0, 1, 1, 1, 1, 3, 3, 0, 1,
#         1, 0, 1, 1, 1, 0, 1, 1, 0, 1, 3, 0, 1, 1, 1, 1, 3, 0, 1, 1, 0, 1, 1, 0,
#         3, 1, 0, 1, 0, 0, 1, 0, 1, 0, 1, 1, 1, 0, 0, 1, 3, 3, 1, 0, 0, 0, 1, 3,
#         0, 3])

print("_target", _target)
# _preds tensor([0, 0, 0, 5, 0, 0, 3, 0, 0, 0, 1, 1, 1, 3, 3, 1, 1, 1, 0, 0, 1, 3, 1, 1,
#         1, 1, 1, 1, 0, 0, 0, 0, 0, 3, 5, 0, 0, 0, 1, 0, 0, 1, 1, 0, 1, 1, 1, 5,
#         0, 0, 1, 3, 1, 3, 1, 0, 1, 1, 0, 0, 3, 0, 0, 0, 3, 0, 0, 0, 0, 0, 3, 0,
#         0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 1, 0, 0, 0, 3, 1, 1, 0, 0, 1,
#         1, 3, 0, 0, 3, 1, 1, 5, 0, 0, 0, 1, 0, 1, 1, 1, 1, 0, 0, 0, 5, 0, 0, 0,
#         1, 1, 0, 1, 1, 0, 5, 0, 0, 0, 0, 3, 3, 0, 3, 0, 3, 5, 0, 0, 0, 1, 0, 3,
#         0, 0, 0, 1, 1, 0, 3, 1, 1, 1, 0, 1, 1, 1, 3, 1, 0, 0, 0, 0, 0, 1, 1, 3,
#         0, 1, 1, 0, 0, 3, 1, 1, 1, 1, 0, 5, 0, 0, 3, 0, 1, 1, 1, 1, 3, 3, 0, 1,
#         1, 0, 1, 1, 1, 0, 1, 1, 0, 1, 3, 0, 1, 1, 1, 1, 3, 0, 1, 1, 0, 1, 1, 0,
#         3, 1, 0, 1, 0, 0, 1, 0, 1, 0, 1, 1, 1, 0, 0, 1, 3, 3, 1, 0, 0, 0, 1, 3,
#         0, 3])

acc = Accuracy(task="multiclass", num_classes=NUM_CLASSES, labels=dataset.classes, average='weighted')
# tensor(0.8430)

acc = Accuracy(task="multiclass", num_classes=NUM_CLASSES, labels=dataset.classes, average=None)
# tensor([0.9813, 1.0000, 0.0000, 0.0625, 0.0000, 0.2500, 0.0000])

# -- expected implementation (according to Accuracy = `(TN + TP) / (N + P) = (128 + 105) / (128 + 7 + 105 + 2)`)

_target = torch.tensor([one_hot(torch.tensor(y), num_classes=7).tolist() for y in _target])
_preds = torch.tensor([one_hot(torch.argmax(p).cpu(), num_classes=7).tolist() for p) in _preds])

acc = Accuracy(task="multilabel", num_labels=NUM_CLASSES, labels=dataset.classes, average='weighted')
# tensor(0.9352)

acc = Accuracy(task="multilabel", num_labels=NUM_CLASSES, labels=dataset.classes, average=None)
# tensor([0.9628, 0.9256, 0.9917, 0.8719, 1.0000, 0.9339, 1.0000])

Of course the behaviour between sklearn and torchmetrics is constant, so this is probably me ...
Just for anyone else stumbling upon this issue :sweat_smile:


Webpack -p contains comments by default

This results in a 240kb react app when it could be 160kb.
It would make sense to me that using the -p switch adds this:
new webpack.optimize.UglifyJsPlugin({comments: false})
instead of just this:
new webpack.optimize.UglifyJsPlugin()
would it make sense to strip comments by default if using -p ?

My apologies it appears this was because I was also using -d and removing -d removes the comments, I am closing this issue.


[tw] Add content/zh-tw/devsecops.md

Describe your changes

Add content/zh-tw/devsecops.md for 'DevSecOps' localization.
Original content: https://glossary.cncf.io/devsecops/

Related issue number or link (ex: resolves #issue-number)
#2195
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

Hi reviewers,
As described in issue #2167, the original page contains a reference link error, so I fix the link to match the term.


SubViewport UPDATE_ONCE lags behind a frame

Godot version
v4.0.beta.custom_build [54346e94a]
System information
Windows 10, Forward+, NVIDIA GeForce GTX 1050 Ti (<IP_ADDRESS>4)
Issue description
Updating a SubViewport with update mode UPDATE_ONCE appears to lag behind a frame. This means that two await RenderingServer.frame_post_draw is required for the SubViewport to update. At least in my testing.
Steps to reproduce
My use case has been to tile noise textures, and that is where I noticed this delay.

Create a SubViewport

Clear mode never, and update mode disabled.

Attach a Sprite2D to the viewport

Give it a NoiseTexture2D with FastNoiseLite (unnormalized for best tiling)

Write some code to update -> wait -> and sample the viewport texture
func begin_sampling():
	for y in range(0,512,64):
		for x in range(0,512,64):
			# only sample one at a time
			await sample_viewport(x, y)

func sample_viewport(x:float, y:float):
	# change noise offset
	var new_offset = Vector3(x, y, 0)
	renderer.texture.noise.offset = new_offset

	# ask viewport to draw the noise texture at the new offset
	viewport.render_target_clear_mode = SubViewport.CLEAR_MODE_ONCE
	viewport.render_target_update_mode = SubViewport.UPDATE_ONCE

	# wait until the rendering server has drawn the next frame
	await RenderingServer.frame_post_draw

	# one frame is apparently not enough
	# if you look closely, the first offset is drawn twice, and each next
	# texture lags one offset behind. This creates a seam when moving on
	# to each next row.

	# waiting another frame solves it
#	await RenderingServer.frame_post_draw

	# create an object at the noise offset. If done correctly, the noise textures should tile.
	var sprite = Sprite2D.new()
	sprite.centered = false
	sprite.texture = ImageTexture.create_from_image(renderer.texture.get_image())
	sprite.position = Vector2(new_offset.x, new_offset.y)
	add_child(sprite)

This is the result of using size 64x64 noise textures to form a 512x512 area and only waiting one frame between sampling. Each drawn texture will lag one frame behind. Each of the textures in column 1 should be the last texture on the previous row (with the exception of the top left texture, which is the same as the texture following it.)

Minimal reproduction project
Steps to reproduce in a small project. Let's you see the difference between 1 and 2 await draw.
SubViewport Draw Issue.zip

I've actually posted this issue incorrectly. I am not taking the texture from the viewport in the code above. I will update it.

Upon further testing, it might look like it is not a bug after all.
# change noise offset
renderer_texture.noise.offset = new_offset

# wait a frame for the noise texture to be updated to the new offset
await RenderingServer.frame_post_draw

# ask the viewport to draw once
viewport.render_target_clear_mode = SubViewport.CLEAR_MODE_ONCE
viewport.render_target_update_mode = SubViewport.UPDATE_ONCE

# wait until the noise texture has been drawn onto the viewport
await RenderingServer.frame_post_draw

# sample - it is drawn in the correct location with the correct offset
var texture = ImageTexture.create_from_image(viewport.get_texture().get_image())

I will close this issue.


support safari

Is it possible to be compatible with the Safari browser.?

As far as I know, safari is not supported natively, as WebRTC is not built into safari. I found a plugin for this (https://temasys.atlassian.net/wiki/display/TWPP/WebRTC+Plugins) but didn't had the chance to test it yet.
Maybe you could report if it is working?
Thanks and best regards,
Chris

SimpleWebRTC doesn't at this time support the Temasys plugin.


User onboarding flow and New channel tour

Summary
This PR introduces a UI component for the new tutorial tour tip component that isn't dependent on react-bootstrap and Use tippy instead to make it useable in our other products like Boards, Playbooks.
A new on boarding channels tour which will be replacing the existing one for all users and simple tour for other tasks( system console, user profile, invite modal)
Ticket Link
Related Pull Requests
NONE
Screenshots

before
after

Release Note
* UI: New tutorial tour tip component introduction (use new library React-tippy)

@matthewbirtch except navigation via dots in tour and check have fixed all the issue you have mentioned in https://github.com/mattermost/mattermost-webapp/pull/9774.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/150368

Code generally looks good to me; finishing up the rest of my review and post those comments a bit later. I wanted to call out sooner what I think is the main issue we need to resolve for this PR. The existing tour is stored in the preferences table as:
           userid           |            category            |            name            |     value
----------------------------+--------------------------------+----------------------------+---------------
 gan834poyibzjrodff577q3aee | tutorial_step                  | gan834poyibzjrodff577q3aee | 2
 gan834poyibzjrodff577q3aee | tutorial_step_auto_tour_status | gan834poyibzjrodff577q3aee | 0

This PR uses a new set of code for the tours, which seems fine to me. That new code also adds and reads from a new preferences entry, i.e.
           userid           |            category            |            name            |     value
----------------------------+--------------------------------+----------------------------+---------------
 gan834poyibzjrodff577q3aee | channels_tour                  | auto_tour_status           | 0
 gan834poyibzjrodff577q3aee | channels_tour                  | on_boarding_step           | 4

It uses the new entry, and disregards the old one. While this is not an issue for new users, is does mean all existing users (admin or otherwise) get put through a tour again, which is pretty similar to the existing, in-prod/deployed one (the content isn't exactly the same). @AshishDhama  @esethna @matthewbirtch are we ok with that? If not, if we're going to add the new on_boarding_step entry to the table, we should add some sort of code to migrate over existing user progress. Not sure if all steps have a tranlsation between the old tour set and the new one. If they don't, we could at least code it in so that users that were 999/FINISHED before in the old tour preference keep that status in the new on_boarding_step tour preference.

@neallred Thanks for pointing this out, Old Users will not get this tour as there is additional conditions I am going to add, that’s what I wanted to make sure when I asked about current onboarding flow next steps one I showed you in our 1-1.
This tour want be available as default, there is trigger condition which needs to be satisfied to start it. Will push soon.

Cool, will take a look when that's pushed. Thanks!

@matthewbirtch Thanks for such a detailed review,

For the video modal, it starts out blurred. How come?
could you please share image of this, I am not sure as this is Iframe it might be that’s how wista do it

Also, for the video modal, can we add the standard modal rounded corner (assume that's a variable?). There is no rounded corner right now.
It was like that in Figma, will add border-radius

We need the task list to follow us even while we're in the System Console.
I checked when you mentioned about it on MM, Due to use of styled components it wasn’t rendering in admin console(after explicitly putting it there), Then Nevy dropped a message that she will fix it, so I dropped further investigation I am not sure if we can do that with styled components but will check and get back to you tomorrow with answers.

@matthewbirtch Thanks for such a detailed review,

For the video modal, it starts out blurred. How come?
could you please share image of this, I am not sure as this is Iframe it might be that’s how wista do it

Also, for the video modal, can we add the standard modal rounded corner (assume that's a variable?). There is no rounded corner right now.
It was like that in Figma, will add border-radius

We need the task list to follow us even while we're in the System Console.
I checked when you mentioned about it on MM, Due to use of styled components it wasn’t rendering in admin console(after explicitly putting it there), Then Nevy dropped a message that she will fix it, so I dropped further investigation I am not sure if we can do that with styled components but will check and get back to you tomorrow with answers.

could you please share image of this, I am not sure as this is Iframe it might be that’s how wista do it

This is what I see when it opens

@esethna

The sound on the video wasn't working for me

Not sure about 1 as we don’t have any control over video using Wista embedded in Iframe

When are we removing the previous "getting started" stuff in the sidebar so it doesn't conflict with the new task list?

We aren’t removing them for now except for first admin user and for first admin user it will be done once we merge all branches

@Willyfrog please help review to unblock merging

@AshishDhama can you have a look at the following?

Still seeing this: When I clicked on 'Download the desktop and mobile apps', it opened and new tab and when I returned to original tab, the task list was gone. Can it stay open in this case?

When I click on 'Visit the System Console...' task, I saw this the first time. It only happened the first time though it seems

You're already aware of this one, but adding it to the list. When the task list if open in the system console, the header area is highlighted

I think that's it!

Adding the QA deferred label as we will test all the PRs together after merge
cc// @jgilliam17 @Willyfrog

@koox00 can you give this another review asap as we are aiming to merge this as soon as we can

@esethna done. @AshishDhama there are conflicts to be resolved though


Wakapi instance cannot start

Describe the bug
Wakapi doesn't start after update to 2.10.0
logs:
Waiting for database to come up
wait-for-it.sh: waiting 60 seconds for localhost:5432
wait-for-it.sh: localhost:5432 is available after 0 seconds
2023-12-02T18:11:28.092520755Z [ERROR] failed to read config: yaml: unmarshal errors:
  line 19: cannot unmarshal !!str `7_days` into bool
panic: failed to read config: yaml: unmarshal errors:
  line 19: cannot unmarshal !!str `7_days` into bool
goroutine 1 [running]:
github.com/emvi/logbuch.(*StandardFormatter).Pnc(0x2347fa0?, {0x111beaf?, 0x111beaf?}, {0xc000339860?, 0xc000339860?, 0x1?})
	/go/pkg/mod/github.com/emvi/logbuch@v1.2.0/standard_formatter.go:59 +0x5f
github.com/emvi/logbuch.(*Logger).Fatal(0x2347fa0, {0x111beaf, 0x19}, {0xc000339860, 0x1, 0x1})
	/go/pkg/mod/github.com/emvi/logbuch@v1.2.0/logger.go:132 +0x72
github.com/emvi/logbuch.Fatal(...)
	/go/pkg/mod/github.com/emvi/logbuch@v1.2.0/funcs.go:55
github.com/muety/wakapi/config.Load({0x110c765, 0xa}, {0x1108b1b, 0x7})
	/src/config/config.go:412 +0x15e
main.main()
	/src/main.go:120 +0x138

Env var :
WAKAPI_LEADERBOARD_SCOPE=all_time
System information
Please provide information on:

Wakapi version : 2.10.0
Operating system

Docker: 	ghcr.io/muety/wakapi:latest (2.10.0)

Database (SQLite, MySQL, ... ?) : PostegreSQL

Seems like I made a copy & paste mistake in config.default.yml. Will push a fix in a sec! In the meanwhile, seting WAKAPI_LEADERBOARD_ENABLED=true shoud do as a workaround.

thank for your response, I have tested the workaround and it doesn't seem to works

Please try to re-pull the image and start again.

Done and it works, thanks for your reactivity.

I can also confirm that WAKAPI_IMPORT_BATCH_SIZE=0 work :

Can confirm this does not appear to be working for me still with the latest version.
version: '3.8'

services:
  wakapi:
    image: ghcr.io/muety/wakapi:latest
    container_name: wakapi
    restart: always
    ports:
      - "3002:3002"
    environment:
      [...]
      WAKAPI_DB_TYPE: "mysql"
      WAKAPI_ALLOW_SIGNUP: "false"
      WAKAPI_DISABLE_FRONTPAGE: "true"
      WAKAPI_EXPOSE_METRICS: "true"
      WAKAPI_LEADERBOARD_ENABLED: "true"
      WAKAPI_LEADERBOARD_SCOPE: "month"

2023-12-03T08:34:15.888275565Z [ERROR] failed to read config: yaml: unmarshal errors:
  line 19: cannot unmarshal !!str `7_days` into bool
panic: failed to read config: yaml: unmarshal errors:
  line 19: cannot unmarshal !!str `7_days` into bool

@cfouche3005 To disable imports, set WAKAPI_IMPORT_ENABLED=false.
@MSWS Can you double-check that you're really using the latest image version?
This command
docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/muety/wakapi:latest

should return
ghcr.io/muety/wakapi@sha256:516c29ce9b64c6fe3974ea591eb4e60b8b10ebee8c232f389a3c87b9b00ebf27

I am dumb, I have misread the readme, thank for your correction


Hello, how do I configure zsh-autosuggestions to suggest me only one word instead of all suggestions?

Hello, how do I configure zsh-autosuggestions to suggest me only one word instead of all suggestions?

Try using the completion suggestion strategy rather than history. Check the reader for details.


bug: Fix property names

The property names in this note don't match the property names in the list options above it.

Sorry I missed this.
 Alpha coming soon


Cast input to number before isNumber validation for non-strict

PR to solve issue #178
I'd be honest, I'm very new to Open Source contribution, please bear with me and my mistakes.
I just want to contribute to a project that I use.

Well done.

Thanks @OnyekaIjeh 😄

Thank you for Adonis and Indicative.


libevent source outdated

When installing formulas that have libevent as a dependency (tmux for example) you get a 404 since this is outdated. The correct version can be found here.

This issue will be fixed in the new year when Homebrew is merged into Linuxbrew. Thanks for the bug report.


Fix SVG to VGCI open paths

Boris suggested the problem with closed shapes being formed in the  SVG to VGCI process as follows:
...the reason (the process) creates closed edges in the SVG to VGCI converted is that you also need to create two vertices for each SVG open path.
This attempts to implement that suggestion.

Just a note to suggest this change doesn't actually do what I thought it did and instead appears to close all paths.
Will continue to research this.


Raining Gold auto-click stops working after a while (some minutes) of letting the script run

@ric2b What version of the script are you running? I thought I fixed this a day ago.

It's been running great for a few hours now, though, maybe it's gone. I was running the latest version of about 12h ago, when the game restarted I went and grabbed the most recent version again.