Public API to turn Ecto.Query structs into the query they represent

Right now, there's no public API that given an %Ecto.Query{} struct returns the actual query as a string:
# named to_string or whatever
query = from u in User, where: u.email == "my email"
Ecto.Query.to_string(query)
#=> "SELECT FROM users WHERE email == 'my email'"

I think it would be useful for a number of possible use cases (mine is wrapping Ecto.Repo and doing stuff with the query before and after it's been performed).

I think we have a to_sql in the Ecto.Adapters.SQL module, no?
On Monday, November 23, 2015, Andrea Leopardi<EMAIL_ADDRESS>wrote:

Right now, there's no public API that given an %Ecto.Query{} struct
returns the actual query as a string:
named to_string or whateverEcto.Query.to_string(from u in User, where: u.email == "my email")#=> "SELECT FROM users WHERE email == 'my email'"
I think it would be useful for a number of possible use cases (mine is
wrapping Ecto.Repo and doing stuff with the query before and after it's
been performed).
—
Reply to this email directly or view it on GitHub
https://github.com/elixir-lang/ecto/issues/1096.

--
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

@josevalim Only works for SQL adapters of course.

Yes, it needs to be adapter specific. Some adapters do not even have a
string representation.
On Monday, November 23, 2015, Eric Meadows-Jönsson<EMAIL_ADDRESS>wrote:

@josevalim https://github.com/josevalim Only works for SQL adapters of
course.
—
Reply to this email directly or view it on GitHub
https://github.com/elixir-lang/ecto/issues/1096#issuecomment-159015027.

--
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D

It doesn't have to be a string, it can just return the query that the adapter sends to the database. Why does it have to be adapter specific, we can add it to one of the adapter behaviours.

I'm afraid it won't be that easy with MongoDB. Query struct does not contain params, and we can't generate a query without them - there are no parameters in Mongo's query syntax.

I'm pretty sure we can supply params in this case.

Can we update the proposal then? I would like to know:

What we are going to call a function that receives a query and returns whatever the query is supposed to be for the given adapter

Where should this function exist. It cannot exist in Ecto.Query because we need the repository (so we get the adapter). If we need it in the repository, why is it important enough to be in the repository and not just in the adapter like today.

Thanks folks. :)

It's fine if it's on the adapter (not on the repo) as long as it's a generic interface for all adapters (hence on one of the behaviours).

@ericmj I honestly wouldn't like to impose user facing API to the adapters which otherwise are only internal. I don't want to teach folks to rely on those APIs because I would like to retain the liberty of changing it any time. In other words, :-1: for conflating the current adapter behaviour with user functions.
It is ok for the adapter itself to expose it, because they are assuming this responsibility, I just don't want developers to access Ecto.Adapters.PostgreSQL.insert (for example) and assume it won't ever change. It will because it is an internal Ecto requirement. It goes through a different cycle than the user APIs.


Can't run install on Laravel v7x

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for yal/laraveldash ^1.0@dev -> satisfiable by yal/laraveldash[1.0.x-dev].

    - Can only install one of: laravel/framework[5.5.x-dev, v7.9.2].
    - Can only install one of: laravel/framework[5.6.x-dev, v7.9.2].
    - Can only install one of: laravel/framework[5.7.x-dev, v7.9.2].
    - Can only install one of: laravel/framework[5.8.x-dev, v7.9.2].
    - Can only install one of: laravel/framework[6.x-dev, v7.9.2].
    - illuminate/support 5.2.x-dev conflicts with laravel/framework[v7.9.2].
    - illuminate/support 5.3.x-dev conflicts with laravel/framework[v7.9.2].
    - illuminate/support 5.4.x-dev conflicts with laravel/framework[v7.9.2].
    - illuminate/support 5.5.x-dev conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.2.43 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.2.45 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.3.0 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.3.16 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.3.23 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.3.4 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.0 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.13 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.17 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.19 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.27 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.36 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.4.9 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.0 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.16 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.17 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.2 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.28 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.35 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.36 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.37 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.39 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.40 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.41 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.43 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.5.44 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.6.4 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.6.5 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.6.6 conflicts with laravel/framework[v7.9.2].
    - illuminate/support v5.6.7 conflicts with laravel/framework[v7.9.2].
    - laravel/framework 5.4.x-dev conflicts with laravel/framework[v7.9.2].
    - don't install illuminate/support v5.5.33|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.5.34|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.6.x-dev|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.10|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.11|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.12|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.13|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.14|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.15|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.16|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.17|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.19|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.20|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.21|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.22|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.23|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.24|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.25|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.26|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.27|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.28|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.29|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.3|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.30|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.31|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.32|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.33|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.34|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.35|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.36|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.37|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.38|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.39|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.8|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.6.9|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.7.17|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.7.18|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.7.19|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.7.x-dev|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.10|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.11|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.15|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.20|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.21|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.22|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.23|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.26|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.27|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.28|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.3|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.4|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.5|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.6|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.7|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.8|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.7.9|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.8.x-dev|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.11|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.12|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.14|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.15|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.17|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.18|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.19|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.20|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.22|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.24|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.27|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.28|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.29|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.3|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.30|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.31|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.32|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.33|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.34|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.35|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.36|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.4|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.8|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.8.9|don't install laravel/framework v7.9.2
    - don't install illuminate/support 6.x-dev|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.0.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.0.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.0.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.0.3|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.0.4|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.1.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.10.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.11.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.12.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.13.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.13.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.14.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.15.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.15.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.16.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.17.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.17.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.10|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.11|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.3|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.4|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.5|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.6|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.7|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.8|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.18.9|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.2.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.3.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.4.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.5.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.5.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.5.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.6.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.6.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.6.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.7.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v6.8.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.1.x-dev|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.1|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.13|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.16|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.2|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.20|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.22|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.25|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.28|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.30|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.31|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.41|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.6|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.1.8|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.19|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.21|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.24|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.25|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.26|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.27|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.28|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.31|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.32|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.37|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.6|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.2.7|don't install laravel/framework v7.9.2
    - don't install illuminate/support 5.0.x-dev|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.0|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.22|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.25|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.26|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.28|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.33|don't install laravel/framework v7.9.2
    - don't install illuminate/support v5.0.4|don't install laravel/framework v7.9.2
    - Installation request for laravel/framework (locked at v7.9.2, required as ^7.0) -> satisfiable by laravel/framework[v7.9.2].

Hi @goodmuyis,
The Bug has been solved.
Thanks to @oliuz

Hi @goodmuyis,
The Bug has been solved.
Thanks to @oliuz

Thanks for the mention, I will try the install again


Windows support

Hi there. Are there any intentions of supporting the process of building tezedge on Windows?

Hi @mweichert, at the moment there are no plans for supporting Windows. In the meantime you could run TezEdge with Docker, or maybe WSL


Activation of Valueset Lookup Tables

Problem statement
Currently in the Valueset Editor UI, when someone edits or adds a row, that new version of the lookup table(s) is(are) automatically "activated" via a call to the Lookup Table API's activate endpoint:
PUT {{baseUrl}}/lookuptables/sender_automation_value_set[_row]/{{version}}/activate
In other words, we made the decision for MVP to only display the latest active version of the lookup tables in the UI, and any edits are automatically activated. However, a better understanding of the current use cases in and around activation should be investigated and better handled in the UI, if this current default handling is insufficient.
For example,

Are table versions only inactivated/re-activated in emergency rollback scenarios?
Are they sometimes left inactive to represent a "draft" or "in-development" version of a table, to be reviewed before being made active?
Are they sometimes left inactive in order to more precisely time their deployment?
Is this more important just for audit/archive capabilities?
All of the above?
None of the above?

This spike is to determine

Is the current default handling sufficient for our present needs?
If not, what use case(s) do we need to support, and how?

