[Bug report]:  Cannot claim Shimmer rewards

Platform
Desktop
Version
2.1.3
Description
I had the first round of staking on the iota and I got some shimmer coins and I can not give them claim
Expected behaviour
after connecting with the 24 words following the claim steps I expected it to work
Actual behaviour
I downloaded the firefly shimmer application I added the words I gave revedinca coins and does not work
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Operating System
Windows
Diagnostics
Version 2.1.3
Language: en
Platform: win32
Platform Version: 10.0.22621
Platform Architecture: x64
CPU Count: 8
Total Memory: 16085.8 MB
Free Memory: 8615.7 MB

Developer Profile
No
Profile Type
Software (Stronghold)
Staking
Previously staked
Crash Status
White screen
Error Messages
An error occurred while searching for rewards
Error Logs
Wed, 07 Jun 2023 13:30:48 GMT
BaseError: An error occurred while searching for rewards

Wed, 07 Jun 2023 13:30:48 GMT
BaseError: An error occurred while searching for rewards

Wed, 07 Jun 2023 13:22:42 GMT
BaseError: An error occurred while searching for rewards

Wed, 07 Jun 2023 13:22:41 GMT
BaseError: An error occurred while searching for rewards

Wed, 07 Jun 2023 13:22:40 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 11:31:15 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 11:31:14 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 11:31:14 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 11:29:09 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 11:29:09 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 11:29:07 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:29 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:29 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:29 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:28 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:28 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:28 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:21 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:55:21 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:52:31 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:52:31 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:52:31 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:52:29 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:52:28 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:52:27 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:44:50 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:44:49 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:43 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:42 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:42 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:42 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:41 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:41 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:41 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:41 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:40 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:40 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:40 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:39 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:39 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:38 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:38 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:38 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:32 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:32 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:41:31 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:40:58 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:40:58 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:40:57 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:38:26 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:38:26 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:36:52 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:36:51 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:35:11 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:57 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:56 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:45 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:45 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:45 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:44 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:36 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:36 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:29 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:26 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:23 GMT
BaseError: An error occurred while searching for rewards

Thu, 25 May 2023 10:34:19 GMT
BaseError: An error occurred while searching for rewards

Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed by https://github.com/iotaledger/firefly/pull/7568 we will  release a new version very soon


[Refactor][config-ui] add a specific manager to read and set transformations If there are specific encode way.

What and why to refactor
https://github.com/apache/incubator-devlake/blob/24804f67423a726d955003589cc93bb773db16b2/config-ui/src/hooks/useDataScopesManager.jsx#L60-L75
https://github.com/apache/incubator-devlake/blob/24804f67423a726d955003589cc93bb773db16b2/config-ui/src/hooks/useDataScopesManager.jsx#L262
https://github.com/apache/incubator-devlake/blob/24804f67423a726d955003589cc93bb773db16b2/config-ui/src/hooks/useDataScopesManager.jsx#L691-L694
https://github.com/apache/incubator-devlake/blob/24804f67423a726d955003589cc93bb773db16b2/config-ui/src/hooks/useDataScopesManager.jsx#L734-L736
Describe the solution you'd like
I think we need to add a specific manager to read and set transformations to avoid causing problems.

@likyh I think this is a duplicate and already resolved with #3371?


Feature request: ability to set local path as destination

Would be awesome to be able to run this using a local path or if none supplied, the CWD

@cellvia Is --destination . what you're looking for?

no, sorry, i meant for "input"  it accepts npm package or git url, but would be cool to be able to point it at a subfolder or CWD (assumes there is a package.json in the folder in question)

@cellvia To install the dependencies of a package.json, you just need gpm -i .

In 3.x.x we can set a custom node_modules folder.


Rate limiting issues

Some servers get rate limited and whoogle needs to force a new connection.

Fixed with implementation of the autoheal_protonvpn sidecar. Due to how thenetwork stack is configured, the APP container needs to be restarted every time a new connection is established.
The sidecar restarts the VPN container if it fails (stopped/error) or the APP container fails healthchecks. The APP is then restarted - subsequently re-establishing service.


Added summary and golden metrics for multiple open instrumentation providers (ext-service)

Relevant information
Added summary golden metrics for multiple open instrumentation providers under ext-service such as opentelemetry, kamon-agent, micrometer and pixie.
Checklist

[x] I've read the guidelines and understand the acceptance criteria.
[x] The value of the attribute marked as identifier will be unique and valid.
[x] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: jonatns:x: fryckbosYou have signed the CLA already but the status is still pending? Let us recheck it.

Validation fixed in this PR: https://github.com/newrelic-experimental/entity-synthesis-definitions/pull/168
That said we have a hard-coded version of EXT-SERVICE in the internal service. I think this was done to allow multiple providers in a quick way. So I will need a bit of time to understand if we can remove that now or we are leaving something behind. I'll be back!


Make agent name linkable from task(s) view

Easier than navigating back thru agents list

Added in ad4c464


Developer home page

Description
Implements developer home page
NOTE: Still needs new HubHero implementation from v7.24.1

Description
Implements developer home page
NOTE: Still needs new HubHero implementation from v7.24.1

HubHero is now on dev 🎉

Thanks @pettinarip. Brought in those changes and ran linter since that is now in dev. I think this should be good to go now if this builds.

@corwintines on a final test, I noticed this

While you load or refresh the page, it seems that the translations are not fully loaded 🤔 Maybe it is related with a rehydration issue?


feat(rest-api-client): update space.getSpace method

Why

With the official release of the June 2024 version, the 'permissions' parameter was added in the response body of Get Space API.
What

Update the type of Space to add 'permissions' parameter.

In addition, the following parameters were missing, so they were also added to the type definition:

showAnnouncement
showThreadList
showAppList
showMemberList
showRelatedLinkList

update doc for space.getSpace.

How to test

Create a space on UI.
Exec space.getSpace method
Check to include the permissions parameter in the response
Check to be able to access permissions parameter of the value of the response.

Checklist

[x] Read CONTRIBUTING.md
[x] Updated documentation if it is required.
[x] Added tests if it is required.
[x] Passed pnpm lint and pnpm test on the root directory.

@tasshi-me
ありがとうございます、見逃していました :bow:


How to conceptualize subtyping for legacy-nullness

It's beyond debate that @NotNull Foo <: @Nullable Foo. When @LegacyNull Foo comes in, well, it should still be uncontroversial that assigning from not-null to legacy is safe, and that assigning from legacy to nullable is safe.
But then the questions of assigning legacy to not-null, and/or assigning nullable to legacy, are not as clear. I would say there are two choices of rule sets that both make good sense:
(1) The strict interpretation: neither of these cases is assignable; both are unsound.
(2) The lenient interpretation: both are assignable, because we don't have enough basis for complaint and we will annoy users.
Interestingly, (1) leads to a "normal" subtype arrangement of not-null <: legacy <: nullable where the anti-symmetric property is preserved. (2) leads to breaking not just anti-symmetry but also transitivity (we want nullable <: legacy and legacy <: not-null but we don't want nullable <: not-null!).
I think a clean solution may be this:  assignability rules really are defined conservatively as in (1). But we also have something akin to Java's "unchecked conversion". Even though nullable </: legacy and legacy </: not-null, you can still make that conversion anyway IF you @SuppressWarnings("nullness:legacy") (let's not debate the name though).
What's nice about this is that projects can decide whether they want to be strict or lenient based on whether they apply that warning suppression at a broad level or not. I think it's also much easier to think about this way, rather than saying only "not-null <: nullable but legacy is a special thing sitting off to the side somewhere".

Way back when, I wondered about the implications of circular subtyping.
I still don't have a great understanding of the question, but: From what I understand, there is only one sufficiently powerful approach to checking if one Java type is a subtype of another: by traversing the inheritance graph (whose edges connect a type to its direct supertypes, as defined in JLS 4.10.2, etc.).
I believe that we, too, are stuck doing this even though we'd prefer to check "only the nullness part" of types. (To handwave: That's thanks to type variables, types that extend Foo<@Nullable Bar>, and probably other stuff.) I think someone (from JetBrains?) warned us that this would be the case a long time ago. I don't know that we heard details at the time, but I should give credit, if only I remembered who it was....
So, what does this mean? Well, first of all: If we're traversing a graph that has cycles in it, then we need to track which nodes we've already seen. We might need to do this anyway, though??
We might also need to ensure that we complete any "definitely safe" traversals before we complete any "possibly safe" / "not enough information because of unspecified nullness" traversals. That way, we don't issue warnings spuriously.
This might happen naturally (especially?) if we use BFS over DFS, but (a) I'm not absolutely 100% confident in that and (b) BFS might complicate an already complicated implementation. (Another small complication: We need to track whether we have used a "possibly safe" edge.)
I can think of another possible implementation, which is easier, albeit slightly wasteful: Run a full search of an inheritance graph without the "possibly safe" edges first and then, if that fails, to run a search of an inheritance graph with those edges.
There's good news for tools that operate only in "lenient mode": They don't need to worry about whether they use "possibly safe" edges or not, so they can run a single search with all edges present.

