Add the option to create other sections in Pipfile

A common pattern in Django projects is spliting requirements in differents files. We do this in our company following the recommendations of the Two Scoops of Django of @pydanny and @audreyr. In cookiecutter-django you can see this patterns: https://github.com/pydanny/cookiecutter-django/tree/master/{{cookiecutter.project_slug}}/requirements
So, my thought is that pipenv needs to provide more options besides the regular pipenv install and pipenv install --dev. Maybe something like pipenv install requests --section=production and then pipenv install --section=production to install all the production related packages.

not happening. explicitly designed for just two groups.

e..g this is an explicit design decision, inspired by composer, not an accident.

[default] is production.

Ok, got it.
I just wanted to separate dev packages from test packages but it's not a big deal.

yeah, that's the idea, it's not a big deal. the fact that the composer community has been able to pull this off gives me faith that we'll be able to as well.
keep in mind, the pipfile spec allows for other groups to be added in the future, so we can add this later, if demand is really very high, but so far, it's been smooth sailing.

e.g. only having two groups is a superior experience (imo) to having arbitrary groups.

keep in mind, the pipfile spec allows for other groups to be added in the future, so we can add this later, if demand is really very high, but so far, it's been smooth sailing.

agree with that

Here's a use case: when we want to install certain packages only in production and not in a local environment. For example, gunicorn, or whitenoise, or some email library from a provider like Mailgun, Sendgrid, etc.

Don't you test your production packages?

If you want to separate requirements this much, think on the following:

consider staying with pip and virtualenv. It's low level enough and works great. Especially if you want to keep debugging tools that can be a risk out of production.
Remember that standards and practices evolve over time. So maybe pipenv has invalidated the approach we specify in Two Scoops of Django.

@techalchemy, sure, I test the production packages, but perhaps I don't want to do it on my local machine and only on a CI server or something.
@pydanny, indeed. I did separate the production packages before reading Two Scoops of Django, though :) Great stuff, by the way!
In the end, I agree with what others said: it's not a big deal. It means I will have to install packages I don't need in my local environment but it's not a show-stopper.

@pydanny Pipenv is actually very well suited to keep debugging tools out of production, since if you install them with pipenv install --dev then you have to forcibly and intentionally install your dev dependencies with the --dev flag again in the future.  Its just having things that only belong in production that pipenv does not currently offer

Just want to add a use-case of how the two groups are less-than-ideal, although workable:
I would suggest that "groups" are for humans. they are for helping us organize are minds and the projects our minds build. in rubygems land, groups can be arbitrarily named. assuming that prod and dev as the distinction is not something that ecosystem tries to impose.
For example, one project I'm interested in doesn't even use python on the production website, but has some processing tasks that happen locally to build assets. The two groups it wants to make distinction between are "devserver" (a mock api server that runs in python only locally) and "processing" (a bunch of long-compiling scientific packages for doing geospatial work). Forcing a project like this in the dev/prod dichotomy makes less sense.
Basically, I feel that the distinction is more opinionated than need be, and prevents to tool from speaking human in the way that users might like it to. In my example, we need to have a section to explain this, instead of just having intuitive names of the groups that can go in a command line flag :)
Anyhow, thanks so so much for all your hard work. Just wanted to provide a counter-point. Everything is work-aroundable, but I simply would contest that it shouldn't need to be -- it seems a reasonable ask. (fwiw, as someone who comes from php land, i feel rubygems and maybe go is the package management ecosystem to emulate, not composer)
Y'all are awesome! :heart:

Composer has been successful with just two groups. That's what inspired this decision.

I also worked with PHP for a very long time and, just like Patrick, don't really think it's the best thing to emulate.
@kennethreitz, how would Composer handle the scenario @patcon described?

What I don't get is why impose a limitation that brings no clear advantage (aside from the obvious simpler implementation but I wouldn't say it's such a big difference), when lifting that limitation would make life easier for many people, even if they are just 5%. But hey, it's not my project and I don't want to become a PITA by insisting on this ad nauseam :)

The implementation factor is a huge advantage though. As a maintainer I can say that anywhere our codebase is complex or hard to follow I’m reluctant to accept any PR I didn’t personally test by hand and trace just because things are much more likely to break.
For end users, if you’re new to python and you see that you can have 5 sections you start thinking maybe you should. Then every time you try to use pipenv you can’t remember what section you put a package in. You don’t use cat Pipfile because you’re new, you have to open it in an editor and this is a slow process. You get frustrated. Eventually you just start guessing and accidentally wind up installing the same package in a brand new section you just created. Now you have 6 sections. Ultimately you decide the whole process is overly complicated and you don’t feel like dealing with it anymore so you go back to some other thing that isn’t pipenv or maybe it isn’t even python.

Yes, implementation is a big factor. As a contributor I went through multiple episodes that went like “maybe I should come up with something to try persuading Kenneth and Dan” and after 15 minutes my head started hurting so I stopped. For anyone strongly pushing this issue, I encourage you to get yourself familiar this whole dependency resolution thing is done, and try to come up with a workable implementation. Hopefully one of us will eventually come up with something, but before that, take my words and drop it.

I totally agree with the implementation complexity weighing considerably on the decision of implementing something. Not so sure about the multiple sections, though. But yes, it's dropped :)

Being able to have sections for docs/tests/... as in https://github.com/pypa/pipenv/issues/726#issuecomment-387707042 would be nice, but one can sort of live without this. However, how should one handle the case when one codebase covers multiple related but separate applications, each having different dependencies. For example, I am developing an application, which has a web, gui and cli interface. The gui needs the PyQt5 package but I wouldn't want to install it on the server serving the web interface (and in some environments, perhaps I couldn't, even if I wanted).

Being able to have sections for docs/tests/... as in #726 (comment) would be nice, but one can sort of live without this. However, how should one handle the case when one codebase covers multiple related but separate applications, each having different dependencies. For example, I am developing an application, which has a web, gui and cli interface. The gui needs the PyQt5 package but I wouldn't want to install it on the server serving the web interface (and in some environments, perhaps I couldn't, even if I wanted).

Same situation can be applied to API development, I need set different requirements for client and server side of the API.

I'm deploying an application in a (alpine-based) docker container and need different dependencies in that environment.  It would be helpful if I could define optional dependencies in a a [docker] section.

I'm deploying an application in a (alpine-based) docker container and need different dependencies in that environment.  It would be helpful if I could define optional dependencies in a a [docker] section.

Yep, a [container] or [docker] section could prove to be useful.  At times I'm building docker containers with base images that already have certain packages preinstalled (eg OpenCV with a specific build configuration), removing package installs already present in the docker images is useful.

Just to contribute with the discussion, I have a scenario where >2 groups would be useful:
I'm working on a project that's entirely backed by AWS Lambda functions. The code is structured as a SAM project; one application - in one Git repository - composed of multiple Lambda functions, like so:
application
├── .git/
├── Pipfile
├── Pipfile.lock
├── lambda_function_a/
│   ├── __init__.py
│   ├── app.py
├── lambda_function_b/
│   ├── __init__.py
│   ├── app.py
├── [...]
├── template.yaml
└── tests/
[...]

Each Lambda function is packaged and deployed independently, and they each have their own dependencies. Currently, I'm specifying all dependencies in the main Pipfile, which means each function gets packaged with all dependencies of all other functions. This is not a huge problem, but it would be neat if we could either specify one dependency group for each lambda_function_X...

@igorlg We are tracking this feature request in:  https://github.com/pypa/pipenv/issues/4745
I am going to post my latest thought in that thread of something we will have to look out for.

@igorlg We are tracking this feature request in: #4745
I am going to post my latest thought in that thread of something we will have to look out for.

Thanks for your reply, @matteius! Would you like me to move my previous comment to #4745?

Feel free to cross-post it.


Dev ssk

Completed the model and training function so I have a working neural network. Next step is fitting it with some other data such as healthcare data

@SidKasi will take a look this weekend!


SNOW-925266: Session should not close connection when connection provided manually

What is the current behavior?
Currently it is possible to provide a connection to SessionBuilder using the connection option. This is useful with systems that provide connection creation automatically, e.g. Prefect.
However, regardless of how the connection is passed in, closing the session will always close the connection as well. This is unexpected when the SessionBuilder doesn't create the connection itself.
What is the desired behavior?
It would be good to explicitly say that "do not close the connection" when closing a session. Ideally this would be the default if the connection is passed in, but that might be backwards incompatible.
How would this improve snowflake-snowpark-python?
It'd be less surprising for the usecase where the connection is passed in.

This seems reasonable and could be a starter's task. cc @sfc-gh-yixie


Waypoint: Target the Children of an Element Using jQuery

Any idea why this code isn't working? I've had problems with the past 2 Waypoints that were recent issues with the website.

Solution: Website issues, just had to reset the code and reload the page multiple times. Crisis averted!


Chrome considered $http request cancelled with either timeout number or promise to still be "pending" indefinitely

I'm pretty sure the snippet below is correct. I don't think it matters that I'm using JSONP since I basically had the same problem when trying to use a simple "get" method. If the URL in this case does not respond and my timeout kicks, the "deferral.resolve()" correctly triggers the "error" method on the $http request, but in the Chrome tab for the page I see the "spinning" request-pending animation and the Javascript Console shows the request still "pending." Is there some way programmatically to convince Chrome that the request HAS been cancelled?
    var deferral = $q.defer();

    $http.jsonp('http://something/api?callback=JSON_CALLBACK',{timeout: deferral.promise})
      .success(function(data){
        $timeout.cancel(timeout); // not sure if this is necessary, but assume it is...
        console.log('success! ');
      })
      .error(function(data, status){
        $timeout.cancel(timeout); // not sure if this is necessary, but assume it is...
        console.log('error! ' + status);
      });

    var timeout = $timeout(function(){
      if (deferral) {
        console.log('timeout! ');
        deferral.resolve();
      }
    },250);