An important consideration here also relates to how we're currently representing valueset lookup tables. For MVP, we chose to represent all valuesets in one "master" lookup table, sender_automation_value_set_rows (with their parent records in sender_automation_value_set). What this means in terms of activation/de-activation is that the "versions" we're talking about here equate to the latest version of all valuesets at once, as a big set. There is a story in the backlog (#5909) to refactor this into a lookup table per valueset. If that story has been completed by now, that will greatly help guide the decisions in and around activations. In other words- is it even meaningful/useful to provide any control over version activation when the version we're talking about one version of all valuesets combined?
What you need to know

Valueset Editor Backend Architecture spike
Lookup Table API Enhancement stories: #5706 #5707 #5708
OG Design Doc

Acceptance criteria

[ ] Document findings on this ticket. Or, if extensive, on a new external doc
[ ] Recommend a general course of action and write supporting stories for design and/or implementation as needed
[ ] Unit tests as appropriate. Just kidding, there's no coding here, I just wrote that out of habit.

Hey team! Please add your planning poker estimate with ZenHub @ahay-agile6 @doug-s-nava @kevinhaube @sethdarragile6

this should likely be taken into account in any future Value Sets research. heads up to @fmccaf1 . If user testing doesn't bring up any of these issues, this card can be closed.

Labeled with "needs design" so @fmccaf1 and @drew-usds have visibility. Not sure if we did ValueSets usability testing or not, but if not, this can remain open. If we did, let's assess the outcomes for relevance of this ticket together!

Looks like usability testing was done by Andrea C. as one of her items on her last sprint. Here's the ticket - 6786 - , which is where findings are located.

Experience team has a new value sets issue/epic tracking our updates to Value Sets UI in #7904. Any other updates needed will be requested by O+O team a future date. Closing.


[Improvement][DOCS] Update EN doc

Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Please rebase master to fix conflict


kapp does not allow placing app resource into namespace resource belonging to the app

Relevant slack thread here: https://kubernetes.slack.com/archives/CH8KCCKA5/p1563362345098000
On a newly created cluster, with only default namespaces, I am attempting to install a new application in the demo namespace.
My workflow until now was to create a context pointing to the demo namespace and apply the resources. (i.e. DEMO_CONTEXT)
Example namespace resource
kind: Namespace
metadata:
  annotations: {}
  labels:
    name: demo
  name: demo

Error
When applying a simple namespace using kapp pointing to DEMO_CONTEXT, kapp fails with:
Error: Creating app: namespaces "demo" not found

Possible explanation
kapp seems unable to handle a context pointing to a yet-to-be-created namespace. Possibly because if needs to store some state there?
Workaround
using a context pointint to a different namespace, i.e. default, kapp is able to create the application successfully
Changes

Namespace  Name  Kind       Conditions  Age  Changed  Ignored Reason
-          demo  Namespace  -           -    add      -

1 add, 0 delete, 0 update, 0 keep

1 changes

2:44:26PM: --- applying changes
2:44:26PM: add namespace/demo (v1) cluster
2:44:26PM: waiting on add namespace/demo (v1) cluster
2:44:27PM: --- changes applied

Unfortunately, if after this bootstrap process we revert to using the original DEMO_CONTEXT, kapp finds a mismatch in the app ownership
cat  namespace.yml | kapp  deploy --kubeconfig-context demo_context -a pre-deploy -f - -y --tty
Error: Ownership errors:
- Resource 'namespace/demo (v1) cluster' is associated with a different label value 'kapp.k14s.io/app=1563371065560753000'

The only solution then becomes to force import the app --dangerous-override-ownership-of-existing-resources

recorded gist of our conversation in faq: https://github.com/k14s/kapp/blob/master/docs/faq.md#where-to-store-app-resources-ie-in-which-namespace

marking this as wontfix for now. may be we will circle back to this eventually.

I still think this is one of the only real shortcomings of kapp.  It should have an option to manage the namespace and create and destroy it automatically.  It should destroy it when the last app in the namespace is destroyed.

We also might need an annotation on the namespace as well and with the current setup I think you'd need to do that using kubectl.

related in a way: https://github.com/k14s/kapp/issues/112


Highlight particular route of multiple routes in google map

I want to hightlight the particular waypoints (route) from multiple waypoints in a google map.
For example in the below image, I want only need the route which is drawn line in red color. How to show/ highlight the certain route?

@mrajeshkrossark As I understand correctly, you can change route color globally for all paths together: https://stackoverflow.com/questions/19022702/how-to-change-the-color-of-route-in-google-maps-v3
There is a new version of this module at npm @react-google-maps/api Please consider to switch.

No, let I will explain clearly. I have multiple routes. So I have view
specific route button for every routes. If user selects particular view
then all other routes should be hide. Same for every routes. How to achieve
this?
On Wed 6 Mar, 2019, 1:28 AM Alexey Lyakhov<EMAIL_ADDRESS>wrote:

@mrajeshkrossark https://github.com/mrajeshkrossark As I understand
correctly, you can change route color globally for all paths together:
https://stackoverflow.com/questions/19022702/how-to-change-the-color-of-route-in-google-maps-v3
There is a new version of this module at npm @react-google-maps/api
Please consider to switch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomchentw/react-google-maps/issues/966#issuecomment-469835431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVwzgFGPzyqoyjnnA8QPI4B6cew6zmlVks5vTsx2gaJpZM4bcO7B
.

@mrajeshkrossark In new version of @react-google-maps/api you can make several  components, and assign to each renderer its own default color, show al of them by default, and hide those you don't need.

I just managed with the array collection of multiple routes.


Yarn support

Many users prefer Yarn over NPM, this PR adds support for it to Sail.
Yarn is added via apt and the sail.sh script has been modified to forward yarn commands to the container.

Aww I was hoping for something like this.

This probably should have been sent to 1.x


fix: manifest case

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

v2.3.1
GitHub release

Your semantic-release bot :package::rocket:


ng new fails - Package install failed, see above. ng serve fails - Cannot read property 'glob' of null

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Linux Ubuntu (docker node container)
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

@angular/cli: 1.0.0-beta.32.3
node: 7.5.0
os: linux x64
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

ng new myApp
The log given by the failure.

Normally this include a stack trace and some more information.

ng new myApp
ng new.txt
ng serve
serve.txt
Mention any other details that might be useful.
I don't think that I did anything special... just followed the directions.

Thanks! We'll be in touch soon.

It looks like #4207 is the same issue.  If you set up the environment in your home directory, it fails.  It's a common pattern in docker to put the app in the home directory.
Changing the home directory seems to resolve the issue.

https://github.com/angular/angular-cli/issues/4919 (there's more info there). I'll add your comment there as well.

I have tried the following option to resolve the issue
Steps to resolve the issue
$ pwd
it shows —> /Users/YourName /*** That is your Home path***/
Execute the below command to display the hidden files
$ defaults write com.apple.Finder AppleShowAllFiles true
$ killall Finder
After executing the above command you will see the hidden files.
if “.angular-cli.json” file exist under “/Users/yourname” (i.e Home Path) then remove “.angular-cli.json” file.
then navigate to your application path and try execute ‘ng’ command.

I had the same issue. I just deleted the .angular-cli.json file from my user directory and it resolved the issue.
To resolve this issue in Ubuntu, follow the below steps

cd /home/userName (provide the appropriate userName.)
ls -a
If you find .angular-cli.json. listed then  use the command
rm -r .angular*


Rename ASP.NET Core Error Reporting Entry Funciton to Match Style

The general style for adding to IApplicationBuilder is Use*.

Thanks Jon :)


Collapse icon in source code editor is too close to editor's content so that it's hard to put cursor at begining of line by clicking mouse

Issue Type: Performance Issue
When mouse is near the side bar, a collapse/expand icon appears. This makes it hard to put cursor at the begining of line. It might be better to put some padding space between content and editor's real border so that it's easy to put cursor there by clicking mouse.
Thanks,
VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:41.156Z)
OS version: Linux x64 5.13.0-39-generic
Restricted Mode: No

/duplicate of #135114


Image orientation in codestream, exif and xmp - clarification

Is this information correct?
If the optional Exif (or XMP) metadata says something that conflicts with what the codestream says, then a decoder has to ignore the Exif/XMP
Source - https://github.com/w3c/csswg-drafts/issues/4929#issuecomment-718849793
If that is the case than how should one implement lossless rotation (without image re-compression to update orientation in codestream)? For formats like jpeg, png, tiff all that is needed to be done is updating exif/xmp orientation. But that would not work for JPEG XL as one should also fix the value in codestream. Considering the complexity of codestream, that is not an easy task.
Are there plans for libjxl to implement such operations on codestream directly?
Thank you for clarification.
BTW heif and avif image formats have similar problem. Luckily the orientation there is not stored inside compressed bitstream but it is accessible through transformative properties in isobmff container itself.

That information is correct, yes.
The orientation is part of the image header in the codestream, which is not that complicated — you certainly don't need to implement a full encoder/decoder if you only want to change that field.
But yes, it's not super trivial and it would be useful if at some point libjxl would offer basic functionality for doing image header manipulations like that one. Orientation, intrinsic size, adding or removing a preview frame, tweaking ToneMapping info, stripping or changing an informative ICC profile or changing the nominal bit depth in case of xyb_encoded are some of the things that can be done just at the level of the image header (without any reencoding of pixel data), and I imagine they can all be useful. If we also allow frame header manipulations (without changing the actual frame data), even more things are possible, like reversible cropping, mild sharpening/blurring by adjusting gaborish weights, changing names of layers, changing durations or timecodes of frames.
We'll have to see to what extent it is sensible to have such functionality in libjxl, as opposed to a separate jxltran tool that does such things. @deymo / @lvandeve / @veluca93 opinions on whether e.g. changing image orientation is something that libjxl should do or not?

Thank you for clarification. Unfortunately I haven't found any traces of jxltran. Is it something to be developed in the future? I don't have a problem with having such a functionality in another library.
I have checked the codestream structure and to change orientation one must parse whole "Annex A Headers" and rewrite it from scratch.
Although "orientation_minus_1" occurs fairly early:

it is not always in the same bit offset because bit size of "SizeHeader" is variable
it is optional thanks to "extra_fields" / "all_default"
when "extra_fields" or "all_default" is 0 than to introduce "orientation_minus_1" one must also introduce some additional stuff after it in the ImageMetadata bundle

I do not say that it is some major obstacle. But I am bit worried if such a functionality is not easily available (in libjxl/jxltran) others (while integrating jxl ) might just give up and update the EXIF only. In the end the real word jxl will not be standard compliant. Rotating an image is one of the most basic operations users will do on files...