I still need to finish rereading this thread, but: Currently I'm less concerned with circular subtyping per se than I am with the idea that, in the specific case of "lenient mode," we might accidentally have nullable <: unspecified <: non-null (as kevinb9n notes in the first post).
One solution to this seems to be that nullable is never a subtype of unspecified, but it can be "consistent with" it. It's not clear to me whether people have extended this idea to parameterized types (and whatever other challenges we'd face in extending it to Java). I think I saw a paper that sounded related, but I haven't read it yet. But even if this isn't a fully solved problem, maybe it's easier to solve when the domain is only ~2 nullnesses instead of an arbitrary number of types?
Another solution is that subtyping of nullness is non-transitive. Non-transitive subtyping is part of Kotlin. (See also flexible types and subtyping for flexible types. Here are Andrey's slides again. Probably I should also look at subtyping for nullable types.) I haven't looked into how they prevent nullable <: non-null. Maybe they refuse to follow the edge to unspecified unless they're handwave directly matching an unspecified type in the some known type that they're comparing to?
Hopefully I can understand this a little better and get to the point of having specific questions for Andrey / Denis / Werner / others.

I sent an email to ask about "consistency"/"equivalence" as a way of supporting non-transitive subtyping.

I do like the "Many-Worlds Interpretation" (MWI) of unspecified nullness. What I think it says is that many seemingly-boolean propositions need instead to be answered with a ternary boolean {false, unknown, true}. Then we imagine forking off two parallel universes for each unspecified-nullness type in the system, then IF the question has the same true or false answer in ALL of those universes, we can definitively choose that as the real answer; otherwise the answer is "unknown".
(Or we just use the usual truth tables for ternary boolean logic; I still think this works out to the same thing.)
(Aside: when asking whether a type is nullable, it is helpful to standardize on that as the positive direction (i.e. mapping true=nullable, false=non-nullable); then we can speak of things like "intersecting" or "ANDing" nullness, and the nullness of an intersection type would be the intersection of the nullness of each component, etc. And it's conventional to view false < true as well as to view subtypes < supertypes... "it all just works out, man..")
Anyway, all this to say,
The part of the initial proposal here, that non-nullable is a subtype of unspecified and that unspecified is a subtype of nullable, is simply a consequence of MWI. Fork off two universes, get the same true answer in both, you're done.
But asking whether unspecified is a subtype of non-nullable yields the answer "unknown". This led to the idea that we would have a middle-of-the-road response: allow it, but with a warning. However, it sure feels like we need one definitive answer on whether these are subtypes or not. The initial proposal said "they're not, because subtyping is quite strict and also expected to be transitive and antisymmetric; but we can allow a type conversion with a warning anyway".
This last part seems to be the part that's remained the most controversial.

I support thinking of the null direction as "true." I like thinking of it as "Union with null? Yes," in contrast to "Union with null? No" and "Union with null? Unknown."
(I am glossing over some deeper questions, but we may be able to agree on this much without getting into those.)
I do think that we're going to need "unknown" to mean "yes" in lenient mode, even though that makes subtyping non-transitive. I'm encouraged that Kotlin gets away with non-transitive subtyping -- and I don't think it's too hard to implement, even if the spec resorts to handwaving a little.
Non-transitive subtyping is scary, but the alternative seems to be: "Subtyping is transitive, but you don't actually check subtyping anymore. Instead, every place where you would have used subtyping, you use <some other check> instead."[*]That alternative sounds like the exact same thing, only under a different name :) It's scary either way, so I think we should be direct about it and say "subtyping is non-transitive."
[*] We'd have to use such a check for more than just "conversions.": For example, we would also use it to check type arguments. So I am wary of even saying the word "conversions": It may suggest "This is just like unchecked conversions [and thus it's a solved problem]" when in fact there's more to it.

I don't think that Jspecify should try to "conceptualize subtyping for legacy-nullness" (per the title of this issue).  Putting @UnknownNullness at a specific location in the type hierarchy of @Nullable and @NonNull implies a subtyping relationship that every tool must respect.  No such subtyping relationship exists, because @UnknownNullness may be treated differently by different tools.  Jspecify should state @Nullable :> @NonNull, but different tools may place @UnknownNullness at different locations within that type hierarchy.
Similarly, Jspecify should not dictate a tool's assignability rules.  Different tools will forbid/permit different assignments when @UnknownNullness is involved.
The  English description of @UnknownNullness can use type system concepts, so long as it does not dictate how a tool treats @UnknownNullness.  For instance, it might say that @UnknownNullness is wildcard-like in that a complete specification would give each type @NonNull or @Nullable, but in an incomplete specification (one that uses @UnknownNullness) the type's qualifier in Jspecify's type system is unknown.  But it would not say that tools must treat @UnknownNullness the same way that the Java type system treats wildcards (even though some particular tool might make that choice).
The discussion in this thread about putting @UnknownNullness in the type hierarchy or inventing new assignability rules might be useful for the implementation of one particular tool.  However, it is outside the scope of the Jspecify project proper.  I think that the Jspecify team should avoid such discussions, because they muddy the distinction between the definition of Jspecify and the behavior of a tool, and because they bias people toward one particular implementation choice that is not appropriate for all tools.
TL;DR: @UnknownNullness is outside the type hierarchy, from Jspecify's perspective.  Jspecify should not impose subtyping or assignability rules related to @UnknownNullness.

Additionally: I understand that @NonNull <: @NullnessUnspecified <: @Nullable is not sufficient to get all the properties that all tools might want. Still, do you see cases in which it gives results that a tool would consider unsound? I'm hoping that it's sound but incomplete.
Hmm, in asking this, I'm probably making a lot of assumptions about what @NullnessUnspecified (and for that matter, @Nullable) means. Under different assumptions, the thing that I just said is probably not true.

How would you feel about the idea that Jspecify supplies subtyping rules but tools can apply those rules when (and only when) they see fit?

What is the benefit of Jspecify taking a stand on subtyping of @UnspecifiedNullness, but permitting tools to ignore it and/or impose their own different subtyping?

When searching for the elusive the line between what we should specify and what we should leave open to tools, I just want to opine again that our primary guiding star must always be, "if it influences how an API owner would choose to annotate their API, then we must specify it."
Can I annotate a return type as non-null if its supermethod returns unspecified? Can I annotate it as nullable if it already has overrides that may be unspecified?
That is a clear example of a question that needs definitive answers, and I've been seeing specifying subtyping rules as just a way to achieve that. But the same concern exists on a more subtle level too:
If I annotate this parameter type as nullable, how do I know I'm not causing a problem for any users no matter what they're passing in?
Essentially, every time I choose a parameter type, a part of that decision is always "and why is this not the next more general type, and why is this not the next more specific type?" For example, why did I settle on Collection, rather than Iterable or List?  I think I need to be able to do that for nullness too, and that's why it seems important that everyone agree on what the subtyping rules are.

I should have mentioned that I do think we very often forget to think about that line on a daily basis, and it's right to call our attention to it so we can make sure we're respecting it.
I guess I can't really picture how tools could choose different subtyping rules unless they were also assuming different meanings for our annotations themselves. Or how they could do so without putting an API owner in the position of having to choose whether to make their X-tool users or their Y-tool users happy.

Can I annotate a return type as non-null if its supermethod returns unspecified? Can I annotate it as nullable if it already has overrides that may return unspecified?

I'm not sure what question you are asking in "Can I".

If you are asking whether this is syntactically correct, then the answer is yes, because Jspecify does not forbid it.
If you are asking whether this causes a tool to issue a warning, that is a question that different tools may have different answers to.  Jspecify cannot and must not take a position on this question.

I guess I can't really picture how tools could choose different subtyping rules unless they were also assuming different meanings for our annotations themselves.

Yes, different tools may treat @UnspecifiedNullness differently.  I'm not sure what other annotations you are talking about when you say "our annotations", since this discussion is only about @UnspecifiedNullness.

What is the benefit of Jspecify taking a stand on subtyping of @UnspecifiedNullness, but permitting tools to ignore it and/or impose their own different subtyping?

Fair: At this point, I am throwing ideas at the wall and seeing what sticks. If I'm not being outright self-contradictory, I'm getting very close. Still, I will try to wriggle out of this :)
In proposing that tools can ignore rules, I am mostly just acknowledging reality: I can write as many tens of thousands of words as I want, but ultimately tool owners get to decide what their tools do -- including, say, not recognizing Jspecify annotations at all, treating them like the FindBugs @Nullable, or checking only for contradictory constructions like @Nullable @NonNull. I can say that one interpretation or another is "required," but that distinction is not necessarily meaningful to end users. So I'm happy to push for weaker requirements if that makes this process less controversial.
But it may be that a weaker spec ends up more controversial! Certainly there will be some controversy no matter what: After all, we're here because we assume that whatever "requirements" or "suggestions" we write will have some effect. Maybe I am just playing semantic games? I don't feel that I have a well-thought out position of my own for this, and I surely haven't internalized your whole position, either.
For the purposes of our present discussions, I'd like to have some term (whether it's "subtyping" or not) that we can use. With it, we can discuss behavior that we expect some tools to find useful but that we acknowledge that not all tools will implement. I think that providing a guide to such "potentially useful behavior" is a noble goal for us, even if it's "not a spec."
Yet, at the same time, I am poking you with question about whether @NonNull <: @NullnessUnspecified <: @Nullable is sound, presumably under the assumption that you and other tool authors might adopt it :) I do want for our "suggestions" to be palatable to tool authors. Not to mention that I want to be unsound only intentionally, rather than by accident. As much as possible, I'd like for tool authors to feel that they need only layer knowledge on top of ours: "Jspecify doesn't know that this this expression's type is a subtype of @NonNull Object, but I know that someone just performed a null check on it, so...."

@mernst , I'm sorry if you've stated this before and I've forgotten it, but do you have an idea in mind of where you would draw the line between what to specify and what not to? I just linked to one thing you said, but I don't want to make assumptions about what you meant by "perhaps a few other weak properties."
For example, in endorsing @Nullable :> @NonNull, it seems like you might consider the following test to be acceptable:
Object foo(@Nullable Object p) {
  return p; // type mismatch
}

In terms of what to check, I'm thinking a little in terms of the Subtyping Checker here. (You would know better than I if that comparison is in any way illuminating or even fair.)
But it may be that even that is too far: If we're not prescribing tool behavior, then what does it mean to "test" what happens when there's a mismatch?