@spemmons actually it does make a difference when you do JSONP request as JSONP is a smart hack really and it is next to impossible to cancel requests in a reliable way.
Could you please provide a minimal, live reproduce scenario for non-JSONP requests? At the end of the day AngularJS is just calling xhr.abort() to cancel a pending request so if a browser doesn't honor this call, there is not much we can do...
Anyway, please provide a minimal, live reproduce scenario so we can have a look.

I'm gonna close this as we have not reproduce scenario, Feel free to reopen with more information.

We're seeing this same behaviour on Chrome on Ubuntu 16.04 when call $http.get().


feat:Contributors

What feature?
As this is open source project it is important to show users who is owner of this project and contributors. I want to create contributors part where all contributors will be shown in card format just like projects and their contributions will be shown.
Add screenshots

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[ ] I want to work on this issue

duplicate of https://github.com/priyankarpal/ProjectsHut/issues/1847


Pictures are not displayed in Chrome

When using the plugin in chrome there is no pictures visible.
I'm having the issue on my website and on the demo: https://sharebutton.co/
It seem to works fine in all other browser.

Be glad for that... Downloading the latest and the share button dosen´t even display for me in either Safari nor Firefox on El Capitan! :/

But for me the demo page is working fine in Chrome!

It also doesn't work on IE11 nor Edge browsers, but works for me in Safari. As per https://github.com/carrot/share-button/issues/250 there seems to be untested new version that has improved cross-browser compatibility. Unfortunately I am not able to test it as it requires a build environment to create distribution files, and I was not successful in creating one.
In the meantime I did some digging in the CSS and it seems that there are problems with <svg> tags. When I used SVG editor, exported and pasted updated content I was able to see the icons in all browsers. The side effect however is that the icons are not centered within the boxes in IE nor Edge, but look fine in other browsers.

I have the same issue. On Chrome 50, and IE - icons are invisible.
So here's a workaround that I did. I took the SVG images from the repo, I added a second version of each (example: pinterest-light.svg) that's the same, but white (with fill="white") and finally I overrode the messed-up plugin styles - updating the background-image with the external SVGs that I placed in my project /img/share-button directory. Here's an example.
share-button .sb-social li[class*='pinterest']:after {
    background-image: url('/img/share-button/pinterest.svg');
}
share-button .sb-social li[class*='pinterest']:before {
    background-image: url('/img/share-button/pinterest-light.svg');
}

So I did this steps for all icons that I needed. It works on Chrome, Firefox, Safari and IE latest. The only issue is that it 'costs' a few additional server (http) requests. But I guess, this is still better then not working at all :)
And here's my full fix. Download the zip: share-button-svgs.zip and extract it in your images directory. Than paste this styles in your project stylesheet, making sure the url on your side is correct.
/**
 * Solves the issues with SVG as a background image,
 * that doesn't display on Chrome 50 and IE latest.
 * This way it works on Chrome, Firefox, Safari and IE latest.
 *
 * https://github.com/carrot/share-button/issues/301
 */
share-button .sb-social li[class*='pinterest']:after {
    background-image: url('/img/share-button/pinterest.svg');
}
share-button .sb-social li[class*='pinterest']:before {
    background-image: url('/img/share-button/pinterest-light.svg');
}

share-button .sb-social li[class*='twitter']:after {
    background-image: url('/img/share-button/twitter.svg');
}

share-button .sb-social li[class*='twitter']:before {
    background-image: url('/img/share-button/twitter-light.svg');
}

share-button .sb-social li[class*='facebook']:after {
    background-image: url('/img/share-button/facebook.svg');
}
share-button .sb-social li[class*='facebook']:before {
    background-image: url('/img/share-button/facebook-light.svg');
}

share-button .sb-social li[class*='googlePlus']:after {
    background-image: url('/img/share-button/googlePlus.svg');
}
share-button .sb-social li[class*='googlePlus']:before {
    background-image: url('/img/share-button/googlePlus-light.svg');
}

share-button .sb-social li[class*='email']:after {
    background-image: url('/img/share-button/email.svg');
}
share-button .sb-social li[class*='email']:before {
    background-image: url('/img/share-button/email-light.svg');
}

share-button .sb-social li[class*='linkedin']:after {
    background-image: url('/img/share-button/linkedin.svg');
}
share-button .sb-social li[class*='linkedin']:before {
    background-image: url('/img/share-button/linkedin-light.svg');
}

I’m having the same issue as @nicolasbadia
The icons show up in Safari and Firefox. But they aren’t appearing in Chrome.
You can see the live site here: http://www.ecovativedesign.com/blog/146

@shanetheboland You seem to have fixed this on your site. What was the solution?

@hypergeometric

Download this zip https://github.com/carrot/share-button/files/254008/newcss.zip
Move the new share-button.css into your css directory and replace the old share-button.css

Found the answer in Issue #305.

@shanetheboland Awesome thanks!


Fixing Fixing headline formatting.

Not sure what was up with those hashtags before but the "Guideline Summary" did not get displayed correct as a headline in github.

I only changed a single line in a .md file so I don't think that any of these failing checks are actually related to my change. Maybe octobot just got stricter since it evaluated this file last :)


Agda: <IP_ADDRESS> -> 2.5.1

Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] 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/)
[x] Fits CONTRIBUTING.md.

This PR contains a few things associated with updating from Agda-<IP_ADDRESS> to Agda-2.5.1. It fixes #15306 by compiling all of the built-in modules in the postInstall section. Then, agda-stdlib and agda-prelude have been updated to versions which work with the new version.
I've tested agda-mode and tested checking modules using agda-stdlib. I don't know what agda-ghc-names is about, but I vaguely assume that it works. agda-ghc-names --help works, anyway.

Okay, so the update breaks some old packages from 2014. Some of the Agda packages seem to be obsolete (agda-base replaced by HoTT-Agda, Agda-Sheaves replaced by constructive-sheaf-semantics). Should I go through them all and set broken = true?

cc @peti

Tests are failing now because it takes too long. Agda does take a long time to build.

Merging, given the lack of feedback and seeing how this fixes an issue with Agda. Thank you.

@joachifm, you diagnose "lack of feedback" in a PR that's barely 24 hours old?

@peti for me it's showing 2 days. Anyway, I was too hasty, I'm sorry.

@laMudri I've pushed a fixed version of your PR at https://github.com/joachifm/nixpkgs/commits/Agda-fixed

Thanks for fixing, and sorry about not looking more carefully. How did the postInstall instructions ever get into that auto-generated file? I notice that other Agda versions also have those commands, but they're not in configuration-common.nix.

https://github.com/NixOS/cabal2nix/blob/master/distribution-nixpkgs/src/Distribution/Nixpkgs/Haskell/FromCabal/PostProcess.hs#L193-L199

Um, too much was reverted. Please see 072ce88, 92b843f, and 6343cf8. All of these packages are still broken on master.

@laMudri I reverted the merge itself. Please open a new PR if you want these changes integrated. Feel free to use the version I posted, but beware that it is untested, so please confirm that it is still valid.
I think the only issue was writing to the auto-generated file, so if you address that we can go ahead with your changes. The issue is quite old at this point (17 days as of this writing) with no alternative solution.

Okay, thanks. I have something tested based on your branch, so I'll just double check it and make a new PR.


fix: typo mail link in feedback section on readme

Should the pushing to the registry not only be executed on the master/main branch? I've got no permission to the secret settings of this repository therefore the pipeline will always fail.

@theexiile1305 Awesome, thanks for this PR. @BenedictHomuth Could you please change the GitHub Actions settings, that the pipeline will only run on main/master. Thanks!


feat!: Allow providing app_name, toolkit_name and toolkit_version in Tree, remove parameters from unix adapter constructor

Similar to the unix crate, this adds app_name, toolkit_name and toolkit_version parameters to the adapter constructors.

FrameworkIdProperty: exposes toolkit_name
ProviderDescriptionProperty: exposes app_name (toolkit_name toolkit_version)

fixes #280

Thanks @leonardder for taking this!
I think the adapters constructors have too many arguments now. I didn't put too much thought into the Unix adapter because I wasn't sure what we would do with this information, but if we support it for Windows too, I think we should consider the builder pattern, and preferrably do it in a similar way on both Windows and Unix.
I don't know if we can implement the same for macOS, but now might be the right time to allow setting these values for the winit adapter as well, the builder pattern might be relevant here too.

Also before you push here, please make sure to format your code by running cargo fmt (on the whole workspace) and cargo clippy (on the updated crates).

I was actually thinking about putting this info in the accesskit::Tree struct that has to be provided with the first tree update. That might complicate how that structure is built in the C bindings, but I think it would make sense.

This would indeed make sense. Do we want these fields to be optional?

Yes, definitely optional. So make them Option<String>, and if they're absent, then the Windows adapter leaves those properties empty (as in an empty variant, not an empty string), and the Unix adapter returns empty strings.

I was actually thinking about putting this info in the accesskit::Tree struct that has to be provided with the first tree update. That might complicate how that structure is built in the C bindings, but I think it would make sense.

I'm happy to give this a try, but I assume that also means removing the constructor parameters from the unix adapter right? If so, it might be better to close this pr and come up with something new whenever I'm done with that.

@leonardder We definitely want to drop those options from the Unix adapter's constructor. For that reason, I'd like to include this change alongside the other breaking changes we've been making lately, if you have time to do it in the next week or so. Whether you close this PR and open a new one, or just edit this one, is up to you. It's only a draft right now anyway.

As for the C bindings, I think we'll need to turn accesskit_tree into an opaque boxed type with setters, like I recently did for accesskit_tree_update.

For that reason, I'd like to include this change alongside the other breaking changes we've been making lately, if you have time to do it in the next week or so.

I'll do whatever I can.

I added three new fields to the Tree struct. We can either:

Expose them in the new constructor method
Remove the new constructor (i.e. use struct initialization)
Leave them optional at construction time. This keeps backwards compatibility but if someone wants to fill the struct field, he ought to store the tree instance in a separate variable first.

