[BEAM-2576] Split Beam portability framework into construction, job, and execution modules

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

The Beam portability framework has a lot of simple pieces that can be modularized more usefully than "Runner API" and "Fn API".
Here are some semantic categories that should remain stable, and make sense to depend on separately:

Modeling of a Pipeline and pieces of it
Standardized transform payloads

primitives
non-primitives
execution-time only transforms

Standardized UDFs
Job submission and management (Job API)
Artifact upload and retrieval (Artifact API) (could separate upload and retrieval)
Model of bundle processing instructions (ProcessBundleDescriptor)
Standardized execution-only instruction payloads (like data plane read instructions)
Setting up the SDK harness (Provision API)
Control plane for bundle processing (FnControl)
Multi-purpose data streaming (FnData)
Logging
... more later, maybe ...

This PR is a first move in this direction, organizing the components according to when in a pipeline's lifecycle they are used.

Construction: building a pipeline and specifying transforms. Basically just data structures, not APIs. Code doing this work should only depend on this module.
Job: submission and management of a pipeline, including artifacts, etc. Construction code should not depend on this module.
Execution: SDK harness management and UDF invocation. Only runner internals and SDK harnesses should depend on this module.

What this PR does is move the existing protos into the right maven modules, but does not split them yet.

R: @robertwb
(anyone's comments welcome, like @lukecwik @tgroh @aljoscha, @herohde, @tweise. I'm just limiting reviewer resources consumed)

I think splitting it up this way makes a lot of sense. I recently gave a talk at Flink Forward Berlin about the compatibility efforts and I roughly explained the API with those separations but I didn't take the extra further step of thinking how it should be organised in the actual code.

This split makes a lot of sense and will reduce confusion down the line. Not to be that guy, but the names "job" and "construction" seem slightly off to me -- I'm thinking more of them as just "model" and "submission"/"management", say.

I think now is the perfect time to have a naming discussion :-)
Construction -> ??
I think "model" is a bit general as a replacement for "construction". It is pretty much what we know as the "Beam programming model". I want to explicitly make clear that there is separately an execution model and a job submission/management model.
I toyed with "pipeline" but opted for something more broad in order to also lump the primitive payloads and standardized payloads into the same artifact. There's no technical reason they need to be in one artifact, but just keeping the artifact count lower because maven is heavy on boilerplate.
Could definitely split into beam-model-pipeline, beam-model-primitives, beam-model-standard-transforms, and beam-model-standard-fns.
Job -> ??
No strong opinion, but isn't "job" the thing that you are submitting and managing?

standard-transforms would contain, for example, Combine?
I'm pretty happy with job or job-management; submission is to specific (because you can also get out information about running jobs, update, drain, cancel, etc.
I don't know how useful I find model as a common prefix, especially when the subpackages are things like 'construction' and 'job'. Something like org.apache.beam.model.pipeline... mostly makes sense to me, and I suppose to some extent ...model.execution... does as well. I don't think ...model.job... scans particularly well, however. It may be because the job APIs are the only one where there are two top-level systems communicating (at least in how I comprehend the three divisions here)

For "job", I was more expecting something contrasting "execution". I agree that jobs are what we submit and manage, but also what we execute.
For "construction". the split names seem clearer. I don't have a better suggestion and don't feel too strongly about it, but "construction" suggests something active as opposed to passive data structures to me.

Maybe "execution" is the worst of all. Maybe fn is still the best for this. Beyond what is currently in beam_fn_api it would also have provision and other bits pertinent to setting up a harness and managing it. Certainly its whole point is to invoke UDFs.

@tgroh yes, standard-transforms would contain Combine and perhaps some more like Create and WriteFiles (most IOs should manage their own payloads, but this one is in the core SDK). The distinction between primitives and standardized transforms is perhaps not critical here.

Based upon the list of parts, I grouped them into the three areas I believe they should go:

beam-model-core:

Modeling of a Pipeline and pieces of it
Standardized transform payloads
primitives
non-primitives (only ones which are shipped with Apache Beam, users creating their own should package and ship their own)
Standardized UDFs

beam-model-job-management:

Job submission and management (Job API)
Artifact upload

beam-model-job-execution:

Artifact retrieveal
Model of bundle processing instructions (ProcessBundleDescriptor)
Standardized execution-only instruction payloads (like data plane read instructions)
Setting up the SDK harness (Provision API)
Control plane for bundle processing (FnControl)
Multi-purpose data streaming (FnData)
Logging
execution-time only transform payloads

@lukecwik awesome - that's exactly what I've got, except the artifact upload vs retrieval split. For this PR I just want to move proto files without splitting them, but afterwards I will do a little bit towards the breakdown you outlined.

That division makes a lot of sense to me, except having Artifact Upload and Artifact Retrieval separate seems a bit odd (but I could live with that, as long as they share a common definition of Artifact).

Yes, I was thinking the same thing now that you mentioned it that the a common Artifact definition should fall under beam-model-core.

It's a bit of a strange place for it, given that it has no use until the Job API, which does not appear to be part of the core model

Artifact upload is part of job management though.

We should think hard about whether the notion of artifacts (which seem
similar in spirit to environments) should be in the core model, especially
if they're per-step or anything like that. I agree that submitting
artifacts belongs as part of the job API (though perhaps not distinct from
submitting the job itself) and fetching them part of the execution API.
On Tue, Oct 3, 2017 at 5:03 PM, Lukasz Cwik<EMAIL_ADDRESS>wrote:

Artifact upload is part of job management though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/3924#issuecomment-334014039, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdqgdfIyWnnGl08oWvuKOAZWqTeUSZMks5sostqgaJpZM4PpSZ9
.

Agree with @robertwb that there's a decent chance the TBD Environment bit on UDFs may reference things like artifacts. It seems like a bit much to include the whole classpath, or to narrow the list down effectively, but there may well be special cases, like when the user specifies additional resources to stage. I think "core" might be a loaded term that makes us more hesitant to include things than we need to be.

Since this is a pretty conflict-ridden PR due to imports, can we go with an LGTM on the basic modules so I can asynchronously fix conflicts and merge?
Specifically, based on this feedback, how about:

model/pipeline
model/job-management
model/fn

These are just package renames from what is already here.

+1 on getting basic modules in to avoid continuous rebasing.
One though: what about
model/worker-management

instead of fn?
On Thu, Oct 5, 2017 at 11:52 AM, Kenn Knowles<EMAIL_ADDRESS>wrote:

Since this is a pretty conflict-ridden PR due to imports, can we go with
an LGTM on the basic modules so I can asynchronously fix conflicts and
merge?
Specifically, based on this feedback, how about:

model/pipeline
model/job-management
model/fn

These are just package renames from what is already here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/3924#issuecomment-334558312, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdqgbmyOl_niDGcd0jC9rbgbRt2sElLks5spSVUgaJpZM4PpSZ9
.

So far we haven't really had a notion of a worker in Beam - every runner has their own sort of worker, sometimes doing runner-specific stuff. I'd hate to cause confusion there.
I guess I like fn because it has to do with invoking DoFns, WindowFns, etc. But it pretty much entails most aspects of execution since you need to fuse and code/encode, etc. Hence my first draft being model/execution, but that wasn't specific about exactly what was being executed.

fn-execution? maybe that is just extra characters. On the other hand, folks like job-management more than job (I still like the pithier job, personally)

