Improve the handling of stringified annotations in _takes_container

Summary

Pull Request Check List

[x] Typos aside (please, always submit typo fixes!), I understand that this pull request may be closed in case there was no previous discussion.
[x] Do not open pull requests from your main branch – use a separate branch!

There's a ton of footguns waiting if you don't heed this warning. You can still go back to your project, create a branch from your main branch, push it, and open the pull request from the new branch.
This is not a pre-requisite for your your pull request to be accepted, but you have been warned.

[x] Added tests for changed code.

The CI fails with less than 100% coverage.

[ ] New APIs are added to our typing tests at https://github.com/hynek/svcs/blob/main/tests/typing/.
[ ] Updated documentation for changed code.

[ ] New functions/classes have to be added to docs/core-concepts.md or one of the integration guides by hand.
[ ] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.

The next version is the second number in the current release + 1. The first number represents the current year. So if the current version on PyPI is 23.1.0, the next version is gonna be 23.2.0. If the next version is the first in the new year, it'll be 24.1.0.

[ ] Documentation in .rst and .md files is written using semantic newlines.
[ ] Changes (and possible deprecations) are documented in the changelog.
[ ] Consider granting push permissions to the PR branch, so maintainers can fix minor issues themselves without pestering you.

This should work in all the cases that are included in the tests, but it will still fail in the following case:
from __future__ import annotations

from svcs import Container as ServiceContainer

def get_service(container: ServiceContainer) -> None:
    ...

This can be handled, but we would have to add something like this to the Registry and then pass in that signature namespace mapping to _takes_container which would then pass it to the locals of inspect.signature.
Please let me know if there are any changes that needs to be made and I'd be happy to do so :)
NOTE: I haven't updated the changelog yet.

OK 3.8 & 3.9 are failing again – but you're not even using get_type_hints? :|

I should have read the documentation in more detail :P eval_str was introduced only in 3.10 :/
Maybe instead of signature, we should use get_type_hints to get the annotations from the function.

OK 3.8 & 3.9 are failing again – but you're not even using get_type_hints? :|

I should have read the documentation in more detail :P eval_str was introduced only in 3.10 :/

FWIW, I'm OK if you write two versions hidden behind a huge if sys.version block.

Maybe instead of signature, we should use get_type_hints to get the annotations from the function.

Yes, but as you'll notice, it's a bit more complicated that it looks like. 🤓 Because I've tried cobbling something together and your PR was so fast I gave up on it.

OK 3.8 & 3.9 are failing again – but you're not even using get_type_hints? :|

I should have read the documentation in more detail :P eval_str was introduced only in 3.10 :/

FWIW, I'm OK if you write two versions hidden behind a huge if sys.version block.

Maybe instead of signature, we should use get_type_hints to get the annotations from the function.

Yes, but as you'll notice, it's a bit more complicated that it looks like. 🤓 Because I've tried cobbling something together and your PR was so fast I gave up on it.

Yeah, this is quite frustrating actually. If the factory functions are annotated, then we can use the get_type_hints route, but if they aren't then we have to go through the inspect.signature route to handle cases where the first argument is name svcs_container.

I have a doubt. The factories are only supposed to take zero or one argument and if it takes in an argument, it has to be the container correct?
If this is the case, can't we just return len(sig.parameters) == 1 instead of having to deal with all this typing related stuff?

hmmm the reason I'm strict with this is that I want to keep the option of adding more arguments down the road.

Technically it should error out, not return False. 🤔

Like one example of what I maybe want to do in the future is allowing passing arguments to factories (x = svcs.get(X, foo="bar") call's X's factory like factory(kwargs={"foo": "bar"})).

Like one example of what I maybe want to do in the future is allowing passing arguments to factories (x = svcs.get(X, foo="bar") call's X's factory like factory(kwargs={"foo": "bar"})).

This is really nice. Okay then here's another idea. What if you place the following constraints:

factories can only have one positional argument at most and if there is one, then it must be the container
all other arguments must be keywords

Hmm, why would we enforce that tho? Like: what problem are we solving right now?
I find it nicer to say to users of at least 3 years old Pythons that their accuracy of container detection is a bit lower (for comparison: both attrs and data classes check for ClassVar using string compare to avoid importing typing) than enforcing new rules on everybody.
Or am I missing something?

Hmm, why would we enforce that tho? Like: what problem are we solving right now?
I find it nicer to say to users of at least 3 years old Pythons that their accuracy of container detection is a bit lower (for comparison: both attrs and data classes check for ClassVar using string compare to avoid importing typing) than enforcing new rules on everybody.
Or am I missing something?

The current way of comparing the strings wouldn't work if a user aliases Container to something (like the example I have given in the description of the PR). With the constraint I proposed, there would be no issues related to typing nor any issues related to the aliasing etc.

Agreed, but I'm fine to say "no aliasing pre-3.10" and let everyone use factory(*, s: [svcs.]Container). I find that is a reasonable compromise – especially given that svcs is a young project and the cumulative 3.8+3.9 downloads are sub 3%.

Agreed, but I'm fine to say "no aliasing pre-3.10" and let everyone use factory(*, s: [svcs.]Container). I find that is a reasonable compromise – especially given that svcs is a young project and the cumulative 3.8+3.9 downloads are sub 3%.

Yes, but unfortunately aliasing will not work if it's under a TYPE_CHECKING block regardless of the Python version. For example:
from __future__ import annotations

from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from svcs import Container as ServiceContainer

def get_service(container: ServiceContainer) -> Service:
    ...

The reason I feel it would be nice to support this scenario is because it's a common pattern now and linters like ruff will move these types automatically into the TYPE_CHECKING block even if the user places them outside it (of course, you can disable that).
Of course, you could just document all these edge cases/caveats and tell users to not alias within a TYPE_CHECKING block. Adding the constraints I proposed would make things bit inflexible for change in the future without breaking changes, so it's completely reasonable to go with the approach of documenting these caveats.

Yeah TYPE_CHECKING comes with tons of caveats which is why I've stopped using it unless I have to for breaking import cycles. Eg autodoc also completely falls apart.
Since we're generally agreeing, what would you suggest concretely?

My suggestion is the following:

use the implementation of _takes_container in this PR for Python 3.10+ and use the old implementation for older versions (with an extra string comparison for "Container")
document the different scenarios in which the user will face issues

I agree with points 1 and 2 and I think that's the only ones relevant to this PR. If you want to do only the first point, that would be already above and beyond too!