My preferences is to keep these fields optional on Tree and keep the current constructor. I'm willing to be convinced otherwise though.

I think I share that preference, so I'll go ahead wit that. Thanks for the quick response!

I think this is ready to rock now.

Yeah I encountered the same issue with consts, their support in initializers is quite recent apparently. We should maybe switch to using #define as to avoid initializing the initial focus at runtime.

I believe I have addressed all the review comments now.
I changed the offending const in the examples to a #define but didn't touch the other constants.

I've applied a non-controversial change and I rebased this to save you the hassle. For me this PR is OK now.
Thank you very much for working on this.

 Thanks for the rebase!

@leonardder You should definitely add your name to the AUTHORS file.
I think it would be a good idea to rebase this branch onto the latest main commit one more time, just to make sure none of the recent Unix adapter changes introduce conflicts.
Please make sure you've reformatted the C examples with clang-format.

Otherwise, this looks good. And, having read the minor changes to the Unix adapter, I doubt that we need another rebase now.

Please make sure you've reformatted the C examples with clang-format.

I have performed formatting with VS Code, I'm pretty sure that uses a clangformat file when available, but I'll double check.

I have merged in main and made sure that the c files are formatted correctly. I assume you'll perform a squash merge?

@leonardder Yes, I always do a squash merge.
Now I just need you to add your name to the AUTHORS file, and then once the CI passes, I'm ready to merge this. Thanks for your contribution!

Now I just need you to add your name to the AUTHORS file, and then once the CI passes, I'm ready to merge this.

AH I'm sorry, Done now.

Thanks for your contribution!


Build A Website

A website needs to be built, that will be the home page of the app and interaction point on the computer.

Added in commit 6e8e1fb3c5e2e23238aab7f02cfc2979598a5463


Conversion to SAM produces flags that are all 0

Conversion to SAM produces flags that are all 0, this is manifestly incorrect.
python ga2sam_dev.py http://localhost:8000 MWtnLXAzLXN1YnNldDpIRzAwMDk2OlNSUjA2MjYzNQ== --referenceId=R1JDaDM4LXN1YnNldDoz

Resolved


Screenshots outdated

Screenshots on this page are outdated and don’t match the current blades where “MS dependency agent (preview)” is shown below Auto provisioning - Extensions

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

ID: 069802b7-9db6-f5d6-b1aa-52ebc42e96f8
Version Independent ID: 7b011f8a-0a1c-5066-5d20-3cedcdfc7403
Content: Auto-deploy agents for Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/enable-data-collection.md
Service: defender-for-cloud
GitHub Login: @memildin
Microsoft Alias: memildin

@andrePKI,  Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

Hi @andrePKI, thanks for the feedback and for taking the time to help us improve the docs.
This documentation page is currently undergoing a major refresh. An updated version will be published early next year.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close


⚠ Bofrost.de has degraded performance

In e832230, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1243 ms

Resolved: Bofrost.de performance has improved in 8b6e261.


Update LFH to Support Snapshot Dependency

This PR updates the following:

LFH container configurations now support the snapshot image
Container/Deployment Doc/README cleanup

@ccorley - I thought the location of the section and it's heading was a bit confusing. The section is now titled "Create LFH Project Within an Existing OCP Cluster". I hope that this change along with some verbiage regarding how the provision and "project creation" scripts are independent of one another brings clarity to how the scripts are used.


Godot Engine v4.0.beta6 don't open with Vulkan API 1.1.0 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 520

Godot version
Godot Engine v4.0.beta6.official.7f8ecffa5
System information
Windows 10, Intel(R) HD Graphics 520 Vulkan API 1.1.0
Issue description
Godot Engine v4.0.beta6 don't open with Vulkan API 1.1.0 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 520 in windows 10, I tried but never open, godot show the projects and  then when I click in edit, the window is black.

Steps to reproduce
Godot Engine v4.0.beta6 don't open with Vulkan API 1.1.0 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 520 in windows 10, I tried but never open, godot show the projects and then when I click in edit, the window is black.
Minimal reproduction project
Godot Engine v4.0.beta6 don't open with Vulkan API 1.1.0 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 520 in windows 10, I tried but never open, godot show the projects and then when I click in edit, the window is black.

Duplicate of https://github.com/godotengine/godot/issues/69046


DBSchema: Fix Case Schema

schema with constraints and indexes in this file
https://drive.google.com/file/d/13vfMX4m_m_ubILw-_pJYhd3OIQ9Zk6Ar/view?usp=drive_link

@manimaarans @Ramu-kandimalla @suresh12 - what's the update on this? Can we confirm the latest status?

Hi @subhashini-egov  @atulgupta2024  Need clarity on this ticket @manimaarans @suresh12

@Ramu-kandimalla The DB schema was lacking indexes, foreign keys and basic denormalization. Hence, I had proposed a DB schema and added all artifact details to it including SQL. A decision was made not to take this up due to other. priorities. Would request @suresh12 and @manimaarans to close it with justification.


DHL (paket.de)

Via your account settings on the website the account can be deleted

@ginwithgingerale this repository is not maintained anymore. We keep the fork alive on https://github.com/jdm-contrib/jdm


Unable to see the specflow test in Visual Studio 2019 Test Explorer

##Specflow + Easy Repro
Unable to see Specflow test in test explorer. I am using Visual Studio 2019 Community Version. Using Below Packages

sanjotsaini Do you use nuget? Why do you think that issue is related to Easy Repro?

@Shakevg - I think there is some compatibility issue with easy repro framework because I have another Nunit Api test project in which specflow is not giving me any issue.

Try to ask the author of the same project with Specflow https://github.com/microsoft/EasyRepro/issues/1025#issuecomment-746013971


Kestrel Web Server completely broken when TLS 1.3 is enabled; having TLS 1.2 enabled doesn't help

Describe the bug
Kestrel Web Server completely broken when TLS 1.3 is enabled. Firefox reports PR_END_OF_FILE_ERROR, and the only working client is net core's own HttpClient. Failing clients: Firefox, IE, openssl s_client, Edge (Edge's failure appears to be no TLS 1.3 but I can't really tell).
Expected behavior
It just works.
Additional context
  Request starting HTTP/1.1 GET http://localhost:5104/Heartbeat/Pulse