Can I annotate a return type as non-null if its supermethod returns unspecified? Can I annotate it as nullable if it already has overrides that may return unspecified?

I'm not sure what question you are asking in "Can I".

If you are asking whether this is syntactically correct, then the answer is yes, because Jspecify does not forbid it.

I think it should be more than "I searched everything and couldn't find anything saying not to, so I guess I can". It should be that any person who understands the meanings of the annotations correctly will have positive knowledge that of course this scenario above is okay. I brought the word "subtyping" into all this as a way to provide that positive knowledge. When a person knows that a subtyping relationship exists then they can relax in the knowledge that everything true of the parent is true of the child.
I do get the sense though that you and I are often arguing about something different from what we really seem to be arguing about, but I can't always put my finger on what our real disagreement is.

If you are asking whether this causes a tool to issue a warning, that is a question that different tools may have different answers to.  Jspecify cannot and must not take a position on this question.

I hope I can explain this right. I've tried a number of times.
I really and truly don't care what specific warnings tools choose to emit.
I really and truly do want our annotations to have clear and precise meanings. The result of that is that certain combinations of annotations will be outright logical contradictions. I want our specs to be clear on those combinations being invalid.
I am concerned about tools deciding that one of our annotations carries some meaning that is more and/or less than what we specified, and acting accordingly to that interpretation. Not that I have any illusions that we can prevent it, but I think it is decidedly a bad outcome, and if our decisions pushed the tool owner to that route then we would have to accept some of the blame. The poster child for this is of course @NullnessUnspecified, because it represents the absolute lack of any information about the intended nullness of the type. If a tool interprets that annotation as, "we think what they're really trying to say is...", well, again, I just think that's a bad outcome.

Yes, different tools may treat @UnspecifiedNullness differently. I'm not sure what other annotations you are talking about when you say "our annotations", since this discussion is only about @UnspecifiedNullness.

And I think this glosses over the distinction I've been struggling to make (perhaps because it is just too subtle for its own good). The outcome I hope for is that any two tools are going to agree that the annotations mean the same thing (convey the same information about the API owner's intentions), they may just want to take different actions based on the same information. I can't tell if you understand it the same way and just keep seeing us as trying to dictate the actions, or if this is really what you're objecting to itself.

(A lot of this is the issue that #73 was initially created to discuss, though who knows in what directions the discussion has gone since :-))

Two questions, @mernst:

What's the value of not specifying a (partial or total) ordering of the three qualifiers?  I guess what I'm asking is, can you give some examples of what only specifying "non-null < nullable", and saying nothing about how "unspecified" relates, would allow tools to do that specifying "non-null <= unspecified <= nullable" would prevent?

If we define "unspecified" as "it may be non-null or it may be nullable, we don't know", it appears:

non-null implies nullable
non-null implies unspecified
unspecified implies nullable
Seemingly these implications hold regardless of whether we prescribe them, just following the definition.  Even if we define unspecified := \exists x. (x = non-null or nullable), that is, even if we defined "unspecified" as derived from other qualifiers, these implications seem to hold.  If that's the case then it seems "harmless" to codify something that appears true anyways.  What am I missing?

That said I agree that defining subtyping or assignability could be overreaching, not least since assignments happen in code, which we consider out of scope.  There's however one area where we seemingly should say something, and that is the area of what constitutes valid overriding.  That is, it seems to me it would be useful to introduce some lowest common denominator where all tools are required to consider some declarations class C extends B implements Foo, Bar, ... { ... } as "well formed" so they can interpret them consistently (and I'm talking about declarations only here, not method implementation code).  For instance, consider:
// no annotations
interface ListLike<T> {
  T get(int index);
  boolean contains(Object elem);
}
// annotated
class MyList implements ListLike<@NonNull String> {
  @Override T get(int index) {...}
  @Override boolean contains(@Nullable Object elem) {...}
}

Given ListLike, it seems helpful to prescribe whether MyList should be considered a well-formed declaration, that defines a class that implements ListLike<@NonNull String>, with methods that indeed override ListLike<@NonNull String>'s methods.  If we don't do that, but the author of MyList happens to use a tool that accepted MyList, a second tool might reject MyList or might refuse to process code that depends on MyList or even refuse to read in MyList's bytecode.  We can argue over exactly what that bar should be, and whether it should apply only to bytecode or also source code, but it seems useful to define some bar.  And because most code today is unannotated, it seems important for that bar to include some rules for handling unspecified nullness.
It seems we may get away with simply saying something like, "it's always allowed to use @UnspecifiedNullness (implicitly in unannotated code, or explicitly) where a supertype used @NonNull or @Nullable, and vice versa", which doesn't require an ordering of unspecified vs. other qualifiers.  We could still specify co-, contra-, and in-variant handling of @NonNull vs @Nullable as appropriate, just not for @UnspecifiedNullness.  We can certainly allow tools to raise warnings when seeing changes to or from @UnspecifiedNullness in source code, maybe even in bytecode, but it does seem useful to define "enough" for tools to still interpret MyList consistently, even if some of them raise warnings on MyList's declaration, so that references to MyList in other code can be handled.  I believe this level of specification would be consistent with not including "unspecified" in any kind of ordering as you requested.  Is that what you had in mind?
I personally would like to take one or more of the following steps (still talking only about declarations and overriding here, not code, and specifically overriding that changes @UnspecifiedNullness to one of the other 2 qualifiers), in order of preference:

