merge_knownexploited is expected to be a procedure using PostgreSQL

Describe the bug
While running version 8.0.0 using PostgreSQL the maven plugin fails due to merge_knownexploited being a function instead of a procedure. This seems to be a bug for PostgreSQL only because merge_knownexploited is declared as a procedure for Oracle, MySQL and others.
Version of dependency-check used
The problem occurs using version 8.0.0 of the maven plugin.
Log file
[ERROR] Failed to execute goal org.owasp:dependency-check-maven:8.0.0:check (default-cli) on project product-parent: Fatal exception(s) analyzing product-parent: One or more exceptions occurred during analysis:
[ERROR] 	UpdateException: java.sql.BatchUpdateException: Batch entry 0 CALL merge_knownexploited('CVE-2021-27104','Accellion','FTA','Accellion FTA OS Command Injection Vulnerability','2021-11-03','Accellion FTA 9_12_370 and earlier is affected by OS command execution via a crafted POST request to various admin endpoints.','Apply updates per vendor instructions.','2021-11-17',NULL) was aborted: ERROR: merge_knownexploited(character varying, character varying, character varying, character varying, character varying, character varying, character varying, character varying, character varying) is not a procedure

To Reproduce
Steps to reproduce the behavior:

Create an empty PostgreSQL database.
Add missing to initialize_postgres.sql inside of merge_knownexploited, see additional context, and execute on newly created database.
Run dependency check maven goal.

Expected behavior
The plugin successfully executes updates and checks using PostgreSQL.
Additional context
initialize_postgres.sql also seems to be missing a semicolon inside merge_knownexploited which prevents the migration file from succeeding initially.

Can you try the updated initialization script: https://github.com/jeremylong/DependencyCheck/blob/0961742cc4d69f291b8a543d56b8b47aa81d300a/core/src/main/resources/data/initialize_postgres.sql

I recreated the database wir the updated script but the problem still occures:
[ERROR] 	UpdateException: java.sql.BatchUpdateException: Batch entry 0 CALL merge_knownexploited('CVE-2021-27104','Accellion','FTA','Accellion FTA OS Command Injection Vulnerability','2021-11-03','Accellion FTA 9_12_370 and earlier is affected by OS command execution via a crafted POST request to various admin endpoints.','Apply updates per vendor instructions.','2021-11-17',NULL) was aborted: ERROR: merge_knownexploited(character varying, character varying, character varying, character varying, character varying, character varying, character varying, character varying, character varying) is not a procedure
[ERROR]   Hinweis: To call a function, use SELECT.

My guess is that https://github.com/jeremylong/DependencyCheck/blob/0961742cc4d69f291b8a543d56b8b47aa81d300a/core/src/main/resources/data/dbStatements_postgresql.properties#L21 should be SELECT instead of CALL.

@andfx please try this solution: https://github.com/jeremylong/DependencyCheck/pull/5317
File: https://github.com/jeremylong/DependencyCheck/blob/8b3ecb0ed506bee9fe75a89b43da86f4290815a3/core/src/main/resources/data/initialize_postgres.sql


[Documentation]

Here's what we need to document (in the official docs page): (Please add anything you think of).

[x] Recursive bindings, simultaneous bindings.
[x] Imperative statements if/while/for.
[x] Very basic syntactic features.
[x] More advanced features (named arguments, modules, signatures).
[x] All the very advanced features Objects.
[ ] Describe likelihood of change for each of the three (the later are definitely more likely to change rapidly).
[ ] How to upgrade versions.
[x] How to build a sample project (CommonML is a good "playground" to try our Reason in).
[x] Emacs/Vim setup.
[ ] Using rebuild in existing projects.

Done done done


HAWQ-1333. Change access mode of source files for HAWQ.

@radarwave  @linwen feel free to review this pr, thank you so much.

+1

+1

Good job, please have pr delivered asap. Thanks.

Good job ! please have it delivered asap. Thanks.

+1


Replace mirror link to developer.redhat.com

As of now developer.redhat.com link need to require cookie so
we create a cookieJar and pass it to the http.Client

I'd hold this until we get confirmation we don't have a choice and cookies are required :)

/hold

/retest

/unhold


#162 moved ionicons from bower dependency to npm

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

Duplicate of #165 ?

Thanks @ESadouski but unfortunately this is a dup of #165 as @GRoguelon has mentioned.


Setup Sphinx documentation

@SimonRit Here is a POC regarding automated online documentation.
This is far from being complete but it sets up the minimum infrastructure to automatically generate local and online documentation.
We could keep pushing code to this PR until we have a complete documentation gathering all the resources already available online.
I tried to replicate the wiki applications pages into the examples directory. This cannot be built nor tested with CMake but it makes doc updates easier.
Support for existing markdown files has been added. An example is given by including GettingStarted.md in the main index.rst file.
Support for external images has been added. They can be added to any directory. The documentation/Sphinx/ExternalData folder is a good place to store images that should be included in the doc but that don't belong to any example.
An example of the resulting doc should be available here.
We can setup a call to review and discuss this PR together, just let me know.

@SimonRit Images should now be fixed in the documentation.
I could keep the original approach:

Images can be added using "content-files" referencing the sha512 from data.kitware. (see examples/FDK)
Images are automatically downloaded when building the doc.
Images must be referenced using relative path when included in .rst files (see here)

We can schedule a call to discuss this again.

Thanks, it looks good. We now need to have an internal discussion to agree (or not) on this documentation format... and to write it.

PR updated, a preview of the generated doc is available here: https://lucasgandelrtk.readthedocs.io/en/latest/
A README file has been added to share instructions on how to extend the doc.
Note that the top level index.md file must be placed next to the conf.py file. Because we want the documentation files to be spread across the sources, both index.md and conf.py must be at the root of the RTK source tree.

This is great, I only have minor suggestions. I will split examples into "Code examples" and "Applications examples" with a top page explaining the difference but that's up to me to do it. Thanks @LucasGandel! Any preference between merging as is or taking over the PR to add more content?

Suggestions have been addressed. I think it is better to merge this now and setup the readthedocs build with your account. Once it is up and running, we can make changes to the doc in new MRs


Small chunk heuristics for data density graph

What
The data density graph now renders individual events if it is not prohibitively expensive.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

How I read the benchmark results is that it doesn't matter how the chunks are rendered, it scales with how many total events there are. As expected, unsorted data is slower to process. What I don't understand is why splitting chunks seems to do... nothing?


CORE-6169 JPA backing store performance tests

Summary
In order to make performance improvements to the uniqueness checker backing store (to be delivered by CORE-6171), we must first be able to quantify the performance of the backing store.
To facilitate this, a set of performance tests have been developed against the JPA backing store. These tests can be executed using the new performanceTest gradle command.
(More details TBA)
Testing
TBA

@driessamyn tagged you as a reviewer, as I think it's worth you reviewing the changes to the DB utils library. Basically, I've exposed the showSql parameter to enable this to be switched off, as I didn't want Hibernates very verbose logging affecting the performance of these tests. I've set the default to true, to ensure the existing behavior is retained unless explicitly changed  by a test.

I'm not a fan of adding non-functional testing like this to this repo. It's very hard to get any meaningful data out of it considering the environment it runs in, and we have a setup that is designed to load and performance test.
Maybe it warrants a group discussion?
CC @davidcurrie

@driessamyn happy to have a chat, as long as we can do it in the next day or two as we do have an immediate requirement for this. I suspect there may be a misunderstanding as to exactly what the use-case for these tests are, but happy to hear what the broader plans are and whether that would fulfil our requirements


Revoke and regenerate an API key (bug 1209224)

Why do we only allow one active API key? Is this just an intermediate step to some more sophisticated management?
I feel like the ideal would be to give the keys a name and allow you to generate multiple. That way we don't need to expose the secret to the HTML (other than at generation time which can be AJAX) and if we write a command line client we can do some sort of login process to get a key/secret.
From what I've noticed on other sites we should never expose the secret except for on creation and when a key is created we should email the user telling them a key was created.

Why do we only allow one active API key?

Sure, we could allow multiple keys at any time. It would mostly be a UX change. I can't think of a great reason to offer multiple keys right now though. Theoretically it would add more security if the developer had multiple clients but that won't mean much until API keys are scoped to how they can access the API (for example: read-only, read/write...). I suppose multiple keys would help for accountability in determining the source of a breach?

That way we don't need to expose the secret to the HTML ...

That's already in the works: https://bugzilla.mozilla.org/show_bug.cgi?id=1212959

we should never expose the secret except for on creation

Yes, typically we'd want something like that but for symmetric JWT purposes we need to store the secret. We might be able to throw away the key if we switch to RSA JWT signing (which is asymmetric).

when a key is created we should email the user telling them a key was created

Good idea. I filed: https://bugzilla.mozilla.org/show_bug.cgi?id=1214788

I can't think of a great reason to offer multiple keys right now though.

If I have multiple computers/apps set up and I accidentally commit my key/secret to git when setting up Travis it would be nice to log-in and delete that key and generate a new one. Rather than having to redo all of my computers/apps.

but for symmetric JWT purposes we need to store the secret