Opened https://github.com/libjxl/libjxl/issues/871
I think the concerns from this issue are reflected in that one, so we can continue discussion there. Closing this one.


make a "pure" orig.tar.xz for Debian

Hi @xylo04 - this isn't really a pull-request as much as an easy way to demonstrate how I ended up generating kel-agent_0.2.2.orig.tar.xz for the Debian packaging.

Good to know, thank you @tmancill. Might as well merge it!

Oh, but removing debian will prevent me from building my own .deb files for release here... Well, I can remove that part and keep the rest of the tar command.

Oh, but removing debian will prevent me from building my own .deb files for release here... Well, I can remove that part and keep the rest of the tar command.

Right.  I am thinking maybe we add add a separate target.  Maybe deb-orig-tarball - does that sound okay?

Yes! Sounds good
On Wed, Dec 23, 2020 at 3:09 PM tmancill<EMAIL_ADDRESS>wrote:

Oh, but removing debian will prevent me from building my own .deb files
for release here... Well, I can remove that part and keep the rest of the
tar command.
Right. I am thinking maybe we add add a separate target. Maybe
deb-orig-tarball - does that sound okay?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/k0swe/kel-agent/pull/21#issuecomment-750492023, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC7GU6U6O2DUHV7P5AYY53SWJTBVANCNFSM4VGQ7JVQ
.


Dnn 9.4.1 upgrade does not update versions table

Description of bug
Upgrading to 9.4.1 only shows the missing UpgradeWizard.aspx page after the upgrade.
Steps to reproduce
List the steps to reproduce the behavior:

Install 9.4.0
Upgrade to 9.4.1
Follow the wizard until it completes and click view site.

Current result
No way to see home page, we are always redirected to the now missing upgrade wizard and get an error page.
Expected result
Show show the site home page.
Additional context
In order to check if it needs to upgrade, Dnn checks the DotNetNuke.dll assembly version and compares it to the highest version in the Versions database tables. In this case, the latest found in the database is 9.4.0 but the dll is 9.4.1 so Dnn thinks it is due to fire the upgrade wizard.
I believe it is because there is no 09.04.01.SqlDataProvider file and the database updates the versions table when running the sql upgrade... I am not 100% sure but will now give it a try and submit a PR is that is the case.
Affected version

[ ] 10.0.0 nightly build
[x] 9.4.1 nightly build
[ ] 9.4.0 latest supported release

Merged


nulls in seekindex