I'll update the PR accordingly. I'll try to write the documentation, but if it's something you'd like to do yourself then just let me know :)
Also, regarding the 3rd point, maybe "recommend" isn't the right word. I felt it would be nice if the docs mentioned that this is a workaround in case they have some limitation they're facing with respect to the typing and the containers not being injected into their factory functions. I was facing this issue and it took me some time to figure out that the easiest workaround was to just name my parameter svcs_container.

Yeah I'll add something like that – don't worry about it and just fix what's breaking you. :)

@hynek I think it's ready for another review. The tests are passing for me on both 3.8 and 3.9 locally.
Also, we don't need to have different implementations based on the version since if there's some exception then it falls back to using only inspect.signature(factory) without the use of eval_str or anything.


Add command line argument parser to set the port

Done here https://github.com/sebastianconcept/memoizer/pull/5


ipvs proxy share util funcs with iptables proxy

What this PR does / why we need it:

fix session affinity timeout bug

fix node ipv6

move some basic funcs into pkg/proxy/util so that ipvs proxy can share util funcs with iptables proxy.

@dhilipkumars PTAL.

Roughly the code looks okay, i think this is a good improvement to the code proxier.go has shed close to 700 LOC.
The same will happen to iptable's proxier.go too.
I believe if we did not do this refactoring the community would have asked us to do this anyways.
I will merge this code for ease of testing.  We should have more people looking at this in a couple of days.


Explore Hive with SSL

Affected module
Ingestion Framework
Describe the bug
we use pyhive to load the metadata from hive source. It does not seem to do a great job when there is a hive server with ssl enable, explore the pyhive alternatives or explore steps to configure pyhive with ssl.

As of this regards we had the same problem of connecting to hive with ssl and kerberos authentication.
The fix that we tested to use pyhive for the connection was to pass a custom thrift_trasport object to hive.Connection , configured with TSSLSocket. This worked.
You could add a specific hive+ssl option on the connection scheme drop in the "Edit Service Connection" page so that, if choosen,  you could construct this object and pass it to the pyhive connection constructor to make it work for ssl too.
...
socket = thrift.transport.TSSLSocket.TSSLSocket(host, port, cert_reqs=CERT_NONE)
thrift_transport = thrift_sasl.TSaslClientTransport(sasl_factory, sasl_auth, socket)

However it would be nice if you could also explore using impayla as a connection library in alternave to pyhive to cover also http and https as per #7793
Impayla covers hive and impala too and has a SqlAlchemy connector and its back by Cloudera.
You might also think about how to approach passing a custom ssl certificate for client validation too, or toggling the validation on/off.

can this be solved by impalya driver cc @ulixius9

Yes closing by https://github.com/open-metadata/OpenMetadata/pull/10270


Removal of aws sdk breaks retrieval of instance metadata when using IMDSv2

Bug Description
The removal of the aws sdk in favour of simple http requests to the metadata endpoint in PR https://github.com/istio/istio/pull/37873 breaks functionality as it does not authenticate with the APIs as per docs: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html
The removal of the aws sdk for use in this call removed the automatic compatibility with this (and other) mechanisms of authenticating against aws APIs. Whilst fixing the auth issue will solve this initially, why is this problem being solved at all? The sdk will simply adapt to work whatever changes aws make in the future (as well as being able to make use of IRSA: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html)
Version
Anything with https://github.com/istio/istio/pull/37873

Additional Information
No response

This remains an issue. Whether the service manages the auth flow itself, or via the sdk, istio cannot get metadata from IMDSv2 currently, see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html for details on what flow would be required.


Make eprintf-calling functions easier to test

As of today there is no unified interface for mock error values - functions can either return NULL or (in case of value-returning functions), arbitrary values - however, there is no consistency with these and so, we'll need something like macros to help us solve these. exit function in eprintf has a magic number of '2' which is not okay. I want it to signal something so that bash scripting can be made a tad bit easier.

Would it be possible to handle mocking outside of the library code?
Some quick googling:

Alternatively, the library itself could be written in C but testing can easily be done in C++.

I'm not sure if we are on the same page - Criterion is the library of choice for that project, however eprintf usage restricts our testing capabilities.


Remove 'Loading...' for Annotations

Updates to allow annotation information to be fetched more quickly to avoid the 'Loading...' text in the UI.

@googlebot I fixed it.


Please correct npm maintainers configuration.

ioBroker adapter checker for npm access
Access right check for adapter yahoo-stock-market returned the following issue:
Bluefox was not found in the collaborators on NPM!.
Please execute in adapter directory: "npm owner add bluefox iobroker.yahoo-stock-market"
Current maintainers are
realnewan<EMAIL_ADDRESS>Please fix the above error as soon as possible.
All adapters listed at ioBroker repositories must have 'bluefox' added as maintainer.
Future version updates at the repositories will be suspended until this problem is fixed.

@GermanBluefox  Failed to update package: "409 Conflict - PUT https://registry.npmjs.org/iobroker.webuntis/-rev/7-8bfa6d2d7288d2acf1fb17a409811d66 - User already has a pending invite"

should be fixed:
C:\Users\Martin>npm owner list iobroker.yahoo-stock-market
bluefox<EMAIL_ADDRESS>realnewan<EMAIL_ADDRESS>


Returning index of each matched string

Hi,
Thanks for this great tool!
I had one question, is it possible to also return the index in the wordset that a particular query word matches? For example, using the example in the README, can I do the following:
import Levenshtein_search

excerpt1 = ["We","went","to","the","fire","Mother","said","Is","he","cold","Versh","Nome","Versh","said","Take","his","overcoat","and","overshoes","off","Mother","said","How","many","times","do","I","have","to","tell","you","not","to","bring","him","into","the","house","with","his","overshoes","on"]

first_wordset = Levenshtein_search.populate_wordset(-1,excerpt1)

q = "overshoes"
maxdist = 4
results1 = Levenshtein_search.lookup(first_wordset,q,maxdist)

And somehow get the indices of all matches (without using the results1 output and iterating through the excerpt1 list again)? Iterating again through the excerpt1 list would be very slow for my large applications of this.
Thanks!
Keshav

Keshav,
The capability that you are describing is not included in Levenshtein_search. I may be able to include the capability in a future Github repository. As of right now, I have no definite plans to do this. Also, the capability is somewhat more complex because words may appear more than once. You could have a Python dictionary that maps to a set. The set would contain the indices of that word. That would be my advice to you.
Best regards,
Matt

Hi Matt,
Thanks for the quick response! Sounds good, if there is a future release with this functionality I'd greatly appreciate it, but it's a great tool as it is!
One quick question unrelated to this: is there an easy way to do the same thing as this package, but for Hamming distance instead of Levenshtein (search for all strings that match within a distance)? If not, are you aware of any other packages that do this? I can only find ones which would require me to compute the distance between all pairs.
Thanks,
Keshav

