implement position management for class Window

This is a subtask of #6

Completed. Still to be tested.
Added constructors signatures.
Fixed an erroneous method naming in module oglfw_errors.ixx.
Fixed a few bugs and removed move operators or constructors in module oglfw_utils.
Enhanced ordering of declaration and definition of constructors signatures in class Window.


[CM-28] Process post request with mastery learning info

Jira Ticket

Jira Ticket
Description

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Changes

Created the function generate_cm_from_post_parameters, which is essentially a modified version of index
Added validation for the post request in validate_mastery_learning_post_request

Testing
I have not tested this yet, because I am not sure how to do so.
Checklist

[X] My branch name matches the format: <ticket-id>/<brief-description-of-change>
[X] My PR name matches the format: [<ticket-id>] <brief-description-of-change>
[ ] I have added doc-comments to all new functions (JSDoc for JS and Docstrings for Python)
[X] I have reviewed all of my code
[X] My code only contains major changes related to my ticket

Screenshots/Video

Additional Notes
Here is the proposed POST body schema:
{"school": [String], "class": [String], "[Insert concept name 1]": {student_mastery: [Integer], class_mastery: [Integer]}, "[Insert concept name2]":...}
The "school", "class", all concepts, and all nested "class_mastery" fields are optional

For testing, you should do a local integration test using the docker stack (you can use the dev stack)

Please add screenshots as necessary.  Also, you can give an example using postman

Please add screenshots as necessary. Also, you can give an example using postman

Will do!


Is this project still alive?

after adding a bunch of new Issues, I noticed that the last issues were from 2016.
So, is this project still alive and used?
thx

Hi,
Yes, it's still being used, but mostly in maintenance mode.
We're using https://feincms3.readthedocs.io/ and https://django-content-editor.readthedocs.io/ for new sites these days.

As an aside, I still use Feincms 1.x and plan to keep it alive as long as possible, as I have a lot of vested interest (aka lots of content types, and lots of sites running on it, and no budget to migrate "just because"). I haven't explored moving to feincms3 yet, as we are rather happy with the 1.x status.
    mjl

On 29 Jun 2018, at 15:57, Matthias Kestenholz<EMAIL_ADDRESS>wrote:
Hi,
Yes, it's still being used, but mostly in maintenance mode.
We're using https://feincms3.readthedocs.io/ and https://django-content-editor.readthedocs.io/ for new sites these days.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I should add that the "maintenance mode" comment above mostly concerns elephantblog, and not FeinCMS 1.x (which I am also planning to keep alive)

Alright, thx for the info about feincms3 and django-content-editor. Maybe you want to add hints to the feincms docs since that was my way of eventually lading here.
Anyways, cool, I probably don‘t have to implement my own blog with django :)

I guess that should be enough information for anyone interested, could be opened of course in the future in case it's needed. thx for the answers matthiask and mjl.

Btw, I'm starting a series of posts motivated by this exchange: https://406.ch/writing/the-future-of-feincms/


setting image_link_style = "markdown" not working [BUG]

Please confirm

[x] I am running the latest version of this plugin: yes

Describe the bug and expected behavior
In my setting I have setting image_link_style = "markdown" but the link included is [[zettelkasten/my_link]] instead of [](zettelkasten/my_link)
Operating system (please complete the following information):

OS: "Linux Mint 20 Ulyana"
neovim 0.7

Is it related to https://github.com/renerocksai/telekasten.nvim/issues/131 maybe?

I can't really reproduce the issue... When I use insert_image_link with a file that is already in img, it works as expected and insert ![](img/myimage.png).
But as in #131, the paste from clipboard stuff does not work.
Could you provide a bit more detail on what you are doing, what function you are calling, etc?

it is about a link to a file by the function lua require('telekasten').insert_link({ i=true }). Sorry for being imprecise! I can I prove more details and in case which one best?

insert_link inserts a link to a note. Currently, links to note can only be in wiki style: [[link]]
The config option image_link_style = "markdown" only applies for images. To post a link to an image, you must use insert_img_link.

So I think there is a bit of misunderstanding here. If you would like markdown links for notes as well, there is already issues #139) and discussions about that (#56). Was that it?

Ah sorry then I was really confused! Many thanks for the clarification!


UnusedPrivateClass has false positive behavior for deserialized items

Code:
   fun readId() =
       jacksonObjectMapper().readValue<Response>(content).id

  private class Response(
      val id: Int
  )

Expected Behavior
Response class is used, so rule "UnusedPrivateClass" skips it.
Observed Behavior
Rule "UnusedPrivateClass" warns, that Response class is private and is not used.
Context
Private classes for deserialization are very useful to hide interops inside deserialization wrappers.
Your Environment

Version of detekt used: 1.2.1
Version of Gradle used (if applicable): 6.0.1
Operating System and version: Windows 7 x64
Link to your project (if it's a public repository): NDA

Thanks for reporting this bug.


⚠ Bofrost.lu has degraded performance

In 573e6d1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1335 ms

Resolved: Bofrost.lu performance has improved in 8ac929e after 19 minutes.


How to specify DeletionPolicy to dynamodb ?

How to attach Deletion policy to software.amazon.awscdk.services.dynamodb.Table Class ?

Thanks for reaching out!
DeletionPolicy is an enumerable option of a CDK resource (cfnresource) in the Construct Library! I recommend taking a look at the Construct Library documentation.
Try something along the lines of: resource.options.deletionPolicy = DeletionPolicy.Retain;.
Let me know if this is what you were trying to accomplish!

I believe @mansisorathiya is asking about the dynamodb.Table construct (L2) and not the dynamodb.CfnTable construct (L1). Indeed, L1 have an options field which is where you can specify raw CloudFormation options for the low-level resource.
Some L2s (such as s3.Bucket) actually expose a removalPolicy prop which offers an API for defining the deletion policy, but we haven't gotten around to adding those to all stateful L2s (see #2282). It should be easy to add if you anyone is interested to pick this up.
As a workaround, you should be able to use an escape hatch like so:
const resource = table.node.findChild('Resource') as CfnResource;
resource.options.deletionPolicy = DeletionPolicy.Retain;


Add template typedef review usage test

_type is a property of the template typedef addded in this PR.
I merged updateTemplateUsage and checkTemplate to become the documented update_templateUsage method.
The undocumented updateTemplateUsage method was only called by the undocumented checkTemplate method which in turn updated the templateUsage param.
There are still a few things I want to check.
Having a custom_templates object and templateUsage object which are essentially the same but the latter has a counter feels odd.
The templates object can just be cloned with the count being added once.
It doesn't feel right to iterate through layers in locales to update_templateUsage on each iteration within an iteration.
The update usage should be done once after all locales and layers have been parsed.
I am worried that templates used in an entry, or dataview in a layer do not count to the usage if we only check the layer.templates and layer.template.

//We get the initial custom templates from the workspace.templates as we want to see usage of templates before we merge templates from layers.
    custom_templates = {
      ...Object.fromEntries(
        Object.entries(workspace.templates).filter(([key, value]) => value._type === 'workspace_template')
      )
    };

We get the initial custom templates from the workspace.templates as we want to see usage of templates before we merge templates from layers.
I added in this comment where I get the workspace_templates from the workspace.templates object before we merge the layer templates as we want to see what's explicit templates are in the workspace.templates that either need to remain or be removed.
If a template is being merged from a layer then chances are it's something that is needed for the workspace. But if its just old legacy config that is lying around this could help us 'couper le gras'.
If we have other ideas in how we could handle this, then lets discuss it :)

https://github.com/GEOLYTIX/xyz/issues/1494
I have updated the templates test spec with additional things we discussed.

   "template": {
          "key": "metrics_dwelling_privaterented_perc_thematic_2021",
          "template": "1-999"
        },

With a configuration as above, the used_templates array will contain
"used_templates": [
"1-999": 1
]

for example. It should use the key of the template instead

The template object: key should not be removed from unused templates and added to usage statistics as these are added to the templates object and not immediately used. This prevents double counting.
Instead the key should be added to the overwritten_templates set if the template existed as a _type=workspace template in the first place.

Just pushed a commit to sort the templates so related naming of templates are seen together - this is working as expected for me now - thank you!


Add regex capability to rcqt strings.

This is a feature request. Would it be possible to add regex capabilities to the rcqt strings that are being checked for correctness. For example, when a kernel check is made could we specify a kernel like this:

name: ROCm kernel support check
device: all
module: rcqt
os_version: Ubuntu 16.04.5 LTS
kernel_version: 4.13.0*
.
and have it match this 4.13.0-32-generic.
.
I would want to extend this to all types strings in the rcqt checking tests.

Merged in #364


Consider switching dependencies from moment.js to date-fns

For me,  the amount of size that moment.js adds to my builds is unmanageable. There are other issues:
https://github.com/date-fns/date-fns/issues/275#issuecomment-264934189
Date-fns has some very good endorsements:
https://twitter.com/dan_abramov/status/805030922785525760?lang=en
Would you consider, if I were to submit a pull request to switch the dependency from moment.js to date-fns?

+1.

I've just migrated the project to date-fns and the native Date type https://github.com/kkomelin/time-picker

See what has changed for the end-user here.
The Storybook examples work as expected npm start.
Most of the automated tests are successful npm test. There are a couple of failed. Need help with fixing them.

To play with the project, install it with npm i https://github.com/kkomelin/time-picker
Roadmap