I don't think that means we need to expose it to the user more than once. If you create an access token on GitHub or an app-specific password with Google there's no view option. You create it, set up the service and there's no way to see it again. You can re-generate it or delete and create a new one but you can never recover that secret for reuse if you've lost it. I know that isn't JWT but it is symmetric in that it is a shared secret.

That's already in the works: https://bugzilla.mozilla.org/show_bug.cgi?id=1212959

If we add an endpoint that returns the secret that seems like a pretty high value target to gain access to an account. If the only way to get a secret from AMO is to create a new one and that action emails the account owner then that makes it a much less ideal target. If you look at the email as a "someone now has access to your account" notification then we should be emailing the user when they click the "show secret" button.

Sure, if you want to file for supporting multiple keys, that sounds reasonable to me.
As for only showing secrets once, it sounds like it could be poor UX to me. People lose things. But I can see some benefits. It would be nice to get security to weigh in on this to know if it's worth the UX trade-off.
As for the JSON endpoint to show a secret when the developer needs to get it, that would be CSRF protected so it's not much more of a target than a regular HTML view that renders a secret in the dom. We could add a feature where we email the user any time they 'view the secret' (with a debounce so it doesn't send more than one email a day). That would add similar protection to only allowing revocation/regeneration anytime someone needs to get a secret.

I don't think the UX is really any different between showing the secret and not. If you're going to the API key management page to get a key it makes no difference whether you click "Show" or "Create". In the end you're asking for a key and we're giving you one.
The attack vectors are known when exposing the secret but the attack vectors still exist. If we never show the secret (other than upon creation) then those attacks go away, leaving only create which we (should) send an email about.

If we never show the secret (other than upon creation) then those attacks go away

... so does a developer's ability to retrieve a lost secret. That's all I meant by poor UX.

@mstriemer should I hold off on this patch or could we move forward and follow up with additional bugs to address the issues you raised? It would be helpful to have security weigh in on the pros/cons, maybe when Adam Muntner is back.

I recommend you move forward and file additional bugs, we've got some time before this goes into prod.

Yeah, I'm cool with merging this. We can address stuff in separate bugs.

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1214928 to implement multiple API keys per user. I think it provides the same benefit of allowing the secret to be shown to the user and has the added benefit of reducing the cost of a key being compromised since you can revoke a single key's access.

sounds good, thanks for all the reviews


docker pull提示denied: requested access to the resource is denied

docker pull提示denied: requested access to the resource is denied
>docker pull registry.cn-beijing.aliyuncs.com/ms-jupyter/ak_tools:v1.0.5
 Error response from daemon: pull access denied for registry.cn-beijing.aliyuncs.com/ms-jupyter/ak_tools, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