Hamming distance is easier than Levenshtein distance. But making another search algorithm - regardless of its difficulty - would be a big lift. Anyone is encouraged to make a fork of this repo and modify it to use the Hamming distance. I don't know of any other packages that would do this. I do use another Postgres-based tool as an alternative to the Levenshtein search so maybe there is a Postgres-based tool that does Hamming distance.

https://dba.stackexchange.com/questions/72134/fast-hamming-distance-queries-in-postgres


Update circular_countdown_timer.dart

add add seconds function

Can you please further explain that what you have done in this Pull Request. You have defined a add function but you didn't invoke it. What is the purpose of the function?

Closed due to missing information/engagement of PR author #38


Add codeblock colors to hover.build

The hover.build website shows multiple code blocks, these are not colored right now, but should be. Investigate a good codeblock color plugin for hugo, or client-side. Copy button would be nice to have as well.

I took the liberty to push changes to the website repo.
Duplicating wikis isn't maintainable, I prefer to have everything on github. That why my changes are include redirecting the user the the github wiki.
About the blog, with medium I really thing that having personal hugo blog aren't made for massive sharing, deleted the hover.build link to the empty hover.build/blog site.
Overall, maintaining this site can be a lot of work, that why I prefer to keep it simple & minimal.

I want to clean the issue backlog.
Since there isn't much content on hover.build, I guess it's not our top priority.


fix: response text for not online greeting needed to be updated.

fixes #87

Coverage increased (+0.1%) to 96.774% when pulling e47508c9b94bcb6d5fab88513b9e58f1bd226488 on lholmquist:87-not-online-response into cf5dc7a035881795bad33a4cf84e657a86eab33c on bucharest-gold:master.


Mcooley/ut capabilities

Fixes #.
Description of the changes:
Isn't properly programmed.
How changes were validated:

automated testing

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


GO:0014823 response to activity -> "response to physical activity"

If this term is required the label should be changed because it is misleading.
Here the activity referred to is "physical activity" not a molecular activity
210/286 annotations are IEP
(also GO:0014865 detection of activity)

Also add GO:0032501
multicellular organismal process
to give taxon restriction

@pgaudet  do you agree with this?
The definition is
Any process that results in a change in state or activity of a cell or an organism (in terms of movement, secretion, enzyme production, gene expression, etc.) as a result of an activity stimulus.
but the related synonym
"response to exercise" implies this refers to physical activity?
GO:0014865   detection of activity
Is weird, but has not been used in annotation. I can obsolete that one?

@pgaudet  do you agree?

I cannot make a decision on an obsoletion without looking at the intended usage for the term. I have no time to look at 200 annotations.

It just seems strange to use the  term label "activity"  in a label when it doesn't refer to the GO concept of "activity" (i.e molecular activity)
I thought this one would be a simple term relabelling , I didn't think we would  need to check the annotations,  but I guess it is possible that some of the direct  annotations  to the activity terms are not related to physical activity.

I can close this one....I only opened because I was confused by the term


Fix #49

Fix #49
Clean out HTML Templates (classes not used whatsoever).

Good!
But maybe we should keep BS in nimwcpkg/tmpl/blog.tmpl which is not using genMainAdmin()? If the user chose to use BS instead of Bulma, then the CSS would not fit.

nimwcpkg/tmpl/blog.tmpl Revert from master


chore(main): release 0.5.0

:robot: I have created a release beep boop
0.5.0 (2024-11-27)
Documentation

Remove two fill words (d6477ed)

Miscellaneous Chores

release 0.5.0 (c49b460)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/MaxG87/collectiondict/releases/tag/v0.5.0 :sunflower:


Implement SHOW CREATE TABLE

Implement SHOW CREATE TABLE statement.
See: https://github.com/src-d/gitbase/issues/361#issuecomment-427285397

I'll try this

I can't find Charset, Auto increment by number and engine. Should ENGINE default to InnoDB, and DEFAULT CHARSET to utf8mb4

I've got to a point where I can print out the basic structure of the statement, but have some issues with the constraints part. Test run image
Can you provide some guidance regarding the constraints part?
My bet is that something similar to the following snippet should happen, where you grab the indices and just print the expressions:
`	indexes := i.registry.IndexesByTable(i.db.Name(), i.table)
constrCreateStatements := make([]string, len(indexes), len(indexes))
for indx, index := range indexes {

	createStmtPart := fmt.Sprintf("%s (`%s`)", stripBrackets(index.Expressions()), index.ID())

	if index.Driver() != "" {
		createStmtPart = fmt.Sprintf("%s USING driverid (%s)", createStmtPart, index.Driver())
	}

	constrCreateStatements[indx] = fmt.Sprintf(",\n%s\n", createStmtPart)
}`

Maybe add a switch on this because:
	// Expressions returns the indexed expressions. If the result is more than 	// one expression, it means the index has multiple columns indexed. If it's 	// just one, it means it may be an expression or a column. 	Expressions() []string

Charset being under conversation on #407

ENGINE=InnoDB by default sounds good, it is the default both for MySQL and MariaDB. Although it's completely fake, users will not be expected to use these CREATE TABLE statements within go-mysql-server itself at the moment.

@Zarkopafilis constraints should be empty. go-mysql-server does not create primary keys, foreign keys or unique indexes right now, so they should not show up. The kind of indexes created by go-mysql-server shouldn't show up here.


Allow enable standard SQL

https://cloud.google.com/bigquery/docs/reference/standard-sql/enabling-standard-sql

fixed https://github.com/keboola/google-bigquery-extractor/pull/17


L.disableClickPropagation not working

How to reproduce

Leaflet version I'm using: 1.0.1
Browser (with version) I'm using: Google Chrome Version 57.0.2987.133 (64-bit)
OS/Platform (with version) I'm using: Linux Manjaro

What behaviour I'm expecting and which behaviour I'm seeing
When doubleClicking the test div the map zoom event is triggered.
Minimal example reproducing the issue

[ ] this example is as simple as possible
[ ] this example does not rely on any third party code

Check the example here.
Is something wrong  with my code?
Thanks.

Related to #5217

@danierod hi there,
I looked at your example, and in fact it looks like there is an issue with your code.
To get hold of the created div, you use getElementById, but you haven't assigned an id to the div, so you end up passing null as element to disableClickPropagation.
I highly recommend always looking at the console output when something weird happens. In your case, you can clearly see your call to disableClickPropagation causing the error Uncaught TypeError: Cannot read property '_leaflet_events' of null.
A fixed version of your code can look something like this: http://playground-leaflet.rhcloud.com/huw/edit?html,output