[x] Perform migration from Moment.js to date-fns.
[ ] Fix the failed automated tests. Need help with this task.
[ ] Discuss with react-component/time-picker maintainers whether we release a new major version or keep two projects separate.
[ ] Depending on the results of the discussion, send PR to react-component/time-picker or release a new project.

I would appreciate your feedback and any help with testing and optimizing the code.

@kkomelin cannot run your fork 😭

@kkomelin cannot run your fork

@behagoras Why?


thinking about destructuring: allow value type name on declarations

What the heck?
Yes, I know, yuck, this breaks the beautiful annotations type/keyword name syntax followed by all declarations. But I think this has already been broken by destructuring.
What do we gain?
Regularity. The language would be easier to learn and easier to compile.
A little bit of backstory
When destructuring was first introduced, I thought it was really irregular that we wrote value foo and String foo while we wrote value [foo] and value [String foo]. This proposal gracefully solves that problem.
Regularity?
Imagine that you want to destructure a tuple. Here is how you’d do it:
value [v] = [""];

Imagine that we’d like to be explicit about the type:
value [String v] = [""];

Here we can clearly see that v is as much of a destructuring pattern as String v.
We can imagine the destructuring syntax being the following:

keyword? pattern = rhs

We can imagine the pattern syntax being the following:

type? identifier
[pattern+]
pattern->pattern

is conditions
Whenever the destructuring is done in an is condition, the keyword (is) and all the type must be present. That is, all the following are valid is conditions:
is Foo foo = bar

is [Foo foo] = bar

is Foo foo->Bar bar = baz

is [Foo foo->Bar bar] = baz

While all the following are invalid is conditions:
is foo = bar

[Foo foo] = bar

is Foo foo->bar = baz

is [foo->bar] = baz

exists conditions
Whenever the destructuring is done in an exists condition, the keyword (exists) must be present and each the type may be ommited. That is, all the following are valid exists conditions:
exists Foo foo = bar

exists [Foo foo] = bar

exists foo->Bar bar = baz

exists [foo->bar] = baz

While the following is an invalid exists condition:
Foo foo = bar

for
Whenever the destructuring is done inside a for, the keyword (value) and the each type may be omitted. That is, all the following are valid inside a for:
item in stream

value item in stream

String item in stream

value String item in stream

Integer key->String item  in stream.indexed

value Integer key->item  in stream.indexed

Assignements
Whenever the destructuring is done in a assignment expression, both the keyword and all the types must be omitted. That is, the following are all valid assignment expressions:
foo = bar

[foo, bar] = baz

foo->bar = baz

While the following is an invalid assignment expression:
String foo = bar

Declarations
Whenever the destructuring is done in a declaration, either the keyword (value) must be present, or all the types must be present. In the case the keyword is present, each type may be omitted. That is, the following are all declarations expressions:
value foo = bar

[String foo, String bar] = baz

value [String foo, String bar] = baz

Annotations
Whenever a destructured declaration is annotated with some annotations, it’s the equivalent of each destructured value being annotated with that annotation.
Shortcut refinement
Whenever the destructuring is done in a shortcut refinement declaration, both the keyword and all the types must be omitted. That is, the following are all valid shortcut refinement declarations:
foo = bar

[foo, bar] = baz

foo->bar = baz

Wait. What?
Yes, I know, destructuring for non‐locals, yuck. I’m only adding this for the proposal’s completion sake, because of its regularity. This is a feature you won’t see me defending too much.
Isn’t this more irregular compared to the rest of the language?
Maybe. I think destructuring as it currently exists in the language is pretty irregular by itself, by providing a non‐keyword/type name declaration. One could argue that this, while it makes the destructuring syntax more regular compared with itself, makes it stand out as different and irregular compared to the rest of the language. That’s a reasonable argument in my opinion.

What would be the difference between
is [Foo foo] = bar

and
exists [Foo foo] = bar

?

@xkr47
exists [Foo foo] = [bar] would fail to compile if bar’s compile‐time type isn’t a subtype of Foo?.
Analogous to how today’s exists Foo foo = bar fails to compile on the same conditions.

Wait, I haven’t thought about this completely. I think exists [Foo foo] = [bar] should fail if bar’s compile‐time type isn’t a subtype of Foo, and not Foo?.
It would also give an error in an older version of the language, since [bar] isn’t optional. I guess a better example would be exists [Foo foo] = [bar]  of [Bar]?.

To be clear about how this proposal actually differs from the syntax of Ceylon as it exists today, the main thing being proposed is two allow the following two things which are not currently allowed:
value String hello = "Hello";

And:
[Float x, Float y] = [1.0, 2.0];

That's actually not an unreasonable suggestion. The "irregularity" that is being raised here is that:

a destructuring statement always requires value before the pattern, even if types are explicit, but
a regular specification statement does not allow value in combination with a type.

Oh, wait, it would also imply allowing:
function String hello() => "Hello";

And:
value String name => ... ;
assign String name => .... ;

So I've now re-thought through all the syntax possibilities for allowing destructuring statements. Let's recap them all.
No value modifier or type anywhere at all
Initially, one might imagine that there is no need for a special additional keyword for a destructuring statement, and that one could simply write:
[x, y] = [1, 2];

The problem with that is that it looks like an assignment to pre-existing labels x, and y, not like a statement which introduces new labels. Compare:
x = 1;
[x, y] = [1, 2];

This would be unacceptably confusing.
Require value modifier or type on every pattern variable
OK, so, given that the syntax for introducing a new local is value x = 1, how about:
[value x, value y] = [1, 2];

That seems reasonable in the very simplest case where you have only two pattern variables. It starts to become unacceptably verbose very soon after that. Consider:
[value x, value k -> [value a, value b]] = [1, 2->['x', 'y']];

That's really quite verbose. And what about patterns in, for example, a for loop? Would I also be expected to write:
for ([value x, value y] in pairs)

That would be pretty nasty, since the value keyword (or type) is not usually required when declaring control structure variables.
The current syntax
Hence we arrived at the current syntax. We added a new type of statement, distinguished by a keyword. You can think of the things it defines as being basically control structure variables. So:
value [x, y] = pair;

and:
for ([x, y] in pairs) {}

Are the same sort of "thing" in the language, and the rules applying to the destructuring pattern are the same. Now, sure, perhaps one could argue that the syntax should have been:
value ([x, y] = pair);

Or that we shouldn't have reused the keyword value just because that's one we already had lying around. Hell, just now it occurs to me that perhaps it should have been:
let ([x, y] = pair);

And if that had been the syntax we had chosen, I bet we would not currently be having this discussion. But let's be clear: the value keyword in the current syntax is, conceptually, like the let above. It is not the same thing as the value keyword you can write in place of a type when defining a label.
It seems to me that this entire issue arose because @Zambonifofex is confused about the two very different roles which value serves in the language:

as a replacement for a type when defining a label with an inferred type, and
as a way to syntactically distinguish a destructuring statement (which is, conceptually, a lot like a control structure).

That is to say, there's absolutely nothing conceptually wrong with:
value value x -> value y = 1 -> 2;

Since here the first value is a completely different thing to the other two. It just means, in pseudo-ceylon:
let (value x -> value y = 1 -> 2);

Sure, it looks a bit funny because of the value value, but of course nobody every actually writes that.
However, sure, we can still ask ourselves if any improvement is possible.
Require value or type on at least one pattern variable or the whole statement
One option might be to allow any of these options:
value [x, y] = [1, 2];
[value x, value y] = [1, 2];
[value x, y] = [1, 2];
[x, value y] = [1, 2];

I think it's clear that this is wrong, since value now has an effect that goes beyond the label to which it directly applies.
However, note that @jvasileff came up with a way to rescue this idea, but with somewhat different semantics, which I'll come to later.
Require value or type on every pattern variable or the whole statement
A second option might be to allow either of these:
value [x, y] = [1, 2];
[value x, value y] = [1, 2];

At first this doesn't seem unreasonable. But:

even pattern variables in nested patterns would need the value modifier or type, even though
pattern variables in control structures don't, and
it's significantly harder to parse, and
adds no value at all, since the first form is always less verbose and is what everyone would write in practice.

Therefore see no value at all in adding this. It wouldn't make the language better.
Disallow types in destructuring patterns
Since I've observed on many occasions that there is almost no reason to every explicitly write in the type in a destructuring pattern, one very simple solution would be to simply disallow, or, more precisely, deprecate that syntax. Thus, this would no longer be legal:
value [Integer x, Integer y] = [x, y];

And, therefore, we would remove the possibility of value value.
One argument against this would be that types are useful for tuple cases in switch, for example case ([Integer x, Integer y]), but arguably that's a different kind of thing anyway.
Honestly this outcome would be perfectly acceptable to me, but I don't particularly see how it would make the language better. I suppose it makes the language simpler, strictly speaking, which I suppose is better.
Allow assignment in destructuring statements
As suggested by @jvasileff, a way to rescue one of the options rejected above would be to say that we can assign to pre-existing labels from within a destructuring statement, so this would be legal:
Integer x;
[x, value y] = [1, 2];

Then, he suggests, the existing syntax would be a way to say that the value modifier distributes over all the pattern variables, so:
value [x, y] = [1, 2];

would just be an abbreviation of:
[value x, value y] = [1, 2];

This looks very reasonable, though I have the following reservations:

it is really quite difficult to parse,
the idea of a keyword "distributing over stuff" is new to me and I'm not 100% sure I like it, and
it's not clear to me that it really truly addresses @Zambonifofex's objection, since value value would still be grammatical, AFAICS.