some form of @SuppressWarnings-like annotation should suppress warnings related to overriding that changes qualifiers to and from @UnspecifiedNullness in the annotated scope.  This would make it so users have a way to make any tool accept the overriding they want.
if we draw a distinction between warnings, where tools print something but continue, and errors, where tools stop, tools should never "error" when they see these situations in bytecode (e.g., tools would be required to accept MyList's bytecode: they can print warnings but should continue on).
changes to and from @UnspecifiedNullness that are consistent with the proposed qualifier ordering (non-null <= unspecified <= nullable) and allowed per co- or contra-variance rules shouldn't cause warnings, or at least shouldn't cause errors (because they are seemingly "safe" as discussed above).

Now only the last one requires defining some kind of ordering of all 3 qualifiers.  I do think it's a useful rule that would make interop between different tools more seamless.  But I guess in all of this I've talked myself into thinking that we can get pretty far even without defining this ordering.  Thoughts?

One other thing to note is that not ordering "unspecified" seemingly has both perils and advantages in this weird case, which I implicitly referenced in ListLike<T> in my last post:
interface Foo<T extends @NullnessUnspecified Object>

It's always been a bit vexing what this is supposed to mean.

by not relating "unspecified" to other qualifiers, we're somewhat side-stepping that question, and in particular that would allow tools to raise warnings on Foo<@NonNull String>, which multiple folks have considered desirable.
by stating that non-null <= unspecified we're apparently saying that Foo<@NonNull String> should be considered valid, which I personally think is fine, but it's then seemingly inconsistent that Foo<@Nullable String> can cause warnings.

Two questions, @mernst:
 Seemingly these implications hold regardless of whether we prescribe them, just following the definition.

Yes, thank you for that clarity, this is my view too.

That said I agree that defining subtyping or assignability could be overreaching, not least since assignments happen in code, which we consider out of scope.

Just to renew my objection to this: a conscientious API owner decides what type a parameter should have based on what kinds of actual parameter expressions should be assignable to it.
I think "APIs, not implementation code" has been a slight oversimplification, and we might as well just use this better oversimplification instead:

APIs: in scope
Implementation code that is directly interacting with an API: in scope
Other implementation code, out of scope

I personally would like to take one or more of the following steps (still talking only about declarations and overriding here, not code, and specifically overriding that changes @UnspecifiedNullness to one of the other 2 qualifiers), in order of preference:

some form of @SuppressWarnings-like annotation should suppress warnings related to overriding that changes qualifiers to and from @UnspecifiedNullness in the annotated scope.  This would make it so users have a way to make any tool accept the overriding they want.

(aside: This should be @SW itself, since one of the reasons the qualifier is getting overridden to unspec may be that the library is not taking on our dependency yet.)

if we draw a distinction between warnings, where tools print something but continue, and errors, where tools stop, tools should never "error" when they see these situations in bytecode (e.g., tools would be required to accept MyList's bytecode: they can print warnings but should continue on).

To head off Mike's probable objection :-), we don't need to take stances on what tools print.
Once we provide precise enough meanings for our annotations, then we can point out various situations that are categorically invalid ("error") as direct consequences of those meanings, and situations that are less than provably safe ("warning") as well. And we should. We certainly mustn't avoid doing so out of fear that it could sound like dictating tool behavior.

But I guess in all of this I've talked myself into thinking that we can get pretty far even without defining this ordering. Thoughts?

I'm still in sync with your opener: that the ordering is nothing but a logical consequence of the definitions. One reaction to that is "so we don't need to specify it", but mine is "so it would be silly of us to pretend that we're not specifying it." We are, just by consequence rather than fiat.

Btw, the more repeatedly and strenuously I assert a position, the more I welcome comments like "and here are some consequences of that position you might not be accounting for." That, in my view, is how this all works.

I'm convicting this issue of the crime of being extremely long and outdated. Anyone may file a new issue for any particular aspect touched on here that feels in need of resolution.


Multi-task training

In a multi-task training, how do you handle rewards between different tasks? I see CLIPPED_REWARDS in the code. Will the rewards of different types of tasks be added up and then backpropagated? Can you figure it out for me in the code?? @lespeholt

There is no adding. You just train the games in a round robin fashion. One can do much better though, please see https://arxiv.org/abs/1809.04474

There is no adding. You just train the games in a round robin fashion. One can do much better though, please see https://arxiv.org/abs/1809.04474


How to use it？

Can you show me how to use it？ thanks！

You can generate subsequent code by selecting the specified content or by generating code from the previous text.
The shortcut key for triggering code prediction is alt+s.
Or use the right mouse button to pop up the tool.

I downloaded a zip package of the project, but was unable to install the project as a plug-in. Error message: "Fail to load plugin descriptor from filefauxpilotClient-main.zip" Do you know why？

Did you download it from the Releases folder https://github.com/csnowfox/fauxpilotClient/releases/tag/v0.9.0 ?
I managed to get the popup working with Alt+S, but how do I accept the suggestion and have it insert the result into the editor?

Hello,how can I change the server address?

It appears under File > Settings > Tools > fauxpilot-client . Mine is http://localhost:5000/v1/engines/codegen/completions and that worked for me.

The prompt effect of the code is not satisfactory. Not yet inserted into the editor with prompt language. To use, manually select Copy in the prompt window.

The prompt effect of the code is not satisfactory. The prompt language insertion into the editor has not been implemented yet. To use, manually select Copy in the prompt window.


Custom Notes aren't displayed correctly

Describe your bug here.
Currently, all Custom Notes are colored just like the normal notes, which is actually quite cool...
But they are also changed, if the colors are the normal ones, so the custom notes appear in a wrong color,
Is this intended? Is there any way to fix this? If yes, how?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

#12802


Add a button on top to toggle dark/light theme in all pages

This issue is raised in ui/ux enchantment

okay, you can close this issue too


I cant see the label of the tabs

I'm trying to create a tabbed card for my remotes, each card is vertical stack of horizontal stacks with buttons
I see the tab at the top but the label is not showing, i tried to change the color and font size with the styles but it only changed the color of the ident of the tab and resizing didn't seem to have any affect
I'm using latest HA version (2022.12.0) and I installed manually (added all of the files in SRC folder to resources and the latest release tabbed-card.js).

can you please post a screenshot/cast of the issue and your exact config?

this is the code:
http://pastie.org/p/0kDBTkLHi4XfyiREODvAWO
but it also happens with the default card showing the sun

thats not following the configuration schema: https://github.com/kinghat/tabbed-card#card-schema
type: custom:tabbed-card
tabs:
  - label: Kodi
    card:
      ...

should be:
type: custom:tabbed-card
tabs:
  - card:
      type:
    attributes?:
      label?: string

can you post the same for the default card you are talking about? if youre talking about whats returned form the editor, thats being worked on so isnt functional and you can disregard.

thank, i was missing the "attributes" as i copied the script from the default card which is also missing it


Orphan guide

Based on the name of this file "azure-api-management-certs" it should be in either API Management section or maybe even somewhere else

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

ID: ea96d36c-ecca-def8-29bb-081f363f48ce
Version Independent ID: c482444e-69a8-b31d-a7a8-ce24d8ff72f6
Content: Upload an Azure Service Management Certificate
Content Source: articles/azure-api-management-certs.md
Service: na
GitHub Login: @Thraka
Microsoft Alias: adegeo

@mike-urnun-msft - Please reassign to @mikebudzynski, the PM that owns content for this service.

#please-close This has nothing to do with Azure API Management.


fix(volume): prevent bind mounts and allow named volumes [EE-2364]

Closes https://github.com/portainer/portainer/issues/6387


test: enhance test coverage of seata common

Ⅰ. Describe what this PR did
Enhance the test coverage of seata-common module.
Ⅱ. Does this pull request fix one issue?

It's a partial fix of #187 .
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Run tests and coverage of seata-common module.
Ⅴ. Special notes for reviews

Codecov Report

Merging #2007 into develop will increase coverage by 0.16%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #2007      +/-   ##
=============================================
+ Coverage      55.25%   55.41%   +0.16%
- Complexity      2430     2442      +12
=============================================
  Files            432      432
  Lines          14439    14439
  Branches        1706     1706
=============================================
+ Hits            7978     8002      +24
+ Misses          5736     5715      -21
+ Partials         725      722       -3

Impacted Files
Coverage Δ
Complexity Δ

...eata/common/exception/EurekaRegistryException.java
100% <100%> (+100%)
4 <1> (+4)
:arrow_up:

...o/seata/server/coordinator/DefaultCoordinator.java
48.41% <0%> (+0.39%)
28% <0%> (+1%)
:arrow_up:

...in/java/io/seata/server/session/GlobalSession.java
85.02% <0%> (+0.48%)
68% <0%> (+1%)
:arrow_up:

...server/store/file/FileTransactionStoreManager.java
56.5% <0%> (+0.63%)
29% <0%> (ø)
:arrow_down:

...io/seata/common/exception/DataAccessException.java
100% <0%> (+100%)
6% <0%> (+6%)
:arrow_up:

add Copyright on new Classes

add Copyright on new Classes

resolved


Add Option to Change Notebook Location

Problem
Notebooks are currently saved to %appdata%\ideanote\notebooks without any option to move them
Solution
Add an option to change the location notebooks are saved

That's a good idea! I will add it in the next version.

Added in 588ff4b809b02c8e239e536b2211bad2021373c8. I'm currently working on releasing this version.

Released in 1.13.0!
The Microsoft Store version is under review, but will be available soon.


Addition and Multiplication between BlockDiagonals not type stable

I think implementing broadcasting will fix this for us, but not totally sure

it is only type unstable between Matrix and the types of the input, which should be a union of less than 4 types... which aparently makes this "not that bad" (using BlockDiagonals will still be a big improvement to users) -- but still, not totally ideal

https://julialang.org/blog/2018/08/union-splitting


Allow adding published to the generated Cargo.toml

Abort mission, the key is publish

Yeah I just noticed it as well :)


No Badge from completed Tutorial

MissionURL: https://developers.sap.com/mission.mobile-dev-kit-get-started.html
Get Started with the Mobile Development Kit
I get no Badget for that Mission while I made all Tutorials for that. :)
Can you have a look for that?
Thank you
Regards

The badge takes about a week to be added to your profile -- a few more days perhaps since we just added it to our system. Please write back at the end of this week whether you received it.