`

赞！优秀！


Citation IRIs as virtual resources

The idea is to plan to provide a specific IRI for each citation included in the Corpus. However, we would like to avoid to add additional resources in the Corpus (i.e. a specific resource for each citation), since we want to avoid to be redundant with the data and to avoid the additional use of HD space.
Thus, the idea is to reserve a space in the OCC URLs for enabling "virtual" IRIs for accessing citations among two articles. Such "virtual" IRIs basically should not exist in the Corpus (nor in the dumps), but they could be accessed via HTTP as usual (by means of content negotiation). The basic structure of these virtual IRIs for citations could be as follows:
https://w3id.org/oc/virtual/citation/[citing OCC ID]/[cited OCC ID]

For instance, a citation from br/1 to br/11 would be identified by https://w3id.org/oc/virtual/citation/br/1/br/11.
If an agent asks for the information available to such citation virtual IRI, the serving mechanism would return all the basic string metadata (title, subtitle, year, if any) + type of the citing article, of the cited article, and the explicit link between those via cito:cites. For instance, considering the aforementioned example, accessing to https://w3id.org/oc/virtual/citation/br/1/br/11 will result in having the following RDF triples (in Turtle here):
<https://w3id.org/oc/corpus/br/1> cito:cites <https://w3id.org/oc/corpus/br/11> .

<https://w3id.org/oc/corpus/br/1> a fabio:Expression , fabio:JournalArticle ;
    dcterms:title "ESMO-ESGO-ESTRO Consensus Conference on Endometrial Cancer" ;
    fabio:hasSubtitle "Diagnosis, Treatment and Follow-up" ;
    fabio:hasPublicationYear "2016"^^xsd:gYear .

<https://w3id.org/oc/corpus/br/11> a fabio:Expression , fabio:JournalArticle ;
    dcterms:title "ACOG Practice Bulletin #65: Management of Endometrial Cancer" ;
    ns5:hasPublicationYear "2005"^^xsd:gYear .

This is just a proposal still under discussion – please feel free to comment on it.

As alternative to
https://w3id.org/oc/virtual/citation/[citing OCC ID]/[cited OCC ID]
we could also used a more compact format, e.g.:
https://w3id.org/oc/virtual/citation/[citing BR ID]-[cited BR ID]
since citations in the OCC happen only between BR resources. For instance, a citation from br/1 to br/11 would be identified by https://w3id.org/oc/virtual/citation/1-11.

Additionally, the returned metadata could include the statement
https://w3id.org/oc/virtual/citation/1-11 cito:hasCitationSpan 11 .   (years)

What does "ns5:hasPublicationYear "2005"^^xsd:gYear ." above mean?  Shouldn't this be "fabio:hasPublicationYear "2005"^^xsd:gYear ."?

@davidshotton,
Yes, wrong cut&paste: it should be fabio:hasPublicationYear indeed!


multystate lexer

Can you say how u can mamke multystate lexer (as in flex)?

@wwall Can you give an example? I'm not familiar with what that means.

hi.
For JFlex example fo lexer states here https://github.com/jflex-de/jflex/blob/master/docs/md/example.md
can in alexa use lexer state?

You can set variables in the action to give context, but the rules themselves don't specify context.


Add initPartialPlain to init plain messages with partials

It is possible to run initPartial with a plain message by passing the type separately from the plain message.
This is useful for initializing plain messages with partials.
In the interest of backwards compatibility. the initPartial function signature is kept the same. A separate function called initPartialPlain is added which accepts the type as a third parameter. initPartial is updated to call initPartialPlain with the type from getType() if source is set.

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


survey on molecule usage

Please vote on all options that apply to you and welcome others to do so. This will help us identify popularity of different components of molecule and on which to focus our testing and development.
If you vote other on any of the questions, please also add a comment so we would know what other means (we cannot update the poll once we created it).
Which molecule providers are you using or planning to?

Which molecule verifiers are you using?

Which linters are you using with molecule?

What is preffered way to install molecule?

What other tools are you using with molecule?

From which platforms are you running molecule from?

Closing but feel free to continue to vote.


Map .qhelp to XML

Description

Add .qhelp as an XML extension
Checklist:

[x] I am associating a language with a new file extension.

[x] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension:

https://github.com/search?q=extension%3Aqhelp+qhelp&type=Code

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

https://github.com/Semmle/ql/blob/master/cpp/ql/src/Critical/Unused.qhelp

Sample license(s): https://github.com/Semmle/ql/blob/master/LICENSE

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

Harvester reports only 8 unique users, with the majority of results coming from a single repository: (Semmle/ql).
1,392 total files (Click to show)
List elided so users watching this repository don't get a huge-ass e-mail notification.

So I'm afraid this falls short of our usage requirements.

@pchaigno Should I close this or mark it as Pending popularity?


create a new branch for readme

for checking the local  branches and it's workflow
ex:
4th_practice vs main branch
ithoda git pull -> branch poruthu irukuma,
on branch 4th_bractice
git pull -> git pull orgin 4th_practice
on branch main
git pull -> git pull orgin main

ok now check the difference


TLSv1.3: Add TLSv1.3 SSL_METHOD and other base plumbing changes

Checklist

[x] documentation is added or updated
[x] tests are added or updated

Description of change
Add the SSL_METHOD for TLSv1.3 and all other base changes required.
Includes addition of the various options to s_server/s_client. Also adds one of the new TLS1.3 ciphersuites.
This isn't "real" TLS1.3!! It's identical to TLS1.2 apart from the protocol name/number and the ciphersuite...and the ciphersuite is just a renamed TLS1.2 one (not a "real" TLS1.3 ciphersuite).
This will form the basis for future TLS1.3 implementation work.
As this is not a working TLS1.3 implementation at this stage it is disabled by default. Use "enable-tls1_3" to built it.

don't we use tls11 and tls12 elsewhere?  Why tls1_3 here?

@richsalz

don't we use tls11 and tls12 elsewhere? Why tls1_3 here?

Your comment was just standalone and not against a particular line, so I'm not sure which specific usage you are referring to. Generally though we use tls1, tls1_1 and tls1_2 at the moment (e.g. in option flag names etc), so tls1_3 is consistent.

Updated commits pushed to remove the accidentally added debug code.

I am concerned about the "get to it later."
I suggest "TLS13_AES" and "TLS1_CHACHAPOLY"

In retrospect, the entire "SSL_OP_NO_..." interface was a bad idea, and we've replaced it with a semantically cleaner interface for setting the min/max supported protocol versions.  Users should be strongly encouraged to use that instead.
As for holes with SSL_OP_NO_... they should still be avoided.  The client-side semantics should likely remain that only the protocols below the lowest hole end up enabled.  Alternatively, the client-side hello setup could always fail if holes are configured.
Changing the behaviour of existing functions strongly deters adoption of the toolkits in OS distributions.  So we can only introduce better interfaces, but need to very much avoid changing existing ones.

I am concerned about the "get to it later."

@richsalz your comment was standalone again...I'm assuming this was in reference to my comment:

WRT, decoupling from the current cipherstring processing: that may well be where we end up...but that's for a later stage in the development. Not right now.

If so, then there is a huge pile of stuff that we need to get to later that this PR raises....like the whole of the rest of the TLS1.3 implementation ;-). This is just one aspect! At this stage we're really not in a position to do anything much with the cipherstring selection processing. I've only added a single cipherstring...and its just a TLS1.2 cipher under the hood really. I think we really need to get some experience of actually implementing real TLS1.3 ciphersuites before we look at this...not to mention that without the underlying ciphersuite logic, doing cipherstring rule processing would be difficult to test. I've added a TODO in the code though so we don't forget about it. There's going to be a lot of TODOs over the coming PRs for stuff we need to "get to later".

I suggest "TLS13_AES" and "TLS1_CHACHAPOLY"

I assume you meant "TLS13_CHACHAPOLY". I'd like to avoid the "13" bit of that. It might make sense now, but in a few years time when TLS1.4 comes along with backwards compatible ciphersuites, its going to be annoying and difficult to get rid of. Also are you suggesting to use "_" as the separator? I used it, because that's what standard RFC names use. All the rest of our ciphersuites use "-" (i.e. minus sign). Also, did you really mean "TLS13_AES"? Or perhaps you meant "TLS13_AES_128_GCM_SHA256"? You really need to include the mode and hash.
Just dropping the "13" bit of the above gives you "TLS_AES_128_GCM_SHA256"...which is the same as my original proposal...or "TLS-AES-128-GCM-SHA256" if you prefer "-" as the separator.

Added a couple of commits, to insert a TODO around cipherstring selection, and convert a big "if" into a "switch" as per review comments.

I prefer to see the TLS13- prefix in the  cipher names for now.  We can clean it up later.

note that we have OPENSSL_NO_CHACHA and OPENSSL_NO_POLY135 (I think it silly that there are two, but so be it).  So you need that in the cipher table, too?
Or change config to disallow no-chacha/no-poly if you enable tls 1.3

Well I've not added any chacha/poly ciphersuites for TLS1.3 yet. I've only added a single AES one so I had something to test against. The others will be added when we actually do the proper ciphersuite implementation.

Right I've renamed the ciphersuite to "TLS13-AES-128-GCM-SHA256" for now. I'm not entirely happy about it (I really don't like the TLS13 bit), but in the interests of getting things to move on I'll go with that for now. There was already a big TODO about reviewing the ciphersuite naming. Updated commits pushed.
Is there anything else holding this one up? I'd really like to get this merged.

Merged. Thanks.


Long Triangles along edges of meshes being projected into head space

I'm encountering a bug where long triangles are being generated along edges of objects but rather than projecting into the distance they jut inward into the head space area. The cubemaps were rendered with anti-aliasing turned off with the hope that it would prevent these artifacts. Hopefully these screenshots illustrate the problem well enough.
Without wireframe

With wireframe

Top down:

I am seeing this too.  I am trying the seurat-pipeline with '-projective-texture' to see if this helps.  I will report back after I compare the results.  I have also bumped up the faces from 72K to 100K in hopes this will help as well.

Are these screenshots taken from inside the headbox? It is not uncommon for Seurat to generate these 'fins', but they shouldn't be noticeable as long as you stay inside the headbox.

The first two screenshots are within the headbox

How big is the headbox?

it is 5, 3, 5.


Drop Python 2 support and set 3.5 as the min version.

Technically speaking it closes https://github.com/ntoll/microfs/issues/19 😅
But yeah, tests fail with Python 2.7 and 3.4 (as indicated in https://github.com/ntoll/microfs/pull/30), so we should set the min version as 3.5 with python_requires.

Btw, there will be another PR coming soon to fix an issue with the ufs get command.

Ack (hello from Ghana :ghana: ). Give me a kick via GitHub when the PRs are lined up and I'll press buttons to cut a release.


[ FEATURE REQUEST ] - Add IBC capability to Azure Blockchain

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ x ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

N/A

Any log messages given by the failure

N/A

Expected/desired behavior

When I launch a blockchain on Azure, I want my blockchain to have interoperability with other chains that have IBC implemented.

OS and Version?

EVM

Versions

latest

Mention any other details that might be useful

EVM machines and other corporate enterprise chains that are a part of the Hyperledger community are already implementing IBC, the Inter Blockchain Communication protocol. The nearest protocol that could be most useful is here.

Thanks! We'll be in touch soon.

Teku is the Eth2 client powered by ConsenSys, built by the team behind Hyperledger Besu,
the leading Ethereum client for enterprises. It is the only client built to meet institutional
needs and security requirements.

Saw the closed issue #247 that Microsoft blockchain was being retired, and reference to ConsenSys.

I'll leave this open for now, I don't see where the blockchain workbench is being retired as it's still in public preview.

I'll leave this open for now, I don't see where the blockchain workbench is being retired as it's still in public preview.


cowboy instrumentation breaks cowboy_metrics_h callback

Describe the bug
When using the cowboy_telemetry_h and cowboy_metrics_h handler together, the metrics cb fails with:
2024-03-25T12:25:21.637585+01:00 <0.3469.0> telemetry:execute/3 : error: Handler opentelemetry_cowboy_handlers has failed and has been detached. Class=error
Reason={case_clause,[]}
Stacktrace=[{otel_telemetry,pop_from_tracer_stack,1,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/opentelemetry_telemetry/src/otel_telemetry.erl"},
                 {line,110}]},
            {otel_telemetry,end_telemetry_span,2,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/opentelemetry_telemetry/src/otel_telemetry.erl"},
                 {line,49}]},
            {opentelemetry_cowboy,handle_event,4,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/opentelemetry_cowboy/src/opentelemetry_cowboy.erl"},
                 {line,79}]},
            {telemetry,'-execute/3-fun-0-',4,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/telemetry/src/telemetry.erl"},
                 {line,160}]},
            {lists,foreach_1,2,[{file,"lists.erl"},{line,1686}]},
            {cowboy_metrics_h,terminate,3,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/cowboy/src/cowboy_metrics_h.erl"},
                 {line,302}]},
            {cowboy_stream,terminate,3,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/cowboy/src/cowboy_stream.erl"},
                 {line,138}]},
            {cowboy_http2,terminate_stream_handler,4,
                [{file,
                     "/usr/src/erlang/erccn/_build/default/lib/cowboy/src/cowboy_http2.erl"},
                 {line,1334}]}]
                 ```

Additionally, the cowboy_telemetry_h unconditionally overwrites the metrics_callback. That fact is neither documented nor desirable.

**Expected behavior**
not failing

**Additional context**

cowboy setup:

ProtoOpts =
    #{env => #{dispatch => Dispatch},
      logger => logger,
      metrics_callback => fun prometheus_cowboy2_instrumenter:observe/1,
      stream_handlers => [cowboy_telemetry_h, cowboy_metrics_h, cowboy_stream_h]
     },
cowboy:start_clear(?MODULE, TransOpts, ProtoOpts).

Hey @RoadRunnr, this repository is not the home of that library. Please raise the issue in its repo for assistance https://github.com/beam-telemetry/cowboy_telemetry

@bryannaegele but the stacktrace shows otel_telemetry crashing?

@bryannaegele but the stacktrace shows otel_telemetry crashing?

The later comments and errors higher up the stacktrace are suggesting the issue is running both stream handlers, so the issue would be in that library.

using the cowboy_telemetry_h and cowboy_metrics_h handler together, the metrics cb fails

And the offending conflict appears to be happening in the setup with some prometheus callback that's being run from another library.
metrics_callback => fun prometheus_cowboy2_instrumenter:observe/1,
stream_handlers => [cowboy_telemetry_h, cowboy_metrics_h, cowboy_stream_h]

opentelemetry_cowboy does nothing with stream handlers or anything else of that matter. It's just listening on telemetry events.

@bryannaegele the root cause is the way how cowboy_telemetry_h abuses cowboy_metrics_h, but the crash is in otel_telemetry:pop_from_tracer_stack/1 in this repo. The sister method otel_telemetry:peek_from_tracer_stack/1 does have special support for an empty context stack. So why would the others methods not have that too??

If you want to open a PR, we can accept that. But this error means you are ending a span early and your trace will be missing the root span.


Emily dev p1 s2

I completed step 2 of project 1. I added password to Datastore and updated the test for Datastore to test the password.

How does this PR related to #5 ? Is this an extension of it? It looks like it also contains some of the same changes.

This was step 2 of the project. I think I somehow messed up the branches when submitting a pull request for this. The step 2 parts are editing the PersistentDataStore class to add the password to 2 places. Then I also added tests in persistentDataStoreTest.


When I am trying to install in laravel 6.2 version it's showing error

[InvalidArgumentException]
Could not find a matching version of package javaabu/bml-connect-laravel. Check the package spelling, your version
constraint and that the package is available in a stability which matches your minimum-stability (dev).
require [--dev] [--prefer-source] [--prefer-dist] [--fixed] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] []...