Ultimately, this is really a disguised request for a new language feature, and not strictly speaking a solution to the objection raised in this issue. In fact, it's really just a (nice) refinement of proposal #6513, and we should continue discussing it there.
Conclusion
Ultimately the only two possibly syntax changes that I would find to be acceptable "solutions" to the posed "problem" would be:

change the syntax of a destructuring statement to let ([x, y] = [1, 2]);, or
disallow types within patterns.

I guess I'm sorta warming up to 1. It's quite trivial to implement, of course, and perhaps it reads better:
let ([x, y] = [1, 2]);

vs
value [x, y] = [1, 2];

If we can't reach a consensus on doing either 1 or 2, then I'm simply going to close this issue, since I see it as an entirely trivial and unimportant objection to the syntax of the language. Indeed, I'm already itching to just close it and leave this whole discussion behind.

Frankly I prefer value [x, y] = [1, 2]; myself. Also I don't find let works nicely without a scope. To me it introduces a bound scope, and should be a block statement.

Also I don't find let works nicely without a scope. To me it introduces a bound scope, and should be a block statement.

@FroMage Yeah, I agree. That's probably why we didn't pick it in the first place.
This feels natural to me:
let ([x, y] = [1, 2]) {
    print(x);
}

This feels less natural:
let ([x, y] = [1, 2]);
print(x);

Indeed, I did very briefly suggest let in the original discussion:
https://github.com/ceylon/ceylon/issues/3626#issuecomment-156648695
But I rejected it because

This has nothing to do with a let expression.

And nobody else seemed to bite.
Or course, if this issue really boils down to changing a keyword, then it's a non-issue.

This feels natural to me:
let ([x, y] = [1, 2]) {
   print(x);
}

This feels less natural:
let ([x, y] = [1, 2]);
print(x);

Agree completely.

Other English words that read well:
assign ([x, y] = [1, 2]);
define ([x, y] = [1, 2]);

But:

this has seriously nothing at all to do with setters, and
adding a new keyword define to the language at this stage is something I don't see as an acceptable solution.

I don't wanna add more noise here, and, to be true, I tend to agree with @gavinking comments.
But I think there is a third approach to this.
IMHO, one big problem here is value being used as the destructuring keyword, overloading its semantics.
Reusing other keywords (like let) or introducing new keywords seems also problematic.
So, what about a variant for the actual keyword + parens: value(...)? This way we can differentiate easily a declaration (value label ...) from a destructuring (value (pattern) ...).
Pros:

It breaks the value value ...  pattern @FroMage is fighting against, by adding parents between them: value (value...)
It is agnostic about inner value/type/nothing is used inside the destructuring pattern.

[ ]  value ([x,y]) = [1,2];
[ ]   value ([value x, value y]) = [1,2];
[ ]   value ([Integer x. Integer y]) = [1,2];
[ ]   and other mixing variants.

Not completely sure, but seems not to hard to parse
Not introducing new keywords, but an alternative usage for existing one.

Cons:

Bit too ascii-art when destructuring tuples.
Many more to come.

Thoughts?

Thoughts?

@someth2say my thoughts are:

For consistency with assert, if, for, etc, the syntax would be value ([x, y] = [1, 2]);, i.e. the parens would go around the whole thing.
It's trivial to parse, indeed, it's somewhat easier to parse.
I have no objection to it.

@gavinking

For consistency with assert, if, for, etc, the syntax would be value ([x, y] = [1, 2]);, i.e. the parens would go around the whole thing.

Looks a bit strange having the = inside the parens. But for the shake of consistency I can live with it.
👍

Looks a bit strange having the = inside the parens.

Why?
if (exists name = process.arguments[0]) { ... }

Because it is
if (exists name = process.arguments[0]) { ... }

and not
if exists (name = process.arguments[0]) { ... }

Maybe I should have said: Looks a bit strange having the = inside the parents but having the keyword ouside them.

Jordi now it's you who is mixing up the role of the two value keywords. In this case the value keyword is like the if, not like the exists.
Sent from my iPhone

On May 10, 2017, at 12:06 PM, Jordi Sola<EMAIL_ADDRESS>wrote:
Because it is
if (exists name = process.arguments[0]) { ... }
and not
if exists (name = process.arguments[0]) { ... }
Maybe I should have said: Looks a bit strange having the = inside the parents but having the keyword ouside them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@someth2say i.e. we have:
if    (exists var                = expression)
value (value  var1 -> value var2 = expression)

I'm a little uneasy with partial assignment a'la [x, value y] = [1, 2]; of @jvasileff because

then I have to mentally scan destructuring statements to see if there's a stealthy declaration inside .. and the same goes for [x, Integer y] = [1, 2];
I will unavoidably start thinking about how I could "optimize" statements by only partially declaring new values, and further spend time undoing that when I refactor my code later.. distracting me from the actual task at hand.
I'm not really convinced it would be great to update some existing variable while adding new ones in the same go. But some good example could help me out here :)
often variable reuse is not really necessary; creating new variables would better communicate the usage in those cases

Thanks @gavingking for the long writeup on the issue! It was good, and also I gotta say I think the value (...) syntax proposed by @someth2say feels good.
Correct me if I'm wrong, but you would still use just [x,y] = [1,2] for pure assignment to existing variables?

I really dislike where you guy are going with this. My proposal centers around unifying the destructuring syntax with the value declaration syntax. Separating it further really doesn’t make sense to me. Afterall, if you read my proposal, I say that String foo is as much of a pattern as [String foo].
The value keyword doesn’t really speak to me “type inferece” as much as it does “value declaration”. With destructuring, you simply extend this syntax to allow it to declare multiple values.
However, interestingly enough, if you prefer to see it as meaning “type inferece”, it still does mean that in destructuring (with my proposal): it means “infer the type of all the declared values”.
As for @FroMage’s concerns on Gitter (the lack of backwards compatibility), my proposal is completely backwards compatible with what people actually write[1], while what you guys are proposing is a completely different and new syntax that really doesn’t match what people can actually write today.
[1] It’s not technically backwards compatible, as people would not be able to write value [value foo] anymore, but it’s really not something anyone would want to write anyway.

Alright, fine, so there we have it: it doesn't look like it's possible to address your concerns while also satisfying our other requirements, and so, given what I think everyone else agrees is the extremely low priority of this "problem", I'm going to go ahead and close this issue.
Sometimes it's simply not possible to find a perfect solution, so we have to go with something that is merely "perfectly fine".
Sorry!!

Which requirements do you mean? You guys start discussing this completely tangential syntax to my OP’s suggestion, without even pointing out what is wrong with the syntax I suggested.

Why does my suggestion not fit your requirement?
Why are your requirements important?
How/why is the current syntax better than what I suggested?

Sorry for missing the related comments on gitter..

I really don’t understand why you don’t want to discuss this issue, @gavinking. It might not be high priority, but I think it’s important to have something as basic as destructuring declarations be regular.
Additionally, even if you insist it’s “low priority”, it’s not like discussing and trying to solve this problem will cause any sort of harm. Quite the opposite, it might make the language more consistent and overall better.
From the lively arguments the different people are giving, I get the impression that everyone here seems to be interested in continuing to discuss this issue, even if you see it as “low priority” yourself. Even if we disagree on how, it seems to me that everyone is invested in trying to come with a syntax that is better than today’s. I feel like that definitely mean the current syntax is not “perfectly fine”.
 I do so because I care about the language you designed, and I wholeheartedly believe that my proposals can help make it better.
I understand that I’m not the only one collaborating to Ceylon for free, and I know I’m definitely not even close to being the biggest collaborator, but I do what I can do, and what I can do is making suggestions.
I’m really sorry for bringing this up here, but I really feel like I had to say it somewhere — even if I think you won’t want to respond to it here (probably justifiedly).

@Zambonifofex While I agree, that this discussion has been, well, interesting as a thought excercise, it has come too late to the party in the sense that we already have a syntax for destructuring statements.
The reasones and rationalle for picking the syntax we currently have has been discussed in the appropriate issue and rehashed by @gavinking several times now. It may not have yielded the result that you desire, but it is what we have and there is existing code that uses this syntax. So in a sense, this is the situation we are currently in now and if any changes are to be made to the language syntax, those changes need to be mindful of the backwards compatibility.
Any further discussion in this matter is futile in the sense that unless there is a concrete technical implementation that we may try out and possibly comment on, theorising over "possible syntax that might have been" is going to get us nowhere, except drawing everyone's attention away from other issues.

@luolong

those changes need to be mindful of the backwards compatibility

My syntax is completely backward compatible. All I’m asking is that the following be valid:
value String foo = "";
[String foo] = [""];

As @gavinking himself puts it:

That's actually not an unreasonable suggestion. The "irregularity" that is being raised here is that:

a destructuring statement always requires value before the pattern, even if types are explicit, but
a regular specification statement does not allow value in combination with a type.

I really don’t know what changed. Why did my idea go from “not an unreasonable suggestion” to “not satisfying his requirements”? And I still don’t know what these requirements are.
I also really don’t understand why @gavinking is fine with @someth2say’s backward incompatible idea but doesn’t like mine.

Any further discussion in this matter is futile in the sense that unless there is a concrete technical implementation that we may try out and possibly comment on […]

There isn’t a concrete implementation, but there is a complete proposal for the syntax. I really don’t understand why a concrete implementation is needed for people to comment on.
destructuring:

keyword? pattern "=" rhs

pattern:

type? identifier
"[" (pattern ",")+ "]"
pattern "->" pattern

[…] theorising over "possible syntax that might have been" […]