@aousterh stumbled across this when using the id.orig_h as the pool key...
When the seekindex has nulls from records without pool keys or records with a pool key that has a null value, it punts.   The if-statement that rejects this case should be removed and the code that computes intersections over keyspans should be updated to handle nullsmax.
https://github.com/brimdata/zed/blob/7359b7de0f2989e809ba82b043dbb0586ef2dcb9/lake/segment/reader.go#L40
Replicate with:
zed lake create -p bug -orderby id.orig_h
zed lake load -p bug zq-sample-data/zeek-default/*.gz

Then you will see meta.last is null:
zed lake query -Z "from bug[objects]"

And this query will run slowly because the seek index isn't used:
zed lake query -z "from ip2 range <IP_ADDRESS> to <IP_ADDRESS> | id.orig_h == <IP_ADDRESS>"

Verified in Zed commit cf116a83.
Circling back to Zed commit 97cb737 that was right before the changes in the linked PR, here's the repro steps with current Zed syntax showing the baseline of the noted query slowness.
$ zed -version
Version: v0.30.0-63-g97cb7379

$ zed lake init
using environment variable ZED_LAKE_ROOT
lake created: /Users/phil/logs

$ zed lake create -orderby id.orig_h bug
pool created: bug 1z2wC7ygSUaxizuZ7WIXdy1UdAz

$ zed lake use -p bug
Switched to branch "main" on pool "bug"

$ zed lake load zed-sample-data/zeek-default/*.gz
1z2wHGW1HvqRvq7u7N0vWb7kqOn committed

$ zed lake query -Z "from bug@main:objects"
{
    id: 0x0de8c81c96307da996fbcc8051a0802ff372c000 (=ksuid.KSUID),
    meta: {
        first: <IP_ADDRESS>,
        last: null,
        count: 1462078 (uint64),
        row_size: 83899492
    } (=data.Meta)
} (=data.Object)

$ time zed lake query -z "from bug range <IP_ADDRESS> to <IP_ADDRESS> | id.orig_h == <IP_ADDRESS>" > /dev/null
real	0m1.920s
user	0m3.205s
sys	0m0.227s

But repeating the query at Zed commit cf116a83 that has the benefit of the fix in the linked PR, now it completes much faster.
$ zed -version
Version: v0.30.0-64-gcf116a83

$ time zed lake query -z "from bug range <IP_ADDRESS> to <IP_ADDRESS> | id.orig_h == <IP_ADDRESS>" > /dev/null
real	0m0.455s
user	0m0.586s
sys	0m0.055s

Thanks @nwt!


feat: Add :RubyBrowseGem

Create ruby command to get a gem and go to where the gem is hosted (rubygems)

If you wanna test this feature put on your plugin.lua the following command
  use {
    'vinibispo/ruby.nvim',
    branch = 'feature/ruby_browse_gems',
    ft = {'ruby'}, -- optional
    requires = {'nvim-lua/plenary.nvim'},
    config = function() -- optional
      require("ruby_nvim").setup({
        test_cmd = "ruby", -- the default value
        test_args = {}, -- the default value
      })
    end,
  }

@cuducos What do you think?

Ok, I'mma merge this @cuducos, so later could you try to refactor this to pattern matching?


Unit test cases.

Hi, I would like to take this issue. Do you think I can start by doing the DOT folder tests?

Hi, I would like to take part of this issue.
I'll start working with the tests in the DTO folder.

@laautarolopez Thanks for picking this up, I really appreciate. 😄

@r0hi7 The project is working on eclipse? or about what ide?

I did it in IntelliJ, but I am hopeful IDE wont be an issue.

Hello how are you? Lombok libraries are not working for me.
Do you have any idea how to make it recognize the getters and setters in the tests?

I have been using IntelliJ and they have a Lombok processor. Not sure about
the other. Can you check for your IDE ?
On Fri, Nov 27, 2020 at 1:48 AM Thomas Lautaro López <
<EMAIL_ADDRESS>wrote:

Hello how are you? Lombok libraries are not working for me.
Do you have any idea how to make it recognize the getters and setters in
the tests?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/r0hi7/TrashEmail/issues/34#issuecomment-734465808,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFBMCRTB2JXACFWDWQBTGODSR2ZZHANCNFSM4NZLM74A
.

I use Eclipse. I'll see if I can use Lombok. Thanks!

#72

I took a pull request. Can you see it?

#72

Hi @r0hi7,
I have pull request please check.

Thanks Rod, let me check in a day or two and take a step fwd.
On Fri, Apr 23, 2021 at 7:58 PM Rod Fetalvero @.***>
wrote:

Hi @r0hi7 https://github.com/r0hi7,
I have pull request please check.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/r0hi7/TrashEmail/issues/34#issuecomment-825697467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFBMCRSLV4MWD5BNVVALIADTKF7XXANCNFSM4NZLM74A
.


bug(ThemePalette): ThemePalette for Material 3

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Currently in some components (radio-button for example) the color is typed themePalette.
But themePalette only allows 'primary', 'accent' and 'warn' colors.
So if we try to use it with a Material 3 palette it is not possible to specify a 'primary', 'secondary', 'tertiary' and 'error' color.
color.ts contain
`/** Possible color palette values. */
export type ThemePalette = 'primary' | 'accent' | 'warn' | undefined;`
Reproduction
StackBlitz link:
Steps to reproduce:
1.
2.
Expected Behavior
ThemePalette Marerial 3 compatible
Actual Behavior
ThemePalette only Marerial 2 compatible
Environment

Angular: 17.3.1
CDK/Material: 17.3.1
Browser(s): all
Operating System (e.g. Windows, macOS, Ubuntu): all

Colors are different in M3, the spec has a whole new color system (https://m3.material.io/styles/color/roles). For example, accent does not exist in M3.
We have a mixin for backwards compatability that I would recommend taking a look at so you can keep your existing color variants but get to use M3: https://material.angular.io/guide/material-3#optional-add-backwards-compatibility-styles-for-color-variants

I know the "backwards compatability" mixin I use it !
But I want to develop a new full M3 compatability web site.

i tried this with the different color variants for ex: primary, secondary or tertiary and does not work. Always getting the tertiary with a custom theme that i generated
@use '@angular/material' as mat;
$theme: mat.define-theme();
.tertiary-checkbox {
@include mat.checkbox-color($theme, $color-variant: tertiary);
}

for me it works
I defined three classes
.tertiary-checkbox {
@include mat.checkbox-color($theme, $color-variant: tertiary);
}
.secondary-checkbox {
@include mat.checkbox-color($theme, $color-variant: secondary);
}
.primary-checkbox {
@include mat.checkbox-color($theme, $color-variant: primary);
}
In your html
...
...
...

it works, my bad.
I passed the wrong theme: $theme: mat.define-theme();
Instead I had to pass my generated theme.
thanks for the reply


Monitor jdkXXu-dev repositories for breaking changes on AIX

Updates and development (usually backports) for released versions of OpenJDK happen in jdkXXu-dev repositories which are periodically merged to a jdkXXu repo. This means that breaking changes can be caught earlier in the jdkXXu-dev repo than in the jdkXXu repo. Normally breaking changes should not be merged to the dev repo in the first place, but for platforms supported by Adoptium which are not build by OpenJDK, surprises can occur. I believe the only platform that fits this criterion at the moment is AIX, and an example of a 'surprise' failure is given below [1].
A solution to this issue would be to add a regular build for some subset of the dev repositories  on AIX. There is one dev repo for each released version, so it's likely too much fuss to build them all; I think building LTS versions should be sufficient. That would mean builds for the following repos:

jdk8u-dev
jdk11u-dev
jdk17u-dev

As my role is to support AIX on ppc, I am willing to regularly monitor these builds for failing output and create issues and fixes as needed.
More information on the merge schedule for jdk11u can be seen in the Timelines section of this page.

[1] The timing looks about right for this to have happened last December (2021) with an issue I was involved in resolving. I believe the merge on Dec 8 from 11u->11u-dev brought changes that broke the jdk11u build on AIX, then a build issue was reported on Dec 17th here which was later fixed.

We had a cautious amount of positivity to this in the PMC call today, but we felt that ideally we should maybe have a way of providing feedback direct to the OpenJDK community in the future.
For now I've implemented https://ci.adoptopenjdk.net/job/AIX-jdk11-dev-build/ for JDK11 only and set that to run on a timer to run daily except at the weekends. Note that this comes with a disclaimer that it's a best effort basis, it only runs a build, no tests, and we won't be monitoring it ourselves etc. - I'll look at modifying it later to support all three versions either as a multi-config job or as three separate jobs.
While it won't currently run any tests it would still be possible to pass the output from these builds into a Grinder job or similar to execute any suite we want - it may make sense to automate sanity.openjdk on these jobs at some point as a basic test. Let's see how it goes.
I'll keep this open for further discussion and until I've got it running for the other release lines.

Thanks for discussing this, and creating the build. I've set up an IFTTT to monitor for failures.
I can certainly understand that you would want feedback to go directly to the OpenJDK community. It would be a shame if I went on vacation, the build broke, and no one knew about it because I'm the only one checking. I'm not sure what form a solution to this issue would take, but I'm happy to work with the Adoptium team to find something better. For now, I will keep an eye out for any failures and create issues or email the OpenJDK mailing list(s) as appropriate.

FYI @sxa I've modifed the job to include  --custom-cacerts false (we likely want the build to use the default OpenJDK cacerts to stay as close to the upstream build process as possible)

FYI @sxa I've modifed the job to include  --custom-cacerts false (we likely want the build to use the default OpenJDK cacerts to stay as close to the upstream build process as possible)

Yeah I'm fine with that - I was planning to propose making that the default for hotspot builds as opposed to temurin along with removing any other temurin specifics that are still in there now that the split has been mostly working well.

The build failure on yesterday appears to have resolved itself, so I'm just some notes here for future reference. The build seemed to be proceeding normally when the last console message was printed at 16:14. The next line in the output comes at 23:56 and indicates that the build was killed by an 8 hour timeout. I wonder if it was paused, preempted and starved by higher priority builds, or otherwise blocked from continuing. Today's build succeeded.
The failing build log is here: https://ci.adoptopenjdk.net/job/AIX-jdk11-dev-build/11/consoleText

Closing as it's been complete for a while :-)


Allow skipping the use of the PYTHONNOUSERSITE variable

Motivation for this change
By default, Nix-installed Python binaries use the PYTHONNOUSERSITE variable (see here) to prevent Python from looking for packages in the user's site-packages directory.
I wanted to be able to install a Python installation that is slightly impure, so that you can run pip install --user some_package and then use the resulting package. This is convenient when you want to set up an environment where the user either can't install new Python packages via Nix, or would prefer to use pip directly (for example, if a package version isn't available on Nix).
So, this PR introduces a flag skipNoUserSite that can be used to disable the PYTHONNOUSERSITE setting when needed. The change happens in two places:

pkgs/development/interpreters/python/mk-python-derivation.nix and pkgs/development/interpreters/python/wrap.sh: the change here allows you to disable PYTHONNOUSERSITE for individual Python packages, i.e. those built by buildPythonPackage.
pkgs/development/interpreters/python/wrapper.nix: the change here allows you to disable PYTHONNOUSERSITE for Python environments, i.e. those created by python.withPackages. It causes every wrapped binary inside the environment to be user site-packages aware.

This flag is purely opt-in, so hopefully it's okay to add a little impurity for this use case :)
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Friendly ping on this @FRidh

I think it's good to go now? Is there anything I need to do to target staging?

Squash commits so we have two commits again, and then rebase onto staging.

Whoops are you sure I should have rebased onto staging? Should I change the target of this PR to staging or rebase onto master? (Sorry everyone who was just added for the spam)

@FRidh anything else I need to do on this one or is it waiting on more review? Thanks!

Friendly ping on this @FRidh , is it ready to land? Github is acting like there are changes requested but I think it's confused...

I haven't looked at this in a while. I'm away now until Thursday.
On Fri, Apr 19, 2019, 11:57 Tom McLaughlin<EMAIL_ADDRESS>wrote:

Friendly ping on this @FRidh https://github.com/FRidh , is it ready to
land? Github is acting like there are changes requested but I think it's
confused...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/51641#issuecomment-484835066, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQHZ32CPPP7GFQNGZPGXNTPRGJQDANCNFSM4GI6DG4Q
.

@FRidh could we push this one over the finish line? Thanks!

Commit titles are incorrect, it's PYTHONNOUSERSITE.

Fixed

In a followup commit, please explain the options in the Nixpkgs manual.

You mean a followup PR? I can't add a commit here since this PR was merged.

Created #61502


use Restyle instead of Update in scroll position -- fixes excessive layout with texteditors

for #1056 -- tested on android device native and it seemed smoother, though still not great.
@kkoreilly can you test on various web platforms?  it is too slow here at the hospital.

This is much much better on all web platforms!


fix/keccak-decode-overflow: calculate with bitshifts in u64

With KECCAK_DEGREE=19, get_num_bits_per_absorb_lookup() is 11. In some places, 2**3**11 overflows u32.
Replace with u64. Also use faster bitshifts like Axiom’s version.

That works, there is test in #326
 // The largest imaginable value does not overflow u64.
assert_eq!(get_num_bits_per_lookup_impl(3, 32) * BIT_COUNT, 60);

Maybe you were using profile "bench"? Or set k but not KECCAK_DEGREE?
debug-assertions = false
overflow-checks = false


Command-line flag to change model target or environment

Requested feature: Command-line flag to change model target or environment
Use case: Proving certain errors don't happen on non-host targets
I have code that does some operations done that I believe could overflow, but only with a 16-bit usize. I wish to support this case, and use kani to check whether it does occur, and when I expect it to. The covered condition is reported UNREACHABLE on my 64-bit host, as expected.
Link to relevant documentation (Rust reference, Nomicon, RFC):

https://doc.rust-lang.org/stable/reference/types/numeric.html?highlight=16-biit#machine-dependent-integer-types
https://doc.rust-lang.org/stable/reference/conditional-compilation.html?highlight=target_poi#target_pointer_width
The only 16-bit in-tree target, msp430-none-elf

Our use-cases:
Verifying Endian-Dependent Code
The zerocopy crate provides byte-order aware abstractions over the numeric types. Kani is used to prove that these abstractions are correct on little endian targets. With this feature, Kani could be used to verify that these abstractions are also correct for big endian targets.
Verify Complex Harnesses By Reducing Pointer Width
The zerocopy crate hopes to expand its use of Kani to verify the correctness of critical routines that operate over usizes. Unfortunately, the most natural ways to express proofs for these routines encounters catastrophically bad verification performance. However, these harnesses complete in reasonable time when usize is replaced with u16. Unfortunately, cannot make the routine-under-verification generic over numeric type (because these are const functions, and such functions cannot have bounded generics) --- we would need to duplicate-and-modify the routine-under-verification.
If Kani permitted verification on alternative targets, we could leave our routine and harness as-is, and merely run verification using a target with reduced pointer size.

We need to update our documentation for supported architectures.
Please see https://model-checking.github.io/kani/install-guide.html for a list of supported architectures.


Which branch version for 5.7.0?

I am trying to build AOMP for ROCm 5.7.0. However, the branches are a bit confusing.
The latest AOMP version appears to be 18.0-0 found in branch aomp-18.0-0. When I select branch rocm-5.7.x released after aomp-18.0-0 it appears to be using AOMP 11.5-0 which released many years ago?

Refer to issue #695 for more detailed instructions on building openmp support for ROCm 5.7.


Warn about duplicate dependencies

Add duplicate-package-checker-webpack-plugin as proposed here: https://github.com/facebookincubator/create-react-app/issues/1844.

Since this is just a warning, I don't think we have to consider it breaking. /cc @gaearon

I have two slight issues with this pull request, maybe someone can help me out.
I noticed that warnings are not being displayed when building. The solution would be to display any warnings from react-scripts/scripts/build.js.
The second issue is that the tests for kitchensink are failing since babel-runtime is duplicated in the bundle and the tests fail on compilation warnings:
Warning in duplicate-package-checker:
  <babel-runtime>
    6.20.0 ./~/react-dev-utils/~/babel-runtime from ./~/react-dev-utils/~/stack-frame-resolver/lib/index.js
    6.23.0 /Users/Darren/projects/create-react-app-bk/packages/babel-preset-react-app/~/babel-runtime from ./src/features/syntax/ArraySpread.js

After some digging, it appears that in the kitchensink, two different babel-runtime versions are being included, one in the main chunk and one in the features/syntax/ArraySpread.js chunk.
Any suggestions?

You can bump stack-frame-resolver to 0.1.4 or switch this PR to the 0.9.x branch, both should fix the problem.

Created new PR to the 0.9.x branch #1866 . Closing this PR.

@Timer can you add tags and milestone to the other PR please?


major: Delete Core's helpers

Deleting Core's helpers to reduce dependencies in Core which is later scheduled to be deleted.
Core's helpers are now available at https://github.com/balena-os/test-helpers
Signed-off-by: Vipul Gupta (@vipulgupta2048) <EMAIL_ADDRESS>

I would merge this only after https://github.com/balena-os/meta-balena/pull/3091 is merged - as you probably already know but just posting it here for visibility

will we have to change this as well https://github.com/balena-os/leviathan#documentation-for-leviathan-helpers

Done, good spot


a is not a constructor at g.value

Hello,
I have an issue using tooltip and popper js in a flask web page.
I use : python for backend, jinja2, html, js
this is my import:
<script src="https://unpkg.com/popper.js/dist/umd/popper.min.js"></script>
<script src="https://unpkg.com/tooltip.js/dist/umd/tooltip.min.js"></script>

 eventRender: function(info) {
                 var tooltip = new Tooltip(info.el, {
                        title: "info.event.extendedProps.description",
                        placement: 'top',
                        trigger: 'hover',
                        container: 'body'
                      });
            },

its suppose to be a very basic function but i got a wierd bug:
the tooltip elem is created in the html when hovering on it but i got this error:
Uncaught TypeError: a is not a constructor
    at g.value (index.js:246)
    at index.js:381

referencing
    this.popperInstance = new Popper(
      reference,
      tooltipNode,
      this._popperOptions
    );

if someone as an idea

Thank you for your issue.
Unfortunately I can't answer to all the reported issues without a little help from you.
Please, make sure to follow the issues template when you submit a new issue, in this way I will already have all the informations needed to understand the problem and help you with it.
I'm closing this issue for now, but feel free to open a new one making sure to follow all the instructions!
Thank you for your understanding.

I was experiencing this same issue. Make sure both scripts are fully loaded before trying to create a new popper instance.
Hope this helps!


[TF 2.0] tf.summary step argument should cast to int64

The TF 2.0 versions of tf.summary.scalar(), image(), etc now require a step argument at the callsite. This step argument should allow at least any integral type and probably also floating point types (at least if they have no fractional part), but it currently requires a python integer or a tf.int64 tensor.
This results in errors like:
tf.summary.scalar('foo', 22, step=tf.constant(1))
...
ValueError: Tensor conversion requested dtype int64 for Tensor with dtype int32: 'tf.Tensor(1, shape=(), dtype=int32)'

tf.summary.scalar('foo', 22, step=1.0)
...
TypeError: Cannot convert provided value to EagerTensor. Provided value: 1.0 Requested dtype: int64

pleasecan i contribute to this @nfelt. Can you guide me

Hi @nfelt! This issue seems to be resolved in latest stable version TF 2.6 , Attaching Gist for reference.

I was able to reproduce this issue in TF Nightly 2.12.0.dev20221215. Please find the gist here. Thank you.


Bad network: Not a valid NetParameter: 19:16 : Couldn't parse integer: [

I found this error when I ran a network in digits.Maybe it is a bug?
the error placce at:
layer {
  name: "data"
  type: "Data"
  top: "data"
  top: "label"
  include {
    phase: TRAIN
  }
  transform_param {
    mirror: true
    multi_scale: true
    fix_crop: true
    crop_size: 336
    scale_ratios: [1.0, 0.9375, 0.875, 0.8125, 0.75, 0.687, 0.625]
    max_distort: 2
    mean_value: [105, 113, 116]
    more_fix_crop: true
  }
  data_param {
    source: "places3_train_standard_384_lmdb"
    batch_size: 32
    backend: LMDB
    shuffle: true
  }
}

I don't think protobuf likes those square brackets. Try something like:
    mean_value: 105
    mean_value: 113
    mean_value: 116

And I don't think this scale_ratios exists (at least not in nv-caffe 0.15).

@gheinrich yeah,scale_ratios does not exists in nv-caffe. Adding support for '[' is just my advice ~


Publish Antora Doc with multiple sources

Hello
I try to publish in Confluence an Antora documentation that contains multiple sources in the playbook. This sources are differents Gitlab projects.
Actually, with the basic configuration, I can only publish the doc of the first source of the list. I didn't find an option to publish the whole documentation.
Is it normal ? Is the option to publish a doc with multiple sources is in the roadmap ?
By the way, thanks for this plugin that will save me a lot of time !

Hey @TitouanM  thanks for this issue. I Would like to re-open it to keep track on that. I assume you ran into an issue that Confluence rate limited you, right? Maybe it makes sense to handle throtteling also at Captain level :)

Hey
Yes, I think that the possibility to use a throtteling could be nice !


Abecedarium Activity: Unexpected behaviour with language change button

Hey @llaske , i have found a functionality break in Abecedarium Activity ,  tutorial popup is been visible but the "Change Language" button is not visible there(mainly "Country flag" image on button is not displaying). In the last screen i.e. Game Finished Screen, initially the "Change Language" button is not visible. But when i switch to full-screen mode and return back to normal mode, "Change Language" button starts appearing which is not the expected behavior. Also clicking the ( "Country flag" image) button show unexpected popup,
Please find the attached video for reference:
https://user-images.githubusercontent.com/81116984/223954325-4494c59b-b3b3-4e6e-bb64-ffa3b20fa7d6.mp4

Hmmm. It is unlikely that an user click on the help button here. It's not blocking. Not an issue.

But if we turn off the full screen mode , the langauge button shows up, And if user clicks it is show unexpected popup
See

Yes you're right. Good point.

Fixed in https://github.com/llaske/sugarizer/pull/1328


SVG files from /svgs don't load correctly in Sketch and Illustrator

SVG files under /svgs and src/svgs are not equivalent and as a result the assets under /svgs don't load correctly in Sketch and Illustrator

This has been "fixed" in 2.1.0. You should use the SVG files from within src/svgs.


Allow to define an additional instance redis prefix.

This additional namespace gives more flexibility when it comes to handlind hundreds or thousands of matrices.

Hey Christoph,
Thanks for using the library!
However, how is this different than the redis_prefix option that's already supported?
class CourseRecommender
  include Predictor::Base
  redis_prefix "courses" # => "predictor:courses:users:items:user1"
  redis_prefix { "courses_for_user-#{User.current.id}" } # => "predictor:courses_for_user-7:users:items:user1"
end

The redis_prefix is on class level. Given i instantiate 2 recommenders, and i want them to work an different namespaces. What can i do? I would either define 2 classes, with the same code, which is not DRY. Or i try to hack some meta programming, to change class variable. But then the code is not thread safe anymore. So i want to do something like this:
s1 = Shop.first.id
s2 = Shop.last.id
r1 = Recommender.new(s1)
r2 = Recommender.new(s2)

# => FORK off in background workers with sidekiq

w1 = Worker.new(r1).process!
w2 = Worker.new(r2).process!

So each worker can now compute recommendations on a separate namespace per shop. This would be be possible with class level namespace.

Ah yes, I see. Totally seems reasonable, but I'm wondering if we can make some 'tweaks' to the existing support to satisfy this case (without adding an extra constructor option).
It may take me until Friday (our day to work on open source software) to get back to you on this, but I'll follow up by then at the latest!

Well, the constructor is up the person writing the recommender class. It can also be a setter, or a db lookup. Essentually, the instance method get_redis_prefix has to be overriden.

Yep, I totally just glanced at this last time and mistook your example as a hard change. This looks good, so I'll merge. Thanks!

Awesome, thx.


add support for getting an object representing a map from field names to values

As part  the work to implement support for a predicate querystring parameter to filter through VOLAPI's ListVolumes' results, I needed a way to validate the input predicate.
Adding a method on the Predicate's class prototype named fieldsAndValues() that returns an object representing a map from field names to values would allow me to iterate through this map, get the validation function corresponding to each field name, and call that validation function for each value used for that field in the input predicate.
This would take the following form:
var types = {
    'hostname': 'string',
    'latency': 'number'
};

var input = {
    'or': [
        { 'eq': [ 'hostname', 'spike' ] },
        { 'gt': [ 'latency', 300 ] }
    ]
};

var predicate = krill.createPredicate(input, types);

/* Output the map between field names and their values */
console.log('field names to values: ' + predicate.fieldsAndValues());
/* Prints: { hostname: [ 'spike' ], latency: [ 300 ] } */

Does that sound useful?

Fixed by 7c5efeaa13ec5dcdd63aaf198bf6d8623ce27a4d.


Render diffs

Howdy,
At the moment the react-blessed renderer is recreating the tree with each render call, this differs from react-dom which attempts reconciliation with the dom rather than stamping over it (too much). This means that you can't use top-down data-flow with react-blessed as each render call effectively recreates the entire tree, and, actually, I've noticed a hefty slow down after repeatedly calling render, is there also a clear-up issue?
Am I right with this thinking? And is there a quick-win using one of the component update lifecycles to stop react-blessed from recreating everything each render?
I've stuck a side-by-side with react-dom in this repo, the blessed and browser files are near identical and they just render a list of items, the react-blessed one remounts (which I'm assuming means its recreating) the list each render whereas react-dom reconciles and should just be performing 2 dom ops (unhighlight old selected node, highlight selected node). I think.
Are there any plans to support working out the minimum amount of mutations required for blessed? I had a quick look and I'm guessing it is not an easy task as the blessed components have a richer public api than the dom generally does. Any ideas how to get unidirectional data shizzle working without having to totally recreate the diff-application algorithm?

can we prevent renders with componentShouldUpdate with react-blessed ?

I guess so. Never tried it though. @revolunet maybe your issue with the list comes from this. @mattstyles there is probably a bug somewhere in my code that implies remounts (or maybe I was lazy and did not properly diffed somethings).

any news on this? i'm getting a ton of complete redraws with distracting blanking when a list of items is being updated

Hum... I don’t remember the specifics of the problem very clearly right now. As I recall the upgrade to latest reconciler logic did something bad but I cant be sure. Unfortunately I don’t have much time right now to investigate. Will definitely review any related PR though. Else you can try to ping me in two weeks when I can find more time.


Can't change video quality

When attempting to use -q to assign quality the video still uses the default (which is the highest available). Judging by a quick look through the code I think this is because the quality isn't passed on to the download function properly

Hmm. I remember having issues with the quality flag. Let me look into it and I'll get back to you.

see my note in #47 that may fix the issue (not tested)

Hopefully this is taken care of in #49. If not please feel free to re-open!


Add num_blocks metric

Motivation
Useful metric to have
Proposal
Implement it
Test Plan
Will update after testing

#1949  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @andresilva91 and the rest of your teammates on  Graphite


Bugfixes: Allow any of the deployment types to be used, fix spurious errors on services

This PR fixes two issues I encountered while trying out kubeaudit:

When using another deployment type than the one specified in types.go, checks would silently fail.
When running kubeaudit on a type not known to it (Such as, for example, running kubeaudit -f <service yaml>), you'd get an incorrect error that automountServiceAccountToken: false needed to be set.

@luna-duclos Thanks for the PR. I had some concerns regarding two new deployments types. Since k8s api wants to deprecate use of v1beta1 and v1beta2 and just use v1 in future (more reference https://kubernetes.io/docs/reference/workloads-18-19/ ). So it would be a good idea to warn users if they are using v1beta1.

@luna-duclos  If you want to get k8s version you can use the same function as one of the subcommands https://github.com/Shopify/kubeaudit/blob/master/cmd/version.go and warning according to version of k8s would be really awesome. :smile:

I'd prefer perhaps not adding this as part of this PR, It's more complicated than it looks since there might be no cluster setup at all. Would that be ok ?

I think the code is much better now, errors are handled generically in each audit, and getResources will only return resources it knows are supported.
I did leave newResult calls into the loop however, since a new result object is needed to be appended into the results slice that is returned.

What would be the best way to add tests for this ?
Should I add some a v1beta2 deployments and an extensions/v1beta1 deployment yml to the fixtures and then add tests for those ? Would that be sufficient ?
Perhaps also a Service to validate those are properly skipped ?

What would be the best way to add tests for this ?

Create *v1beta*.yml fixtures in fixtures and take a look at https://github.com/Shopify/kubeaudit/blob/master/cmd/autofix_test.go or https://github.com/Shopify/kubeaudit/blob/master/cmd/cronjob_test.go and do something similar, just so that you can validate that the workload manifests are properly translated.

Should I add some a v1beta2 deployments and an extensions/v1beta1 deployment yml to the fixtures and then add tests for those ? Would that be sufficient ?

That sounds good to me!

Perhaps also a Service to validate those are properly skipped ?

If you want to, that'd be great!

@klautcomputing I changed some of the current fixtures so they vary between all 3 available deployment types, would that be sufficient ?
I also added an unknown_type fixture and validated it was properly skipped when getting manifest files.

Sorry for not taking care of this way earlier! Thanks again for all your work. 🙂

Thank you for getting to it! :)


Bump resources on the mirror scraper

We're seeing this job not run to completion, with errors such as:

Jan  9 01:57:22 ip-10-13-29-166 kernel: Memory cgroup out of memory: Killed process 2720094 (govuk-mirror) total-vm:13084964kB, anon-rss:8341956kB, file-rss:9092kB, shmem-rss:0kB, UID:1001 pgtables:23380kB oom_score_adj:922

Bumping the memory limits to see if it'll finish with a few more resources.
The nodes that this runs on should have plenty of head room to cope with this.

Thanks @theseanything 🙏


Reword work shift reminder emails to make arrival time more clear

From Syndallas:
"The reminders are good. Thank you.  But, maybe the reminder for the assistant cook shift should be reworded so it is clear the worker should arrive at 4pm rather than 6:15pm.
This announcement makes it sound like the worker should arrive at 6:15pm"
This is a reminder that you are scheduled as Assistant Cook for a meal by Jennifer Janssen on Tue Dec 1, 6:15pm at Great Oak Common House.
Your help is crucial! Please arrive promptly for your shift!
I don't know what time the TS and SW workers should show up, but at GO it has been 4pm since the dawn of our meals program.
Originally created by Willie Northway at 2015-12-01 03:45, migrated from redmine-#3698

We've had a request from TS to update this too. I'm going to implement it as
an optional "additional text" field that can be set per-community. I think we
should still publish the serving time of the meal, since it may not be the
same for all communities or meals (we have morning brunches).
Just waiting on Deb for some text and then I'll get it done, should be next
week.
By Tom Smyth at 2016-03-03 07:45

On Mon, Feb 15, 2016 at 9:14 AM, Robby Griswold
<EMAIL_ADDRESS>wrote:
hey there,
I'm looking and looking and can't find the description that tells me what time
I need to report to the CH Kitchen for my assistant cook shift tomorrow. Could
someone tell me?
By Willie Northway at 2016-02-17 08:25

Priority changed from 4 to 3

Katie has just commented on this as well:
"This says my assistant cook shift is at 6:15 - it should say that it is from
4-6:15. Of course, I know the hours of an assistant cook shift - but new
members might not.
Ironically, the email says, "Please arrive promptly for your shift!". But then
doesn't give an accurate start time."
By Willie Northway at 2016-06-26 19:33

Priority changed from 3 to 2

From Tammy:
4:13pm He (she?) is one of my assistant cooks tonight and hasn't arrived. I
don't
know how to contact them, anyone have a phone number? Thanks.
4:30pm No answer, and the name on the voice mail is someone other than Gaz.
Might need some help setting tables later, if anyone is available..."
From Mary King:
"Gaz showed up for his cook shift tonight...at 6:15pm! That's because the
email reminder he received listed the time for his shift as 6:15. He was
bummed because he was excited to work his first shift."
I suggest just doing the math and telling assistant cooks to show up 2 hours
15 minutes before, and cleaners 45 minutes after the dinner is served. I'm
happy to come up with some language if necessary.
By Willie Northway at 2016-09-07 04:15

Status changed from New to Cancelled

This is now a duplicate of #5067. I want to kill multiple birds
with one stone here. Sometimes folks are forgetting to reserve both kitchen
and dining room, you've had issues with the auto dining room booking being
overzealous, then the shift time thing, they are all related. See 5067 for
what I mean. So cancelling this one.
By Tom Smyth at 2016-09-08 06:04


Issues when installing repository in container

Hi, I follow the instructions and when comes the moment of running the model I get the following error
File "<string>", line 1, in <module>   File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module     return _bootstrap._gcd_import(name[level:], package, level)   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import   File "<frozen importlib._bootstrap>", line 983, in _find_and_load   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked   File "<frozen importlib._bootstrap_external>", line 728, in exec_module   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed   File "/opt/seft-hypoxia/seft/cli/fit_model.py", line 13, in <module>     from seft.training_routine import TrainingLoop   File "/opt/seft-hypoxia/seft/training_routine.py", line 12, in <module>     from .callbacks import (   File "/opt/seft-hypoxia/seft/callbacks.py", line 8, in <module>     import tensorflow_datasets as tfds   File "/opt/virtualenvs/seft-NyYu6qKP-py3.7/lib/python3.7/site-packages/tensorflow_datasets/__init__.py", line 51, in <module>     from tensorflow_datasets import __init__py3 as api   File "/opt/virtualenvs/seft-NyYu6qKP-py3.7/lib/python3.7/site-packages/tensorflow_datasets/__init__py3.py", line 43, in <module>     from tensorflow_datasets.core import tf_compat   File "/opt/virtualenvs/seft-NyYu6qKP-py3.7/lib/python3.7/site-packages/tensorflow_datasets/core/__init__.py", line 21, in <module>     tf_compat.ensure_tf_install()   File "/opt/virtualenvs/seft-NyYu6qKP-py3.7/lib/python3.7/site-packages/tensorflow_datasets/core/tf_compat.py", line 63, in ensure_tf_install     "This version of TensorFlow Datasets requires TensorFlow " ImportError: This version of TensorFlow Datasets requires TensorFlow version >= 2.1.0; Detected an installation of version 1.15.3. Please upgrade TensorFlow to proceed.
My environment is a singularity container based on ubuntu docker image with python 3.7.4
I installed poetry using pip3 install, as it was the only  way I found to make poetry persistent in the container.

Hey Daniel,
sorry for the delay. It looks like tensorflow datasets is not correctly specifying its dependencies (the dependency on tensorflow is only included in the tensorflow extra - a bit strange imho).
Thus, poetry (which is run under the hood even when installing with pip) has no chance to understand that it should not install the most recent version of tfds in order for everything to run correctly. Adding an additional dependency to pyproject.toml fixes the issue. I will push an updated version in a second.
Hope that helps!
Cheers,
Max


version bump

@DvirDukhan why bump to 2.0.4 if 2.0.3 was not released yet?

ok
so let's release master as 2.0.3

I guess it should be 2.1.0 (since we have new feature)


Real-time volume performance monitoring

The real time performance should be shown in the volume's detail page.

Related to https://github.com/rancher/longhorn/issues/82

Related to #677

It's a part of #1180


Refuses to flash zshark firmware

The filename version check fails for the zshark firmware unless it is renamed to ./zshark_conbee2_v1_0.0x0.bin.GCF to contain 0x0. Works just fine after renaming.

Good find, GCFFlasher should only look in the file signature header, filename checks were a silly idea :)


Fix encoding error when printing messages

Short Description:
Some messages that will be printed will contain utf-8 chars, e.g. Pokestops in European locations.
Fixes:

Printing messages that contain special chars, e.g. Pokestops in Europe.

thanks!


Could not  uninstall catalog with helm2

Bug Report
What happened:
Could not uninstall catalog, got this error:
Error: Job failed: BackoffLimitExceeded

this log is from cleaner job:
kubectl logs -f catalog-catalog-pre-delete-clean-job-s4xnr -n catalog
I0220 05:34:57.051409       1 hyperkube.go:192] Service Catalog version v0.3.0-beta.2 (built 2019-11-05T19:03:03Z)
Error: failed to scale down controller manager: cannot get deployment catalog/catalog-catalog-controller-manager: the server could not find the requested resource

What you expected to happen:
catalog is uninstalled
How to reproduce it (as minimally and precisely as possible):
Install catalog following this file
values file:
image: registry.bluven.me:5000/bocloud/service-catalog:v0.3.0-beta.2

apiserver:
  resources:
    requests:
      cpu: 100m
      memory: 128Mi
    limits:
      cpu: 100m
      memory: 128Mi
  storage:
    etcd:
      image: registry.bluven.me:5000/bocloud/etcd:v3.3.12
      resources:
        requests:
          cpu: 100m
          memory: 256Mi
        limits:
          cpu: 200m
          memory: 256Mi
controllerManager:
  resources:
    requests:
      cpu: 100m
      memory: 128Mi
    limits:
      cpu: 200m
      memory: 128Mi

The values file is used for catalog 0.2.0, I didn't changed according to 0.3.0 values.yaml, but it seems ok, anyway catalog was installed.
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:12:17Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}

service-catalog version:
0.3.0-beta.2

Cloud provider or hardware configuration:

Do you have api aggregation enabled?
Not sure.

Do you see the configmap in kube-system?

➜  catalog git:(f950e68) ✗ kubectl get configmap -n kube-system
NAME                                 DATA   AGE
calico-config                        4      2d23h
catalog.v1                           1      26m
coredns                              1      2d23h
extension-apiserver-authentication   6      2d23h
kube-proxy                           2      2d23h
kubeadm-config                       2      2d23h
kubelet-config-1.17                  1      2d23h
mysql-operator.v1                    1      126m
redis-operator.v1                    1      123m

Does it have all the necessary fields?

kubectl get cm -n kube-system extension-apiserver-authentication -o yaml and look for requestheader-XXX fields

  requestheader-extra-headers-prefix: '["X-Remote-Extra-"]'
  requestheader-group-headers: '["X-Remote-Group"]'
  requestheader-username-headers: '["X-Remote-User"]'

Install tools:

Did you use helm? What were the helm arguments? Did you --set any extra values?
helm2.

Are you trying to use ALPHA features? Did you enable them?
Basiclly default features.

It seems the cleaner command used AppsV1beta while the actual depolyment is under Apps/v1 api group:
deployment, err := c.client.AppsV1beta1().Deployments(namespace).Get(controllerName, v1.GetOptions{})

kind: Deployment
apiVersion: apps/v1
metadata:
  name: {{ template "fullname" . }}-controller-manager
  labels:
    app: {{ template "fullname" . }}
    chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
    release: "{{ .Release.Name }}"
    heritage: "{{ .Release.Service }}"

@bluven, is it fixed already? I'm experiencing exactly this issue with v0.3.0-beta.2.


bug(mat-select): selected options removed when filtering and selecting options

Reproduction
https://stackblitz.com/edit/mat-select-filtered
Steps to reproduce:

Select 1+ options
Search for an option which is not selected
Select the option
Clear search

Expected Behavior
Previous selected options are kept
Actual Behavior
Previous selected options are not selected anymore
Environment

Angular: 10.0.1
CDK/Material: 10.1.0

Duplicate of https://github.com/angular/components/issues/9038.

@crisbeto I am not sure its a duplicate of that issue.
The problem is not that its not emitting the values, but rather of not keeping them after options changed.

The underlying issue is the same: options aren't removed from the selection when they're destroyed. The selection matches up with the model value.


Add a mechanism to ignore input to the controller

When not visible, input queue must not be filled or it's only once visible that it gets processed.
Currently, this results in a 'replay' which is clearly not what we want.

1678ccaf54f74ed46f8c4f3f68469ef2dde93cb2


check if a .pem file is empty and alert user

Check if a user uploaded .pem file is empty and alert user if it is.
Was able to upload and get an alert on the signin page without having to create an account.

For issue: [Edge Case] Handle the Empty file Upload #104

I added this file to the new PR with both the updates to  Login/index.jsx and Dashboard/dashboard.jsx
This one can probably be closed.


Support unique_together with RandomCharField

AutoSlugField already supports unique_together through find_unique() in UniqueFieldMixin.  Add support for unique_together in RandomCharField as well by checking for the attribute name in unique_together before short-circuiting find_unique() there.

Coverage decreased (-0.06%) to 71.143% when pulling 42008d6db5929a1062e6ca9ca08c139755df293a on swt2c:random_char_unique_together into afa8f0c242126197ca0e1eaf9d1c226e615a013b on django-extensions:master.

Coverage decreased (-0.06%) to 71.143% when pulling 42008d6db5929a1062e6ca9ca08c139755df293a on swt2c:random_char_unique_together into afa8f0c242126197ca0e1eaf9d1c226e615a013b on django-extensions:master.

Thanks !!


Players

I use the latest MyPlot Version.
Pocketmine 3.11.2
Player can destroy the rand of a plot.
Rand=Stoneslap

Building on the plot's border is a new feature in version 1.6.7 and was mentioned in the changelog. See also #248


python310Packages.zwave-me-ws: 0.3.1 -> 0.3.6

Diff: https://github.com/Z-Wave-Me/zwave-me-ws/compare/refs/tags/v0.3.1...v0.3.6
Changelog: https://github.com/Z-Wave-Me/zwave-me-ws/releases/tag/v0.3.6
Description of changes
Related to #216168

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 223264 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.zwave_me
python310Packages.zwave-me-ws
python311Packages.zwave-me-ws


Fix b option

Coverage remained the same at 89.235% when pulling 17856bc8c630640bd23f1646211655c26105456a on fix_b_option into 633e51f906164a775de2e3395454c8e3f092455e on 0.30.


(WIP) Test for parallel qc crash

Presently unable to reproduce the failure in #2330 using multiprocess but I figured it would be useful to get some extra eyes on this.
Using multiprocess with 6 processes generating 300 reports fails to trip this bug.
@jcohenadad any thoughts on how to increase our chances of encountering the bug? It is possible I'm generating the reports wrong, or perhaps two different reporters need to be used.

@cfhammill I am able to get it crashed using your test, see here. Note that it does not fail all the time (see below). I am running 64f99eaa8ec7c3e1b223cc84bf1f9410e1463462.
Further info:

Regardless the number of iterations and jobs, the test always crashes. E.g., I used that config and the test crashed:

    with multiprocessing.Pool(2) as p:
        p.map(gen_qc, range(5))

However, when running the test another time, it always passes. It is only if I manually remove the /tmp/qc folder that the test crashes again.
I am running on an OSX Mojave. Are you an Linux?  Maybe it is an Apple file system specific issue?

@jcohenadad yes I was running on ubuntu 17.10, so maybe it is file system specific. I started at two cores parallelism and 100 trials and worked my way up, periodically clearing /tmp/qc. Also passes on my 18.04 running under windows subsystem linux.
Looking at the travis results, there's a failure on Ubuntu 14.04 that seems independent of the problem (I think it's mad that I pool mapped a function with no return value), and failing on mac high sierra (although passing on mojave). Seems suggestive that this is a mac specific problem.
I don't have a mac to test on unfortunately, but I can implement the fix suggested in #2330.

It fails on 18.04 in the next push: https://travis-ci.org/neuropoly/spinalcordtoolbox/jobs/659871081?utm_medium=notification&utm_source=github_status
I don't know if I'm satisfied this test triggers the bug reliably enough, @jcohenadad what do you think? Should I invest more time making the test robust or just go ahead and try the fix?

hum... i would say, try the fix. Even if the test fails with 20% probability, we do so many pushes that i'm sure within days it will fail again (if the fix does not work).


making constraints more generic

See #637 for reference. Changes since I made that PR

I did make Key and Value constraints more generic. It wasn't too hard.

I got UnaryTCConstraint working with Const[Foo]#ƛ and Generic. When I say "I got" what I really mean is whatever changes you all made unbroke it.

I'll close #637.

I take it back, guess it only works on later Scala versions...

Thanks, I'll get to this later. Unfortunately the diff looks larger than it actually is.

Just sanity checking ... are all the old tests preserved by this PR? It's hard to tell given the file reorganisation.
If yes, then LGTM!

Just sanity checking ... are all the old tests preserved by this PR? It's hard to tell given the file reorganisation.

Yes, and more added on top.
The diff can be seen comprehensively in Intellij if we rename the file to the old name.


Create February 2024 crawl release

@katehausladen, it may be good to create a February 2024 crawl release just like you did for the December 2023 crawl.

Done!


Ignoring url using the trace-ignore-plugin plug-in throw a  java.lang.NullPointerException

Bug

Which version of SkyWalking, OS, and JRE?
OS:CentOS Linux release 8.2.2004
JAR :openjdk version "1.8.0_252"

What happened?
Ignoring url using the trace-ignore-plugin plug-in throw a java.lang.NullPointerException

/apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/context/ContextManager.java

    /**
     * Recommend use ContextManager::stopSpan(AbstractSpan span), because in that way, the TracingContext core could
     * verify this span is the active one, in order to avoid stop unexpected span. If the current span is hard to get or
     * only could get by low-performance way, this stop way is still acceptable.
     */
    public static void stopSpan() {
        final AbstractTracerContext context = get();
        // Throw NullPointerException
        stopSpan(context.activeSpan(), context);
    }

error log
2021-04-02 10:55:03,218 [TID:Ignored_Trace] [XNIO-1 task-1] [com.demo.home.HomeController] [INFO] - I am hello. log4j
2021-04-02 10:55:03,220 [TID:N/A] [XNIO-1 task-1] [org.jboss.threads.errors] [ERROR] - Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
java.lang.NullPointerException
	at org.apache.skywalking.apm.agent.core.context.ContextManager.stopSpan(ContextManager.java:199)
	at org.apache.skywalking.apm.plugin.undertow.v2x.SWRunnable.run(SWRunnable.java:47)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:2019)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1558)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1449)
	at java.lang.Thread.run(Thread.java:748)

This may be a bug of webflux. Ignoring plugin has not relationship with this npe.

This is a repeat problem.
Hope to fix it.

This is a repeat problem.
Hope to fix it.

Fixing belongs to the whole community, including yourself.
Taking action rather than a hope. Hope means no one is doing this now.


fix(tls): do not shutdown server on unexpected Eof

Motivation
When receiving non TLS packets (like TCP healtchecks), the server shuts down due to the UnexpectedEof returned by rustls.
Solution
Ignore this error

cc @djc if we can get that into 0.12.3

LGTM!

Hi! Just chiming in to say thank you!
We're hitting this issue, which is even worse for us as we have long-lived gRPC streams, that prevent the tonic server from exiting, effectively DoS-ing our APIs if for whatever reason we get non-tls tcp connection.


Area calculation not proper while drawing a polygon intersecting it's own shape

I was trying to draw and measure area of a polygon using Openlayers v3.7.0, It gave correct values for proper figures in which line continuation didn't intersect.
But when I draw a figure in which line continuation did intersect the total area was coming as subtraction of the two figures which forms as a result of line intersection.
Please refer the image below for more details.

This issue tracker is for OpenLayers 2
If you're talking about OpenLayers 3 you need to use https://github.com/openlayers/ol3 instead
I'm now very confused.


Get Started doc - issue 3998 fixes

fixes #4133
Internal review url

@rachelappel,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@Rick-Anderson review

@rachelappel,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@rachelappel,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Open Pages/Index.cshtml and add the following to the page above the carousel:

Edit Pages/Index.cshtml and ..
files are italic.
I don't see a carousel. Can you add highlighting?
[!code-csharp[Main](start-mvc/sample/src/MvcMovie/Models/MovieDateFormat.cs?name=snippet1&highlight=2,10)]

I think this is where it's supposed to go
`
@page
@model IndexModel
@{
ViewData["Title"] = "Home Page";
}
ADD CODE HERE and HIGHLIGHT