+1 to fn-execution. (We do have the concept of a "SDK worker," but I agree
the term worker is way overloaded. I'm all for pithy, but I think in this
context a little verbosity is worth the clarity.
On Thu, Oct 5, 2017 at 12:31 PM, Kenn Knowles<EMAIL_ADDRESS>wrote:

fn-execution? maybe that is just extra characters. On the other hand,
folks like job-management more than job (I still like the pithier job,
personally)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/3924#issuecomment-334568593, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdqgeEbdWTi3I-N1sZ4kc_XjY4q3mGAks5spS6QgaJpZM4PpSZ9
.

So, I'll go ahead with model/pipeline, model/job-management and model/fn-execution.

Ah, the issue now is that the module beam-runners-core-construction depends on beam-model-job-management but it is not in the reactor. So it may be that to get maven to function correctly we'll need to hand-curate the list of modules.

retest this please

Coverage decreased (-0.07%) to 69.515% when pulling 7ca045a4cd0616955d668ea7e883e44947469c91 on kennknowles:beam-model into b44056fc6fe5b40f9fde09c4488de4692fe23a37 on apache:master.

Changes Unknown when pulling 3cec3d969d9f54864508357615c75c4b0b8d3e75 on kennknowles:beam-model into ** on apache:master**.

Changes Unknown when pulling 3cec3d969d9f54864508357615c75c4b0b8d3e75 on kennknowles:beam-model into ** on apache:master**.

Changes Unknown when pulling b2daa0cf432eb81d3f9283b9239f164a60ff92e1 on kennknowles:beam-model into ** on apache:master**.


Protect $ROLE_REQUIREMENTS with quotes.

This is important in case the filename contains spaces, but more importantly, if no file is set, the test for file existence does not give the desired outcome: [ -f ] evaluates to true/returns an exit code of 0, hence [ -f $VAR ] with $VAR empty does the same. Protecting $VAR with quotes has the desired behaviour.
Not entirely sure whether this is an odd behaviour on my machine, but protecting variables is always a good idea...

You're quite right—I was only testing with 'machine-name' style filenames, so I didn't catch this. Looks good to me!


Block and policy discoverability/search

Problem description
At present authors of Guardian policies have a number of tools they can use to assist with policy creation to avoid creating a policy 'from scratch'

wizards
policy blocks suggestions in the editor
pre-built policy modules
use sample policies available out-of-the box as a template and change/extend as required

However there is frequently a need to add elements to the policy to address specific use-cases. When such a need arises it would help policy authors to be able to quickly look-up other existing policies which use this element[s] and thus have examples or copy/paste sources.
Requirements

Introduce a capability into Guardian where a user can search, directly from the editor, examples of the usage of specific blocks
The search scope should be inside a Guardian instance and, additionally, further through all published policies
Uses should be able to preview the usage of the block without having to import policy into their Guardian instance
There should be additional filters in the UI that would allow users to restrict the scope of the search based on:

date range
SR (list)
Presence/absence of tags and their scoring (e.g. 'minimum 50 thumbs-up tags')
name

Definition of done

Functionality is implemented in the Guardian UI (no corresponding API is required)
Documentation updated accordingly

Acceptance criteria
Policy authors are able to quickly look-up the examples of usage for tags as per requirements above

@anvabr can you please share more on discoverability across guardian instances here?

@nodlRob ^ for awareness

@anvabr it would be great if we could use this across multiple instances of Guardian as as part of the definition of done and have it update our methodology library with listed undocumented policies for analytics. cc: @danielnorkin

use this across multiple instances of Guardian

This is in scope, i.e. it specifies "and, additionally, further through all published policies"


Dataset Preprocess

Hello, thank you for your work.
Will you provide a data set processing file later? That is, how to convert from the original dataset to the sample_datasets format you gave us.
I looked at the UMLS website, but I didn't know which API was used to extract medical terms from text.
Looking forward to your reply!

Yes, we will provide those files later. If your major concern comes from identifying medical terms by UMLS, I suggest you to check out scispacy: https://github.com/allenai/scispacy. The EntityLinker  part is what we used in our paper to identify medical terms.

Thank you for responding.
I attempted to apply for the test set of the RSS dataset on the official website, but encountered some issues with the application process. Will it be released later?
Additionally, regarding the MDS dataset, are there any plans to make it publicly available in the future?

Thank you for responding.
Additionally, regarding the MDS dataset, are there any plans to make it publicly available in the future?

We are constantly reaching out to the platform to ask for permission, but we have not obtained one yet - the same as all the related work that tried to crawl the data there (to the best of our knowledge). As a solution on this, our paper has detailed description of how we collected the data and annotated medical terms.

Hi @lisdarr ! We have added preprocess_QS.ipynb and preprocess_RRS.ipynb to show how we preprocess the English datasets. You may check the updated README (the last paragraph of the dataset section) for more details. I will close this discussion for now. Let me know if there are additional questions.


npm: Change request to other packages

The npm package request is under maintenance mode: https://github.com/request/request/issues/3142
Therefore, you need to change request to other packages.
Alternative libraries to request: https://github.com/request/request/issues/3143

Request 2.88.2 depends on form-data 2.3.3, which depends on json-schema 0.2.3
json-schema 0.2.3 has a critical vulnerability:
https://github.com/advisories/GHSA-896r-f27r-55mw
Which is a problem for using Elm. If you org needs to comply with security audits (like us).
So it would be really good to change this

FYI: The request dependency is being removed in https://github.com/elm/compiler/pull/2287

@adrian-gomez I’m not sure I understand what you mean. Could we chat about it on Slack perhaps?


Update go version used to v1.18

What this PR does / why we need it:
Update go version used to v1.18
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Update Go version to `v1.18`

/invite @himanshu-kun

/reviewed ok-to-test

Yes the pipeline had to be updated and also update the linter because of a bug marking used variables as unused.


add JsonLayout for logging

will solve #367
add a workaround for #453

@meltsufin

The logging module may be used without Sleuth, and the traceId should be extracted from TraceLoggingEnhancer.getCurrentTraceId(). We may be able to put it into the MDC, but currently it's not happening.

I've already used the TraceId from the TraceLoggingEnhancer see method addTraceId

I also noticed that the log lines from the docker container are wrapped at a length of about 16 kB. Thus, fluentd no longer parses the JSON correctly. This happens with long stacktraces. Does anybody have a good solution?

It might be better to just output stack traces directly without wrapping into JSON. The fluentd plugin parses stack traces automatically and creates error reports from them, even if they are multi-line.
@igorpeshansky Do you know regarding the log message limit?

It might be better to just output stack traces directly without wrapping into JSON. The fluentd plugin parses stack traces automatically and creates error reports from them, even if they are multi-line.

I don't think that's a solution. Hence, the TraceId for the stacktraces would be missing. But that's exactly where this connection is extremely helpful for the analysis.

@Andy2003 I see your point, but can you log the short version of the exception without the full stack trace with JSON, and the full stack trace separately? This is not perfect, but might be a good solution given the log message length constraints.

The Stackdriver limit on the log entry length is 100k. Docker has decided to go with 16k, breaking many log parsers (not just Stackdriver).
FWIW, GKE is running on a custom build of Docker that increases the wrap limit to 100k. Might be worth doing that with GAE Flex as well. I don't think there's a good solution for other systems.

Our application runs within the GKE and we have reached the 16k limit. Do we have to configure anything else to achieve 100k?
Nevertheless, the PR should not be blocked by this, right?

@Andy2003 This may depend on the master/node versions in your cluster. @crassirostris may know more.

Do we have to configure anything else to achieve 100k?

The patch was only introduced for COS images with version m64 and higher

@Andy2003 I'm happy to merge this if you're not planning any more commits to this PR.

Feel free to merge!
Am 05.03.2018 15:21 schrieb "Mike Eltsufin"<EMAIL_ADDRESS>
@Andy2003 https://github.com/andy2003 I'm happy to merge this if you're
not planning any more commits to this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-gcp/pull/454#issuecomment-370433493,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEQfihwU0VJ4gyFfUUeArQRtuIrU2HSAks5tbUnLgaJpZM4STUFK
.


reenable crash handler

Scope & Purpose
Reenable previously disabled crash handler.

[x] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/9850/

Tests blue


Link button doesn't do anything

The permalink button by a post title doesn't seem to do anything. It would also be helpful to be able to click the post title on the home page to get a permalink.

The permalink button by a post title doesn't seem to do anything.

What browser are you using?

Brave, just looked into it more closely and it looks like clicking it copies the link to the clipboard, but there's no indication that's what has happened, so it's more of a UI thing than a bug. And to clarify, the post I'm referring to is the post title for the first post on the homepage.

Resolved in 14d9370 and 90c5853


optimised docker image

use multi-stage image to remove build dependencies from final layer
updated to python 3.7.3

Closes #122
Signed-off-by: Weston Steimel<EMAIL_ADDRESS>

Sample scan from built image:
The Can't open /etc/ethertypes file also seems to appear when building from Dockerkfile in master
$ docker run --rm -it kube-hunter:test --internal --pod
~ Started
~ Discovering Open Kubernetes Services...
Can't open /etc/ethertypes file
|
| API Server:
|   type: open service
|   service: API Server
|_  host: <IP_ADDRESS>:6443

----------

Nodes
+-------------+------------+
| TYPE        | LOCATION   |
+-------------+------------+
| Node/Master | <IP_ADDRESS> |
+-------------+------------+

Detected Services
+------------+-----------------+----------------------+
| SERVICE    | LOCATION        | DESCRIPTION          |
+------------+-----------------+----------------------+
| API Server | <IP_ADDRESS>:6443 | The API server is in |
|            |                 | charge of all        |
|            |                 | operations on the    |
|            |                 | cluster.             |
+------------+-----------------+----------------------+

Hunter Statistics
+----------------------+----------------------+--------+
| NAME                 | DESCRIPTION          | EVENTS |
+----------------------+----------------------+--------+
| Proxy Hunting        | Hunts for a          | 0      |
|                      | dashboard behind the |        |
|                      | proxy                |        |
+----------------------+----------------------+--------+
| Kubelet Secure Ports | Hunts specific       | 0      |
| Hunter               | endpoints on an open |        |
|                      | secured Kubelet      |        |
+----------------------+----------------------+--------+
| Kubelet Readonly     | Hunts specific       | 0      |
| Ports Hunter         | endpoints on open    |        |
|                      | ports in the         |        |
|                      | readonly Kubelet     |        |
|                      | server               |        |
+----------------------+----------------------+--------+
| Etcd Remote Access   | Checks for remote    | 0      |
|                      | availability of      |        |
|                      | etcd, its version,   |        |
|                      | and read access to   |        |
|                      | the DB               |        |
+----------------------+----------------------+--------+
| Dashboard Hunting    | Hunts open           | 0      |
|                      | Dashboards, gets the |        |
|                      | type of nodes in the |        |
|                      | cluster              |        |
+----------------------+----------------------+--------+
| Certificate Email    | Checks for email     | 1      |
| Hunting              | addresses in         |        |
|                      | kubernetes ssl       |        |
|                      | certificates         |        |
+----------------------+----------------------+--------+
| CVE-2018-1002105     | Checks if Node is    | 1      |
| hunter               | running a Kubernetes |        |
|                      | version vulnerable   |        |
|                      | to critical          |        |
|                      | CVE-2018-1002105     |        |
+----------------------+----------------------+--------+
| Access Secrets       | Accessing the        | 1      |
|                      | secrets accessible   |        |
|                      | to the pod           |        |
+----------------------+----------------------+--------+
| API Server Hunter    | Checks if API server | 1      |
|                      | is accessible        |        |
+----------------------+----------------------+--------+
| API Server Hunter    | Accessing the API    | 1      |
|                      | server using the     |        |
|                      | service account      |        |
|                      | token obtained from  |        |
|                      | a compromised pod    |        |
+----------------------+----------------------+--------+
| AKS Hunting          | Hunting Azure        | 0      |
|                      | cluster deployments  |        |
|                      | using specific known |        |
|                      | configurations       |        |
+----------------------+----------------------+--------+

No vulnerabilities were found

This looks fine to me, and I can’t really see why that /etc/ethertypes message would have changed, but I’d like to understand where it’s coming from. @westonsteimel do you know if this also appeared in 3.7.2 or 2.7.x?

@lizrice , it appears to have been introduced with scapy version 2.4.2 probably by the EtherCat functionality which was added in that release .  It looks like scapy wasn't explicitly versioned in requirements.txt until f0160e2eba5f87fd0c5ffdd1681f6eb71dfeaeaf, so it would have just been getting the most recent version from pypi at the time the image was built.  I have verified that the message does not appear with scapy 2.4.0.  I don't really want to downgrade that though, so adding /etc/ethertypes to the alpine image also works.  That is available with the ebtables pacakge in alpine.

Pinging @danielsagi for review please

lgtm


Edited two files.

Shannon,
You will have to sign the cla. Follow the link. It's easy.

Will merge for now, but @shanayres please sign the CLA, should be pretty easy.


libtock-sync: alarm: Support empty delays

If libtocksync_alarm_delay_ms() is provided a delay of 0ms we currenty schedule an alarm which is a high overhead for a empty delay.
Instead let's just call a yield_no_wait() and return success if we don't actually need to delay.

Why call yield_no_wait() at all? Why not just return?

Why call yield_no_wait() at all? Why not just return?

I'm going to guess that users may expect a delay to always cause upcalls to run. Which I think is a reasonable expectation.
However, with that premise, I'm not sure I buy this optimization, when it still runs a full system call. Sure, we get rid of a bit of overhead, but how common is this edge case?

We need to reckon with what libtock-sync guarantees, and I think the expectation we want to move towards (and why we added yield-nowait) is that unrelated events don't run. I know that delay_ms doesn't promise that today, but I think the ideal is that it does block everything.

I'm going to guess that users may expect a delay to always cause upcalls to run. Which I think is a reasonable expectation.

Exactly!
Basically FreeRTOS tasks (and lots of stuff is built around FreeRTOS) use vTaskDelay(0). So this is adapting to support that type of usecase

libtocksync_alarm_delay_ms() today already allows anything else to run though, so this isn't really any different. We are just not setting an alarm

So, to be clear, a delay of 0 ms does work today with the code as it exists before this PR, right?
If so, then I don't see a good reason for the optimization here. Applications can call yield_no_wait() directly, and don't have to libtocksync_alarm_delay_ms(0).
I can see a scenario where some higher-level library is deciding on delay times, and might incidentally decide to delay 0 ms. But in my mind, that means this optimization should go in that higher-level library. But maybe there's an important use-case I'm missing?
I personally think the argument that matters here is whether we should have the optimization or not. If yes, then per today's semantics a yield_no_wait() makes sense. And a future change to make delay_ms() actually delay and not yield for anything could fixup this optimization too.

So, to be clear, a delay of 0 ms does work today with the code as it exists before this PR, right?

It doesn't work for me, but I suspect that's a bug in Tock.

If so, then I don't see a good reason for the optimization here. Applications can call yield_no_wait() directly, and don't have to libtocksync_alarm_delay_ms(0).

Ha! The high level application said the exact opposite: https://github.com/jgromes/RadioLib/pull/1149#issuecomment-2211799640
One issue that other applications might not have a yield_no_wait() HAL to call, but they do have delay(0)

I'm also happy to drop the yield_no_wait() from this PR, but that feels a bit sneaky to me as the caller probably expects a yield to be called

It doesn't work for me, but I suspect that's a bug in Tock.

I agree, this seems to be the real fix then.

I'm curious whether this is really a bug in Tock or a bug somewhere in the libtock-c virtual alarm stack?
In either case, this seems like papering over the real problem, e.g., putting this check here won't fix the case where someone chooses to call libtock_alarm_in_ms(0, ...) for a user of the async libtock interface (which is all that the delay_ms(0 translates too under the hood.
I agree there's a bug somewhere in the timer stack, but this doesn't look like the right place to fix it (at minimum the ==0 check needs to move to the lower-layer async impl).


Moviepy

i wrote this code and it did not display the video
i do not now why ?
from moviepy.editor import *
myvideo =  VideoFileClip('C:/Users/Sohayla/Desktop/PythonSourceCode/road_lane_line_detection-master/challenge.MP4').rotate(180)
myvideo.ipython_display()

Sorry, this doesn't have anything to do with this project. Try asking the moviepy project instead.


Regenerating helptags dirties the repo

Description
This was introduced in  #1497
Whenever you run helptags on nvim-lspconfig, the geterated tags file will differ from the one checked into the repo.
I think a lot of people might be generating their helptags on their own as well.
Since I have nvim-lspconfig as a subrepo here, my own repo becomes dirty after generating the tags
Neovim version
NVIM v0.6.0-dev
Build type: Release
LuaJIT 2.0.5
Compiled by<EMAIL_ADDRESS>Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/share/nvim"
Run :checkhealth for more info
Nvim-lspconfig version
d9aa848d
Operating system and version
slackware64-current
Affected language servers
none
Steps to reproduce
Running helptags ALL inside neovim with nvim-lspconfig.
Actual behavior
nvim-lspconfig repo becomes dirty
Expected behavior
nvim-lspconfig files do not change from the committed versions
Minimal config
Not relevant?

Health check
Not relevant?
LSP log
not relevant

I'm open to suggestions, but I think having the markdown file directly indexed as a tag is an invaluable feature (cc @muniter)

Is there no way to have it added there by helptags automatically?

The other thing is that if someone is running helptags on their own as well, the markdown file will not be indexed, defeating the purpose of the feature altogether

So there's a few options as I mentioned in matrix.

Rename tags to tags-en which helptags won't overwrite since there's no lapconfig.enx and in my testing (my machine) :help always searches tags-en.

Symlink servers_configuration.md to servers_configuration.txt and add a comment at the top of the file with the tag name. Making helptags find it and generate it always. The downside is i don't think symlinks work out of the box from a repo in windows 🪟
2.1. Ugly: duplicate the markdown file as txt and md extension and it will work anywhere.
2.2 Rename server_configurations.md to server_configurations.txt and provide a modeline saying is a markdown file. According to this link it works. So GitHub displays it as markdown. Vim sees as txt because the extension and generates the proper tag!!!

So 2.2 sound like the best solution. What do you think @mjlbach your call.

Leaning towards 1


feat: create a span for traceability of tests

Now we now which test is generating which log, even if they run at the same time:
2023-09-14T21:17:28.790892Z  INFO on_chain_peg_in_and_peg_out_happy_case: fedimint_wallet_tests: Peg-in transaction claimed height=1415 tx=Transaction { version: 2, lock_time: PackedLockTime(1414), input: [TxIn { previous_output: OutPoint { txid: 37c7dbc03954476ac7f5e5990c550467f3b75ae72625e1df58d270bc2fa6235d, vout: 0 }, script_sig: Script(), sequence: Sequence(4294967293), witness: Witness { content: [64, 10, 230, 137, 46, 253, 53, 206, 47, 129, 55, 237, 34, 38, 34, 80, 127, 74, 175, 196, 42, 236, 87, 31, 210, 33, 170, 223, 182, 248, 54, 16, 150, 229, 253, 217, 201, 101, 110, 161, 136, 4, 168, 102, 36, 60, 242, 112, 217, 104, 30, 219, 58, 10, 6, 76, 29, 62, 68, 125, 183, 39, 156, 27, 11], witness_elements: 1, last: 0, second_to_last: 0 } }], output: [TxOut { value: 5000, script_pubkey: Script(OP_0 OP_PUSHBYTES_32 61443d44882b34a73e9e8661682f6f10c25f3b9a686f2eca78edf333119b5dc5) }, TxOut { value: 78062760, script_pubkey: Script(OP_PUSHNUM_1 OP_PUSHBYTES_32 6eeaf2ea46ee310f301975e9570d592711b17e9057cc8489021cddcb45ed2d89) }] }
2023-09-14T21:17:28.790965Z  INFO on_chain_peg_in_and_peg_out_happy_case: fedimint_wallet_tests: Peg-in finished for test on_chain_peg_in_and_peg_out_happy_case
2023-09-14T21:17:28.792862Z  INFO on_chain_peg_in_and_peg_out_happy_case: fedimint_wallet_server: Creating peg-out tx inputs=1 input_sats=5000 peg_out_sats=1000 fees_sats=730 fee_rate=1000 change_sats=3270
2023-09-14T21:17:28.792862Z  INFO on_chain_peg_in_and_peg_out_happy_case: fedimint_wallet_server: Creating peg-out tx inputs=1 input_sats=5000 peg_out_sats=1000 fees_sats=730 fee_rate=1000 change_sats=3270
2023-09-14T21:17:28.792910Z  INFO on_chain_peg_in_and_peg_out_happy_case: fedimint_wallet_server: Creating peg-out tx txid=2ae728b9c2c41279bea18f5fa5233b7ed5a296962765c1ba4a5f26cb92914e88
2023-09-14T21:17:28.792916Z  INFO on_chain_peg_in_and_peg_out_happy_case: fedimint_wallet_server: Creating peg-out tx txid=2ae728b9c2c41279bea18f5fa5233b7ed5a296962765c1ba4a5f26cb92914e88
2023-09-14T21:17:28.794953Z DEBUG on_chain_peg_in_and_peg_out_happy_case: timing: Operation timing name=autocmmit - commit_tx duration_ms=0
2023-09-14T21:17:29.029553Z DEBUG sanity_check_bitcoin_blocks: timing: Operation timing name=sign last epoch key duration_ms=3
2023-09-14T21:17:29.042543Z DEBUG sanity_check_bitcoin_blocks: timing: Operation timing name=sign last epoch key duration_ms=2
2023-09-14T21:17:29.045441Z DEBUG peg_outs_support_rbf: timing: Operation timing name=sign last epoch key duration_ms=2
2023-09-14T21:17:29.053717Z DEBUG peg_outs_support_rbf: timing: Operation timing name=sign last epoch key duration_ms=1
2023-09-14T21:17:29.242081Z  INFO sanity_check_bitcoin_blocks: consensus:

Note it includes server module api calls.

OK. So running with cargo nextest is going to render this redundant, I think.
With cargo nextest each output of every test is captured separately, displayed only when needed, making figuring out which test is which simple. I'm going to convert everything to nextest soon, no matter the cost in property damages. Our CI insurance should cover it.
Also what I learned yesterday, wasting more time than I wanted playing with it is that:
https://github.com/tokio-rs/tracing/issues/2597
Also since spans don't propagete to spawned tasks, the're kind of clunky. And span name needs to be a constant making some dynamic stuff impossible.
I still don't understand log levels on spans, and I think chatgpt doesn't either.
Anyway - I think we should put it on hold for now, re-evalute after cargo nextest is fully rolled out.

@douglaz I think cargo nextest did indeed make identifying failing test not an issue, so closing.


Support a Mustache mode that highlights the templated language

Preface: I'm opening this issue mostly for the technical discussion. If this feature seems possible and would be accepted into the project, I'd be happy to do the work.
I think that most often, Mustache template files have two extensions: the "wrapped" language extension, followed by ".mustache". So an HTML template file has the extension ".html.mustache" and a Markdown template might have the extension ".md.mustache".
It would be awesome if CodeMirror supported a mixed mode Mustache mode that highlighted the "wrapped" language as normal, and caught Mustache tags, highlighting them as Mustache tags.
One way that mustache makes this crazy simple is it's crazy simple interface: Mustache tags are exactly the two following syntaxes: {{tag}} and {{{tag}}}. The mustache highlighter could distinguish between variables {{name}} and sections {{#list}}, etc., but honestly, if they were just plain text, that'd be fine.
The "Set Delimiter" functionality would probably be hard to support, but I don't think it would be needed in v1. It's not a commonly used feature.
The only tricky thing I can think of is the Mustache mode knowing the file extensions, and dynamically using the proper mode for the "wrapped" language.

This is already how most CodeMirror template language modes work. For example the handlebars mode -- scroll down in the example to see HTML highlighting of the content.
As for a specific Mustache mode (if the syntactic differences with Handlebars annoy you), I don't take feature requests for modes -- you can write it yourself (probably by making the Handlebars mode configurable) or pay me to do so.


[bug 1136840] Back out new WSGIHandler

This backs out the new WSGIHandler for stage/prod server environments.
When I landed this, I stopped getting the HB errors that I implemented
this to help track down. That's either a fluke or I messed something up.
Backing this out to eliminate the latter possibility.
Quick r?

LGTM r+!

Landed in ecdd00f [bug 1136840] Back out new WSGIHandler
Thank you!


"Log In Successful" does not match original style

When you login successfully with casuser/Mellon, "Log In Successful" should show as bold. It's probably related to other styling issues.

If you look at the "statistics" endpoint, you'll see all header titles have shrunk down in size and color.

Reverted to original styling
"Log In Successful" shows as bold and other styling reverted also.


Visualizations Feedback!

Below are some thoughts about the visualizations in this report and some suggestions for improvement, and notes when things are done well. You should implement these in milestone4

[ ] It would really have helped if you had a caption and a figure/table number for each plot. That way you can easily reference it in your text, and it's easier for readers to find

[x] Figure 1: working day/temperature

[x] This is a really powerful visualization. I think there is some overplotting happening, but it's not actually interfering with your overall message and what you're trying to convey

[x] I would suggest you add better facet titles/subtitles. So rather than workingday no/yes, maybe remove the 'workingday' title and instead of no/yes, change to Not a working day/Working day in larger text size. Let me know if you need help doing this in altair!

[x] Figure 2:

[x] Also a really powerful visualization that shows exactly what you want it to!

[ ] If you add a figure number and caption, this will be even more effective

[x] Consider setting the lower limit of your colour bar to 0 rather than 4

[x] Figure 3:

[x] Great work! This is really excellent. I've submitted this one to the altair examples dir as Victor sent me a minimum working example

[ ] Ideally, you only want to show half the correlation map as the other half is redundant (see example here) - let me know if you figure out how to do this in Altair

[x] Table 1:

[x] Too many sig figs, there's no need to show that many, it hurts readability and interpretability

[x] Figure: importance of predictors and actual vs. predicted rides

[x] perfect! Well done here

[x] Overall the report looks very polished and clean! Great work! Excellent work with your labels, titles, and plot choices! For every plot I was immediately able to understand what you were trying to convey.

Figure 3: we did not find the solution to show half of the correlation maps. We will mark it optional.

For the figure number and captions, we tried several times with the same code, it showed up in 2/5 times due to some unknown reason.

RE: Figure 3, for future reference, here is some sample code to do this:
# Load packages
import altair as alt
from vega_datasets import data

# Load the data
df_iris = data.iris()

# This bit of wrangling creates a new dataframe with only half the elements
l1 = sorted(df_iris.corr().columns.to_list())
l2 = l1.copy()
rows = []

for e1 in l1:
    for e2 in l2:
        rows.append([e1,e2, df_iris.corr().loc[e1,e2]])

    l2.remove(e1)

# Create dataframe from list of rows
newdf = pd.DataFrame(rows,columns=['Var1','Var2','Corr'])

# If you want to remove the diagonals
newdf = newdf[newdf['Var1']!=newdf['Var2']]

# Create the heatmap first
heatmap = alt.Chart(newdf).mark_rect(
).encode(
    alt.X('Var1:O', title = ''),
    alt.Y('Var2:O', title = '', axis=alt.Axis(labelAngle=0)),
     alt.Color('Corr:Q',
                scale=alt.Scale(scheme='viridis'))
)

# Add the correlation values as a text mark
text = heatmap.mark_text(baseline='middle', fontSize=20).encode(
    text=alt.Text('Corr:Q', format='.2'),
    color=alt.condition(
        alt.datum['Corr'] >= 0.95,
        alt.value('black'),
        alt.value('white')
    )
)

# Set the height, width, title and other properties
corrMatrix_chart = (heatmap + text).properties(
    width = 400,
    height = 400,
    title = "Iris variables correlation matrix",
)
corrMatrix_chart.configure_axis(
    labelFontSize=18,
    titleFontSize=24,
).configure_title(
    fontSize=24,
    anchor='start',
).configure_legend(
    labelFontSize=20,
    titleFontSize=20)


Using set_parameter_values with ModelingToolkit type models

With Catalyst (and other packages) we generate models ranging from small to large that we can encode as ModeligToolkit ODESystems (or other stuff). I want to assess the identifiability of these systems. However, I am unsure how to apply certain functions in the system to these (which seems primarily designed for StructuralIdentifiabiltiy ODEs).
Say that I have an identifiability problem, but know the value of certain initial conditions and parameters, how do I give StructuralIdentifiabiltiy this information? My only lead, the set_parameter_values function, seems to only work on ODEs defined by StructutralIdentifiability.

Just to clarify: you would like to have a function which takes an ODESystem and sets some of the parameters to given constants? I can add it, I would just feel that it belongs rather to ModelingToolkit...

Sorry, yes, that would be a solution (however, I think this would be rather messy to do).
What I mean is, I want to assess the identifiability of a system. However, there are certain parameters and/or initial conditions that I know. E.g. if I have a system
dX/dt = - p1*p2 * X

I would get both p1, and p2 unidentifiable (I presume). However, I want to supply the information that I know that value of p1 (in which case identifiability for p1 would never have to be assessed, and p2 should become identifiable).
How would I do this?

Oh, I see.
If you want to indicate the knowledge but not a particular value, you can add this parameters as a measurable_quantity.
For initial conditions, unfortunately, for the moment we do not have this functionality.

Got it (For biology and chemistry this functionality would ver very useful).
I will see if I can coble together some internal hack to enable this for Catalyst (until the feature is added here, please ping me when you do).


nethogs 0.8.1 (new formula)

Can this formula be built on Mac OS? If so this formula should be submitted to Homebrew/homebrew. Please read CONTRIBUTING.md

I am not sure nethogs works on OSX but I will try to build it.

Like I thought, the current nethogs does not work on OSX.
But I submitted a patch to add OSX compatibility: https://github.com/raboof/nethogs/pull/20

Nicely done, and your patch was merged upstream. With the next stable release of nethogs including your patch, please submit to Homebrew.


Update dependencies - typescript to 3.0

Closes #824
Closes #825
Closes #816
Closes #744
Closes #779

Thanks!

Is there an ETA on when a new version of typedoc would be released with this change?

I'm hoping to release soon. I tried last night but ran into issues with a test timing out locally on my machine.


report_kuji: invalid URL. No scheme supplied

Hello,
Thank you very much for your staketax tool!
After following all installation instructions, I can successfully execute
python staketaxcsv/report_juno.py #JUNO_ADDRESS#
, but for KUJI, I get the following error message (see below).
Can you tell me what I may be doing wrong?
Thank you very much,
Best,
Ron

(base) $ python3 staketaxcsv/report_kuji.py #KUJI_ADDRESS#
INFO:root:localconfig: {'module': 'staketaxcsv.kuji.config_kuji', 'ibc_addresses': {}, 'contract_history': {}, 'doc': None, 'job': None, 'debug': False, 'cache': False, 'limit': 20000, 'koinlynullmap': None}
INFO:root:koinly NullMap: use_cache=False, json_path=/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/../_reports/koinly_null_map.json
INFO:root:Requesting url /cosmos/tx/v1beta1/txs?pagination.limit=50&pagination.offset=0&pagination.count_total=True&order_by=ORDER_BY_DESC&events=message.sender%3D%27kujira1fhr5s6awg0dud2g9pcm36xqgpxzr3lj0pv3puj%27 ...
Traceback (most recent call last):
File "/Users/ronlehnert/dev/staketaxcsv/src/staketaxcsv/report_kuji.py", line 81, in
main()
File "/Users/ronlehnert/dev/staketaxcsv/src/staketaxcsv/report_kuji.py", line 22, in main
report_util.main_default(TICKER_KUJI)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/report_util.py", line 17, in main_default
run_report(ticker, wallet_address, export_format, txid, options)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/report_util.py", line 28, in run_report
staketaxcsv.api.csv(ticker, wallet_address, export_format, path, options)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/api.py", line 100, in csv
exporter = module.txhistory(wallet_address)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/report_kuji.py", line 61, in txhistory
count_pages = staketaxcsv.common.ibc.api_lcd_v1.get_txs_pages_count(KUJI_NODE, wallet_address, max_txs, debug=localconfig.debug)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/ibc/api_lcd_v1.py", line 173, in get_txs_pages_count
_, _, num_txs = api.get_txs(address, event_type, offset=0, limit=limit, sleep_seconds=sleep_seconds)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/ibc/api_lcd_v1.py", line 98, in get_txs
data = self._get_txs(wallet_address, events_type, offset, limit, sleep_seconds)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/debug_util.py", line 19, in wrapper
return func(*args, **kwargs)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/ibc/api_lcd_v1.py", line 93, in _get_txs
data = self._query(uri_path, query_params, sleep_seconds)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/staketaxcsv-0.0.1-py3.10.egg/staketaxcsv/common/ibc/api_lcd_v1.py", line 31, in _query
response = self.session.get(url, params=query_params)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/requests/sessions.py", line 600, in get
return self.request("GET", url, **kwargs)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/requests/sessions.py", line 573, in request
prep = self.prepare_request(req)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/requests/sessions.py", line 484, in prepare_request
p.prepare(
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/requests/models.py", line 368, in prepare
self.prepare_url(url, params)
File "/Users/ronlehnert/miniconda3/lib/python3.10/site-packages/requests/models.py", line 439, in prepare_url
raise MissingSchema(
requests.exceptions.MissingSchema: Invalid URL '/cosmos/tx/v1beta1/txs': No scheme supplied. Perhaps you meant http:///cosmos/tx/v1beta1/txs?
(base) Laptop-von-Digidoc:src ronlehnert$

Ah, try:
export STAKETAX_KUJI_NODE=<some_lcd_url_>

Ah yeah, I probably should provide better error message or clues since lots of folks run into this.  For some like KUJI, you need to supply the environment variable like above.

Sample list of kuji lcd urls: https://github.com/hodgerpodger/staketaxcsv/blob/main/src/staketaxcsv/cosmosplus/list_lcd.json
The environment variables that need to be filled in for certain reports can be found at sample.env.  I did not want to use some nodes as defaults for various reasons.

Thank you very much, hodgerpodger!


Issue 174 acl

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #174
Test URLs:

Before: https://main--zemax--hlxsites.hlx.page/
After: https://issue-174-acl--zemax--hlxsites.hlx.page/

@synox Please take a look I have some pending issues which I will fix as a bug. thanks


Some questions about evaluation metrics

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (master) or latest version (3.x).

💬 Describe the reimplementation questions

What is the difference between different evaluation metrics？
If I want to calculate corloc, how should I do it?

Environment
sys.platform: linux
Python: 3.7.12 | packaged by conda-forge | (default, Oct 26 2021, 06:08:21) [GCC 9.4.0]
CUDA available: True
GPU 0,1,2: GeForce RTX 2080 Ti
CUDA_HOME: /usr/local/cuda-11.0
NVCC: Build cuda_11.0_bu.TC445_37.28845127_0
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
PyTorch: 1.7.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.4-Product Build 20210904 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v1.6.0 (Git Hash 5ef631a030a6f73131c77892041042805a06064f)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 10.2
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75
CuDNN 7.6.5
Magma 2.5.2
Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.8.0
OpenCV: 4.6.0
MMCV: 1.2.0
MMCV Compiler: GCC 9.4
MMCV CUDA Compiler: 11.0
MMDetection: 2.6.0+fd6f994
Expected results
No response
Additional information
No response

coco metric is using IoU-thr as [0.5:0.95, 0.05] and voc style metric is using IoU thr = 0.5. For more details, it is suggested to have a look at the official evaluation documents.
MMDet is not supported calculating corloc yet.


reapplied clear image cache PR

Just reapplied this PR to latest version
https://github.com/DylanVann/react-native-fast-image/pull/425#issuecomment-906271383

Can we get this merged as its a very crucial feature. :)

@trickeyd I made a fork & pulled in this PR and switched off webp format as suggested by #46 but still get memory issues & a crash on iOS after 300-500 images.

LGTM! 🚢

Thanks for merging the original. I'll close this one.


add xml node property  row and column  in document file

sometimes, i need to know a xml_node's location in the document.
it's useful to edit xml from another program interface.  when edited, dynamically update the document, not reload the document.
thanks very much,  i like pugixml.

did you have finished this plan ?


Add Qwantify search engine to bots list and switch to using oop php

See github issue: https://github.com/WhichBrowser/Parser-PHP/issues/568
Qwantify Bot (current 1.0)
Qwantify Bot 1.0

Qwantify Bot (current 2.4w)
Mozilla/5.0 (compatible; Qwantify/2.4w; +https://www.qwant.com/)
Mozilla/5.0 (compatible; Qwantify/2.4w; +https://www.qwant.com/)/2.4w
Mozilla/5.0 (compatible; Qwantify/2.4w; https://www.qwant.com/)/2.4w

Qwantify News Bot
Mozilla/5.0 (compatible; Qwant-news/2.0; +https://www.qwant.com/)

Qwantify Bleriot Bot
Mozilla/5.0 (compatible; Qwantify/Bleriot/1.1; +https://help.qwant.com/bot)
user-agent Mozilla/5.0 (compatible; Qwantify/Bleriot/1.1; +https://help.qwant.com/bot;)
Mozilla/5.0 (compatible; Qwantify/Bleriot/1.1; +https://help.qwant.com/bot)
Mozilla/5.0 (compatible; Qwantify/Bleriot/1.2.1; +https://help.qwant.com/bot)

Qwantify Ai4eu Bot
Mozilla/5.0 (compatible; Qwantify/ai4eu/1.1; +https://help.qwant.com/bot;)

Qwantify Mermoz Bot
Mozilla/5.0 (compatible; Qwantify/Mermoz/0.1; +https://www.qwant.com/; +https://www.github.com/QwantResearch/mermoz)

Qwantify Vr Bot
Mozilla/5.0 (compatible; Qwantify/vR; +https://www.qwant.com/)

Qwant Research Bot
Mozilla/5.0 (compatible; Qwant Research Bot/1.0; +https://www.qwant.com/)

Reverse DNS
qwantbot-91-242-162-20.search.qwant.com

Dead Bots (2015 - 2016)
Qwantify
Mozilla/5.0 (compatible; Qwantify/2.3w; +https://www.qwant.com/)/2.3w
Mozilla/5.0 (compatible; Qwantify/2.2w; +https://www.qwant.com/)/*
Mozilla/5.0 (compatible; Qwantify/2.1dw; +https://www.qwant.com/)/*
Mozilla/5.0 (compatible; Qwantify/2.1w; +https://www.qwant.com/)/*
Mozilla/5.0 (compatible; Qwantify/2.1n; +https://www.qwant.com/)/*
Mozilla/5.0 (compatible; Qwantify/2.0n; +https://www.qwant.com/)/*
Mozilla/5.0 (compatible; Qwantify/2.0n; +https://www.qwant.com/)
Mozilla/5.0 (compatible; Qwantify/2.0; +https://www.qwant.com/)

Not going to add dead bots to this pr.
Link: https://www.qwant.com/
Link: https://help.qwant.com/bot

Coverage increased (+0.02%) to 99.97% when pulling 750a2ab8249a0e6126d15b9a8f52e9095750a308 on ayumi-cloud:Qwantify into 880b9fa797401d14b28956442944c3daa70240ff on WhichBrowser:master.

Add fake bot to the rules:
Mozilla/5.0 (compatible; Qwantbot/1.0; +https://qwantbot.net/)

cleaned version: https://github.com/summercms/Parser-PHP-v3.x.x/pull/174/files


Fix PYTHON_VERSION in travis installer

PYTHON_VERSION variable is empty, so we actually pass python= in conda create so Travis always tests scanpy with latest Python in Conda distribution. Therefore Python 3.5 is actually never tested. Furthermore, conda switched to python 3.7, so now all test are run on Python 3.7. This is also the reason of weird HDF error message we get in tests.

Thank you very much Gökcen! :smile:


[vcpkg] Add --nuget-description option for vcpkg export

Fixes #11989 as suggested by user

Thanks for your contribution!


Rebuild 3.1

…nda-forge-pinning 2<IP_ADDRESS>.28.41
Last build failed due to the missing image. Rerender should fix this.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge/core  , can you help with merging this PR? Thanks!


temporarily switch to a manual workflow for helm chart

Steps:

Manually release helm chart v1.2.0
Revert this PR
Re-release v1.2.1

To understand the context of this change better, it would be good to describe the motivation for the change in the PR description along with a Github issue referenced to indicate an existing problem it is attempting to circumvent.


In the new agenda, links in the material box don't open in a new window

Describe the issue

Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

I clicked on a link in the dispatch agenda to the slides.

Actually the box only show the agenda and not the rest of the material.

And one more issue about the new agenda (might be a separate issue, please decide to split up yourself): I have a setting to always show the left-side menu but it does not show up with the new agenda.

left menu for that page is a known issue

This might be a bit problematic to solve as the contents are rendered inside an iframe, but we could add <base target="_blank" /> to the page loaded inside the iframe to force all links to open in a new window (or _parent to re-use the same window).

@ngpixel if there's not a separate issue tracking left menu, please add one?

See #4285 for left menu.


all-caps must not be used for emphasis

Capital letters can be used only in a small number of scripts. They don't exist in Arabic, Hindi, Georgian, Chinese, and most other languages.
Because of this, relying only on all-caps, as in "Please do NOT upload" makes it impossible to translate the emphasis into languages that don't have capital letters.
The emphasis must be added using some other design method.

Hm, we already have big red X's on the images above this text, so I wouldn't say that the capitals are absolutely essential to making the point. Is it possible to have caps in languages where it makes sense, and just omit it where it doesn't?

Yes, it's possible, but then isn't the big X enough for these languages, too? :)
If you insist on having capital letters in languages in the Latin alphabet, and you thing it's OK not to translate it, please do mention this in the corresponding string under values-qq.

Please bear with me here. Does something like the below suffice?
<string name="tutorial_3_text" values-qq="Caps not required">Please do NOT upload:</string>

Yes, that's OK. Thank you.


RuntimeError: CuDNN Error: CUDNN_STATUS_MAPPING_ERROR

When I ran the docker, I first got the found no nvidia driver error as issue. After installing nvidia-container, the problem seemed solved.
Then I tried again the following command. Since I have 2 cards on the machine, only card 0 is assigned.
sudo docker run -it --rm --gpus='"device=0"' -v xxx:/input -v xxx:/output --entrypoint bash jukemir/representations_jukebox
And then,
python main.py --batch_size 8
After a few minutes (of initializing I guess), I got the following error:
Traceback (most recent call last):
File "main.py", line 177, in
representation = get_acts_from_file(input_path, hps, vqvae, top_prior, meanpool=True)
File "main.py", line 86, in get_acts_from_file
z = get_z(audio, vqvae)
File "main.py", line 27, in get_z
zs = vqvae.encode(torch.cuda.FloatTensor(audio[np.newaxis, :, np.newaxis]))
File "/code/jukebox/jukebox/vqvae/vqvae.py", line 141, in encode
zs_i = self._encode(x_i, start_level=start_level, end_level=end_level)
File "/code/jukebox/jukebox/vqvae/vqvae.py", line 132, in _encode
x_out = encoder(x_in)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/code/jukebox/jukebox/vqvae/encdec.py", line 80, in forward
x = level_block(x)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/code/jukebox/jukebox/vqvae/encdec.py", line 26, in forward
return self.model(x)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/container.py", line 100, in forward
input = module(input)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/container.py", line 100, in forward
input = module(input)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/conv.py", line 202, in forward
self.padding, self.dilation, self.groups)
RuntimeError: cuDNN error: CUDNN_STATUS_MAPPING_ERROR
I googled it and added torch.backends.cudnn.enabled = False to main.py but a new problem occurred:
Traceback (most recent call last):
File "main.py", line 179, in
representation = get_acts_from_file(input_path, hps, vqvae, top_prior, meanpool=True)
File "main.py", line 88, in get_acts_from_file
z = get_z(audio, vqvae)
File "main.py", line 29, in get_z
zs = vqvae.encode(torch.cuda.FloatTensor(audio[np.newaxis, :, np.newaxis]))
File "/code/jukebox/jukebox/vqvae/vqvae.py", line 141, in encode
zs_i = self._encode(x_i, start_level=start_level, end_level=end_level)
File "/code/jukebox/jukebox/vqvae/vqvae.py", line 132, in _encode
x_out = encoder(x_in)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/code/jukebox/jukebox/vqvae/encdec.py", line 80, in forward
x = level_block(x)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/code/jukebox/jukebox/vqvae/encdec.py", line 26, in forward
return self.model(x)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/container.py", line 100, in forward
input = module(input)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/container.py", line 100, in forward
input = module(input)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in call
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/conv.py", line 202, in forward
self.padding, self.dilation, self.groups)
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling cublasSgemm( handle, opa, opb, m, n, k, &alpha, a, lda, b, ldb, &beta, c, ldc)
Did I miss anything?

I solved the problem by copying the souce codes from docker to my local dir and run in my own conda env. Seems the preblem originated from environment issues.


When delete application, how to put the account and password empty?

Because I test found that, when the APP delete, and then when installation can still get a user name and password

This is the expected behavior of the system keychain.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9a9cml4rne/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_9a9cml4rne/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_9a9cml4rne/clone/recipe/meta.yaml:31: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_9a9cml4rne/clone/recipe/meta.yaml:39: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_9a9cml4rne/clone/recipe/meta.yaml:39: http_url: http://feature-engine.readthedocs.io/ is not https
WARNING: /tmp/abs_9a9cml4rne/clone/recipe/meta.yaml:39: missing_description: The recipe is missing a description
Errors were found


fix: update tinygo to resolve package issue

Detailed description:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist

[ ] Documentation added
[ ] Tests updated

I'm closing this one since the fix has been reverted, as the error cannot be reproduced


Publish pipeline artifact - failed with error that the artifact already exists

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: PublishPipelineArtifact@0
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:  61677

Issue Description
The task failed with error saying the artifact already exists, but I am pretty sure the name is unique and only only used once.
on rerun, the task passed and I don't remember seeing this error before.
Task logs
2020-04-17T08:18:09.4008730Z ##[section]Starting: Publish SelfSigned
2020-04-17T08:18:09.4030790Z ==============================================================================
2020-04-17T08:18:09.4031650Z Task         : Publish pipeline artifact
2020-04-17T08:18:09.4032410Z Description  : Publish a local directory or file as a named artifact for the current pipeline
2020-04-17T08:18:09.4033120Z Version      : 0.140.0
2020-04-17T08:18:09.4033680Z Author       : Microsoft Corporation
2020-04-17T08:18:09.4034430Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/publish-pipeline-artifact
2020-04-17T08:18:09.4035240Z ==============================================================================
2020-04-17T08:18:09.8812340Z Uploading pipeline artifact from /Users/runner/runners/2.165.2/work/1/s/.build/darwin/archive/azuredatastudio-darwin.zip for build #61677
2020-04-17T08:18:10.9594780Z Information, ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session 50718340-f273-47a9-a5d0-514f56f3a706
2020-04-17T08:18:10.9917040Z Information, DedupManifestArtifactClient will correlate http requests with X-TFS-Session 50718340-f273-47a9-a5d0-514f56f3a706
2020-04-17T08:18:12.8741720Z Information, 1 files processed.
2020-04-17T08:18:12.8753470Z Information, Processed 1 files from /Users/runner/runners/2.165.2/work/1/s/.build/darwin/archive successfully.
2020-04-17T08:18:16.1239420Z Information, Uploading 1 files from directory /Users/runner/runners/2.165.2/work/1/s/.build/darwin/archive to Drop service.
2020-04-17T08:18:16.1245490Z Information, Uploaded 0 out of 140,692,601 bytes
2020-04-17T08:18:16.1286980Z Information, Batcher OutputCount: 0  Uploader queue: 0  Active Upload sessions: 1.
2020-04-17T08:18:21.1337940Z Information, Uploading 1 files from directory /Users/runner/runners/2.165.2/work/1/s/.build/darwin/archive to Drop service.
2020-04-17T08:18:21.1339130Z Information, Uploaded 0 out of 140,692,601 bytes
2020-04-17T08:18:21.1339900Z Information, Batcher OutputCount: 0  Uploader queue: 0  Active Upload sessions: 1.
2020-04-17T08:18:26.2162830Z Information, Uploading 1 files from directory /Users/runner/runners/2.165.2/work/1/s/.build/darwin/archive to Drop service.
2020-04-17T08:18:26.2163950Z Information, Uploaded 20,115,585 out of 140,692,601 bytes
2020-04-17T08:18:26.2164730Z Information, Batcher OutputCount: 0  Uploader queue: 0  Active Upload sessions: 1.
2020-04-17T08:18:28.3882160Z Information, Uploaded 40,972,441 out of 140,692,800 bytes
2020-04-17T08:18:28.3883050Z Information, Content upload is done!
2020-04-17T08:18:28.3892770Z Information,
2020-04-17T08:18:28.3893360Z Content upload statistics:
2020-04-17T08:18:28.3893860Z Total Content: 281.4 MB
2020-04-17T08:18:28.3894310Z Physical Content Uploaded: 40.4 MB
2020-04-17T08:18:28.3894820Z Logical Content Uploaded: 41.0 MB
2020-04-17T08:18:28.3895360Z Compression Saved: 0.6 MB
2020-04-17T08:18:28.3895810Z Deduplication Saved: 240.4 MB
2020-04-17T08:18:28.3896260Z Number of Chunks Uploaded: 511
2020-04-17T08:18:28.3896630Z
2020-04-17T08:18:29.8842300Z Warning, [] Try 1/3, non-retryable exception caught. Throwing. Details:
2020-04-17T08:18:29.8844300Z No LastRequestResponse on exception ArtifactExistsException: Artifact darwin-selfsigned already exists for build 61677. Microsoft.TeamFoundation.Build.WebApi.ArtifactExistsException: Artifact darwin-selfsigned already exists for build 61677.
2020-04-17T08:18:29.8846120Z    at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
2020-04-17T08:18:29.8847270Z    at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
2020-04-17T08:18:29.8848460Z    at Microsoft.TeamFoundation.Build.WebApi.BuildHttpClientCompatBase.SendAsync[T](HttpRequestMessage message, Object userState, CancellationToken cancellationToken, Func3 processResponse) 2020-04-17T08:18:29.8849930Z    at Microsoft.TeamFoundation.Build.WebApi.BuildHttpClientCompatBase.SendAsync[T](HttpMethod method, IEnumerable1 additionalHeaders, Guid locationId, Object routeValues, ApiResourceVersion version, HttpContent content, IEnumerable1 queryParameters, Object userState, CancellationToken cancellationToken, Func3 processResponse)
2020-04-17T08:18:29.8852060Z    at Agent.Plugins.PipelineArtifact.BuildServer.AssociateArtifactAsync(Guid projectId, Int32 pipelineId, String name, String jobId, String type, String data, Dictionary2 propertiesDictionary, CancellationToken cancellationToken) 2020-04-17T08:18:29.8853190Z    at Agent.Plugins.PipelineArtifact.PipelineArtifactServer.<>c__DisplayClass2_1.<<UploadAsync>b__2>d.MoveNext() 2020-04-17T08:18:29.8854440Z --- End of stack trace from previous location where exception was thrown --- 2020-04-17T08:18:29.8855320Z    at Microsoft.VisualStudio.Services.Content.Common.AsyncHttpRetryHelper1.InvokeAsync(CancellationToken cancellationToken)
2020-04-17T08:18:29.8860140Z Information, ApplicationInsightsTelemetrySender correlated 2 events with X-TFS-Session 50718340-f273-47a9-a5d0-514f56f3a706
2020-04-17T08:18:29.8905370Z ##[error]Artifact darwin-selfsigned already exists for build 61677.
2020-04-17T08:18:29.9055000Z ##[section]Finishing: Publish SelfSigned

turns out someone from our team did rerun the job.

I am also having that issue, is there any solution for that?
@alanrenmsft

@BoazWarshawsky I don't see a task available to delete pipeline artifact, I guess you shouldn't be rerunning the failed jobs to avoid this problem

We had the same issue when one pushes twice in small time interval. So the PR triggered the pipeline twice in the same 60 seconds, resulting in the same fail. Is there an option to turn off batch per PR?

I'm having the same issue.
It makes no sense to have a task that can only run once if the pipeline can run often because of retries or a failure after the artifact was published.
This is a bug and should be fixed. It should allow the publishing of the artifact again in case the build has failed.
So now I have a failing build and can't use the retry feature because of this. Makes no sense.

was there ever a solution for this, to override existing artifact?

I do not like commenting on old "closed" issues. But to those who will benefit from this work-around:
In this case it'll use the JobAttempt as a prefix.. I do not like it but it works.
      - publish: $(System.DefaultWorkingDirectory)/my-artifact
        artifact: $(System.JobAttempt)-my-artifact
        condition: always()

Assuming that artifacts are the product of a successful run up until the step where the artifact is published, what about checking and using this artifact, then continue from this step in the event a re-run is required?
I have to re-run the deployment because a connection was not shared with the SPN, so if I'm bound to using ALM Accelerator I would basically need to commit some irrelevant changes and build the entire solution again just for it to do the deployment 🤔

I agree this is a bug.
We had this issue when trying to re-run failed jobs. To fix this, we made the publish task dependOn the tasks before:
https://learn.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops
This way, it would only publish once we were happy with the artifacts that would be published. Cant protect against failures later on in the pipeline. Though, if your publish task depends on tasks run later on, it might make sense to let it actually dependsOn them.

+1
Why is this issue "closed". Same issue here.

Experienced the same and the run should see it as different
Below worked for me (replace your details  : you're "crazy stack", subscriptions , DEV app name , PROD app name, both env names of pipeline)  :
This is DEV   >>>   Approval Step   >>>   PROD
*confirm it by looking at both "Download Artifact" steps

`
Node.js Express Web App to Linux on Azure
Build a Node.js Express app and deploy it to Azure as a Linux web app.
Add steps that analyze code, save build artifacts, deploy, and more:
https://docs.microsoft.com/azure/devops/pipelines/languages/javascript
trigger:

main

variables:
Azure Resource Manager connection created during pipeline creation
azureSubscriptionPROD: '########-####-####-####-############'
azureSubscriptionDEV: '########-####-####-####-############'
Web app name
webAppNamePROD: 'prod-app'
webAppNameDEV: 'dev-app'
Environment name
environmentNamePROD: 'prod-env'
environmentNameDEV: 'dev-env'
Agent VM image name
vmImageName: 'ubuntu-latest'
stages:

stage: Build_DEV
displayName: Build DEV stage
jobs:

job: Build
displayName: Build DEV stage
pool:
vmImage: $(vmImageName)
steps:

task: NodeTool@0
inputs:
versionSpec: '20.x'
displayName: 'Install Node.js'

script: |
npm install
npm run build --if-present
npm run test --if-present
displayName: 'npm install, build and test'

task: ArchiveFiles@2
displayName: 'Archive files'
inputs:
rootFolderOrFile: '$(System.DefaultWorkingDirectory)'
includeRootFolder: false
archiveType: zip
archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
replaceExistingArchive: true

upload: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
artifact: drop

stage: Deploy_DEV
displayName: Deploy code to DEV app
dependsOn: Build_DEV
condition: succeeded()
jobs:

deployment: Deploy
displayName: Deploy
environment: $(environmentNameDEV)
pool:
vmImage: $(vmImageName)
strategy:
runOnce:
deploy:
steps:
- task: AzureWebApp@1
displayName: 'Azure Web App Deploy: dev-app'
inputs:
azureSubscription: $(azureSubscriptionDEV)
appType: webAppLinux
appName: $(webAppNameDEV)
runtimeStack: 'NODE|20LTS'
package: $(Pipeline.Workspace)/drop/$(Build.BuildId).zip
startUpCommand: 'npm run start'

stage: Review_DEV_App
displayName: Review DEV deployed app dev-app
dependsOn: Deploy_DEV
condition: succeeded()
jobs:

job: waitForValidation
displayName: Wait for external validation
pool: server
timeoutInMinutes: 4320 # job times out in 3 days
steps:

task: ManualValidation@0
timeoutInMinutes: 1440 # task times out in 1 day
inputs:
notifyUsers: |
<EMAIL_ADDRESS>instructions: 'Please validate the DEV build before release to PROD'

stage: Build_PROD
displayName: Build PROD stage
dependsOn: Review_DEV_App
condition: succeeded()
jobs:

job: Build
displayName: Build PROD stage
pool:
vmImage: $(vmImageName)
steps:

task: NodeTool@0
inputs:
versionSpec: '20.x'
displayName: 'Install Node.js'

script: |
npm install
npm run build --if-present
npm run test --if-present
displayName: 'npm install, build and test'

stage: Deploy_PROD
displayName: Deploy code to PROD app
dependsOn: Build_PROD
condition: succeeded()
jobs:

deployment: Deploy
displayName: Deploy
environment: $(environmentNamePROD)
pool:
vmImage: $(vmImageName)
strategy:
runOnce:
deploy:
steps:
- task: AzureWebApp@1
displayName: 'Azure Web App Deploy: prod-app'
inputs:
azureSubscription: $(azureSubscriptionPROD)
appType: webAppLinux
appName: $(webAppNamePROD)
runtimeStack: 'NODE|20LTS'
package: $(Pipeline.Workspace)/drop/$(Build.BuildId).zip
startUpCommand: 'npm run start'
`


changes to add the UTC time for errors

also a test to assert it remains so

This looks goods - I adjusted the format a bit and updated from master since there were a lot of PRs merged in between. I'll merge as soon as Travis reports back.


Look into spellchecking

This is a quick look into spell checking the docs.
Vale is a super extensible linter written in go. If you want to run it yourself:

Install vale
Run vale pages
Optionally install an editor plugin for Atom

Work still to do:

[ ] clean up the word list in vale/vocab.txt
[ ] make better exceptions (probably most of the agent/v3/_help dir, some html tags, some code that isn't detected as code, etc)
[ ] add to CI :-p

CC @harrietgrace take a look, even if we're not yet good to go.
And if we ever need to figure out how to populate the vocab file again:

Delete vale/vocab.txt
Run vale without the custom work file :point_up:

specify json output
grep out all matches with nasty regex
sort them and restrict to one of each match
strip out leading characters with nasty regex
strip out trailing characters with nasty regex
dump the lot into the vocab file

$ vale --output JSON pages/ | ack Match | sort | uniq | sed "s/\s*\"Match\": \"//" | sed "s/\"$//" > vale/vocab.txt

Everything except ba2ec91 and 4842023 are actual typo fixes. I'll cherry pick them out if this looks like it is going to hang around long.
:eyes: especially welcome on vale/vocab.txt in case I've missed anything obvious.

So psyched for this! It's looking great 🌈
Omg so many spelling mistakes 😱

Hey @matthewd thanks for the :eyes:
What is happening is that the vale spell check comes with built in "filters for acronyms, abbreviations, and numbers." and think that includes camel case stuff.
So probably some code in there is getting treated as text. I suspect the help files. For example, removing http from the vocab list gives us
 pages/agent/v3/help/_artifact_upload.txt
 32:39  error  Did you really mean 'http'?  Vale.Spelling

 pages/integrations/cc_menu.md.erb
 47:1  error  Did you really mean 'http'?  Vale.Spelling
 51:1  error  Did you really mean 'http'?  Vale.Spelling

✖ 3 errors, 0 warnings and 0 suggestions in 152 files.

The CC_menu page needs refactoring, and it looks like the indented code block in the help pages indeed are showing up as text.
So over all, it is a slight chicken egg situation with needing to get the amount of errors down to something manageable to be able to look at them.
I'll try to remove a ton more of the stuff that looks like URL contents and see what gets flagged. Overall, keeping the vocal list as small as possible is best I think.
And I need to make sure the case sensitive stuff works as well.

Yeah, looks like the blocks in the help aren't indented right to be detected as code. Making it four spaces instead of one tab and one space makes them not turn up.

There is probably a better way than pulling the installer every time.

Alright, after a long rambling PR mostly talking to myself, I'm ready to merge this in.
I'll track proposed enhancements to the linter separately.


Segmentation violation on splash screen destroy (Linux)

Hi All,
Built the suite from source on my Ubuntu (Xenial) system. LimeSuiteGUI would segfault, it flicked open the tiny splash window, the console prints:
cmcmanis@qbert:build$ LimeSuiteGUI
[INFO] LMS7002M cache /home/cmcmanis/.limesuite/LMS7002M_cache_values.db
Visible GUI update time: 0
Visible GUI update time: 0
Create time 0 ms
Segmentation fault (core dumped)
cmcmanis@qbert:build$

I reran Cmake to build a debug version and tracked the segfault to line 47 of lms7suiteApp.cpp
(gdb) run
Starting program: /usr/bin/LimeSuiteGUI
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec74a700 (LWP 16536)]
[New Thread 0x7fffebf49700 (LWP 16544)]
Visible GUI update time: 0
Visible GUI update time: 0
Create time 0 ms

Thread 1 "LimeSuiteGUI" received signal SIGSEGV, Segmentation fault.
0x0000000000e0b7e0 in ?? ()
(gdb) where
#0  0x0000000000e0b7e0 in ?? ()
#1  0x000000000058994a in lms7suiteApp::OnInit (this=0xcd6920)
    at **/home/cmcmanis/src/limesuite/src/lms7suiteApp.cpp:47**
#2  0x0000000000589aed in wxAppConsoleBase::CallOnInit (this=0xcd6920)
    at /usr/include/wx-3.0/wx/app.h:93
#3  0x00007ffff68cbf92 in wxEntry(int&, wchar_t**) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#4  0x00000000005897a8 in main (argc=1, argv=0x7fffffffe538)
    at /home/cmcmanis/src/limesuite/src/lms7suiteApp.cpp:25
(gdb)

Which calls splash->Destroy();. If I comment out that line and re-build then it runs without segfaulting. Very strange but perhaps a WX bug?

Current, LimeSuiteGUI is being tested and does not crash on splash screen on Ubuntu 16.04 (xenial) with wxWidgets installed from libwxgtk3.0-dev packages or compiled from source (current latest stable release: 3.0.4) .


install problems -> new ComlinkWorker "not found"

HI there, i am trying to get vite-plugin-comlink to run, but cannot find the problem why it would not work:
i have followed the install readme so my vite.config.ts looks like that:
import react from '@vitejs/plugin-react'
import { defineConfig } from 'vite'
import { comlink } from 'vite-plugin-comlink'
import EnvironmentPlugin from 'vite-plugin-environment'

// https://vitejs.dev/config/
export default ({ mode }) => {
  console.error('vite mode', mode)
  return defineConfig({
    envPrefix: 'REACT_APP_',
    logLevel: 'info',
    esbuild: {
      pure: ['console.log', 'console.time', 'console.timeEnd', 'console.warn'],
      minify: ['production', 'preview'].includes(mode),
    },
    plugins: [
      comlink(), // must be the first plugin...
      react(),
      EnvironmentPlugin('all', { prefix: 'REACT_APP_' }),
      EnvironmentPlugin({ PUBLIC_URL: '' }),
    ],
    worker: {
      plugins: [comlink()],
    },
  })
}

vite-env.d.ts looks like this:
/// <reference types="vite/client" />
/// <reference types="vite-plugin-comlink/client" />

vite-plugin-comlink is installed via yarn add vite-plugin-comlink (3.0.4).
the Problem is, when i try to create a new ComlinkWorker like so:
const instance = new ComlinkWorker(new URL('./worker.js', import.meta.url) i get any
Cannot find name 'ComlinkWorker'.ts(2304)
Where did i do something wrong? what can be  the Problem?
Any help would be awesome!
Thanks a lot!

never mind... the vite-env.d.ts was in the wrong place.

I am getting the same error where should vite-env.d.ts should be at?

Important is that vite-plugin-comlink/client is used by typescript.
That can be done by
/// <reference types="vite-plugin-comlink/client" />

In the vite-env.d.ts file if generated or by adding it to tsconfig.


Question : How can I manually set filename?

I am working on uploading profile image. I want to manually set my filename to their userId so that when the same user upload new profile image, it will replace the old one. I found how to set directory in #61 , but I still can't figure out how to manually set the filename.
Thank you :)

<ReactS3Uploader                     className = "upload-img-input-btn form-control center-block"                     signingUrl="/api/s3/sign"                     accept="image/*"                     onProgress={this.onUploadProgress.bind(this)}                     onError={this.onUploadError}                     onFinish={this.onUploadFinish.bind(this)}                     signingUrlHeaders={{ additional: 'Access-Control-Allow-Origin'}}                     uploadRequestHeaders={{ 'x-amz-acl': 'public-read' }}                     contentDisposition="auto"                 />
This is my code on react side

No functionality currently built to support this, but it can be easily added.  Just need to support an optional filekey modifier/processor function, which would let you change the filekey based on the session or whatnot.  Code would be plugged in right around here: https://github.com/odysseyscience/react-s3-uploader/blob/master/s3router.js#L69
I don't have time to build this right now, but if you want to take a stab at a PR, I'll be happy to merge and release.

I can manually set it now. I also forked it. Don't know if I did it correctly though. haha
Thank you again.

Just released v4.0.0 which changes the filename scrubbing logic, and provides a simple way to add custom scrub logic.  Check out the updated documentation if you still need this functionality.
Thanks


Setup of integration failed: Could not connect to local Tibber Pulse Bridge

Hi,
first thank you very much for this integration. Documentation is really good. But having issues setting up this integration.

(I replaced the last 4 chars of the password with XXXX)
The REST Template works fine:

Please help :-)
As far as I read your code, the host should be hostname without leading http://, maybe this should be updated in your docs

could you please be so kind and check, in which mode your bridge is running? - I assume it will be something different then the current "only" supported mode SML...
How to find information about the mode can be found here...
https://github.com/marq24/ha-tibber-pulse-local/issues/1
and if you are having a new/unsupported mode - please provide details here... TIA

Sorry for my late reply. After spamming the Submit Button for 10 Minutes, the integration accepted the values and initialized. The received data is much more stable but still not updated every 2-10 seconds (~4 minutes) - but I think this is worth another ticket ;-)

please be so kind and enable the debug log (for the integration) an check if you have (also) this intense occurrence of the CRC errors... (would like to know, if you have the same issue as #6)

Fixed in #6

"fixed by rotation" ;-)


Test: fix MSS tests: delete bootstrapped templates

ManagedSubjectService intergration tests checking outgoing emails were
failing because bootstrapped EmailTemplates were taking over the
templates provided in tests.
Explicitly delete the bootstrapped templates in test setup to fix the tests.

@vladimir-mencl-eresearch do you recall why bootstraped email templates existed in the database being used to run grails tests against to start with?
I can't recall having ever done that (however it has been a while so it is highly likely I've forgotten about some specific context).

Well, several tests in virtualhome/test/integration/aaf/vhr/ManagedSubjectServiceSpec.groovy test whether "the right email is sent".  And the test injects the template into the database.  And leaves it there.  And the next test tries to inject a template with the same ID - and because it already exists, it used the existing one.  But with a different wording.  And the tests check whether the message body is what is expected - but check it against the wording used in the template the test tried to install.
I had 3 integration tests failing - and zapping the email template before the test tried to install its own version fixed it...

@vladimir-mencl-eresearch good enough reasoning for me then, strange I never saw previously.
¯_(ツ)_/¯


Cannot access to the supplementary material of the paper

first of all, thanks for your nice work!
I am currently reading your work, but I can't have access to the supplementary materials (https://bit.ly/3blZMgc)
How can I get this...?

Thank you for ur interest. In our final version, we have included almost all the content in our main paper, which can be found here https://www.cse.ust.hk/~weiwa/papers/metis-sc20.pdf.
And the appendix u mention here has been removed.

Okay. Thanks for your kind help!


Added doc note FW rule for GKE private clusters

Hello,
Raising a PR for an important note on how to get Rancher working correctly in a GKE private cluster.
Fixes https://github.com/rancher/rancher/issues/29451

lgtm


Overworld structures in Eternal Dimension (Neoforge 1.21.1)

Hello, I just installed the mod to explore and it's great. Unfortunately I found that overworld structures are generated in this dimension (Iron's Spells 'n Spellbooks, Dungeons Arise for example) so I wanted to inform you. Greetings

Maybe it's caused by data-driven structure generation.
For example, in file data/irons_spellbooks/tags/worldgen/biome/has_structure/evoker_fort:
{
  "replace": false,
  "_comment": " This biome tag can specify the biome directly. Or specify another biome tag by starting with # ",
  "values": [
    "#minecraft:is_hill",
    "#minecraft:is_forest",
    "#c:is_desert",
    "#c:is_plains",
    "minecraft:windswept_savanna",
    "minecraft:savanna",
    "minecraft:savanna_plateau"
  ]
}

To solve this issue on eternal starlight side, we need to remove all #c:is_{some_type} tags for eternal starlight biomes. However these tags are not only used for determining structure generation, but also for some other game mechanics.

See also:
https://github.com/iron431/irons-spells-n-spellbooks/issues/654

Will fix soon, I'll just delete those c tags


Add support for customizing Add component buttons

This is a suggested approach to the request in #274 for the ability to fully customize the "Add" buttons.
This update will include three solutions that are mentioned in the issue:

Ability to update the popover labels (perhaps to provide translated buttons or to tweak the terminology)
Ability to invoke the addCardObj and addSectionObj from outside FormBuilder (perhaps this could be used to create custom buttons on a sidebar or elsewhere in the parent application)
Ability to provide custom components to replace the popover as needed (perhaps if someone wants a different UX that does not involve a popover)

I also updated the documentation with detailed examples. I wasn't sure if an example should be added to the demo page, but open to discussing this if needed.
I tried to follow the code conventions that I saw and I used mods to provide these capabilities. I welcome any feedback or suggested edits! 🤠
Of Note: I noticed there are some errors showing when running unit tests, however all tests are passing. These errors also show on the main branch. Seems unrelated to the work done here.

I have fixed the flow lint error

@nateplusplus There is still a Flow failure: https://github.com/ginkgobioworks/react-json-schema-form-builder/actions/runs/4932376049/jobs/8815657139?pr=455#step:5:38

I have fixed the flow lint error

I sit possible that you didn't push the commit fixing the flow error? I see comment but not a commit accompanying it.


Formatting issue with nested CascadingValue components

This issue has been moved from a ticket on Developer Community.

[severity:It bothers me. A fix would be nice]
The autoformat for .razor pages in blazor webassembly is wrong in strange ways.
The code below as a demo, The indent goes wrong after the @if() and is the result of the ctrl + k + d
@if (Object1!= null)
{
	<CascadingValue Value="Variable1">
		<CascadingValue Value="Variable2">
			<SomeRazorPage1  />
			@if (VarBool)
		{

				<SomeRazorPage2  />
				<SomeRazorPage3  />

		}
	</CascadingValue>
</CascadingValue>
}

I tried to record it, but my computer could not handle it.

Original Comments
Feedback Bot on 20/01/2022, 02:03 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

A similar issue occurs when you put different elements within a div on separate lines.
@if (_showDatepicker)
{
	@foreach (var day in _no_of_days)
	{

 ClickDate(day)"
		 class="cursor-pointer text-center text-sm leading-none rounded-full leading-loose transition ease-in-out duration-100 @(_inSelectedMonth && day == _day ? "bg-red-600 text-gray-100" : "")">
				@day

	}
}

Note to future self: This will probably be a pain as the generated C# content in this case is indented less that in normal nested scenarios, and I don't think the formatting code handles negative numbers :(


no support for zero size components in environment definitions

There does not seem to be a way to define a component without building it for all environments.  some environments may not need certain components, or may share components with other environments, and so shouldn't need to be built out in all environments.  utility servers, smtp, proxy, etc would all fit that design, but can't be provisioned with elevage as it can only provision full environments.  I've tried setting count to false, zero, etc, but it fails a health check when running.

@ncheneweth I think more accurately, @pharvey42 is seeking a way to be able to omit select components from an environment within the platform definition.
Alternately, if this is concerning the ability to provision "utility" components which service the entire platform (bastions/jump boxes, etc.), should it even be part of the platform definition, or managed in its own separate platform definitions?


Conversion issue for float32 images with large dynamic

Description
For certain types of images with float32 and large dynamic, the int16 conversion is inadapted, resulting in failing of OptiC algorithm.
Steps to Reproduce
Data: sct_testing/large/ucl_2017-grussu_01/t2s
# this will fail:
sct_get_centerline -i t2s.nii.gz -c t2s
# this will work, after rescaling the image:
sct_maths -i t2s.nii.gz -div 100000 -o t2s_scaled.nii.gz
sct_get_centerline -i t2s_scaled.nii.gz -c t2s

State of spinalcordtoolbox
v3.0.7
Additional Information
Conversion to int16:

Conversion to int16 after rescaling:

Also, it would be nice to take the opportunity to remove the file "_int16_RPI" at the end.


Adding support for HTTPs backends with Kubernetes ExternalName services

What does this PR do?

Motivation

More

[ ] Added/updated tests
[ ] Added/updated documentation

Additional Notes

Please check the code, it's my first Golang attempt. I've used a new variable to determine if the protocol should be http or https. In the original code, there was only support for http.
I've already  checked it and it's working as expected: docker -> kpeiruza/traefik:2.0


datagen --csvfile fails with model/lens setting

datagen.py --csvfile Dataset/triangle.csv segfaults; with triangle2.csv it succeeds.  Only difference is that the latter uses config instead of lens/model columns.

This was a problem using Raytrace+PM which is undefined.


Use forked ldapjs to remove dtrace

Fixes #1756.
There are endless isues with dtrace, e.g. #2016. There are 2 commits on top ldapjs that remove bunyan and dtrace-provider dependencies.
This fork isn't going to be maintained (I archived the repo), just like the main project, which is why it was forked in the firstp lace.

Conflicts

The new maintainer of node-ldapjs has mentioned he would go through open PRs and bugs this week, so I say let's give them a chance to do that :) If by the end of this week there is no activity on the repo, then it's fair to proceed :(

@astorije We can easily revert back if they do start to maintain.

Yeah, I'm with @xPaw ... even if it gets fixed, it'll take some time. Meanwhile this is an issue on our current release. So, let's merge this in, and if it gets sorted in upstream we can switch back.

Well, clearly nothing is happening with node-ldapjs yet, so just merge it.
In other news, I can't merge PRs again :-\


"Index was outside the bounds of the array." error

v0.9.2
No matter what I try, I get "Index was outside the bounds of the array."
Here's the correct version of the command I should be typing (based on the IDs in the MKV file):
Sushi.Net.exe --type subtitle --src-script=5 --src-audio=4 --dst-audio=2 --src "bd.mkv" --dst "uhd.mkv"
[Demuxer] Getting Media information for bd.mkv
[Demuxer] Getting Media information for uhd.mkv
[Sushi] Using default track 1 (Surround 5.1): truehd, 48000 Hz, 5.1(side), s32 (24 bit) (default) in bd.mkv
[Sushi] Using default track 1 (Surround 5.1): pcm_s24le ([1][0][0][0] / 0x0001), 48000 Hz, 5.1(side), s32 (24 bit), 6912 kb/s (default) in uhd.mkv
[Sushi] Index was outside the bounds of the array.

I tried all 0, all 1, and all 2, but nothing worked.
I have a Japanese UHD Blu-ray of a movie that I originally only had a US Blu-ray. I want to put the US Blu-ray's subtitles in the Japanese release. Both have the same Japanese audio, so I want to move it there, but the English audio is the first one on the US release, so I need to choose the correct audio ID.
What am I doing wrong to get that error?

Sorry for the delay, does the original file have image subtitles?
Image subtitles are not supported at the moment.
Anyway, the good news, is, all this years, i was updating this project, but didn't commit to this repo, because i need to clean it up first. So a new version is incoming....

That's a great question. I'm actually not sure how to check for image subtitles other than maybe going through the file itself.
I can't remember which one I was trying that day, but I had some with fonts that changed if I didn't do the MKV copy correctly, so I'm thinking they're text.

is project, but didn't commit to this repo, because i need to clean

Any ETA on the new version? I'm quite interested.

Just updated, tell me how it goes.