As I said, this is backward compatible. Unlike the other suggestions in this thread, my suggestion was built around the current syntax, hoping to only extend it to make it feel more regular.

@Zambonifofex what I was trying to say is that instead of endlessly theorizing over this idea, which sounds a LOT like "you guys need to fix this or else...", why not demonstrate how this fix will improve the language with a pull request.
It will not guarantee that it will be accepted, but it is much easier to argue your case if the implication is thatcher hard work is already done rather than "I have this idea and you guys need to implement it "


Update ZenFS

This PR updates @zenfs/core and @zenfs/dom to stable versions (i.e. ^1.0.0) and updates @zenfs/zip to the latest minor release (^0.5.0).

@atty303 Could you please take a look?


fix(client): pass parameters correctly within getProduct method

Changes
In the getProduct method is an attribute called params, wich is simply given to the request body as params.
This makes it that you cant give request config like associations, etc..
I believe this was by mistake, if so please accept the pull request.
If not, why? and what does params do, because I couldn't find any documentation or usage that would make sense.

hi @samuellembke. thank you very much for the PR! Please update the tests to not lose code coverage 👍🏻

@mkucmus What exactly do you mean by update the tests to not lose code coverage?
This is my first time I do a pull request for you guys


Investigate new project structure for apps per each binder implementation

As a developer, I'd to like to explore options to restructure the current maven project, so I can come up with flexible model to embed core bits of the application along with each of the binder implementation.
Acceptance:

Base project structure includes core app bits along with the binder-starter (for each binder) as maven dependency in pom.xml
I can create source, processor, or sink artifacts under the same group name for different binders
The model is flexible to adopt to additional binder implementations in future

As well as additional binder implementations you can imagine each platform (CF, k8s, YARN. etc.) will require additional utility configuration, and also that users will want to impose corporate standards by adding additional features. Plus there is the question of maybe wanting to add a config client and/or discovery (one of several flavours). I think it's good to be opinionated and provide some simple starting points, but we need to be flexible and allow additional dependencies to be added to all or some deployments at runtime, and make that configurable at the level of the admin server.

As a first pass, I tried to use maven profiles to create a single executable jar for each binder using the spring-boot-maven-plugin. For example, using something like - mvn package -Pkafka :pl time-source I am seeing the correct executable jar built - time-source-1.0.0.BUILD-SNAPSHOT-kafka-exec.jar that contains the kafka binder and using the rabbit profile - time-source-1.0.0.BUILD-SNAPSHOT-rabbit-exec.jar that contains the rabbit binder.
One problem I encountered was that it was not allowing me to pass in multiple profiles -Pkafka,rabbit in one pass. It always picked just one name (the second one declared in the pom) and stick both binders in them. Still need to see if there is a way around this. But, we can run them individually and create the correct artifacts.
Another option is to create separate maven projects for each binder. time-source-core, time-source-kafka, time-source-rabbit so on and so forth. But, this is a brute-force approach and may not be scalable as we add more binders. One good thing with the profiles is that we can move them to the parent pom in spring-cloud-stream-modules and apply for all sources/sinks/processors. So, if we need to add a new binder, it is a change in only one pom as opposed to creating new maven projects.
Another option is to create binder-starters (poms) for different sources/sinks/processors that allow the users to customize them more. I think this is what @dsyer is alluding to above if I understand it correctly. This would give the users the freedom to extend the modules the way they want, but this approach will not allow us to create pre-built jars and make them available in a maven repo which would lock them to use a fixed version.
What do you think? @markpollack @markfisher @dsyer @sabbyanandan @mbogoevici

I really hope we don't resort to creating dedicated projects per binder...
Do you have a branch with the profile POC?

@ericbottard It is not polished much and I put the profiles in the parent pom. Here is it. https://github.com/sobychacko/spring-cloud-stream-modules/tree/gh-186
mvn clean package -Pkafka -pl time-source (or rabbit as profile).

I guess I disagree.  Additional binder implementations at runtime is a nightmare in my experience.  It also basically destroys the entire argument that we are 'just running a boot app'. Instead we are running a boot strapper app that can download the Internet, complete with incompatible libraries so who knows if you even end up with something that should run.  I'm surprised you don't find the term 'dymanic runtime' to be off putting.  We can provide some basic staring point with OOTB apps, but make it super simple, spring command line, initializr, dataflow shell calling initializr, even attempting to automate a local build and publish once someone has more opinions - how you may want to do service discovery in a processor - which technology stack for that, which Hadoop distro, what jdbc and wants to mix and match different libraries.  I think the min bar for opinions are the required env-var translation libs that are included but enabled via a profile (to replace the current connector lib approach) and putting cloud config on the CP for OOTB modules - the app will still run if it can't speak to config server.

+1 for each "module" being a starter and then separate projects per binder that have the starter + binder as dependencies and a main class (we also might want one that has both kafka and rabbit binders).

The work Soby is doing now is to work out the approach for how to best organize the OOTB apps for different binders.  The general idea is to have an artifact that had only the core logic of the OOTB apps.  That is used to bootstrap the final OOTB app that includes the rabbit binder, say time-rabbit.jar.  Same would apply for time-Kafka.jar.   These OOTB apps would be constructed in the same way as an end user would if they wanted to create their own time app with different binder.  I've tried my best to explain in the ppt/Google doc and the final stories but it seems to be a hard thing to convey clearly.  Posting links to the ppt/Google doc where everything is in some
Better context may help.

I don't think that the profile based approach will work. They are not intended to produce multiple artifacts, which is what we want (and yes, they override each other, as Soby noticed). One option would be to produce different classifiers for the different binder types. e.g. instead of 'exec' we would get 'exec-kafka', 'exec-rabbit'. This could be in principle generalized in a super-pom so easier to apply across the board, and could be configurable in the artifact resolver (the classifier). The original artifact (unclassified) would remain binder-less. Not sure how you can tune the different dependency sets per execution, but that's one thing to investigate if this, as a general approach is acceptable. I can't think of a better way to prevent project explosion.

Just to clarify, we can aim for several artifacts (hence build time resolved), one for each binder, without resorting to 1 + 3 maven projects. But if the starters have value for other purposes, then so be it

For profile, I meant only for the env-var translations stuff which would be only relying on JDK classes

The current issue for Soby is to come up with an approach and to discuss.

@markpollack I meant the approach based on Maven profiles which was in the posted commit.

The starter would definitely have value in the sense that would be the entry point for anyone interested in using a custom binder implementation. In fact, it's even broader than that since other aspects of our OOTB apps could be customized, e.g. security config for the HTTP source.

@here: As @markpollack said, this is a spike to come up with design alternatives, so we can get together and discuss and then come to consensus.
Let's wait until we have it in reviewable form, please.

Ah, sorry Marius...


local registry set in .npmrc file not respected

Problem
I'm trying to publish to a local verdaccio instance located at http://localhost:4873/.
I've updated my .npmrc file to have:
registry=http://localhost:4873/

But when I run pnpm changeset publish it tries to publish to npmjs.org.
Note, when I run pnpm publish it correctly uses http://localhost:4873/
I've set up a demo of the issue I'm seeing here:
https://github.com/gxxcastillo/changesets-npmrc

As a workaround, this works for me:
npm_config_registry=http://localhost:4873 pnpm changeset publish


Erased map by //et not disaper from list and is allowed to requeue and play again

we must store the current map until the end of the round, so removing it would be pretty bad

OK, If nothing else breaks.
Unfortunately, I didn't have time to do more research.


jax/stax BatchNorm: running average on the training set and l2 regularisation

Hi all,
Thanks for releasing this package to the research community! I have two specific questions about the BatchNorm layer in stax.
1/ The mean is supposed to be a running average on the training set in order to collect stats of feature maps during learning, so is the variance. It doesn't seem to be like this in the jax's implementation, right?
2/ When applying the l2 regularisation on a neural network with BatchNorm layers using the built-in "l2_norm" function, it also aggregates the learnable params, beta and gamma, which doesn't seem to be appropriate to me. Am I right?
Thanks again!

Thanks for the issue report!
There's an existing bug open for the batch norm moving averages:
https://github.com/google/jax/issues/139
In general stax is in jax.experimental and experimental means just that: it's an experiment in how to write neural network layers on top of Jax. It isn't intended to be the last word on the topic. We expect that we will replace it with a Stax 2 before long incorporating some of the things we have learnt from the current Stax, and this is definitely on the list of things to fix.
Note however that stax is only a tiny amount of code:
https://github.com/google/jax/blob/master/jax/experimental/stax.py
If it doesn't do what you want, you should feel free to copy, remix, and adapt it to your needs. We want to get away from the having monolithic frameworks that researchers can't change. As an example, the Trax project in tensor2tensor has built their own variant of layers that work on top of Jax: https://github.com/tensorflow/tensor2tensor/tree/master/tensor2tensor/trax/layers
I'm not saying it is the final word in layers libraries either, but you should not feel limited to stax as it stands today.
Hope that helps!


fix(apps/prod/jenkins): add node affinity on clean cache cronjob

Add node affinity on clean cache cronjob to void scheduling to arm64 nodes that may cause task failures.

it's fixed.


Transpile into Babel/tcomb syntax

I know this is a stretch, but what if you could set a flag to transpile TS code into code that would be readable by babel-plugin-tcomb, which came out recently? This would enable runtime type checking, which I previously brought up in #1573, but it would require interfaces be transpiled into structs:
interface Point {
    x: number;
    y: number;
}

function foo(point: Point) {
    return point.x * point.y;
}

becomes...
import t from 'tcomb';