`

#sign-off


Added thead & tbody tags for correct table semantics

Just added thead & tbody tags to admi  index table pages for erb/haml/slim. It was strange that index table was missing them. Actually with this it will be much easyer to add prototype frameworks like Foundation & Bootstrap to admin.
Please review. Thanks!

Great thanks! Can you checkout the new bootstrap branch?

Great, will check it out!. Curruntly I'm in proxess of designing some admin mockups for another project. Got some great ideas. If something will not fit there, I will code that show that designs to padrino. I think tehy will look nice here.

Yea! Thank you!

Looking at bootstrap branch this isn't useful anymore. What would you say about designing custom admin theme for padrino?  If tthis is intresting we can discuss this. I can work on it in my spare time. I would love to commit something to opensource.

We are in the middle of a admin refactoring, we would use twitter boostrap.
We would love to have a "custom" padrino admin layout, so we will appreciate if in your spare time can make some pics with admin layout ideas.

http://hollow-night-6297.heroku.com/admin
user<EMAIL_ADDRESS>password: admin

Yep, I saw that already. Twitter bootstrap based.


problems with dbab-svr

On Tue, May 28, 2019 at 8:54 AM Dirk Geschke <dirk geschke @ genua.de> wrote:
... the debian-package of dbab-svr, seemed to terminate from time to time
However, I found some issues:

The while loop might terminate, if $sock->accept() fails.
Better would be:
  while (1) {
     my $new_sock = $sock->accept() or next;

There is no timeout mentioned, so a simple connected client
which does not send any data, would block the whole program.
So something like this might be a good idea:
    $new_sock->setsockopt(SOL_SOCKET, SO_RCVTIMEO, pack('l!l!', 10, 0));

HTTP/1.0 would be better than HTTP/1.1 and a "Connection: close", too:
    print $new_sock "HTTP/1.0 200 OK$crlf";
    print $new_sock "Content-type: image/gif$crlf";

In case of proxy.pac/wpad.dat, the header is missing, e.g.:
print $new_sock "HTTP/1.0 200 OK$crlf";
print $new_sock "Connection: close$crlf";
print $new_sock "Content-Type: application/octet-stream$crlf";
print $new_sock "function FindProxyForURL(url, host) {".
    qq| return "PROXY $proxyaddr:3128; DIRECT"; }$crlf|;

Maybe you can intregate some of this? Probably the timeout of 10s
is a little bit long, I would expect the answer far earlier at all.

Now:
$ curl -s --dump-header - http://na.ads.yahoo.com/
HTTP/1.0 200 OK
Connection: close
Content-type: image/gif
Accept-ranges: bytes
Content-length: 43


[BUG]Right-click menu configuration can affect the right-click menus of other plugins.

When the right-click menu configuration option is disabled, it can cause the right-click menus of other plugins to not display properly.

That is strange because if you disable right-click menu in Image Converter, it simply stops execution of the code which renders it.  It doesnt prevent any defaults or propagation etc.
Which plugin does it break?

Multiple reports of it impacting the Second Window plugin. If we disable Image Converter it works instantly again.

What is the use-case for that plugin? How is it being used in TTRPG community? Nowadays there is native Obsidian way of opening image in 2nd window, or am I missing something?

That is strange because if you disable right-click menu in Image Converter, it simply stops execution of the code which renders it. It doesnt prevent any defaults or propagation etc.
Which plugin does it break?

such as Image Context Menus plugin
After rolling back to a previous version , they no longer conflict.

Fixed in 1.2.17, although this release is not out yet, as there are a few other things which need fixing.

I have very limited time with full-time uni, work, family and this plugin in-between. Thus, if you enjoy the project so far, and would like to get certain features faster, to support sleepless nights, please considering supporting via Ko-fi