RAM requirements listed on installation instructions wiki page?

Hi there,
For those of us provisioning cloud instances to run the CTAT containers, it would be helpful if there was a note about the RAM requirements of CTAT/VIF, so that we can account for this when we are setting up the compute environment. I was unable to run VIF on a smaller cloud instance I provisioned today; error noted that 32GB of RAM was required.
EXITING: fatal error trying to allocate genome arrays, exception thrown: std::bad_alloc
Possible cause 1: not enough RAM. Check if you have enough RAM<PHONE_NUMBER>4 bytes
Possible cause 2: not enough virtual memory allowed with ulimit. SOLUTION: run ulimit -v<PHONE_NUMBER>4

(alternatively, if this number is dynamic based on the data, it would be nice to know how to estimate it).
I'd file a PR myself with a suggested change, but I don't think it's possible to do that on wiki pages. :)
Thanks for considering it!

Hi,
We tend to run the STAR alignment step with 45 G RAM.
I'll add a note on the wiki.
best,
~brian
On Wed, Jun 16, 2021 at 4:42 PM Robert Allaway @.***>
wrote:

Hi there,
For those of us provisioning cloud instances to run the CTAT containers,
it would be helpful if there was a note about the RAM requirements of
CTAT/VIF, so that we can account for this when we are setting up the
compute environment. I was unable to run VIF on a smaller cloud instance I
provisioned today; error noted that 32GB of RAM was required.
EXITING: fatal error trying to allocate genome arrays, exception thrown: std::bad_alloc
Possible cause 1: not enough RAM. Check if you have enough RAM<PHONE_NUMBER>4 bytes
Possible cause 2: not enough virtual memory allowed with ulimit. SOLUTION: run ulimit -v<PHONE_NUMBER>4
(alternatively, if this number is dynamic based on the data, it would be
nice to know how to estimate it).
I'd file a PR myself with a suggested change, but I don't think it's
possible to do that on wiki pages. :)
Thanks for considering it!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/issues/30,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZRKX3IA7I4AGJTB3FNXQDTTEECZANCNFSM462HHATQ
.

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas

Thanks so much, and thanks for all of your work maintaining this awesome
toolkit!
Cheers,
Robert
On Thu, Jun 17, 2021 at 7:48 AM Brian Haas @.***> wrote:

Hi,
We tend to run the STAR alignment step with 45 G RAM.
I'll add a note on the wiki.
best,
~brian
On Wed, Jun 16, 2021 at 4:42 PM Robert Allaway @.***>
wrote:

Hi there,
For those of us provisioning cloud instances to run the CTAT containers,
it would be helpful if there was a note about the RAM requirements of
CTAT/VIF, so that we can account for this when we are setting up the
compute environment. I was unable to run VIF on a smaller cloud instance
I
provisioned today; error noted that 32GB of RAM was required.
EXITING: fatal error trying to allocate genome arrays, exception thrown:
std::bad_alloc
Possible cause 1: not enough RAM. Check if you have enough RAM
31259734944 bytes
Possible cause 2: not enough virtual memory allowed with ulimit.
SOLUTION: run ulimit -v<PHONE_NUMBER>4
(alternatively, if this number is dynamic based on the data, it would be
nice to know how to estimate it).
I'd file a PR myself with a suggested change, but I don't think it's
possible to do that on wiki pages. :)
Thanks for considering it!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/issues/30
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABZRKX3IA7I4AGJTB3FNXQDTTEECZANCNFSM462HHATQ
.

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/issues/30#issuecomment-863304534,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3WNSFQJAM63PS4NDAQAPDTTIDKNANCNFSM462HHATQ
.

sure thing!  let me know if it gives you any trouble. It's one of our newer
software tools and there are some things that are still being further
optimized.
best,
~b
On Thu, Jun 17, 2021 at 10:54 AM Robert Allaway @.***>
wrote:

Thanks so much, and thanks for all of your work maintaining this awesome
toolkit!
Cheers,
Robert
On Thu, Jun 17, 2021 at 7:48 AM Brian Haas @.***> wrote:

Hi,
We tend to run the STAR alignment step with 45 G RAM.
I'll add a note on the wiki.
best,
~brian
On Wed, Jun 16, 2021 at 4:42 PM Robert Allaway @.***>
wrote:

Hi there,
For those of us provisioning cloud instances to run the CTAT
containers,
it would be helpful if there was a note about the RAM requirements of
CTAT/VIF, so that we can account for this when we are setting up the
compute environment. I was unable to run VIF on a smaller cloud
instance
I
provisioned today; error noted that 32GB of RAM was required.
EXITING: fatal error trying to allocate genome arrays, exception
thrown:
std::bad_alloc
Possible cause 1: not enough RAM. Check if you have enough RAM
31259734944 bytes
Possible cause 2: not enough virtual memory allowed with ulimit.
SOLUTION: run ulimit -v<PHONE_NUMBER>4
(alternatively, if this number is dynamic based on the data, it would
be
nice to know how to estimate it).
I'd file a PR myself with a suggested change, but I don't think it's
possible to do that on wiki pages. :)
Thanks for considering it!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/issues/30
,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ABZRKX3IA7I4AGJTB3FNXQDTTEECZANCNFSM462HHATQ

.

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/issues/30#issuecomment-863304534
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AE3WNSFQJAM63PS4NDAQAPDTTIDKNANCNFSM462HHATQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/issues/30#issuecomment-863310019,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZRKX3EDHFVN2R2TYNSSPLTTIED7ANCNFSM462HHATQ
.

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas


Yet to implement backend

The backend of the game is yet to be implemented by using some chess engine (most probably Stockfish)

The backend will be implemented for Microsoft Windows due to limited hardware


Capture code coverage data

Currently code coverage is captured from our 'Sonar' test runs
This is done by enabling 'jacoco' in the build. This attaches an agent to the jvm used by surefire for running Unit Tests. Coverage data is captured and saved in a file which is then uploaded to sonar
We need to look at

[ ] How is this affected by the move of our PR builds to github actions - is it still working
[ ] could we capture code coverage in actions instead
[ ] how are results published and made accessible
[ ] Are we sure FVT coverage data is captured. From the client (failsafe)? How about the server (launched from groovy)
[ ] Ensuring developer guidelines updated with information on finding and collecting code coverage data

I have added an example of capturing code coverage data from gradle at : https://github.com/odpi/egeria/pull/5159
The challenge with a multi module project is aggregating the results. In maven this is particularly difficult - and would almost certainly be easier to do via a shell script post-build
Gradle is more flexible, and where we will likely focus future build improvements, so an initial implementation is added there
Still need to look at

[ ] setting up a merge gradle build
[ ] integration with external tools like codecov (upload a file to ? )
[ ] where else could we publish the results to
[ ] whether any other in-build processing could create a better build format
[ ] capturing data from FVTs
[ ] what we can/should do in maven

Recently I tried to add capture of code coverage data in FVTs (maven only) (above). This involved changing the configuration of the agent prep & report to surround the integration test phase, as opposed to unit tests.
However although I can see the java agent being prepared
[INFO] --- jacoco-maven-plugin:0.8.7:prepare-agent (agent) @ asset-consumer-fvt ---
[INFO] jacoco.argLine set to -javaagent:/Users/jonesn/.m2/repository/org/jacoco/org.jacoco.agent/0.8.7/org.jacoco.agent-0.8.7-runtime.jar=destfile=/Users/jonesn/IdeaProjects/egeria
.maven/open-metadata-test/open-metadata-fvt/access-services-fvt/asset-consumer-fvt/target/jacoco.exec

And then I can see that the exec plugin that is used to launch the server chassis is specifying the agent ie:
[INFO] --- process-exec-maven-plugin:0.9:start (chassis-start) @ asset-consumer-fvt ---
[INFO] arg: java
[INFO] arg: -javaagent:/Users/jonesn/.m2/repository/org/jacoco/org.jacoco.agent/0.8.7/org.jacoco.agent-0.8.7-runtime.jar=destfile=/Users/jonesn/IdeaProjects/egeria.maven/open-metad
ata-test/open-metadata-fvt/access-services-fvt/asset-consumer-fvt/target/jacoco.exec
[INFO] arg: -Dserver.port=10443
[INFO] arg: -Dloader.path=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/server/lib
[INFO] arg: -Dspringdoc.api-docs.enabled=false
[INFO] arg: -Djavax.net.ssl.trustStore=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/trus
tstore.p12
[INFO] arg: -Dserver.ssl.trust-store=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/trusts
tore.p12
[INFO] arg: -jar
[INFO] arg: ../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/server/server-chassis-spring-2.
11-SNAPSHOT.jar
[INFO] Full command line: java -javaagent:/Users/jonesn/.m2/repository/org/jacoco/org.jacoco.agent/0.8.7/org.jacoco.agent-0.8.7-runtime.jar=destfile=/Users/jonesn/IdeaProjects/eger
ia.maven/open-metadata-test/open-metadata-fvt/access-services-fvt/asset-consumer-fvt/target/jacoco.exec -Dserver.port=10443 -Dloader.path=../../../../../../open-metadata-distributi
on/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/server/lib -Dspringdoc.api-docs.enabled=false -Djavax.net.ssl.trustStore=../../../../
../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/truststore.p12 -Dserver.ssl.trust-store=../../../../../
../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/truststore.p12 -jar ../../../../../../open-metadata-distri
bution/open-metadata-assemblies/target/egeria-2.11-SNAPSHOT-distribution/egeria-omag-2.11-SNAPSHOT/server/server-chassis-spring-2.11-SNAPSHOT.jar
[INFO] Starting process: chassis-start
[INFO] Using working directory for this process: /Users/jonesn/IdeaProjects/egeria.maven/open-metadata-test/open-metadata-fvt/access-services-fvt/asset-consumer-fvt/target/classes
[ERROR] Picked up JAVA_TOOL_OPTIONS: --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED
[INFO]  Project Egeria - Open Metadata and Governance

The tests then run:
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 s - in org.odpi.openmetadata.accessservices.assetconsumer.fvt.execution.AssetConsumerOMASInvalidParamet
erIT
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0

And then the agent reports:
[INFO] --- jacoco-maven-plugin:0.8.7:report (report) @ asset-consumer-fvt ---
[INFO] Loading execution data file /Users/jonesn/IdeaProjects/egeria.maven/open-metadata-test/open-metadata-fvt/access-services-fvt/asset-consumer-fvt/target/jacoco.exec
[INFO] Analyzed bundle 'Asset Consumer OMAS FVT' with 5 classes
[INFO]