Sorry, I haven't published this package on packagist yet. For now if you want to use this package in your project, you can add the following to your composer.json file
"repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/javaabu/bml-connect-laravel.git"
        }
    ],

Sorry, it wasn't published to packagist. Now I've published it. Please check now.


"before all" hook: codeceptjs.beforeSuite:Cannot read property '0' of null

I am trying to launch my test case on Internet Explorer on my client server on azure with Window 10 Enterprise N..for this I am starting the selenium standalone server automatically by using start_server.js, stop_server.js and system_config.js..I have installed latest selenium standalone with latest drivers of all browsers i.e (chrome,firefox and IE).
For IE I have manually placed IEdriver version 2.53.1 in location AppData/Roaming/npm/node_modules/selenium-standalone/.selenium as with latest version of IE there is some issue and my it don't launch the IE when my tests starts.
I am using codecept version 1.0.3, npm version on my client server is 5.3.0 and Node version is 8.2.1
With only change in npm version(5.5.0) on my local machine and everything else is same as I described above now when I am trying to launch the IE browser by using this command (npm run test:multi_ie) on client server then I am getting below error,but on my local system with windows 7 I am able to launch the IE without any issue.
Error When I run on client server.

C:\Tests_Debug>npm run test:multi_ie

<EMAIL_ADDRESS>test:multi_ie C:\Tests_Debug
codeceptjs run-multiple "ie:internet explorer"

null
[1.ie:internet explorer] CodeceptJS v1.0.3
[1.ie:internet explorer] Using test root "C:\Tests_Debug"
[1.ie:internet explorer] Fv anonymousShpntSbmt --
[1.ie:internet explorer]  × "before all" hook: codeceptjs.beforeSuite in 1666ms
[1.ie:internet explorer] TypeError: Cannot read property '0' of null
[1.ie:internet explorer] -- FAILURES:

Fv anonymousShpntSbmt: "before all" hook: codeceptjs.beforeSuite:
Cannot read property '0' of null

# paste output here

Provide test source code if related

// paste test

Details

CodeceptJS version:1.0.3
NodeJS Version:8.2.1
Operating System:Windows 10
Protractor || WebDriverIO || Nightmare version (if related)
Configuration file: Please find link

# paste suite config here

@reubenmiller : Please help me in this

I would highly recommend updating to Nodejs 8.9.3, but I just did some research and it is a bug with npm 5.5 (see the issue on the npm repo.
So the fix should be to update npm to 5.6.0. Though I still recommend updating nodejs to 8.9.3 as well.
Note you will problably have to remove your node_modules folder and reinstall the all of the dependencies using npm install.

@reubenmiller : I first tried to update Npm but its not getting updated.
I removed the node_modules folder and then by below steps I try to updated the Npm but its not getting updated..I also used npm install but again same npm not getting installed but with version 5.3.0
C:\Tests_Debug>npm install<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN The package mocha is included as both a dev and production dependency.

<EMAIL_ADDRESS>updated 1 package in 32.734s

C:\Tests_Debug>npm version
{ fvautomation: '1.0.0',
npm: '5.3.0',
ares: '1.10.1-DEV',
cldr: '31.0.1',
http_parser: '2.7.0',
icu: '59.1',
modules: '57',
node: '8.2.1',
openssl: '1.0.2l',
tz: '2017b',
unicode: '9.0',
uv: '1.13.1',
v8: '5.8.283.41',
zlib: '1.2.11' }
Do I need to first update the nodejs to 8.9.3 and will this updating of nodejs effect any of my settings?

Google is your friend with these sorts of problems. You probably have to at least start your shell session again (always good to do incase any environment variables were updated).
It is worth your while checking the node release page and npm repos for information about these issues. I just saw a note about the new node 8.9.4 release which added npm 5.6.0 as a dependency. So try installing node 8.9.4.
And there is only one way to find out if any of your config will be affected ;)

npm issue. Please install npm 5.6.0


Generalize the various chunk methods to produce any collection that implements Default + Extend

Fixes #2492