const Point = t.struct({
    x: t.Number,
    y: t.Number
});

function foo(point: Point) {
    return point.x * point.y;
}

If not provided directly by the compiler, the same could be achieved by a 3rd party module, if only a concrete syntax tree #625 were provided.
Related issues:

https://github.com/Microsoft/TypeScript/issues/2944
https://github.com/Microsoft/TypeScript/issues/1573
https://github.com/Microsoft/TypeScript/issues/625

For the record, I already have node modules that transpile from TS into ES6 and then Babel transpiles it from there and it works great! If only this last missing piece of the puzzle were implemented, we would have an awesome solution for both compile time and runtime type checking.

I think this is an interesting and useful proposition. I would say the best way this can be implemented is as an emitter extension; we first need to allow for an extension point in the emitter to allow for additional transformations. @rbuckton has a change to make this doable today: https://github.com/Microsoft/TypeScript/pull/4010 and some helper factory functions in https://github.com/Microsoft/TypeScript/pull/3762.

Related is #1573.

The TypeScript compiler should expose a transformation API that enable these scenarios. i do not think this belongs in the core though. We are working on enabling a plug-able emitter transformation system, so this, along with an extension should address the OP.


✨ Use ruff for py linting

What's the problem this feature will solve?
Include https://github.com/charliermarsh/ruff for python linting as in mqt/qcec
Describe the solution you'd like
see https://github.com/cda-tum/qcec/pull/255 for a setup

see https://github.com/cda-tum/qcec/pull/230


Improve type-name-incorrect-variance message

Summary
Change the type-name-incorrect-variance diagnostic message to include the detected variance and a name change recommendation. For example,
`TypeVar` name "T_co" does not reflect its contravariance; consider renaming it to "T_contra"

Related to #5651.
Test Plan
cargo test

I think something went wrong with GitHub Actions.

What happens in the event that a variable is marked as both covariant and contravariant?

What happens in the event that a variable is marked as both covariant and contravariant?

Currently, it ignores anything that is both covariant and contravariant. However, looking at the Pylint implementation, it emits
Type variable name does not reflect variance

It should be simple to emit a similar generic message. Do you think it's better to ignore invalid bivariant types or to emit a generic message instead?

Hmm, I think ignoring them is fine actually, since this diagnostic can't actually be satisfied by renaming the variable.


securityContext for the container weblogic-server

Hello,
In order to remain coherent between initContainer and container, could it be possible to offer the capability to define securityContext for the container weblogic-server ?
Thanks.

The securityContext for the weblogic-server container is controlled by the domain.spec.serverPod.containerSecurityContext field.

Hello @rjeberhard
We are using the following podSecurityContext definition:
  serverPod:

    podSecurityContext:
      fsGroup: 1
      seccompProfile:
        type: RuntimeDefault

      # Is the ID of the group so "bin"
      supplementalGroups:
        - 1

      runAsNonRoot: true
      runAsUser: 1000

Here is an example of container we are using:
    containers:
    - name: xxx
      securityContext:
        privileged: false
        allowPrivilegeEscalation: false
        capabilities:
          drop:
          - ALL

The elements privileged, allowPrivilegeEscalation and capabilities are specific to container and not to pod.
We dont' have access to the definition of weblogic-server container so what I'm asking if it could be possible to have the capability to define the securityContext element for the container  weblogic-server in order to increase a bit the security.

Sorry for the confusion ; I read too fast


Incorrect check in rehashUserPassword

Laravel Version: 8.37.0
PHP Version: 7.4.16
Database Driver & Version: mongo 4.4.4

Description:
As in the description using logoutOtherDevices() will invalidate all other user's session only, https://laravel.com/docs/8.x/authentication
In the change password scenario, when we call logoutOtherDevices(),
$password is supposed to hold the new password.
This method calls rehashUserPassword() where the new password is checked against the current password's hash, which will never match.
if (! Hash::check($password, $this->user()->{$attribute})) {
    throw new InvalidArgumentException('The given password does not match the current password.');
}

Then in next line, the new password's hash is created and saved.
Also not able to see a point why this would be InvalidArgumentException? Shouldn't this be AuthenticationException ?
Steps To Reproduce:
A code snippet to show the example
if ($validation->passes()) {

    User::updatePassword($uid, Request::get('password'));

     Auth::logoutOtherDevices(Request::get('password'));

    $this->reset(['current_password', 'password', 'password_confirmation']);

    return $this->dispatchBrowserEvent('success', [
        'title' => 'Password updated successfully!',
        'icon'  => 'success',
    ]);
}

Don't see how this is a bug. Sounds to me like you just implemented it incorrectly. Firstly, it's odd that you want to update the password and logout other devices in the same request.
Even if you do want to do that, you need to update the cached user instance held by the auth guard.
By doing User::updatePassword you forget to reset the cached version of the user, and so logoutOtherDevices still holds the old password. This is an issue with your implementation, and not a bug in the framework.
To fix this, you should do something like:
$request->user()->forceFill(['password' => Hash::make($request->input('password'))])->save();

Auth::logoutOtherDevices(....);

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


[Slider] Feature Custom Icon

I have added a new prop called thumb to the Slider component, which you can use like this.
import React from 'react';
import PropTypes from 'prop-types';
import { withStyles } from '@material-ui/core/styles';
import Typography from '@material-ui/core/Typography';
import Slider from '@material-ui/lab/Slider';
import DeleteIcon from '@material-ui/icons/Delete';

const styles = {
  root: {
    width: 300,
  },
};

class SimpleSlider extends React.Component {
  state = {
    value: 50,
  };

  handleChange = (event, value) => {
    this.setState({ value });
  };

  render() {
    const { classes } = this.props;
    const { value } = this.state;

    return (

        <Typography id="label">Slider Image</Typography>
        <Slider
          value={value}
          aria-labelledby="label"
          onChange={this.handleChange}
          thumb={}
        />
        <Typography id="label">Slider Simple</Typography>
        <Slider value={value} aria-labelledby="label" onChange={this.handleChange} />
        <Typography id="label">Slider Icon</Typography>
        <Slider
          value={value}
          aria-labelledby="label"
          onChange={this.handleChange}
          thumb={<DeleteIcon style={{ color: 'green' }} />}
        />

    );
  }
}

SimpleSlider.propTypes = {
  classes: PropTypes.object.isRequired,
};

export default withStyles(styles)(SimpleSlider);

This looks something like this

This is a clean version of https://github.com/mui-org/material-ui/pull/12485 which got messed up, I kept on trying for some hours. but I guess I messed that pr more. Lesson learnt at my end.

@oliviertassinari I deleted the old PR, and created a new PR from scratch updated from upstream master, and I didn't run yarn docs:api but the build is still failing for CircleCI.
@eps1lon can you point me in the write direction?

I didn't run yarn docs:api

You need to in order to update the slider API docs

No worries. BTW, no need to close one PR and open another - you can force push your fixed branch.
Please could you make the customization examples a little more practical? The first looks like a glitch, and the third doesn't make much sense. Why would a slider have a trash-can icon for it's thumb?  😄
No need for the second example - we already know what it looks like when not customized.
It also needs a heading "Custom thumb"? Not sure it warrants a description.

I have added a better demo

Along with the description, as instructed.
Regarding the part

BTW, no need to close one PR and open another - you can force push your fixed branch.

I tried doing it, tried for like 2 hours but I think I ended up messing the PR more, so created a new one. I'll spend some time tomorrow learning how to git reset, git revert and git reflog 💯

Interactions are currently not very smooth. The Icon bounces up and down on activation:

This also happens with the mui icon.
Chrome Version 68.0.3440.106 (Official Build) (64-bit)

@eps1lon I have made changes to the thumb icon, is this the right approach? your suggestions.

Regarding the CircleCI pipeline for ci/circleci: test_browser am I doing something wrong, I saw it's log but it didn't make much sense to me.

And now circleCI is failing again, because the docs needs to be updated using yarn docs:api.

I have updated the demo with a better image of a circle.

Should I change this to thumbIcon too, along with inside the code as well.

Makes sense to me. @eps1lon?

@eps1lon is this PR now okay?

I merged with master, now almost all CircleCI tests are failing with this error There appears to be trouble with your network connection. Retrying...

@eps1lon I think the tests passed successfully this time.

@mbrookes since I updated the comment on style, the yarn docs:api  command needs to be run again. I have an issue on windows. Can you please run the commands for this PR.

@oliviertassinari this PR has no conflicts any more, can this be merged now?

@eps1lon Could you have a last look please?

@adeelibr We got there in the end 😄 Thanks for working on it.


indent_style doesn't work with editor.insertSpaces: "auto"

I want VS Code to default to doing whatever the file already does unless an .editorconfig is present.  However, if you have "editor.insertSpaces": "auto" in your VSCode settings.json and indent_style = tab in your .editorconfig, new files that match the .editorconfig file matcher end up using spaces (the VS Code fallback for new files) rather than the .editorconfig settings.

CC @chrisdias @alexandrudima

This is a somewhat a duplicate of #19 I guess. Or #19 is a duplicate of this one. Because of slow response times by the authors which are probably too busy to update the core VS Code, we forked this repository to https://github.com/editorconfig/editorconfig-vscode and released under a new plugin. When https://github.com/editorconfig/editorconfig-vscode/pull/5 lands in that repo, this is fixed.

Which will probably be sometime in the next 24 hours.

closing


tests: Increase unit-test coverage on create.go