What we see is only 5 classes reported. That makes no sense, and on inspection we see in the csv file (this is generated by the report phase, alongside the .xml file which sonar uses):
$ cat ./access-services-fvt/asset-consumer-fvt/target/site/jacoco/jacoco.csv                                                               [9:15:57]
GROUP,PACKAGE,CLASS,INSTRUCTION_MISSED,INSTRUCTION_COVERED,BRANCH_MISSED,BRANCH_COVERED,LINE_MISSED,LINE_COVERED,COMPLEXITY_MISSED,COMPLEXITY_COVERED,METHOD_MISSED,METHOD_COVERED
Asset Consumer OMAS FVT,org.odpi.openmetadata.accessservices.assetconsumer.fvt.setup,AssetOwnerFactory,208,0,6,0,58,0,8,0,5,0
Asset Consumer OMAS FVT,org.odpi.openmetadata.accessservices.assetconsumer.fvt,AssetConsumerOMASFVTSuite,40,0,6,0,16,0,5,0,2,0
Asset Consumer OMAS FVT,org.odpi.openmetadata.accessservices.assetconsumer.fvt.clientconstructors,ClientConstructorTest,93,0,0,0,24,0,4,0,4,0
Asset Consumer OMAS FVT,org.odpi.openmetadata.accessservices.assetconsumer.fvt.errorhandling,InvalidParameterTest,150,0,0,0,50,0,7,0,7,0
Asset Consumer OMAS FVT,org.odpi.openmetadata.accessservices.assetconsumer.fvt.tagging,CreateTagTest,710,0,52,0,118,0,31,0,5,0

These look like the test driver tests, not the chassis. This is despite
a) The prepare agent only being done in the fvt phase, not ut.
b) The surefire plugin is not in use here
The problem here most likely is either

Since prepare agent is really only generating a cmd line, once it's run once, anywhere in the project, we'll probably get the same result each time
could it be that the file is being ovewritten due to test data being written by the failsafe plugin (not just sirefire)
but currently it's not clear what else should be using it

The possible approaches to fix might include