[FIX] missing ctx in new_form

added the ctx for the project link in new_form.tmpl

@lng2020
Question: I just started looking into the Gitea project and I've noticed that there are quite a few issues related to the same 'missing ctx' error.
I'm wondering what is the reason these errors are being overlooked so frequently and not noticed earlier.

@lng2020 Question: I just started looking into the Gitea project and I've noticed that there are quite a few issues related to the same 'missing ctx' error. I'm wondering what is the reason these errors are being overlooked so frequently and not noticed earlier.

Currently, we are refactoring about db context(https://github.com/go-gitea/gitea/issues/27065), which inevitably causes some issues. The version before 1.21 does not include this refactoration, so there are not such issues.

I was unable to create a backport for 1.21. @mohammedahmed18, please send one manually. :tea:
go run ./contrib/backport 27514
...  // fix git conflicts if any
go run ./contrib/backport --continue


Creating Posts

When I try to create a post for the first time, I cannot create a nickname.
I get the loading circle for ages and nothing happens. I can't click out and have to close the app to exit the loading screen.  When I return to the app/create post view to set up a nickname, I get the loading circle then "Error Creating Account: Try again later."
If I go to Settings, Paik Talk, create a nickname, go back to create post view, I can continue with agreement and make a draft.

I saw this once when testing now, but then could not reproduce it again. I did see something about a "404 error" in the logs when creating the WPClient user name.

The automated testing suite passes so I wonder if there's a server issue
there..
On Thu, Aug 20, 2015 at 2:01 AM, N-Pex<EMAIL_ADDRESS>wrote:

I saw this once when testing now, but then could not reproduce it again. I
did see something about a "404 error" in the logs when creating the
WPClient user name.
—
Reply to this email directly or view it on GitHub
https://github.com/guardianproject/securereader_ios/issues/51#issuecomment-132944468
.

I just tested this again, and it worked.


Adjust rounding for meta cell bit-packing

It seems that OpenGL allows different behavior for rounding when normalizing colors, which in turns makes the bit-packing logic sensitive to changes. This change adjusts the rounding, to work on more devices.

Codecov Report

Merging #701 (8f6ee20) into main (849151d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #701   +/-   ##
=======================================
  Coverage   70.63%   70.63%
=======================================
  Files         113      113
  Lines        5497     5497
  Branches     1083     1083
=======================================
  Hits         3883     3883
  Misses        869      869
  Partials      745      745

Impacted Files
Coverage Δ

...anyo/composelife/openglrenderer/GameOfLifeShape.kt
0.00% <ø> (ø)

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


Multiple warnings in docs

Describe the bug
With the .26 release, I started seeing a large number of the following error when running the docs site in dev mode:
reactivity.esm-bundler.js:9  [Vue warn] Set operation on key "value" failed: target is readonly. RefImpl {dep: Dep, __v_isRef: true, __v_isShallow: true, _rawValue: null, _value: null}

vue-warnings.log
Looking at #2353, it appears there are issues with name conflicts in useTemplateRef causing warnings. But I can't find anything in the vue docs to back this up. What I do see is that the reference that is created shouldn't conflict with other references, but in #2353, we're changing the symbol in the template.
In any case - I tried changing the element refs in BOffcanvas.vue to avoid collisions, and it removed several of the warnings.
const elementRef = useTemplateRef<HTMLElement>('offcanvas-element')
const fallbackFocusElement = useTemplateRef<HTMLElement>('fallback-focus-element')

But, I'm not even sure how to track down the ones where _rawValue === null. Do we have to 'fix' every place that we call useTemplateRef to make the names unique? We've got a lot of places where we're referencing element, so that won't be a small chore, but doable. I just wouldn't want to tackle that without understanding what is actually going on.
Also, this appears to only happen with SSR. A simple app that uses an BOverlay doesn't repro.
@mbabker - any thoughts? Can you point me at anything that describes why the changes you made in #2353 work?
Reproduction
All of the docs pages
Used Package Manager
pnpm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

There are probably other fixes similar to what I did in #2353 needed.  When looking for info when I filed #2337, it seems like the root cause is the template ref having the same name as the script variable.  Because of the way Vue handles template references, it tries to automatically assign the reference to something with the same variable name (in BModal I see a fallbackFocusElement and a const fallbackFocusElement = useTemplateRef('fallbackFocusElement') as an example), and https://github.com/vuejs/core/issues/11795 leads me to believe that's the wrong use of the useTemplateRef helper.

Thanks @mbabker - If I'm reading the vue core information correctly vuejs/core#11795 is closed as fixed by bc63df0, which shows up in the changelog as fixed in 3.5.1
So I don't think the right answer is to go an change all our names. We should figure out why we're either not seeing the fix or why the fix isn't working in our case.
@VividLemon, @xvaara any thoughts? Are you seeing these warnings on your local machines or am I doing something weird? I see the pnpm-lock.yaml is showing vue as 3.5.13 and I'm also showing that version number in vue tools, so I think I've correctly pulled down the most recent version that should have this fix.

Check again

Okay, I take it this means you're not seeing the issue?
I'm attempting as clean a build as I can, so I created a clone directly from the main branch of the main fork.
Here's what I did:

git clone https://github.com/bootstrap-vue-next/bootstrap-vue-next.git bsvn
cd bsvn
pnpm install
pnmp dev
open http://localhost:8000/bootstrap-vue-next/ in a browser

I get the same errors I attached above. Other than global caching of corrupt or outdated packages, I can't think of anything else that would cause this to fail on my machine and not yours, but as I've said before this is not my native environment, so please let me know if you have any ideas.
P.S. Just tried the above on a different machine and get the same results, so I'm completely stumped...

I am also seeing these errors

@VividLemon this is the reason I sais we shouldn't change to useTemplateRef without a reason to do so.
My understanding of this is that it complains in dev mode. Of the ref:ed element isn't rendered at the first load then vue needs to set the ref to the element. If the ref="foo" matches const foo then vue tries to set the const foo to the element with ref="foo", and useTemplateRef does it a diffrerent a little bit more complex way.
So we need to change the ref="x" to something to avoid changing the variables. My suggestion is that we add _ to the begining of them, common convention for "internal variables".

@dwgray can you test the pr if it fixes all the errors for you?

Thanks, @xvaara, that resolves the warnings I'm seeing, and the solution makes sense to me.


Toggle to remove shadow from Display Named NPCs

When an NPC gets inputted into the Display Names section the name does indeed appear however it has a shadow background that I think makes it look more difficult to see compared to without a shadow, if there was a toggle or any possibility to remove this I would think it looks much better

Adding this next update

excellent love you


Fix -f routine lookup in Type/independent-routines

The problem
Because the pseudo-Type name 'independent-routines' contains the string
'routine', it was being filtered out of the results list when looking up
a routine in it, such as p6doc -f sprintf.
$ p6doc -f sprintf
No such type ''

Solution provided
Be less cavalier about filtering the @types array.

Ah, I didn't realize it was going away. What is replacing it?

A new and better p6doc... I think I'll merge this anyway.


Enabling typing in Homebrew::API module

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

This enables typing for all the files that I could find under Homebrew::API

The rest of this LGTM

Thanks again @dduugg!


NameError: global name 'timezone' is not defined

Had the "timezone -> datetime" issue described in https://github.com/defaultnamehere/tinder-detective/issues/13, but after changing the code on my end, I'm getting this error after running the app.

Was able to resolve by changing line 8 of api.py to:
"from datetime import *"

It's possible this issue could have been caused if you were trying to run the app with python2 instead of python3.


Support file uploads

In the edit view, as alternative to using the text area, a user should be able to upload a file from his computer. The contents of that file will be saved under the URL being edited.

Options for upload components:

Dropzone.js, compatible to HTML upload, no JS dependencies, fully customizable, but maybe doesn't match our requirements out of the box (per default designed for multiple files to upload)
FileDrop.js -- dead simple, can turn every HTML tag into an upload component, no JS dependencies


Can't create Datadog integration for existing PostgreSQL service

I'm not able to create datadog integration for existing PostgreSQL service. In the kubernetes logs i see message that preconditions are not met
INFO controllers.ServiceIntegration preconditions are not met, requeue {"kind": "serviceintegration", "name": "aiven-operator/datadog-kotest", "annotations": {}}.
Using the Aiven API, the same integration is created without any problems

Hi @AgasiAm

Does your service exists and running?
What version of the operator do you use?
Could you please provide some logs and yamls I can take a look at?

Hi @byashimov
Thank you for quick response

Yes, service exist and running
Version 0.9.0
I tried using different configurations for datadog service integration and finally come up with this one

`apiVersion: aiven.io/v1alpha1
kind: ServiceIntegration
metadata:
name: service1-prd-kotest
spec:
authSecretRef:
name: aiven-token
key: token
project: aghasioptest
integrationType: datadog
sourceServiceName: service1-prd
destinationServiceName: 'Null'
sourceEndpointID: 'Null'
destinationEndpointId:
datadog:
datadog_dbm_enabled: True
datadog_tags:
- tag: env
comment: stg`

Also want to mention that when creating integration using API, only source_project, source_service and dest_endpoint_id is required, however operator is forcing to add destinationServiceName and sourceEndpointID to config

Yeah. I see the problem now. 'Null' is not really a null, it is a string (?). So I assume it cannot wait a 'Null' service being running. I'll come back with a fix soon. Thanks for the reporting.

@AgasiAm just checked out CRD. Only project and integration_type are required.
Could you please remove those fields and try again. Or what exactly error does say?

destinationServiceName and sourceEndpointID becoming required when sourceServiceName and destinationEndpointId is set. Here is a error example
Error from server (destinationServiceName cannot be empty when sourceServiceName is set): error when creating "services/service1/datadog.yaml": admission webhook "vserviceintegration.kb.io" denied the request: destinationServiceName cannot be empty when sourceServiceName is set

Same for EndpointIDs

Also one other question regarding to integration
To find destinationEndpointID i need to query all available integrations for the services by using API endpoint /v1/project/{project}/service/{service_name}/integration then filter results by integration_type=datadog and dest_endpoint=<integration name>
Can the integration be extended so that there is no need for an API? For example, use the endpoint name in yaml, which will be converted to endpoint id behind the scenes by the operator


Misleading opengl example

extern crate gl;
extern crate sdl2;

fn main() {
    let sdl_context = sdl2::init().unwrap();
    let video_subsystem = sdl_context.video().unwrap();
    gl::load_with(|name| video_subsystem.gl_get_proc_address(name) as *const _);

    let window = video_subsystem.window("Toyunda Player", 800, 600)
        .resizable()
        .position_centered()
        .opengl()
        .build()
        .unwrap();

    unsafe{gl::BindVertexArray(0);}
}

It doesn't work ("gl function was not loaded"). gl::load_with must be run after the window creation (implicit dependencies yeay). You should at least mention it in the README.

Is this related to #497 ?

Seems to, yes


[Test] Fix Runtime/protocol_conformance_collision.swift on 11.3+.

This test checks the OS version to decide how to operate but that check isn't right. Revert to a fake future version.
rdar://77389722

@swift-ci please smoke test

@swift-ci please smoke test windows platform


Use RbNaCl for HMAC if available with fallback to OpenSSL

For the 1.x version I will not add any new features. This PR is interesting for version 2.0.

Hi @excpt, I've rebased this to master if you're interested in including it in the 2.0 release. Let me know if you'd like any changes!

Thanks for the Rebase 👍

Yessir, thanks for the merge!


Remove the leftovers after ImportLocator removal

Follow the FIXME's suggestion (https://github.com/rust-analyzer/rust-analyzer/pull/3034/files#diff-001b3b1412c33fee802c22b0f848dcd7L237) and remove the ModuleDefId reexport.
Also rename ImportsLocatorIde into plain ImportsLocator

bors r+


Will gateway support spring MVC in the future

i have a web project, and all http request  are intended to go through the spring cloud，but Spring-boot-starter-web is incompatible with spring-cloud-starter-gateway.
In the end, I had to choose zuul. but zuul can not support websocket.
Will gateway support spring MVC in the future ??

Duplicates #36


:arrow_up: Move the Front end docker images to alpine latest

User Story
As a developer
I expect to run docker images which contain library updates
So that we keep software upto date and reduce the vulnerability footprint
Value / Purpose
Some recent image scanning has highlighted the lack of updates to our base docker images and the need for an approach to keep on top of updates going forward.
We should look to deploy the node and python alpine images as these are prebuilt on the latest os versions and are minimal in that they only contain the necessary packages required for the OS to function which means there are less libraries and therefore less opportunities for vulnerabilities.
If we opt for the given major train number and alpine this will give us all required updates throughout the life of the train, this does however add potential risks of the occasional failing build due to incompatible libraries.
Examples - image:[version number]-alpine
python:3.11-alpine & node:23-alpine
Definition of Done

[ ] Docker file updated with new image details
[ ] Successful build is completed
[ ] Tests are green
[ ] App successfully deployed

Issue experienced with local docker build and run with existing dockerfile pre changes.
`find-moj-data-py3.11➜  find-moj-data git:(fmd-1037-docker-images) ✗ docker exec -it f01458d17dee sh
$ python
Python 3.11.4 (main, Jun 13 2023, 11:45:08) [GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import sqlit3
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'sqlit3'
import sqlite3
sqlite3.sqlite_version
'3.27.2'`

Image builds successfully with python:3.11-alpine3.20 & node:23-alpine3.20 images.
Currenty Vulnerabilties
find-moj-data-py3.11➜  find-moj-data git:(fmd-1037-docker-images) trivy image --scanners vuln find-moj-data
2024-11-13T16:28:08Z    INFO    [vuln] Vulnerability scanning is enabled
2024-11-13T16:28:19Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pip" version="24.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Deprecated" version="1.2.14"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Django" version="5.1.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Markdown" version="3.7"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="PyJWT" version="2.8.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="PyYAML" version="6.0.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="acryl-datahub" version="<IP_ADDRESS>"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiohappyeyeballs" version="2.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiohttp" version="3.10.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiosignal" version="1.3.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="asgiref" version="3.8.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="avro" version="1.11.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="avro-gen3" version="0.7.11"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cached-property" version="1.5.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="certifi" version="2024.7.4"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cffi" version="1.16.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="charset-normalizer" version="3.3.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="click" version="8.1.7"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cryptography" version="43.0.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="deepdiff" version="6.7.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-azure-auth" version="2.1.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-debug-toolbar" version="4.4.6"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-prometheus" version="2.3.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-waffle" version="4.1.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="docker" version="7.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="docopt" version="0.6.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="expandvars" version="0.12.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="freezegun" version="1.5.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="frozenlist" version="1.4.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="gunicorn" version="23.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="hiredis" version="3.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="humanfriendly" version="10.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ijson" version="3.2.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="joblib" version="1.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="jsonschema" version="4.22.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="jsonschema-specifications" version="2023.12.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="markdown-headdown" version="0.1.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ministryofjustice-data-platform-catalogue" version="1.1.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mixpanel" version="4.10.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="msal" version="1.28.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="multidict" version="6.0.5"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mypy-extensions" version="1.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="nltk" version="3.9.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="notifications-python-client" version="10.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pip" version="24.3.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="progressbar2" version="4.4.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="prometheus_client" version="0.20.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psutil" version="5.9.8"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psycopg" version="3.2.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psycopg-binary" version="3.2.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pycparser" version="2.22"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pydantic_core" version="2.18.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-dateutil" version="2.9.0.post0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-dotenv" version="1.0.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-utils" version="3.8.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="redis" version="5.2.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="regex" version="2024.4.28"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="requests" version="2.32.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="requests-file" version="2.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="rpds-py" version="0.18.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ruamel.yaml" version="0.18.6"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ruamel.yaml.clib" version="0.2.8"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sentry-sdk" version="2.18.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="autocommand" version="2.2.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="typeguard" version="4.3.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="six" version="1.16.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="tabulate" version="0.9.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="termcolor" version="2.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="toml" version="0.10.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="tqdm" version="4.66.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="typing-inspect" version="0.9.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="wrapt" version="1.16.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="yarl" version="1.9.4"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Deprecated" version="1.2.14"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Django" version="5.1.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Faker" version="30.8.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Markdown" version="3.7"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="PyJWT" version="2.8.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="PyYAML" version="6.0.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="acryl-datahub" version="<IP_ADDRESS>"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiohappyeyeballs" version="2.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiohttp" version="3.10.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiosignal" version="1.3.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="asgiref" version="3.8.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="avro" version="1.11.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="avro-gen3" version="0.7.11"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="black" version="24.10.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cached-property" version="1.5.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="certifi" version="2024.7.4"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cffi" version="1.16.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cfgv" version="3.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="charset-normalizer" version="3.3.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="click" version="8.1.7"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="coverage" version="7.5.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cryptography" version="43.0.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="deepdiff" version="6.7.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="distlib" version="0.3.8"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-azure-auth" version="2.1.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-debug-toolbar" version="4.4.6"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-prometheus" version="2.3.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-waffle" version="4.1.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="djhtml" version="3.0.6"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="docker" version="7.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="docopt" version="0.6.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="expandvars" version="0.12.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="flake8" version="7.1.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="freezegun" version="1.5.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="frozenlist" version="1.4.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="gunicorn" version="23.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="h11" version="0.14.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="hiredis" version="3.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="humanfriendly" version="10.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="identify" version="2.5.36"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ijson" version="3.2.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="isort" version="5.13.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="joblib" version="1.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="jsonschema" version="4.22.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="jsonschema-specifications" version="2023.12.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="markdown-headdown" version="0.1.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mccabe" version="0.7.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ministryofjustice-data-platform-catalogue" version="1.1.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mixpanel" version="4.10.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="msal" version="1.28.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="multidict" version="6.0.5"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mypy-extensions" version="1.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="nltk" version="3.9.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="nodeenv" version="1.8.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="notifications-python-client" version="10.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="outcome" version="1.3.0.post0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pip" version="24.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pluggy" version="1.5.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pre_commit" version="4.0.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="progressbar2" version="4.4.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="prometheus_client" version="0.20.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psutil" version="5.9.8"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psycopg" version="3.2.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psycopg-binary" version="3.2.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pycodestyle" version="2.12.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pycparser" version="2.22"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pydantic_core" version="2.18.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pyflakes" version="3.2.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pytest" version="8.2.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pytest-cov" version="6.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pytest-django" version="4.9.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-dateutil" version="2.9.0.post0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-dotenv" version="1.0.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-utils" version="3.8.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="redis" version="5.2.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="regex" version="2024.4.28"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="requests" version="2.32.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="requests-file" version="2.0.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="rpds-py" version="0.18.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ruamel.yaml" version="0.18.6"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ruamel.yaml.clib" version="0.2.8"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="selenium" version="4.26.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sentry-sdk" version="2.17.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="six" version="1.16.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sniffio" version="1.3.1"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sortedcontainers" version="2.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="tabulate" version="0.9.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="termcolor" version="2.4.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="toml" version="0.10.2"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="tqdm" version="4.66.3"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="trio" version="0.25.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="typing-inspect" version="0.9.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="websocket-client" version="1.8.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="wrapt" version="1.16.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="wsproto" version="1.2.0"
2024-11-13T16:28:20Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="yarl" version="1.9.4"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Deprecated" version="1.2.14"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Django" version="5.1.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Django" version="5.1.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Faker" version="30.8.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="Markdown" version="3.7"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="PyJWT" version="2.8.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="PyYAML" version="6.0.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="acryl-datahub" version="<IP_ADDRESS>"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiohappyeyeballs" version="2.4.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiohttp" version="3.10.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="aiosignal" version="1.3.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="asgiref" version="3.8.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="avro" version="1.11.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="avro-gen3" version="0.7.11"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="black" version="24.10.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cached-property" version="1.5.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="certifi" version="2024.7.4"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cffi" version="1.16.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cfgv" version="3.4.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="charset-normalizer" version="3.3.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="click" version="8.1.7"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="coverage" version="7.5.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="cryptography" version="43.0.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="deepdiff" version="6.7.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="distlib" version="0.3.8"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-azure-auth" version="2.1.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-debug-toolbar" version="4.4.6"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-prometheus" version="2.3.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="django-waffle" version="4.1.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="djhtml" version="3.0.6"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="docker" version="7.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="docopt" version="0.6.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="expandvars" version="0.12.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="flake8" version="7.1.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="freezegun" version="1.5.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="frozenlist" version="1.4.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="gunicorn" version="23.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="h11" version="0.14.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="hiredis" version="3.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="humanfriendly" version="10.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="identify" version="2.5.36"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ijson" version="3.2.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="isort" version="5.13.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="joblib" version="1.4.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="jsonschema" version="4.22.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="jsonschema-specifications" version="2023.12.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="markdown-headdown" version="0.1.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mccabe" version="0.7.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ministryofjustice-data-platform-catalogue" version="1.1.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mixpanel" version="4.10.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="msal" version="1.28.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="multidict" version="6.0.5"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="mypy-extensions" version="1.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="nltk" version="3.9.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="nodeenv" version="1.8.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="notifications-python-client" version="10.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="outcome" version="1.3.0.post0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pip" version="24.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pip" version="24.3.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pluggy" version="1.5.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pre_commit" version="4.0.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="progressbar2" version="4.4.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="prometheus_client" version="0.20.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psutil" version="5.9.8"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psycopg" version="3.2.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="psycopg-binary" version="3.2.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pycodestyle" version="2.12.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pycparser" version="2.22"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pydantic_core" version="2.18.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pyflakes" version="3.2.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pytest" version="8.2.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pytest-cov" version="6.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="pytest-django" version="4.9.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-dateutil" version="2.9.0.post0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-dotenv" version="1.0.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="python-utils" version="3.8.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="redis" version="5.2.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="regex" version="2024.4.28"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="requests" version="2.32.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="requests-file" version="2.0.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="rpds-py" version="0.18.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ruamel.yaml" version="0.18.6"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="ruamel.yaml.clib" version="0.2.8"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="selenium" version="4.26.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sentry-sdk" version="2.17.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sentry-sdk" version="2.18.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="autocommand" version="2.2.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="typeguard" version="4.3.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="six" version="1.16.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sniffio" version="1.3.1"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="sortedcontainers" version="2.4.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="tabulate" version="0.9.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="termcolor" version="2.4.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="toml" version="0.10.2"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="tqdm" version="4.66.3"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="trio" version="0.25.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="typing-inspect" version="0.9.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="websocket-client" version="1.8.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="wrapt" version="1.16.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="wsproto" version="1.2.0"
2024-11-13T16:28:21Z    INFO    [python] License acquired from METADATA classifiers may be subject to additional terms  name="yarl" version="1.9.4"
2024-11-13T16:28:21Z    INFO    Detected OS     family="alpine" version="3.20.3"
2024-11-13T16:28:21Z    INFO    [alpine] Detecting vulnerabilities...   os_version="3.20" repository="3.20" pkg_num=41
2024-11-13T16:28:21Z    INFO    Number of language-specific files       num=1
2024-11-13T16:28:21Z    INFO    [python-pkg] Detecting vulnerabilities...
find-moj-data (alpine 3.20.3)
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)
2024-11-13T16:28:21Z    INFO    Table result includes only package filenames. Use '--format json' option to get the full path to the package file.
Python (python-pkg)
Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)
┌───────────────────────┬───────────────┬──────────┬────────┬───────────────────┬───────────────┬─────────────────────────────────────────────────────┐
│        Library        │ Vulnerability │ Severity │ Status │ Installed Version │ Fixed Version │                        Title                        │
├───────────────────────┼───────────────┼──────────┼────────┼───────────────────┼───────────────┼─────────────────────────────────────────────────────┤
│ setuptools (METADATA) │ CVE-2024-6345 │ HIGH     │ fixed  │ 65.5.1            │ 70.0.0        │ pypa/setuptools: Remote code execution via download │
│                       │               │          │        │                   │               │ functions in the package_index module in...         │
│                       │               │          │        │                   │               │ https://avd.aquasec.com/nvd/cve-2024-6345           │
└───────────────────────┴───────────────┴──────────┴────────┴───────────────────┴───────────────┴─────────────────────────────────────────────────────┘