info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
Route matched with {action = "Pulse", controller = "Heartbeat", area = ""}. Executing controller action with signature Microsoft.AspNetCore.Mvc.IActionResult Pulse() on controller Cedaron.FormBuilder.Presentation.Controllers.HeartbeatController (Cedaron.FormBuilder.Presentation).
info: Microsoft.AspNetCore.Mvc.StatusCodeResult[1]
Executing HttpStatusCodeResult, setting HTTP status code 204
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Executed action Cedaron.FormBuilder.Presentation.Controllers.HeartbeatController.Pulse (Cedaron.FormBuilder.Presentation) in 1.2453ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Request finished in 2.4098ms 204
fail: Microsoft.AspNetCore.Server.Kestrel[0]
Unhandled exception while processing 0HLQHOG2JCIDM.
System.NullReferenceException: Object reference not set to an instance of an object.
at System.Buffer.Memmove(Byte& dest, Byte& src, UInt64 len)
at System.Net.Security.SafeDeleteContext.AcceptSecurityContext(SafeFreeCredentials& inCredentials, SafeDeleteContext& refContext, ContextFlags inFlags, Endianness endianness, ReadOnlySpan1 inSecBuffers, SecurityBuffer& outSecBuffer, ContextFlags& outFlags)    at System.Net.SSPISecureChannelType.AcceptSecurityContext(SafeFreeCredentials credential, SafeDeleteContext& context, ReadOnlySpan1 inputBuffers, ContextFlags inFlags, Endianness endianness, SecurityBuffer& outputBuffer, ContextFlags& outFlags)
at System.Net.SSPIWrapper.AcceptSecurityContext(SSPIInterface secModule, SafeFreeCredentials credential, SafeDeleteContext& context, ContextFlags inFlags, Endianness datarep, ReadOnlySpan1 inputBuffers, SecurityBuffer& outputBuffer, ContextFlags& outFlags)    at System.Net.Security.SslStreamPal.AcceptSecurityContext(SafeFreeCredentials& credentialsHandle, SafeDeleteContext& context, ArraySegment1 input, Byte[]& outputBuffer, SslAuthenticationOptions sslAuthenticationOptions)
at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
at System.Net.Security.SslStream.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
--- End of stack trace from previous location where exception was thrown ---
at System.Net.Security.SslStream.ThrowIfExceptional()
at System.Net.Security.SslStream.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslStream.EndProcessAuthentication(IAsyncResult result)
at System.Net.Security.SslStream.EndAuthenticateAsServer(IAsyncResult asyncResult)
at System.Net.Security.SslStream.<>c.b__69_1(IAsyncResult iar)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Server.Kestrel.Https.Internal.HttpsConnectionMiddleware.InnerOnConnectionAsync(ConnectionContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.KestrelConnection.ExecuteAsync()
Include the output of dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   3.0.100
Commit:    04339c3a26
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.18362
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.0.100\
Host (useful for support):
Version: 3.0.0
Commit:  7d57652f33
.NET Core SDKs installed:
1.1.14 [C:\Program Files\dotnet\sdk]
2.1.403 [C:\Program Files\dotnet\sdk]
2.1.604 [C:\Program Files\dotnet\sdk]
2.1.700 [C:\Program Files\dotnet\sdk]
2.1.701 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.1.802 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

With one broken client, it might make sense to conclude with client is broken. When every client I could try not sharing a codebase with net core is broken, it makes sense to conclude something in net core is broken.

Which OS are you hosting this on?

This issue was moved to dotnet/corefx#41828


Overrides Rainbow Brackets

Rainbow Brackets by 2gua colors pairs of e.g. parenthesis, which helps immensely with finding errors in nesting. And it looks pretty. When Syntax Highlighter is enabled it seems to override the stylesheet for brackets, clobbering the entire purpose of the other extension.
This happens with C/C++ but not with Python code, with and without Microsoft's C/C++ extension.
Removing
        "\";\"": "punctuation",
        "\":\"": "punctuation",
        "\",\"": "punctuation",
        "\"[\"": "punctuation",
        "\"]\"": "punctuation",
        "\"{\"": "punctuation",
        "\"}\"": "punctuation",
        "\"(\"": "punctuation",
        "\")\"": "punctuation"

from grammars/cpp.json seems to fix the problem.

Hello @ganzuul ,
This happens because both extensions use decoration API. And priority of decoration providers (order in which decorations are applied) cannot be defined.
I recommend you to simply disable highlighting of punctuation tokens. There is special setting for this. Just put "syntax.highlightTerms": [...], in your settings.json and remove "punctuation" from the array of terms to highlight.


Support model weights and calculations in bfloat16

Probably this is a long shot, but all new NVIDIA accelerators already support bfloat16, and there are some models like T5 that are actually trained on TPUs and have option to export weights in bfloat16.
Making inference in bfloat16 would require less casts to float32 compared to float16, therefore better performance.

Currently, we don't find obvious drop when running FP16 on BF16 model.
And we have plan to support BF16 inference in the future.

bfloat16 calculation is supported in most model in latest release.
Because we don't have good way to save the bfloat16 weight now, so you still need to store the model as FP32 now.

Are the activations in BFloat16 when inference is said to be in bfloat16? (except may be some softmax layers).

When users set data_type to be bfloat16, this means that the input/output of all layers are bfloat16, but FasterTransformer may uses fp32 to compute/accumulate in some kernels, like GeLU.

bfloat16 calculation is supported in most model in latest release. Because we don't have good way to save the bfloat16 weight now, so you still need to store the model as FP32 now.

@byshiue do we support save bfloat16 weights now?

so you still need to store the model as FP32 now.
If we store the model as FP32 now, how do we load that weight in FT C++ implemented models then?

Because we don't have good way to save the bfloat16 weight now

Hi @byshiue , another quick question, since there are some numpy extensions to bfloat16 (such as bfloat16 and tensorstore), I wonder if we could just convert huggingface weights to bfloat16 numpy with these extensions? If not, may I ask why it is not a good way to save the weights?

Hi, @void-main, FT does not support loading bfloat16 weight now because numpy does not support such data type. It is a good idea to use numpy extensions to support bfloat16. We will consider it, thank you for the suggestions.


Use read_label_file() function now integrated in pycoral package (instead of our own tool for this)

If we remove the pycoral package as a dependency of camml (using tflite_runtime directly instead) as is loosely planned (see Issue #9), we'd no longer have access to this function so perhaps is a bad idea to create increased dependency by doing this.


explainer: add workgroup shared memory

This PR:

adds example with workgroup shared memory in explainer
force links to open in new window (sometimes you lose an unsaved shader due to clicking example)

Thanks!


Improve error reporting in WebSocketServer

This should make troubleshooting easier. Note that I didn't add messages for the ERR_BUSY returns – let me know if that should be done.
See https://github.com/godotengine/godot/issues/45681.

This should make troubleshooting easier. Note that I didn't add messages for the ERR_BUSY returns

That's correct, ERR_BUSY is a valid error for non blocking (like EAGAIN).
I think the messages should be logged with print_verbose though.
We don't want to spam the user too much. Some of those conditions can be things like a client disconnecting too soon, an internet crawler poking you, etc.
I think, it should go to logs and processed from there in case.
The only "real error" I see there is when ssl.is_null(). Which I think should not happen so it should probably be an ERR_BUG in case.

I changed the PR to use to verbose prints per @Faless' reuqet.

Thanks!

Cherry-picked for 3.4.

Cherry-picked for 3.3.3.


Example flow name should get derived from url

Also the step names need to get adopted

In the example images and projects, the name of the user-flow should be the URL.


Add px4-firmware-updater submodule

Codecov Report

Merging #21 (a57973e) into master (dafb126) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   27.27%   27.27%   -0.01%
==========================================
  Files         781      781
  Lines       59095    59095
==========================================
- Hits        16118    16117       -1
- Misses      42977    42978       +1

Flag
Coverage Δ

unittests
27.27% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

platforms/posix/src/px4/common/drv_hrt.cpp
85.95% <0.00%> (-0.83%)
:arrow_down:

Continue to review full report at Codecov.

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


confusing file names among examples

at some point, many of the example scripts had plot_ prepended to their filenames.  I suspect this has something to do with building the docs automatically.  However, there's a serious downside in that it makes them all look like they are scripts designed to plot something.  Since the examples folder is really designed for new users to learn about how expyfun works, I think clear filenames (and clear relative imports within code, cf. #297) are an important part of that even if it means having to do some inelegant things with the doc-building code.

It is fixable, do you have time to make a PR?

not this week, but probably next week I can make time.  I just looked through our examples folders, and all of the scripts say plot_ except for eyetracking_experiment.py, pupillometry_experiment.py, and version_checking.py (all in the experiments subfolder).   Might be easier to do  add _noplot (or something similar) to those 3 files --- or maybe put them in a misc subfolder --- and then do an inverse regex on those, rather than prepending all the other files with something less confusing than plot_.  WDYT?

Sure an effective exclude plus rename works for me, though If rather spend
too the have than relocate to different folders. You could even make the
regex contain the specific filenames to skip if you want. It's less DRY but
had the most readable naming structure

I meant "I'd rather append to the name". Silly phone
If rather spend too the have


Discovery+ credentials needed for devs?

Checklist

[X ] I'm reporting a site feature request
[ X] I've verified that I'm running youtube-dl version 2<IP_ADDRESS>
[X ] I've searched the bugtracker for similar site feature requests including closed ones

Description

Does any dev need credentials to support Discovery+? I would like support for it since i have the 7 day free trial. Ends in 5 days

if it's about support for discoveryplus.com then you should comment on the already open issue.


BUG - High CPU usage

Summary
Standup Raven has high CPU time
Steps To Reproduce
Steps to reproduce the behavior:

Use plugin

Expected behavior
Lower CPU usage + time
Observed Behavior
The plugin is having up to 20% CPU load while idling and therefore is the most active process on the whole server (more than Mattermost or GitLab). The server is up for two weeks now and the plugin has almost two full days of cpu time.
Screenshots

Environment

Mattermost version: 5.36.1
OS: Ubuntu 20.04
Platform: on the server itself
Browser (if applicable): –
Platform Version: –

Yep. Had to remove it. After 4 months of work it spikes at 100% cpu usage and eats out all memory so the server crashes. And we have only 10 people in our Matterost.

A little message to confirm that this is also happening on our end - thanks @chainslunatic for noticing this.
@harshilsharma63 - is there any direction you could give to help figure out what could cause this? Happy to help in any way I can.

In my experience you can safely run killall plugin.exe and in a few seconds it'll safely respawn back, now without a huge CPU load. A temporarily workaround could be adding a cronjob to start once per night outside work hours:
15 3  * * *   root   /usr/bin/killall plugin.exe
``
It seems like this issue is in relation with posting reports to channels. Looks like each report posted adds a bit of constant CPU load into plugin process what in a matter of time sums up into a 100% load.

I can confirm that @phpony's solution of running killall plugin.exe also solves the issue of CPU load on our end, but it causes the button to fill in your daily to disappear. To re-enable the button, an administrator needs to disable and re-enable the plugin in the admin console (unless you've found another workaround for this @phpony ?)

but it causes the button to fill in your daily to disappear

Just Ctrl+R the page a few seconds after plugin respawn and it appears back. And if Mattermost tab was already open at time - it does not disappear. Just a caching things. Scheduling for night hours eliminates users negative feedback.

Ok - I confirm that the button does re-appear after roughly 20-30 seconds. Thanks for the tip @phpony - I'll implement it the way you propose for now on our instance.

@harshilsharma63 please investigate this issue.

Seeing high CPU usage on 3.2.2 as well.

Same issue here on 3.2.2 (which seems to be wrongly labeled as 3.2.3 in github releases.

To make it worse latest Mattermost do not monitor and restart plugin processes, so after manually killing it, now you need to re-enable plugin in server config. Guess this project is falling out now?


Spelling fix

Changed to IList warnings = renderedCard.Warnings;

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/net-html/render-a-card.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks for the fix @DaraOladapo


Alert Levels should be able to go to different endpoints.

Right now an AlertNode will send an alert of any level to all configured handlers.
To send them to different endpoints you can create multiple alert node that only send alerts for certain levels.
Maybe we should change it so that each level is a node and can have its own handlers.
Example: Send INFO alerts to email,  send WARNING and CRITICIAL alerts to http endpoint and log them.
Currently this can be done this way:
var data = stream. ....

data
  .alert()
    .info(...)
    .email(...)

data
  .alert()
    .warn(...)
    .crit(...)
    .post(...)
    .log(...)

Would something like this make more sense?

var alertNode = stream ....
  .alert()

alertNode
     .info(...)
        .email(...)
alertNode
     .warn(...)
        .post(...)
        .log(...)

alertNode
     .crit(...)
        .post(...)
        .log(...)

The second method will be inefficient as it has to evaluate all three alert conditions where as the first method can break out early if its only a warning.
I like the way it is now so maybe just some good examples is all we need.
@pauldix  Thoughts?

No one has asked for this closing.

The docs could use an example calling out how to achieve do this. I wanted to do configure alerts this way and didn't figure out how until finding this issue and seeing that first example.

@nathanielc I think it's a very nice feature, for example on critical alerts I would like to send an email alerts on some specific alerts - but it's must be combined with noStateChanges.
But I can't understand what is the difference between the methods, the first methods seems pretty good:
var data = ...

// Send info and warn to alert service
data.alert().info().warn().post('my-alert-service')

// Send crit to alert service and *email*
data.alert().crit().email().post('my-alert-service')

@yosiat Yes, the first method is the one that works. The second method was a proposed different way of doing it that is no longer valid. Since the first method works we should document it in the AlertNode examples so its easier to find.


Remove optimizer.py and replace it using Hydra instantiate

Currently we use "load_optimizer" and "get_optimizer" from bliss/optimizer.py in quite a few places, but it doesn't seem to do much.
We already eliminated the separate config files for the optimizer in #396. Currently we specify "training.optimizer" as a dictionary:
https://github.com/prob-ml/bliss/blob/71393515625d821b9b250c7186ba8fba6c808759/config/training/sdss_galaxy_encoder.yaml#L9-L17
This could be made even simpler as follows:
 training:
     name: "sdss_galaxy_encoder"
     model: ${models.galaxy_encoder}
     dataset: ${datasets.simulated}
     optimizer:
         _target_: torch.optimizers.Adam
         lr: 1e-4
         weight_decay: 0

This might be a little harder than I thought since the optimizer objects in torch require the model parameters when initializing them.


Disable read timeout for Pub/Sub connections

Due to the nature Pub/Sub connections they highly likely to block on reads for long periods hence it doesn't make sense to apply any read timeout configured on the pool to Pub/Sub connections.

Inherently we can't add a nice way to test we don't time out, but otherwise it looks good 👍


Add shorcuts for windows & linux to debugger.html

Very simple PR to add the shorcuts for windows/linux to the web debuger interface so it's less mac-centric.
Test plan: Open the debugger and see the shorcuts for windows/linux/mac

By analyzing the blame information on this pull request, we identified @frantic and @chrisnager to be potential reviewers.

I'd be cool to do a simple navigator.userAgent check and show only the shortcut for the current platform. We can do a simple regex check.

@facebook-github-bot shipit

@mdamien updated the pull request - view changes

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.


[ISSUE #2300] Enhancement: Benchmark support acl and msg trace

What is the purpose of the change
Issue #2300
Brief changelog
1.add support for acl
2.add msgTraceEnabled option for producer and consumer
3.fix Algorithm HmacSHA1 not available using openjdk
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.07%) to 51.227% when pulling b31aa7403b5587cb406f50beb514eafa3c6cb4ba on maixiaohai:benchmark_support_acl_and_msg_trace into 2a8ba5a79935ab0a23646455427647ebd57d9e07 on apache:develop.


Tellstick duo sensors

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.51.2
Python release (python3 --version):
3.4
Component/platform:
Tellstick
Description of problem:
I have 2 sensors dht. When I restart it only shows one of 2 sensors and most time randomly. Using the cmd line tdtool -l I can see all switches and sensors but not appearing in homeassistant.
Has been working prior to 0.48 approximately. No code changes on my part and groups are set correctly
Expected:
All sensors (kitchen and living room) to be shown
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
Multiple other users on hass.io forum with same issue

Same problem here, 2 out of total 3 sensors appear. IF the third one shows up it is showing values out of range while tdtool is showing all sensors with reasonable values.
Worked fine in 0.54.2 and got wrong without any apparent changes.
Others reporting the same issue here: https://community.home-assistant.io/t/problems-with-sensors-over-433mhz-with-tellstick-duo/11208/2
Home Assistant release (hass --version): 0.55.2
Python release (python3 --version): 3.5.2
Component/platform: Tellstick

Looking at https://pypi.python.org/pypi/tellcore-py it seems like there is a newer version of tellcore available (1.1.3) while the current HASS version uses 1.1.2.
No idea if this solves the issue though.

Hi,
I have the same issue.
I'm running Ubuntu 16.04 with hass.io installed and the current version is 0.65.0.
When I reboot my server not all of my sensors is listed and when I try to restart the Tellstick configuration I can see this in the home-assistant.log file:
To get the sensors back I then have to restart the home-assistant server from Configuration-General-Restart
2018-03-10 19:53:17 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.utomhustemperaturen_temperature fails Traceback (most recent call last):   File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 204, in async_update_ha_state     yield from self.async_device_update()   File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 327, in async_device_update     yield from self.hass.async_add_job(self.update)   File "/usr/lib/python3.6/asyncio/futures.py", line 332, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup     future.result()   File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result     raise self._exception   File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/lib/python3.6/site-packages/homeassistant/components/sensor/tellstick.py", line 125, in update     self._value = self._tellcore_sensor.value(self._datatype).value   File "/usr/lib/python3.6/site-packages/tellcore/telldus.py", line 483, in value     self.protocol, self.model, self.id, datatype)   File "/usr/lib/python3.6/site-packages/tellcore/library.py", line 431, in tdSensorValue     value, sizeof(value), byref(timestamp))   File "/usr/lib/python3.6/site-packages/tellcore/library.py", line 257, in check_int_result     raise TelldusError(result) tellcore.library.TelldusError: The method you tried to use is not supported by the device (-4)

Im having exactly the same problem as the previous poster. Changed a lot recently though (migrated into docker etc) so wont be much help. I have a tellstick duo.
When i start the docker container none of the telldus sensors (or sometime one or two (have 7 in total in 3 hardware devices)) show up. If i follow @daniarv's advice and restart home-assistant internally all 7 sensors shows up.

Similar behaviour is reported here for KNX climate #15772
What i have found with my tellstick is that a couple of reboots and then it will appear, most likely due to that it has not yet received any value during startup of the host and while not having any persisted last known value upon startup of hass then the sensor will fail to initialise.
Not sure how to best solve this, if it can be done with only configuration?
One thought is to keep last known value for dht sensors that could be persistent upon reboots and when the sensor is sending new value it will be updated.
@balloob what is your thoughs on this?

@leebejeebee I'm no longer seeing this issue in latest versions of home-assistant, can you please confirm if you experience the problem?
Otherwise, please close the issue.

Thanks. Has been resolved for me

I started experiencing this issue a while back. I am currently on .90.2 and after a restart of hassio (which sometimes fail, and the last log entry is about "Configuring switch.tellstick" or something), the sensors don't show up. When doing a {"addon":"core_tellstick","input":{"function":"list-sensors"}} to list the sensors, they show up though. Is the restart problem related to the sensor issue, and is there something that can be done?
Result from the list-sensors
[Info] Read list-sensors /  [Info] TellStick list-sensors success -> type=sensor	protocol=fineoffset	model=temperaturehumidity	id=215	temperature=22.1	humidity=20	time=2019-03-29 10:27:48	age=37 type=sensor	protocol=fineoffset	model=temperaturehumidity	id=247	temperature=21.4	humidity=26	time=2019-03-29 10:28:02	age=23 type=sensor	protocol=fineoffset	model=temperature	id=231	temperature=11.6	time=2019-03-29 10:28:04	age=21


/data/system/maps/montlake.bin is missing or corrupt

hi, i got a problem trying to run the program, when I run it, the terminal show me this error ./data/system/maps/montlake.bin is missing or corrupt. what does it mean? how can I fix it ?

It means the version of the code and the version of the data are out-of-sync. Run git pull to make sure you have the latest code, and ./data/grab_minimal_seed_data.sh to get the latest data. https://github.com/dabreegster/abstreet/blob/master/docs/dev.md#getting-started has these steps.
I just tried a fresh install using these instructions and it worked for me. The scripts use relative paths, so make sure to run from the correct directories.

There's now a more powerful updater tool. https://github.com/dabreegster/abstreet/blob/master/docs/dev.md has new instructions. Please reopen if you're having issues. Thanks!


README: fix hyperlink

To the document "Known Limitations".

Codecov Report

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

@@           Coverage Diff           @@
##           master     #940   +/-   ##
=======================================
  Coverage   35.53%   35.53%
=======================================
  Files          58       58
  Lines        4016     4016
=======================================
  Hits         1427     1427
  Misses       2426     2426
  Partials      163      163

Continue to review full report at Codecov.

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

@glarrain Thanks for the contribution!
Could you sign CLA according to the process explained by the bot?
The change LGTM and I'll merge this once you signed it.

Hi @mumoshu. I already did it. It seems the robot caught it a while ago. Thanks

@glarrain Confirmed. Thanks again for the contribution!


v1.2 changelog does not merge entries with identical text

Link to problem area:
https://spec.matrix.org/v1.2/changelog/#client-server-api
Issue

Duplicate of https://github.com/matrix-org/matrix-doc/issues/3441
Only affects rendered changelog when using the fragments. After generation (like v1.2 in unstable), it's working off of the towncrier output


Update Less to latest version

Update of Less to support CSS min and max function: https://github.com/less/less.js/issues/3463

No longer relevant


cmd/compile: internal compiler error: not lowered: v22, StructMake0 STRUCT

What version of Go are you using (go version)?

$ go version
go version devel go1.18-f4cd001b57 Sat Aug 28 18:48:37 2021 +0000 linux/amd64

Does this issue reproduce with the latest release?
yes
What did you do?
Compiled this code:
package main

func main() {
	Fooer2[byte]()
}

type Fooer[T any] interface {
	Foo(p T)
}

type fooer1[T any] struct{}

func (fooer1[T]) Foo(T) {}

type fooer2[T any] struct {
	r []Fooer[T]
}

func (mr fooer2[T]) Foo(p T){
	mr.r[0] = fooer1[T]{}
	return
}

func Fooer2[T any]() Fooer[T] {
	return fooer2[T]{}
}

I see the following panic:
# github.com/rogpeppe/generic/bug-2021-08-29
<autogenerated>:1: internal compiler error: '(*fooer2[uint8]).Foo': not lowered: v22, StructMake0 STRUCT

goroutine 1 [running]:
runtime/debug.Stack()
	/home/rogpeppe/go-dev/src/runtime/debug/stack.go:24 +0x65
cmd/compile/internal/base.FatalfAt({0xc73500, 0x0}, {0xc00008d8e0, 0x8}, {0xc00042a860, 0x2, 0x2})
	/home/rogpeppe/go-dev/src/cmd/compile/internal/base/print.go:227 +0x154
cmd/compile/internal/base.Fatalf(...)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/base/print.go:196
cmd/compile/internal/ssagen.(*ssafn).Fatalf(0x8, {0x367b75b8, 0x7f4a}, {0xce9c12, 0x2}, {0xc0000727e0, 0x1, 0x5})
	/home/rogpeppe/go-dev/src/cmd/compile/internal/ssagen/ssa.go:7477 +0x17d
cmd/compile/internal/ssa.(*Func).Fatalf(0xc0004301c0, {0xce9c12, 0x2}, {0xc0000727e0, 0x1, 0x1})
	/home/rogpeppe/go-dev/src/cmd/compile/internal/ssa/func.go:773 +0x27f
cmd/compile/internal/ssa.checkLower(0xc0004301c0)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/ssa/lower.go:41 +0x409
cmd/compile/internal/ssa.Compile(0xc0004301c0)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/ssa/compile.go:96 +0x9e7
cmd/compile/internal/ssagen.buildssa(0xc00011ec60, 0x0)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/ssagen/ssa.go:584 +0x1e30
cmd/compile/internal/ssagen.Compile(0xc00011ec60, 0xc00042a6a0)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/ssagen/pgen.go:183 +0x4c
cmd/compile/internal/gc.compileFunctions.func4.1(0xc0000abb01)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/gc/compile.go:153 +0x3a
cmd/compile/internal/gc.compileFunctions.func2(0xc0000001a0)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/gc/compile.go:125 +0x1e
cmd/compile/internal/gc.compileFunctions.func4({0xc00042e2c0, 0x7, 0x8})
	/home/rogpeppe/go-dev/src/cmd/compile/internal/gc/compile.go:152 +0x53
cmd/compile/internal/gc.compileFunctions()
	/home/rogpeppe/go-dev/src/cmd/compile/internal/gc/compile.go:163 +0x162
cmd/compile/internal/gc.Main(0xd21740)
	/home/rogpeppe/go-dev/src/cmd/compile/internal/gc/main.go:302 +0xfb6
main.main()
	/home/rogpeppe/go-dev/src/cmd/compile/main.go:55 +0xdd

@griesemer @ianlancetaylor

This appears to work with GOEXPERIMENT=unified.

I am curious, is GOEXPERIMENT=unified planned for 1.18?

@scott-cotton Let's not speculate on implementation approach and schedule. But in the interest of the best possible user experience it seems reasonable (to me) to select the most stable and feature-complete implementation approach when the time comes, whichever that is. Thanks.

@randall77 Do you want to take a look.  I don't immediately know why the lowering is not happening properly.    If you add //go:noinline in front of method "mr fooer2[T]) Foo(p T)", then it seems easier to debug, since then the error occurs on that function (the instantiation 'fooer2[.shape.uint8].Foo'), rather than on a wrapper (which inlines that method)
The problem seems to be with the STRUCTLIT in that function - somehow the final lowering is not happening.  It could possibly be related to the fact that the type of the STRUCTLIT is a shape type (e.g. fooer1[.shape.uint8] ), but I haven't look far enough into the SSA code.

@randall77 @danscales While investigating this, I notice that:
GOSSAFUNC='fooer2[.shape.uint8].Foo' go tool compile p.go

produce ssa.html with no source code in the sources section.:

sources   main.go
--

Unified IR can properly show:

sources  20212223 /Users/cuonglm/main.gofunc (mr fooer2[T]) Foo(p T){	mr.r[0] = fooer1[T]{}	return}
--

There is a missing OCONVIFACE. This assignment:
	mr.r[0] = fooer1[T]{}

Implicitly converts the concrete type on the RHS to an interface type on the LHS.
The immediate problem is easy, in stencil.go:929, we need to assign the results of lhs[0] and rhs[0] back to as.X and as.Y. (The OCONVIFACE is made in transformAssign, we just lose it by not assigning back to the source.)
But then we end up with a OCONVIFACE introduced late, too late to convert the OCONVIFACE to using the dictionary. Have to think a bit more about how to make that work.


fix: Append all credentials for OpenAPI security infos

When using an OpenAPI definition with multiple security infos that should be AND'd together (per https://docs.gptscript.ai/tools/openapi#1-security-schemes), the tools credential injection with only include 1 of the environment variables instead of all of them. The result is non-deterministic on which envvar will be included to do Go's behavior with slices.
This changes the behavior to include credential injections for all schemes declared in the 1st security info block in the api definition.

Tried to add tests for this, but the current openApi loading tests don't handle tool linking and wasn't quite sure how to set that up in the test fixture. Got an error like so -
failed linking listPets at : failed resolving github.com/gptscript-ai/credential as petstore.swagger.iobearerAuth with GPTSCRIPT_PETSTORE_SWAGGER_IO_BEARERAUTH as env and "Please provide a value for the GPTSCRIPT_PETSTORE_SWAGGER_IO_BEARERAUTH environment variable" as message and "bearer token" as field from : can not load tools path= name=github.com/gptscript-ai/credential

Hey @johnrengelman , thanks for the contribution. Sorry it took me so long to get to this. It looks good to me but the linter is failing. If you could apply the suggestion I left, then I can merge this. Thanks!

Pushed this change from the linter.
I tried to look into the openai_revamp implementation to see if this same problem exists, but I wasn't able to follow where the credential envvars are injected in that (the tools are built up differently).

Pushed this change from the linter.
I tried to look into the openai_revamp implementation to see if this same problem exists, but I wasn't able to follow where the credential envvars are injected in that (the tools are built up differently).

Yeah I think we are planning on removing that. That was mostly just an experiment, which is why it is hidden behind an env var. So no worries. Thanks again for your contribution!


Check for invalid device ID before query

Description
Check for invalid device ID before query.
Fixes THEEDGE-1617
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I run go fmt ./... to check that my code is properly formatted
[x] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #615 (04a5a93) into main (d1a2fbe) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #615   +/-   ##
=======================================
  Coverage   31.28%   31.28%
=======================================
  Files          37       37
  Lines        3829     3829
=======================================
  Hits         1198     1198
  Misses       2466     2466
  Partials      165      165

Continue to review full report at Codecov.

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


replaceVars: allow exemptions

replaceVars has a checkPhase to confirm that no left-over @...@ patterns remain. Since it's not possible to use "placeholder" with replaceVars, the substitution of some patterns must be delayed to a later step.
By passing "false" for those keys explicitly, replaceVars can make an exemption just for this case, but keep checking all other references.
This replaces the approach taken in #339303. @philiptaron

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I like it.

I like the idea, but I don’t love false here, semantically. (What would true be?)
I would prefer null or perhaps an explicit placeholder value, if those are options.
(Or, semi‐serious straw proposal: foo = "@foo@"; would “naturally” have the semantics we want…)

I'm fine with either false or null as a sentinel value, and if @emilazy prefers null, that tips the scales.
The argument in favor of false is that it's much less commonly used in package argument lists, so inherit foo is less likely to pass it through.
Consider:
{ lib, stdenv, dep, optionalDep ? null }:

...
   (replaceVars ./patch { inherit dep optionalDep; })

It's kind of a weak argument, and if we adopt a sentinel-based approach at all, null is a fine thing to settle on.
I originally used builtins.toString on the values passed in, and was guided out of that decision -- and very glad of it now, since true, false, null, and many other values aren't stringified but rather raise evaluation errors.
As @wolfgangwalther points out, "@foo@" isn't a good sentinel because it looks like any other string value, and hence would take substantially more logic to avoid. While it could be done, it would up the "magic factor" of the replaceVars expressions, and so I think we should not do it.
The really rogue sentinel value option is replaceVars itself.
replaceVars ./something { foo = replaceVars; }

There's some language that advocates against well-known sentinels in favor of these bespoke, qunine-ish beasts, but it's slipping my mind at the moment. I prefer null on familiarity grounds.

FWIW, I believe the logic i had in mind could be implemented by dropping the conditional on subst-var-by here, and something like: instead of matching on @name@ explicitly in lookahead, simply include all replacement values in left-overs. That could handle @wolfgangwalther’s examples and it might actually be simpler, implementation‐wise. (I think the regex there doesn’t quite work out, but you get the concept.)
However I agree it’s sort of weird. I like null, in this context (not in general!). I definitely don’t like anything that uses equality on functions.
My one remaining counterproposal is just replaceVarsWith { ignore = ["out"]; } { … }, which avoids all in‐band signalling. I would be fine with both null and that.

I suppose that is true if you accept replaceVars and replaceVarsWith { } being different. This would result in people nitpicking replaceVars into being essentially deprecated, or introducing replaceVars2 = replaceVarsWith { }, though. Anyway, I don’t know if null will be a meaningful problem here in practice, so I’m happy to proceed with this version.


Current make watch target fails to find air even after successful installation

Description
When running make watch after successfully installing air, the Makefile still prompts "air is not installed. Do you want to install it now? (y/n)". This happens even though air has been installed and is available in the PATH.
It seems like the GOPATH has been deprecated in Go 1.16 and should not be relied on.
Environment

Go version: 1.21.0
OS: Ubuntu 22.04

Additional Information
Here is the watch target in the Makefile:
watch:
	@if [ -x "$(GOPATH)/bin/air" ]; then \
	    "$(GOPATH)/bin/air"; \
		@echo "Watching...";\
	else \
	    read -p "air is not installed. Do you want to install it now? (y/n) " choice; \
	    if [ "$$choice" = "y" ]; then \
			go install github.com/cosmtrek/air@latest; \
	        "$(GOPATH)/bin/air"; \
				@echo "Watching...";\
	    else \
	        echo "You chose not to install air. Exiting..."; \
	        exit 1; \
	    fi; \
	fi

$GOPATH itself is not deprecated, what this was doing was fine. https://blog.smantic.dev/posts/gopath-is-not-deprecated/
What is deprecated is using $GOPATH as the workspace for go projects. This was typically where you developed go codebases before go modules.
read -p "Go's 'air' is not installed on your machine. Do you want to install it? [Y/n] " choice; \
	    if [ "$$choice" != "n" ] && [ "$$choice" != "N" ]; then \
	        go install github.com/cosmtrek/air@latest; \
	        air; \
	        echo "Watching...";\

This still assumes that the user has added $GOBIN ($GOPATH/bin) to the user's path. This isnt a thing that happens automatically. The previous implementation did not assume that the user had $GOBIN in their path.

Yess @smantic, the description of the issue is indeed wrong, thanks for pointing it out.
My experience (and from issue #111 apparently) was that the previous implementation ran on every run of make watch. So it would install air on the system but not detect the installation afterward. Then I think neither the previous implementation should be relied upon.
I'm currious to see if people will have issues with the new implementation as you said that. I will take look into what could solution could be taken to make this as more generalized (work on more machines) as possible.

Hi @andrerocco
I'm using the latest versions of both go and go-blueprint. but i'm still facing this problem of air: not found. Below is the watch target:
# Live Reload
watch:
	@if command -v air > /dev/null; then \
		air; \
		echo "Watching...";\
	else \
		read -p "Go's 'air' is not installed on your machine. Do you want to install it? [Y/n] " choice; \
		if [ "$$choice" != "n" ] && [ "$$choice" != "N" ]; then \
			go install github.com/air-verse/air@latest; \
			air; \
			echo "Watching...";\
		else \
			echo "You chose not to install air. Exiting..."; \
			exit 1; \
		fi; \
	fi

i also tried this:
watch:
  @echo "Watching..."
  @air -v

but that also didn't do any help. any idea what i'm doing wrong here?
note: i can successfully access the air command from terminal directly. this problem only occurs when i do it using the makefile


Updated node removals docs for clarity and correctness, overuse warning

There were several outdated items in the Node Removal guidelines. Fixed those, and hopefully made the section more clear - trying to make the node removal API more usable while discouraging overuse.

Are there docs describing the options?
On Fri, Nov 8, 2024, 15:58 Shawn Rushefsky @.***> wrote:

@.**** commented on this pull request.
In products/sgs/node-removals.mdx
https://github.com/SaladTechnologies/salad-cloud-docs/pull/106#discussion_r1834539300
:

-## Example Request
+## Example request
+
+```Curl.sh
I think this should just be "shell" or "bash" to get the right highlighting
—
Reply to this email directly, view it on GitHub
https://github.com/SaladTechnologies/salad-cloud-docs/pull/106#pullrequestreview-2424030321,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATAG2PGFCOSRK5RRU6ONEHLZ7TGTBAVCNFSM6AAAAABRNHQZI2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMRUGAZTAMZSGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@shawnrushefsky addressed your comment above. List of languages supported is visible here for future reference.


testing: "There is no current event loop in thread 'MainThread'."

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
I have several modules with unit-tests:
test_sum.py
import pytest
from httpx import AsyncClient

pytestmark = pytest.mark.anyio

async def test_sum(app):
    async with AsyncClient(app=app, base_url='http://<IP_ADDRESS>:5000') as ac:
        response = await ac.post('/v1/sum', json={"x": 4, "y": 6})

    assert response.status_code == 200
    assert response.json() == {"sum": 10}

test_items.py
from tests.expected_data import created_item
from tests.moks_data import items

pytestmark = pytest.mark.anyio

async def test_create_item(app):
    async with AsyncClient(app=app, base_url='http://test') as ac:
        response = await ac.post('/v1/items', json={
            "name": "TestName",
            "description": "Test description",
            "price": 100
        })

    assert response.status_code == 200
    assert response.json() == created_item

async def test_get_item(fill_db, app):
    async with AsyncClient(app=app, base_url='http://test') as ac:
        response = await ac.get('/v1/items/2')

    assert response.status_code == 200
    assert response.json() == items[1]

conftest.py
import pytest
from alembic.command import downgrade, upgrade
from alembic.config import Config as AlembicConfig

from core.app.web import create_app
from core.data.postgres.engine import session_scope
from core.data.postgres.models import Base, Item
from tests.moks_data import items

@pytest.fixture
def app():
    app_instance = create_app()
    return app_instance

@pytest.fixture(scope='session')
def db_session():
    config = AlembicConfig('alembic.ini')
    config.attributes['configure_logger'] = False

    upgrade(config, 'head')

    yield 'on head'

    downgrade(config, 'base')

@pytest.fixture(autouse=True)
async def clear_data(db_session):
    yield 'I will clear tables for you'

    reference_value_tables = [f'{name}' for name in ('role',)]

    async with session_scope() as session:
        for name, table in Base.metadata.tables.items():
            if name not in reference_value_tables:
                await session.execute(table.delete())

@pytest.fixture
async def fill_db(event_loop):
    items_list = [Item(**item) for item in items]
    async with session_scope() as session:
        session.add_all(items_list)
        await session.flush()

Description
I'm using:
python 3.10.1,
fastapi 0.72.0,
pytest 6.2.5,
pytest-trio 0.7.0,
sqlalchemy 1.4.31,
alembic 1.7.5,
asyncpg 0.25.0,
postgresql 14.1.**
Now, i have issue when i try to execute my tests.
When i run my tests - tests in test_sum is successfully ended but tests in test_items is failed with error:
There is no current event loop in thread 'MainThread'.
Please tell me what I'm doing wrong and how to solve this problem?
Operating System
Linux
Operating System Details
manjaro linux 21.2.1
FastAPI Version
0.72.0
Python Version
3.10.1
Additional Context
tests work correctly with fastapi <= 0.68

Your formatting makes things hard to read.
Is there a reason you are avoiding the use of the decorator that starts a loop for you?

Specifically I meant @pytest.mark.anyio
You can see it in use here https://fastapi.tiangolo.com/advanced/async-tests/
However now I see you are using the pytestmark = pytest.mark.anyio method
Anyway test_sum.py probably passes because you are not using the async fixtures in conftest.py
In test_items.py you are using fill_db which is in conftest.py but you are not starting a loop in conftest (no pytestmark = pytest.mark.anyio in there)
Maybe try adding that to conf_test or wrapping the fill_db and clear_data in @pytest.mark.anyio so that fixture has a loop to use.

I encountered this when writing my tests as asynchronous tests (async def test_xyz) with asyncpg and pytest-asyncio.
I found an alternate solution by opting for regular def test_xyz tests and removing any class wrapper! (Which is what broke regular tests for me). While this doesn't resolve being able to run async code in tests, I was able to test my endpoints this way.


Use groups to contain dependabot updates into group PRs

Ticket(s)

11842

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Description
Updates the dependabot.yml with further consideration of our actual needs from dependabot. Using groups, dependabot will open one pull request on behalf of all dependencies in that group. I separated them into prod dependencies and dev dependencies, and allow for only major and minor update types, omitting patch. I further ignored all major version updates specifically for next, since we want to control when that happens separately.
Overall PR Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have filled this PR out fully, and cleaned up any extraneous items so that it is clear and easy to understand

@e-papanicolas looks good!


Update develop-client-apps.md

Added two words that were missing in the top paragraph.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@rpetrusha I made the changes we agreed on. I'm not sure how to resolve the "changes requested" blocker. Maybe you can? Thanks for your help.

@gewarren, "changes requested" is removed either when the person who requested changes approves them or dismisses the review, or when someone else with the necessary permissions dismisses the review that requests changes. This looks good, so I'll approve and merge.

Thanks Ron!


Nice feature the icon

https://github.com/Jelmerovereem/web-app-from-scratch-2021/blob/448ef1cfb69ff24052dc7728dc1801726ab848b3/scripts/modules/renderToMap.js#L10

Thank you! 😄


cert-manager is failing when using this example

# flux get helmrelease cert-manager -n cert-manager
NAME        	REVISION	SUSPENDED	READY	MESSAGE
cert-manager	v1.15.0 	False    	False	Helm install failed for release cert-manager/cert-manager with chart<EMAIL_ADDRESS>Unable to continue with install: CustomResourceDefinition "certificaterequests.cert-manager.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "cert-manager"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "cert-manager"

The error message is telling you that the cert-manager CRDs have been deployed in the cluster by other means. You need to delete them with kubectl delete crd <all-cert-manager-crds>.

Thanks, @stefanprodan  - yeah found it. All fine now!


Documentation page not found

This link redirects to this link with this content:
Whoops, looks like something went wrong.
I need that, please fix it.

@themsaid please can you fix the doc link we need it

@himan72 for generate markdown you can run.
php katana build

and start the server
gulp watch

what is your problem?


Remove BOXContentSDK.h from header files

Verified that @jpang1 has signed the CLA. Thanks for the pull request!

Closing due to different approach wanted. Should not require developers to import the Content SDK separately if using the Browse SDK.


Test guillotine 6 app compliance

There is a problem with headers being sent in lowercase described here https://github.com/enonic/app-guillotine/issues/247
Otherwise works fine


fix(datepicker): add wrapper div

Add wrapper div to guard against angular 1.3 ngAnimate bug

This fix is thanks to @moonboyio
Fixes #4012 and #4174.

This looks like an incorrect fix here.


[MM-18958] Migrate components/get_android_app to TypeScript

Summary

This migrates components/get_android_app to TypeScript.
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/12469
Related Pull Requests
N/A

Corresponding JIRA tickets for these have already been designated "No testing required" for QA, so no QA needed on the PR; removing label.

Merged! thanks @kgeorgiou! :dancer:


Test Lightsheet workflow from UFL

The workflow seems to work properly, but the current output image pyramid data shows quantization issues.  It looks like the Zeiss .czi file (included in the upload) stores its image as UInt16, but the ome.tiff file has a UInt8 image.  This implies that some error was made in translation from the .czi to the .ome.tiff .  My understanding is that that translation was done using the Zeiss Zen (black) software, circa 2014.  This issue should not be closed until a correctly translated dataset is passed through the pipeline.  See https://github.com/hubmapconsortium/ingest-pipeline/issues/348


snakemake conda issue

Waiting for this issue to be merged in snakemake. Until then, I corrected the file manually:
https://github.com/snakemake/snakemake/issues/1674

fixed

Hello, how to fix it ?


[BUG] can not support PLAINTEXT and SASL_PLAINTEXT both

Describe the bug
can not support PLAINTEXT and SASL_PLAINTEXT both. The client connected to 19092 with Protocol SASL_PLAINTEXT Successfully，but can not connect to 9092 with Protocol PLAINTEXT

Kafka Client: 2.8.0
Pulsar: 2.10.1
KoP: <IP_ADDRESS>

log:
2022-07-19T16:30:20,234+0800 [pulsar-ph-kafka-93-23] INFO  io.streamnative.pulsar.handlers.kop.KafkaRequestHandler - channel active: [id: 0xc1609c28, L:/<IP_ADDRESS>:9092 - R:/<IP_ADDRESS>:51522]
2022-07-19T16:30:20,237+0800 [pulsar-ph-kafka-93-23] ERROR io.streamnative.pulsar.handlers.kop.KafkaCommandDecoder - Failed authentication with [/<IP_ADDRESS>:51522] (Unexpected Kafka request of type METADATA during SASL handshake.)
2022-07-19T16:30:20,538+0800 [pulsar-ph-kafka-93-23] INFO  io.streamnative.pulsar.handlers.kop.KafkaCommandDecoder - close channel [id: 0xc1609c28, L:/<IP_ADDRESS>:9092 - R:/<IP_ADDRESS>:51522] with 0 pending responses
2022-07-19T16:30:20,642+0800 [pulsar-ph-kafka-93-24] INFO  io.streamnative.pulsar.handlers.kop.KafkaRequestHandler - channel active: [id: 0x6c8d8e20, L:/<IP_ADDRESS>:9092 - R:/<IP_ADDRESS>:51525]
2022-07-19T16:30:20,647+0800 [pulsar-ph-kafka-93-24] ERROR io.streamnative.pulsar.handlers.kop.KafkaCommandDecoder - Failed authentication with [/<IP_ADDRESS>:51525] (Unexpected Kafka request of type METADATA during SASL handshake.)
2022-07-19T16:30:20,947+0800 [pulsar-ph-kafka-93-24] INFO  io.streamnative.pulsar.handlers.kop.KafkaCommandDecoder - close channel [id: 0x6c8d8e20, L:/<IP_ADDRESS>:9092 - R:/<IP_ADDRESS>:51525] with 0 pending responses
2022-07-19T16:30:21,052+0800 [pulsar-ph-kafka-93-25] INFO  io.streamnative.pulsar.handlers.kop.KafkaRequestHandler - channel active: [id: 0xa74aeed6, L:/<IP_ADDRESS>:9092 - R:/<IP_ADDRESS>:51526]
2022-07-19T16:30:21,055+0800 [pulsar-ph-kafka-93-25] ERROR io.streamnative.pulsar.handlers.kop.KafkaCommandDecoder - Failed authentication with [/<IP_ADDRESS>:51526] (Unexpected Kafka request of type METADATA during SASL handshake.)
2022-07-19T16:30:21,355+0800 [pulsar-ph-kafka-93-25] INFO  io.streamnative.pulsar.handlers.kop.KafkaCommandDecoder - close channel [id: 0xa74aeed6, L:/<IP_ADDRESS>:9092 - R:/<IP_ADDRESS>:51526] with 0 pending responses

KoP configs:
kafkaListeners=kafka_internal://<IP_ADDRESS>:9092,kafka_external://<IP_ADDRESS>:19092
kafkaProtocolMap=kafka_internal:PLAINTEXT,kafka_external:SASL_PLAINTEXT,PLAINTEXT:PLAINTEXT
kafkaAdvertisedListeners=kafka_internal://<IP_ADDRESS>:9092,kafka_external://<IP_ADDRESS>:19092
entryFormat=kafka
defaultNumPartitions=6
saslAllowedMechanisms=PLAIN
allowAutoTopicCreationType=partitioned

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
support Protocol PLAINTEXT and SASL_PLAINTEXT both.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

what's your use case ?
if you enable SASL you want to protect your cluster, it doesn't make sense to allow non authenticated users

@eolivelli internal users connect to the cluster by internal_ip:9092，external users connect to the cluster by external_ip:19092.
internal users can be trusted
kafkaAdvertisedListeners=kafka_internal://internal_ip:9092,kafka_external://external_ip:19092

You should configure the authentication when you connected to the 9092 port. Currently there is no difference between PLAINTEXT and SASL_PLAINTEXT in KoP.

The multi-listener feature is usually used when your KoP needs to expose multiple listeners, e.g. if the KoP is running inside a docker, it must expose:

An IP within the docker network for other KoP nodes or the Kafka clients inside the docker network.
A public IP that is accessible to clients outside the docker network

Thanks @BewareMyPower


Tutorial --> Build Web Application and Build Console Apllication

In Tutorial --> Build Web Application  has  a Create .NET console application example, and Build Console Application  has  a Create ASP.NET web application example
Ref: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/tutorial-dotnet-web-app#create-aspnet-web-application
Ref: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/tutorial-dotnet-console-app#create-net-console-application
[Enter feedback here]

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

ID: af90dbc6-bff5-0f9a-7969-ac94b0352987
Version Independent ID: ec5de32b-ad0a-be2f-144f-6376ca55ccd9
Content: Tutorial: Develop a .NET console application with Azure Cosmos DB for NoSQL

Content Source: articles/cosmos-db/nosql/tutorial-dotnet-console-app.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

@Gauravjain449 Thanks for your findings, I'm assigning this to the author for the feedback review.

Thanks @Gauravjain449 for spotting this error. These are two brand new articles that were released together.
The fix for this should be live later today


Version change from 13.0.1 to 13.0.2

Changes

[x] Changed package version to 13.0.2.

Notes
There is an issue with NPM registry so we would try to publish another patch version.
Regards.

Codecov Report

Merging #186 (2cbdc18) into master (036a19b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #186   +/-   ##
=======================================
  Coverage   91.19%   91.19%
=======================================
  Files         266      266
  Lines        6363     6363
  Branches     1257     1257
=======================================
  Hits         5803     5803
  Misses        306      306
  Partials      254      254

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


docs: append file extension in Crowdin config to avoid conflict

Crowdin fails to synchronize when a path contains multiple file types.
As an example, _category_.json and markdown.md in the same directory will output an error and stop the synchronization process.
It has to be excluded, regardless, I am unable to find a clear statement in the Crowdin documentation on this specific case. I tested it with my project as this was the reason for the failure.
References
https://support.crowdin.com/configuration-file/#general-configuration
https://support.crowdin.com/configuration-file/#usage-of-wildcards

Motivation

Have my own Docusaurus websites so it is reasonable to fix issues and propose changes along the way.
Have you read the Contributing Guidelines on pull requests?

[x] Yes

Test Plan

Minor change which has been tested on my own project.
Related PRs

Not sure if this is necessary. Our website uses the same configuration without explicit extensions, and it works well, since the deploy logs suggest that _category_.json, etc. are being synced.
Have you contacted Crowdin support, or have some kind of documentation to back up this change?

Just tried to reproduce it. It appears that if files are already synchronized or manually added the synchronization is not affected. However, if file types missing and start fresh synchronization. it fails:
Incorrect files flagged as soon as file type removed.

To be sure, I set up fresh:

crowdin.json

project_id_env: PROJECT_ID
api_token_env: ZI_CROWDIN_TOKEN
base_url: 'https://digitalclouds.crowdin.com'
commit_message: '[ci skip]'
preserve_hierarchy: true
files:
  # JSON translation files
  - source: /i18n/en/**/*
    translation: /i18n/%two_letters_code%/**/%original_file_name%
  # Docs Markdown files
  - source: /docs/**/*
    translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%
  # Blog Markdown files
  - source: /blog/**/*
    translation: /i18n/%two_letters_code%/docusaurus-plugin-content-blog/**/%original_file_name%

While sync is still in progress received the email

Then message in the Crowdin UI

And notification about the issue

The issue can be solved as this PR propose.
Reviewed Crowdin Knowledge Base (links previously added to this PR.) which shows techniques that manage files excluding/including files types or appending it. Seems obvious so not contacted Crowdin support.

Our website uses the same configuration

Is the website environment tested, fresh, docker, etc.? That could be the reason why not noticed.
:octocat:
Regards,
@ss-o

As previously mentioned, it seems that if files persist on Crowdin then sync is not affected. I fully agree that it is not necessary for your website as it is not going to be affected. But those who start a new environment with Crowdin might.
Should I close PR?
Thanks,

It could be useful, just not sure if it would mean some files are accidentally not synced. I'll leave it to @slorber who's probably more experienced with Crowdin than I am.

I checked multiple times and could not pinpoint the exact failure. Leaving as is.
Thanks for the replay.

I can't tell exactly why you are running into errors, but we definitively want to use a wildcard without extension.
Remember that the docs folder might co-locate assets alongside the md files. (such as images that you use in the docs).
If that's the case, you should be able to translate those assets on Crowdin too (ie provide localized images on which text is translated)
We also have a folder of assets on our own docs: https://github.com/facebook/docusaurus/tree/main/website/docs/assets and translated sites would stop working if we stop uploading/downloading it.
I definitively think it makes sense to recommend * by default, and power users will read the Crowdin docs and adjust the settings to their own needs. If Crowdin refuses to upload files with * that looks like a Crowdin bug that they should fix.

Crowdin fails to synchronize

You say it fails but I don't understand what it means exactly. Is there an error message anywhere?
We can't prevent Crowdin to have bugs in their CLI or API, so it's always good to get in touch with them directly

I'm going to close but we can continue the discussion.