There is no fallback created in this document or the .NET 8 template for the Blazor Server example

Description
[Enter feedback here]

I don't understand how to set up a fallback for a new blazor server chat app. see links below. I'm getting multiple endpoints without creating a fallback.  There are lots of docs for fallbacks on older versions of .Net with examples and new examples that seem to create duplicate endpoints for me.

I'm trying to get this to work with dotnet 8.0 on a windows 11 pc to start.
Use ASP.NET Core SignalR with Blazor | Microsoft Learn
I'm using the the second part of the doc "Blazor Server experience"
https://learn.microsoft.com/en-us/aspnet/core/blazor/tutorials/signalr-blazor?view=aspnetcore-6.0&tabs=visual-studio#blazor-server-experience
I don't understand this part:
"Between the endpoints for mapping the Blazor hub and the client-side fallback, add an endpoint for the hub immediately after the line app.MapBlazorHub();:"
C#Copy
app.MapHub("/chathub");
With this code in Programs.cs I get a runtime error:
app.MapBlazorHub();
app.MapHub("/chathub");
app.Run();
Runtime error:
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware: Error: An unhandled exception has occurred while executing the request.
Microsoft.AspNetCore.Routing.Matching.AmbiguousMatchException: The request matched multiple endpoints. Matches:
Blazor web static files
Blazor web static files
   at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ReportAmbiguity(Span1 candidateState)    at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ProcessFinalCandidates(HttpContext httpContext, Span1 candidateState)
   at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.Select(HttpContext httpContext, Span`1 candidateState)
   at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.MatchAsync(HttpContext httpContext)
   at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.TryServeStaticFile(HttpContext context, String contentType, PathString subPath)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
The thread 0x8bc4 has exited with code 0 (0x0).
The thread 0x5aa4 has exited with code 0 (0x0).
The thread '[Thread Destroyed]' (0x277c) has exited with code 0 (0x0).
The thread '[Thread Destroyed]' (0x240c) has exited with code 0 (0x0).
The thread 0x4238 has exited with code 0 (0x0).
The thread 0x38d4 has exited with code 0 (0x0).
The thread 0x3260 has exited with code 0 (0x0).
With this code I get a runtime error as well:
app.MapBlazorHub();
app.MapHub("/chathub");
app.MapFallbackToPage("/");
app.Run();
same for app.MapFallbackToPage("/Home");
this produces a runtime error:
System.InvalidOperationException: Cannot find the fallback endpoint specified by route values: { page: /, area:  }.
   at Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.DynamicPageEndpointMatcherPolicy.ApplyAsync(HttpContext httpContext, CandidateSet candidates)
   at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.SelectEndpointWithPoliciesAsync(HttpContext httpContext, IEndpointSelectorPolicy[] policies, CandidateSet candidateSet)
   at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.g__AwaitMatch|10_1(EndpointRoutingMiddleware middleware, HttpContext httpContext, Task matchTask)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
The thread 0x1c8 has exited with code 0 (0x0).
The thread 0x2118 has exited with code 0 (0x0).
The thread 0x97e8 has exited with code 0 (0x0).
The thread 0x3d2c has exited with code 0 (0x0).
Thanks for your help!
Brian.
<EMAIL_ADDRESS>Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/tutorials/signalr-blazor?view=aspnetcore-6.0&tabs=visual-studio#blazor-server-experience
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/tutorials/signalr-blazor.md
Document ID
85af7a99-672c-0438-dcc2-e8edfaf70c54
Article author
@guardrex

Hello @affinity7software ... You're looking at the .NET 6 version of the doc. Change your doc version selector to .NET 8 to load the updated content.
There's also the updated sample app at ...
https://github.com/dotnet/blazor-samples/tree/main/8.0/BlazorSignalRApp
I'll close as answered, but I can re-open this issue if we need to chat further.

@guardrex , I didn't even see the selector, thanks! and thanks for the link  to the updated sample app!

Hello @affinity7software ... You're looking at the .NET 6 version of the doc. Change your doc version selector to .NET 8 to load the updated content.
There's also the updated sample app at ...
https://github.com/dotnet/blazor-samples/tree/main/8.0/BlazorSignalRApp
I'll close as answered, but I can re-open this issue if we need to chat further.

Hi @guardrex, I followed this link to deploy that on nginx, https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-8.0&tabs=linux-ubuntu and I got errors on the HOME - chat page, I was able to see other pages ok, see secure websockets for the counter from my pc to the app behind an Nginx reverse proxy and AWS ALB passing HTTP request which got upgraded. I have not implemented the secure Nginx part described in the Microsoft link which I will try next but the chat part is failing on in:
BlazorSignalRApp.Components.Pages.Home.OnInitializedAsync() in Home.razor
51         await hubConnection.StartAsync();
I'm happy to share a zip or just the Program.cs as it's the only thing I'm changing.

The product unit provided guidance for Linux at ...
https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/server?view=aspnetcore-8.0#linux-with-nginx
If that doesn't work (and the links mentioned there), open a new issue from the bottom of that article.


Improve article 2103.11909 (arydshln.sty)

Exact location of issue
The last table of 2103.11909
Problem details
In the converted HTML, the tail end of the document is wrongly cast as a multi-part flexbox table.
The support for {threeparttable} is likely at fault, as well as the lack of support for arydshln.sty.
Expected behavior
The table should render well, in its appropriate scope, as should the trailing text.

Will use this issue as a tracking one for arydshln.sty. I stumbled on 2208.00748 today, which can also benefit from that package.
Also, we have it mentioned in #228 , mentioning it to cross-reference.


examples/third-party-resources does not compile

The recently added third-party-resource example does not compile
% go get k8s.io/client-go/examples/third-party-resources
package k8s.io/client-go/pkg/api/unversioned: cannot find package "k8s.io/client-go/pkg/api/unversioned" in any of:
        /home/dfc/go/src/k8s.io/client-go/pkg/api/unversioned (from $GOROOT)
        /home/dfc/src/k8s.io/client-go/pkg/api/unversioned (from $GOPATH)

It's broken by 243d8a9cb66a51ad8676157f79e71033b4014a2a. I'll fix it.

Thanks!
On Thu, 15 Dec 2016, 07:34 Chao Xu<EMAIL_ADDRESS>wrote:

Closed #52 https://github.com/kubernetes/client-go/issues/52 via #53
https://github.com/kubernetes/client-go/pull/53.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/client-go/issues/52#event-894256161, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA0jrGTzUPKvsb-C0CYRJoGDcLx5wks5rIFLwgaJpZM4LMZno
.


Allow for theme only installation

I installed this theme and not paying attention, I realized it also installed a bunch of other extensions that I may or may not have wanted on my system.
It would be wonderful if you could provide a version of the theme that does not include all of the other extensions.
Thanks.

Ok tanks for pointing that out until this issue is review and fixed you can disable the features you don’t want.

Can you possibly tell us what is the most important thing for you to be removed we might decide to remove none, some or all included extension but it could be helpful if you let us know what feature or extension is the most irritating to you ...
[x] alphabetical-sorter
[x] better-comments
[x] bracket-pair-colorizer-2
[x] material-icon-theme

All of the above. I realize that if I looked carefully then I would have seen that a bunch of extensions are included when I installed but I missed it. Suddenly I had all of this extra behavior in my IDE that I wasn't expecting and that I don't want.
I would propose

Pop N Lock Deluxe (all the extensions)
Pop N Lock Lite (none of the extensions)

I have removed [ ] alphabetical-sorter in the latest version but you can disable the extensions if you want to continue using the theme without the other extensions
[x] better-comments
[x] bracket-pair-colorizer-2
[x] material-icon-theme


Extension is not working with the Latest Version of Azure CLI - 2.2.0 or later

When I try to add a new cluster in the Kubernetes tools window, I got the error below:

I'm using Windows and I did not find a way to install a specific version of the Azure CLI, just the latest one.

Hmm, that seems to be a warning coming from the Azure CLI interactive extension, which we are incorrectly treating as an error.  If you are not using the interactive extension to the CLI, could you try uninstalling it using az extension remove please, and see if the problem goes away?  Thanks!

I've removed the interactive extension and now it is working, thanks.

Closing as this was an Azure CLI issue where the error message was misleading, and is now resolved, but this may imply we are being oversensitive to errors-that-are-actually-warnings...


Ghost session

I got a ghost open session after closing all skype-unofficial-client instances. It was listed simply as skype() using /showplaces. Perhaps a Skype web client but, but there's no way for me to know.
Anyway, the repo consisting mainly of binaries and the lack of comments from the devs is too shady. I'm staying away from this project for good. Good luck.

@kehugter Ok, stay away for good. Good Luck.

@kehugter Well, before you get away, take a look at the /src dir, the binary just render that files.
If u wanna build your own binary out of the src its (very simple)[https://github.com/nwjs/nw.js/wiki/how-to-package-and-distribute-your-apps]
If u wanna help, or do constructive criticism reopen the issue.


Enable Typescript 5.0 compatiblity

The tsconfck dependency needs to be updated to at least v2.1.0 in order to meet peer dependency requirements for Typescript 5.0

I submitted a PR


test: test-case for sku package

ping @laurafitzgerald

@laurafitzgerald feel free to merge it the PR looks good to you

@laurafitzgerald is this one ok to merge?

@psturc yes let's merge this one. I will update the automated test as new functionality is added from the sku work. 👍
btw. I did force push the feature branch couple of days ago. Don't know if it will affect the merge.

Actually @psturc can you merge it to the copy on the integreatly fork.


Following page renew

Tasks

[ ] Remove xxx published
[ ] Move circle and tag to the card footer
[ ] Replace xxx 廣播於 xxx_circle： with xxx_circle new 新廣播：
[ ] Remove unfollow button

References

Design v3

@pitb2022 I added a new tasks circle broadcast and design. Please check. 🙏🏻


afterEach hook that runs like in native cypress

How can this be achieved? I am assuming this is not implemented yet, right?
// sample.feature
Feature: Some feature name
Scenario: Sample test 1
Given step 1
When step 2  <-- imagine this step failed for whatever reason
Then step 3 with some validation
//sample.ts step defintions for above
`Given("step 1", function () {
cy.log('step 1 Successful');
});
When("step 2", function () {
cy.log('step 2 FAILED for whatever reason');
});
Then("step 3", function () {
cy.log('step 3 SKIPPED, which expected');
});
After(function () {
cy.log('I want this hook to still run like CYPRESS afterEach() HOOK');
});`

No. If you want the behaviour of Cypress hooks, then use Cypress hooks.

afterEach is running after each feature file instead of only the step definition file that contains it, how can that be achieved though?

I've extended the documentation regarding pairing and explained a common trap that people fall victim to: https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/docs/step-definitions.md
It's probably relevant for you.

It's difficult to follow your example and it looks like the indenting might be off. Can you provide an example in form of a repository?


Implement admindocs

Take a look at the usefulness/functionality of admindocs app.
Reference: https://docs.djangoproject.com/en/4.0/ref/contrib/admin/admindocs/

Overview
To activate the admindocs, you will need to do the following:

Add django.contrib.admindocs to your INSTALLED_APPS.
Add path(admin/doc/, include(django.contrib.admindocs.urls)) to your
urlpatterns. Make sure it’s included before the admin/ entry, so that
requests to /admin/doc/ don’t get handled by the latter entry.
Install the docutils Python module (https://docutils.sourceforge.io/).
Optional: Using the admindocs bookmarklets requires
django.contrib.admindocs.middleware.XViewMiddleware to be installed.

Once those steps are complete, you can start browsing the documentation by going to your admin interface and clicking the “Documentation” link in the upper right of the page.


Update database host for imported user(s)

Fixes #12791

🔴 I tried to move an organization from ded02 to the staging cloud. It failed with
=== Importing visualizations and search tweets ===
2017-09-18 07:59:52 UTC: Importing: #<Sequel::DatabaseConnectionError: PG::Error: could not connect to server: Connection refused
    Is the server running on host \"<IP_ADDRESS>\" and accepting
    TCP/IP connections on port 6432?

Merge on 🍏


HUBViewController.visibleBodyComponentViews not working on initial load

When the HUBViewController first renders my data, calling visibleBodyComponentViews doesn't return an accurate response for the body components that are on-screen.
If I have 3 "shelves" each showing 3 child components, the index paths I get back are:
0, 0.2, 1, 1.2, 2 and 2.2
i.e index paths for the 1st 2 children on each "shelf" are missing.
If I scroll the shelves shelf to the end and then back again, I get the results I expect. This only happens on initial render.

The Hub Framework is being phased out at Spotify, and therefore we will not be maintaining it further.


Event: appland.appmap/project:open

:tada: This issue has been resolved in version 0.18.0 :tada:
The release is available on:

v0.18.0
GitHub release

Your semantic-release bot :package::rocket:


fix: the usage instructions

Checklist

[x] npm install && npm test passes
[ ] tests are included
[ ] documentation is changed or added
[x] commit message follows commit guidelines

Description of change
The descriptions of build and list commands are undefined on the usage instruction. This is happening because an error was made while exporting usage variable.

awesome, thanks for picking this up and thanks for the fix!
landed in 0f5e258


Add missing tooltips to all interface buttons

As the tittle says.

Closed. New issue: https://github.com/baobabsoluciones/cornflow-ui/issues/52


Image Rotation when creating Thumbs

When using the simpleimages.transforms.Scale, my thumbnails were being rotated. I think it might have to do with PIL's method of scaling.
http://stackoverflow.com/questions/4228530/pil-thumbnail-is-rotating-my-image

@vccabral Yeah that sounds right.

[ ] create failing test case
[ ] implement fix


Add warning for aktualizr-lite update

Brief warning added as single line.
QA steps: viewed rendered html.
This commit addresses FFTK-2965
Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[x] Review for wordiness
[x] Match tone and style of page/section.
[ ] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[ ] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Docs for 1bf9499230aff70606dfad4d2d8aa7c973dc839e are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2560/docs/artifacts/html/index.html

Docs for abf0250175e46277821b35402240754e04a2d39d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2562/docs/artifacts/html/index.html


Update CLI version to 45

@ccoenraets and @muenzpraeger I am just updating the CLI version to 45

@zaynelt All signed.


Set argument only after successful dup on CMP APIs

Changes done to set the argument passed only after successful dup.

This seems to have dropped off the radar.  Merged to master.


Need hosted HTML archive

Some consumers of the Technical Framework need to be able to reference specific hosted releases of the TF by URL. They are currently able to accomplish this for the PDF versions of the TF via the archived versions. We need a similar capability for HTML content.
I'd request the following:

Permalinks for version-specific content
Section anchors that continue to function in the archive

see #6 for alternatives. No solution is obvious and supported. Current use of github release versions is the only solution today.


求问如何提高发射功率？

求问如何提高发射功率 -> How to increase transmit power

The following may help: https://github.com/ckcr4lyf/EvilAppleJuice-ESP32/issues/18#issuecomment-1815950744
I've not verified it, but realistically the transmit power would depend more on the model of ESP32 you have and its antenna, I think.

Closing as no further activity.


Error: Plugin scan failed.

Unable to use amplify command.
On each amplify command I am getting the following error.
Scanning for plugins...
Plugin scan failed.
Plugin scan failed.
Error: Plugin scan failed.
at scan
Installed using npm i -g @aws-amplify/cli --unsafe-perm=true
It was working few days ago.

OS: Linux
Node Version. 10.16.3

Kindly help ASAP.

@akmalrasool You'll have to instal the CLI globally - npm install -g @aws-amplify/cli

@kaustavghosh06 Sorry about that but I installed it globally.

@akmalrasool Is there any other stack trace after the following message:
Error: Plugin scan failed.
at scan

@kaustavghosh06 This is the exact error:
Error: Plugin scan failed.
at scan (/home/akmalrasool/.nvm/versions/node/v10.16.3/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11)

This is a duplicate issue as this one:
https://github.com/aws-amplify/amplify-cli/issues/3560
Please use this hack to diagnose ( we will soon update the CLI to print out error log)
/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11, and insert one line of code before it to help us to diagnose?
print.error(JSON.stringify(e));

After you add the line, do a npm run build at /usr/local/lib/node_modules/@aws-amplify/cli/

@UnleashedMind Tried this but no help!

sudo amplify plugin scan still give you the error?
Then use the hack to diagnose, what's the error message that's printed out?

Closing the issue due to lack of response.
Feel free to open a new issue if you still have the problem.


CI/cov. framework, installer, pkgd data, contributing.md

Ok team I think this will be a great foundation. Here is a summary of what exists in this commit.
Cleanup

I deleted useless files and made a .gitignore tuned for both R and Python so we can have both code live happily in this repository. It also disallows uncompressed data files in the data directory.
I modified the existing API to privatize submodules. This enables an un-cluttered tab-completion and all flavors of import syntax like:

import edgePy
edgePy.io.get_dataset_path

import edgePy.io
io.get_dataset_path

from edgePy.io import get_dataset_path

Testing

Travis Continuous Integration has been enabled. The complete test suite uses the nose extension to unittest (Python built-in) as well as doctests in the primary module edgePy.
Code testing coverage is computed with codecov and reported with codecov.io. I set a project goal of 90% coverage but ideally we get to 100% fast and stay there as PRs arrive. For code that is unreachable  in testing you can comment the line defining the scope with   # pragma: no cover

Documentation

We now have a brief instruction for how to contribute. GitHub should provide us integration once this PR is merged as listed here
I've created a docs/ directory for us to place .rst files for later doc building like with readthedocs or Sphinx.
I have enabled doctest and all public functions/methods should have an example when able.
We have cool badges on the README which give off status updates of master!

Installation and Packaging
I created a generic setup.py which should be compatible with the most recent PyPI updates (including Markdown support!) for when we make a release. I included in the package (when we build one!) all .csv, .tsv, and .txt files in the edgePy/data/ directory. Here is one dirty way you can load package data as a binary blob:
import pkgutil
blob = pkgutil.get_data('edgePy', 'data/GSE49712_HTSeq.txt.gz')

Versioning
This project will use semantic versioning. I have started us out as working on v0.1.0 which will eventually be our first minor release. We will not have a stable API until v1.0.0.
Git Branching Model
When in doubt follow this schematic but we should not feel the need to maintain a seperate develop branch.

FYI you can install for development with:
❯ git clone git@github.com:r-bioinformatics/edgePy.git
❯ pip install -e 'edgePy[ci]'

As we grow you should be using virtual environments!

Oh and we support Python3.6+ at the moment.

Hi @apfejes I added a 100 column request to commits in the file CONTRIBUTING.md


fix(product-detail): test flicker lazyload solution

Summary
This is a test to check if the flicker problems in Product Detail Page can be solved using LazyLoadComponent wrapper.
Original Task: https://phabricator.sirclo.com/T42562
Note: No changes were found on local after implementing the Lazy Load wrapper. This solution is meant to be tested on staging because the problem could not be reproduced on local, yet persists in staging & prod environment.

Di framic

sekarang di false in sih
Di nexus
di productdetail

Uda di cek belum kalo pake lazyload bawaan bisa apa engga?


Develop

@ReuDa I just updated the readme of shopping-demo to not contain outdated deployment instructions. Can I merge it with your changes to main?


Add code to check encoder/decoder agreement

It would be useful to have an automated way to check that the encoder and decoder agree on the reconstructed frame.  This could be done by running the decoder inside the encoder after each frame with the coded bitstream.
See issue #31.

Added encoder/decoder checking in 0d34dcfee90f0cb083bcf0b1ff2bbf9568804ef6; not quite the same, but sufficient.


parameters values and u0s

Handle via defaults.
Currently we numerically evaluate all ps andu0s. We should see if ModelingToolkit properly handles specifying those that are functions of other parameters/u0s symbolically, and then use that via the defaults.

Should work with latest versions.


Update register_stakepool.md

Updated the link to the "Establishing connectivity between the nodes" to URL https://docs.cardano.org/getting-started/operating-a-stake-pool/node-connectivity

This has already been fixed on master.
Thanks for the constribution!


pythonPackages.autoflake: init at 1.0

Motivation for this change
autoflake ( https://pypi.python.org/pypi/autoflake ) is a tool that automatically removes unused imports and unused variables from Python code.
Primarily, it is a standalone tool, but we put it under python-modules following the way how the similar package pythonPackages.autopep8 is packaged.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@Mic92 Thank you very much for the suggestions, I agree that this (and perhaps also autopep8) fit better in all-packages.nix. (Ping @bjornfor ?)
Anyways, I've updated the pr and made it a Python3 app.
Hope now it conforms to https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/python.md

Thanks!


how to join

hi, there
I want to know how to contribute netty, i hope join, I can do some basic work first

Of course, you can also do non-code contributions, like improving the documentation or help answer peoples questions.

great.thanks a lot👍


detect-secrets 1.2.0 pre-commit hook errors out with "ModuleNotFoundError: No module named 'requests'"

I think this is a regression; I don't see this error with the 1.1.0 hook and I see that a similar issue (which I can reproduce) was reported in 1.0.0.
If I try to use this hook on my Ubuntu machine...
  - repo: https://github.com/Yelp/detect-secrets
    rev: v1.2.0
    hooks:
      - id: detect-secrets

... then I get this error:
Detect secrets........................................................................................Failed
- hook id: detect-secrets
- exit code: 1

Traceback (most recent call last):
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/bin/detect-secrets-hook", line 5, in <module>
    from detect_secrets.pre_commit_hook import main
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/__init__.py", line 1, in <module>
    from .core.secrets_collection import SecretsCollection  # noqa: F401
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/core/secrets_collection.py", line 12, in <module>
    from . import scan
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/core/scan.py", line 12, in <module>
    from ..filters.allowlist import is_line_allowlisted
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/filters/__init__.py", line 2, in <module>
    from . import gibberish     # noqa: F401
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/filters/gibberish/__init__.py", line 9, in <module>
    from ...core.plugins import Plugin
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/core/plugins/__init__.py", line 1, in <module>
    from . import initialize    # noqa: F401
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/core/plugins/initialize.py", line 9, in <module>
    from .util import get_mapping_from_secret_type_to_class
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/core/plugins/util.py", line 13, in <module>
    from ...plugins.base import BasePlugin
  File "/home/mark/.cache/pre-commit/repovs5glrvx/py_env-python3/lib/python3.9/site-packages/detect_secrets/plugins/base.py", line 19, in <module>
    import requests
ModuleNotFoundError: No module named 'requests'

Not sure what information about my environment would be useful to aid you debugging this but am happy to answer questions!

Hmm. requests is definitely installed in the environment from which I run my Git commands. Originally I was running them with a virualenv enabled, but I tried killing that and just using pyenv without a virtualenv (but again with requests installed), and then finally tried using my system Python without pyenv enabled (again, with requests installed), and still got the same error every time.
I guess it doesn't matter how the Python environment from which I run my Git commands looks anyway, because, based on the traceback above, pre-commit seems to create it's own environment in the ~/.cache/pre-commit directory.
Aha! And it turns out that if I simply delete that folder, everything works again. Interesting.
I've tried to reproduce starting from an empty ~/.cache/pre-commit by e.g. moving between different versions of the hook in my pre-commit-config.yaml, but without success. It seems like the fact that that cache directory was able to get into a broken state indicates a bug somewhere, but without being able to reproduce it, and without having much knowledge of pre-commit's internals, I really have no idea whether to point the finger at detect-secrets, pre-commit itself, or maybe even some other Python-based pre-commit hook I've used other than detect-secrets.
I won't close this myself since perhaps the issue really is in detect-secrets and what I've written above will be enough to make a lightbulb go off in the mind of one of your devs who intimately understands pre-commit... but I will understand if you just decide to close this now that we know it's somehow caused by a bad pre-commit cache but don't have repro instructions.

@MarkAmeryCurative Can you please indicate more information on your configuration. Ubuntu version, pre-commit version etc? Have you tried on a different machine?

Ubuntu 20.04, pre-commit 2.11.1, and haven't tried on a different machine.

Hi @MarkAmeryCurative, thanks for the additional information you've provided here. I haven't been able to reproduce this issue using Ubuntu 20.04, pre-commit 2.11.1, and detect-secrets 1.2.0 so I'm thinking this isn't an issue with detect-secrets itself. I'm going to close this issue for now but please feel free to re-open it if you (or anyone else) finds that this is indeed being caused by detect-secrets.


No space on user page between References and #references at some screen widths

Subject: No space on user page between References and #references at some screen widths
Description:
changed screen width
Results:
there is no space between "references" and the number of references at some screen widths
Backend version: develop-e1d7b61e
Frontend version: develop-e1d7b61e
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0
Page: https://app.couchers.org/user/excinit/
User: itsi (2)

Closing as looks to be fixed!


Null check error on default Wallet ...setting

Steps to produce error

default bull wallet sync done
go to setting,select testnet mode -  on(red)
Go to setting,select testnet mode -off
go to home,select ...wallet setting

Not able to reproduce this. However i get this error on Transaction Detail page for Send Tx where Recieving Bitcoin Address is empty.

Not able to reproduce

Able to reproduce it now.
NOTE: do not leave the settings page between steps 2-3 AND make sure no testnet wallets exist.

@mocodesmo i'll need some help on this. Something to do with walletSelected being null when testnet is toggled.


Add links to corresponding project in docs

Clear and concise description of the problem
Hello,
Each time I want to report an issue, I create a stackblitz, go to nuxtseo.com, install module and create the reproduction.
Then, I want to report the issue but I struggle to find the repo since there is no links in the docs to the corresponding project.
Suggested solution
I think it could be good to add links to each repo in the documentation.
Alternative
No response
Additional context
No response

Agreed, the v2 workflow is not ideal at the moment. Docs will exist in their own repo at some point.

Agreed, the v2 workflow is not ideal at the moment. Docs will exist in their own repo at some point.

Do you want to split docs into each package repo and use unstorage to use it on nuxtseo.com?
Another point, I think that it is important to have, on documentation, a list of links to each repo since there is 2 or 3 for schema-org for example.
If you want help to improve docs, ping me!

Agreed, the v2 workflow is not ideal at the moment. Docs will exist in their own repo at some point.

Do you want to split docs into each package repo and use unstorage to use it on nuxtseo.com?
Another point, I think that it is important to have, on documentation, a list of links to each repo since there is 2 or 3 for schema-org for example.
If you want help to improve docs, ping me!

Once docs are stable I think this is a great idea :+1: I don't think I can offer v1 docs as they only existed within the read me file and I can't be bothered to port them.

I think this should be well solved now within the docs, also each module has a DevTool integrationwhich has a link to create an issue.

Do you want to split docs into each package repo and use unstorage to use it on nuxtseo.com?

This is still something I'd like to explore but still a lot more I want to do with the docs before this


Static files and api proxy

I've seen #61 and https://github.com/chimurai/http-proxy-middleware/blob/master/recipes/servers.md#lite-server
If i run lite-server --baseDir=dist and then curl http://localhost:3000/index.html => works
I then add the follwing bs-config.js
const { createProxyMiddleware } = require('http-proxy-middleware');

const apiProxy = createProxyMiddleware({
  target: 'http://localhost:5111',
  changeOrigin: true, // for vhosted sites
  pathFilter: '/api',
});

module.exports = {
  server: {
    // Start from key `10` in order to NOT overwrite the default 2 middleware provided
    // by `lite-server` or any future ones that might be added.
    // Reference: https://github.com/johnpapa/lite-server/blob/master/lib/config-defaults.js#L16
    middleware: {
      10: apiProxy,
    },
  },
};

If i run lite-server --baseDir=dist and then curl http://localhost:3000/index.html => 404
It looks like the config-default.js middlewares are completely overriden
Is this a documentation bug or am I doing something wrong ?

I finally found the problem !
pathFilter is ignored because the createProxyMiddleware should be called with createProxyMiddleware(filter, options)
const { createProxyMiddleware } = require('http-proxy-middleware');

const apiProxy = createProxyMiddleware('/notifications-api', {
  target: 'http://localhost:5111',
  changeOrigin: true, // for vhosted sites
});

module.exports = {
  server: {
    // Start from key `10` in order to NOT overwrite the default 2 middleware provided
    // by `lite-server` or any future ones that might be added.
    // Reference: https://github.com/johnpapa/lite-server/blob/master/lib/config-defaults.js#L16
    middleware: {
        10 : apiProxy
    },
  },
};
console.log("apiProxy registered")


Add authentication to longhorn

Hi
Would it be possible to add authentication to Longhorn ? A simple password would be enough, no need for a full fledged user management.
This would allow to expose the UI on the net (for remote administration).

Yeah, it's in our plan. We're planning to do it after the next release.
BTW, it's OK to file all the issues in rancher/longhorn. It would be easy to track everything in one place. I will move this topic there.


[bug] Font Weight automatically decreases after using color prop in Header Tag.

Describe the bug
To Reproduce

Hello

Yogesh

System Info:
System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1
    Memory: 108.39 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 3.2.3 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Firefox: 108.0.2
    Safari: 16.2
  npmPackages:
    @babel/runtime: ^7.18.9 => 7.20.7
    @manypkg/cli: ^0.19.1 => 0.19.2
    @react-navigation/bottom-tabs: ^6.5.3 => 6.5.3
    eslint: ^8.21.0 => 8.31.0
    prettier: ^2.7.1 => 2.8.2
    turbo: ^1.4.2 => 1.7.0
    typescript: ^4.7.4 => 4.9.4

Providing Screenshots

for reference:

+1 for some odd font-weight stuff on headers.
Upgrading from 1.0.1 to 1.0.7 my headings received "extra" bolding on web, and I had to set font-weight 400 on them in a style reset.
Not sure what changed.

Yea something happened on fontWeight in patch 2 or 3. Should be fixed very soon.

Have a fix almost ready. Leave the compiler off for now on native.

1.0.9 Should fix, re-open if not.

I can confirm, 1.0.9 fixed it for both native and web.


Add general factory for credential verifier instances

This is a mechanism to create and return the appropriate credential verifier based upon the credentials passed in.
The effect is that from the credentials alone, the verifier can be created an be initialised.
This permits us to have a database with many different types of credentials stored, supporting them all.

Overall the ideal API is:
public class LoginLogoutManager<TEntered,TStored>
{
  public LoginResult AttemptLogin(TEntered credentials);

  public void Logout();

  protected void HandleLoginSuccess(TEntered entered,TStored stored);

  protected void HandleLoginFailure(TEntered entered);

  protected void HandleLogout();

  TStored Create(TEntered source);
}

In the above, TStored is:
public interface IStoredCredentials<TAccountInfo>
{
  string SerializedCredentials { get; }

  TAccountInfo AccountInfo { get; }
}

The process flow is roughly:

Get the stored credentials from the repository using the entered credentials.

This is closed as the whole library has been pretty much completely rewritten from scratch since this issue was raised.
However, all of the intentions of this ticket are now fulfilled.


Listener ECDS: Adding config provider manager implemantion for listener filter

Problem description:
Listener ECDS: Adding FilterConfigProviderManagerImpl class implemantion for listener filter.
This is the 3rd PR to support listener filter ECDS as in issue: https://github.com/envoyproxy/envoy/issues/20049. It includes:

The class definition of ListenerFilterConfigProviderManagerImpl.
Moving getMessage() method to the base class to avoid duplicated code.
Unit test cases for ListenerFilterConfigProviderManagerImpl.

Build:
passed
Testing:
passed
Release Notes:
N/A
Issues: ecds: add support for listener filters https://github.com/envoyproxy/envoy/issues/20049
Signed-off-by: Yanjun Xiang<EMAIL_ADDRESS>
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign @adisuissa @kyessenov @yanavlasov

For something like this, an xDS integration test would be useful. There is one for HTTP, so it can be copied and adapted fairly easy.

For something like this, an xDS integration test would be useful. There is one for HTTP, so it can be copied and adapted fairly easy.

Yes, that's planned.
This PR just added a ListenerFilterConfigManagerImpl definition. It's not used any where.   In the planned next PR, I will be creating an object of it in class ListenerManagerImpl, and using it to create listener filter factories, and build listener filter chain.  In that PR, I will be extending the current test/integration/extension_discovery_integration_test.cc to test listener ECDS functionality end-to-end.

/retest

/assign @htuch

Generally looks good, thanks @yanjunxiang-google. +1 on xDS integration test as soon as we land enough of the PRs. I'll take another pass once @kyessenov and @adisuissa have LGTMed for senior maintainer review.

This looks reasonable to me. At some point we should make factories be more uniform to avoid a lot of redundancy but it's easy to compare now that it's all in one file.

Generally looks good, thanks @yanjunxiang-google. +1 on xDS integration test as soon as we land enough of the PRs. I'll take another pass once @kyessenov and @adisuissa have LGTMed for senior maintainer review.

Thanks!
Yes, will add the xDS integration test in the next PR when working on the items of  #4, #5, #6 of issue: https://github.com/envoyproxy/envoy/issues/20049

@adisuissa @kyessenov  PTAL

Thanks, overall LGTM. @soulxu can you take another look.

overall LGTM also! except for the listener filter matcher https://github.com/envoyproxy/envoy/pull/20560#discussion_r855829729

@htuch @kyessenov  PTAL

LGTM. I think @kyessenov can do final pass/merge (now as a maintainer). Generally I'd also ask for a non-Googler, but this is mostly an internal change and consistent with previous work on ECDS, so won't insist on that unless someone feels strongly in favor.

Matt volunteered to do a final pass, once @kyessenov LGTM's this PR.

/assign @mattklein123  Thanks for help reviewing!

For reviewers:
This PR added the building blocks to support listener filter ECDS.  But it is not hooked into listener manager code yet (e.g. https://github.com/envoyproxy/envoy/blob/aa19a78404e285d5cd219c564a68e67c59484075/source/server/listener_manager_impl.cc#L112), which will be done in the coming PR.


Use less jQuery, alipinejs or vanillajs instead

[x] Convert toggle-related.js to vanillajs.
[x] On submission detail convert toggle-actions-panel.js to alpinejs.
[x] Convert submission-text-cleanup.js to vanillajs.
[x] Replace dropdown.js with alpinejs.
[x] Convert all-submissions-table.js to vanillajs.
[x] Convert application-form-links-new-window.js to vanillajs.
[x] Made PAF and SOW views and download buttons to look the same.

all looked good on test from what I could see!


Add Polygonal Boundaries at EDDH

This PR adds polygonal boundaries to Hamburg, it improves the SID's and adds a few more airlines for realism. When I first updated EDDH, I was not able to find a reliable source of coordinates for the fixes. However, while working on EDDF, I found one! The changes to the SID's are mainly visual, as you can see in the pictures:
Before:

After:

@Fechulo What is that "reliable source" for navdata? Just curious

@erikquinn I found these files, used for the ATC clients for VATSIM. It isn't exactly reliable as it isn't real life data, but the information is extremely accurate.

Oh okay, cool. I'm always looking for more data sources. Usually I get everything from SkyVector, they seem to be pretty spot on, but even they don't have everything...

It's not easy to find...


Medical device template developed by GE Healthcare

Work by Matthew Clapham, Valery Berestetsky, Dan Birtwhistle, and Jonathan Schaaf (all at GE Healthcare).

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

Content under review for inclusion with TMT

@jpschaaf  For testing purpose , this needs to be merged to dev first. Can you raise a PR with required changed to be merged to dev ? We will test it out and then merge to master , if it all passes.

@jpschaaf For testing purpose , this needs to be merged to dev first. Can you raise a PR with required changed to be merged to dev ? We will test it out and then merge to master , if it all passes.

It might be a few days before I get to it, but I will do as requested.

@jpschaaf I have merged the template to Dev branch and we are currently in process of verifying it. As and when you have time , please check to see if it looks good on the dev branch.
https://github.com/Microsoft/threat-modeling-templates/pull/24


Add date format assert

This assert checks if a date is valid in a given format.

@franciscocardoso what about using the Date assert with { format: 'YYYY-MM-DD' } as an option instead?

I prefer this approach but don't have strong feelings about it.
Do you want me to update to your suggestion?
/cc @ruimarinho

Let me ping @nunofgs @fixe to hear their thoughts too.

Deprecated by https://github.com/seegno/validator.js-asserts/pull/95.


Snap Events: scrollsnapchange and scrollsnapchanging

New events were released for scroll snaps. Would be nice to have this in caniuse:
https://groups.google.com/a/chromium.org/g/blink-dev/c/-naLTco_PEo/m/GwL4OA6dAQAJ

this could remain it's own issue, but is also part of #6335 🤓

these 2 APIs are shipping in Chrome 127!


Stack Overflow when action has recursive url parameter

Swashbuckle.Swagger.Filters.HandleFromUriParams.ExtractAndAddQueryParams goes into an infinite recursive loop when you define an action with a url parameter that has circular references in it. IIS dies instantly with Stack Overflow Exception when Swashbuckle tries to generate the schema.
The problem only occurs when you explicitly set the model to be an url parameter with [FromUri] attribute. It can detect circular references correctly in body parameters.
Here is a small test case:
public class CategoryModel
{
    public int Id { get; set; }
    public CategoryModel Parent { get; set; }
}

public class CategoryController : ApiController
{
    [HttpGet]
    [Route("api/category/level")]
    public int GetLevel([FromUri]CategoryModel model)
    {
        return 1;
    }
}

And the stack trace:
...
Swashbuckle.Core.dll!Swashbuckle.Swagger.Filters.HandleFromUriParams.ExtractAndAddQueryParams(Swashbuckle.Swagger.Schema sourceSchema, string sourceQualifier, bool sourceRequired, Swashbuckle.Swagger.SchemaRegistry schemaRegistry, System.Collections.Generic.IList<Swashbuckle.Swagger.Parameter> operationParams) Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.Filters.HandleFromUriParams.ExtractAndAddQueryParams(Swashbuckle.Swagger.Schema sourceSchema, string sourceQualifier, bool sourceRequired, Swashbuckle.Swagger.SchemaRegistry schemaRegistry, System.Collections.Generic.IList<Swashbuckle.Swagger.Parameter> operationParams) Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.Filters.HandleFromUriParams.ExtractAndAddQueryParams(Swashbuckle.Swagger.Schema sourceSchema, string sourceQualifier, bool sourceRequired, Swashbuckle.Swagger.SchemaRegistry schemaRegistry, System.Collections.Generic.IList<Swashbuckle.Swagger.Parameter> operationParams) Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.Filters.HandleFromUriParams.ExtractAndAddQueryParams(Swashbuckle.Swagger.Schema sourceSchema, string sourceQualifier, bool sourceRequired, Swashbuckle.Swagger.SchemaRegistry schemaRegistry, System.Collections.Generic.IList<Swashbuckle.Swagger.Parameter> operationParams) Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.Filters.HandleFromUriParams.HandleFromUriObjectParams(Swashbuckle.Swagger.Operation operation, Swashbuckle.Swagger.SchemaRegistry schemaRegistry, System.Web.Http.Description.ApiDescription apiDescription)   Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.Filters.HandleFromUriParams.Apply(Swashbuckle.Swagger.Operation operation, Swashbuckle.Swagger.SchemaRegistry schemaRegistry, System.Web.Http.Description.ApiDescription apiDescription)   Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.SwaggerGenerator.CreateOperation(System.Web.Http.Description.ApiDescription apiDescription, Swashbuckle.Swagger.SchemaRegistry schemaRegistry) Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.SwaggerGenerator.CreatePathItem(System.Collections.Generic.IEnumerable<System.Web.Http.Description.ApiDescription> apiDescriptions, Swashbuckle.Swagger.SchemaRegistry schemaRegistry) Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.SwaggerGenerator.GetSwagger.AnonymousMethod__4(System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription> group) Unknown
System.Core.dll!System.Linq.Enumerable.ToDictionary<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>,string,Swashbuckle.Swagger.PathItem>(System.Collections.Generic.IEnumerable<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>> source, System.Func<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>,string> keySelector, System.Func<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>,Swashbuckle.Swagger.PathItem> elementSelector, System.Collections.Generic.IEqualityComparer<string> comparer) Unknown
System.Core.dll!System.Linq.Enumerable.ToDictionary<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>,string,Swashbuckle.Swagger.PathItem>(System.Collections.Generic.IEnumerable<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>> source, System.Func<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>,string> keySelector, System.Func<System.Linq.IGrouping<string,System.Web.Http.Description.ApiDescription>,Swashbuckle.Swagger.PathItem> elementSelector)    Unknown
Swashbuckle.Core.dll!Swashbuckle.Swagger.SwaggerGenerator.GetSwagger(string rootUrl, string apiVersion) Unknown

Good catch! Although, a self referencing type doesn't seem like a great idea for a FromUri binding because it essentially represents an infinite set of individual query params.
That said though, SB should handle it correctly. Do you have any thoughts on the correct behavior here - it's a little different to the body parameter scenario because in the case the complex type needs to be flattened into a finite set of individual parameter descriptions.
The only thing I can think of is to only support an arbitrary nesting level when flattening out an object graph. This would produce unexpected behavior if the level of nesting in your FromUri object happens to exceed the chosen arbitrary value.
Would be interested to get your thoughts?

I can't really think of a scenario where such url parameters would be userful. In fact I accidentally found this bug thanks to a controller action that was created by our team to temporarly test a custom json model binder. I just banged my head into the desk until I figured out that it was this strange test model that caused it.
In my opinion you should do the same as you did with recursive models in the request body. Just detect the recursion and switch the self referencing parameter to string or remove it completely.

Because this is a serious edge-case I'm going to punt on it. In the next version of AspNet (vNext), expanding out these params will be fully handled in the framework and so won't need to be done by SB. As a result, this should be resolved in the next major version of SB because it targets vNext.

Hi all,
Unfortunately I have this problem in my current project :( My project is running on .NET framework 4.5.2, and using the latest Swashbackle 5. But according to the discussion above it seems this problem is not resolved. Have anyone any idea how to approach it or resolve it?

This happened to me when one of my actions was taking System.Web.Http.OData.Query.ODataQueryOption as a parameter and I was setting readonly = null on all properties. My workaround was to perform the readonly = null logic in an IDocumentFilter instead of an IOperationFilter. This allowed the buggy HandleFromUriParams OperationFilter to be bypassed because it did its work when readonly was set to null.

@henkosch I just ran into this issue too although the recursion was due to using Entity Framework models in the parameters and as return types. Therefore, if you want to use any of those models in your parameters, Swagger will break. To me, this seems like a somewhat common use case as EF is used quite frequently.


Mirror throws NullReferenceException on connect causing client to disconnect

Describe the bug
Object that is disabled throws NullReferenceException when client connects
relevant log message

NetworkBehaviours array is null on object name
Typically this can happen when a networked object is a child of a non-networked parent that's disabled, preventing Awake on the networked object from being invoked, where the NetworkBehaviours array is initialized.
UnityEngine.Debug:LogError (object,UnityEngine.Object)
Mirror.NetworkIdentity:ValidateComponents () (at Assets/Plugins/Mirror/Core/NetworkIdentity.cs:313)
Mirror.NetworkIdentity:DeserializeClient (Mirror.NetworkReader,bool) (at Assets/Plugins/Mirror/Core/NetworkIdentity.cs:1024)
Mirror.NetworkClient:ApplySpawnPayload (Mirror.NetworkIdentity,Mirror.SpawnMessage) (at Assets/Plugins/Mirror/Core/NetworkClient.cs:1041)
Mirror.NetworkClient:OnSpawn (Mirror.SpawnMessage) (at Assets/Plugins/Mirror/Core/NetworkClient.cs:1308)

Expected behavior
Mirror should not throw NullReferenceException when client connects
Suggested fix
Mirror should call InitializeNetworkBehaviours if it isn't called when object is spawning. This can be made save using a flag to say if InitializeNetworkBehaviours has already been called once, so that it isn't invoked multiple times.
Version

Mirror version: v78.3.0

the DeserializeClient code path is still the same, but it is possible it was fixed somewhere else

ok I'm going to close this then. Reopen or make a new one if you find the error comes back.


ERROR: could not create engine from ONNX. Aborted (core dumped)

when i run the command "./visualizer " in the terminal, and then select an ".bin" file  ,throw the error:
$ ./visualizer
OpenGL Context Version 4.5 core profile
GLEW initialized.
OpenGL context version: 4.5
OpenGL vendor string  : NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2
Extracting surfel maps partially.
Performing frame-to-model matching.
Setting verbosity to: false
Trying to open model
Trying to deserialize previously stored: /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.trt
Successfully found TensorRT engine file /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.trt
Successfully created inference runtime
No DLA selected.
Successfully allocated 426755792 for model.
Successfully read 426755792 to modelmem.
Could not deserialize TensorRT engine.
Generating from sratch... This may take a while...
Trying to generate trt engine from : /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.onnx
Platform DOESN'T HAVE fp16 support.
No DLA selected.
----------------------------------------------------------------
Input filename:   /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.onnx
ONNX IR version:  0.0.4
Opset version:    9
Producer name:    pytorch
Producer version: 1.1
Domain:
Model version:    0
Doc string:
----------------------------------------------------------------
WARNING: ONNX model has a newer ir_version (0.0.4) than this parser was built against (0.0.3).
----- Parsing of ONNX model /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.onnx is Done ----
Success picking up ONNX model
Failure creating engine from ONNX model
Current trial size is<PHONE_NUMBER>
Failure creating engine from ONNX model
Current trial size is<PHONE_NUMBER>
Failure creating engine from ONNX model
Current trial size is<PHONE_NUMBER>
Failure creating engine from ONNX model
Current trial size is<PHONE_NUMBER>
Failure creating engine from ONNX model
Current trial size is 536870912
Failure creating engine from ONNX model
Current trial size is 268435456
Failure creating engine from ONNX model
Current trial size is 134217728
Failure creating engine from ONNX model
Current trial size is 67108864
Failure creating engine from ONNX model
Current trial size is 33554432
Failure creating engine from ONNX model
Current trial size is 16777216
Failure creating engine from ONNX model
Current trial size is 8388608
Failure creating engine from ONNX model
Current trial size is 4194304
Failure creating engine from ONNX model
Current trial size is 2097152
Failure creating engine from ONNX model
Current trial size is 1048576
terminate called after throwing an instance of 'std::runtime_error'
 what():  ERROR: could not create engine from ONNX.
Aborted (core dumped)

Waiting for your reply! thanks!

Hey @shaoquanfeng, this seems to be a problem of rangenet_lib. Have you already tried the example given there?

thanks for your reply！ yes， i have successful tested the example in the rangenet lib！------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年9月10日(星期四) 晚上11:49
收件人<EMAIL_ADDRESS>抄送: "Shq feng"<602414626<EMAIL_ADDRESS>主题: Re: [PRBonn/semantic_suma] ERROR: could not create engine from ONNX. Aborted (core dumped) (#31)

It seems still trying to build the tensorrt model, which should be already generated if you passed the demo in rangenet_lib.
Did you specify the path of the model in the configuration file?

thanks! Today, I rebuild the project, and then pass the demo in rangenet_lib, throw the same bug with #30.
$ ./visualizer
OpenGL Context Version 4.5 core profile
GLEW initialized.
OpenGL context version: 4.5
OpenGL vendor string  : NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2
Extracting surfel maps partially.
Performing frame-to-model matching.
Setting verbosity to: false
Trying to open model
Trying to deserialize previously stored: /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.trt
Successfully found TensorRT engine file /media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53/model.trt
Successfully created inference runtime
No DLA selected.
Successfully allocated 426755792 for model.
Successfully read 426755792 to modelmem.
Created engine!
Successfully deserialized Engine from trt file
Binding: 0, type: 0
[Dim 5][Dim 64][Dim 2048]
Binding: 1, type: 0
[Dim 20][Dim 64][Dim 2048]
Successfully create binding buffer
calibration filename: /home/raymond/data/kitti-odometry/kitti/dataset/sequences/07/calib.txt...loaded.
ground truth filename: /home/raymond/data/kitti-odometry/kitti/dataset/poses/07.txt
1101 poses read.
Performing frame-to-model matching.

It seems that yesterday's problem has not been solved ! this is my test data folder tree:
└── kitti-odometry
└── kitti
└── dataset
├── poses
└── 07.txt
└── sequences
└── 07
└── velodyne
└── .bin
this is my model path:
<param name="model_path" type="string">/media/raymond/17354422509/suma++_ws/src/semantic_suma/config/darknet53</param>

Hey @shqfeng,
Is there any update on the issue?

Since there is no update for this issue, I'm going to close it.
If there is any problem, please feel free to ask me to reopen it.


No published analyzer available for language version 2.11.0

same issue

same here

Same here:
Your current analyzer version may not fully support your current SDK version.
Please try upgrading to the latest analyzer by running flutter packages upgrade.
Analyzer language version: 2.9.0
SDK language version: 2.11.0
If you are getting this message and have the latest analyzer please file
an issue at https://github.com/dart-lang/sdk/issues/new with the title
"No published analyzer available for language version 2.11.0".
Please search the issue tracker first and thumbs up and/or subscribe to
existing issues if present to avoid duplicates.
[INFO] Generating SDK summary...
[SEVERE] functional_data_generator:functional_data on test/mocks/app_settings_store_mock.dart:
Bad state: Unexpected diagnostics:
/Users/sandeep/flutterdevelopment/flutter/bin/cache/pkg/sky_engine/lib/ui/channel_buffers.dart:152:17 - This requires the 'non-nullable' language feature to be enabled.
/Users/sandeep/flutterdevelopment/flutter/bin/cache/pkg/sky_engine/lib/ui/channel_buffers.dart:119:41 - This requires the 'non-nullable' language feature to be enabled.

Any update? facing same issue

One has since been published.


Unexpected Safe Links Functionality for entire tenant

A customer could be taken off guard if they never had an MDO defender license in the past and then added it later.  We had a customer who never had a defender license in the tenant and then added it for a small group of people (not for entire tenant).  They had not applied any custom policies. All of sudden everyone in the entire tenant got safe links and they had no idea why.  Also in order to be license compliant they would have to exclude everyone from the built in policy that they did not buy the license for.  I think this needs to be in one of those blue or pink boxes as an  important change or warning.  Before this change no one in the tenant got safe links or attachments unless you set up a policy..thats a big change.

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

ID: 4f6f1cf3-a121-3c6e-9380-79440f4c6671
Version Independent ID: 9b1bc5d1-8ecc-d0f9-092e-325c6acff4fe
Content: Preset security policies - Office 365
Content Source: microsoft-365/security/office-365-security/preset-security-policies.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@chrisda Please help us in resolving this issue. Thanks

Checking.

@lmarianko, although the topic already contains the following text:

Until you assign the policies to users, the Standard and Strict preset security policies are assigned to no one. In contrast, the Built-in protection preset security policy is assigned to all recipients by default, but you can configure exceptions.

I'll admit that doesn't exactly stand out., so I added the following text nearby:

[!IMPORTANT]
Unless you configure exceptions to Built-in protection, everyone in the organization will receive Safe Links and Safe Attachments protection.

OK?

That's part of it but I think something should be mentioned about licenses specifically.  Does the built in protection now give you safe links and safe attachments even if you don't have a defender license?  Is it now part of EOP basic protection?  This is where the confusion comes in.
Do you have to add exceptions for those users that don't have a defender license or you won't be in license compliance?
Thanks.
Leslie
Leslie Marianko
Sr Cloud Solutions Architect
State and Local Government
Modern Work
Office: +1<PHONE_NUMBER>
Mobile: +1<PHONE_NUMBER>
<EMAIL_ADDRESS>[Microsoft]
From: Chris Davis @.>
Sent: Wednesday, February 1, 2023 6:06 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Leslie Marianko @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Unexpected Safe Links Functionality for entire tenant (Issue #10818)
@lmariankohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flmarianko&data=05|01|Leslie.Marianko%40microsoft.com|21920c0564664cd8580408db04a8d5d5|72f988bf86f141af91ab2d7cd011db47|1|0|638108895413841883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=s9luvjv0%2BRh2XSXx4r7kY5VsCogYPv6QaA3qVdk9BZU%3D&reserved=0, although the topic already contains the following text:
Until you assign the policies to users, the Standard and Strict preset security policies are assigned to no one. In contrast, the Built-in protection preset security policy is assigned to all recipients by default, but you can configure exceptions.
I'll admit that doesn't exactly stand out., so I added the following text nearby:
[!IMPORTANT]
Unless you configure exceptions to Built-in protection, everyone in the organization will receive Safe Links and Safe Attachments protection.
OK?

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F10818%23issuecomment-1412870183&data=05|01|Leslie.Marianko%40microsoft.com|21920c0564664cd8580408db04a8d5d5|72f988bf86f141af91ab2d7cd011db47|1|0|638108895413841883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=vwcbhHG91kY3NCux8FVJApXdPkP8KticM2%2FjMBdcwkU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMOBZKSYGVAJSAJMD24KOYLWVLT4FANCNFSM6AAAAAAUJEFAFY&data=05|01|Leslie.Marianko%40microsoft.com|21920c0564664cd8580408db04a8d5d5|72f988bf86f141af91ab2d7cd011db47|1|0|638108895413841883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Isl1vo3kahwjd0LEeYcPw3F4mcNGVQ5fWd6qOJvIw5A%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

So are we saying its not out of license compliance if everyone has built in protection and does not have a defender license?
Leslie Marianko
Sr Cloud Solutions Architect
State and Local Government
Modern Work
Office: +1<PHONE_NUMBER>
Mobile: +1<PHONE_NUMBER>
<EMAIL_ADDRESS>[Microsoft]
From: Chris Davis @.>
Sent: Thursday, February 2, 2023 1:30 PM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Leslie Marianko @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Unexpected Safe Links Functionality for entire tenant (Issue #10818)
@lmariankohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flmarianko&data=05|01|Leslie.Marianko%40microsoft.com|75ff6b24c41a408a7ce208db054b8e2c|72f988bf86f141af91ab2d7cd011db47|1|0|638109594290847699|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=NGYuDYWKDahOsOrkOq%2Fg%2Fjd%2B3%2BpPjy8eIZTiUQtzpDE%3D&reserved=0, it would appear so.
The new note I added is accurate in that it says all recipeints will get Safe Links and Safe Attachments via Built-in Protection unless you configure exceptions.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F10818%23issuecomment-1414185291&data=05|01|Leslie.Marianko%40microsoft.com|75ff6b24c41a408a7ce208db054b8e2c|72f988bf86f141af91ab2d7cd011db47|1|0|638109594290847699|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2FnwhDWluX7Co4qX9IYEIoZVSrgg%2FKrQ5w4a0r4QBbi0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMOBZKVKIPSJ6YZFO5FM5BTWVP4MFANCNFSM6AAAAAAUJEFAFY&data=05|01|Leslie.Marianko%40microsoft.com|75ff6b24c41a408a7ce208db054b8e2c|72f988bf86f141af91ab2d7cd011db47|1|0|638109594290847699|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=3d4gxK3KEgxdYQsAkJGLyaOXSJJAw0E8QUDSgXLykS4%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Switching to email.


emotes issues

When i write a emote in my message they disappear after few secondes but i see them if i try to delete my message for example. Or if i write a message with a emote alone, then i write another message, the emote will be "behind" the new message

This sounds like the same issues we (and evidently at least a few others) are having. I'm mostly curious whether it's working for anyone at all right now? Are we doing something wrong? Have downloaded and installed the latest release from this project.

emotes vanishing is a known issue atm. everyone supposedly has it happening. discord re-renders the entire chat area (probably more) everytime the window loses focus. it also recreates entire message groups when their message count changes. why BD doesn't just insert the emotes again when that happens, i can't tell you. the hooks to do so are in place. as a non-developer there's nothing you can do really.

This should now be fixed and be even better than before =)


Multiline text

Hello,
I want to ask about long text/byte array submissions. How to correctly encode it, so it can be sent via your library.
I intend to create a bot that invokes some specific commands defined in the YAML config file. The exec output is a byte array and I'm unable to predict its content (which means not only whitespace, and unprintable signs but some fancy/exotic UTF signs can occur).
Can you help me?

Do you want send bytes data to users in telegram?

Hello, I want to send a text (the output of the command) which is returned as a byte array (docs)

This example will sent a result of command on any message to the bot
package main

import (
	"bytes"
	"context"
	"log"
	"os"
	"os/exec"
	"os/signal"

	"github.com/go-telegram/bot"
	"github.com/go-telegram/bot/models"
)

func main() {
	opts := []bot.Option{
		bot.WithDefaultHandler(handler),
	}

	b := bot.New(os.Getenv("EXAMPLE_TELEGRAM_BOT_TOKEN"), opts...)

	ctx, cancel := signal.NotifyContext(context.Background(), os.Interrupt)
	defer cancel()

	b.Start(ctx)
}

func handler(ctx context.Context, b *bot.Bot, update *models.Update) {
	buf := bytes.NewBuffer(nil)

	cmd := exec.Command("pwd")
	cmd.Stdout = buf

	err := cmd.Run()
	if err != nil {
		log.Printf("error run command, %v", err)
		return
	}

	b.SendMessage(ctx, &bot.SendMessageParams{
		ChatID: update.Message.Chat.ID,
		Text:   buf.String(),
	})
}

Thank you!!


new version not working

loadPayments  function giving 400 bad response, even another app I have used 0.0.4 its working, but 0.2.0 is not working.
plase sugest any solution.

the required data was passing null, solved.


azure-cosmosdb-table 1.0.3 has requirement azure-storage-common<1.2.0,>=1.1.0, but you'll have azure-storage-common 1.2.0rc1 which is incompatible.

azure-cosmosdb-table 1.0.3 has requirement azure-storage-common<1.2.0,>=1.1.0, but you'll have azure-storage-common 1.2.0rc1 which is incompatible.

azure-cosmosdb-table 1.0.3 has requirement azure-storage-common<1.2.0,>=1.1.0, but you have azure-storage-common 1.3.0.

FYI fix is merged, waiting for release:
https://github.com/Azure/azure-cosmosdb-python/pull/29

V 1.0.5 has been released and has this change.


[WIP] Allow required UUID type in scaffold.

Allow scaffolding to create a required UUID.

I just realized the existing UUID field was mandatory by default (unless I'm mistaken) so adding optionality here will require going back and making all existing usages of it into the uuid! version.

@BWStearns your current fix looks OK, what do you mean?

Ah I misread the TYPEMAP bit in the gen model here. Yeah I guess it should be fine.


Increase window resizable area on Windows #1413

Pull request type

Please check the type of change your PR introduces:

[X] Bugfix
[ ] New feature or enhancement
[ ] UI change (please include screenshot!)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Internationalization and localization
[ ] Other (please describe):

What is the current behavior?

Issue Number: #1413
What is the new behavior?
Increase margin around the window content.
Other information

Quality check
Before creating this PR:

[X] Did you follow the code style guideline as described in CONTRIBUTING.md
[X] Did you build the app and test your changes?
[ ] Did you check for accessibility? On Windows, you can use Accessibility Insights for this.
[ ] Did you verify that the change work in Release build configuration
[ ] Did you verify that all unit tests pass
[ ] If necessary and if possible, did you verify your changes on:

[X] Windows
[ ] macOS
[ ] Linux

issue #1228 may reoccur.


Adding/Removing Subscribers - Goroutine Leak

Hello,
We are attempting to write a frontend microservice that creates a global instance of a pub/sub go-microservice on v2.9.1 (using the kafka plugin), and then for every request it receives from the client:

spins up a subscriber unique to the request by subscribing to a topic name that has the request UUID baked in
passes the request onto a request topic that goes out to another ms, which in turn processes the request and returns the data back to the unique topic described in 1)
in the callback for the subscriber, processes the response and then unsubscribes from the topic
repeat for each request

The idea is that each unique request to the microservice will result in a new ephemeral subscriber that gets spun up, listens for a response on its unique topic, then unsubscribes once it receives its response.
Things are working at first glance, i.e. we are getting responses back to the client fine and it's handling concurrent requests fine, but peeking at our goroutine count in the microservice using runtime.NumGoroutine(), we notice that the goroutine count slightly increases with each request, meaning we are not correctly/fully spinning down our subscriber each time (I think). We are admittedly new to both pub/sub architecture as well as this package so I was hoping to get some help on what we might be doing wrong.
Here is some slimmed code for our pubsub service which is created once globally at app startup(relevant to this package is the usage of NewService/kafka.NewBroker):
func NewPubSub(config PubSubConfig, schemas map[string]*goavro.Codec) (*PubSub, error) {
	brkr := kafka.NewBroker(//address)
	brkr.Connect()

	pubSub := micro.NewService(
		micro.Name(/servicename),
		micro.RegisterTTL(//heartbeatval),
		micro.RegisterInterval(//heartbeatval),
		micro.Broker(brkr),
	)

	pubSub.Init()

	pubSubService := &PubSub{
		Service: pubSub,
		Schemas: //schemas,
	}

	return pubSubService, nil
}

and here is our Subscriber function for the pubsub service, it returns a subscriber object that we then use later to call Unsubscribe():
func (ps *PubSub) Subscribe(topic string, schemaName string, callbackFunction func(msg map[string]interface{}, args ...interface{}) error, callbackArgs ...interface{}) map[string]*broker.Subscriber {
	codec, found := //get avro codec

	subxtion, err := ps.Service.Options().Broker.Subscribe(
		topic,
		func(p broker.Event) error {
			decodedBody := decode(codec, p.Message().Body)

			err := callbackFunction(decodedBody, callbackArgs...)
			if err != nil {
				return err
			}

			_ = p.Ack()
			return nil
		},
		broker.DisableAutoAck(),
	)
	return subxtion
}

The following is a slimmed version of our callback function (it sends the response to a channel that our request thread waits for before unsubscribing, seen below):
func Callback(decodedMsg map[string]interface{}, args ...interface{}) error {
	args[0].(chan string) <- decodedMsg //send to responseChannel
	return nil
}

The flow is that we first create an instance pubSub of the PubSub service (described at the top) in the main thread like so:
	pubSub, _ = pubsub.NewPubSub(pubsub.PubSubConfig{
		ServiceName: "cmdb-http-interface",
		Heartbeat:   time.Second * 15},
		schemas.GetAllSchemas())

	go logrus.Fatal(http.ListenAndServe(":3001", r))

	fmt.Println("before start")
	if err := pubSub.Service.Run(); err != nil {
		fmt.Printf("Error running PubSub microservice: %v\n", err)
	}

and then for every request we run the following:
	sub := pubSub.Subscribe(topic, schema, Callback, responseChannel, requestUUID) // last two args are sent to callback func as variadic args

        pubSub.Publish(//topic, //schema, //request)

	select {
	case fetchedResources := <-responseChannel:
		w.Write([]byte(fetchedResources))
		sub.Unsubscribe() // unsubscribe to the unique topic
	}

	return nil

so while the pubsub service remains persistent, each subscriber should be starting/stopping per request.
We basically are at a loss for how we should be subbing/unsubbing per request and this is the best we've gotten so far. We're aware this might be impossible to diagnose without full context but I thought we'd give it a shot to ask. Any tips on this per-request subscription behavior in general would be greatly appreciated.
Thanks!

Closing - posted in microgo-plugins here.


test example in CI (new)

#552

@giovp @ArinaDanilina what's the state here?

super cool @selmanozleyen , just fyi I think it's fine to just run for now notebooks in the example folder. Looking forward to updates!

thanks @giovp, current setup should be a functional example. Some notebooks do give errors.
First,I tried to do it the way @michalk8 suggested here  https://github.com/theislab/moscot/issues/552#issuecomment-1596752234 (by building docs) but it required messing with the metadata of nb files and the errors were written to log files. For now jupytext seemed easier.

I think it's a jax update https://jax.readthedocs.io/en/latest/changelog.html , I think we need to pin down jax for the time being until ott-jax supports it, cc @MUCDK @michalk8

Isn't the example failing according to the tests?

@ArinaDanilina can you check the failing example, please?

thanks @ArinaDanilina , @selmanozleyen , still some issues in notebooks, but should be easy fix!


No answer when posting only text-fields (no files)

Hi,
I don't know if this is a formidable issue or a gridform issue, or maybe even more likely an issue with my code, but when posting a form without any files (only text fields), I get no answer. When only a file is provided everything works fine, the same when both files and fields are provided in the post. Do you have any idea what this problem might be?
var form = gridform(); //enters into the incoming form constructor (see longer down)
	assert(form instanceof formidable.IncomingForm);
	form.parse(req, function (err, fields, files) { // this is not fired at all.....

I have tracked it down to the IncomingForm.handlePart method here:
IncomingForm.prototype.handlePart = function(part) {
...
...
    part.on('end', function() {
    	console.log(value);//this prints
      self.emit('field', part.name, value);
    });
    return;

With published 0.1.7
formidable 1.0.14 and gridfs-stream: 0.5.0
This problem reapears.
I've updated to: formidable 1.0.16 and gridfs-stream: 0.5.3
all test passed and empty file posts parsed ok!


Questions on @sensitive

Suppose we have:
@sensitive
structure Struct {
    member: List
}

list List {
    member: Password
}

@sensitive
string Password

I have a few questions on the @sensitive trait; let me know if you'd like me to create separate issues for any of them.
1. Transitivity of @sensitive
Is @sensitive transitive? Is List to be considered sensitive in the same respects as Struct and Password (i.e. redacted from logs)? Or only when it is being hosted in the programming language type represented by Struct? Note that:

If List were @sensitive, it would be logged as "*** Sensitive Data Redacted ***".
If List were not @sensitive and had two members, it would be logged as ["*** Sensitive Data Redacted ***", "*** Sensitive Data Redacted ***"].

2. Backwards compatibility of @sensitive
Currently, in smithy-rs we implement the Debug trait on structs so that if the structure shape is @sensitive, we redact it; likewise, if any of the structure members targets a shape that is @sensitive, we redact them too.
let st = Struct { member: vec![String::from("password")] };
dbg!(&st); // Prints `"*** Sensitive Data Redacted ***"`.

Is this behavior compliant with the spec? I assume, from the lack of a mention in the Evolving models page, that it is backwards-compatible to add or remove @sensitive in the model. However, in smithy-rs it might not be, because the actual implementation of Debug would change.
3. On newtyping @sensitive shapes
In smithy-rs, Password is currently rendered as a regular std::string::String type from the standard library. So when a user writes:
let password = String::from("secret");
dbg!(&password);
println!("{}", &password);

They'd be printing out the contents. In this particular example it might be OK to go ahead and log the string, since the user's intention is clear. However, consider that:

Password may be very nested in a (non-@sensitive) shape hierarchy. When the user logs the root shape, they might be inadvertently logging Password.
The @sensitive trait may be added to a shape at any time. Things that are currently being logged might become sensitive in the future and the user's application would then be inadvertently logging them!

I doubt this problem is solvable in all programming languages, but in Rust newtypes are a widespread pattern that may offer a solution. Instead of rendering the Password shape as a standard library String type, we'd render it as a code-generated Password unit struct type we have control over. We'd be able to implement Debug and Display on said type to redact its contents if the shape is @sensitive. We're considering implementing such a thing over in https://github.com/awslabs/smithy-rs/issues/1833 for server SDKs. As experts in the spec, do you have any thoughts about whether we should or shouldn't do this?

Is @sensitive transitive

No. It only applies to the direct shape and it's members.

Is this behavior compliant with the spec? I assume, from the lack of a mention in the Evolving models page, that it is backwards-compatible to add or remove @sensitive in the model. However, in smithy-rs it might not be, because the actual implementation of Debug would change.

It is backward compatible to add/remove the sensitive trait, yes. Changing the output of Debug shouldn't be an issue and is actually desirable IMO if something truly is sensitive and a team adds the sensitive trait. Changing the type signature based on sensitive traits would be something to avoid though since it would break previously generated code, and we don't want to discourage service teams from retroactively fixing their models by applying missing sensitive traits.
re: Evolving models page: This page doesn't contain every possible backward or forward compatible change, and I don't think it ever could. Maybe we need to make that more clear. The best place to look for trait compatibility is the spec for the trait and the prelude model. Trait defintions describe their backward compatibility constraints, so you can find them in the prelude. We need to better publish the prelude somehow too.

On newtyping @sensitive shapes

The problems I can think of here are:

You'd be changing the generated type from, say a normal String, to a different type. If a service omitted a sensitive trait and later needs to add the trait, that would be a breaking change. We don't want to discourage adding the sensitive trait.
If you're generating code based on the type name, then that's a risk. It's actually documented as something you don't need to worry about changing in a few places in Smithy specs and guides. smithy-diff won't care if you change a member target from one compatible string to another (you could, say, change a member from targeting a sensitive marked "Password" to a senstive marked "SecretKey", and it would be considered backward compatible).

Thanks for answering my questions.

The best place to look for trait compatibility is the spec for the trait and the prelude model.

Ah, I didn't know that. It'd be neat if we parsed the backwards compatibility info and surfaced it in the docs.
re: the problems on newtyping you call out, it's clear we can't do this on generated clients. Our doubt is whether to do it in server SDKs, which are authoritative model consumers, and where it might even be a good thing to break the build, since allowing the application author to inadvertently log these may be seen as a security risk. We already newtype constrained shapes (with a codegen option to disable such behavior), so newtyping on @sensitive would follow a similar approach.

Closing as I believe the main question is answered and the note for checking compatibility has been added to the spec.


CUDA out of Memory with Callbacks

Hi!
I'm trying to train a model using my own data. I followed the tutorial for the data in order to achieve the correct format for source, target and the prompts.json. The data I use is 512x512. I have a machine with 16GB GPU, and the training starts without problem until the logger frequency from the image logger and the checkpointing frequency match. Then the training stops and raises the following:

torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 512.00 MiB (GPU 0; 14.76 GiB total capacity; 12.84 Gi
B already allocated; 401.75 MiB free; 13.33 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory
try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

This is my training code:
from share import *

import pytorch_lightning as pl
from pytorch_lightning.callbacks import ModelCheckpoint
from torch.utils.data import DataLoader
from control_dataset import MyDataset
from cldm.logger import ImageLogger
from cldm.model import create_model, load_state_dict

# Configs
resume_path = './models/path_to_model.ckpt'
data_root = 'path_to_dataset_with_source_target_and_prompts'
batch_size = 2
train_name = 'training_name'
logger_freq = 1000
checkpoint_freq = 1000
learning_rate = 1e-5
epochs = 2
sd_locked = True
only_mid_control = False

# First use cpu to load models. Pytorch Lightning will automatically move it to GPUs.
model = create_model('./models/cldm_v15.yaml').cpu()
model.load_state_dict(load_state_dict(resume_path, location='cpu'))
model.learning_rate = learning_rate
model.sd_locked = sd_locked
model.only_mid_control = only_mid_control

# Misc
dataset = MyDataset(data_root=data_root)
dataloader = DataLoader(dataset, num_workers=0, batch_size=batch_size, shuffle=True)
logger = ImageLogger(batch_frequency=logger_freq)
checkpointer = ModelCheckpoint(
    dirpath=f'checkpoints/{train_name}',
    every_n_train_steps=checkpoint_freq,
    save_last=True,
    save_weights_only=True
)
trainer = pl.Trainer(
    gpus=1,
    precision=32,
    accumulate_grad_batches=2,
    callbacks=[logger, checkpointer],
    max_epochs=epochs,
)

# Train!
trainer.fit(model, dataloader)

When the training arrives at the step 1000, then the image logging works as expected sampling 50 samples:

Data shape for DDIM sampling is (2, 4, 64, 64), eta 0.0
Running DDIM Sampling with 50 timesteps
DDIM Sampler: 100%|███████████████████████████████████| 50/50 [00:54<00:00,  1.09s/it]
Epoch 0:   4%| | 1000/25007 [55:58<22:23:39,  3.36s/it, loss=0.156, v_num=0, train/loss_simple_step=0.130, train/loss_vl

But at this stage the cuda out of memory error ocurres. I am doing something wrong with the ModelCheckpoint callback?
I have set save_memory=True but nothing changes.
Any idea why this happens?

I am facing the same issue. Is there any way to solve this problem. I am using 12GB GPU to train the network

拉屎擦屁股是资本主义骗局吗？

all duplicate concerning "RAM and out of memory exceptions (OOM)":
https://github.com/lllyasviel/ControlNet/issues/21
https://github.com/lllyasviel/ControlNet/issues/33
https://github.com/lllyasviel/ControlNet/issues/191
https://github.com/lllyasviel/ControlNet/issues/236
https://github.com/lllyasviel/ControlNet/issues/241
https://github.com/lllyasviel/ControlNet/issues/247
https://github.com/lllyasviel/ControlNet/issues/294
https://github.com/lllyasviel/ControlNet/issues/301


[OSDEV-1346] Refactor search_after and sort_by parameters for GET v1/moderation-events and GET v1/production-locations endpoints

Fixed OSDEV-1449
OpenSearch:

Refactored sort_by parameter.
search_after has been split to search_after_value and search_after_id.

Converted to draft because it requires refinement for asc / desc sorting.


Validate all info in PIPELINE.md

Validate all info in PIPELINE.md

@hfranklin I added doc build and deploy steps to the pipeline, see #367 .

Need to update the details of each pipeline step, still.


12.6.6

Channel: snowflake
Upstream: https://gitlab.com/conradsnicta/armadillo-code/-/tree/12.6.x?ref_type=heads
conda-forge: https://github.com/conda-forge/armadillo-feedstock
Depends on:

https://github.com/AnacondaRecipes/superlu-feedstock/pull/1

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:10: http_url: http://sourceforge.net/projects/arma/files/armadillo-12.6.6.tar.xz is not https
WARNING: clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:36: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:10: http_url: http://sourceforge.net/projects/arma/files/armadillo-12.6.6.tar.xz is not https
WARNING: clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:36: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:31: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:38: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:33: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:40: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Arg, I think I'll need to compile with OpenMP. Which means I'll need to figure out why I can't compile with OpenMP...

Arg, I think I'll need to compile with OpenMP. Which means I'll need to figure out why I can't compile with OpenMP...

Is it some similar trick for llvm-openmp / intel-openmp conflict?
https://github.com/AnacondaRecipes/pytorch-forecasting-feedstock/blob/d8f6e07bc093bb1a0c012669a62f4177c5bce2e2/recipe/meta.yaml#L25-L35

[PKG-3197]

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:33: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:43: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
ERROR: clone/recipe/meta.yaml:45: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:33: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:43: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
ERROR: clone/recipe/meta.yaml:45: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:42: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
ERROR: clone/recipe/meta.yaml:44: cbc_dep_in_run_missing_from_host: Run dependencies listed in the cbc should also be present in the host section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:9: invalid_url: https://sourceforge.net/projects/arma/files/armadillo-12.6.6.tar.xz : Not reachable: 502
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
WARNING: clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
Warnings were found


fix: update JavaScript standard objects String.prototype.trimright stub article

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @abbotttp for your contribution and congratulations on your first PR merge to this repo! 🎉