Create a mapLayout class to read text files and load map

Description
Task: [Create a mapLayout class to read text files and load map]
Feature: #300 #309
This task is related to creating a class that can read text files containing information about the tiles of the map. It consist of reading letters and being able to create the correct map based on that text file. A class and different functions will need to be created for this.
Dependencies

No dependencies for the reader but in order to load in all maps and complete this it depends on finish the design of all maps and the text files #301 #348. This also depends on the stations team to finish implementing their stations.

Milestones
List of steps that need to be completed for this task.

[ ] Creating a class for the layout (Sept 24)
[ ] Creating a function that is able to load/read a text file (Sept 28)
[ ] Handle different letters/tiles (Sept 30)
[ ] Load the map in the game area/spawn elements (Oct 1)
[ ] Implement different maps for each day/level (Oct 2)
[ ] Test the code written (Oct 3)

Completion Deadline: Oct 3
Documentation

Map Layouts

Member

@Sarahkhalek
@ATOApplett

added BenchLayout class for this, possibly going to add other map layout type classes to clean up ForestGameArea a bit more I think

Closed by #447


[bug]: kubernetesClient.UpdateStatus() causes resourceVersion change which causes 'conflict' on next UpdateStatus call

Describe the bug
We employ this library to set up AWS infrastructure. Upon generating a resource (i.e SecurityGroup.yaml) within Kubernetes, our operator (utilizing dotnet-operator-sdk) initiates the creation or update of the corresponding SecurityGroup in AWS.
We utilize kubernetesClient.UpdateStatus() to modify the status field of a resource. In a single synchronization cycle, we need to invoke kubernetesClient.UpdateStatus() multiple times to log the creation of the security group, as well as the establishment of both ingress and egress rules within the said security group.
After upgrading to KubeOps version 7.4.2, we have noticed that any modifications made to the status field result in a modification to the resourceVersion. In contrast, in the previous version of KubeOps, changes to the status field did not lead to alterations in the resourceVersion.
Since invoking kubernetesClient.UpdateStatus() leads to a modification in the resource version, any subsequent call to kubernetesClient.UpdateStatus() encounters an exception (k8s.Autorest.HttpOperationException: Operation returned an invalid status code 'Conflict').
To reproduce