Seems that this is an issue for the "mobile" tutorials/missions. I finished the mobile card tutorial (https://developers.sap.com/mission.mobile-cards-get-started.html) already weeks ago and the badge does not appear. But hey, it is just a badge ;)

What day did you finish it?

On March 10, after issue #3188 was fixed.

OK, I will check with the "badge people", who will arrive later on today. Will update you when I know something.

No Badge from "Connect Microsoft Office 365 and SAP Data Through an SAPUI5 App ", too.
Regards
I just assume that it is a technical problem. Maybe it was just forgotten when researching?

Hi,
I think I found the mistake. There is no badge. I completed the missions

Connect Microsoft Office 365 and SAP Data Through an SAPUI5 App
Get Started with the Mobile Development Kit
Develop Your First SAPUI5 Web App on Cloud Foundry

and just assumed that there is a badge. However, the said missions are not listed on the overview page. "Currently Available Missions and Badges" (https://www.sap.com/community/resources/missions-badges.html). Maybe they will be introduced in retrospect ...
Regards...

Caroleigh Deneen fixed it!


Update mover's oc_chef_authz config

This is necessary for mover to create a pool of ibrowse workers to make
authz changes in a migration.
I wonder if we want to consider using partial templates for this kind of thing.

:+1:


Add Pipe Job type with new helpers with unit tests

This change continues the addition of the shx package started in https://github.com/m-lab/go/pull/131, meant to replace the  m-lab/pipe package with better implementations and extensibility.
This change adds one new type, PipeJob and several new helper functions. PipeJob is used to create a pipeline of Jobs where the first output writes to the input of the next. New helper functions include: Println. IfFileMissing, and IfVarMissing. New unit tests and examples illustrate usage.

This change is

Pull Request Test Coverage Report for Build 1009

114 of 119 (95.8%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 93.51%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shx/job.go
114
119
95.8%

Totals

Change from base Build 1006:
0.3%

Covered Lines:
1902

Relevant Lines:
2034

💛  - Coveralls


gapi.auth2.authorize does not take login_hint into account when passing the User ID

When passing the Google User ID as the login_hint property of the gapi.auth2.authorize no account is preselected. Instead the whole list of user accounts is displayed. It only works when providing the User Email Address instead of his User ID contrary to what is explained in the documentation:

The email, or User ID, of a user to pre-select in the sign-in flow. This is susceptible to modification by the user, unless prompt: "none" is used.

Note that I checked that the User ID was valid (and in my case it is provided by the Google Drive UI integration as the userId parameter)

I'm having the same issue. Would be great to get this fixed as a user id is immutable, unlike an email address.

I have the same issue.

Also says it here:

Set the parameter value to an email address or sub identifier, which is equivalent to the user's Google ID.

Except the sub identifier does not work. Only email works.

I have the same problem with this feature... When will someone fix it?

I can't believe this bug hasn't been resolved yet.


Modal with fixed footer has a fixed height of 70%

It would be better if the modal would calculate dynamically the height. Otherwise in the case you just have less content you'll see a huge nearly empty modal.

It doesn't work work percentages
On Mar 22, 2015 2:08 PM, "Jaime Venturini"<EMAIL_ADDRESS>wrote:

It would be better if the modal would calculate dynamically the height.
Otherwise in the case you just have less content you'll see a huge nearly
empty modal.
—
Reply to this email directly or view it on GitHub
https://github.com/Dogfalo/materialize/issues/971.

Sorry, I can't understand your answer. Do I have to change something to make it work?

This type of modal cannot have a variable height such as a percentage.

Can we put a width or height in px or em ? If yes, how to do it ?


Error on "export policy definition"

Getting the following error while trying to export the policies via UI -
"Service prinicipal creation failed : Insufficient privileges to complete the operation."

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

ID: 4ff59c65-dffd-a9d3-e02c-25c688322d91
Version Independent ID: 001249ab-2a55-e8ee-7d3c-e3cb7f4afd24
Content: Export Azure Policy resources - Azure Policy
Content Source: articles/governance/policy/how-to/export-resources.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

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

#reassign:DCtheGeek

@mpchen Thanks for letting us know.  As this isn't an issue with the Doc, please open a support ticket so they can troubleshoot and assist you directly.  Thank you!  cc / @raiyanalam
@MicrosoftDocs/azure-cxp-triage #please-close

So what's the sol?


Add medium-links.md

Added a new medium-links.md file in the awah_fortune/Fortune/documents directory.

You did a great job with the article! However, I don't see the link to the article on Medium, which should have been submitted instead of the article file directly to GitHub.
Also, for future tasks, please create a new branch before pushing any changes to GitHub. For this task, please create a new branch, move the article there, and submit a pull request. This will help keep the main branch clean and organized. Thank you!


Updated the user.js and user.spec.js to add a name field to the user …

Assignee Tasks

[x] added unit tests (or none needed)
[x] written relevant docs (or none needed)
[x] referenced any relevant issues (or none exist)

Reasons for pull

Updated the user model with name
Added name to test of user model

THIS IS COOL WITH ME


GridUnitType link is broken

Link goes to https://docs.microsoft.com/en-us/uwp/api/gridlength_gridunittype, which returns a 404.

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

ID: f021912e-813f-dff3-ed06-0ebfc17dbfa5
Version Independent ID: a4ad2849-206a-28df-b2f8-e7b41f82993b
Content: GridLength Struct (Windows.UI.Xaml) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.ui.xaml.gridlength.yml&version=GBlive&_a=contents
Service: unspecified
GitHub Login: @wdg-dev-content
Microsoft Alias: wdg-dev-content

This link appears to be fixed.


[HUD] Scan option

Hi all -
I started using HUD with ZAP and it has been a great experience. Very efficient way to do the manual testing. My request is, it would be great to give a button that can trigger an active scan on the intercepted request.
Thanks!
Nagpradis

Thanks for the feedback!
Definitely agree with the option to scan a specific url, I can see that being very useful


Change require string in error to fix SystemJS import

SystemJS is trying to do a real require with this error string, which is only informational. This will fix the problem.
This is the issue with more info about the problem: https://github.com/systemjs/systemjs/issues/1417

Really? OK. Disappointing that they're parsing code with RegExps, but it's no big deal to change this on our end.

Thanks @finneganh!


Can't save image as a GIF?

Hello,
I've recently been playing around with libvips and all has gone smoothly save for one issue: I can't seem to be able to save a GIF image back to file after reading it; I get a VipsForeignSave: "test2.gif" is not a known file format error.
That error is being raised by this code:
local vips = require("vips")

local image = vips.Image.new_from_file("test.gif", {n = -1})
image:write_to_file("test2.gif")

Additionally, I also tried running a code sample provided in a different issue, only to get the same result.
Reading the GIF and saving it to other formats (PNG) works. I've also tried to use magicksave()
local vips = require("vips")

local image = vips.Image.new_from_file("test.gif", {n = -1})
image:magicksave("test2.gif")

but that gives me a no such operation error.
Is this a limitation of the Lua binding? Am I doing something wrong?
My libvips version is 8.10.2.
Thanks in advance!

Hi @RiskoZoSlovenska, it sounds like your libvips has been built without libmagick support.
You'll need to install imagemagick-dev and then reconfigure and rebuild libvips.

Hi @RiskoZoSlovenska, it sounds like your libvips has been built without libmagick support.
You'll need to install imagemagick-dev and then reconfigure and rebuild libvips.

Apologies for the absurdly long radio silence. I see a gif saver has been added at some point since I asked this (yay!), and as such I no longer have a problem. Thanks!

Yes, libvips 8.12 has its own GIF saver now. There are some notes and a benchmark here:
https://www.libvips.org/2021/11/14/What's-new-in-8.12.html


Fix regression on view expand

View should no longer be able to expand for indices past the number of row pivots.
Add tests to confirm expand works as intend
Refactor view.cpp to explicitly specialize expand(), collapse(), and set_depth()

Thanks for the PR!


Southalc podman module doesn't enable service

From the podman v0.6.7 module on forge.puppet.com:
enable
Data type: Boolean
Status of the automatically generated systemd service for the container. Valid values are 'running' or 'stopped'.
Default value: true
There is an issue with the code in container.pp.  The variable $service_unit_file is defined as:
${User[$user]['home']}/.config.systemd/user/podman-${container_name}.service
In this code block, you don't specify the full path of the service:
$command_sp @("END"/L)
${systemctl} ${startup} podman-${container_name}.service
${systemctl} ${action} podman-${container_name}.service
| END
This code should be changed to:
${systemctl} ${startup} ${service_unit_file}

Hey, I'm using v0.6.7 (the latest release) in my environment. I can't say I've encountered this issue myself.
I'd expect this sort of thing could happen if a daemon-reload was somehow not executed?
Relevant sections
https://github.com/southalc/podman/blob/0.6.7/manifests/container.pp#L101-L157
https://github.com/southalc/podman/blob/0.6.7/manifests/container.pp#L300-L343
Could you share more details about the your environment and the specific issue you're having? (Debug logs might be good)

This has also been working for me, so I'm gonna close the issue.  If you're still having issues with user containers, try the quadlet type


[Question] Streams with 'chunked' transfer encoding cannot be played

The exact same stream transferred with the chunked Transfer Encoding does not play/is silent, but if sent over unchunked and with a content-length header, it plays.
I'm not necessarily suggesting that react-native-track-player support this. I'd just like to hear your thoughts on how difficult it might be to support. My use is case is that we're working on text-to-speech generation in elixir/phoenix and my team tells me there isn't a way to send an unchunked response, at least with their current architecture. HLS seems like it may be an option tho, so they are working on implementing that. However, I'm curious if it could be possible to play the chunked response with react-native-track-player. I think the only practical difference is the lack of content-length.

Which platform have you tested this?

We've just rolled an update to a lib and it started working. I have no idea what was going on.


Add BEAM Gitter channel to docs

Add the gitter channel https://gitter.im/exercism/xerlang (from #296) to:
https://github.com/exercism/xelixir/blob/master/docs/INSTALLATION.md
https://github.com/exercism/xelixir/blob/master/docs/RESOURCES.md
https://github.com/exercism/xelixir/blob/master/docs/LEARNING.md

Any reason to not also add https://elixirforum.com/ to at least resources and learning?

Resolved with #311


v10-rc3: Map-Rotation shows "Allies" on Warfare-Maps

Hey everyone,
as already discussed on discord (https://discord.com/channels/685692524442026020/706075642885832764/1269305968429371495), the new v10-rc3 update now shows "Allies" on warfare maps:

Is this intentional?
Thank you for your work!

Fixed, thanks!


G1GC Archive regions

GCToolkit recognized but does not use the data to account for G1 archive regions when calculating the size and occupancy of tenured.
GCToolkit's calculation of tenured should subtract archive regions from the tenured total.

I would love to work on this issue! Could you please point me to the specific file(s) that would need to be modified for this issue?

@kcpeppe for guidance :-)

@kcpeppe appreciate if you could provide guidance

@kkdlau - G1GCPauseEvent#getTenured()

Thanks, @kkdlau, for your contribution and for you patience with us!


Add blog post about INTERSECT video

I drafted the blog post to focus more on the video than on when the presentation will occur. @cosden if you think we should revise the blog post to be more like the others (or if you have other wording), please edits.

I cannot find the link to the file in the CircleCI build or I would post it here.

It's not building a preview because the date (in filename) is in the future. If you make it today's date it should build. It wouldn't display on the website either, until Monday.

I changed the filename, but I still don't see it in the preview

The preview drops the date. The page is here: https://41-293151248-gh.circle-artifacts.com/0/intersect-training.github.io/announcement/intersect-overview-video/index.html
And it appears on the main page: https://41-293151248-gh.circle-artifacts.com/0/intersect-training.github.io/index.html

Post preview: https://42-293151248-gh.circle-artifacts.com/0/intersect-training.github.io/announcement/intersect-overview-video/index.html
Front page: https://42-293151248-gh.circle-artifacts.com/0/intersect-training.github.io/index.html
@JeffCarver - over to you. If you're good with this, I am too.


After msd_lite is compiled into openwrt firmware, there is no luci, and terminal commands cannot be controlled.

After msd_lite is compiled into openwrt firmware, there is no luci, and terminal commands cannot be controlled. https://github.com/bauw2008/luci-app-msd.git provides a msd_lite available for personal testing.

https://github.com/kenzok8/small-package/tree/main/luci-app-msd_lite
I'm not sure if you have changed luci-app-msd.git and checked compile


Update documentation for use of MongoDB Atlas

Fixes #915
Hey,
Since mLab is being acquired by MongoDB, Inc.  I have made some changes in documentation for mLab.
Do you want any more changes?
Thanks

Thank you!


Update box-connector-examples.adoc

Fixed per the following PR: Update Box Connector with technical changes #338
closing this one.


CloudQuery Harvester Source Plugin

Hi Team, hopefully this is right place to ask, if not, I'd appreciate if you can direct me.
I'm the founder of cloudquery.io, a high performance open source ELT framework.
Our users are interested in a Harvester plugin, but as we cannot maintain all the plugins ourselves, I was curious if this would be an interesting collaboration, where we would help implement an initial source plugin, and you will help maintain it.
This will give your users the ability to sync Harvester data to any of their datalakes/data-warehouses/databases easily using any of the growing list of CQ destination plugins.
Best,
Yevgeny

@yevgenypats It sounds a good idea. How would you like to start ?

@w13915984028 Awesome! Can you please open an empty repo at https://github.com/harvester/cq-source-harvester (with empty README) so we can fork and open a PR  ?

@yevgenypats We have an new repo now: https://github.com/harvester/cq-source-harvester

No further response, close. Feel free to reopen, thanks.


Allow signing hex messages from stdin

subkey can't sign or verify hex-encoded messages right now (using -h) because hex decoding chokes on the trailing newline.
 I'm not sure we should modify the message depending on what we expect.

-n works!


fix minor issues in the script Update check-orphans.sh

Type

[ ] feature
[x] bugfix
[ ] dev (no functional changes, no API changes)
[ ] fmt (formatting, renaming)
[ ] build
[ ] docs
[ ] testing

Description

Removed unnecessary quotes around 0 in the condition check:
In Bash, it's standard to avoid quotes around numeric values in conditions. This update replaces if [ $? -ne '0' ]; then with if [ $? -ne 0 ]; then, making the code more consistent with common Bash practices.

Simplified echo command by removing -e flag:
The -e flag in the echo command is used to interpret escape sequences, but there are no special characters to interpret in the string. Therefore, the flag was removed, and the code is now cleaner and more efficient.

Breaking changes?

[ ] yes
[x] no

Hey @mdqst thanks for the contribution.
Im closing this PR as we are removing the check-orphan script


Header of locked requirements does not include Python version

Hello, I noticed that pip-tools includes the Python version compiled against in the header, while uv does not:
1,6c1,2
< #
< # This file is autogenerated by pip-compile with Python 3.12
< # by the following command:
< #
< #    pip-compile requirements.in
< #
---
> # This file was autogenerated by uv via the following command:
> #    uv pip compile requirements.in -o requirements.txt

As we know, until a platform-agnostic lock file is created, the output depends on the Python version.
Having the version included is useful for caching mechanisms, typically in CI where the venv can be cached based on the hash of the requirements.txt file.
As a workaround for now, we can add the version in UV_CUSTOM_COMPILE_COMMAND.
Results above from pip-tools 7.4.1 / uv 0.1.44.

@charliermarsh I've proposed a change in dependabot that relies on the tiny piece of string autogenerated by uv to decide if it should use uv pip compile instead of pip-compile. I'm worried about the brittleness of this approach but if we don't have any better ideas, I would like to at least add a test that ensures this doesn't change without warning. I can try adding it if you think that helps.


fix dev error reading matches

[x] fix dev error reading matches
[x] fix unclosed div

Screenshot:

Hi @felipetodev, What do you think about add something like the following code instead of the optional chaining to avoid render an empty header:
{
	firstDayWithPendingMatches && (

	)
}

Hi @felipetodev, What do you think about add something like the following code instead of the optional chaining to avoid render an empty header:
{
	firstDayWithPendingMatches && (

                ...

	)
}

you right! thanks 4 the advice @PChaparro ✌

@felipetodev Can you confirm if closing the non closed
 tag fixes the #277 issue?

@felipetodev Can you confirm if closing the non closed
 tag fixes the #277 issue?

Yes, closing that div that section works correctly

Yes, closing that div that section works correctly

Nice! Can you add the issue number on the pull request description? That will make the issue to close automatically when this pull request goes merged.
You can add it like this:
Fixes: # 277
(Remove the space between the # and the number).

Yes, closing that div that section works correctly

Nice! Can you add the issue number on the pull request description? That will make the issue to close automatically when this pull request goes merged.
You can add it like this:
Fixes: # 277
(Remove the space between the # and the number).

Ready. Thank you! @PChaparro 🫰


error in make

Error in make for compiling the Openblas library such as follows:

Backtrace for this error:
#0  0x2B66E2D51697
#1  0x2B66E2D51CDE
#2  0x2B66E35AE27F
#3  0x2B66E2E104C0
#4  0x2B66E2E1DE27
#5  0x403281 in MAIN__ at sblat1.f:?
make: *** [level1] Segmentation fault (core dumped)

Which version of OpenBLAS is that, and which compiler are you using ? (If gcc+gfortran, please make sure they are both the same version)

The version of OpenBLAS is 0.3.10. The version of gcc and gfortran are both 9.1.0.
At 2020-08-13 22:13:36, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Which version of OpenBLAS is that, and which compiler are you using ? (If gcc+gfortran, please make sure they are both the same version)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Very strange. E5-2678v3 should be standard "Haswell" architecture, I do not see why OpenBLAS should fail in this simple single-precision BLAS test unless there is a problem with your hardware.

sorry！Maybe my information is not enough. I found the library path is wrong:
../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../..  -lc
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls -m64  -mavx2  -o dblat3 dblat3.o ../libopenblas_haswellp-r0.3.10.a -lm -lpthread -lgfortran -lm -lpthread -lgfortran -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../..  -lc
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls -m64  -mavx2  -o cblat3 cblat3.o ../libopenblas_haswellp-r0.3.10.a -lm -lpthread -lgfortran -lm -lpthread -lgfortran -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../..  -lc
gfortran -O2 -Wall -frecursive -fno-optimize-sibling-calls -m64  -mavx2  -o zblat3 zblat3.o ../libopenblas_haswellp-r0.3.10.a -lm -lpthread -lgfortran -lm -lpthread -lgfortran -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../..  -lc
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./sblat1
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0  0x2AB256D97697
#1  0x2AB256D97CDE
#2  0x2AB2575F427F
#3  0x2AB256E564C0
#4  0x2AB256E63E27
#5  0x403281 in MAIN__ at sblat1.f:?
make[1]: *** [level1] Segmentation fault (core dumped)
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/public1/home/sc50250/software/OpenBLAS-0.3.10/test'
make: *** [tests] Error 2
I use the gcc 9.1.0, but the libthread and libgfortran path is gcc 4.8.5. I wonder to know how to change the library path.
At 2020-08-13 23:29:43, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Very strange. E5-2678v3 should be standard "Haswell" architecture, I do not see why OpenBLAS should fail in this simple single-precision BLAS test unless there is a problem with your hardware.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Possibly you still have a link from /usr/bin/cc to the old gcc ? And you should be able to set the library path with `export LD_LIBRARY_PATH= to where your gcc lib (or lib64) directory is.

[sc50250@ln22%bscc-a OpenBLAS-0.3.10]$ less Makefile
[sc50250@ln22%bscc-a OpenBLAS-0.3.10]$ echo $LD_LIBRARY_PATH
/public1/soft/gcc/9.1.0/lib64:/public1/soft/gcc/9.1.0//lib64:/public1/soft/gcc/9.1.0//lib:/public1/soft/gcc/9.1.0//libexec:/public1/home/sc50250/software/lib/openblas/0.3.10_gcc4.8.5/lib:/public1/home/sc50250/software/openmpi_install/lib:
The gcc9.1.0 lib directory is already added the DLL.
At 2020-08-14 00:02:40, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Possibly you still have a link from /usr/bin/cc to the old gcc ? And you should be able to set the library path with `export LD_LIBRARY_PATH= to where your gcc lib (or lib64) directory is.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

The gcc 9.1.0 lib directory exist in the DLL path, but the make command still use the old gcc lib directory.
At 2020-08-14 00:02:40, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Possibly you still have a link from /usr/bin/cc to the old gcc ? And you should be able to set the library path with `export LD_LIBRARY_PATH= to where your gcc lib (or lib64) directory is.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hmm. And you did the build with something like make CC=/public1/soft/gcc/9.1.0/bin/gcc FC=/public1/soft/gcc/9.1.0/bin/gfortran ?

It is ok!  Thanks
At 2020-08-14 00:32:14, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Hmm. And you did the build with something like make CC=/public1/soft/gcc/9.1.0/bin/gcc FC=/public1/soft/gcc/9.1.0/bin/gfortran ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It is ok! But i wonder to know what's the difference between the two?
At 2020-08-14 00:32:14, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Hmm. And you did the build with something like make CC=/public1/soft/gcc/9.1.0/bin/gcc FC=/public1/soft/gcc/9.1.0/bin/gfortran ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Well, you did not write what you did before, so I can only guess. If CC is not set, the c_check script will default to using the "cc" command for figuring out what compiler and libraries to use. If /usr/bin/cc is still linked to the old gcc-4.8.5 that came with the original system installation, this will put the wrong entries in the generated Makefile.conf

Ok. Thank you very much!
At 2020-08-14 01:03:23, "Martin Kroeker"<EMAIL_ADDRESS>wrote:
Well, you did not write what you did before, so I can only guess. If CC is not set, the c_check script will default to using the "cc" command for figuring out what compiler and libraries to use. If /usr/bin/cc is still linked to the old gcc-4.8.5 that came with the original system installation, this will put the wrong entries in the generated Makefile.conf
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Add container labels to service create/update

This is related to #24067 and would fix it in a way.
Swarm mode makes it possible through the API to set labels to containers but not through command line. This tries to fix it 👼.
Quoting @stevvooe

SwarmKit and docker swarm-mode supports labeling both. We don't propagate service labels to containers so that one can put sensitive labels on the service and trust those separately from the container labels. While it seems intuitive that they would propagate, there are valid use cases for them not to propagate.
Not sure why these aren't in the CLI. That seems like the major omission here.

This adds --container-label on service create and --container-label-add, --container-label-rm to service update.
Is commented on #24067, I think this would be a little weird to not have the possibility to add container labels in 1.12 (lots of tools from the ecosystem uses them at container labels and to ease the evolution to service it would be a good way to break less stuff).
Putting his on 1.12 milestone even though I know it's pretty late to add this for the release :sweat:.
/cc @thaJeztah @stevvooe @icecrime @aaronlehmann @tiborvass
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Design LGTM.

I'm carrying it

Carried in #25038


Support preconditioners for linear solvers?

At the moment, none of our linear solvers (gmres, bicgstab, and cg) actually support preconditioning. How about creating an abstract_precond type with type-bound procedures apply(x) and undo(x) (or something along those lines)?
If we take gmres as an example (assuming we standardize the interface as suggested in #25), the interface could be
subroutine gmres(A, x, b, info, precond, opts)
    !> Standard arguments.
    ...
    !> Preconditioner
    class(abstract_precond), optional, intent(in) :: precond
    class(abstract_precond), allocatable :: P
    logical :: has_precond = .false.

    !> Check whether a preconditioner has been passed or not.
    if (present(precond)) then
        has_precond = .true. ; P = precond
    endif

    ....

    return
end subroutine gmres

and we have some P%apply(x) and P%undo(x) wherever needed. For the sake of simplicity, I think only right preconditioning should be supported, i.e. $\mathbf{A} \mathbf{P} \mathbf{P}^{-1} \mathbf{x} = \mathbf{b}$ where $\mathbf{P} \simeq \mathbf{A}^{-1}$.
What do you think?

I have just send a PR for this. For the moment, preconditioning is only effective for gmres. I need to dig a bit deeper to see how preconditioning impacts the cg and bicgstab iterations. It will be needed eventually but I think we can get away with just gmres for the time being.


Add TPL5111 for super low-power shutdown

https://cdn-shop.adafruit.com/product-files/3573/3573_datasheet.pdf

Use a ~five minute interval

This might not work. Looks like the TPL5111 has a watchdog feature that causes it to shutdown at the interval if it has not been powered down yet.

LTC5956 (https://www.analog.com/media/en/technical-documentation/data-sheets/2956fa.pdf) should do the trick.

Soldering the test component didn't work. Just put it on the next version with a bypass.

Sounds like it can be hooked up to a button that does a full shutdown. I should look into this!. Would be nice to have a soft shutdown button...

LTC2956 Operation
RUN Mode
Awake State
Exits awake state when:

Falling edge detected on !SLEEP pin
OR t_ONMAX expires

So, we need to make sure that t_ONMAX does not expire. SLEEP should only occur on a falling edge to !SLEEP performed by the teensy.
Settings
ONMAX
ONMAX is tied to GND because it is unused.
Resistors
R_long is 1.02 MOhms, corresponding to a power-up RUN mode and an 8.2 second LONG delay
R_RANGE
is set to 61.9 kOhms corresponding to a period between 102s and 14 minutes.
R_PERIOD
is set to 117 kOhms which is roughly 5 minutes
(1024 * 117) / 400 = 299.5 seconds
NB: Could also use 2-3 digital pots to set this...

Using the AD5248 (https://www.analog.com/media/en/technical-documentation/data-sheets/AD5243_5248.pdf) to switch the timing is an interesting idea, but too complicated for this. I should just set a 5-minute timer with fixed resistors and be done with it for this version.

Resolved with e5c251fa29a354784e84738623c5bc9274a97c33. Final checks required.


installation error with python3.10

Hi,
Thank you for developing this great repo.
I have a trouble in installing matbench with python 3.10 using pip install matbench. The error might be occurred due to sklearn==1.0.1. I'm wondering if the fixing version of sklearn can be omitted, for example, sklearn>=1.0.1.
Thank you in advance for your answering.

Apparently, scikit-learn didn't provide a wheel in version 1.0.1. They fixed that on version 1.0.2: https://github.com/scikit-learn/scikit-learn/issues/21511
I also tried pip installing on version 3.8.18 and had a problem while compiling something
Cython.Compiler.Errors.CompileError: sklearn/ensemble/_hist_gradient_boosting/splitting.pyx
However, the repo's last version updated the setup.py to make the requirements less restrict.
Cloning and installing using the setup.py works fine for me both on python 3.8.18 and 3.10.13

This issue also causes  pip install matbench to currently fail on Google Colab notebooks.
While pip install git+https://github.com/materialsproject/matbench.git does work, a new release to update PyPy would be appreciated 🙏

Even with that fix, there are dependency issues on import:
ContextualVersionConflict: (scikit-learn 1.2.2 (/usr/local/lib/python3.10/dist-packages), Requirement.parse('scikit-learn~=1.3'), {'matminer'})


Heroku site is broken

I was really excited to learn more about dragons but the Heroku app is experiencing an error.

thank you!
fixed: https://github.com/wbruno/dragons-api/commit/ef2c752e2dfeb4d5b44b58d8a1f05e408c00283c
the dragons are alive again!
http://dragons-api.herokuapp.com/api/dragons

Wow, that was fast! Thanks 👍 💯 :1st_place_medal:


added owerflow-y-scroll class to DetailView component

Fixes long text overflow in view modal

Hi, @thezahedi
Try new version pls


SQL server exception during run

Hi
As I follow your readme, I get SQL error
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have tried to do in the package console:
update-database
doing following in the webapi project throws exception in the SQL server
dotnet run
I have tried opening 1433 default SQL server port and still not working.

Hi,
The Web API project connects to SQL Server using the . (dot) alias - this points to the local machine instance. Review the connection string here; https://github.com/JasonGT/NorthwindTraders/blob/master/Northwind.WebApi/appsettings.json. You might need to updated dependent on the configuration of your environment, for example if you are using a named instance or if you have not windows authentication.
You could install SQL Server Management Studio and try connecting to . (dot) to see if everything is working normally.
Good luck!

I just changed '.' to '(localdb)\mssqllocaldb' and used 'update-database' in the package manager console.
Now I see all the tables and database in local.

Awesome, thanks for sharing your solution.


Bring back the mascot

Description
I saw on Reddit that the Hypr-chan wallpapers have been removed. The boomers still using Reddit in 2024 are now rejoicing in the fact that Hyprland has become more matured. I think it has become less cool, perhaps we might even call it Boomerland now. Speaking on behalf of Gen-Z and feminism, I protest that Hypr-chan be added back.
From Reddit:

Nothing said "accessible software for everyone" than a drawing of an overtly sexualised girl... Good riddance.

The girl is not even overly sexualized. It's just a cool girl wearing nice outfits. Only the patriarchy would ever say something like that.
Nothing says "accessible software for everyone" than based non-corpo pilled software with a waifu mascot.
I see from the commit that there was a contest, and I don't know how it was conducted. If I were to know nothing better, I'd say the voting was hijacked by corporate AI to enforce the will of American right wing traditionalist capitalists. How did this abomination (which is the corpse of Hypr-chan, how disrespectful) win instead of this?
To the complaining boomers: the future is now, old man.
 If no, set disable_hyprland_logo to true before loading the wallpaper.

firstly, https://github.com/hyprwm/Hyprland/blob/main/assets/wall2.png
secondly, I don't care about you protesting

secondly, I don't care about you protesting

neither do I, as this is a joke.
Also the old one was subjectively better but I guess you've made your choice.


Small XRootD authZ doc fixups

I was able to get to a pair of the most egregious issues

CI unrelated, merging


DPVP: Add TruePVE PVP exit delay support

Need to implement support for new TruePVE API for efficient/cross-plugin PVP exit delays.
Should probably follow what I did for PBPZ here.
Should probably also unsubscribe from damage hooks when using this.

Implemented for 4.3.0.


this for social learning purpose

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

started from 06 march 2020

@lincoilntgl Thank you for your feedback. There doesn't seem to be enough details in the
issue for us to work on. If this really is a documentation issue and I have
misunderstood, please reopen it with more information.


[docs] Quick docs review

[ ] Simplify URL and folder structure by removing documentation from the path
[x] Home page index.rst should be what's now Introduction to Rubrix. Ideally, this page will still be the first item of the Getting started block (I've seen this in other docs) but if it's not easy to do, no problem.
[x] Rename Introduction to Rubrix -> Rubrix docs
[ ] Add right-side table of contents (toc) to each page, with a header like "On this page".
[x] Merge Concepts and Methods into one section called Concepts (I think is a heading issue).
[ ] Try to include the video on the home page with autoplay and using either html5 or a sphinx-contrib package.
[ ] Complete the home page (what's now Intro to Rubrix)
[ ] Complete missing things in Concepts (keep it as simple as possible).
[ ] Add Community section, with direct links to github and github discussion forum.

Wouldn't it be nice to add the direct links to github and the discussion forum on the Next Steps section of the first page (Intro to Rubrix)? Mainly because it would be an almost empty section, unless you want to include more things.

Good idea, you can include them there. In any case we will be adding more
content in that part, with the goal of guiding the reader to the content of
the documentation.
El mié., 12 may. 2021 9:35, Ignacio Talavera @.***>
escribió:

Wouldn't it be nice to add the direct links to github and the discussion
forum on the Next Steps section of the first page (Intro to Rubrix)? Mainly
because it would be an almost empty section, unless you want to include
more things.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/recognai/rubrix/issues/26#issuecomment-839538080, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIOJJ6DVGTQCKUE5FIJ46TTNIVVPANCNFSM44W5SMPA
.

@ignacioct I like. I would put a permanent link to GitHub somewhere in the header, i find it always super useful.
Ideally we want to have a PR for each of the items listed above, and check it once the PR is merged and put a reference there. Would you mind providing a PR for the items you already implemented?

I think this can be now closed, we've at least looked at everything here 😃


Always see google results??????

Why so much google results shown? How am o supposed to know what to analyze??
[POC][G][GET][BAV/OR] http://google.com [POC][G][GET][BAV/OR] https://www.google.com/%2f%2e%2e [POC][G][GET][BAV/OR] https://google.com// [POC][G][GET][BAV/OR] http://www.google.com/%2e%2e%2f [POC][G][GET][BAV/OR] http://google.com// [POC][G][GET][BAV/OR] https://google.com/%2f.. [POC][G][GET][BAV/OR] http://www.google.com/%2f%2e%2e [POC][G][GET][BAV/OR] https://google.com/ [POC][G][GET][BAV/OR] https://google.com [POC][G][GET][BAV/OR] http://google.com/%2f.. [POC][G][GET][BAV/OR] https://www.google.com/%2e%2e%2f [POC][G][GET][BAV/OR] http://google.com/ [POC][G][GET][BAV/OR] http://google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/?gws_rd=ssl [POC][G][GET][BAV/OR] https://www.google.com/?gws_rd=ssl [POC][G][GET][BAV/OR] https://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/?gws_rd=ssl [POC][G][GET][BAV/OR] https://www.google.com/?gws_rd=ssl [POC][G][GET][BAV/OR] https://google.com// [POC][G][GET][BAV/OR] https://www.google.com/%2e%2e%2f [POC][G][GET][BAV/OR] http://google.com [POC][G][GET][BAV/OR] http://www.google.com/%2f%2e%2e [POC][G][GET][BAV/OR] http://google.com// [POC][G][GET][BAV/OR] https://www.google.com/%2f%2e%2e [POC][G][GET][BAV/OR] http://google.com/%2f.. [POC][G][GET][BAV/OR] http://www.google.com/%2e%2e%2f [POC][G][GET][BAV/OR] http://google.com/ [POC][G][GET][BAV/OR] http://google.com/ [POC][G][GET][BAV/OR] https://google.com/ [POC][G][GET][BAV/OR] https://google.com/%2f.. [POC][G][GET][BAV/OR] https://google.com [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] http://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/ [POC][G][GET][BAV/OR] https://www.google.com/?gws_rd=ssl

Hiya @DaddyBigFish
Dalfox includes a feature called BAV, which encompasses various passive scanning rules. However, this feature tends to produce a lot of false positives, and it seems like the information you've sent might also be a false positive.

[POC]: This is PoC
[G]: From Grep
[GET]: HTTP Method
[BAV/OR]: Open Redirect Rule

So I'm going to change the BAV so that it doesn't activate by default. More question?

No more questions thank you the tool is excellent 🙏


Added popup before deleting the file (#136)

Hey, i have added the popup before accidently deleting a file, it asks for a confirmation before deleting it.
Issue (#136)

@srivastavaritik , hey please merge this


Migrate to Django2 path urls

Closes #1519.

@saschalalala any news of this one?

@webyneter Yeah, just did the things @browniebroke mentioned and looked around in basically all other files if I missed something more but just found the development default url in settings.rst which I also adjusted to stay consistent.


pythonPackages.robotframework: 3.0.4 -> 3.1.2

pythonPackages.robotframework: source file is zip formated

Motivation for this change
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] 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)
[X] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Should the plugins not be updated?


az monitor diagnostic-settings create will not accept same json as returned by show for 'logs'

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: script
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here: 2.0.3
OS Version: What OS and version are you using?
Answer here: Ubuntu 16.04 x64
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

Description
The input to logs option for monitor create won't accept the logs array as returned by 'az monitor diagnostics-settings show' - you have to strip out the 'retentionPolicy' elements. This seems incorrect.
Example in my case:
  "logs": [
    {
      "category": "ApplicationGatewayAccessLog",
      "enabled": false,
      "retentionPolicy": {
        "days": 0,
        "enabled": false
      }
    },
    {
      "category": "ApplicationGatewayPerformanceLog",
      "enabled": false,
      "retentionPolicy": {
        "days": 0,
        "enabled": false
      }
    },
    {
      "category": "ApplicationGatewayFirewallLog",
      "enabled": true,
      "retentionPolicy": {
        "days": 0,
        "enabled": false
      }
    }
  ],

It fails with:
u'retentionPolicy'
Traceback (most recent call last):
  File "/users/nneul/lib/azure-cli/local/lib/python2.7/site-packages/azure/cli/main.py", line 36, in main
    cmd_result = APPLICATION.execute(args)
  File "/users/nneul/lib/azure-cli/local/lib/python2.7/site-packages/azure/cli/core/application.py", line 201, in execute
    result = expanded_arg.func(params)
  File "/users/nneul/lib/azure-cli/local/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 403, in _execute_command
    raise ex
KeyError: u'retentionPolicy'

@vishrutshah it looks like the UX here could use improvement.

Command insists on 'resource-id' when it should support names or IDs.
It really doesn't seem like "create" is the right verb here. If anything it seems more like a "configure" command.
The JSON dump doesn't seem necessary at all. It seems I should be able to simply specify the name, whether it is enabled or not, and a retention period (optional).

No disagreement with @tjprescott comments, my issue was more: If it's going to take json for the settings, it should at least accept the same json as input that is output by the same command.

@nneul agreed.

@nneul Thanks for reporting this issue. Yes we agree that it should take the logs.
I see that you mentioned that you have to stip out retentionPolicy. Could you please try keeping them but renaming it retention_policy. I believe that is the case for the issue. Let me know if that works or not.
Meanwhile, I am working on fixing the issues to take the same json as input. 👍 Thanks again for reporting the issue.

Yes, using retention_policy proceeds without error.

@nneul Closing the bug as PR is merged in. Could please use the nightly tomorrow and let us know whether things are good on you end or not. Appreciate your help.

Confirmed that this is now working. Thank you!


Extended telemetry for tracking users and sessions

Coverage decreased (-0.02%) to 99.98% when pulling 74ca490a6e41e75682e5718861d3e377d3214140 on waldekmastykarz:enh-telemetry into ca98f341f563d3da0d77dad90dc42c6a274063fd on SharePoint:dev.

Merged manually


Updates to docs to fix the compilation errors on RTD

:white_check_mark: Build SMT 0.1.172 completed (commit https://github.com/SMTorg/SMT/commit/42f989f977 by @)


"Poiana", "Poienița" are listed in the drop-down menu

Description:
When user writes ” Poiana” and "Poienița" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Poiana"

Expected results
The location appears in the drop-down menu as "Sat Poiana, DÂMBOVIȚA (Poiana)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Poienița"

Expected results
The location appears in the drop-down menu as "Sat Poienița, DÂMBOVIȚA (Poiana)".


Add webmention support

Is your feature request related to a problem? Please describe.
It would be a better IndieWeb experience to have the theme pull in and display webmentions as suggested in #12.
Describe the solution you'd like
There are services like https://webmention.io that can be used to aggregate webmentions for static sites. However, this will involve adding JavaScript that makes external requests; this should be well documented for users to understand and implemented in such a way as to maintain site download speed, and disabled by default.
Describe alternatives you've considered
None.
Additional context
PR #39, opened by @kisik21, starts us off on this work! 🎉

Could you also take alook at https://webmention.app/?

@xavierroy webmention.app is used with outgoing webmentions, while webmention.io (and the scope of this issue) is processing inbound webmentions.


UI: Supporting merge strategies

We should allow to choose source-wins or dest-wins from the UI as well.

Duplicate: #3266


How is "done" variable being defined in exploration task?

Hello, I observe the following code in habitat_extensions/exploration_demo.py. And I am confused how is the value of "done" being computed.
while True:
obs, reward, done, info = env.step(action)
if done:
obs = env.reset()
Apart from the maximum number of steps per episode, is there any other condition for an agent to finish one episode? For example, if the agent has fully explored all spaces in the house before the number of experienced steps reaches the allowed maximum number of steps per episode. Will the agent finish this episode and perform env.reset()?

Sorry for asking. I have found the answer by checking the code in habitat module.


[Feature] Detailed lunar information: make them dynamic?

Short summary
Showing the direction, altitude, illumination and distance dynamically when the user hovers over the moon's trajectory would be interesting
Detailed description
Currently, when you hover over the trajectory, it shows the elevation in an info box. Updating the detailed info too below would be fun
Examples 🖼

This is an interesting idea, I'll try to expand this information in the tooltip, instead of adding info for current time.

I'll try to expand this information in the tooltip, instead of adding info for current time.

I thought you could replace the info for the current time with the info at the "hovered point". Then back to current when the cursor stops hovering over the trajectory.
But the tooltip works too...

@Nickduino, I added a function to update the date simultaneously with hover over point. I will fix other bugs and release a new release 🎉

This is so cool! :heart:


Is there a way to get the current/ambient temperature?

Most AC units I've done code for return the current/ambient temp reported by the AC unit.  Browsing thru the properties returned from the cloud service I see the setpoint temp but nothing that jumps out as a current room temp.  The unit must know the temp as it needs it to adjust what it's doing to cool/heat the room.  FGLair app also shows no local temp for any of the 4 Fujitsu units I have so I'm pretty sure I'm not just missing it.
Anyone know how to get this info?  I use it a lot in my home automation to watch for problems with AC units (running on Cool, High fan and the temp isn't changing much or at all over time, for example).

Hi,
Depends on what indoorunit/wifi adapter you have.
The old adapters for the old indoorunits do not forward the current temperature.

I don't get the temperature reading either, but I can poll it with FGLair app, so it SHOULD be possible.

I CAN poll ambient temp on AC via FGLair app, but it won't show on any cards I use in HA.


WhatsApp bans clients using old proto version

I created a new WhatsApp account and when i try to read the qr code, this number got instantly banned. WhatsApp app says your account is banned and i am no longer able to use whatsapp with that number.  I found the js file that contains the proto structure of the new version. Will you update the def.proto file? Or how can i create updated version of def.proto using that js file on WhatsApp web servers?
#48 same problem :/

I don´t know how the def.proto is created. We got it from sigalor/whatsapp-web-reveng. The latest update there is 3 months old. I already asked for the extraction method over there. link

Duplicate of #48