Add a new test TestCreateCgroupsFilesFailToWriteFile() to test another
failure path.
Fixes #485.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Coverage remained the same at 81.68% when pulling 776ad379d9b0d03fc5429c4b06b31ff0f5c78447 on jodh-intel:increase-create-coverage into 8a21d77e75884d3094244618db812fd01cadad07 on clearcontainers:master.

lgtm


preserve array type in date_bin and date_trunc functions

Which issue does this PR close?

Closes #5976. N.B. this issue is already closed, but I don't think the issue was completely fixed.
Rationale for this change

Elliding timezone information in these functions makes the data harder to process downstream. It would have been sufficient for the purposes of not losing information to normalize all timezones to "+00" (UTC), however if the trouble has been taken to convert a time to a particular timezone it is friendlier to preserve that.
What changes are included in this PR?

The result type of date_bin and date_trunc never includes any timezone information. Change this such that the timezone of the resulting array from these functions is copied from the input array.
Are these changes tested?

Yes
Are there any user-facing changes?

I don't think this would be considered user facing.

I am sorry @mhilton  -- I ran out of time today to review this PR. I plan to do so tomorrow

(thank you for the review, BTW @Weijun-H 🙏 )


Can't upload torrent more than 2MB

I just opened a PR with a fix
For now you can hotfix your existing image with something like this (using SSH):
$ printf "upload_max_filesize = 200M\npost_max_size = 200M\n" > /etc/php5/fpm/conf.d/50-scaleway.init
$ service php5-fpm restart


after train custom model i am getting this error when i am processing video and as well as image also

Hi,
I have trained the yolov3 on a custom data set of 10000+ images with 1 class for 2 epochs.
When I try to load this trained model back for video detection  and image detection using your code, I get the error in the title of this post.
Any suggestions?
below error
"ValueError: Dimension 0 in both shapes must be equal, but are 1 and 18 for 'Assign_360' (op: 'Assign') with input shapes: [1,1,1024,255], [18,1024,1,1]."

Can you share your complete stack trace?
Thanks

okay tell me one thing that has been solved actually i have to train multiple category then what i have to do.
now i train only one category that is fine running well and detecting also.
but when i am going to train multiple categories then it is giving me error as like
====================================================================
Using TensorFlow backend.
Generating anchor boxes for training images and annotation...
9
Average IOU for 9 anchors: 0.67
Anchor Boxes generated.
Detection configuration saved in  ./Dataset/json/detection_config.json
{'Humanhair': 1013}
Some labels have no annotations! Please revise the list of labels in your configuration.
['Humanarm', 'Humanface', 'Humanhair', 'Humanhead']
Training on:    None
Training with Batch Size:  2
Number of Experiments:  4
Traceback (most recent call last):
File "train.py", line 7, in
trainer.trainModel()
File "/usr/local/lib/python3.6/site-packages/imageai/Detection/Custom/init.py", line 231, in trainModel
norm=normalize
File "/usr/local/lib/python3.6/site-packages/imageai/Detection/Custom/generator.py", line 36, in init
if shuffle: np.random.shuffle(self.instances)
File "mtrand.pyx", line 4830, in mtrand.RandomState.shuffle
TypeError: object of type 'NoneType' has no len()

this is my code..,
from imageai.Detection.Custom import DetectionModelTrainer
import os
trainer = DetectionModelTrainer()
trainer.setModelTypeAsYOLOv3()
trainer.setDataDirectory(data_directory="./Dataset")
trainer.setTrainConfig(object_names_array=['Humanhair','Humanface','Humanarm','Humanhead'], batch_size=2, num_experiments=4, train_from_pretrained_model="./pretrained-yolov3.h5")
trainer.trainModel()

if shuffle: np.random.shuffle(self.instances)
File "mtrand.pyx", line 4830, in mtrand.RandomState.shuffle
TypeError: object of type 'NoneType' has no len()

This error is because self.instances is None. This is probably because data is not being loaded properly. Check if your directories are ok and your files are actually where they should be. Consider also removing cache folder which may be saving train/validate empty samples from previous runs


Doesn't work in new regions that require AWS4-HMAC-SHA256

I have my bucket in Frankfurt (EUCentral1) and I receive this error:

FAILURE: Error Domain=com.AmazonS3RequestManager.error Code=-9999 "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256." UserInfo={NSLocalizedFailureReason=The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.}

Is there anything I can do to fix this? Moving the bucket is not an option.
Thanks!

@tbleckert We have to implement V4 signatures. For this to work the Authentication header must be adjusted. If you want to give it a shot AmazonS3SignatureHelpers.m would be the starting point. I think it's not too hard to do. Have a look at the implementation of the official iOS SDK: https://github.com/aws/aws-sdk-ios/blob/master/AWSCore/Authentication/AWSSignature.m

Thanks for making me aware of this. I'll try looking into this sometime soon, but I'm probably not going to have time this week. If anyone wants to take a crack at it, I'd be happy to take a PR.

I've started work on this, but it's quite a big project. This could take a while.
You can check out the AWS_signature_V4 branch if you want to contribute.
AWS documentation for the signature calculations are here:
http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html

@AnthonyMDev Cool, thx. I'll have a look at it.

@tbleckert Just an update for you. I have been working on this. I'm almost done getting the V4 Signature set up. I'll integrate it as soon as I have some more free time and we will be good to go!

@AnthonyMDev Cool stuff! Thx mate.

@AnthonyMDev Great work! Thanks!

@tbleckert Okay, I've got a working beta of the V4 signature up and running. Can you try using the /feature/AWS_signature_v4 branch and see if that works for you please?
I'm fairly certain that this should work for GET requests just fine now. There is some wording in the AWS documentation that makes me think that we may have to sign the requests a completely different way for POST requests.
Can you please confirm that BOTH GET and POST requests work for you? If so, I'll release a new version with this included. Otherwise, I'll need some time to get the POST encoding done.

Really stoked about this. I've been getting those 9999 codes as well.

@WadeSellers Glad to hear that other people want this as well. I haven't had time to do ample testing of this to feel comfortable pushing it to master yet. As I said above, I'm not sure if POST requests are going to work yet specifically. If you are looking for this to be pushed to a new version and have some time, I'd really appreciate getting some outside sources to test and confirm that everything is working.
Thanks

looks like the v4 signing dosent work for me when i try to upload an object..
any way to find out why?

The POST requests may take a separate signature type. I'm not sure when I'll have time to look into this, but it's on my list. If someone else wants to make a PR before me, feel free.


feature request: greedy_alt (fictional name)

Hello, great work for nom!
I'm been repeatedly met with a problem, though. The alt combinator return the first succeeded result. so i have to carefully arrange the sub-parsers in a "reverse-dictionary order" to make the result correct what i wanted.
I wonder if we can make a special version of alt so it run all the sub-parsers and return the first version that ate the most data. That'll be slower, but it can be much more convenient.
Thanks!

that could be interesting :)


#482: Format log message with old printf style

Description
Formatted log messages with old printf style
Fixes #482
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation changes only

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

I set this PR to draft status because it has failing tests.


ExShuffle-chrisda to Master

Docs Build status updates of commit 68024f7:
:clock10: Full build: the average full build time is 17 min(s) 37 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 68024f7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c0245a8:
:clock10: Full build: the average full build time is 17 min(s) 37 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit c0245a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f2012c8:
:clock10: Full build: the average full build time is 17 min(s) 37 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit f2012c8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/connect-to-scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/docs-conceptual/scc-powershell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Added Android Development (Subject Quiz)

Added New Subject of Android Development and quiz related to this domain.
Screenshots Attached:

Nice work @Interstellar07, Keep it up 👍


Define target group(s) and find a categorizaion system to match resources