install KubeOps version 7.4.2
create entity
modify status using sdk
it changes resourceVersion and subsequent status update result in exception "Conflict"

exception details
k8s.Autorest.HttpOperationException: Operation returned an invalid status code 'Conflict'
at k8s.Kubernetes.SendRequestRaw(String requestContent, HttpRequestMessage httpRequest, CancellationToken cancellationToken)
at k8s.AbstractKubernetes.k8s.ICustomObjectsOperations.ReplaceNamespacedCustomObjectStatusWithHttpMessagesAsync(Object body, String group, String version, String namespaceParameter, String plural, String name, String dryRun, String fieldManager, IReadOnlyDictionary2 customHeaders, CancellationToken cancellationToken)    at k8s.CustomObjectsOperationsExtensions.ReplaceNamespacedCustomObjectStatusAsync(ICustomObjectsOperations operations, Object body, String group, String version, String namespaceParameter, String plural, String name, String dryRun, String fieldManager, CancellationToken cancellationToken)    at KubeOps.KubernetesClient.KubernetesClient.UpdateStatus[TResource](TResource resource)    at Platform.Operators.Kubernetes.KubernetesClientExtensions.UpdateStatusWithConflictRetryAsync[TResource,TStatus](IKubernetesClient client, Action1 statusUpdate, TResource resource, CancellationToken cancellationToken)
at Platform.Operators.Kubernetes.KubernetesClientExtensions.UpdateStatusWithConflictRetryAsync[TResource,TStatus](IKubernetesClient client, Action`1 statusUpdate, TResource resource, CancellationToken cancellationToken)
Expected behavior
it should not change resourceVersion when we update status field.
Screenshots
No response
Additional Context
k8s version : 1.26

tomitesh colleague here...
This may be caused by a misunderstanding on how this library is supposed to be used on our part, please ignore this issue for now, we will re-evaluate our approach and possibly close the issue on the next Tuesday.

I ran into this myself just now. I was upgrading from a previous version of the KubeOps library (5.4.1 -> 7.4.2). I have a sort of "operator" where a deployed custom entity type ends up generating other deployed entities.
As part of the Reconcile loop it does:
// Add an entry to the `status` on the entity with "Progressing"
SetStatusAsProgressing(customEntity);
client.UpdateStatus(customEntity);
DeploySomeThingsOwnedByTheCustomEntity();
// Find that "Progressing" status and change it to "Deployed"
SetStatusAsDeployed(customEntity);
// Here's where I get the Conflict:
client.UpdateStatus(customEntity);

This is new since 5.4.1, which doesn't narrow it down a lot, but it looks like there was some pretty big change about seven months ago, I'm guessing with the 7.0 release.
What was a little confusing is that operations on the IKubernetesClient that mutate the object seem to return the updated object, but UpdateStatus does not, so it wasn't obvious that there would be a change to the resource version.

For now doing with a single operation and status update per reconcile "solved" the issue for us.
This is probably safer than forcing a status update on a entity that has since the start of the loop changed, as we can't be sure if it was our process or something else in the background that modified it

this is fixed in v8


Personalized emoji

Hello, would it be possible to provide personalized emoji?

Hello @alexni15, yes of course, it's an awesome idea!

And.. you can now start a duel between animals, or anything you want! :t-rex:

Mentionned commit adds custom emojies support through the configuration. You will be able to use both strings like :cow:, :cat: or unicode representations of them. Current emojies remain the default ones. Example of a configuration:
{
  "language": "en",
  "command": "-ttt",
  "gameBoardEmojies": [":dog:", ":cat:"]
}

It will be released in the next version!

Oh trop cool et merci.


Add support for relative path to dependencies

** BUG REPORT / FEATURE REQUEST?** (choose one):
When using a monorepo hosting many Charts, one of them refering the other with file://... protocol.
In such situation, I decided to use a path relative to the folder of the Chart.yml.
Thus, it works with helm triggered directly.
But when running the mvn command, the dependency is not found. The error message indicates a looking path incorrect.
I suspect the helm command is not triggered by the plugin from the chart's root directory but from project's root directory.

Ignore me: it is an error on our side.


Add files via upload

@ijim7 hillhouse.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


Job links in Readme are broken

All job links in readme just lead to https://docs.vouched.id/#tag/job-model.
That site does not contain any information about the Job model.

Thanks for letting us know! We switched to a new docs site and now the link structure changed. The job model can be found by clicking the 200 response on this page: https://docs.vouched.id/reference/findjobs. I will update the readme as well.


New version: BioMakie v0.1.1

Registering package: BioMakie
Repository: https://github.com/kool7d/BioMakie.jl
Created by: @kool7d
Version: v0.1.1
Commit: aab48f3222c01d02f1ba13f785b874df48328246
Git reference: v0.1.1

@kool7d you still need to

add a compat bound for Distances, but this seems to be done already in https://github.com/kool7d/BioMakie.jl/commit/0cca521dc2f7b365911abc85d956f1f66be22b13
make your package actually being able to be loaded :slightly_smiling_face:  Testing your package with continuous integration would help a lot in this regard

Once you're done, you can trigger registration again as you did before, keeping the same version number, which will simply update this pull request.  Note that you'll need to delete the v0.1.1.  Generally speaking, you should not create tags manually but use TagBot to do it automatically after a successful registration
[noblock]


review and re-enable multiplatform docker workflow

I think this is needed for Umbrel and Start9 releases when we have them. The build is failing currently and only runs on:
  release:
    types: [published]

which is inconsistent with our other workflows (not that it is necessarily wrong, just needs review).

This should be fixed by https://github.com/getAlby/nostr-wallet-connect-next/pull/501
As for the Github action trigger, it seems appropriate to run this action on release. It is quite slow, so running it only when a release is published makes sense.