Use a unique filename for FVTs vs UTs - this makes the output much clearer
Ensuring test output is always appended to the file rather than replaced (in case of multiple use use?)
Use a unique, non-default variable name for all surefire tests (to ensure the agent configuration doesn't automatically leak into surefire without it being explicitly set)
.....

I have made a change to ensure

unique filenames for UT vs FVT
unique argline variable for surefire vs the server chassis

However the problem remains. (see my branch 'issue3969b')

See PR
Unable to get valid jacoco reporting (which is needed for sonar) even though jacoco binary file appears correct
More detailed analysis and test cases needed in case of any stack/plugin bugs, but inclined to suspend further work on the maven plugin and try with gradle instead (since we are moving that way).
Will leave open for now.

Attempt using maven attached. However this fails with maven exec plugin issues.
At this point I suggest we stick with gradle. Will add patch & then close the associated PR for now
Patch: https://gist.github.com/f39969518c00a0fc1bc9fc243ada4230

Looks like we already have an issue open on capturing code coverage data -- my super-quick scan suggests this still seems focused exclusively on jacoco and SonarCloud (?) Should we reach out to LF and see if there are other "standard" tools in the kit bag that we might leverage here (that might give more consistent / integrated outputs in GitHub directly)?

Yes - it's a good question. codecov seems most popular on github, but is paid-for (though some capabilities free) - so good question for LF.
There is a ci/cd workgroup, though it's been rather quiet. I'll start by asking there.

We should probably target the gradle build for fixing this, on the basis that is where we are moving to


Add optional support for the PROXY protocol

This adds support for the commonly implemented PROXY protocol, allowing TCP proxies to pass along upstream client information. When this is enabled gorouter will read the PROXY preamble and inject the upstream information into the X-Forwarded-For header.
http://blog.haproxy.com/haproxy/proxy-protocol/
It should be noted that when using PROXY on the HTTPS port the X-Forwarded-Proto header will not be set to "https" as expected because the X-Forwarded-Proto code checks for source.TLS, which is only set by the go http library if the conn is a tls.conn:
https://golang.org/src/net/http/server.go#L1398
This can only be fixed properly by patching the standard library. We plan to submit a separate gorouter patch to allow operators to override the autodetected X-Forwarded-Proto if they are terminating SSL at the load balancer before gorouter and using PROXY to communicate with gorouter.

This should close https://github.com/cloudfoundry/gorouter/issues/125

The build is failing due to Travis being slow and tests timing out, they pass when I run them locally.

It should be noted that when using PROXY on the HTTPS port the X-Forwarded-Proto header will not be set to "https" as expected

What is the behavior when using PROXY on the HTTP port? Your use case is an insecure private network. Since your SSL terminator is sending requests to port 80, would Gorouter detect the value of X-Forwarded-Proto using this PROXY protocol? If so, it seems like your "Force Proto" solution isn't necessary.

@shalako When the inbound connection is on port 80 the X-Forwarded-Proto header will be set to http unless the header is already set, in which case gorouter will leave it unmodified.
The PROXY protocol does not communicate the incoming protocol used, and the upstream proxy itself is not HTTP-aware so will not insert the X-Forwarded-Proto header.
The PROXY protocol does communicate the incoming port number, so it would be possible to automatically set X-Forwarded-Proto to https if the upstream port is detected as being the same as SSLPort, but unfortunately go makes it extremely difficult to get the local address in an HTTP handler, so implementing this would be extremely intrusive.

Yesterday upstream golang gained support for accessing the local address from a http handler, which would make my previous suggestion substantially easier to implement. Obviously this won't be possible until there's a new golang release though.

As commented here what is the decision for this PR?
Shall we go for the approach of an updated golang release which would allow implement logic to check if the upstream port the same as SSLPort?

@keymon @Jonty
Please confirm my understanding of the alternative you're suggesting

requires support for PROXY protocol
requires gorouter upgrade to newer version of golang (which version?)
upstream TLS-terminating component does not support sending X-Forwarded-Proto http header, but can send the port it received the request on
If gorouter receives a request that includes the port an upstream component received the request on, identified using the PROXY protocol, and this port is 443, then gorouter will set X-Forwarded-Proto: https in the request to backend

requires support for PROXY protocol

Yes, in order to get the original connection information from the first proxy (e.g. ELB in TCP mode)

requires gorouter upgrade to newer version of golang (which version?)

Yes, it is required to be able to check the port as described in @Jonty comment.
But as @Jonty pointed, it has been added and reviewed here, and you can see the github commit here. But it seems that the code has not been released yet.

upstream TLS-terminating component does not support sending X-Forwarded-Proto http header, but can send the port it received the request on

Yes, they send the port as part of the proxy protocol

If gorouter receives a request that includes the port an upstream component received the request on, identified using the PROXY protocol, and this port is 443, then gorouter will set X-Forwarded-Proto: https in the request to backend

exactly

@keymon @Jonty In terms of the X-Forwarded-Proto being set to https when the port is 443, I do not see how being able to find out the local address of the connection enables us to identify the upstream proxy was listening on port 443.
In the commit you mention, the context key is set to the l.Addr() value, which in the proxy protocol library you use in the PR will still return the local address of the gorouter, when one would want to check the destination port provided by the proxy header at the beginning of the connection. Let me know if I am missing something here.
Other than that, the PR looks fine code-wise.
@crhino && @flawedmatrix

@crhino go-proxyproto wraps the connection and replaces the connection local port with the one communicated via the PROXY protocol, which will be 443 (PROXY communicates the protocol version, source port, destination port, and remote IP address).

@Jonty : Thank you for submitting PR. We were wondering if you could provide an integration test to verify the support for Proxy Protocol.
Regards
@shashwathi  && @flawedmatrix

@flawedmatrix @shashwathi Is the test we implemented not sufficient?

@Jonty :
We were thinking more along the lines of an end-to-end test. After looking at the PR again, the given tests should do the job.
We are trying to deploy this on an AWS environment and verify it works as expected. Nothing more should be required from your end.
Regards
@shashwathi && @flawedmatrix

@Jonty :
We noticed an issue when we were testing this PR, gorouter does not seem accept multiple connections anymore.
Steps to reproduce this issue:

Enable proxy protocol on gorouter
Use telnet to establish a long lived connection to GOROUTER_IP:PORT
You can use curl or telnet to establish another connection to GOROUTER_IP:PORT. If you are using curl you will notice your request just hangs.

When you disable proxy protocol and repeat the above steps, you will see that the gorouter accepts multiple connections on its port.
We have a failing test case on a branch in gorouter to demonstrate the same. We think the problem might be in the proxyproto library, where listener which is a wrapper around http listener only accepts one connection at a time.
To solve this immediately, we will add a Known Limitations section in Gorouter README to warn the operators. In the meantime, could you please take a look at this?
Let us know if you have any questions.
Regards
@shashwathi

Hi @shashwathi, I'm one of @Jonty's colleagues.
This is definitely not intended behaviour & we'll take a look in the next few days.

@bleach There is an open PR that fixes this, however no work has been done to get it upstream: https://github.com/armon/go-proxyproto/pull/2
I would suggest that someone should take that and work with @armon to get it into master, rather than forking it.

I think that this issue happens only if:

you enable proxy protocol
and you get ONE connection which sends no data, which will block the Accept() call until some data is sent.

If you have a proxy sending Proxy Protocol prefixes in front of go-router it should not happen.
But it must be fixed, indeed.

As an update:

Indeed the http.Serve gets block in RemoteAddr() call until the Proxy Protocol or at least 6 bytes are sent (len('PROXY ') ).

On Go 1.6 this does not happen, I guess they changed the http server so it does not call RemoteAddr() immediately with the TCP connection. (link to change needed)

The branch armon/go-proxyproto#2 does NOT really solve this issue. Actually makes it worse because it blocks on Accept.

I opened a new issue #141 to track this. We propose a solution there.


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-bicep
Extension Version: 0.9.1
OS Version: Darwin arm64 21.6.0
VS Code version: 1.70.0

:warning: Make sure to attach this file from your home-directory:
:warning:file:///var/folders/cq/ph9fgfjd4wzgp_7vpqwl90gr0000gn/T/ms-azuretools.vscode-bicep-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

@erreyi - please could you upload the file from the error (/var/folders/cq/ph9fgfjd4wzgp_7vpqwl90gr0000gn/T/ms-azuretools.vscode-bicep-unresponsive.cpuprofile.txt).
If you don't want to share it publicly, feel free to email to me (antmarti at microsoft dot com)

Hi, attack the txt.
ms-azuretools.vscode-bicep-unresponsive.cpuprofile.txt

Here's what the profile looks like:

And the method in question:
// Copyright (c) Microsoft Corporation.
// Licensed under the MIT License.
const deployParamsPattern = new RegExp('.*"token":\\s*"(?<token>.*)"');
export function removePropertiesWithPossibleUserInfoInDeployParams(
  value: string
): string {
  const matches = deployParamsPattern.exec(value);

  if (matches) {
    const groups = matches.groups;

    if (groups) {
      const token = groups["token"];

      return value.replace(token, "<REDACTED: token>");
    }
  }

  return value;
}

The regex could be optimized (pre-compile, remove the ".*" from the beginning), although it seems unlikely to be causing serious performance issues.

@erreyi Does this happen frequently?  Was it a one-time event?  Thanks.


Maintenance of this project

Hi,
Firs of all this is an amazing project with great UI and speed.
However this project has been semi-abandoned basically and maintenance of it has sadly not kept up with it.
I would like to request to become a maintainer of this project for the community and implement bug fixes/features.
Currently, I have fixed quite a few of the issues in my own private fork of this repository maintained for my own website here: https://tracktak.com
The big issue with this project is the settings of features programmatically and not just on initialization which I can fix and the structure of the code needs converting from classes to functions/objects to stop inheritance hell.
We have the time to maintain this project for the community as we use it ourselves for our site.
I will also email you directly with this.
Thanks

you can pull requests

@myliang I'm not going to waste time doing pull requests and raising issues when there are over 212 open issues already and pull requests just left for dead with 0 comments or replies on them.
This is why this project has over 1.2k forks. Because it isn't being maintained well enough.


[Feature Request] document how to validate upload_multiple

Feature Request
What's the feature you think Backpack should have?
In https://backpackforlaravel.com/docs/4.1/crud-fields#upload_multiple
document that for upload_multiple, since the form field is an array, the laravel validation requires the field name followed by .* like so
$request->validate([
    'upload_multiple.*' => [ // field name note the .*
        'file',
        'min:1', 'max:2000', // file size in kiloBytes
        'mimes:jpg',
        'mimetypes:image/jpeg',
    ],
];

Schould be in Laravel-Backpack/Docs


Open source

Help me. Please

Help me make a JavaScript function for a website in an app designed by me open sourced


Request - add link from /collection to /search

Help us understand your request (check below):

[ ] search or data request (help with SQL or provide the specific fields you are trying to retrieve for your collection)
[ ] add a new Github user to the Arctos Users team
[ ] a new barcode series
[ ] a new term for data entry or management
[ ] a change or new report or label
[ ] update to an Agent (split, merge, or other type of change)
[ ] bulkload changes (to Agents, Identifiers, etc that are not already available as a bulkloading tool)
[x] new feature or otherwise a good idea to make Arctos even better
[ ] quarantine taxon name and suggested replacement (please supply links)
[ ] other

Describe what you're trying to do
Is there anyway to add a button the the collection page (e.g., https://arctos.database.museum/collection/OGL:Genomic) to point someone to searching that collection? We want to send people to the page that's metadata about the collection but then have a really obvious way to go look at our data rather than having to navigate the headers?

Love that this was added. At the risk of being très annoying, is there any chance that this can be a button? or in the header? Or something that makes it easier to find?


[WFLY-11363] fix HttpInvocationInContainerTestCase with secmgr

Issue: https://issues.jboss.org/browse/WFLY-11363

This one is not failing for me with the security manager enabled.


Installing this in Angular project

Hello, what are the steps to add this library to an Angular 2 application? Ideally I would like this to act as a module that I can load whenever I need it, not on the whole application.

@papakonstantinouko I'm currently having issues doing this as well. Can you tell me how you did it?

I have this under dependencies in package.json
"css-element-queries": "^0.4.0"
then in my component file I have these 2 lines underneath my imports
const RESIZE_SENSOR = require('../../../../node_modules/css-element-queries/src/ResizeSensor.js');
const ELEMENT_QUERIES = require('../../../../node_modules/css-element-queries/src/ElementQueries.js');
and the component implements AfterViewInit like this
ngAfterViewInit() {
ELEMENT_QUERIES.init();
}
and finally in the css I do things like this
li[min-width~="100px"] {
padding-top: 3px;
}
li[min-width~="290px"] {
padding-top: 13px;
}

@papakonstantinouko Thanks! Gonna try that : )


#5 - problem with flags - fix

Fix is only in bootstrap-select-country.js
It must also be loaded into *.min.js file, but i do not know how :)

released as v4.1.1


Errors installing/importing in python3.6

Hi Randall,
Thanks for putting this project together. I'm using python3.6 and attempting a plain install  python setup.py install and getting the following error:
File "build/bdist.macosx-10.5-x86_64/egg/compecon/quadrature.py", line 9
    def __init__(self, dist, *args):
                                   ^
SyntaxError: unexpected EOF while parsing

Weird as it is, it doesn't break the install. When I try to from compecon import Basis I get this error:
In [2]: from compecon import Basis
  File "/Users/btengels/Dropbox/Econ/VCS_Tengelsen/Book code/CompEcon-python-master/compecon/demos/setup.py", line 106
    fname = name + f'--{n+1:02d}.pdf'
                                    ^
SyntaxError: invalid syntax

Is this familiar at all?

Hi Ben,
Thank you for reporting these two issues.

quadrature.py file: you can safely delete it of comment out all of its content. I shouldn't have included it in the repository yet (it was just work in progress, to make an object-oriented version of the functions in the quad.py file. Sorry about that.

demos/setup.py file: I could not figure this out; in my PC it's working fine. Are you sure you are using Python 3.6? If not, the problem would be with the f-string, which is a new feature in 3.6. I'll try again to see if I can spot the cause of the problem.


feat(@angular/cli): set loaders to minimize

Loaders weren't being set to minimize in prod mode, as per https://webpack.js.org/guides/production/#the-manual-way.

The webpack documentation may be a little out of date.  debug and minimize are deprecated loader API properties and shouldn't be used by loaders.  CSS-loader still uses minimize but it should be disabled in that case anyway since the CLI controls minification directly.  The functionality is scheduled to be dropped from the next major version of the loader as well.

Thanks for the heads up @clydin 👍


Updated iOS Azure Communication Services Calling Hero Sample App Documentation

This PR contains updated instructions and documentation for the next release of the hero sample app.
The code change PR is here:
https://github.com/Azure-Samples/communication-services-ios-calling-hero/pull/116

@ddematheu2

Can you review this PR?
If you approve, please note that the commits will need to be moved to the private repo so we can use the staging and validation tools there. (you can move this yourself, but let us know if you need assistance)

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Serialize custom attributes

This change stores the custom attributes as strings instead of objects. This allows them to be converted in the inferencing step.
This change also adds a comma separated list as some entries into triples need to be stored in the same attribute for the same node.
Be aware that this PR has a few downsides.

It was necessary to get all custom attributes. There was not an easy way to do so. This ended up being a comparison of attribute name with the word "http". This could go wrong as a standard attribute can have http, and it would then be inference-ed back into the model and cause wrong knowledge.
A multi-key map was used to store and concatenate multiple values read from statement iteration. Key 1 is the RDF_Identifier of the node, and Key 2 is the predicate. The value is the object. This map is then used to add the required attribute values (comma separated) to the graph. This could be bad as there is no guarantee that the other custom attributes cannot have a comma within their value.
The above also means that if RDF_Identifier data is migrated to just Identifier, then this section of code should also be refactored to take that into account.

To test this change, I used the import from RDF plugin. I used the Attribute Editor to check the values within the custom attributes. I wanted to see a comma separated list on the items like "LaReine"@en.
I also wanted to ensure that once inferenced, the correct data went back into the model. I stepped with the debugger to ensure that the values were written correctly into the model again.
Potential downside:
I seen no possible way to make a statement with the same xml language tag <rdfs:label xml:lang="en">LaReine</rdfs:label> So in place of that, I have stored the item to look as follows (I think?): <rdfs:label>"LaReine"@en</rdfs:label>
constellation-app/constellation#840 (comment)

You need to call RDFUtilities.setLiteralValuesVertexAttribute(wg, literalToValue); it in the edit method of the RDFSInferencerPlugin as well. Maybe now we need a better way to pass few maps without affecting method signatures.

I've made the change @Auriga2


added check for bind on create to determine local volume driver

Signed-off-by: Clinton Kitson<EMAIL_ADDRESS>

This patch fixes the issue https://github.com/docker/docker/issues/15467. Ping @calavera
The fix is to check what binds are specified and to only specify the selected volume driver when a bind is specified. Otherwise the default "local" volume driver is used.
For any volume that is specified in the Dockerfile but not binded, the "local" volume driver is used regardless.
It also ensures that contents of a container FS only attempt to be copied under the "local" volume driver scenario. I believe it is assumed that attached container volumes have persistent data and thus should not be overwritten by an initialization process.

This needs tests. We have a constant for the local driver in the volumes package, please use it.

Ok, thanks for reviewing.  Will do.

Question for you here @calavera.  As far as testing this, would you assume that integration-cli testing would suffice?  If so, it seems like creating a Dockerfile on the fly with a volume with data and then making a container from it to be tested with would be appropriate to test with?

yes, that sounds like a good plan. We already have tests that generate images on the fly in integration-cli, like in the tests for docker rm, but there are others. Feel free to copy the behavior in one of them.

@calavera this works, but still needs some cleanup.  Passing it here to see if the method seems right.
Struggled through a bit to be able to get a container with a file at the right daemon.  I think creating this via an echo command in the Dockerfile seems legitimate.  The buildImage functions could use the args params to allow passing of the correct daemon socket.

The error condition is
[d92493071] waiting for daemon to start
[d92493071] daemon started
docker_cli_start_volume_driver_unix_test.go:278:
    c.Assert(s.ec.creations, check.Equals, 1)
... obtained int = 2
... expected int = 1

Updated based on comments.

@calavera Notable change here is to include the image config directly with volumes defined as to whether to flip the default volume driver.

Removed debugging statements.

LGTM

LGTM

One problem with this is, the data was only being copied IF the volume was empty, so there was no persistent data anyway.

(we were just discussing this)
Basically, that change makes it impossible to replace the built-in volume driver ('local') with an alternative, and keep the same behavior.


feat: add sso pkce

What kind of change does this PR introduce?
Adds support for PKCE to the SSO flow

We don't introduce a foreign key since we can have relay states which use the implicit flow and won't have an associated  flow state. The

How this was tested:

On staging with Okta as IDP, on an instance with the branch version of GoTrue uploaded

GoTrue-js PR:

https://github.com/supabase/gotrue-js/pull/707

We don't introduce a foreign key since we can have relay states which use the implicit flow and won't have an associated flow state

btw, you can have a foreign key on the auth.relay_states.flow_state_id with default NULL

You’re right, let me amend

Hi, when using signInWithSSO with PKCE with Next.js you get redirected with the access_token in the URL hash but the session is not saved automatically and nothing happens
When will this PR land approximately? Thank you for the great work!

Hey @remorses,
Thanks for the query - I'll be patching the PR and sending it for re-review later today.

Oh as an update on having a fkey with default null. I looked again and realized that the column is a UUID and can't be set to null so going to go without a foreign key.
Let me know if anyone has other suggestions though.


Guard against crashes in docker list commands

The docker container list command seems to not be atomic and crashes whenever the container is pruned during its runtime:
Traceback (most recent call last):

  File "/usr/local/lib/python3.10/site-packages/docker/api/client.py", line 268, in _raise_for_status

    response.raise_for_status()

  File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status

    raise HTTPError(http_error_msg, response=self)

requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/993075dc249f1533cf36f52a473838ab0dd26b67bc5559712a8aba697097e172/json

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

  File "/opt/events-notifier/./network_exporter_prom.py", line 205, in <module>

    watch_networks()

  File "/opt/events-notifier/./network_exporter_prom.py", line 135, in watch_networks

    for container in client.containers.list(all=True):

  File "/usr/local/lib/python3.10/site-packages/docker/models/containers.py", line 988, in list

    containers.append(self.get(r['Id']))

  File "/usr/local/lib/python3.10/site-packages/docker/models/containers.py", line 924, in get

    resp = self.client.api.inspect_container(container_id)

  File "/usr/local/lib/python3.10/site-packages/docker/utils/decorators.py", line 19, in wrapped

    return f(self, resource_id, *args, **kwargs)

  File "/usr/local/lib/python3.10/site-packages/docker/api/container.py", line 783, in inspect_container

    return self._result(

  File "/usr/local/lib/python3.10/site-packages/docker/api/client.py", line 274, in _result

    self._raise_for_status(response)

  File "/usr/local/lib/python3.10/site-packages/docker/api/client.py", line 270, in _raise_for_status

    raise create_api_error_from_http_exception(e) from e

  File "/usr/local/lib/python3.10/site-packages/docker/errors.py", line 39, in create_api_error_from_http_exception

    raise cls(e, response=response, explanation=explanation) from e

docker.errors.NotFound: 404 Client Error for http+docker://localhost/v1.41/containers/993075dc249f1533cf36f52a473838ab0dd26b67bc5559712a8aba697097e172/json: Not Found ("No such container: 993075dc249f1533cf36f52a473838ab0dd26b67bc5559712a8aba697097e172")

We should the script resilient against this as well as the same case for networks - we already did this for services.

Not doing it for networks for now. docker client has an option to ignore failures via ignore_removed


[NEW ICON] TailwindCSS, Drupal

Skill Name
TailwindCSS, Drupal
Why?
Tailwind CSS is an open source CSS framework. The main feature of this library is that, unlike other CSS frameworks such as Bootstrap, it does not provide a series of predefined classes for elements such as buttons or tables.
Drupal is a free, open-source content management system published under the GNU General Public License and written in PHP. It enables websites to be created and maintained faster and more efficiently than conventional HTML/CSS programming.
Reference Image
TailwindCSS :

Drupal :

Sorry, I didn't see tailwind, but still relevant for drupal :)


profile: Fix glitch when exiting custom profile display UI.

Fixes: #9702.
GIF:

@shubhamdhama can you talk about how this works and why we should be confident this won't create problems with other modals?  E.g. why is 50% correct?

@timabbott
Three-point we should understand:

First this applies to hidden modals only because for visible .in containing modal this is overridden.
We have  transform: translateY(-50%);  so all the positioning will be done according to the center of modal.
When we close modal first it moves negative top of the screen and then it hides.

For most of modal top: -25% is more than the whole height of modal but here the modal is so large that the remaining part of modal  is visible to us i.e. Height of modal > 25% screen. And this remaining causes glitch. But having set it to -50% is just equivalent to moving it to the same position in a screen of the same size but it negative top(kinda parallel universe :).
This is my understanding and visualization of the issue, hope this makes sense.

I should add this to commit message if this makes sense.

OK, that's what I was imagining.  Merged as ed7373febb2212c6f0a79279dbb40ed7bad4a447, after adding a brief comment explaining that detail.  Could also be good to have the longer explanation in the commit message.  To provide a bit of reasoning here:

Anything that answers the question "why does this code do this strange thing" best belongsin a code comment, since that's what'll be most visible to folks reading the code later.
Anything that explains "why did we make this change" or "what research or reasoning was done to determine this code (change) is correct" generally belongs in the commit message.  This is really valuable for folks trying to understand whether changing the code later will break something, but is much more buried than code comments (but also adds much less clutter).

Both are really valuable for saving reviewers time guessing why you did something :)


Turn off over active alerts in Dev and Test

CPU alerting and memory utilization alerts are over active on the Test and Dev environments. These environments are used locally and do not effect users other then our team.

[ ] Turn off CPU alerting and memory utilization in test and dev

PR: https://github.com/CDCgov/prime-simplereport/pull/1149

Deployed to dev/test


Stop people from following themselves

You can follow yourself through your own feed on your own market -> three dot button.
This PR should now return an error if you try to do that.

we should also remove it as an option from the menu on the frontend on your own profile!

addressed by 477e5d8 so closing


Added Czech translation

I have slightly renamed the preset modes. English equivalent would look like this:
Auto -> Automatic
Silent -> Night
Favorite -> Manual
The used terms are from Czech manual at page 4

Thanks for contributing!


vdk-control-cli: Expand missing resource error message

In the case when a user creates a job in the control service with
a given team name, then changes the team name in the job's config
file, the message printed is not clear enough.
The message was expanded to inform the user of the aforementioned
possible issue. This approach was chosen over checking for this
issue specifically, as that approach would have required changes
to both vdk-control-cli and the control-service and would have
required much longer development time.
Closes #605
Testing done: following reproduction steps found in #605 and
verified message is printed
Signed-off-by: Gabriel Georgiev<EMAIL_ADDRESS>

That's good. change, as it makes the generic not found message a bit more helpful.
but in the ticket https://github.com/vmware/versatile-data-kit/issues/605 I have a more bold goal. I'd like that the control service returns exactly what is not found (not generic 404) but it would say "No job with that name", "no such team exists" . So please keep the ticket open.


Cannot Connect To Telethon

telethon was working fine but suddenly when i try connect to telethon using client.connect() or client.start() I get the following error
WARNING:telethon.network.mtprotosender:Connection error 5 during auth_key gen: ConnectionError: Not connected
INFO:telethon.network.connection.connection:<class 'OSError'> during disconnect: [WinError 121]The semaphore timeout period has expired
Could anyone help me please..
I am using Telethon from yemen..windows8
I Updated Telethon Version to 1.23.0 and the problem unsolved
I Updated pip Version to 21.3.1 and the problem unsolved
python Version 3.8.6

Could you show us the code you use to connect with Telethon? What arguments you pass to client = TelegramClient(...)?


Fixing the endless loop during skyux watch.

Codecov Report

Merging #479 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #479   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          53     53
  Lines        1642   1642
  Branches      241    241
=====================================
  Hits         1642   1642

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

config/karma/shared.karma.conf.js
100% <ø> (ø)
:arrow_up:

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 6614bd9...cb81c43. Read the comment docs.


drivers: can: add accessor for the CAN bit error counter

Add accessor function for the CAN bit error counter.
This was missed in #63733 since #63432 was merged the same day.

@alexanderwachter, @karstenkoenig, @str4t0m: Please review

Thanks, both!


another Unix workbencher for the guestbook

The Ch6 Markdown example includes the command nano README.md and suggests that the example text should be copied and pasted into README.md in nano. The command is not part of the text to be copied and seems redundant here given the instructions.
This follows a feedback suggestion that I made through the Coursera page (I see my other two suggestions are already addressed).

Thank you!


Add developer note

Hi,
I really like the project you have put together. I just wanted to share with you a little trouble I ran into when using this solution.
The "standard" webconfig setting is
<handlers>
	<add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />
</handlers>

but it seems this doesn't work with the routering. It needs to have an extra "*"
<handlers>
	<add name="ExtensionlessUrlHandler-Integrated-4.0" path="*.*" verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />
</handlers>

Maybe, it would be nice to have a little section in the readme file or something. Just a thought. Hope this helps out someone else.

Thanks for the feedback! I remember running into this issue but neglected to document it.
Do you think it would make sense to add a Powershell script to add this to the web.config? I think it probably only applies if one is using IIS ...

Yeah, I think that PS is overkill in this case. Just a simple, notes or gotcha section would be fine. Devs are smart enough to figure it out.


chore: upgrade to node18

Overview
Upgrades dependencies to avoid incompatible peer dependencies on node > 14.x
Updates pipelines to use node 18.x or 18.16.x
Closes #2670
Notes
Open question, should we add an engines section to package.json to make the supported node version explicit?
Currently this set of dependencies appears to build, run, and test correctly on node v14 - v20
Testing Instructions
There are currently a few tests that are failing, as they are when running on node 14, it's just that now they are detected as the failures are inside async operations, which Jest can't detect and report on properly when running on node 14
@Onokaev are you able to take a look at the test failures we're getting on this PR and address them, I don't have enough context for the AuthenticationWrapper tests

Yeah. Sure. Let me take a look at the tests


'update_varmap!' not being used

In line 207 in pde_system_transformation.jl, the function update_varmap! is used but has not been imported from PDEBase and so an error is caused.

Can you post the error and code to reproduce?

I used the code:
using Plots, MethodOfLines, DomainSets, ModelingToolkit
@variables u(..) f(..)
@parameters t θ λ P
dθ = Differential(θ)
dθθ = Differential(θ)^2
dθθθθ = Differential(θ)^4
dt = Differential(t)
dtt = Differential(t)^2
function δ(θ)
return 1/1000sqrt(2π) * exp(-θ^2/(21000^2))
end
Iθ = Integral(θ in DomainSets.ClosedInterval(-1.0,1.0))
eq = [
dtt(u(t,θ)) ~ -dθθθθ(u(t,θ)) + λ^2 * dθ(f(t,θ) - u(t,θ) +0.5dθ(u(t,θ))^2dθ(u(t,θ)))+λ^2 * (f(t,θ) - u(t,θ) +0.5dθ(u(t,θ))^2)+Pδ(θ), 0 ~ Iθ(f(t,θ))
]
bcs = [
u(t,-1.0) ~ 0.0, u(t,1.0) ~ 0.0,
dθ(dθ(u(t,-1.0))) ~ 0.0, dθ(dθ(u(t,1.0))) ~ 0.0,
dθ(f(t,-1.0)) - dθ(u(t,-1.0)) ~ 0.0, dθ(f(t,1.0)) - dθ(u(t,1.0)) ~ 0.0,
u(0.0,θ) ~ 0.0, dt(u(0.0,θ)) ~ 0.0
]
domains = [t ∈ (0.0,50.0),
θ ∈ (-1.0,1.0)]
@named pde_sys = PDESystem(eq, bcs, domains, [t,θ], [u(t,θ),f(t,θ)])
discretisation = MOLFiniteDifference([θ => 100],t)
prob = MethodOfLines.discretize(pde_sys, discretisation)
and got the error message:
ERROR: UndefVarError: update_varmap! not defined
I manually changed the export line in pde_system_transformation.jl, and also had to manually copy over the function get_ops but this resolved the issue on my machine.

I have the exact same problem with a stationary 1D pde:
using MethodOfLines,DomainSets,NonlinearSolve,ModelingToolkit
@parameters  x
@variables u(..)
Dxx = Differential(x)^2
Dx = Differential(x)
D=0.1
L=5
eq= -Dx((x-x^3)u(x))  +DDxx(u(x)) ~ 0
bcs = [u(-L) ~ 0,u(-L)~ 0]
domains = [x ∈ Interval(-L, L)]
@named pdesys = PDESystem(eq, bcs, domains, [x], [u(x)])
dx = 0.1
discretization = MOLFiniteDifference(x => dx, approx_order=2)
prob = discretize(pdesys, discretization)
it works fine in 2D spatial dimension


Python setup with Homebrew on Mac

brew unlink python[version]  to unlink homebrew linking to your old version of python. Then install or upgrade the version of your python. Then run:
brew link python[version] to link to the new version.

The underlying issue here was with f-strings, which are no longer used in any of the install scripts' dependencies.


Scheduled Tasks behave unexpectedly

Used Version: User v6.0.0-Early Access 1
Installation: Manual Installation on a local system
System: Linux CentOS 7
PHP-Version: PHP 7.2.14RC1
Web-Server:  Apache 2.4.37, PHP-FPM
Database: MariaDB-10.2.21
I've been trying to set up scheduled Tasks in a Plugin. I've followed the steps at: https://docs.shopware.com/en/shopware-platform-dev-en/how-to/scheduled-tasks?category=shopware-platform-dev-en/how-to but could not seem to make it work. Upon further investigation in the database, I discovered some strange behaviour while monitoring the scheduled_task table.
When using the Administration backend under Plugins, then ACTIVATING the Plugin with a scheduled task, the database table does not update. BUT when DEACTIVATING the Plugin with a scheduled task, the database table does an update and includes the scheduled task of the plugin and runs it once.
Since I wasn't sure whether or not I made an error in my plugin structure, I decided to test the same procedure with your provided Example Plugin at https://github.com/shopware/swag-docs-scheduled-task-plugin .
To make it easier to track I only altered the MyTaskHandler.php::run function and added a simple error_log("Hello World"); instruction to it. - The same phenomenon happened.
Steps I have done to make this issue occur:

Install and Configure a Shopware 6 installation
Fetch Plugin from https://github.com/shopware/swag-docs-scheduled-task-plugin
Place Plugin to /custom/plugins
Initiate Command /bin/console plugin:refresh
Install Plugin in Admin Backend
Activate Plugin in Admin Backend (No Scheduled Task in Database)
Deactivate Plugin in Admin Backend (Scheduled Task in Database, but only 1 execution)
Activate Plugin in Admin Backend (Scheduled Task disappears from Database)
.....

I didn't have time to test it on a separate server installation yet.
Maybe I did a crucial mistake in the order of execution here, or I found a bug in how scheduled tasks are handled. Either way I would be delighted to hear back from you.

Thank you for your detailed report.
I've looked into the issue and you've found a bug indeed. I have created a Ticket for it. You can follow it through our issue tracker:
https://issues.shopware.com/issues/NEXT-4343


PAB-400: add migration framework and initial migration

Change description
Add migration framework and initial migration

[x] Unit tests and other appropriate tests added or updated
[x] README and other documentation has been updated / added (if needed)
[x] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

How to test
Steps in README should work locally
Note will need to be merged alongside sister PR: https://github.com/communitiesuk/funding-service-design-post-award-docker-runner/pull/8
Screenshots of UI changes (if applicable)

@cyrusdobbs I don't believe it breaks local development using sqlite, but feel free to check-out the branch and verify for yourself?

@cyrusdobbs I don't believe it breaks local development using sqlite, but feel free to check-out the branch and verify for yourself?

It did break because db.create_all() was never called so the tables weren't built. I've added:
        with flask_app.app_context():
            db.create_all()

to app.py that's called if sqlite is in the DB URI


Poisson GLM

Hi,
Suppose that I'd like to fit a constrained Poisson GLM using CVXR, much like the logistic regression example in the documentation.
The program does not seem to optimize the function using either maximum likelihood formulation
    ## MWE
    library(CVXR)
    y <- rpois(n=100, lambda=50)
    X <- matrix(rnorm(100), ncol=1)
    betaHat <- Variable(1)
    obj <- sum(y* log(exp(X %*% betaHat)) - exp(X %*% betaHat))
    prob <- Problem(Maximize(obj))
    result <- CVXR::solve(prob)

or a Poisson loss formulation
    obj <- mean(exp(X %*% betaHat) - y * log(exp(X %*% betaHat)))
    prob <- Problem(Minimize(obj))
    result <- CVXR::solve(prob)

returning the error Error in construct_intermediate_chain(object, candidate_solvers, gp = gp) :    Problem does not follow DCP rules. However, the problem does follow DGP rules. Consider calling this function with gp = TRUE. Setting gp=TRUE gives an opposite error.
Am I overlooking something?

Not sure what you are trying to do with the logs/exp in the objective. See below. Both ways will yield the same result.
> y <- rpois(n=100, lambda=50)
> X <- matrix(rnorm(100), ncol=1)
> betaHat <- Variable(1)
> obj <- sum(y* X %*% betaHat - exp(X %*% betaHat))
> prob <- Problem(Maximize(obj))
> result <- CVXR::solve(prob)
> result$getValue(betaHat)
[1] 1.496695
> obj <- mean(exp(X %*% betaHat) - y * X %*% betaHat)
> prob <- Problem(Minimize(obj))
> result <- CVXR::solve(prob)
> result$getValue(betaHat)
[1] 1.496695

I see, that's useful. Many thanks!


tx power adv

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hi Espressif engineer ,
i work with the example of "gatts_demo" -ble
board: evk esp32-c3-devkitm-1
I succeed in changing the tx power with the func but if I see with NRF app what is the advertisement of the tx power is always 9dbm
even if change the to 18dbm or 0 dBm and with my spectrum analyzer I verify that it's really transforming the power tx but in the app I always see 9dm
thanks

Seems duplicate of https://github.com/espressif/esp-idf/issues/9780


[REQUEST] Add openvdb/GridFwd.h (and friends?) providing forward declarations.

Is your feature request related to a problem? Please describe.
Being nearly all headers, OpenVBD is expensive to #include. There are places I pass around OpenVDB classes where I'd like to be able to just have them forward-declared so I can name them.
Using -ftime-trace on clang, and speedscope or chrome://tracing to view, I'm seeing over a second to #include <openvdb/Grid.h>.
Describe the solution you'd like
Something like openvdb/TypesFwd.h or openvdb/GridFwd.h or openvdb/openvdbFwd.h containing forward-declarations of at least the named grid types... So to get MaskGrid
#include <cstdint>

using Index32 = std::int32_t;

using Index   = Index32;
template<typename T, Index Log2Dim>
class LeafNode;

template<typename _ChildNodeType, Index Log2Dim>
class InternalNode;

template<typename ChildType>
class RootNode;

template<typename _RootNodeType>
class Tree;

class ValueMask;

namespace tree {
template<typename T, Index N1=5, Index N2=4, Index N3=3>
struct Tree4 {
    using Type = Tree<RootNode<InternalNode<InternalNode<LeafNode<T, N3>, N2>, N1>>>;
};
}

using MaskTree     = tree::Tree4<ValueMask,   5, 4, 3>::Type;
template<typename> class Grid;
using MaskGrid     = Grid<MaskTree>;

Describe alternatives you've considered
In my own codebase I've done
// This is inherited rather than a using declaration so we can forward-declare it elsewhere.
struct VolumeGrid : openvdb::MaskGrid {
    using openvdb::MaskGrid::MaskGrid;
};

instead of using VolumeGrid = openvdb::MaskGrid; to allow me to forward-declare VolumeGrid.
Additional context
Beyond this, since Grid is really a shared pointer to a tree, it may be possible to reduce what Grid.h includes (or add a GridMinimal.h) which defines Grid but doesn't include tree or much else.

LMK if this is interesting and the degree of granularity we'd want and I'll consider doing it. I can see a few different approaches:

Just one big openvdbFwd.h that forward-declares everything.
Enough forward-declaration so openvdb/Grid.h defines Grid but only forward-declares tree types.
Several separate ones: TypesFwd.h that declares the basic types like scalars, points, and bboxes, TreeFwd.h that declares the tree types, GridFwd.h that includes TreeFwd.h, foward-declares the Grid template, and all of the common named grid types.

Hey @BenFrantzDale yeah there was interest in this last TSC meeting. The scope was to:
Introduce "openvdbfwd.h" which contains forward declarations for all native openvdb Grid and Tree types. Implicitly, this will also include any forward declarations for any types necessary for these Grid/Tree types.
Once we see what that looks like and what that requires we'll have a better idea of what else needs to exists to support it.

Has there been any movements on this?
PS: @BenFrantzDale congrats on the issue number 🤓


Added initial snippet support for VSCode

I have add some support for snippets, and added "class" and "include" snippets.

Note there is a Snippet folder for ST
which includes a snippet for INC and CLASS
there are more snippets as well
FWIW, I use ODS & VAR snippets dozens of times a day
Is there a way to use the same files for both VSCode and ST ?

@MarkGoldberg They are not compatible, however your question brought me across this tool: https://www.npmjs.com/package/convert-snippets-to-vscode
So I have ran this against the snippets created for sublime and included them in my next pull request.


Illegal argument in isolate message : (object is a regular Dart Instance)

I want to use another isolate to do the cost-time task. Because the task is depended on some flutter api, so I use FlutterEngineGroup to create the default engine(A), and then create another engine(B) also with the same FlutterEngineGroup. Then I exchange the SendPort of A、B to each other。When I use SendPort to send my TestClz Object from A to B on Debug-mode, it goes wrong：
Invalid argument(s): Illegal argument in isolate message : (object is a regular Dart Instance)

Profile and Release works. And It's also ok when send TestClz from B to A.
But if I use the isolate.spawn instead of FlutterEngineGroup to create new isolate, It works perfectly, both A -> B and B -> A  are ok.
So, I am confused on

the different between Using FlutterEngineGroup to create isolate And Using isolate.spawn
why B -> A is ok, but A -> B not.
why profile and release mode are ok

SouceCode
Override FlutterActivity to use FlutterEngineGroup to create engines.
public class MainActivity extends FlutterActivity {

    private static FlutterEngineGroup engineGroup;
    private static FlutterEngine lonerEngine;

    @Override
    protected void onCreate(@Nullable Bundle savedInstanceState) {
        if (engineGroup == null) {
            engineGroup = new FlutterEngineGroup(getApplicationContext());
        }
        super.onCreate(savedInstanceState);
    }

    @Nullable
    @Override
    public FlutterEngine provideFlutterEngine(@NonNull Context context) {
        return engineGroup.createAndRunDefaultEngine(this);
    }

    @Override
    public void configureFlutterEngine(@NonNull FlutterEngine flutterEngine) {
        GeneratedPluginRegistrant.registerWith(flutterEngine);
        if (lonerEngine == null) {
            DartExecutor.DartEntrypoint dartEntrypoint = new DartExecutor.DartEntrypoint(
                    FlutterInjector.instance().flutterLoader().findAppBundlePath(),
                    "lonerMain"
            );
            lonerEngine = engineGroup.createAndRunEngine(getApplicationContext(), dartEntrypoint);
        }
    }
}

datastruct to send:  TestClz
class TestClz {
  final int a;
  final int b;
  TestC(this.a, this.b);
}

main.dart

@pragma('vm:entry-point')
void lonerMain() {
  SendPort? _loner2mainSendP = IsolateNameServer.lookupPortByName('mainIsolatePort');
  ReceivePort _main2lonerReceiveP = ReceivePort('lonerReceiver');
  _main2lonerReceiveP.listen((msg){
    print('receive msg: $msg');
  });
  _loner2mainSendP?.send(_main2lonerReceiveP.sendPort);
}

void main() {
  runZonedGuarded<Future<void>>(() async {
    WidgetsFlutterBinding.ensureInitialized();

    ReceivePort _main2lonerReceiveP = ReceivePort('mainReceiver');
    _main2lonerReceiveP.listen((msg){
      if (msg is SendPort) {
        SendPort sp = msg;
        try {
          sp.send(TestClz(1, 2));
        } on ArgumentError catch(e) {
          print(e);  // Invalid argument(s): Illegal argument in isolate message : (object is a regular Dart Instance)
        }
      }
    });
    IsolateNameServer.registerPortWithName(
        _main2lonerReceiveP.sendPort, 'mainIsolatePort');

    runApp(MyApp());
  }, (Object error, StackTrace stackTrace) {
//    _reportError(error, stackTrace);
  });
}

Flutter doctor
[✓] Flutter (Channel stable, 2.5.3, on macOS 11.5.2 20G95 darwin-arm, locale zh-Hans-CN)
    • Flutter version 2.5.3 at /Users/xxx/Desktop/SDK/fvm/2.5.3
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (1 year ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/xxx/Desktop/SDK/android-sdk-macosx
    • Platform android-32, build-tools 32.0.0
    • ANDROID_HOME = /Users/xxx/Desktop/SDK/android-sdk-macosx
    • ANDROID_SDK_ROOT = /Users/xxx/Desktop/SDK/android-sdk-macosx
    • Java binary at: /Users/xxx/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.2.1, Build version 13C100
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/xxx/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

You can only send specific types through a SendPort. Consider converting your class to a Map and sending that instead.
https://api.dart.dev/stable/2.18.3/dart-isolate/SendPort/send.html

Hello @joechan-cq. I noticed you're using an older version of Flutter from your doctor output (2.5.3). Could you confirm if this issue is still prevalent in that latest stable (3.3.5)?

Hello @joechan-cq. I noticed you're using an older version of Flutter from your doctor output (2.5.3). Could you confirm if this issue is still prevalent in that latest stable (3.3.5)?

I try it on flutter 3.3.6, it works.
If possible, may i ask for the reason?
@exaby73

@joechan-cq Glad it works :) I couldn't tell you exactly what fixed this issue as there has been a lot of PRs merged since 2.5.3


DbContext prematurely disposed when used in a payload type

Is there an existing issue for this?

[x] I have searched the existing issues

Describe the bug
(Dead-simple repro: https://github.com/aradalvand/hc-dbcontext-disposed)
Given this configuration:
builder.Services.AddPooledDbContextFactory<AppDbContext>(o =>
    o.UseInMemoryDatabase("test")
);

builder.Services.AddGraphQLServer()
    .AddMutationType<Mutations>()
    .AddProjections()
    .RegisterDbContext<AppDbContext>(DbContextKind.Pooled);

And this mutation:
public class Mutations
{
    public CreateProductPayload CreateProduct(AppDbContext db, CreateProductInput input)
    {
        Product product = new()
        {
            Title = input.Title,
        };
        db.Add(product);
        db.SaveChanges();

        return new(
            Success: true,
            Product: db.Products.Where(p => p.Id == product.Id)
        );
    }
}

public record CreateProductInput(
    string Title
);
public record CreateProductPayload(
    bool Success,
    [property: UseSingleOrDefault]
    [property: UseProjection]
    IQueryable<Product> Product
);

When I run the createProduct mutation and request the product field, an exception is thrown complaining about the DbContext instance having been disposed.
Steps to reproduce

Run git clone https://github.com/aradalvand/hc-dbcontext-disposed
Run dotnet restore
Run dotnet run
Send the following query to the GraphQL server:

mutation b {
  createProduct(input: {
    title: "Test"
  }) {
    success
    product {
      id
    }
  }
}

You'll get the following response:

{
  "errors": [
    {
      "message": "Unexpected Execution Error",
      "locations": [
        {
          "line": 13,
          "column": 3
        }
      ],
      "path": [
        "createProduct",
        "product"
      ],
      "extensions": {
        "message": "Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.\nObject name: 'AppDbContext'.",
        "stackTrace": "   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()\n   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()\n   at Microsoft.EntityFrameworkCore.DbContext.Microsoft.EntityFrameworkCore.Internal.IDbContextDependencies.get_StateManager()\n   at Microsoft.EntityFrameworkCore.Query.QueryContextDependencies.get_StateManager()\n   at Microsoft.EntityFrameworkCore.Query.QueryContext.InitializeStateManager(Boolean standAlone)\n   at Microsoft.EntityFrameworkCore.InMemory.Query.Internal.InMemoryShapedQueryCompilingExpressionVisitor.QueryingEnumerable`1.Enumerator.MoveNextHelper()\n   at Microsoft.EntityFrameworkCore.InMemory.Query.Internal.InMemoryShapedQueryCompilingExpressionVisitor.QueryingEnumerable`1.Enumerator.MoveNextAsync()\n   at HotChocolate.Data.Projections.SingleOrDefaultMiddleware`1.InvokeAsync(IMiddlewareContext context)\n   at HotChocolate.Data.Projections.SingleOrDefaultMiddleware`1.InvokeAsync(IMiddlewareContext context)\n   at HotChocolate.Utilities.MiddlewareCompiler`1.ExpressionHelper.AwaitTaskHelper(Task task)\n   at HotChocolate.Execution.Processing.Tasks.ResolverTask.ExecuteResolverPipelineAsync(CancellationToken cancellationToken)\n   at HotChocolate.Execution.Processing.Tasks.ResolverTask.TryExecuteAsync(CancellationToken cancellationToken)"
      }
    }
  ],
  "data": {
    "createProduct": {
      "success": true,
      "product": null
    }
  }
}

What should happen instead:
Maybe you should defer the disposal of the DbContext instance until after the whole field sub-tree has finished executing, I'm not sure though. Let me know if there's a standard workaround.
Product
Hot Chocolate
Version
12.12.1

Update: I just found out that I could do the following as a workaround:
public class Mutations
{
    public CreateProductPayload CreateProduct(AppDbContext db, CreateProductInput input)
    {
        Product product = new()
        {
            Title = input.Title,
        };
        db.Add(product);
        db.SaveChanges();

        return new(
            Success: true,
            ProductId: product.Id
        );
    }
}

public record CreateProductInput(
    string Title
);
public record CreateProductPayload(
    bool Success,
    [property: GraphQLIgnore]
    int ProductId
)
{
    [UseSingleOrDefault]
    [UseProjection]
    public IQueryable<Product> GetProduct(AppDbContext db)
    {
        return db.Products.Where(p => p.Id == ProductId);
    }
}

Now it works perfectly and no longer throws an exception.
Just wanna make sure you approve of this workaround? Is this fine?

The behavior is as intended. The context is preserved per resolver pipeline. Essentially we dispose at the end of a resolver pipeline.

We created a youtube episode on middleware:
https://www.youtube.com/watch?v=Ut33sSTYmgw
Its not specifically about the data middleware but explains how these pipelines work.


CMake fails due to upstream refactoring of sysdig project structure

Describe the bug
cmake fails due to refactoring in the default branch of the upstream sysdig repository. This appears to to related to a general project cleanup/migration, introduced by https://github.com/draios/sysdig/commit/4342ff7671aa621a0c61ba6d9ebedec43b0e99da.
CMake Error at CMakeLists.txt:29 (add_executable):
  Cannot find source file:

    ../sysdig/driver/dynamic_params_table.c

  Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
  .hpp .hxx .in .txx

CMake Error at CMakeLists.txt:29 (add_executable):
  No SOURCES given to target: pdig

CMake Generate step failed.  Build files cannot be regenerated correctly.

Environment

OS:

NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.12.1
PRETTY_NAME="Alpine Linux v3.12"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

Installation method:
From source.

Indeed it's still active.
It's in the backlog :)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Frosted glass effect in css #7282

Description 📜
added the steps to get the frosted glass effect in CSS along with a description.

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[x] Frontend Dev HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Great work. Just check this at the end of the doc:

I was trying to add a footnote..should I remove it?

Great work. Just check this at the end of the doc:

I was trying to add a footnote..should I remove it?

here it is

Great work. Just check this at the end of the doc:

I was trying to add a footnote..should I remove it?

 here it is

ok

Great work @khush2706 keep contributing 🎉🎉

Great work @khush2706 keep contributing 🎉🎉

Thank you so much!😊


[discuss] remove name resolver factory from ClientBuilder

As today we have the possibility to set the name resolver factory on the client builder but it may be better to determine the resolver to use based on the scheme used for the endpoints so i.e.
    // Use the simple resolver
    ClientBuilder.newBuilder().setEndpoints("http://node1:2379", ...)

    // Use the dns+srv resolver
    ClientBuilder.newBuilder().setEndpoints("dns+srv://_etcd-server._tcp.")

They can also be mixed and if an advanced user needs to apply advanced configuration to the underlying channel it can provide its own ManagedChannelBuilder as today.

@lburgazzoli I need sometime to think about this.
Eventually, I want to add
void SetEndpoints(List<String> endpoints)  function to client where this function
allows user to updates endpoints dynamically.
https://github.com/coreos/etcd/blob/master/clientv3/client.go#L119-L122
if newBuilder().setEndpoints only accepts http/https then client.SetEndpoints only update endpoints for scheme http/https. If we introduce more sheme such as dns+srv in newBuilder().setEndpoints(. Then how what's the expectation of ``client.SetEndpointson endpoint with schemedns+srv`.

It would do the same: it goes down to the resolver and it is up to the resolver to update the right underlying resolver.
for (MyResolver resolver : resolvers) {
    // each resolver updates its endpoint list
    // only if it can handle the given scheme
    resolver.update(endpoints);
}

But I'm not a big fan to have a mixed way to set options as in general it cause confusion, maybe we can have something like:
ImmutableEndpointList endpoints = EndpointsList.immutable(...)
Builder.setEndpoints(endpoints)

And:
MutableEndpointList endpoints = EndpointsList.mutable(...)
Builder.setEndpoints(endpoints)

endpoints.update(...)

@lburgazzoli i agree with on this. I don't like mix options too.  the idea of setting resolver based on the scheme  sounds good to me.  cc/ @xiang90

If you guys approve I can work on it

@lburgazzoli talked to @xiang90 in person. We think that the endpoints from setEndpoints  should  always associate to name resolver if there is one given; we need to document this expectation so that there shouldn't be any confusion. If name resolver not given, then we can be smart about choosing the default resolver(simple or dns) base on scheme. I think this approach gives users flexibility to implement their own resolver and have their own endpoint format.

Yeah but there is a problem: endpoints and name resolver are not linked :)
If you look at the documentation of NameResolver and NameResolver.Factory  you'd see that the implementation relies on the target or a single address argument you can set with
ManagedChannelBuilder.forTarget/forAddress.
Our SimpleResolver* does not use the target to resolve the addresses but the endpoints but we can not enforce such relationship so I think that if one wants to use its own resolver it should do it by providing is own `channel builderso that it can also change thetarget``.

@lburgazzoli oh my bad. now I see what you meant.  the currentsetEndpoint only associates with SimpleNameResolver and DnsSRVNameResolver but not any CustomNameResolverFactory.
any CustomNameResolver would have target set to "etcd" which might not be what user wants; hence can be confusing.
removing NameResolver option make sense to me.

close via #181


pathCreate secondcommit

homdirectory

Hi @PAULDANIELDESKTOPQDTGBEG, it looks like this pull request was submitted by mistake. If you would like to contribute to this project, please take a look at our issues that are marked as "good first issue" and "help wanted": https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue"


Add processing for escaping all prohibited characters in a string

Add processing for escaping all prohibited characters in a string for an SQL-query
Example:
pg.execute_to_df(
'''
SELECT
*
FROM
table
WHERE
name LIKE '%foo%'
'''
)

And add tests for case


CREATE method

I think there should be a CREATE method.
An option would be something like creating a drive with name Kopple + (current system time) but this is kinda yuck.
Currently because of CORS stuff, getting the address isn't be possible. This is a different issue though.
What about a new method, not sure how it would work with the URL, perhaps ignore the contents?
Example:
fetch('hyper://new', {method: 'CREATE'}) (returns address)

Beaker uses beaker.hyperdrive.createDrive which returns a drive object which contains the URL of the created drive.

What's the purpose of having a dedicated create method compared to the auto-creation that's already there based on drive names?

As mentioned, one can get around it by using something like system time and assuming that no one will have tried to use that name yet but it's kinda yuck. It'd just be nicer to have it be a dedicated thing that creates a non-named drive. (IMO)

Hmm, I guess I an unwritten guideline I had for naming schemes was to use application names like
hyper://fritter-profile so if another application wanted to use your fritter profile it could get access to it that way too.

Could you maybe elaborate how you'd imagine using CREATE vs using the naming function in an application?

Hmm.. Just using names makes sense I guess.
Just trying to think of reasons against that, perhaps being able to sandbox the drive.
Perhaps this isn't enough of a reason though.
What about having multiple? Check if drive exists yet, if not use that, if yes, append something (and repeat)?

For multiple drives I was imagining you'd either track the names inside localstorage, or mount them on the main application drive or something of the sort.

That makes sense.
What about a malicious site eating the drives of other sites?
Ie. BigPhotoEditor always takes the drive hyper://BigPhotoEditorPhotos as per its code.
MaliciousSite uses hyper://BigPhotoEditorPhotos before the user creates the drive.
Is there anything malicious that the site can do?
I mean I guess the malicious site could inflate the drive? That's not a big problem though.
Maybe we just need to keep it in mind for future CORS stuff?
Can you think of any issues? If not I guess we don't need CREATE

As per our discord discussion:

Maybe we should error when a site gets accessed before it's first PUT
and have an extension exist which prompts the user to accept the initial PUT request for a given origin
That way rogue sites can't pollute a site's index.json without the user allowing it first
Also sites cant create drives without user consent (important for tracking)
You can keep a drive private if you put a CORS header int he index.json that limits access from other domains


At 2.25x and above, the playback speed is not displayed

Is there an existing issue for this?

[X] I have searched the existing issues

Have you read the FAQ?

[X] Yes, I read the FAQ

Device info

iOS/iPadOS version: iOS 16.4.1
Device model: iPhone XR
Sideload tool (AltStore, Sideloadly, TrollStore,...): AltStore
The specific version of CercubePlus (latest or newest is NOT a version number!): 18.13.4-5.3.13

Describe the bug
At 2.25x and above, the playback speed is not displayed on the screen with all video settings.  The problem appeared about versions 4-6 ago.
Steps to reproduce the issue

Make sure YTSpeed is enabled
Open any video
Choose x2.25 or higher playback speed

Crash log (if the app crashes)
No response
Are you using the newest version of CercubePlus? If not, why?
✅ Yes, I'm using the latest version of CercubePlus right now
Does the issue happen with the official YouTube from AppStore?
❌ No, It doesn't
Additional context
Screenhots

Do you mean Fake YouTube version in YouPiP settings?  Since I enabled it, restarted the app, but it didn't help.
Screenshot


Draft PR to integrate autorest.swift with Autorest

leverage swift-nio framework

leverage swift-nio-examples/json-rpc/Sources/JsonRpc for the jsonRPC. The code Codec.swift, Utils.swift, Model.swift under jsonrpc are adapted from swift-nio-examples/json-rpc/Sources/JsonRpc
see https://github.com/apple/swift-nio-examples/tree/master/json-rpc/Sources/JsonRpc

leverage swift-nio-extras for ContentLengthHeader.swift. The code ContentLengthHeader.swift are from that repo.
see https://github.com/apple/swift-nio-extras/blob/c38fb10f5089184f199db47f126525af8346ffc6/Sources/NIOExtras/JSONRPCFraming%2BContentLengthHeader.swift

Code 'AutoRestPlutgin' are following example of main.swift in swift-nio-examples/json-rpc/ServerExample
see
https://github.com/apple/swift-nio-examples/blob/master/json-rpc/Sources/ServerExample/main.swift

To run, do
autorest --verbose --input-file=swagger.json --output-folder=ServiceName --namespace=ServiceName --use=/Users/sacheu/Documents/GitHub/autorest.swift-3
And you see log in autorest-swift-debug.log

Closing in favor of #145, which is merged.


Pin influxdb image to v1.8.4 in docker-compose.yml

My Varken recently blew up because Influxdb was mistakenly upgraded to v2.0. The only errors in the logs were authentication failures. After some debugging and documentation reading, I discovered the incompatible version of Influxdb.
I know v2.0 support is around the corner (#195), but this could save other people the same problems in the future. I'd start pinning specific supported image versions for all required containers.

Please merge into develop instead.

I created a bug (#199) before seeing this pull request as I faced exactly the same issue

Going to close this as the rebase messed up the changes. I have updated develop with image: influxdb:1.8.4

Going to close this as the rebase messed up the changes. I have updated develop with image: influxdb:1.8.4

What could I have done more appropriately? Asking for feedback/instruction.


New maintainer or fork needed?

@prkumar Are you still out there? This is a useful package but needs some maintenance. Would you consider adding someone to maintain it? Perhaps @djbios or @leiserfg would be willing to help?

I would love to help!

I could help next year, I'm semi offline til then.


Header configuration disappears when the drawer opens

Hello, first of all thank's for this excellent lib.
I am having problem with header configuration when drawer is open. The title and logo disappear and the drawer opens under the header.
My code looks like this:

RootNavigator.js

export default RootNavigator = StackNavigator({
  LaunchPage: {
    screen: LaunchPage
  },
  LoginPage: {
    screen: LoginPage
  },
  SignupPage: {
    screen: SignupPage
  },
  ForgotPage: {
    screen: ForgotPage
  },
  AppNavigator: {
    screen: AppNavigator
  }
});

AppNavigator.js

export default AppNavigator = DrawerNavigator({
  DashboardPage: {
    screen: DashboardPage
  },
  ProfilePage: {
    screen: ProfilePage
  }
});

Should I implement this differently?
I have the following need:
I need three screens for authentication and one for startup.
After login, I need to have n screens that I will still define, and have drawer access to go back to login, logout.
Thank you all.

Solution found:
I removed the RootNavigator header by adding headerMode: 'none'.

RootNavigator.js

export default RootNavigator = StackNavigator({
  LaunchPage: {
    screen: LaunchPage
  },
  LoginPage: {
    screen: LoginPage
  },
  SignupPage: {
    screen: SignupPage
  },
  ForgotPage: {
    screen: ForgotPage
  },
  AppNavigator: {
    screen: AppNavigator
  }
}, {
  headerMode: 'none'
});

and add a StackNavigator for each screen in AppNavigator.

AppNavigator.js

export default AppNavigator = DrawerNavigator({
  DashboardPage: {
    screen: StackNavigator({
      DashboardPage: {
        screen: DashboardPage
      }
    })
  },
  ProfilePage: {
    screen: StackNavigator({
      ProfilePage: {
        screen: ProfilePage
      }
    })
  }
});

If anyone knows any other solution I accept evaluate that.
Thanks!

Closing since solution was found 😄


Stl 2159 retry strategy for multiple workers

Short Description

Worker with scheduler
Retry 3 times with 1 second intervals

Changes

Added retry when enqueueing
Readded 5 workers in the supervisord config
Added "with_scheduler" to the worker, needed when using property interval in the retry object
Added new test

Feedback

We decided to readd the retries because we are having some problems with the dongle connectivity on staging when the contract tests are run. We were getting sporadically ERIC_CRYPT_E_SC_SLOT_EMPTY or ERIC_CRYPT_E_SC_SIG_KEY on different integration tests.
I checked the dongle connection (verify_stick was true) and even restarted the pcscd but problem was not solved
Running the contract tests for v2 with only 1 worker didn't produce any error
I decided to use config properties, in case we want to set different values for the retry object in the future, without having to create a new image.
I also had to manipulate a bit a previous test, since now we are using a Retry object.

How to review this Pull Request
Link to Confluence (internal)

@VictorDelCampo (I'm really sorry, I'm reopening this, but) If I'm not mistaken, this retries every failed job, correct? However, in some cases we have errors that we do not want to be retried: INVALID_TAX_NUMBER or - even worse, because we only have 5 tries in total: in case the FSC is wrong.
So I think we have to differentiate between expected and unexpected errors. 🙈


Update KSTS.netkan

Add conflict and suggests sections

I believe this would override the author's ability to control those fields.
Please submit a PR here instead:
https://github.com/mmoench/KSTS/blob/master/KSTS.netkan


[Enhancement] Clicking on the Widget name showing error the debugger must open

Steps to reproduce:

Add a widget
Add inappropriate data
Error is displayed in the widget name
Click on the Widget name
and observe

Observation:
User is not displayed with any action
Expectation:
It is expected that the user is navigate/Highlighted to Debugger or open the debugger as such

@prapullac when the property pane is open, the error field must be highlighted in red and that should be showing the error message and debug action. Is this not happening?

@Nikhil-Nandagopal Yes this is working as expected.

@prapullac I didn't understand then what was the enhancement about?

So the expectation here was that instead of taking a property pane path we could consider that when the user clicks on the error notification (exclamatory mark) on the widget name we can open the debugger which would help the user

Closing this as I think this might be unexpected since the user is used to seeing the property pane open


pino: add 'ecs.version' field in bindings to not have to specify for each log

bindings() is called once at Logger instance creation; log() is called for each <logger>.info() call. While this is premature optimization, it is possibly slightly faster to set this in bindings.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #28 opened

Start Time: 2021-01-11T21:52:07.956+0000

Duration: 7 min 45 sec

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #28 opened

Start Time: 2021-01-11T21:52:07.956+0000

Duration: 7 min 45 sec

Sigh. Never mind, I'd forgotten that I'd already done this in commit 9c23cadfcf9d0e2638b6b51d627e5c0237c07fa0

Sigh. Never mind, I'd forgotten that I'd already done this in commit 9c23cadfcf9d0e2638b6b51d627e5c0237c07fa0


Fixing drag n drop in FireFox and outside the browser in IE

In FireFox, Dragging would sometimes leave files and types null instead of a 0 length array.
In IE, Dragging from outside the browser would cause an exception when the property dataTransfer.effectAllowed was accessed.
See #61

Thanks!


Can I send a persistent RPC via the TB Edge HTTP API?

Component

HTTP API
Rule Engine

Description
Can I send persistent RPCs to the Edge?
###
POST {{host}}/api/rpc/oneway/{{rpb_device_id}} HTTP/1.1
Content-Type: application/json
X-Authorization: Bearer {{auth_token}}

{
  "method": "MyMethod",
  "params": {
    "test": "twoway persistent RPC",
    "file": "test.http"
  },
  "additionalInfo": {
    "extra": "test"
  },
  "retries": 3,
  "persistent": true
}

Where {{host}} is either the TB URL or the edge URL:

TB URL: This returns 200 with a ThingsBoard instance running v.3.6.4PE

Edge URL: but a timeout 504 for the edge instance running v.3.6.4EDGEPE.

I used the default root rule chains where the RPC call request node receives a RPC_CALL_FROM_SERVER_TO_DEVICE. The screenshots above are from these nodes (TB vs. edge respectively)
Environment

OS:  running with your docker images
ThingsBoard: v.3.6.4PE
ThingsBoard Edge: v.3.6.4EDGEPE

Thanks in advance!
Kind regards,
Denise

OK, sry, on another edge instance it works (I get 200 and rpcId) ... seems like I have broken the Rule Chains somehow. Or it has something to do with the setup.

The problem was that the device was created in the main instance. As soon as I created the device in the edge (as it is meant to be in my use case), the call works as expected.
My learning: the RPCs are meant to be executed in the instance where the device has been created (regardless if it is assigned to the edge(?)).

Hi, @dratasich!
Thanks for the request. Unfortunately, there is an issue with persistence RPC. The message is always identified as persistence=false. We could provide a hotfix image for both PE and EDGE-PE, could you send me an email -<EMAIL_ADDRESS>and I'll provide you details?

Hi @AndriiLandiak,
ah, this issue of persistence=false is when sending an RPC request in the rule chain (?) - I have a workaround for that. For now, there is no hotfix image necessary. Thanks!


TP2000-340 Measure edit form creates new FootnoteAssociationMeasure instead of updating the existing

TP2000-340 Measure edit form creates new FootnoteAssociationMeasure instead of updating the existing

Why

Whenever the user clicks "save" on the measure edit form we create a new update version of the measure, even if the data hasn't changed. If that measure has a footnote associated with it, the logic in MeasureForm save will then create a new footnote association. This leads to duplicate footnotes and causes an ME70 violation. We should instead update the existing association to point at the new, updated version of the measure.
What

Adds a check in MeasureForm.save() to see if an a footnote association exists before creating a new one.

Codecov Report

Merging #578 (e82557d) into master (4b893a4) will increase coverage by 0.01%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master     #578      +/-   ##
==========================================
+ Coverage   92.81%   92.82%   +0.01%
==========================================
  Files         320      320
  Lines       19903    19920      +17
  Branches     1593     1595       +2
==========================================
+ Hits        18473    18491      +18
+ Misses       1137     1136       -1
  Partials      293      293

Impacted Files
Coverage Δ

measures/forms.py
95.91% <50.00%> (+0.33%)
:arrow_up:

measures/tests/test_views.py
100.00% <100.00%> (ø)

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 4b893a4...e82557d. Read the comment docs.


Input range doesn't respect interpolated min / max on initialization

See https://github.com/angular/angular.js/pull/14870#issuecomment-237301382

@Narretz
I just test the snapshot  a272a3c and it is working well.
Thanks & Regards,
Michel.


Timeout on test

If you need to increase the timeout of a test, in a regular suite you are able to set a timeout, but this faild with parallel:
parallel('Test with long timeout', function() {
	it('Test running in 3000ms', function (done) {
		this.timeout(4000);
		setTimeout(function(){
			done();
		},3000)
	});
});

Yea, sorry. Dynamically skipping specs also aren't supported. E.g.
it('test', function() { this.skip(); });

Only the following is currently handled:
 *                                               ... Supports hooks, pending
 * or skipped specs/suites via parallel.skip() and it.skip(), but not nested
 * suites.  parallel.only() and it.only() may be used to only wait on the
 * specified specs and suites.
 *

Added basic support for contexts in https://github.com/danielstjules/mocha.parallel/commit/a5ad65119f2607568db8ce3c309905ad5e6156b5 It works for this.skip(), but only partially for this.timeout()
this.timeout() https://github.com/danielstjules/mocha.parallel/blob/a5ad65119f2607568db8ce3c309905ad5e6156b5/fixtures/contextTimeout.js works correctly in mocha 2.2.5, but not mocha 2.3.x. This is because the timeout error isn't thrown, but instead passed directly to the done callback. To avoid that, I'd need to replace runnable.resetTimeout: https://github.com/mochajs/mocha/blob/master/lib/runnable.js#L177-L192 Unfortunately I need access to the runnable via ctx._runnable, but it doesn't exist during spec definition - only execution. https://github.com/mochajs/mocha/blob/master/lib/runnable.js#L219
  // Sometimes the ctx exists, but it is not runnable
  if (ctx && ctx.runnable) {
    ctx.runnable(this);
  }

So it doesn't seem possible to correctly support with mocha 2.3.x. If used with those versions, the exception will be associated with the beforeEach hook rather than the spec. But it works with 2.2.5 (only other version I tested).
This entire library is a hack, so it was pretty likely it'd hit barriers like this one :)

https://github.com/danielstjules/mocha.parallel/commit/0caf28fe1b7cec9fda6d94f010d6869b1e5f2aee Gross, but it works.
Tagged and released 0.10. Thanks!


Verifying clients with retry packets

https://www.litespeedtech.com/docs/litespeed-web-adc/config/tuning#quicDosMitigationDuration
The above feature seems to be supported in LSWS. Is it possible to enable it in lsquic with http mode?

It is a feature in our commercial product, not available in the open source code. Sorry.

@litespeedtech Can the open source server generate tokens with the NEW_TOKEN frame at all? I see some references to a token generator in the source.


Port number fix

Port number fix

Thanks Paul, but I already have it fixed on my working tree; it will be in next release.


Error when creatin module

Hy,
I create a first module with this command "php artisan module:make Sale", the module was created and all is ok, after I wanted to create another module "php artisan module:make Purchase" but i get an error "  Call to undefined function Modules\Sale\Providers\resource_path()  ". Do you  have an idea of what is wrong.
Thanks

What version of laravel are you using?

laravel 5.1

Ah ok that explains it. You'll have to use an older version for that, I'm not sure which one but you can try to go down versions until it works.

ok thanks, i will try.

@nWidart I'm facing this issue right now. I tried to use the 1.19 version but still showing the error. In my previous project, I used the laravel 5.1 version and 1.19 modules version but working.