With an open science training there are possibly different target groups that have different interests in open science and thus require different scopes and/or motivation (undergraduate students, PhD's, senior researchers all have their own view). It might be worth thinking about defining the "relevant" target groups and make material available that caters the different needs (maybe also in recombination of various material).
This issue is closely related to #4.
Furthermore it might be helpful to work on a categorization system to mark which material is reasonable for which target group. This could be done by tags, icons or badges - similar to the idea behind Open Badges, or the badge system that the Association for Psychological Science has implemented with the Open Practices.

I think we all agree that our main target will be university-associated folks. However, I think the motivation/troubles of different "career stages" at the university are very overlapping. Nevertheless, a badge system is useful.
But, I see bigger differences for different scientific fields. E.g. life scientists will have a big focus on open data (with big data issues), whereas social scientists might be more interested in publishing open and collaborative books etc.

Absolutely right @aleimba! I think with a clever badge system we could look into using both elements of the badge (the icon and the colour) to indicate different things e.g. the discipline and the "level" or target group or "type of content".

Closing this issue since it is divided into 2 individual ones - #36 and #37.


NTR: a child term to "ATP transport"

I would like to suggest a child term "ATP efflux" to "GO:0015867 ATP transport" term.
ATP efflux
Definition: The directed movement of ATP, adenosine triphosphate, out of cell or organelle.
Parent term: is_a GO:0015867 ATP transport
PMID:24286344
thanks,
Jinhui Zhang

Added using TermGenie:
[Term]
id: GO:1904669
name: ATP export
namespace: biological_process
def: "The directed movement of ATP out of a cell or organelle." [GO_REF:0000074, GOC:TermGenie, PMID:24286344]
synonym: "ATP efflux" RELATED []
is_a: GO:0015867 {is_inferred="true"} ! ATP transport
intersection_of: GO:0006810 ! transport
intersection_of: exports CHEBI:15422 ! ATP
relationship: exports CHEBI:15422 {is_inferred="true"} ! ATP
created_by: tb
creation_date: 2015-09-09T16:33:06Z


Add DocC availability information to all directive pages

Bug/issue #, if applicable: rdar://110036742
Summary
This add an introducedVersion property to DirectiveConvertible so that each directive page shows what version of DocC is the earliest version to support that directive.
Dependencies
None
Testing
Run swift run docc preview Sources/docc/DocCDocumentation.docc and inspect the various directive documentation pages
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

Note that since this is a new protocol requirement it is a source breaking change for anyone who has defined their own directives. I could add a default value to mitigate this but my concern is that if new directives don't need to specify when they were introduced, we will forget to add it and the documentation will show the wrong version.

@swift-ci please test

@swift-ci please test


Update StringExtensions.cs

promtTokens adjusted by adding 11 tokens to match the token count of the non-stream mode.

comletionTokens uses the token count of the concatenated content to match the token count of the non-stream mode.

Thanks for your PR!

Do you know the adding 11 tokens works with long conversation too?
Could you create additional PR for the bicep request so that it's easier to track what has been changed?

Do you know the adding 11 tokens works with long conversation too?
As far as my understanding, it works with long conversation too.

Could you create additional PR for the bicep request so that it's easier to track what has been changed?
Got it.


Rate limit clarification

According to https://getpocket.com/developer/docs/rate-limits

"Each user is limited to 320 calls per hour"
Each application is limited to 10,000 calls per hour

It's not clear how does this translate when using this plugin.
Gatsby builds a site at once, meaning a burst of calls to the Pocket API.
Does each record in Pocket need one call to retrieve? If so, can we get max 320 or 10k records only?
Or is the plugin getting them in batches, so it requires less calls?
What's the maximum size of Pocket API collection of links that can be retrieved using this module / Gatsby?

The plugin will go and get all records matching the options in gatsby-config.js, in one call. I have a nightly scheduled build to get the current week's articles (1 call). My weekly scheduled build makes 52 calls, to get a years worth of data batched by week.


Bug Report: New Issue with Ghost Tapping's Fix

I see you fixed the "No Ghost Tapping" setting not working bug linked here. Thanks for doing so, as it has troubled me for some time!
However, after implementing your change, continuing to hold the end of long hold notes decreases your health, where it should increase your health. (The first second of holding functions fine, interestingly.) Missing the other part of the hold also decreases your health, making it impossible to not lose health on holds.

The above bug refers to my own implementation of the fix so I'm not sure it's valid. However, I just downloaded and built the master copy of your source code. The bug above doesn't exist, and missed notes play miss animations. But there's a new bug: you take no damage to your life bar when missing notes. Though your accuracy does go down as expected.

Thank you, these bugs are fixed in Kade 1.6!
The no ghost tapping fix is immensely helpful, as it makes the game feel more fair.


Maps Part 2 + Refactoring for code consistency

Refactoring maps-page-loader and maps.html so that it is consistent with the other js scripts. It calls buildUI() from the html page and it uses fetch() instead of jQuery's getJSON.
Functionalities not changed.

Added an online dataset of locations of UFO sightings

Created new UFODataServlets to return csv values into json array.

Adding markers onto map after getting the json values from UFODataServlet

Removed deadcode and changed from UFO data to cinema data.

Hi Reine, I wonder if you have pushed up the backend code for cinema-data. When I checked out this branch, the backend code to send cinema-data json to frontend doesn't seem to be present

Oh noes, I think you're right, so sorry for missing it out, I've just added the cinemaLocationsServlet and the cinemaLocations.csv in. I originally wanted to do some marker cluster thing so I didn't upload them as I wanted to uploade them in one go but I should have >.<


Dependencies are duplicated in bst show --format %{deps}

See original issue on GitLab
In GitLab by [Gitlab user @cs-shadow] on May 13, 2020, 16:10
Summary
The %{deps} format option claims to give a list of all dependencies. However, if a dependency is both a build and runtime dependency, it is currently printed twice.
Steps to reproduce
$ bst -C doc/examples/autotools show --format "%{name} %{deps}"
base/alpine.bst []
base.bst [base/alpine.bst, base/alpine.bst]
hello.bst [base.bst, base.bst]

Note that base.bst and base/alpine.bst are repeated twice in the respective output lines.
What is the current bug behavior?
Elements that are both build and runtime dependencies are listed twice.
What is the expected correct behavior?
They are deduplicated.

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 19:50
mentioned in commit 1e6c03f0fe546a743ed11e8973b43343d52c42dc

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 19:50
mentioned in commit 1e6c03f0fe546a743ed11e8973b43343d52c42dc

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 19:51
mentioned in merge request !1931

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 19:51
mentioned in merge request !1931

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 20:00
mentioned in commit 98391076d14d5d8fc9f5766bd782c899a03bcc22

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 20:00
mentioned in commit 98391076d14d5d8fc9f5766bd782c899a03bcc22

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 20:38
mentioned in commit bcd2536c2405ffa5dcd52ed9823a7c437cc1b2de

In GitLab by [Gitlab user @cs-shadow] on May 14, 2020, 20:38
mentioned in commit bcd2536c2405ffa5dcd52ed9823a7c437cc1b2de

In GitLab by [Gitlab user @cs-shadow] on May 18, 2020, 10:45
mentioned in commit b8b40314740c118398641a3b86655a8b0434631d

In GitLab by [Gitlab user @cs-shadow] on May 18, 2020, 10:45
mentioned in commit b8b40314740c118398641a3b86655a8b0434631d

In GitLab by [Gitlab user @marge-bot123] on May 18, 2020, 11:23
closed via merge request !1931

In GitLab by [Gitlab user @marge-bot123] on May 18, 2020, 11:23
closed via merge request !1931

In GitLab by [Gitlab user @marge-bot123] on May 18, 2020, 11:23
mentioned in commit 0c9ca749b32c2ed8b41e6f94e7c6f5431eae4d70

In GitLab by [Gitlab user @marge-bot123] on May 18, 2020, 11:23
mentioned in commit 0c9ca749b32c2ed8b41e6f94e7c6f5431eae4d70


Consistent definition of "PE" throughout the manual

Original issue: https://charm.cs.illinois.edu/redmine/issues/1912

The term PE should be consistently defined as a thread/process with a scheduler that chares can live on.
The last paragraph in section 1.4 in particular is misleading in that it implies that comm threads count as PEs.

Original date: 2018-05-16 00:06:10

~~https://charm.cs.illinois.edu/gerrit/4188~~ https://github.com/UIUC-PPL/charm/commit/d80304640a63db2d6cb5d7a147fa48eb3724adc6


rework themeregistry to be configured by a builder

Here is what I did:

make ThemeRegistry non-static
hide ThemeRegistry behind an interface
add builder to configure the ThemeRegistry
added first unittests
fixed some errors from unittests
fixed some codesmells
updated readme

Note: For the tests to run, I had to include the fix from #3
TODO:

Test it against our private project

We should, at some point, reconsider the necessity of ThemeRegistry.Current since it's not set automatically at the moment and could be easily confused with a property that always holds the current applications' theme - especially since, with this issue, it doesn't get set automatically anymore at all.
Since this, in my opinion,  is its own topic, I'd propose to discuss this in another issue.


Build failure: haskellPackages.patch-image

Steps To Reproduce
haskellPackages.patch-image cannot be built with GHC-9.4 anymore because of a GHC-9.4 bug that lets build of llvm-tf fail. The problem is fixed at Hackage, but it requires a major version bump of llvm-tf, llvm-extra, llvm-dsl, knead, synthesizer-llvm. What can I do to upgrade these?
https://hydra.nixos.org/build/230970343/nixlog/1
Notify maintainers
@sternenseemann @maralorn
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.0-25-amd64, Debian GNU/Linux, 11 (bullseye), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

If none of them are on stackage, then you just need to wait a little bit until we bump the hackage pin again. We are currently having some problems with our CI, but it should only take a few days. I am also eager for the next bump because it fixes some packages I use.

Those packages depend on LLVM-13 and this is not supported in Stackage.


add license title

It's not strictly required, but it's useful metadata, and part of the recommended license template text (see http://choosealicense.com/licenses/isc/ and https://opensource.org/licenses/isc-license)

Thanks for contribution! 👍

Whoa that was fast! :)


Revert "Fixed development environment setup commands"

Reverts plone/volto#3142

@sneridagh Not a problem, we want the best thing to remain, so can I at least erase the $ symbol before the commands because it's an outdated format and the $ symbol also gets copied when we try copy directly


Using DeepExplainer with torchtext

Hello,
I am using a simple pytorch RNN to train a sentiment detection model and am using torchtext to handle the data iteration (specifically data.BucketIterator).
When I try to use the DeepExplainer on the trained model, I get the error: RuntimeError: only Tensors of floating point dtype can require gradients.
The default type for tensors in the BucketIterator is torch.LongTensor, so I have experimented with changing this type to FloatTensor, but this stops the model from training.
I have also tried to change the type of tensors for the background and test cases being fed into the DeepExplainer to FloatTensor, but upon instantiating the DeepExplainer I get the error: RuntimeError: Expected tensor for argument #1 'indices' to have scalar type Long; but got CPUType instead (while checking arguments for embedding)
I'm at a bit of a loss and would appreciate any insight into what is causing the errors, and if there are known compatibility issues with torchtext.
Thanks!

Hi!
The error you get is from the embedding layer. Neither embedding layers or RNNs are supported by the PyTorch Deep Explainer right now.
Unfortunately, because of the error you get, it's difficult to backpropagate through an embedding layer, so the model also won't work with the Gradient Explainer.

Thanks for the response and suggestion!
To experiment with this, I have taken the code from this page https://slundberg.github.io/shap/notebooks/deep_explainer/Keras LSTM for IMDB Sentiment Classification.html and adpated it to run on tensorflow to check compatibility with tf as opposed to keras. All I have done to the code is insert tensorflow. before all the keras imported modules
The model trains fine, but again when running explainer.shap_values I get an error, this time:
TypeError: Fetch argument None has invalid type <class 'NoneType'>
Do you have any idea why this is? Should I abandon the tf keras wrapper and go straight for 'pure' tensorflow?
Thanks

Hi, I'm using pure tf with an architecture that has a stack of 2 bidirectional lstms and I am runing into the same error: Fetch argument None has invalid type <class 'NoneType'>

@gabrieltseng, thank you for your response! Any ideas how I can begin perhaps solving it on my end - as in, if you were to fix it what steps would you take? I'm happy to take a stab at it perhaps.
or is there some fundamental issues in the pytorch deepExplainer code which does not allow for rnn/embeddings to work with it and needs solid work in redoing it?
Thank you much :)