If a _Set or _Map is used as the collection, duplicate keys overwrite each other, and the len-like of the actual data structure doesn't increase.
Now that not only Vec can be used, we should examine what we mean when we want to set a cap/capacity for the adapter.
Both "how many items to consume" and "how many items to yield" are valid options.
The current implementation does the former.
The latter is missing a trait afaik, but may be less surprising.
Or more surprising, such as causing a soft deadlock with chunks(N) by not doing something necessary for more elements to be produced until a chunk is yielded because there were duplicate keys. (Where each "poke" of the source produces exactly N items.) (Could be fixed by the user with .take(N).chunks(N), but at that point they might as well collect because it won't be reusable.) 🐴

Also, since there is no with_capacity trait, should this be earmarked for when https://doc.rust-lang.org/std/iter/trait.Extend.html#method.extend_reserve is stabilized?

Only the former is implementable today. The latter would require a (stablized) trait for collection lengths. Since the caller already has to cope with undersized collections (at least for the final item with chunks, and potentially much more often for ready_chunks or try_chunks) I don't think that's a big problem.
I don't think there's any need to gate this on extend_reserve being stabilized because the implementation can be changed to use that some day with no externally visible changes.

Regarding extend_reserve, that's what I meant.
Perhaps something like "Depending on collection type, collections of less than capacity items may be yielded, as long as capacity elements were consumed." (but better worded) with or without an example in the doc comment. Probably only chunks needs this.


SW-4720 Render value of body in Message

was missing the curly braces

@nickgraz lets get this in

🤦


Make wordcloud optional?

The wordcloud library seems to cause a lot of troubles (e.g. https://github.com/adamerose/PandasGUI/issues/147, https://github.com/adamerose/PandasGUI/issues/179).
Would it make sense to declare it as an optional dependency so pip install pandasgui would not install it, but pip install pandasgui[wordcloud] would install it?

wordcloud has uploaded wheels now, so maybe not a problem anymore.


session's cookie secure problem

the cookie secure is set to true
while in production. After logging in its unable to set session with the logged user.
Hence the use are unable to create camp.

fixes

fixed!


Cleaning up and fixing parcel coalescing

move util::pool_timer to std::chrono
make coalescing parameters changeable
send parcel right away if the time since last parcel is larger than coalescing time

@justwagle I have fixed the problem you mentioned, please try again.

The problem has been fixed, it works.


Not able to display custom linked work item

Discussed in https://github.com/rfennell/AzurePipelines/discussions/1138

Originally posted by JaydeepUniverse November 12, 2021
Generally in the work item we can see 2 or 3 types of linked work items: Parent, Child, Related
and in the related work item we have diff. kind of work item types like  - bug, task, test plan, test case
We have created custom linked work item type called: Tested By for test plan and test case Ex,

To get the parent work item details we're using below code
{{#forEach this.relations}}
    {{#if (contains this.attributes.name 'Parent')}}
        {{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}
            #{{this.id}}
        {{/with}}
    {{/if}}
{{/forEach}}

and similarly I created another code for Tested By as below, But then issue is those tested by linked work items are not showing up
{{#forEach this.relations}}
    {{#if (contains this.attributes.name 'Tested By')}}
        {{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}
            #{{this.id}}
        {{/with}}
    {{/if}}
{{/forEach}}

We have few work items for which "Tested By" linked work item is not implemented yet, so to cross check other behavior I have noticed is that, I have created new code to get "Related" work items, what I get is related work items but other work items which are type of "Test case" or "Test plan" are not coming in the list
{{#forEach this.relations}}
    {{#if (contains this.attributes.name 'Related')}}
        {{#with (lookup_a_work_item ../../relatedWorkItems  this.url)}}
            #{{this.id}}
        {{/with}}
    {{/if}}
{{/forEach}}

Kindly advise how we can resolve this?
Let me know if any other details are needed
Thanks,
Jaydeep

Adding a new array object the template can use that lists the tested related items for a WI

@rfennell any ETA when this will be implemented?

It is on the backlog as a future enhancement, but I have no plans to implement it in the short term. Happy to consider PR if someone else has time


How to create a calendar and an entry

Installation was easy. Now I'm stuck. How do I add a new year, month, day, note? I don't see an i icon.
Thanks for any help.

Also: How to close the calender panel?

Hi @kklepper,
Notes can only be associated for each day so we can't create year or month notes.
When you create a new note normally in Joplin, they will show up on the calendar. (It may take a few seconds to update the calendar though.)
The "🛈" icon is can be found on the top right:

Ah, thanks a lot. I can open and close the calendar panel now. How do I organize it?
I created a note Diary 2024 and a subnote Jan and then clicked the current day 11 so I got an automatic entry 11 in that subnote.
Is that a viable way? Or is the subnote superfluous? After all, every month has a day 11.
I notice that if switch back to the calendar from any note by activating the cal, I get the cal entry, I understand that. Manipulating the i allows to move entries, is that correct?
Compared with my manual attempt this is a great improvement.

However, I do not understand the creation process. I tried to make a note for a future date, Feb 22, but didn't succeed.

Neither Annastift not 22 are associated to Feb 22. I created a new sub Feb and moved both entries, to no avail.
Please advise how to work with this tool.

I noticed that the keyboard toggle command does not work, which must be due to my German keyboard. Can I change this?

I noticed that the keyboard toggle command does not work, which must be due to my German keyboard. Can I change this?

Yup, this can be changed in the keyboard shortcuts.

Regarding creating notes on the calendar:
The file organization doesn't change the date a note shows up in the calendar.
So moving around notes like "22" and "Annastift" above doesn't actually change the date they show up on.
Let's say, we want to have a note show up on Feb 22, 2024 though.
First, click the "ⓘ" icon.
Then change the created date like so:

After that, the note should show up on Feb 22, 2024 on the calendar.

We have another issue to add notes directly to calendar dates: #11
When that is implemented, this will be easier 🙂

Thank you, very much appreciated.


[BUG] Executing a commented changes data grid

As from screenshot

If i had a datagrid and (accidentally) executed a commented string, i loose datagrid...

Well, what exactly is a bug?
If database allows to execute comments (e.g. MySQL) then we can't restrict this. It makes sense in some cases.

problem is not "executing a comment", problem is loosing the datagrid.
Expected behiavour: "empty query string" in the status bar, no change in the datagrid.

Whenever I execute a query, I expect to get a new data grid as a result. If the query happens to be empty, I don't mind (or would maybe even expect it) if I get an empty datagrid as a result.
Why would you execute a query at all (even if it happens to be empty or a comment only) if you don't want to lose your previous datagrid?

@wiwwo it is not an empty query string, it is a regular query. Comment may be a valuable query.
If you want to see your query on a new tab you can use "Execute in new tab" command (CTRL+</kbd>).
Or you can pin your already open tab and new query will open a new one.

@serge-rider my point is that this situation should be handled same as
https://github.com/dbeaver/dbeaver/issues/6463 :-)

@wiwwo This ticket and #6463 are completely different. Because, again, comment is a 100% valid SQL query (in some databases). It has nothing to do with empty query.

Ok


bump VERSION

hi jhx,
it's time to bump VERSION to 1.1.1, the program still reports 1.1.0

Fixed now.


RolemasterUnified Official: Item fixes for Treasure Law

Also known as the Author is an Idiot bugfix release for Treasure Law.

Allow drops from all magic item types
Save descriptions for all items (even new format)
Funky line as you lose hits or PP
Fix a maneuver penalty error which was messing up item drops

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.


DNM: Full branch_id implementation

One general comment: This PR introduces many different names for seemingly similar things, e.g., branch vs. subplan, reuse vs. elimination. We may want to clean this up before merging to make it easier to grasp concepts.


Using IEventHubReceiveEndpointConfigurator.OnPartitionInitializing (MassTransit.EventHubIntegration namespace) at all throws an exception?

Is this a bug report?
Yes.
Can you also reproduce the problem with the latest version?
Latest release, 7.0.6.
Environment

Operating system: Windows Server 2019
Visual Studio version: 2019, 16.7.6
Dotnet version: Framework 4.7.2

Steps to Reproduce

Create a new console app that simply runs a MassTransit bus. Using Microsoft.Extensions.DependencyInjection for DI and Microsoft.Extensions.Logging for Logging. Since this is .Net Framework, to be able to register MassTransit with IServiceCollection you need a few more dependencies:

MassTransit
MassTransit.EventHub
MassTransit.Extensions.DependencyInjection
Microsoft.Extensions.Logging
Microsoft.Extensions.Logging.Console
Microsoft.Extensions.DependencyInjection
Microsoft.Extensions.DependencyInjection.Abstractions

In the IServiceCollection setup, in the UsingEventHub extension method used to register the Azure Event Hub Rider, in the ReceiveEndpoint definition, specify the OnPartitionInitializing handler. Note, this does not have to do anything, it just has to be registered here.

Run the app.

Expected Behavior
I expect to be allowed to specify my own OnPartitionInitializing handler method in the MassTransit rider configuration so that I can control the PartitionInitializingEventArgs of the event reader.
For example, this would allow control of the DefaultStartingPosition and ContainerName options, which I am evaluating using together (ContainerName = Guid.NewGuid().ToString() to ensure there is never an existing checkpoint record for the new partition listener so that the DefaultStartingPosition is always controlling the new listener) to allow my app to control when in the event stream's history relative to 'now' a new partition listener starts listening from (see: https://docs.microsoft.com/en-us/dotnet/api/azure.messaging.eventhubs.processor.partitioninitializingeventargs?view=azure-dotnet).
I noticed in my testing that you have some input validation that catches the case when OnPartitionInitializing is specified more than once. This condition appears to be a different issue: OnPartitionInitializing cannot be specified at all in MassTransit configuration (nevermind actually setting variables with it) without a NotSupportedException being thrown.
Actual Behavior
On running an app configured with the above code, the following exception is logged:
MassTransit.ConfigurationException: 'An exception occurred creating the EventDataReceiver'
Inner Exception
NotSupportedException: Another handler has already been assigned to this event and there can be only one.
This exception was originally thrown at this call stack:
    Azure.Messaging.EventHubs.EventProcessorClient.PartitionInitializingAsync.add(System.Func<Azure.Messaging.EventHubs.Processor.PartitionInitializingEventArgs, System.Threading.Tasks.Task>)
    MassTransit.EventHubIntegration.Contexts.ProcessorLockContext.ProcessorLockContext(Azure.Messaging.EventHubs.EventProcessorClient, MassTransit.Context.ILogContext, System.TimeSpan, ushort)
    MassTransit.EventHubIntegration.Configurators.EventHubReceiveEndpointConfigurator.Build()
    MassTransit.EventHubIntegration.Specifications.EventHubReceiveEndpointSpecification.Create(MassTransit.Registration.IBusInstance)

Minimum Reproducible Demo
(Note I have removed the use of Microsoft.Extensions.Logging and Microsoft.Extensions.Logging.Console dependencies here for brevity):
using System;
using System.Linq;
using System.Threading.Tasks;
using System.Threading;
using MassTransit;
using Microsoft.Extensions.DependencyInjection;

public static async Task Main(string[] args)
{
   IServiceCollection services = new ServiceCollection();
   services.AddMassTransit(x =>
   {
   	x.AddRider(rider =>
	{
		rider.UsingEventHub((context, ehfc) =>
		{
			ehfc.Host(EventHubCredentials.EventHubConnectionString);
			ehfc.Storage(EventHubCredentials.CheckpointStorageConnectionString);
			ehfc.ReceiveEndpoint(EventHubCredentials.HubName, c =>
			{
				c.OnPartitionInitializing(f => // this is what causes exception
				{
					return Task.CompletedTask;
				});
			});
		});
	});
	x.UsingInMemory((context, cfg) =>
	{
		cfg.ConfigureEndpoints(context);
	});
   });
   IServiceProvider provider = services.BuildServiceProvider(true);
   IBusControl busControl = provider.GetRequiredService<IBusControl>();
   await busControl.StartAsync(new CancellationTokenSource(TimeSpan.FromSeconds(10)).Token);
}

Questions

Is there a better way to achieve what I am trying to do?
If this is an actual bug but you do not think you will get to it, would you be open to a PR?

I'd tell it is EventHub lib bug it self:
add
{
    Argument.AssertNotNull(value, nameof(PartitionInitializingAsync));
    if (_partitionInitializingAsync != default)
    {
        throw new NotSupportedException(Resources.HandlerHasAlreadyBeenAssigned);
    }
    EnsureNotRunningAndInvoke(() => _partitionInitializingAsync = value);
}

Do we wanna provide such sort of configuration anyway?

Well, if it can only be set once, and we are setting it, perhaps we should delegate to the user configured value when our partition initializing handler is called?


feat: controller leader election

Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] Bugfix

[x] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues

#85

Bugfix

Description

How to fix?

New feature or improvement

Describe the details and related test reports.

Backport patches

Why need to backport?

Source branch

Related commits and pull requests

Target branch

Codecov Report

Merging #173 (b9668f2) into master (1669bba) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #173      +/-   ##
==========================================
- Coverage   48.71%   48.65%   -0.07%
==========================================
  Files          30       30
  Lines        1480     1482       +2
==========================================
  Hits          721      721
- Misses        673      675       +2
  Partials       86       86

Impacted Files
Coverage Δ

cmd/ingress/ingress.go
70.76% <100.00%> (+0.45%)
:arrow_up:

pkg/config/config.go
83.33% <100.00%> (+0.47%)
:arrow_up:

pkg/seven/state/solver.go
1.69% <0.00%> (-1.70%)
: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 1669bba...b9668f2. Read the comment docs.

Codecov Report

Merging #173 (b9668f2) into master (1669bba) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #173      +/-   ##
==========================================
- Coverage   48.71%   48.65%   -0.07%
==========================================
  Files          30       30
  Lines        1480     1482       +2
==========================================
  Hits          721      721
- Misses        673      675       +2
  Partials       86       86

Impacted Files
Coverage Δ

cmd/ingress/ingress.go
70.76% <100.00%> (+0.45%)
:arrow_up:

pkg/config/config.go
83.33% <100.00%> (+0.47%)
:arrow_up:

pkg/seven/state/solver.go
1.69% <0.00%> (-1.70%)
: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 1669bba...b9668f2. Read the comment docs.

@gxthrj It's due to the controller didn't push the resources quickly to apisix.

@gxthrj It's due to the controller didn't push the resources quickly to apisix.

it seems that we need to add some E2E test case for this PR.
maybe the https://github.com/chaos-mesh/chaos-mesh is useful for us.

Already mimics the behavior in e2e cases.
What i did is killing the leader controller, and wait for a while until another leader was elected.

it seems that we need to add some E2E test case for this PR.
maybe the https://github.com/chaos-mesh/chaos-mesh is useful for us.

Already mimics the behavior in e2e cases.
What i did is killing the leader controller, and wait for a while until another leader was elected.

@gxthrj ping

@gxthrj ping

We'd better link related issues.

We'd better link related issues.

We'd better link related issues.

Already linked it. See the PR's overview.

We'd better link related issues.

Already linked it. See the PR's overview.

We'd better link related issues.

Already linked it. See the PR's overview.

Should be reflected here.

We'd better link related issues.

Already linked it. See the PR's overview.

Should be reflected here.


New release with updated dependencies?

Would be much appreciated. Thanks!

Brotli 1.0.9 was released on 2020-08-27 and contains a security fix.


Update go.sum for operator-sdk v0.11

Seems to be mismatched

In PR #410 we discovered that the mismatch is caused by compiling with go 1.12.x vs 1.13.x.  Lets turn this into a "move to go 1.13.x" issue, and upgrade to operator-sdk v0.12.0 which also requires go 1.13.x.
The operator-sdk upgrade guide has some information about moving to v0.12.0, and it looks pretty simple:
https://github.com/operator-framework/operator-sdk/blob/master/doc/migration/version-upgrade-guide.md
You can also use operator-sdk print-deps to see what the updated go.mod should contain (the relevant bits go at the bottom of go.mod).

FWIW if you want to come up further than v0.12.0, that's fine.... the upgrade guide doesn't have any information for those releases, but the releases page lists the breaking changes.  It looks like we should stop using operator-sdk generate openapi in v0.13.0.  I don't think we use those generated files anyway.

Fixed in #460


Issue using Terminus font

Backtrace: http://sprunge.us/CiGA
Config: http://sprunge.us/WIhY
As reported by brotherBox on IRC

Fixed

How did you fix?

@jcguu95 There is no problem with the terminus font. Make sure you have it installed and you are using the correct font name.


fix: Add title for footer links that open in a new tab #153

I've added title in all the links with target="_blank"

Thank you!


Is there going to be another release?

I love the game! When do we get the 1st official release?

I'm glad you like my creation. I am not going to abandon this project but unfortunately I have other priorities to resolve first. Hopefully after a few years I'll resume the development.


v-model value must be a valid JavaScript member expression

Version
3.1.0-beta.7
Reproduction link
https://github.com/RyzenPan/vue3-element-plus-vite
Steps to reproduce
I set a v-model value is v-model="data[item.dataIndex[0]]"
data = {
startTime: ''
}
item.dataIndex[0] = 'startTime'
item.dataIndex[0] is String
but the console thorw error v-model value must be a valid JavaScript member expression
What is expected?
It is not error
What is actually happening?
v-model value must be a valid JavaScript member expression

the linked "reproduction" does not contain the code mentioned in the description.
Please open a new issue with a real reproduction.

make sure update @vue/complier-sfc to 3.1.0-beta.7.
It will work.

Hi, i got the same error since @vue/compiler-sfc 3.1.1. It works fine with 3.0.11

Same here, I got the same error on @vue/compiler-sfc 3.1.0 and 3.1.1
VueCompilerError: v-model value must be a valid JavaScript member expression.
v-model="translations['zh-CN'][propName]"

Posting "same here" on a closed issue without providing a reproduction won't help us to solve this.
please open a new issue and provide a real reproduction


MSID: 90606 Version: 2 DOI: 10.1101/2<IP_ADDRESS>6963

MSID: 90606
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>6963
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=90606
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6963

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/90606v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>6963
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/90606/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Jessica Flowers isn't present in author list


Frame for subviews of UIScrollView

The frame of a view that is a direct subview of a UIScrollView needs to have its frame adjusted by the content offset in order to be placed correctly.

Thank you very much!


[Bug]: size() doesnt work

What happened?
RatingStarColumn::make('stars')->size('sm')
Method IbrahimBougaoua\FilamentRatingStar\Columns\RatingStarColumn::size does not exist.

How to reproduce the bug
RatingStarColumn::make('stars')->size('sm')
Package Version
^1.0
PHP Version
8.2
Laravel Version
10.x
Which operating systems does with happen with?
Linux
Notes
No response

I need to manually update package to dev-main to get latest
"ibrahimbougaoua/filament-rating-star": "dev-main"

Undefined variable $getSize
if I specify size, error is shown.


CI Failing with Out of Disk

Describe the bug
CI is failing due to running out of disk space https://github.com/apache/arrow-datafusion/actions/runs/3995952868/jobs/6855600796
This correlates with enabling the dyn_arith_dict feature in CI - https://github.com/apache/arrow-datafusion/pull/4999
To Reproduce
Steps to reproduce the behavior:
Expected behavior
We should not exceed the disk capacity of the runners, either by splitting up the CI into smaller steps and cleaning the target directory inbetween, or splitting the CI into multiple smaller workflows like we do for arrow-rs
Additional context
Add any other context about the problem here.

I plan to work on this later today if nobody gets there first


add documentation about the generated sql resources: why they are best practice and how to use them

ensure to show examples of how to hydrate based on the view (e.g., for array properties and just for references, too)


#27 make TxMessage data members public

see #27

I don't think it's worth giving up OOP or stability and security principles just because of tests. What about just adding getter methods, which return immutable borrows? This would also have the advantage that these methods may also be helpful outside of tests.

Yes probably a better idea, so as an example to get the buff member we could implement a fn like this:
  pub fn get_payload(&self) -> &Bytes {
        &self.buff
    }


Batt btm to grid and manual clip

Pairs with SAM PR https://github.com/NREL/SAM/pull/754
Update charging and discharging constraints to allow:

Clip charging for BTM dispatch (manual and price signals) and FOM manual dispatch
Discharge to grid for BTM dispatch (only affects manual and custom right now)

PVWatts-Battery defaults grid discharging to true.
Peak shaving, grid power targets, and price signals dispatch will need updates to take advantage of grid discharge capabilities. This can be done in a future PR for a patch.
Solves SAM issues https://github.com/NREL/SAM/issues/338 and https://github.com/NREL/SAM/issues/407

Failure matches version of develop used to create this branch. Develop was fixed here: https://github.com/NREL/SAM/runs/4182767103. I can merge in develop and re-run if desired, but refraining for now to save Travis credits.


Experience/13620/submissions filename

This PR ...
Adds the filename to the Submission Table API call
Test Steps:

Open Postman and run the following: /api/waters/org/ignore/submissions?pageSize=61&cursor=3000-01-01T08%3A00%3A00.000Z&since=2000-01-01T08%3A00%3A00.000Z&until=3000-01-01T08%3A00%3A00.000Z&sortcol=undefined&sortdir=DESC

Sign into RS as a sender

See filename in the submissions table

Changes

The response will now return the fileName and fileType

{
       "submissionId": 1885,
       "timestamp": "2024-03-14T17:40:50.641Z",
       "sender": "ignore.ignore-elr-elims",
       "httpStatus": 201,
       "id": "03c3b7ab-7c65-4174-bea7-9195cbb7ed01",
       "topic": "elr-elims",
       "reportItemCount": 1,
       "fileName": "None-03c3b7ab-7c65-4174-bea7-9195cbb7ed01-20240314174050.hl7",
       "fileType": "HL7"
   },

Checklist
Testing

[x] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[x] Added tests?

Linked Issues

Fixes #13620

I'm not sure how to easily find if a function has unit test coverage in the frontend. It might also be worth adding adding an end2end test for this.

I added to the unit and e2e tests.


[Bug]: My application's clang-tidy build failing from abseil package.

Describe the issue
I am getting the following build errors in my application build from abseil conan package. Our application is based on C++14.
From abseil source code, I understand this will happen only if ABSL_USES_STD_VARIANT is defined.
Logs
`/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:54:12: error: no member named 'bad_variant_access' in namespace 'std' [clang-diagnostic-error]
using std::bad_variant_access;
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:56:12: error: no member named 'get_if' in namespace 'std' [clang-diagnostic-error]
using std::get_if;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:57:12: error: no member named 'holds_alternative' in namespace 'std' [clang-diagnostic-error]
using std::holds_alternative;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:58:12: error: no member named 'monostate' in namespace 'std' [clang-diagnostic-error]
using std::monostate;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:59:12: error: no member named 'variant' in namespace 'std' [clang-diagnostic-error]
using std::variant;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:60:12: error: no member named 'variant_alternative' in namespace 'std' [clang-diagnostic-error]
using std::variant_alternative;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:61:12: error: no member named 'variant_alternative_t' in namespace 'std' [clang-diagnostic-error]
using std::variant_alternative_t;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:62:12: error: no member named 'variant_npos' in namespace 'std' [clang-diagnostic-error]
using std::variant_npos;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:63:12: error: no member named 'variant_size' in namespace 'std' [clang-diagnostic-error]
using std::variant_size;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:64:12: error: no member named 'variant_size_v' in namespace 'std' [clang-diagnostic-error]
using std::variant_size_v;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:65:12: error: no member named 'visit' in namespace 'std' [clang-diagnostic-error]
using std::visit;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/types/variant.h:859:16: error: no member named 'visit' in namespace 'absl' [clang-diagnostic-error]
return absl::visit(variant_internal::ConversionVisitor{},
~~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/utility/utility.h:164:12: error: no member named 'in_place_t' in namespace 'std' [clang-diagnostic-error]
using std::in_place_t;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/utility/utility.h:165:12: error: no member named 'in_place' in namespace 'std' [clang-diagnostic-error]
using std::in_place;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/utility/utility.h:181:12: error: no member named 'in_place_type' in namespace 'std' [clang-diagnostic-error]
using std::in_place_type;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/utility/utility.h:182:12: error: no member named 'in_place_type_t' in namespace 'std' [clang-diagnostic-error]
using std::in_place_type_t;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/utility/utility.h:198:12: error: no member named 'in_place_index' in namespace 'std' [clang-diagnostic-error]
using std::in_place_index;
~~~~~^
/root/.conan/data/abseil/20230802.1///package/6557f18ca99c0b6a233f43db00e30efaa525e27e/include/absl/utility/utility.h:199:12: error: no member named 'in_place_index_t' in namespace 'std' [clang-diagnostic-error]
using std::in_place_index_t;
~~~~~^`

My conan file looks like something below.
`class AppConan(ConanFile):
    name = "app"
    description = "Application"
    settings = "os", "compiler", "build_type", "arch"
    requires = (
        "gtest/[1.8.x]",
        "fmt/[8.x]",
       ....
        "abseil/20230802.1"`

My conan profile look like this:
`[settings]
compiler.libcxx=libstdc++11
cppstd=gnu14
arch=x86_64
build_type=Release
compiler=gcc

[conf]
tools.cmake.cmaketoolchain:user_toolchain=['$PROFILE_DIR/../../toolchain/clang-tidy.cmake']`

I also tried changing `cppstd` to `gnu17`, but doesn't fix the abseil build issue.

Seems like bincrafters abseil package is not currently maintained. Hence that also didn't work.
Could some one guide me how can I resolve this issue?

Thanks,
Honey

Honey Sukesan

### Steps to reproduce the problem

Use `abseil/20230802.1` in conan file and try to build an application.

### What version of Abseil are you using?

abseil/20230802.1

### What operating system and version are you using?

# Package and Environment Details
Package Name/Version: abseil/20230802.1
Operating System+version: Linux Ubuntu 22.04
Conan version: conan 1.59.0

### What compiler and version are you using?

g++ 12

### What build system are you using?

conan with cmake 3.24

### Additional context

_No response_

This is likely because you are building your program with C++14 but the version you are getting from Conan is built with C++17. The Conan version has patches that we do not endorse and we cannot offer support for the Conan version. Sorry.


Retraining 512x512 with 68 keypoints，then retraining 512x512 with dlib 68 keypoints detector

I want to retrain FOMM with 68 keypoints (512x512) and release it publicly, if successful.  In addition, I prefer to retrain fomm based on dlib 68 keypoints detector. This allows the keypoints correspondence to semantic information.
However, I am currently having some problems with 512x512 retraining, I hope someone can share their 512x512 training experience

I also found someone have retraining 512x512 seccessfully. https://github.com/AliaksandrSiarohin/first-order-model/issues/20#issuecomment-822862456

When I train the 512 model, I noticed that the vis picture seems to have been cropped

This is the issue of imageio.imsave. It is slow to save the image through imageio.imsave. If you save the numpy file of the image and save convert it to image later then you can see there won't be any cropping.
You can also use cv2.imwrite which is faster and doesn't give the cropping error.


[BACKLOG-22112] fix for print issue on mac

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  ui/src/main/java/org/pentaho/di/ui/core/dialog/ShowHelpDialog.java

Newly Fixed Tests:
org.pentaho.di.trans.step.mqtt.MQTTStreamSourceTest.testMqttStreamSingleTopic:
:large_blue_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError
	at org.pentaho.di.trans.step.mqtt.MQTTStreamSourceTest.getQuickly(MQTTStreamSourceTest.java:253)
	at org.pentaho.di.trans.step.mqtt.MQTTStreamSourceTest.testMqttStreamSingleTopic(MQTTStreamSourceTest.java:122)

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.2% (click to expand)
:new: org.pentaho.di.trans.step.mqtt.MQTTConstants

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumer

Line Coverage: 78.6% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumerDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTConsumerMeta

Branch Coverage: 50% :exclamation:
Complexity Coverage: 58.2% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MqttDialogOptionsLayout

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MqttDialogSecurityLayout

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducer

Branch Coverage: 72.2% :exclamation:
Complexity Coverage: 64.7% :exclamation:
Method Coverage: 75% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducerDialog

Coverage: 0% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTProducerMeta

Branch Coverage: 50% :exclamation:
Complexity Coverage: 63.6% :exclamation:
Instruction Coverage: 75.4% :exclamation:

:new: org.pentaho.di.trans.step.mqtt.MQTTStreamSource

Branch Coverage: 75% :exclamation:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:


Interpolate x value for plotting

I was hoping to improve the plots by not using the constant interpolation at a position x, but using higher order interpolation, in particular I was hoping to have a smaller phase shift in some plots, where we plot the solution at certain x values that are not on the grid. Unfortunately, the plots did not really improve, also not for cubic interpolation.

Codecov Report

Merging #64 (29b49ac) into main (188792b) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
- Coverage   96.09%   96.08%   -0.01%
==========================================
  Files          13       13
  Lines         972      971       -1
==========================================
- Hits          934      933       -1
  Misses         38       38

Files
Coverage Δ

src/visualization.jl
91.72% <100.00%> (-0.06%)
:arrow_down:

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

Nice idea. You could check how it looks like in a scatter plot of the numerical data overlayed on the reference data. If you don't see an improvement of the phase shift there, there is no chance to get better results using intrpolations.


How to retrain the Detector MobileNet-SSD

When I open the repo https://github.com/zeusees/Mobilenet-SSD-License-Plate-Detection I see .prototxt and .caffemodel, so I assume the developer used Caffe for training... But when I check the code of HyperLPR I see Keras... And when I check the file https://pan.baidu.com/s/11V0Pfx6jGNaBOOTqDSVK2Q I see the files .pb and .pbtxt whom are generated by retrain in tensorflow...
So what method did you use for training, Caffe, Keras or Tensorflow??? Also if you can give me a tutorial I will be very happy. Thanks!

you can refer https://blog.csdn.net/lsy17096535/article/details/78687728


Failed to build cpp-netlib 0.12.0

Hi. I have tried to build the lib on solaris but it fail to build.
I have Solaris 11 x86, g++ 7.3.0, cmake 3.9.1, boost 1.68.0.
I have tried to build the version 1.12.0.
This is the output:
 [7%] Building CXX object libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o
cd /export/home/amreo/cpp-netlib-build/libs/network/src && /usr/bin/g++  -DASIO_HEADER_ONLY -DBOOST_NETWORK_DEBUG -DBOOST_NETWORK_ENABLE_HTTPS -DBOOST_SPIRIT_THREADSAFE -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/export/home/amreo/cpp-netlib/deps/asio/asio/include -I/export/home/amreo/cpp-netlib -Wall -std=c++11 -o CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o -c /export/home/amreo/cpp-netlib/libs/network/src/client.cpp
In file included from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/dev_poll_reactor.hpp:211:0,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/reactor.hpp:25,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/system_executor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/associated_executor.hpp:21,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/io_service.hpp:24,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_io_object.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19,
                 from /export/home/amreo/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
                 from /export/home/amreo/cpp-netlib/libs/network/src/client.cpp:13:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp: In constructor ‘asio::detail::dev_poll_reactor::dev_poll_reactor(asio::execution_context&)’:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:33:31: error: expected template-name before ‘<’ token
   : asio::detail::service_base<dev_poll_reactor>(ctx),
                               ^
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:33:31: error: no matching function for call to ‘asio::detail::execution_context_service_base<asio::detail::dev_poll_reactor>::execution_context_service_base()’
In file included from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/scheduler.hpp:21:0,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/system_executor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/associated_executor.hpp:21,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/io_service.hpp:24,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_io_object.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19,
                 from /export/home/amreo/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
                 from /export/home/amreo/cpp-netlib/libs/network/src/client.cpp:13:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/execution_context.hpp:392:3: note: candidate: asio::detail::execution_context_service_base<Type>::execution_context_service_base(asio::execution_context&) [with Type = asio::detail::dev_poll_reactor]
   execution_context_service_base(execution_context& e)
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/execution_context.hpp:392:3: note:   candidate expects 1 argument, 0 provided
In file included from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/dev_poll_reactor.hpp:211:0,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/reactor.hpp:25,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/system_executor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/associated_executor.hpp:21,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/io_service.hpp:24,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_io_object.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19,
                 from /export/home/amreo/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
                 from /export/home/amreo/cpp-netlib/libs/network/src/client.cpp:13:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:32:1: error: uninitialized reference member in ‘class asio::detail::scheduler&’ [-fpermissive]
 dev_poll_reactor::dev_poll_reactor(asio::execution_context& ctx)
 ^~~~~~~~~~~~~~~~
In file included from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/reactor.hpp:25:0,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/system_executor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/associated_executor.hpp:21,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/io_service.hpp:24,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_io_object.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19,
                 from /export/home/amreo/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
                 from /export/home/amreo/cpp-netlib/libs/network/src/client.cpp:13:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/dev_poll_reactor.hpp:177:14: note: ‘asio::detail::scheduler& asio::detail::dev_poll_reactor::scheduler_’ should be initialized
   scheduler& scheduler_;
              ^~~~~~~~~~
In file included from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/dev_poll_reactor.hpp:211:0,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/reactor.hpp:25,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/system_executor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/associated_executor.hpp:21,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/io_service.hpp:24,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_io_object.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ip/tcp.hpp:19,
                 from /export/home/amreo/cpp-netlib/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
                 from /export/home/amreo/cpp-netlib/libs/network/src/client.cpp:13:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:33:31: error: expected ‘{’ before ‘<’ token
   : asio::detail::service_base<dev_poll_reactor>(ctx),
                               ^
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp: At global scope:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:33:31: error: expected unqualified-id before ‘<’ token
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp: In member function ‘virtual void asio::detail::dev_poll_reactor::fork_service(asio::execution_context::fork_event)’:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:116:24: error: ‘class asio::detail::reactor_op_queue<int>’ has no member named ‘get_descriptors’
     op_queue_[read_op].get_descriptors(read_op_helper, ops);
                        ^~~~~~~~~~~~~~~
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:118:25: error: ‘class asio::detail::reactor_op_queue<int>’ has no member named ‘get_descriptors’
     op_queue_[write_op].get_descriptors(write_op_helper, ops);
                         ^~~~~~~~~~~~~~~
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/detail/impl/dev_poll_reactor.ipp:120:26: error: ‘class asio::detail::reactor_op_queue<int>’ has no member named ‘get_descriptors’
     op_queue_[except_op].get_descriptors(except_op_helper, ops);
                          ^~~~~~~~~~~~~~~
In file included from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/context.hpp:755:0,
                 from /export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl.hpp:18,
                 from /export/home/amreo/cpp-netlib/boost/network/protocol/http/client/connection/ssl_delegate.ipp:12,
                 from /export/home/amreo/cpp-netlib/libs/network/src/client.cpp:16:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp: In constructor ‘asio::ssl::context::context(asio::ssl::context_base::method)’:
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp:88:31: error: ‘::SSLv3_method’ has not been declared
     handle_ = ::SSL_CTX_new(::SSLv3_method());
                               ^~~~~~~~~~~~
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp:88:31: note: suggested alternative: ‘SSLv23_method’
     handle_ = ::SSL_CTX_new(::SSLv3_method());
                               ^~~~~~~~~~~~
                               SSLv23_method
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp:91:31: error: ‘::SSLv3_client_method’ has not been declared
     handle_ = ::SSL_CTX_new(::SSLv3_client_method());
                               ^~~~~~~~~~~~~~~~~~~
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp:91:31: note: suggested alternative: ‘SSLv23_client_method’
     handle_ = ::SSL_CTX_new(::SSLv3_client_method());
                               ^~~~~~~~~~~~~~~~~~~
                               SSLv23_client_method
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp:94:31: error: ‘::SSLv3_server_method’ has not been declared
     handle_ = ::SSL_CTX_new(::SSLv3_server_method());
                               ^~~~~~~~~~~~~~~~~~~
/export/home/amreo/cpp-netlib/deps/asio/asio/include/asio/ssl/impl/context.ipp:94:31: note: suggested alternative: ‘SSLv23_server_method’
     handle_ = ::SSL_CTX_new(::SSLv3_server_method());
                               ^~~~~~~~~~~~~~~~~~~
                               SSLv23_server_method
*** Error code 1
make: Fatal error: Command failed for target `libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o'
Current working directory /export/home/amreo/cpp-netlib-build
*** Error code 1
make: Fatal error: Command failed for target `libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/all'
Current working directory /export/home/amreo/cpp-netlib-build
*** Error code 1
make: Fatal error: Command failed for target `all'

Also had a make error.
Scanning dependencies of target atom_reader
[ 58%] Building CXX object libs/network/example/CMakeFiles/http_client.dir/http_client.cpp.o
cd /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++  -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/Users/robert/Desktop/cpp-netlib-0.13.0-final -I/Users/robert/Desktop/cpp-netlib-0.13.0-final/deps/cxxopts/src  -std=c++11 -Wall -ftemplate-depth=256 -std=c++11 -stdlib=libc++   -o CMakeFiles/http_client.dir/http_client.cpp.o -c /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example/http_client.cpp
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f libs/network/example/CMakeFiles/atom_reader.dir/build.make libs/network/example/CMakeFiles/atom_reader.dir/build
[ 62%] Building CXX object libs/network/example/CMakeFiles/atom_reader.dir/atom/atom.cpp.o
cd /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++  -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/Users/robert/Desktop/cpp-netlib-0.13.0-final -I/Users/robert/Desktop/cpp-netlib-0.13.0-final/deps/cxxopts/src  -std=c++11 -Wall -ftemplate-depth=256 -std=c++11 -stdlib=libc++   -o CMakeFiles/atom_reader.dir/atom/atom.cpp.o -c /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example/atom/atom.cpp
/Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example/http_client.cpp:18:10: fatal error: 'cxxopts.hpp' file not found
#include "cxxopts.hpp"
         ^
1 error generated.
make[2]: *** [libs/network/example/CMakeFiles/http_client.dir/http_client.cpp.o] Error 1
make[1]: *** [libs/network/example/CMakeFiles/http_client.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 65%] Building CXX object libs/network/example/CMakeFiles/atom_reader.dir/atom/main.cpp.o
cd /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++  -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/Users/robert/Desktop/cpp-netlib-0.13.0-final -I/Users/robert/Desktop/cpp-netlib-0.13.0-final/deps/cxxopts/src  -std=c++11 -Wall -ftemplate-depth=256 -std=c++11 -stdlib=libc++   -o CMakeFiles/atom_reader.dir/atom/main.cpp.o -c /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example/atom/main.cpp
[ 68%] Linking CXX executable ../../../example/atom_reader
cd /Users/robert/Desktop/cpp-netlib-0.13.0-final/libs/network/example && /usr/local/Cellar/cmake/3.13.4/bin/cmake -E cmake_link_script CMakeFiles/atom_reader.dir/link.txt --verbose=1
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++  -std=c++11 -Wall -ftemplate-depth=256 -std=c++11 -stdlib=libc++ -Wl,-search_paths_first -Wl,-headerpad_max_install_names  -lc++ CMakeFiles/atom_reader.dir/atom/atom.cpp.o CMakeFiles/atom_reader.dir/atom/main.cpp.o  -o ../../../example/atom_reader /usr/local/lib/libboost_system-mt.dylib /usr/local/lib/libboost_thread-mt.dylib /usr/local/lib/libboost_chrono-mt.dylib /usr/local/lib/libboost_date_time-mt.dylib /usr/local/lib/libboost_atomic-mt.dylib ../src/libcppnetlib-uri.a ../src/libcppnetlib-client-connections.a /usr/local/lib/libboost_system-mt.dylib /usr/local/lib/libboost_thread-mt.dylib /usr/local/lib/libboost_chrono-mt.dylib /usr/local/lib/libboost_date_time-mt.dylib /usr/local/lib/libboost_atomic-mt.dylib
[ 68%] Built target atom_reader
make: *** [all] Error 2

This also affects me on Debian testing with 0.13.0-final.
clang version 7.0.1-8 (tags/RELEASE_701/final)
Target: x86_64-pc-linux-gnu

I believe that this is a dupe of #849 where all the bundled deps are missing from the release tarball.


label: remove the needs-cherry-pick labels for archived doc versions

/lgtm
/approve

/ok-to-test


Fix Progress bar with zero progress still shows some progress

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Fixed issues

This fixes the bug but I think how the progress bar calculates and sets the indicators size should be refactored in general.
So that it's possible to create a circular progress indicator just by applying a different style for example. This is currently not possible because the control sets the Width / Hight property of the Indicator directly in code.


AR: pass input options to widget

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues
#16681

User case:
<?=
$form->field($model, 'test', ['inputOptions' => ['placeholder' => 'placeholder#1']])->widget(
    MaskedInput::className(), [
        'name' => 'phone',
        'mask' => '999-999-9999',
        'options' => ['placeholder' => 'placeholder#2']
    ]
);
?>

Got input with 'placeholder#2' placeholder.
<?=
$form->field($model, 'test', ['inputOptions' => ['placeholder' => 'placeholder#1']])->widget(
    MaskedInput::className(), [
        'name' => 'phone',
        'mask' => '999-999-9999',
    ]
);
?>

Got input with 'placeholder#1' placeholder.
It is very raw revision for discussion purposes only.

Any idea what's wrong with tests?

Merged. Thank you!