Error when deploying latest version.

Afterhelm upgrade --install cert-manager-webhook-linode --namespace cert-manager cert-manager-webhook-linode/ --create-namespace got error: cert-manager "msg"="error executing command" "error"="unknown flag: --v"
Chart has been deployed after removing this lines from chart:
# {{- if .Values.deployment.logLevel }}
#             - --v={{ .Values.deployment.logLevel }}
# {{- end }}

I guess unsetting .Values.deployment.logLevel should also work.

for the next poor soul who stumbles upon this, the command would be:
helm upgrade --install cert-manager-webhook-linode --namespace cert-manager https://github.com/slicen/cert-manager-webhook-linode/releases/download/v0.2.0/cert-manager-webhook-linode-v0.2.0.tgz --set deployment.logLevel=null

next up, there is no RBAC permissions set for system:serviceaccount:cert-manager:cert-manager-webhook-linode trying to replicate values from https://github.com/neoskop/cert-manager-webhook-dnsimple/issues/8


DBZ-6439 Don't scan all the tables when loading schema

Enable set log level in tests (https://issues.redhat.com/browse/DBZ-6460)
Don't scan all the tables when loading schema (https://issues.redhat.com/browse/DBZ-6439)

@vjuranek Applied, thanks!


Calling a model and using model.predict yields different results for the same input

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): yes, see in standalone code to reproduce behaviour
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS Monterey 12.4
TensorFlow installed from (source or binary): installed using pip install tensorflow-macosand pip install tensorflow-metal
TensorFlow version (use command below): v2.13.0-rc2-7-g1cb1a030a62 2.13.0
Python version: 3.10.9
Bazel version (if compiling from source):
GPU model and memory: Apple M1, 16 GB LPDDR4
Exact command to reproduce: see in standalone code to reproduce behaviour

Describe the problem.
When I call model(data) and model.predict(data) i get different outputs.
I provided a minimal working example below.
Describe the current behavior.
When I call model(data) and model.predict(data) i get different outputs.
Describe the expected behavior.
Calling model(data) and model.predict(data) should give the same output
Contributing.

Do you want to contribute a PR? (yes/no): no

Standalone code to reproduce the issue.
from tensorflow import keras
import numpy as np

nn = keras.Sequential([
  keras.layers.Input((1)),
  keras.layers.Dense(2,activation = 'relu'),
  keras.layers.Dense(1,activation='linear')
])

nn.compile()

data = np.ones((1))

print(nn(data, training=False))
print(nn.predict(data))

@sachinprasadhs I was able to replicate the issue reported here. Thank you!

When i execute my code in the google colab notebook, I don't get my error.
Could this be an issue with the M1 version of tensorflow?
Here is a screenshot of whats happening on my machine:

Hi, I installed the latest Tensorflow version using pip install tf-nightly and consistently I was able to get the same output on my M1. Please refer the below attached screenshot for reference.


fix(test): karma-dist should test bundle under dist

update karma-dist.conf.js
current karma-dist.conf.js will load bundles under dist and the purpose is to test those built bundles instead of the dev version which under build folder.
so in karma-dist.conf.js, we will load
 config.files.push('dist/zone.js');
 config.files.push('dist/async-test.js');
...

But in current test cases will load some of the lib directly from build folder, for example in async-test.spec.ts, in current version, it will load
import '../../lib/zone-spec/async-test';

so the test case in fact will not test the bundle under dist but build.

in this PR, I load all needed bundles in karma-dist.conf.js and remove all directly import from test specs. And also modify the test entry classes to make sure currently test cases will be ok for both build test and dist test.

in dev mode, test bundles under build.
in dist mode, test bundles under dist.

Also disable ios 8.4 test because saucelabs seems not stable
change default karma browser to Chrome.
change rollup globals.

can you resolve these?


Convert message_parser, password_quality, watchdog, composer_error and upload_widget  to TS

Merged, thanks @priyank-p!


Include bevy_text feature in bevy_ui

Was this intentional? It seems pretty weird to keep them seperate.

I maybe take this back? What's the story for people using default-features=false? bevy_core_pipeline is also not added when bevy_render is added (and maybe bevy_winit should be added too?). I can see the argument that everything should be chosen explicitly since most people won't use default-features=false anyway.

default-features=false has two audiences:

People doing something unusual that want to improve their compile times in serious projects.
Library authors, since features are additive.

Makes sense!

related: #7855


policy instrument roles/qualities/functions

Description of the issue
In #1545 we added economic instrument, regulatory instrument, information instrument, education instrument, voluntary agreement instrument and voluntary agreement to bring structure in the policy instruments.
However, there are instruments that fit in more than one category. E.g. the European Union Emissions Trading System can be seen both as an economic instrument (as certificates are traded) and as a regulatory instrument (as the emissions market only exists due to regulatory intervention).
Ideas of solution
Create a multihierarchy by introducing policy instrument roles/qualities/functions and convert the existing subclasses of policy instrument to equivalent classes.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

First try:

An economic instrument quality is a quality of a policy instrument that expresses that the policy instrument has aspects of an economic instrument.
A regulatory instrument quality is a quality of a policy instrument that expresses that the instrument has aspects of an economic instrument.
...

(I know, these are definition proposals are bit cyclic...)

@stap-m : any thoughts on this proposal?

An economic instrument quality is a quality of a policy instrument that expresses that the policy instrument has aspects of an economic instrument.
A regulatory instrument quality is a quality of a policy instrument that expresses that the instrument has aspects of an economic instrument.

I replaced "quality" with "property" for now. I hope that we can find a def that expresses, what we mean, and see, which classification fits in the next step.
I also made some changes to find a clearer definition. Does this express, what we mean?

An economic instrument property is a property of a policy instrument that promotes, amongst others, economic measures.
A regulatory instrument property is a property of a policy instrument that promotes, amongst others, regulatory measures.
...

Axioms:

'economic instrument' EquivalentTo ('policy instrument' and 'has property' some 'economic instrument property'
...

Do we have property resp. has property?

No, its just a placeholder for now...

I would really like to move on with this issue. A pragmatic solution without deciding yet on whether a policy property is a role, a quality or a function would be to implement the the properties as direct subclasses of realizable entity.[^1] 😄
[^1]: Including an editor note that they will be finally made subclasses of either role, quality or function.

An economic instrument property is a realizable entity of a policy instrument that promotes, amongst others, economic measures.
A regulatory instrument property is a realizable entity of a policy instrument that promotes, amongst others, regulatory measures.
...

Axioms:

'economic instrument' EquivalentTo ('policy instrument' and 'has characteric' some 'economic instrument property'

These wouldn't be the first direct subclasses of realizable entity, we already have acceptance there.

Your suggestion reads good to me, the editor note also helpful for those viewing the OEO.

I read again about functions, roles and qualities. About function, Arp et al 2015 says:

A function is a special kind of [...] realizable entity whose realization is an end-directed activity of its bearer  [...]. Thus a function is a disposition that exists in virtue of the bearer’s physical make-up, and this physical make-up is something the bearer possesses because of how it came into being — either through natural selection (in the case of biological entities) or through intentional design (in the case of artifacts).

In our case, we could say that certain policy instruments are designed to have e.g. an economic impact and therefore have an economic instrument function.

So can I implement these as functions or is there anything left to discuss here?

Yes, please, go ahead!

I've implemented as discussed however we overlooked a thing:
A function needs an independent continuant as bearer, however a policy instrument is an information content entity and therefore a generically dependent continuant. Therefore the reasoner now fails in my feature branch of PR #1906.

I see. For has role we've already broken up the original range and changed it to just continuant, e.g. to enable model role. We did this based on a discussion with @fabianneuhaus.
We might think of doing the same to has function. However, changing the range of imported relations is not a clean solution... 🤔 😕

I think, the cleanest solution is to use has characteristic instead of has function:

has characteristic is the parent object property of has function
it is inverse of characteristic of, which is annotated like this:

Implemented in #1906


Should foreing keys provide an URI to the linked resource?

You often find APIs that provide not only ID's or primary keys to external resources, but also an href field which can be used to retrieve that particular resource or set of resources.
As an example, let's say GET https://example.com/posts?id=eq.123 gives us:
{
    "title": "Some title",
    "body": "...",
    "author": 12
}

It would probably be nicer to have this instead:
{
    "title": "Some title",
    "body": "...",
    "author": { "href": "/users?id=eq.12", ... }
}

This helps for example in the case in which you have an automatic lazy JSON evaluator that takes your resource and allows retrieval of subfields based on this href subfield lazily.
It also provides an opaque resource ID that is not dependent on the actual ID name for the table.
This idea is apparently called HATEOAS, and I've seen this recommended often as it improves the navigation within the API.
Implementation wise this doesn't sound too difficult, as foreign keys are part of the schema and easily analizable.
What downsides am I missing? Should I try to implement this?

Good idea about helping clients discover related resources. How about leaving the json body unmodified but including Link response headers?
Link: </users?id=eq.12>; rel="author"

I didn't even know there was a specific header field for this. Yes, this sounds like a great idea. I'm not sure how easy to parse this header field is with existing Javascript (assuming that's used for the frontend, or any other) libraries though.

Jeffery, you're right about the HATEOAS, and it's actually the very first thing I'm starting to work on once I learn how to build postgrest from source. :-) The content details are a bit different, however, and just how far postgrest can go on its own based on what it discovers from the database structure is limited but still quite useful.
JSON-HAL is probably the closest model to what I like ( http://stateless.co/hal_specification.html ). There is also JSON LD ( http://json-ld.org/ ) which looks closer to what your example uses and also intends to enforce a more strict schema. Support for both (and others) could be implemented and selected based on the accept request header content.
The result content would look something more like this:
{
"title": "Some title",
"body": "...",
"author": 12,
"_links" :
{
"self": { "href" : "https://example.com/posts?id=eq.123" }
"author": { "href" : "/users?id=eq.12" }
}
}
There's a lot more to it but the point is that a simple client can consume the original content directly but a JSON-HAL aware client knows to parse and act on the provided links and their semantics.

This also makes nested URIs fairly easy to directly model. For example, if the primary key for both posts and author is id then you'd have:

https://example.com/posts/123/
{
"id": 123
"title": "Some title",
"body": "...",
"author": 12,
"_links" :
{
"self": { "href" : "https://example.com/posts/123/" }
"author": { "href" : "/author/12/" }  // note this relation could be exposed as ~/posts/123/author/
}
}
One of the key values here is that you don't need to know the structure of the service to be able to discover its api and navigate its links. This is a key value of REST.

Oh yes, self might also be useful. But if we are going to have a separate section explicitly for links, I'd recommend to use the Link header field, just like @begriffs suggested.

There are pros and cons to both the Link header and the json _links attribute.

In favor of Link headers

Old standard
Can be recognized by intermediaries like proxies
Annotates the resource itself, not its json representation (applies to non-json representations if we later add them)
Supports link hints

In favor of HAL _links

Off the shelf client libraries are available to deal with it
Can add link information to responses with more than one resource, such as many posts each having an author link (Link headers apply to the entire response, not per-element)

I think client javascript can handle either solution. Ajax in the browser provides the response headers if you ask for them. So it's more a matter of the above pros and cons. I'd favor of Link headers except I don't know how they can handle responses containing multiple results each with their own links.

Link headers are not quite practical for a lot of purposes, really.
As you say, Link headers are global to a response, so it’s you’d
first need to construct a link relation type that specifies precisely
what part of the response entity a link applies to.  This is
unfortunate for at least one reason: link relation types would have to
contain things such as indices or identifiers in case of collection
resources, and it is not always clear how to do this — and in any
case, you’d end up with tons of link relation types containing a
combination of the link semantics and the path from the root of the
resource to the actual link (such as an index into the collection).
It’s nice when link relation types are limited to a small, consistent,
and even standard
vocabulary,
and it’s in line with one of the fundamental ideas of REST: providing
a uniform interface.
A more practical issue is that HTTP intermediaries may collapse
multiple occurrences of a header into a single one, so if you have a
response with lots of Link headers, they may all end up aggregated
into a single header with the list of all links, and it may end up
being dropped or truncated (or cause the whole response to be dropped)
if it gets so long that it hits header length limits imposed by HTTP
intermediaries such as caches and proxies.
In terms of REST principles, HATEOAS means resource representations
should themselves be hypermedia and thus contain in-line the URIs
of linked resources to indicate possible actions or navigational
transitions.  The URLs should therefore be part of the resource
representation itself (if adherence to strict REST ideology is
desired, of course) — it would probably be considered almost
out-of-band information to use Link headers to specify links.  This
is arguable of course, as the headers are part of what you get from
the server yet they’re not part of the resource representation.
HATEOAS does strongly suggest links are first-class data, not
second-class metadata, though.
Have you looked at Siren?  HAL
is very nice indeed, but Siren is a bit more expressive.  I even have
some old code
(for a project with a very similar approach to Postgrest, by the
way) that helps create Siren documents in Haskell.  Feel free to use
it in any way you want, although I would not necessarily recommend
using it directly as I was playing with some questionable language
extensions at the time.

I would still recommend inline JSON objects with href and rel fields, as opposed to a globally accessible (from the JSON resource) _links separated metadata, as it introduces an important precedence: reserved keys.

Really excellent points, thanks everyone. Seems like adding links to the representation is the way to go. It won't be easy since postgresql is generating the entire json response. To add links we'll have to either get clever with the queries or else parse, modify, and re-serialize the response body in the haskell code.

I vote for including references inline the object representation as well. Link headers would just be too awkward for collections (and too numerous).

It won't be easy since postgresql is generating the entire json response. To add links we'll have to either get clever with the queries or else parse, modify, and re-serialize the response body in the haskell code.

If PostgREST is going to support other response formats or transformations, this will have to happen anyway. I know I'll need to do transformations to the results before serializing the response for my use-case.

To add links we'll have to either get clever with the queries or else parse, modify, and re-serialize the response body in the haskell code.

Small insignificant point: re-serialization at the Haskell level would make sense, since the "href" links are something at the web server level, not concerned with the data itself.

You could do something like this?
      create or replace view "1".events as
      SELECT
        uuid, data->'name' AS name,
        data->'age' AS age,
        CONCAT('{"self": {"href": "http://localhost:3000/events?uuid=eq.', uuid, '"}}')::json AS _links
      FROM items
      WHERE CAST(data->>'kind' AS text) = 'events';

Which would return something like this
[
  {
      "uuid": "f2655290-adcd-4992-956b-eb71995df091",
      "age": 1,
      "name": "lorem",
      "_links": {
          "self": {
              "href": "http://localhost:3000/events?uuid=eq.f2655290-adcd-4992-956b-eb71995df091"
          }
      }
  }
]```

+1 to inline HATEOAS style.
+1 for fancier queries (less chance of bugs, probably better performance)

+1 to JSON-LD (same as example in the OP except @id vs href).
This would be really helpful with @ruslantalpa's additions in #295 to allow for better client side caching by associating a unique id with each object.
Also related is #235

-1 to JSON-LD :)
If we go back to the first post from @Jefffrey it seems to me that what he actually wants is to be able to fetch related content which is now possible using &select
On the first page of JSON-LD "It allows an application to start at one piece of Linked Data, and follow embedded links to other pieces of Linked Data that are hosted on different sites across the Web"
In postgrest case, the related data is clearly not on a different site.
I am not sure how the links are helping anyone. Is there a js client lib that we can point to postgrest and if we have the links it will be able to automatically fetch related objects similar to project.getClient()?
If so then it might make sense but if not then there is no "automatic", a developer would still need to code this ability based on those links and if he is at that stage, why not construct the link manually since he clearly knows he's working with postgrest and is building something custom to consume postgrest.
Anyway, there might be valid use cases for this but this should be a optional/pluggable module, not the default embedded functionality.
Once the code is more uniform (auth is sorted and mutations are also done with parsers and querybuilder) then we can look at the whole system as a big pipe composed of different small functions that progressively transform/mutate the request (the benefit of having an internal data type).
If we get it to that stage, then features like this can be implemented by a small fn in the chain that can be conditionally compiled.

I'm all for the full adoption of the JSON-LD spec (in that case the @context object can turn a simple URL string into a semantic hyperlink), but that won't be fully plausible until a Haskell JSON-LD library has been created like the JavaScript.
The most important part of the spec to me (and something we should implement even if it's not with JSON-LD) is the identification of objects. The new additions to the &select parameter are awesome, but the objects lack any form of unique identification. You could argue they could expose an id property, but that is just a number and in no way specifies what route the object should be located at.
The new &select also introduces a caching problem. Because objects have no unique identifier and they are bested (to a theoretical infinity) it is a breeding ground for stale data. Two films may have the same actor, but when that actor gets updated there is no good universal way for the client (without knowing the entire data model) to update all instances of that actor.
That's why I propose we only adopt the @id part (for local resources alone) of the JSON-LD spec. Choosing JSON-LD also gives us the ability to add more and more of the specs features as it makes sense.
For me, effective client side caching is on my list to get the code base more uniform right there with effective auth.

Maybe these various ways of expressing where to find related resources are less important now that @ruslantalpa has allowed us to embed those resources in one request as needed.

@begriffs I'd say they are more important so clients understand the exact location of embedded resources. Normalizing loses some context.

Given that the db is the one creating the JSON responses it's a big change to have the haskell code generate or modify the response body, and a change that will likely make the code slower and more memory intensive.
How about something more modest like link headers on singular results (aka when Prefer: plurality=singular was requested)?

There was was no activity for some time here, issue could be closed ...

Hmm, this old issue... I'll say yeah let's close it but we'll keep in mind that these relationships should be included in the improved API self-documentation we've been talking about.


Web Deploy task exclude files / folders

Right now, the web deploy task removes folders or files that are not part of the build.  This is causing issues with our logging files that we want to retain as well as images that are placed on the server from a CMS system.

We need more details about the build definitions, tasks and path examples.

Sure.  I am using the IIS Web App Deployment tasks to take a pre-built .zip file that was generated from a MSBuild task.  I want to take that zip file and deploy it to a specific file on an on-prem server, and it is deleting out the subfolders within the location I am deploying to.  So for my example, I am trying to deploy to D:/Websites/uat_coll where I am running my web application, and it is deleting out the folders at D:/Websites/uat_coll/images even though that folder doesn't exist in the bundled zip file that was created by the msbuild task during the build phase of the steps.

As the intent of the task is to deploy to web deploy package to the specified location. We use msdeploy -verb:sync option to do that and this command extracts the zip and makes sure that target folder is in sync with source zip, it is expected behavior.
Can you help me understand why the images folder is static in that folder, instead this should have been checked into to source control along with web project, so that zip will contain this.

https://github.com/Microsoft/vso-agent-tasks/issues/1215

We will address this feedback in next version, for now you can pass -enableRule:DoNotDeleteRule in override params section of the task

Can I go ahead and close the issue?

Sure, thank you.
----- Original Message -----
From: "Subrahmanyam Mandavilli"<EMAIL_ADDRESS>To: "Microsoft/vso-agent-tasks"<EMAIL_ADDRESS>Cc: "swcarter007"<EMAIL_ADDRESS>Sent: Wednesday, March 30, 2016 3:03:23 AM
Subject: Re: [Microsoft/vso-agent-tasks] Web Deploy task exclude files / folders (#1215)
Can I go ahead and close the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

We are creating an extension for this task soon, We will add this feature in that version of task. Thanks for your feedback, we will track it, you can refer above commit to unblock your self


[util] Standardize auto-generated code warning msg

This PR attempts to provide a standalone Python method that returns a
warning message box indicating that the source is autogenerated.
The get_autogen_banner() takes two arguments - command and
comment. It uses tabulate to create a text box containing the
warning banner and the supplied command that wraps to ~70 characters and
is center-justified for a clean look. The comment which is the correct
style supported by the file is applied to all lines and the final text
is returned as a string. Below are some examples:
Example 1:
# +---------------------------------------------------------------------+
# | ----- W A R N I N G: A U T O - G E N E R A T E D   C O D E !! ----- |
# | DO NOT EDIT THIS FILE DIRECTLY. IT HAS BEEN AUTO-GENERATED WITH THE |
# |                         FOLLOWING COMMAND:                          |
# |    util/topgen.py -t hw/top_earlgrey/data/top_earlgrey.hjson -o     |
# |                           hw/top_earlgrey                           |
# +---------------------------------------------------------------------+

Example 2:
// +---------------------------------------------------------------------+
// | ----- W A R N I N G: A U T O - G E N E R A T E D   C O D E !! ----- |
// | DO NOT EDIT THIS FILE DIRECTLY. IT HAS BEEN AUTO-GENERATED WITH THE |
// |                         FOLLOWING COMMAND:                          |
// |   ./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i    |
// |         chip_plic_all_irqs --waves -v h --local --run-only          |
// +---------------------------------------------------------------------+

It will be great to standardize on how we indicate the source has been
autogenerated, considering we have a lot of scripts that autogenerate
lots of things in our codebase. Happy to hear thoughts and opinions on
improving how this should look further.
Signed-off-by: Srikrishna Iyer<EMAIL_ADDRESS>

Looks like a good idea. I'm not so sure about the main function, though: I'd have thought we'd want to dissuade people from running the script and pasting the results into their templates :-)

Looks like a good idea. I'm not so sure about the main function, though: I'd have thought we'd want to dissuade people from running the script and pasting the results into their templates :-)

Agreed - the main() is temporary, just until we finalize how should this look.

Also, I feel like the box/text centering is unnecessary; among other things, it makes it quite hard to copy-paste the command, which ideally should just be on one long, un-wrapped line.
Very well, sounds good. Updated.
Finally, I'm not sure this is an exhaustive list of affected scripts, and we probably want this to be discoverable to stop it from backsliding... @timothytrippel you will have opinions. =)
Agreed -will make this discoverable and apply to all scripts once we are happy with how this looks.

I'm with @msfschaffner and would keep the line breaks: if we have to run the command manually, it's not a big deal to remove a couple of # characters :-) (And, hopefully, we've got CI checks that ensure that we'll never need to run it manually anyway!)

I think the commit diffs are a bit noisy and make it hard to tell what's changed. Can you blow away the second commit and rebuiild it to only contain changes due to the new tool?

Ok.

To Michael's comment, it may be worth trying to crop down the size of the printed commands, but I'm not thrilled. I would also consider avoiding making all of the lines be as long as they are (with the dashes and whatnot) since they make wrapping sad in other places, too.

I agree with others - having to manually run the commands will be very rare, so splitting it on multiple lines does not seem like a huge deal.

I'd take a look at something lighter weight, such as what manticore does: https://github.com/lowRISC/manticore/blob/master/fuzz/gen/manticore_protocol_capabilities_DeviceCapabilities__req_from_wire.rs#L5.
Finally, regarding main(): I don't think it's worth keeping while we're discussing the format. If the format is such a huge deal, maybe we should break it off as a separate discussion... but that seems like a poor use of time.

Yes, I did say im my previous comment that I will remove it.

In the latest force-push, I addressed most of the comments. The warning banner now looks like this:
# ---------------------------------------------------------------------
# ------ W A R N I N G: A U T O - G E N E R A T E D   C O D E !! ------
# DO NOT EDIT THIS FILE DIRECTLY.  ------
// DO NOT EDIT THIS FILE DIRECTLY. GENERATED WITH THE FOLLOWING COMMAND:
// util/topgen.py -t hw/top_earlgrey/data/top_earlgrey.hjson -o
// hw/top_earlgrey
// ---------------------------------------------------------------------

The input command is wrapped so that the linters are happy.

I think the commit diffs are a bit noisy and make it hard to tell what's changed. Can you blow away the second commit and rebuiild it to only contain changes due to the new tool?

For future reference, sometimes with these sorts of things I find it easier to split into ~2+ PRs (similar to how I did with the IRQ DIFs):
-1st PR: just the tooling and proposed format
-2nd+ PR: updating templates and re-generating code with new templates.

To Michael's comment, it may be worth trying to crop down the size of the printed commands, but I'm not thrilled. I would also consider avoiding making all of the lines be as long as they are (with the dashes and whatnot) since they make wrapping sad in other places, too.
I'd take a look at something lighter weight, such as what manticore does: https://github.com/lowRISC/manticore/blob/master/fuzz/gen/manticore_protocol_capabilities_DeviceCapabilities__req_from_wire.rs#L5.
Finally, regarding main(): I don't think it's worth keeping while we're discussing the format. If the format is such a huge deal, maybe we should break it off as a separate discussion... but that seems like a poor use of time.

Our tools are quite customizable - topgen for example takes different arguments to generate code in specific ways. This does not seem feasible.

I think I was unclear. I'm suggesting that all of the ----- characters and spaces between letters are unnecessary; keep it simple. This is going to become irrelevant once we bring Bazel online, so let's not do anything fancy.

Our tools are quite customizable - topgen for example takes different arguments to generate code in specific ways. This does not seem feasible.

I think I was unclear. I'm suggesting that all of the ----- characters and spaces between letters are unnecessary; keep it simple. This is going to become irrelevant once we bring Bazel online, so let's not do anything fancy.

IMO having an outline is useful. I will make the other text a bit simpler. I will let others weigh in too.
Not sure how is bazel going to render this obsolete (maybe for SW) - keeping the generated HW sources checked in was a long long discussion that we've already had (and have agreed to it).

Our tools are quite customizable - topgen for example takes different arguments to generate code in specific ways. This does not seem feasible.

I think I was unclear. I'm suggesting that all of the ----- characters and spaces between letters are unnecessary; keep it simple. This is going to become irrelevant once we bring Bazel online, so let's not do anything fancy.

For something that you think is going to be irrelevant, we sure are having a lot of discussions :)

Addressed all comments in the latest push.


Handle XML CDATA

As CDATA is part of the XML specification, I think xpath should abstract the handling of it.
var xpath = require('xpath');
var dom = require('xmldom').DOMParser;
var xml = "<MediaFile><![CDATA[https://server]]></MediaFile>";
var doc = new dom().parseFromString(xml);
var file = xpath.select("//MediaFile/text()", doc).toString();
console.log(file);

In my opinion xpath should return "https://server", not "<![CDATA[https://server]]>".

When you call xpath.select() on an expression that evaluates to a nodeset (and that is the case here), it returns an array of DOM nodes.
What you are doing here is calling .toString() on an array, which is producing a concatenation of the .toString() values of its elements.
So this isn't really an issue with the xpath library's treatment of CDATA sections. The library handles their string values correctly, but you are effectively using .toString() directly on DOM nodes and that depends on their default behavior.
To get around this:
Option 1: Wrap your expression in a string() function, so that .select() produces a string:
var file = xpath.select("string(//MediaFile/text())", doc);
console.log(file);

Option 2: Use the parsed expression functionality that I have added in my fork of this project. This provides methods to allow selecting the result type that you want:
var file = xpath.parse("//MediaFile/text()").evaluateString({ node: doc });


When is the approximate time for the code to be open-sourced?

Has the code already been open-sourced? Could you provide the complete code?

Thanks for your interest, the code is still being organized. We expect to have the code available by the end of September at the latest. If you would like to be notified when the code is released, you can fill out this Google Form.


Quoted string parser reports end of file when encountering an empty line

Describe the bug
When quoting a string it is possible to have text that goes on multiple lines. If the multiline string contains an empty line however, the parser fails even if the string is properly closed.
To Reproduce
Create a fluentd config like this:
<filter test>
  @type record_transformer
  <record>
    hello "world

"
  </record>
</filter>

Run fluentd in dry-run mode:
fluentd --dry-run -c /tmp/fluent.conf
Traceback (most recent call last):
	18: from /Users/me/.rbenv/versions/2.5.1/bin/fluentd:23:in `<main>'
	17: from /Users/me/.rbenv/versions/2.5.1/bin/fluentd:23:in `load'
	16: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/bin/fluentd:15:in `<top (required)>'
	15: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:85:in `require'
	14: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:85:in `require'
	13: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/command/fluentd.rb:351:in `<top (required)>'
	12: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/supervisor.rb:624:in `configure'
	11: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/supervisor.rb:682:in `setup_global_logger'
	10: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config.rb:52:in `build'
	 9: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config.rb:71:in `parse'
	 8: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:33:in `parse'
	 7: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:44:in `parse!'
	 6: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:96:in `parse_element'
	 5: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:96:in `parse_element'
	 4: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:131:in `parse_element'
	 3: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/literal_parser.rb:75:in `parse_literal'
	 2: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/literal_parser.rb:82:in `scan_string'
	 1: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/literal_parser.rb:114:in `scan_double_quoted_string'
/Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/basic_parser.rb:92:in `parse_error!': unexpected end of file in a double quoted string at fluent.conf line 6,17 (Fluent::ConfigParseError)
  5:   <record>
  6:     hello "world

     -----------------^
  7:

Expected behavior
The string should be parsed like any other multiline string. In this case I'd expect hello to be set to "world\n\n".
Your Environment
- Fluentd version: 1.16.6

Your Configuration
<filter test>
  @type record_transformer
  <record>
    hello "world

"
  </record>
</filter>

Your Error Log
Traceback (most recent call last):
	18: from /Users/me/.rbenv/versions/2.5.1/bin/fluentd:23:in `<main>'
	17: from /Users/me/.rbenv/versions/2.5.1/bin/fluentd:23:in `load'
	16: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/bin/fluentd:15:in `<top (required)>'
	15: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:85:in `require'
	14: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:85:in `require'
	13: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/command/fluentd.rb:351:in `<top (required)>'
	12: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/supervisor.rb:624:in `configure'
	11: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/supervisor.rb:682:in `setup_global_logger'
	10: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config.rb:52:in `build'
	 9: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config.rb:71:in `parse'
	 8: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:33:in `parse'
	 7: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:44:in `parse!'
	 6: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:96:in `parse_element'
	 5: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:96:in `parse_element'
	 4: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/v1_parser.rb:131:in `parse_element'
	 3: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/literal_parser.rb:75:in `parse_literal'
	 2: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/literal_parser.rb:82:in `scan_string'
	 1: from /Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/literal_parser.rb:114:in `scan_double_quoted_string'
/Users/me/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/fluentd-1.16.6/lib/fluent/config/basic_parser.rb:92:in `parse_error!': unexpected end of file in a double quoted string at fluent.conf line 6,17 (Fluent::ConfigParseError)
  5:   <record>
  6:     hello "world

     -----------------^
  7:

Additional context
No response

This also happens if a line is terminated with a literal backslash:
<filter test>
  @type record_transformer
  <record>
    hello "world \\
test"
  </record>
</filter>

It seems that the limitation of current implementation.
As a workaround, use "\n" explicitly.

Thanks for your report.
It appears this is a bug of Fluentd.
This works.
<filter test.**>
  @type record_transformer
  <record>
    hello "world
"
  </record>
</filter>

However, the following don't work.
<filter test.**>
  @type record_transformer
  <record>
    hello "world

"
  </record>
</filter>

<filter test.**>
  @type record_transformer
  <record>
    hello 'world
'
  </record>
</filter>

<filter test.**>
  @type record_transformer
  <record>
    hello 'world

'
  </record>
</filter>

It looks like single-quoted strings don't support multiline.
https://docs.fluentd.org/configuration/config-file#multiline-support-for-quoted-string-array-and-hash-values
So, we need to check double quoted strings behavior, as @Alainx277 says.


jQuery.on() and .off() have several unhandled overloads

Their signatures are:
.on( events [, selector ] [, data ], handler(eventObject) )
.off( events [, selector ] [, handler(eventObject) ] )
but touche.js only handles the trivial case where events is a single event name.
Problem cases:

events is a space-separated list of event names, possibly namespaced
events is an object, which causes our subsequent slice() call to explode

On case 2:

Uncaught TypeError: undefined is not a function

Line 66 fails.
if (event.slice(0, 5) == 'click')


Shorten obs station example

This is a bit of a toy PR really.  I thought that in the current numpy course, the sections on broadcasting, arithmetic and masking all refer to this Observation Stations example but really badly; there are bits where it just brings it up out of the blue and expects you to remember the scenario that was introduced a lot of context-switching earlier.
This PR plays with several ideas:

Make references to the Obs Station scenario less surprising
Add some pandas dataframes (not generated in the course) to give a better graphical representation of the problem
Be a little easier to follow

I have also added the notebook which generates the dataframes to the images folder, but this is purely for reproduceability.  (How do you spell that word...?)

@pelson @corinnebosley I think I've superseded this PR with #139...

@dkillick agreed.


Add exception file JSON validation

CI should at least check that the exception file is valid JSON. See #73 for a justification.

wait, it's already done...


The helper doesn't work well during the development of the tests

Describe the bug
I'm using Laravel/Lumen with the lighthouse package. The development of the schemas is working correctly without errors.
However, when I'm defending the tests the IDE is marking me errors that shouldn't be there (as you can see in the image)
Do you know how to make the helpers work?
Expected behaviour
The helper should identify the compiled schema during the testing.
Screenshots

Version and Environment Details
Operation system: Mac
IDE name and version: PHPStorm 21.1.4
Plugin version: 3.0.0

Sorry for replaying so late!
This is not a bug.
I played until I found a working solution correctly in that lighthouse project.
This is the current configuration inside the .graphqlconfig file:
{
    "projects": {
        "BE": {
            "excludes": [
                "./storage/app/lighthouse-schema.json"
            ],
            "includes": [
                "graphql/**",
                "schema-directives.graphql",
                "programmatic-types.graphql"
            ]
        },
        "FE": {
            "excludes": [
                "graphql/**",
                "schema-directives.graphql",
                "programmatic-types.graphql"
            ],
            "schemaPath": "./storage/app/lighthouse-schema.json"
        }
    }
}

Remember to run @php artisan lighthouse:print-schema --write --json.
ps. Often the changes made to the file .graphqlconfig or the file ./storage/app/lighthouse-schema.json are not loaded immediately on the plugin. So wait or reopen the phpstorm.


Auditor v2 dataaccess

Need to write tests. This includes all of the auditor code... apparently I didn't merge the rules engine stuff into the 2.0-auditor-dev branch yet.
Functional auditor that runs with really basic rules.
How to use it:

Create sample new_rules.yaml:

rules:
  - type: google.cloud.forseti.auditor.rules.rule.Rule
    description: Instance statuses
    name: rules.instance.status.1
    configuration:
      variables:
        - status
      resources:
        - type: instance
          variables:
            status: status
      condition: status != 'RUNNING'

  - type: google.cloud.forseti.auditor.rules.rule.Rule
    description: Test rule for project id
    name: rules.project.id.1
    configuration:
      variables:
        - resource_id
      resources:
        - type: project
          variables:
            resource_id: name
      condition: resource_id != "proj1"

In forseti_conf.yaml, add this section:

auditor:

    # Valid values are: debug, info, warning, error
    loglevel: info

    rules_path: /path/to/forseti-security/rules/new_rules.yaml

Run python setup.py install.

Run the forseti_server.

Run forseti auditor run --config <path to your forseti_conf.yaml>

Closing this -- there will be a new PR for new auditor developments.


Insights dashboard not working with fqdn as machine ID

Running crowdsec 1.4.6 on multiple machines and using prometheus 2.42.0 to scrape metrics. Using grafana v9.3.6 to display metrics using the dashboards from this repository in directory dashboards_v4.
Everything works as expected except the Crowdsec Insight dashboard which has a problem because of the way I tag my machines.
In the prometheus scrape config I added the machine's FQDN as machine label. This causes the Insight dashboard to escape the dots in the machine id, which in turn causes the panels to display empty values.
(process_start_time_seconds{machine="XX07\\.XXXX\\.XX"})*1000
The correct prometheus query should look like this.
(process_start_time_seconds{machine="XX07.XXXX.XX"})*1000
My very simple solution was to disable the "Multi value" and "Include all option" in the machine variable in the settings of the Insight dashboard.

Hello,
Sorry for the delay and thanks for your investigations.
The dashboards_v5 contains working dashboards for crowdsec 1.5, testing w/ Grafana 10.0 on Grafana cloud (including fixed heatmaps).
Please let me know if you face any further issues.


DBZ-429 Fixed signed default value handling

https://issues.jboss.org/browse/DBZ-429

Applied to master and 0.6. Thanks, @jpechane!


Using Multiple GPU

Is there an environ setting to enable which GPU to use and the ability to use more than one for CUPY and Torch?
I am on a machine with 4 GPUs but it only uses GPU #1 which is in use by other processes.

Or a way to provide a list of input values and get a list of Wx back.

No built-in support for multi-GPU, but maybe torch/cupy can be told to use a particular device.

list of input values and get a list of Wx back.

Batched computation is supported, with separate inputs stacked along dim0:
x_batched = np.vstack([x0, x1])   # x0.ndim == x1.ndim == 1


Update jawn-parser to 0.14.3

Updates org.typelevel:jawn-parser from 0.14.2 to 0.14.3.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "jawn-parser" } ]

labels: semver-patch

Codecov Report

Merging #21 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   86.09%   86.03%   -0.06%
==========================================
  Files          18       18
  Lines         266      265       -1
  Branches       10       10
==========================================
- Hits          229      228       -1
  Misses         37       37

Impacted Files
Coverage Δ

...ce/generic/extras/decoding/ConfiguredDecoder.scala
91.37% <0%> (-0.15%)
:arrow_down:

Continue to review full report at Codecov.

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


Some parts of steam-tui are barely readable on light terminals

^ as shown above
It's especially hard to read on lower brightness settings. I think the main reason for that are the hardcoded colours, for example here. I think removing them might partially fix the issue as terminals should determine default colour themselves or use a crate like https://github.com/Canop/terminal-light to detect the style.

For sure, there is already configuration for the highlighting: https://github.com/dmadisetti/steam-tui/blob/b56fef8498a7cf372c83c12ef9bd6cdb482f398f/src/app.rs#L75
It would just be a matter of adding more color fields to Config: https://github.com/dmadisetti/steam-tui/blob/b56fef8498a7cf372c83c12ef9bd6cdb482f398f/src/config.rs#L17
Another point would be extending tui-image for background burn modes (currently alpha is assumed against a black background): https://github.com/AnotherGroupChat/tui-image/blob/bd44e59e0ffc0b7f5344bd02f4b22ec820025e30/src/lib.rs#L39
terminal-light is a nice find- but it's simple enough I'd maybe want to port it rather than include it as a dep? Maybe it's worth just adding another dep, but really we'd just use it to backfill for a default colour scheme

Ohhh yeahh, all those App functions are static because clippy yelled at me when I was too lazy to add all the color options, bit of churn to make them not static, but nothing too bad.


Expand on driver's documentation

As I'm going through this part again, I figured it would be a good day to expand on the documentation.
I'm wondering, what should happen with the libev driver and the winrt driver ? The later looks more like a stub, is it actually usable on winRT ? Do you have anything in mind for this part of the code ?

I did some experiments with WinRT and a full automatically generated set of D bindings, but didn't have time to actually put it to use, so most of this is indeed just a stub. It also requires the bindings and some build tweaks, so it's not usable like it is. Nowadays it actually becomes interesting again, because we have -m32mscoff now, which is needed for Windows apps (because you need to use their linker with special flags). The long-term goal would surely be to put this into libasync or a possible adaption for Phobos, but for now it should probably just there with a note that it's just a stub.
The libev driver has just received some improvements (timers and manual events now fully work) which makes it actually usable for TCP server kind of applications. I don't actually use it for something, but I'd also like to keep it as a comparison with the other divers.

The long-term goal would surely be to put this into libasync or a possible adaption for Phobos, but for now it should probably just there with a note that it's just a stub.

Or we could just remove it. Since it's probably not going to be implemented any time source, and with revision control you would be able to find the code anyway.

I don't know. I like that it gets CI tested at at least stays up to date. It doesn't really hurt as long as it's properly documented what to expect.

Ping ?

Ping ^2 ?

Pingitty-ping, this is quite trivial. If there is any wording you dislike let me know and I'll correct it.

Quite embarrassing that this slipped through the radar despite three "pings", sorry for that! I've cherry picked this now and resolved the conflicts.


Dev dependencies: Update cssnano

Get rid of the vulnerable "is-svg" package.

Codecov Report

Merging #47 (6c29a23) into master (f6261af) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #47   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           34        34
  Lines          422       422
  Branches        72        72
=========================================
  Hits           422       422

Continue to review full report at Codecov.

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


Refactor RequestedAuthnContext

following this https://github.com/IdentityPython/pysaml2/pull/807
we'll wait for the next release of pysaml2 to refactor by our side this feature, that actually is based on this
https://github.com/IdentityPython/djangosaml2/pull/289

Closed by
https://github.com/IdentityPython/djangosaml2/releases/tag/v1.3.5


Update Sci2 Dependencies

Sci2's dependencies are old and not been updated since 2011. Update the dependencies required for Sci2 to use as recent of version as practical.
This does not include updating algorithms.
This task does not include moving CIShell Algorithms to their own process space.
This task will be time-boxed at 2 days. We will review where its at after that to make a determination of whether to continue trying to upgrade or use whatever versions we were able to make work.

We will not upgrade sci2 RCP/SWT/etc dependencies past 3.X as 4.X will require a significant rewrite.


[Bug] False positive in Special Edition

Which Guide
Radarr: Special Edition
Describe the Error in the Guide
The.Final.Cut.2004.1080p.AMZ.WEB-DL.DD+5.1.x264-NOGROUP gets a false positive on Special Edition
Expected behavior
Not to be labeled as Special Edition since The Final Cut it's the name of the movie.
Screenshots

Not a guide issue.
https://github.com/Radarr/Radarr/issues/7004


Is it only show  rtmp outbound(not m3u8)?

Hi,
It doen;t count m3u8 format(hls) outbound traffic.

Hi @gogomir2 ,
yes the hls traffic not included only for rtmp , you can do that by monitoring your network inside the server and push data back to dashboard .

Is there any chance to fix this?

I'd also love to see an implementation of this.

It will be great to see an implementation of track users for hls-M3u8 and M4v/M4a dash.

any updates for this ?
Maybe just some examples so we can experiment with it ?


dSYMs contain obfuscated symbols in the symbol table section when --obfuscate flag is on for iOS build

Summary
When build iOS app with --obfuscate --split-debug-info flag on, App.framework.dSYM contains obfuscated symbols in the symbol table. For the symbolication tools such as breakpad, since it reads from DWARF so there is no problem. But there are other tools read from this symbol table which will results in returning obfuscated stack frame symbolication.
Reproduction steps

Build the app with flutter build ios --release --obfuscate --split-debug-info=<FILE_PATH> and flutter build ios --release --split-debug-info=<FILE_PATH> respectively. Get the App.framework.dSYM file for each build.

If you compare their DWARFs there are no major differences between these two dSYMs.
You can dump the DWARF information by doing:
$ dwarfdump App.framework.dSYM/Contents/Resources/DWARF/App

But if you checking the symbol table by doing:
$ dsymutil --symtab App.framework.dSYM/Contents/Resources/DWARF/App

The obfuscated dSYM contains obfuscated symbols which looks like this:

Expected
The symbol table should contains deobfuscated symbols even when --obfuscate flag on. We are also interested the intention or reason for the existing behaviour.

Thanks for the report @themiswang
Can you take a look at this issue and underlying comments and see if it helps in your case further ?

Thanks for the feedback. I am going ahead and keep this issue open for team's insights on query raised above and actual and expected behavior reported.

Expected
The symbol table should contains deobfuscated symbols even when --obfuscate flag on. We are also interested the intention or reason for the existing behaviour.

/cc @jmagman

Apologies for the delay, we don't need an internal bug.

The symbol table should contains deobfuscated symbols even when --obfuscate flag on.

This code was recently changed with https://github.com/flutter/flutter/pull/101586 and https://github.com/flutter/flutter/pull/111264.  I believe @mkustermann looked at the former.
@christopherfujino @vashworth might be worth following up with the dart team about what the intended behavior of --obfuscate would be on the dSYM.  @jonahwilliams may know off the top of his head too.
cc @vaind

Hmm, that's interesting, I'm pretty I guess it worked fine when integrated into Sentry because (I assume), the symbolication there is using dwarf names.
Also, I'm afraid I don't know what's the "right" approach (if there's any) for what should be in the symtab.
Additionally, if you look at how this is currently implemented, it's using dsymutil to extract dSYM from a compiled binary before stripping it - maybe there're flags to dsymutil to make it update the symbol table you see dumped from dsymutil --symtab?
https://github.com/flutter/flutter/blob/8ec5001ac2614e5dcc3eac8242896bfc7ea4e5a5/packages/flutter_tools/lib/src/base/build.dart#L315-L330

Hey @vaind,
I did more research on this. When --obfuscate build option is on, before build the binary, I assume there is a process of obfuscate symbols, that's probably the reason why in the elf symbol table we see this all obfuscated symbols. For native iOS, how Swift deal with obfuscation is they will mangle the function name to some human unreadable format, but there is function provide to demangle the symbol. Wonder how obfuscation works on dart and does it has the similar strategy for de-obfuscate the symbols.
Attach a sample for native iOS how Swift symbol looks like:

Apologies for late reply.
Enabling obfuscation in Dart will obfuscate class names and function names. This affects various things - not just stack traces. For example it also affects <obj>.runtimeType.toString(). That means even if a binary is stripped, there are symbols remaining in the stripped AOT snapshot that have to be obfuscated iff --obfuscate is enabled.
Due to this we obfuscate class/function names early on in our AOT compiler. Anything that comes later will use those obfuscated names. When emitting DWARF in the backend we explicitly map obfuscated symbols back to the original.
=> We could change the backend emitting the static symbol table to do the same.
For flutter specifically it seems for

iOS/macOS: Flutter builds targeting Apple will tell the AOT compiler to emit the application as an assembly file. This assembly will already today contain unobfuscated DWARF (if --split-debug-info is used). Flutter tools will then compile the assembly to a shared library, extract symbols and DWARF to a .dSYM and strip the binary (by-default).

Android/Rest: Flutter builds targeting non-Apple will tell the AOT compiler to emit the application as an ELF file. Flutter will then (by-default) tell our AOT compiler to strip the resulting ELF file, so we won't emit DWARF in it (we should also double-check we don't emit static symbols in this case).

Since stripping is enabled by default on both (for Apple platform the flutter tools does stripping, for non-Apple platform the AOT compiler emitting ELF does stripping) this will only cause an issue if someone explicitly uses --obfuscate --extra-gen-snapshot-options=--no-strip and then deploys such an app (which would have unobfuscated static symbols). That's maybe not a real concern as users intentionally leave symbol information in the resulting binary.
/cc @sstrickl Could you confirm the above is correct? Could we go ahead and make the static symbols unobfuscated (and ensure we omit static symbols if --strip is enabled - just as in dwarf)?

/cc @sstrickl Could you confirm the above is correct? Could we go ahead and make the static symbols unobfuscated (and ensure we omit static symbols if --strip is enabled - just as in dwarf)?

Yes, I believe we should be able to have the static symbol generation code use unobfuscated strings, we'll just need to feed the appropriate information we already generate for the DWARF writer into the BlobImageWriters/AssemblyImageWriters so they can use that to deobfuscate symbol names before writing. Unless I'm forgetting something from the last time I touched that code, should be fairly straightforward.

Working on this now.

@sstrickl Consider verifying that flutter build --release doesn't leave any unstripped static symbols in the resulting ELF/MachO files? Then we can close this issue?

Hey @sstrickl,
Also let me know if there is a need to update dart or flutter version in order to reflect the change. I'll need to working on other dependency change and announce with our customers as well. Thank you!

I believe this has been rolled all the way up to flutter/flutter now.
Closing this issue.

Also let me know if there is a need to update dart or flutter version in order to reflect the change.

@themiswang Could you verify this works as expected for you in flutter master channel?

Hey @mkustermann,
Sorry I am not a member on Flutter team so I do need a stable version for testing which can be downloaded from get start. Let me know if you know how to do it or the folks who familiar with the process so I can schedule some time for verification.

Never mind, find the instruction: https://github.com/flutter/flutter/wiki/Flutter-build-release-channels#how-to-change-channels. Confirm it works now on main, thank you folks!


Replacing jsonpath with jq and adding 'expressionLang' top level property

Signed-off-by: Tihomir Surdilovic<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please specify parts this PR updates:

[x] Specification
[x] Schema
[x] Examples
[x] Extensions
[x] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[ ] Other

What this PR does / why we need it:

replaces jsonpath with jq
updates expressions syntax
Special notes for reviewers:

Additional information (if needed):
Fixes #216

@jorgenj @ricardozanini
take a look at https://github.com/serverlessworkflow/specification/issues/250
enforcing a single expression lang seems afterall not feasible for real world use. i have added the needed updates
to this pr (added expressionLang) property back where users can define a unique identifier of the expression language
used in workflow expressions (default is "jq").

Adding such expression type attribute weren't we opening the gates of hell? Having an extension to handle this kind of scenario wouldn't be better? So users could import the extension they need and at the same time reuse the same workflow between runtimes.

not sure extension is needed as all expressions are inside workflow definition. we had this before and removed it to try to enforce portability as expression syntax has affects on portability..but it seems that pushing a single language only does significantly lower the adoption possibilities, as many runtimes have hard requirements to use a specific syntax for expressiosn which is not our "default" one.

rebased

need to rebase :)

will go ahead and merge - @jorgenj if you find any issues w/ this please raise them and i'll fix asap


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 3f5262c, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 9285 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in e2786c7.


room ticket cli edit

also clean up all Guest fields on transfer

kewl lewks good to me hashtag send it! <3


add docker processes table

It would be possible to use docker ps and docker top with
--format, but that's not compatible with docker 1.6, e.g. ubuntu 14.04 LTS.

Awesome Pull-request. Thank you, @djtm.

Very welcome! Thank you for the everything else, @afaqurk! :)


rotarycontroller code

Paul -- could you ensure rotarycontroller.ino (for teensy-midi-encoder-box) is correct and current? It won't verify/compile without a boatload of errors using the current teensyarduino app. Further, there seems to be a lot of superfluous code in the file. Do you perchance have a slimmed down or updated version? Cheers, John

You need to set your USB type - Tools > USB Type > MIDI.
After setting that it compiles fine for me with one warning:
In file included from /private/var/folders/qb/qf9kj1px6sv90zv0_lt646d80000gp/T/AppTranslocation/A6217479-27C4-4B32-9057-BF047F700A5D/d/Teensyduino.app/Contents/Java/hardware/teensy/avr/cores/teensy/usb.c:10:0:
/private/var/folders/qb/qf9kj1px6sv90zv0_lt646d80000gp/T/AppTranslocation/A6217479-27C4-4B32-9057-BF047F700A5D/d/Teensyduino.app/Contents/Java/hardware/teensy/avr/cores/teensy/../usb_midi/usb.c:125:50: warning: missing terminating ' character
  but when I add them, MIDI breaks on Linux (haven't tried Mac and

Thank you. That fixed everything. FYI, I'm on Mac OSX Catalina running latest Teensyduino and your code compiles and runs without error. Cheers!!


is this project dead?

Lots of recent issues, no commits in 4 months.

Not at all, I try to address all recent issues that are fixable by me, some others are environment issues or issues that should be solved in other repos
As for the commits, There is a major refactor coming but waiting for some loose ends to be handled

ahh ok cool. I'll test it out when its stable.


Get Gas command: one year timeout message

A number of users have been reporting receiving an error message from Kessing, when using the /get-gas command, that they need to wait for their timeout period to end in a year.  See image below for one example:

Hi there Soundboy,
This is not an error. The /get-gas is meant to help users out on the initial onboarding. Gas for tipping should be provided by the users themselves. I know more people were confused about the message, so it will be updated to a more descriptive response today.


💡[FEATURE] Align the footers of all pages with the main page

Is your feature request related to a problem? Please describe.
It is important to have uniformity in website
Describe the solution you'd like
Keep uniform features in the entire website
Additional context
GSSOC'24

Please assign this issue to me @akshitagupta15june


Allow to use KafkaListenerContainerFactory with custom message converter for batch and record listeners

Expected Behavior
The spring-kafka documentation mentions:

Starting with version 2.8, you can override the factory’s batchListener property using the batch property on the @KafkaListener annotation. This, together with the changes to Container Error Handlers allows the same factory to be used for both record and batch listeners.

This should also work when a custom MessageConverter is defined on the factory.
Current Behavior
For batch listeners, the message converter must be wrapped in a BatchMessagingMessageConverter. Otherwise, the message converter will not be used correctly and the wrong type will be supplied to the batch listener.
Context
We encapsulate spring-kafka into a library that preconfigures the factory as a bean in our setup. This library is then used by many services.
Another option would be to create a separate factory for batch listeners. With this, I am afraid that someone might use @KafkaListener(batch="true") as described in the official documentation but without supplying the correct library, which only works partly.
My current workaround looks like this, but I do not like it as it depends on how spring-kafka internally sets up its configuration, so it might break in future updates:
factory.setContainerCustomizer(container -> {
    var messageListener = container.getContainerProperties().getMessageListener();
    if (messageListener instanceof FilteringBatchMessageListenerAdapter) {
        var meessageListenerDelegate =
                ((FilteringBatchMessageListenerAdapter<?, ?>) messageListener).getDelegate();
        if (meessageListenerDelegate instanceof BatchMessagingMessageListenerAdapter) {
            ((BatchMessagingMessageListenerAdapter<?, ?>) meessageListenerDelegate).setBatchMessageConverter(
                    new BatchMessagingMessageConverter(messageConverter));
        }
    }
});

See also this StackOverflow question.

Thanks! That was fast :rocket:


Please support a running WASM version for testing

I am surprised: The Apple message API is realy open to other operating systems and even for the Web? (May be you could mention in the readme, it is a messenger (specific) for Apple messages.) The WebAssembly version will run on any other OS, will it? Could you support a running WASM version to test your solution?

Hey, as a clarification, this is just a design sample, so it does not provide actual functionality. However, it could be extended and built upon to create such app :-) .


Cannot download a specific version of biber

Hi Manuel,
first of all, I'd like to preface this issue by thanking you for your OSS contribution ❤. Your Action has been instrumental in significantly improving my CI build times.
Unfortunately, I ran into some problems with regards to Biber. The following log output was generated inside act btw:
[release-pls/build] ⭐  Run Setup Tectonic
INFO[0001]   ☁  git clone 'https://github.com/wtfjoke/setup-tectonic' # ref=v1
[release-pls/build]   🐳  docker cp src=/Users/pr1metine/.cache/act/wtfjoke-setup-tectonic@v1/ dst=/var/run/act/actions/wtfjoke-setup-tectonic@v1/
[release-pls/build]   🐳  docker exec cmd=[mkdir -p /var/run/act/actions/wtfjoke-setup-tectonic@v1/] user= workdir=
[release-pls/build]   🐳  docker exec cmd=[node<EMAIL_ADDRESS>user= workdir=
[release-pls/build]   💬  ::debug::Finding releases for Tectonic version latest
[release-pls/build]   💬  ::debug::Getting build for Tectonic version 0.8.0: linux
[release-pls/build]   💬  ::debug::Release: {"id":51168607,"name":"tectonic 0.8.0","version":"0.8.0","tagName":"tectonic@0.8.0","assets":[{"name":"tectonic-0.8.0-arm-unknown-linux-musleabihf.tar.gz","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-arm-unknown-linux-musleabihf.tar.gz"},{"name":"tectonic-0.8.0-i686-unknown-linux-gnu.tar.gz","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-i686-unknown-linux-gnu.tar.gz"},{"name":"tectonic-0.8.0-mips-unknown-linux-gnu.tar.gz","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-mips-unknown-linux-gnu.tar.gz"},{"name":"tectonic-0.8.0-x86_64-apple-darwin.tar.gz","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64-apple-darwin.tar.gz"},{"name":"tectonic-0.8.0-x86_64-pc-windows-gnu.zip","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64-pc-windows-gnu.zip"},{"name":"tectonic-0.8.0-x86_64-pc-windows-msvc.zip","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64-pc-windows-msvc.zip"},{"name":"tectonic-0.8.0-x86_64-unknown-linux-gnu.tar.gz","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64-unknown-linux-gnu.tar.gz"},{"name":"tectonic-0.8.0-x86_64-unknown-linux-musl.tar.gz","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64-unknown-linux-musl.tar.gz"},{"name":"tectonic-0.8.0-x86_64.AppImage","url":"https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64.AppImage"}]}
[release-pls/build]   💬  ::debug::Downloading Tectonic from https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64.AppImage
[release-pls/build]   💬  ::debug::Downloading https://github.com/tectonic-typesetting/tectonic/releases/download/tectonic%25400.8.0/tectonic-0.8.0-x86_64.AppImage
[release-pls/build]   💬  ::debug::Destination /tmp/c6807eda-b589-4909-bdbd-6553215dfe2d
[release-pls/build]   💬  ::debug::download complete
[release-pls/build]   💬  ::debug::Extracting Tectonic
[release-pls/build]   💬  ::debug::Moved Tectonic from /tmp/c6807eda-b589-4909-bdbd-6553215dfe2d to /tmp/1eab2310-8440-451f-841c-70c94e842072/tectonic
[release-pls/build]   💬  ::debug::Tectonic path is /tmp/1eab2310-8440-451f-841c-70c94e842072
[release-pls/build]   💬  ::debug::Biber version: 2.16
[release-pls/build]   💬  ::debug::Downloading Biber from https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/current/binaries/Linux/biber-linux_x86_64.tar.gz/download
[release-pls/build]   💬  ::debug::Downloading https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/current/binaries/Linux/biber-linux_x86_64.tar.gz/download
[release-pls/build]   💬  ::debug::Destination /tmp/d192df98-3c57-49fb-92b7-0cb681ee6230
[release-pls/build]   💬  ::debug::download complete
[release-pls/build]   💬  ::debug::Extracting Biber
[release-pls/build]   💬  ::debug::Checking tar --version
[release-pls/build]   💬  ::debug::tar (GNU tar) 1.30%0ACopyright (C) 2017 Free Software Foundation, Inc.%0ALicense GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.%0AThis is free software: you are free to change and redistribute it.%0AThere is NO WARRANTY, to the extent permitted by law.%0A%0AWritten by John Gilmore and Jay Fenlason.
| [command]/usr/bin/tar xz --warning=no-unknown-keyword --overwrite -C /tmp/369bbafa-5b3c-4726-bb2e-c2bf905cbfcd -f /tmp/d192df98-3c57-49fb-92b7-0cb681ee6230
[release-pls/build]   💬  ::debug::Biber path is /tmp/369bbafa-5b3c-4726-bb2e-c2bf905cbfcd
[release-pls/build]   ✅  Success - Setup Tectonic

When specifying a biber-version, your GitHub Action always downloads the current version regardless of the specified biber-version:
[release-pls/build]   💬  ::debug::Biber version: 2.16
[release-pls/build]   💬  ::debug::Downloading Biber from https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/current/binaries/Linux/biber-linux_x86_64.tar.gz/download
[release-pls/build]   💬  ::debug::Downloading https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/current/binaries/Linux/biber-linux_x86_64.tar.gz/download

That's because Biber does not strictly follow the Semantic Versioning conventions. Thus, the specified biber-version i. e. 2.16 is labelled invalid and defaults to current:
https://github.com/WtfJoke/setup-tectonic/blob/eb5e5c2ff6887545ae527012b424672b28fc34e0/src/biber.ts#L7-L8
Appending a patch version to biber-version i. e. 2.16.0 results in an error:
[release-pls/build]   💬  ::debug::Biber version: 2.16.0
[release-pls/build]   💬  ::debug::Downloading Biber from https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/2.16.0/binaries/Linux/biber-linux_x86_64.tar.gz/download
[release-pls/build]   💬  ::debug::Downloading https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/2.16.0/binaries/Linux/biber-linux_x86_64.tar.gz/download
[release-pls/build]   💬  ::debug::Destination /tmp/dd3d23c4-b1c0-40fc-a1dd-fc1fff58759b
[release-pls/build]   💬  ::debug::Failed to download from "https://sourceforge.net/projects/biblatex-biber/files/biblatex-biber/2.16.0/binaries/Linux/biber-linux_x86_64.tar.gz/download". Code(404) Message(Not Found)
[release-pls/build]   ❗  ::error::Error: Unexpected HTTP response: 404
[release-pls/build]   ❗  ::error::Unexpected HTTP response: 404
[release-pls/build]   ❌  Failure - Setup Tectonic
Error: exit with `FAILURE`: 1

I should be able to fix this issue on my own. I am going to open a PR for this soon.

Hi Thanh

thanking you for your OSS contribution ❤. Your Action has been instrumental in significantly improving my CI build times.

Thank you for your words :) Glad to it helped speeding up your build times, that what I was aiming for :)
Thanks for the detailed

That's because Biber does not strictly follow the Semantic Versioning conventions. Thus, the specified biber-version i. e. 2.16 is labelled invalid and defaults to current:

Thanks for your detailed bug report and your proposed PR.

Will soon take a look at your PR

@pr1metine I just published the changes in v1 (aka https://github.com/WtfJoke/setup-tectonic/releases/tag/v1.1.8), so you should be able to use the 🐛 fix in your CI pipeline

Awesome 🤩. Tysm


Dapr runtime crashes on subscriber with pubsub component

In what area(s)?
/area runtime
What version of Dapr?

CLI version: 1.0.0-rc.4
Runtime version: 1.0.0-rc.3
pubsub provider: Azure Service Bus
Expected Behavior
I was hoping that my original payload would be given to the subscriber in a CE envelop auto-generated by dapr with the .data set. Also, upon completion i would expect the runtime to protect itself from that payload by handling it so that the service can still use dapr.
Actual Behavior
When the topic subscriber gets called, the CE object is not initialized and therefore has all members null. After that, regardless of the http response (200, 500, etc) that the subscriber sends back to dapr, it will crash the runtime.
panic: interface conversion: interface {} is nil, not string goroutine 180 [running]: github.com/dapr/dapr/pkg/runtime.(*DaprRuntime).publishMessageHTTP(0xc0000ff440, 0xc00020ef30, 0x3c8b240, 0xc0005e0360)         D:/a/dapr/dapr/pkg/runtime/runtime.go:1124 +0x17ed github.com/dapr/dapr/pkg/runtime.(*DaprRuntime).beginPubSub.func1(0xc00020ef30, 0x3e96fac, 0x30)         D:/a/dapr/dapr/pkg/runtime/runtime.go:443 +0xba github.com/dapr/components-contrib/pubsub/azure/servicebus.(*subscription).getHandlerFunc.func1(0x43c14c0, 0xc000f7a000, 0xc0005b61e0, 0x0, 0x0)         C:/Users/runneradmin/go/pkg/mod/github.com/dapr/components-contrib@v1.0.0-rc4/pubsub/azure/servicebus/subscription.go:122 +0x1d8 github.com/dapr/components-contrib/pubsub/azure/servicebus.(*subscription).asyncWrapper.func1.1(0xc000f6b560, 0xc0005b61e0, 0x43c14c0, 0xc000f7a000, 0xc000f5bda0)                 C:/Users/runneradmin/go/pkg/mod/github.com/dapr/components-contrib@v1.0.0-rc4/pubsub/azure/servicebus/subscription.go:169 +0xfe created by github.com/dapr/components-contrib/pubsub/azure/servicebus.(*subscription).asyncWrapper.func1         C:/Users/runneradmin/go/pkg/mod/github.com/dapr/components-contrib@v1.0.0-rc4/pubsub/azure/servicebus/subscription.go:147 +0x6c
Steps to Reproduce the Problem

Have a topic subscriber that just returns 200 (Ok)
Publish a  non-cloud event to a topic on Azure Service Bus.
Runtime will crash when receiving callback after subscriber controller code has been completed.

Release Note
RELEASE NOTE: FIX Bug in runtime.

Is there a work around for this issue. I am seeing the same error 1.0.1 version as well.

Is this similar to this issue?
https://github.com/dapr/components-contrib/issues/507

@lynn-orrell  Yes, the subscriber is receiving non-cloud events from external MQTT broker. After receiving few events a runtime crash is observed.

PSA: The current issues related to non-CE message support have been marked for attention in the 6 month roadmap https://github.com/dapr/dapr/issues/2882

This is now fixed in Dapr 1.2: https://docs.dapr.io/developing-applications/building-blocks/pubsub/pubsub-raw/

@yaron2 : This issue is still reproducible on 1.2.
The Dapr Sidecar still goes into a panic state if we are expecting a cloud event but a non CE is received.
`panic: interface conversion: interface {} is nil, not string
goroutine 3137 [running]:
github.com/dapr/dapr/pkg/runtime.(*DaprRuntime).publishMessageHTTP(0xc0004bfd40, 0x3d9b968, 0xc000060038, 0xc000d38280, 0x38e3201, 0xc000d38280)
/home/runner/work/dapr/dapr/pkg/runtime/runtime.go:1238 +0x15f0
github.com/dapr/dapr/pkg/runtime.(*DaprRuntime).beginPubSub.func1(0x3d9b968, 0xc000060038, 0xc0004d0240, 0x0, 0x0)
/home/runner/work/dapr/dapr/pkg/runtime/runtime.go:487 +0x39d
github.com/dapr/components-contrib/pubsub/azure/eventhubs.(*AzureEventHubs).Subscribe.func1(0x3d9b9d8, 0xc0004d0210, 0xc000c30190, 0x0, 0x0)
/home/runner/go/pkg/mod/github.com/dapr/components-contrib@v1.2.0/pubsub/azure/eventhubs/eventhubs.go:144 +0xb6
github.com/Azure/azure-event-hubs-go/eph.(*EventProcessorHost).compositeHandlers.func1.1(0xc0004f11f0, 0xc000c30190, 0xc000efc160, 0xc000b9e000)
/home/runner/go/pkg/mod/github.com/!azure/azure-event-hubs-go@v1.3.1/eph/eph.go:418 +0x4a
created by github.com/Azure/azure-event-hubs-go/eph.(*EventProcessorHost).compositeHandlers.func1
/home/runner/go/pkg/mod/github.com/!azure/azure-event-hubs-go@v1.3.1/eph/eph.go:417 +0x245`

@yaron2 : Is there a way in Dapr 1.2 through which we handle unexpected non CE event while processing CloudEvents?
We tried Dapr 1.2 with metdata.rawpayload as value true while subscribing. We are using .NET 5 Dapr SDK.  Dapr 1.1 used to automatically unwrap the payload to the CloudEvent object in .NET.
But with the 1.2 release, converts the payload into a byte array and wraps it inside another cloud event object thus breaking our existing code flow.


Togglable Line Colors

I only want to know RED or YELLOW light levels, and the SECONDARY is in the way, would be awesome to be able to toggle them on or off somehow. If there already is a way to do this, please don't hesitate to guide me in the right direction

Found it in the settings, "Secondary Light Level"(slider) set it to "off" , didn't notice it. Might be good to add it to the documentation since it says (1.18 only) to (1.18 only, other versions can turn it off in mod config via slider)


unable to configure.

Hi,
I've just install dropbox-sync on hassio.io 0.65 and got this error while saving the configuration in the Hassio dashboard.
not a valid value for dictionary value @ data['options']. Got {'oauth_access_token': 'xxxxxxxxxxxxxxxx', 'output': '', 'keep_last': ''}
(I've removed the dropbox token for security reasons)
Can you help ?
Thanks

Can you tell me what version of the add-on you have installed?

Same error here
V 1.1.1
Thanks.

Adding a number to Keep_last clears the error and allows it to launch

In version 1.1.1, I made the keep_last parameter optional. So you can either set it to a number, or remove it entirely if you don’t want to use the keep_last functionality. Either way should remove the error.

In the next version, I probably won’t include the keep_last option in the default config, so this issue won’t occur “by default” unless the necessary changes are made.

For whatever reason, if  I try to remove the Keep_last option, it won't
save and start properly
https://mailtrack.io/ Sent with Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality&
On Sun, Mar 11, 2018 at 9:52 PM, Daniel Welch<EMAIL_ADDRESS>wrote:

In the next version, I probably won’t include the keep_last option in the
default config, so this issue won’t occur “by default” unless the necessary
changes are made.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/danielwelch/hassio-dropbox-sync/issues/1#issuecomment-372172340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYHs3ScMnwHX3ngayAsTVVO5Jdkqv2Ueks5tddTsgaJpZM4Slz3d
.

version 1.1.0 and also version 1.1.1.
Same error in both versions.
If you remove the last parameter "keep_last" you also get the same error.

@nmsoares @macstibs
Hopefully this issue is resolved with the release of v1.1.2. Please try it out and let me know.
Sorry for the problem, the hass.io dev docs were a little unclear to me around optional parameter definitions so there's a little trial and error here, but v1.1.2 is working in my local testing both with the keep_last parameter set as well as with the parameter omitted entirely.

Closing for now, reopen if problem persists.


Page.getLayoutMetrics

Hi.
I tried to take full-size screenshot of a page with this library. But noticed that the Page.getLayoutMetrics feature is not implemented.
So I was hoping a little help would be welcome. #43.

@kaero598  In addition, what's about having an option for automatically take full size screenshots?

@gsouf That would be useful. I was thinking of a new fullsize option for screenshot() method but I'm not sure how that would behave when clip options is also set.

You can upgrade to version 0.4.0 and do fullpage screenshot:
$page->screenshot([
         'clip' => $page->getFullPageClip()
     ])
      ->saveToFile('/tmp/image.jpg');

Thanks a lot.


[example] Fix command line flag

Hi @Maks3w, are you able to sign the CLA here?

Too much waste of time just for a little fix


Fix compilation on ARM64 macOS

getmntinfo$INODE64 fails with a link error, but getmntinfo works.
I think this closes #92.

Thanks!


type inference of return value in async fn

async fn get_accounts() -> Result<Vec<String>, ()> {
    let accounts = Vec::<String>::new().iter().map(|x| x.clone()).collect();
    //  ^ Vec<String> but r-a infers {unknown}
    Ok(accounts)
}

This works without async.
rust-analyzer: 5a1fd0576 2021-05-26
rustc 1.54.0-nightly (3e99439f4 2021-05-17)

@flodiebold I am currently looking into this. It seems like we get the fully desugared impl trait type (impl Future<Output = ...>) here:
https://github.com/rust-analyzer/rust-analyzer/blob/7869b01b702d1f12acb03ac131b6eb90ad82e9bb/crates/hir_ty/src/infer.rs#L561
It doesn't seem right that we use that fully desugared type for further inference. It would make more sense to use the "actual" return type (Output). I've tried it locally and it seems to work out. Do you think that this is the right fix? Or is there a deeper problem somewhere?

Yeah, I think we can't get around some kind of hacky solution where the 'inner' return type is different from the outer one, since we can't do the full generator desugaring right now. Probably keeping track of the async return type in a separate field in the function data would be the right move for now.

Probably keeping track of the async return type [...]

Are you talking about the fully desugared type (impl Future)? Or the Output type?

The latter, probably.


Remove workaround for a fixed 1.9 issue

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b2e306f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1272   +/-   ##
=========================================
  Coverage          ?   99.91%
=========================================
  Files             ?       33
  Lines             ?     2471
  Branches          ?      102
=========================================
  Hits              ?     2469
  Misses            ?        1
  Partials          ?        1

Impacted Files
Coverage Δ

src/dcos_e2e/backends/_aws/__init__.py
100% <ø> (ø)

Continue to review full report at Codecov.

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


AccessViolationException

When creating a new Background App (IoT Core) as a test app, I get a System.AccessViolationException in IoTivityDotNet\Service.cs at line 106 ('Attempted to read or write protected memory. This is often an indication that other memory is corrupt.').
Update: It turns out that .Net Desktop app broke as well - there the AccessViolationException is thrown at line 33
(using the latest binaries from #4). @TheSuperShoe have you noticed this?

It turns out that UWP app broke as well - there the AccessViolationException is thrown at line 33
(using the latest binaries from #4). @TheSuperShoe have you noticed this?

The strange thing is that the TestApp.UWP sample still works, and that the TestApp.NET45 stopped working (although it worked before).

Never mind. I deleted the repo, cloned it again and now it works again. Don't know why.

For a while I had a similar error with the TestApp.NET45 sample (there the AccessViolationException was thrown at line 33 but that solved itself when I deleted the local checkout and cloned the repo from #4 again.

It turns out the AccessViolationException was thrown when I put a pre-generated oic_svr_db.dat from https://github.com/iotivity/iotivity/tree/master/resource/csdk/stack/samples/linux/secure in the folder, because I wanted to experiment with the security settings.
However, I have not done this for the Background App, so there something else must be wrong. Also, the exception is thrown on another call there.


Google provider

I am trying to add Google provider, but issue is that Google doesn't actually redirect to redirect_url, Normally in all other providers we use webViewhouldStartLoadWithRequest, instead of that we have to use webViewDidFinishLoad. Any suggestions regarding how to implement this without ruining the simplicity of the code ??

Apologies for the way late response on this. #84 fixes this.


"Link to alert" no longer linking to search

Describe the bug
About a month ago, the Show results in Splunk link in slack no longer links to a search, instead, it is opening a loadjob
To Reproduce
Steps to reproduce the behavior:

Edit the 'search alert'
Under Attachment choose "Link to alert"
In slack message, click Show results in Splunk

Expected behavior
Opens up the search term and shows result
Screenshots

Splunk Environment:

Splunk Version: 8.1.0
OS: Linux
Cloud: No

Client Environment: (if it's a UI issue)

Browser Type: Chrome
OS: MacOS

@ziegfried Is this to do with a change from savedsearch to loadjob?
Is there a way I can change this back


Add complex64 support for tf.abs().

We hide this behind tf.abs.
y = sqrt(real ^ 2 + imag ^ 2)

This change is

There's also a length() function in GLSL ES 1.00. It might be slightly faster and also avoid some fringe cases of float32 underflow ( float32( (1e-23)² ) = 0 ).

That's a great point @DirkToewe. Want to send a PR?

Here You go


fix select2 ajax filter clearing

It wasn't clearing selected choice when Remove all filters clicked, because of the wrong selector.
To reproduce:

Search and select some option
Click "Remove all filters"
The filter is not activated, but the last choice is still selected. Search and select the same choice, the filter will not be activated. Because the choice is the same.

$("li[filter-name={{ $filter->name }}] .select2") doesn't select anything. Changed selector to same selector as initializing selector.

Thank you @alashow . Just tested it and merged it into the dev branch. It will be available to everyone this week. Cheers and thank you for using and improving Backpack!


RFE: Prepare VP from 'request' -> 'submit' flow

As a holder of verifiable credentials, I should be able to respond to a request by submitting a verifiable presentation, with only fields asked in request (selective disclosure), from the asked Issuers.

As demonstrated in the demo-vs.js, a new schema and a stream are getting created before creating a verifiable credential.
For this endpoint, what should be the flow?

Getting only schema and space identifiers in the request body and getting their corresponding entities from DB to form a VC.
Getting whole schema properties in the request body and creating a new schema.

And the vc holder's address should be in the request body as well right?

The flow is something like below:

Schema is anchored by policy makers. It is agreed upon by everyone 'issuing' VCs.
Space is created by orgs/entities about to issue VC as per their convenience (about how they group). Can be done by entity admin.
The issuer of VC would use the above anchored reference (only space and schema identifiers) while issuing the VC.

Now, coming to this issue:
the assumption is, the 'holder' entity already has the VC json with them, and is preparing a VP from VC. The flow is mostly important for verifier to holder communcations.


Add a special page to demo various panels with streamfields

Closing in favour of #380, which incorporates all the scenarios here with the exception of "StreamField inside InlinePanel".


The zoom label is impossible to see with certain editor themes

What Happened
Using the "Light" editor theme, the zoom label is almost impossible to see:

How to Reproduce

In Godot's Editor Settings, switch to a theme with a light background colour, such as the "Light" theme preset.
In the block code editor, look for the zoom label in the bottom right corner of the screen.

Block Coding Plugin Version
No response
Godot Engine Version
No response
Operating System
No response
Logs or command-line output
No response
Anything else?
No response

Fixed in main by the PR above. Will be in next release.


No redirect method set jwt

Sets a cookie on jwt creation that's accepted by the client (browser).

@krantzinator Thanks so much! I'm going to merge anyways, need to keep working on this.