Hi @srn284,
I think it would be very tricky to implement this for the embedding layer - PyTorch doesn't allow gradients to be calculated for Long Tensors, which is the tensor type which must be input into an embedding layer (see this issue).
It should be possible to implement the DeepExplainer for RNNs though - they would probably require a new function to be implemented, similar to what happened for the maxpool module (note that these functions are backward hooks).
Definitely happy to help in any way I can if you do decide to work on this!

@gabrieltseng  Thanks much!
I indeed had the embedding problem of the two problems; I was going to attempt it using embedding matrix instead and matrix multiplication with one hot vectors. Right now i believe, pytorch uses a lookup table for embeddings i believe.
Please let me know your thoughts and thank you for your time.

Has there been any progress on this? We're running into this trying to interpret a transformer based model built in pytorch (we're using it for something akin to sentiment, but with regression) and have hit a wall. We cannot get DeepExplainer or GradientExplainer to work.

A solution to backpropagate through embedding layer hasn't been added yet. For now, your best bet is probably to replace the embedding layer with a matrix multiplication using one hot vectors.

Hey everyone, we did some stuff for interpretability on transformer based models as well! And, indeed the embedding layers in transformers/rnn was why i followed this issues page this in the first place. I replaced embedding layers with embedding matrices and got some results. Not sure if I liked what I got so I dropped my work.
However, I moved to another method for interpretability using this paper (https://www.microsoft.com/en-us/research/uploads/prod/2019/05/camera_paper_with_supp_3.pdf) - they have source code as well. The authors use perturbation and mutual information based training protocol to get the contribution of every "token". I changed the paper's original modelling since the work is quite flexible and can be expanded/altered and it still worked, so it should definitely work for the regression task as well if you play with the source code.
source code: https://github.com/icml2019paper2428/Towards-A-Deep-and-Unified-Understanding-of-Deep-Neural-Models-in-NLP

@gabrieltseng I'm not sure how feasible replacing the layers is for us. We're using a base of a pretrained BERT model, which is then finetuned with a specialized head on top for a regression task. We'd have to somehow figure out how to both replace the layer architecture and mimic the trained weights we have.

Hi all, is this solved? I am having troubles with the DeepExplainer with PyTorch BERT.


Fix is_hermitian and add atol

Summary

Fixes bug where FermionicOp.is_hermitian gives false negatives due to not normal-ordering
Adds atol parameter to is_hermitian

Details and comments

@mrossinek I found that sphinx handles inherited docstrings correctly, so I deleted the redundant docstrings for both is_hermitian and simplify.

@mrossinek Done.


AuthStateMissing at /complete/google-oauth2/

Went to login and this happened after entering valid credentials.

This is probably not the technical answer you were expecting but this randomly started happening the other day and I have legitimately no idea why. So I've been fiddling with it - I think it's a bug with cookies not being set. We'll see what happens. It's a good thing I don't have a deadline on this haha.

In hindsight, that probably should have been more obvious. In a recent change I upgraded the site to use SSL/TLS and made a settings change (to SESSION_COOKIE_SECURE, which hasn't been committed due to testing) which prevents cookies from being sent over non-HTTPS sessions. I've removed that so it's fixed now and will either be allowing insecure cookies or forcing all connections to be over HTTPS.
Thanks for the report!

No problem! Just started getting in to web security so it was good practice.
On Wed, Jun 3, 2015 at 7:53 PM -0700, "Gravity"<EMAIL_ADDRESS>wrote:
In hindsight, that probably should have been more obvious. In a recent change I upgraded the site to use SSL/TLS and made a settings change (to SESSION_COOKIE_SECURE, which hasn't been committed due to testing) which prevents cookies from being sent over non-HTTPS sessions. I've removed that so it's fixed now and will either be allowing insecure cookies or forcing all connections to be over HTTPS.
Thanks for the report!
—
Reply to this email directly or view it on GitHub.


gpg key imported but not trusted

Description:
Set up gpg correctly, but in the mvn deploy step failed with message:
gpg: no default secret key: No secret key
[GNUPG:] FAILURE sign 17
gpg: signing failed: No secret key

Task version:
uses: actions/setup-java@v4
Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Repro steps:
Repro link: https://github.com/Jeff-Tian/keycloak-services-social-weixin/actions/runs/10439001430/job/28907013626
Expected behavior:
Deploy success
Actual behavior:
Failed.
** Extra Info:**
After many runs with different debugging command, now it seems that the key imported but not trusted.

Hello @Jeff-Tian 👋,
Thank you for reporting this. We will investigate the issue and get back to you as soon as we have updates.

Hello @Jeff-Tian,
It appears that the issue has been resolved.
The difference between these commands is that gpg --armor export exports a public key in ASCII-armored format, whereas  gpg --armor export-secret-keys  exports a secret/private key in ASCII-armored format.
You will need to provide the secret key and passphrase for GPG to work.
Please feel free to reach out to us if you encounter any other issues.


brew install not working on M1 Mac (arm64)

Env
ProductName:	macOS Monterey
ProductVersion:	12.5
M1 (Arm64)

brew install fails in invalid CPU arch error.
Error
$ brew tap ktorio/ktor
...
$ brew install --build-from-source ktor
ktor: The x86_64 architecture is required for this software.
Error: ktor: An unsatisfied requirement failed this build.

Please install rosetta to be able to install and run Ktor utility.
softwareupdate --install-rosetta

@Stexxe
Thanks for developing the new version.
Will v0.2.0 also be available in homebrew format?
https://github.com/ktorio/homebrew-ktor

@utamori, yes, we will soon add the formula to Homebrew.

You can now install the tool via Homebrew. The readme will be updated by this PR.


Fix precedence of negation vs comparison

Fixed antlr grammar to correctly prioritize negation vs comparison when parsing.
Before fix, expression !foo == 'bar' was parsed into:
Negate(Comparison(==, Property(Foo), String(bar)))

After fix, expression !foo == 'bar' is parsed into:
Comparison(==, Negate(Property(Foo)), String(bar))

Taking the JS implementation as the source of truth, because it prioritizes negation vs comparison. Example:
search(!foo == `true`, {"foo":1}) // false

First foo (which is equal to 1) is negated, resulting in false. Then, the result is compared to true, so the final result is false. Before the fix, this Java implementation would return true for the same expression, because first foo is compared to true, which results in false (because 1 != true) and the result is negated, resulting in true.

Hi. I'm not sure what makes this different from #69, but thank you for fixing this! Will this fix #65?
I'm sorry that I'm not very responsive when PRs come in, I don't have much time to spend on this, but I will get this merged and release, I just can't promise you when.

#69 had some unintended changes pushed and then removed, otherwise the change is the same. Regarding issue #65, I think it should have been solved by PR #66.


Minor additions to coord exports

Other exports + tests Do not merge until #35 is merged.
Note that we should probably come up with a better way of doing these rather than relying on the existing switch statement. For example, tags.h could define ....
template <typename T> static std::string to_string(T) = delete;
template <> static std::string to_string(X_t) { return "Coord::X"; }
template <> static std::string to_string(Y_t) { return "Coord::Y"; }

@OwenArnold This branch needs updating now.

Closing as going to merge with https://github.com/mantidproject/dataset/pull/47 datasetslice_exports


Can't share bins

From the screenshot above I created a new bin and when I couldn't find a share menu I thought my URL would be automatically updated to a sharable one but there it is with no custom url to share. Then I tried jsbin.com/myusername/last and got a 404 because even /myusername returns a 404.

I derived from the console that the save script returns a 500 header

I can see from the screenshot it didn't work. What was the content of the
html you were trying to save with? And does it still happen?
On Mon, 22 Aug 2016, 08:16 B<EMAIL_ADDRESS>wrote:

I derived from the console that the save script returns a 500 header
[image: 500 Error console log]
https://camo.githubusercontent.com/3b146da60d1f3a6fd18ae06c5cdb3cdbbe46cd55/68747470733a2f2f692e6779617a6f2e636f6d2f64626532666162313137666163626664303739356332316332653434383962662e706e67
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsbin/jsbin/issues/2854#issuecomment-241331817, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hFV4o1y4kpqmgdvunuDgIQtyqyKUks5qiUy_gaJpZM4JpkDu
.

I created a new bin in a different browser (Safari) and copied the contents from Chrome in there since that had a URL. The HTML content is here