Initialize apt before installing packages during Vagrant VM setup.

Description
During the Vagrant VM setup, the figlet package apt install was executed before the apt update. Apt couldn't find the package and the VM setup aborted.
apt update is now executed before the figlet apt install.
Test Procedure
Try to set up a new Vagrant VM (vagrant up).
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Other (doesn't fit into the above categories - e.g. documentation updates)

Requires Bitbake Recipe changes?

[ ] The base Bitbake recipe (meta-rdk-ext/recipes-containers/dobby/dobby.bb) must be modified to support the changes in this PR (beyond updating SRC_REV)

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

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


Example for SSR use?

Really great Example,
i also got it to work in my Nuxt.js Enviroment but without the SSR :(
I'm trying since Days to get it work in SSR mode. Could you provide some Information/Tipps or even a Example for that kind of case.
When i load it, i get the Error: 'document' not defined, because its server rendered.
As far as i found out is that it may be achivable with the target set to 'node'. In the packaged index.js i find some document uses from the vue-style-loader and and a line saying:
'vue-style-loader cannot be used in a non-browser environment. ' +     "Use { target: 'node' } in your Webpack config to indicate a server-rendering environment."
But until now i didn't managed to set the target of the build
Any ideas? :)

The module build should automatically work with SSR, because it relies on the user for compilation and they can specify target: 'node' in their configuration.
The CJS and UMD builds are a different story though. Personally, I would just tell SSR users not to use them. However, if you wanted to assume an SSR context, then I believe adding config.target('node') to the chainWebpack function in vue.config.js should work. If you want to separate versions for SSR and the browser, then you'd probably want to use something like config.target(process.env.WEBPACK_TARGET) instead and then update build-lib.js create SSR builds.
Does that make sense?


Remove BaseRequest

Motivation
When pairing with @vinistock, we found that after the listener pattern migration, none of the BaseRequest descendents use the visitor pattern anymore. So now its only usage is to define the @document ivar, which is a wasteful reason to have a class.
Implementation

Remove the BaseRequest class
Remove the obsolete override check task
Update check docs as now some requests don't even have a common request parent class

Automated Tests

Manual Tests

Since each request is invoked individually, it doesn't matter if they have a run, response, or a foo method for them to return the result. Having a parent class to define that interface doesn't provide benefits like duck-typing or type checking but only a consistent-ish naming between those request classes.
And IMO having the same @document also doesn't warrant a parent class because BaseRequest doesn't build any shared logic on top of it.

What is the drawback of keeping BaseRequest?

I think it gives an false-impression that those requests have as strong commonality as those inherit from Listener, which as I explained above, is not true.
Since @vinistock and I are re-thinking the structure of our requests & listeners (e.g. #1247), I think keeping this false-impression will reduce the outcome of it.
What's the benefit of keeping it?

The benefit of the super class defining an abstract run is that you enforce a convention about where the "meat" of a request is implemented. This consistent-ish naming is important as it helps establish commonality between requests.
I think that instead of removing the BaseRequest concept we should instead lay on it. From what I understand the ultimate goal of this series of refactoring is untangling the mess of requests, extensible listeners and listeners.
ExtensibleListener should be removed and add-ons should instead register directly inside the related BaseRequest subclass. The dual concept between Listener vs. ExtensibleListener would then disappear and avoid confusion.
BaseRequest should thus provide all the add-on registration logic in a generic way. As an add-on implementor I only care about registering for a request and the request should then enforce the kind of implementation I should provide.
This means each subclass of BaseRequest should be responsible of defining what "kind" of add-on implementation they accept. For example Hover and friends (maybe all things that could become subclasses of a DocumentRequest actually) would expect a Listener-based add-on. Diagnostics would expect more of an Observer-based add-on etc.
Then, each subclass of BaseRequest would be responsible of triggering the right behavior in its registered add-ons.
Removing the commonality between request will make it easier for requests to stray out of the blessed path and will create a forest of somewhat identical implementations that will make it harder to maintain over the long term. Keeping this superclass, forces us to provide a clean and common implementation. It also enforces a convergent design where contributors external to your team understand how (or are forced to) provide an implementation following your philosophy.
One more change that could be done in parallel is adding a requires_ancestor { Listener } to Support::Common to avoid this module being included where it shouldn't be, making it harder to decouple later. Or maybe the Support::Common methods should be provided to the add-on through the Request or Listener itself rather than an included module.

As an add-on implementor I only care about registering for a request and the request should then enforce the kind of implementation I should provide.

This is indeed what I want to do with changes like this and #1247.
FWIW, we do plan to introduce a parent request class to better capture the commonality between them. And IMO removing this thin layer and not too helpful abstraction will help us come up with a better design later, either in #1247 or in a follow up PR.


Maybe rename Ember Server's maxConcurrency to maxConnections

maxConnections is a much more tangible and well-understood concept for people in the server space (and is consistent with the name of a similar knob in other servers), whereas maxConcurrency kind of brings up the question of "the concurrency of what?"
Obviously this is a breaking change but I figured it was at least worth throwing out

I expect that could be handled with a deprecation.

I expect that could be handled with a deprecation.

I like deleting code, not adding new code! :D

I like deleting code, not adding new code! :D

I like having an incremental upgrade path when working in large codebases that don't give time to keep up but once every few years! :D

I like having an incremental upgrade path when working in large codebases that don't give time to keep up but once every few years! :D

Let's do it.  I don't mind a clean break in 0.22/1.0.  Extra credit for a scalafix.

Closed via #5040


A way to hold onto a promise without blocking cancellation propagation from children

I want to be able to hold onto a promise such that I can create new children, without blocking cancellation propagation from any existing children. With such a mechanism, I should have a callback that's invoked as soon as all children have requested cancel, so I can throw away the parent promise I'm holding.
The idea here is so I can dedupe requests for an upstream asynchronous resource (such as loading images from the network), and allow for cancelling the upstream asynchronous resource as soon as all children have declared they're no longer interested in it.

The actual implementation here is basically just returning a pre-sealed promise, but we need to do this as a child so we have access to the onRequestCancel callback as being able to drop the promise at the point where cancellation is propagated from children upwards is important.

Or we could actually just seal the receiver and attach a new onCancelRequested callback to the resolver. I'm not terribly fond of this because that will pipe cancellation upwards prior to calling the new callback, which means we could end up in a situation where our new onCancelRequested callback is invoked after an onCancel callback (if cancellation is handled upstream as .immediate and onCancel is also .immediate).


Fix ordering problem and reduce synchronization.

Fix:
pendingWrites.add() is not guaranteed to be called before pendingWrites.remove()
Optimization:
Remove synchronization on pendingWrites by using a concurrent data structure instead.
Since there's no concurrent identity based hash map, we can use a regular
ConcurrentHashMap together with a key that implements equals and hashcode based on identity
(a simple Object)
Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for context and/or discussion)

@krka, please sign the CLA/

Oops, I used my personal account - will resubmit later with my employee account and fix the CLA issue

@krka, I'm going to close this PR.  Please reopen the PR from your other account.


Failed to load the "vagrant-managed-servers" plugin on a freshly installed ubuntu server

On a fresh install of 14.04 server version 64bit
uname -a
Linux  3.19.0-25-generic 26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
after
creating a passwordless ssh and sudo for a user named "vcap"
sudo apt-get install git vagrant ruby-full bundler  zlib1g-dev virtualbox
vagrant plugin install vagrant-managed-servers
--> cat Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "tknerr/managed-server-dummy"
config.vm.provider :managed do |managed, override|
managed.server =
override.ssh.username = "vcap"
override.ssh.private_key_path = "/home/vcap/.ssh/id_rsa"
end
end
I get:
--> vagrant up --provider=managed
Failed to load the "vagrant-managed-servers" plugin. View logs for more details.
The provider 'managed' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.

--> vagrant up --provider=managed --debug
ERROR root: Failed to load plugin: vagrant-managed-servers
ERROR root:  -- Error: #<RuntimeError: The Vagrant ManagedServers plugin is only compatible with Vagrant 1.6+>
ERROR root:  -- Backtrace:
ERROR root: /home/vcap/.vagrant.d/gems/gems/vagrant-managed-servers-0.7.1/lib/vagrant-managed-servers/plugin.rb:10:in `<top (required)>'
--> vagrant -v
Vagrant 1.4.3
Bottom line - this is due to vagrant version being too old.


update to follow VADER #178

see https://github.com/JCSDA-internal/vader/pull/178

duplicate of https://github.com/JCSDA-internal/soca/issues/900


(docs) correct code comment for Indirection#prepare

The comment said this method prepares a request, which is not true. In fact,
this method never prepared a request - it was added in 2008 in f9881edd, but
even then it only selected the terminus and checked authorization. This commit
corrects the message and adds param/return doc strings so at least followers can
tell at a glance what's happening here.
Signed-off-by: Moses Mendoza<EMAIL_ADDRESS>

CLA signed by all contributors.


P6 [NEARCON] Give ability for users and moderators to proactively and reactively hide graphic/triggering content and provide tagging features to media

Description
In an effort to protecting sensitive audience and comply with regulation we will set up several features meant to hide or add disclaimer to potentially triggering content on near.org.
Details
In this task, we will set up 2 different features, meant for both Moderators and Users. These will surface at different point in time. Here are the details below:
Feature details:
Overlay image or footage + label (string) describing the image (See screenshot on the right)
Disclaimer in the format of a text underneath any type of posts (text, image, video…) (See screenshot on the left)

Surface and Users
The feature will be available for users when:
When a user is posting a new content they will be able to add a content warning by clicking on the appropriate icon (see blueSky screenshot below for an example). Depending on the option selected and the content type (Text, Image, Video) the feature will display either the graphic overlay option or disclaimer option.
The feature will be available for moderators when:
While reviewing content moderators. They will have a button made available to them within the moderation queue.
The feature will also automatically trigger based on automation (however this will depends on the automations we have implemented here https://pagodaplatform.atlassian.net/browse/ROAD-280 )
When content is posting, the automation will score the content and depending on score it will either amend user overlay/disclaimer decision or add one of these features all while notifying the user.
BlueSky Overlay and Label Features:https://www.loom.com/share/09ef18d01d9046cdb7738594c00e828c?sid=631fea9c-582e-43d6-90a9-6746ea522423
Here is the results of the feature: Please note that BlueSky are not displaying the label created by the user. This might be a mistake in my opinion.

Figma Flow Chart
https://www.figma.com/file/ThgeNehvK42msnFxAMTzq6/Enforcement-Journeys?type=whiteboard&node-id=982-103&t=2yVoD6FcojX9m9IO-4


Web-Server Parameters

Hi,
I've been noticing some differences in the confidence metrics ran locally versus on the web server (No MSA).
I was wondering what parameters (if any) were different in regards to the # of diffusions and # trunk recycles.

AFAIK we use same settings: 5 samples are generated and ranked.
NB: there were recent changes in metrics #60 , not yet deployed to web server


Update free-courses-en.md

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Added a course in C++.
Why is this valuable (or not)?
Teaches English speaker how to code in C++.
How do we know it's really free?
It is a youtube video.
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

For youtube, we prefer "playlist" links and the name of the producer/creator. docs/CONTRIBUTING.md#platforms-and-access-notes

too short


[Powertoys Run] Fixed the "Maximum number of results" setting for the Windows Search Plugin

Summary of the Pull Request
I know this PR is made before any comments on the bug report, but i'd like to create this before that to see if we can improve Powertoys Run.
Fixed the "Maximum number of results" setting for the Windows Search Plugin and moved the logic to filter out hidden files to Windows Search (to prevent it from returning no results when all items had the hidden flag.
References
PR Checklist

[x] Applies to #5068
[x] CLA signed. If not, go over here and sign the CLA
[x] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
I have removed the tests which did the filtering of the hidden flag in code (since this is in the search api). Any suggestions on how to move / readd this test?
Validation Steps Performed

I've created the following folder in my users download folder (with alot of images hidden/ not hidden)  with a similar name.

I search for the text "powerlauncher".
i expect the following to be true.

i get no more then 5 search results (the setting i have it on)
i get only files with the "shown" in the filename.

Please also note the scrollbar to see howmany results there are left.
Before:

After:

Before i forget, i also changed the setting displayHiddenFiles in the contructor to True and saw hidden files in the lists showing up.

I've removed the logic to update the settings, and thus this PR only improves the Windows Search handling the "Hidden" check instead of in code.

I've removed the logic to update the settings, and thus this PR only improves the Windows Search handling the "Hidden" check instead of in code.

Can you please help me understand why this change is needed?
We were previously handling hidden files in the same way by filtering out hidden files.

I've removed the logic to update the settings, and thus this PR only improves the Windows Search handling the "Hidden" check instead of in code.

Thanks for this @royvou.  Would you mind updating the PR title as well for clarity?

Is anything required for this to be merged in?


A Scan has a failure.. Please approve to proceed

Approval required for following Workflow to proceed.

WorkflowName
Workflow#
BranchName
TriggerEvent
LastCommitUser

build-test
71
refs/heads/main
push
Yog4Prog

Issue Details
Found an Issue while performing SCA Scan
:point_right: You are required to Approve (or) Reject the issue
Approve or Reject by commenting in the below section with any of the following keywords
:green_book:  Approved Keys: approved approve lgtm goahead proceed yes
:closed_book: Reject Keys: denied deny reject rejected no abort cancel exit
:point_right: Note: If left uncommented the issue will be closed after the timeout period and the workflow will be marked unsuccessful.

Approval waiting period elapsed. Approval request is automatically closed and workflow status is marked to Failed.


No minified notify.min.js in /dist

Why did you remove it?

so we could remove all the build stuff, I've added the browser uglify.js into notifyjs.com though so you can  get a minified copy from there


istio.io/istio/tests/e2e/tests/mixer TestMixerReportingToMixer flaky

https://k8s-gubernator.appspot.com/build/istio-prow/e2e-suite-rbac-no_auth/1326
istio-telemetry-744b6b7d6b-5bz2j
{"level":"info","time":"2018-04-10T22:18:38.280381Z","instance":"accesslog.logentry.mixer-test-0ffce2e48d8749b7b4b3118dce","connectionMtls":false,"destinationIp":"<IP_ADDRESS>","latency":"30.790657ms","method":"POST","protocol":"http","requestSize":15963,"responseCode":200,"responseSize":5,"sourceIp":"<IP_ADDRESS>","sourceUser":"","url":"/istio.mixer.v1.Mixer/Report"}
{"level":"info","time":"2018-04-10T22:18:39.290313Z","instance":"accesslog.logentry.mixer-test-0ffce2e48d8749b7b4b3118dce","connectionMtls":false,"destinationIp":"<IP_ADDRESS>","latency":"13.633656ms","method":"POST","protocol":"http","requestSize":17470,"responseCode":200,"responseSize":5,"sourceIp":"<IP_ADDRESS>","sourceUser":"","url":"/istio.mixer.v1.Mixer/Report"}
{"level":"info","time":"2018-04-10T22:18:38.466649Z","instance":"accesslog.logentry.mixer-test-0ffce2e48d8749b7b4b3118dce","connectionMtls":false,"destinationIp":"<IP_ADDRESS>","latency":"17.935188ms","method":"POST","protocol":"http","requestSize":15444,"responseCode":200,"responseSize":5,"sourceIp":"<IP_ADDRESS>","sourceUser":"","url":"/istio.mixer.v1.Mixer/Report"}
mixer_test.go:762: Validating metrics with 'istio-policy' have been generated...
mixer_test.go:764: Prometheus query: sum(istio_request_count{destination_service="istio-policy.mixer-test-0ffce2e48d8749b7b4b3118dce.svc.cluster.local"}) by (source_service)
mixer_test.go:779: Validating metrics with 'istio-telemetry' have been generated...
mixer_test.go:781: Prometheus query: sum(istio_request_count{destination_service="istio-telemetry.mixer-test-0ffce2e48d8749b7b4b3118dce.svc.cluster.local"}) by (source_service)
mixer_test.go:801: Validating Mixer access logs show Check() and Report() calls...
mixer_test.go:809: Expected at least 4 lines of Mixer-specific access logs, got 3

https://k8s-gubernator.appspot.com/build/istio-prow/e2e-suite-rbac-auth/1389
istio-telemetry-5c8b849dd6-5x2x9
{"level":"info","time":"2018-04-10T22:17:17.551257Z","instance":"accesslog.logentry.mixer-test-0dd70a4d88fa46a493cb8c1516","connectionMtls":true,"destinationIp":"<IP_ADDRESS>","latency":"5.348704ms","method":"POST","protocol":"https","requestSize":7649,"responseCode":200,"responseSize":5,"sourceIp":"<IP_ADDRESS>","sourceUser":"cluster.local/ns/mixer-test-0dd70a4d88fa46a493cb8c1516/sa/istio-pilot-service-account","url":"/istio.mixer.v1.Mixer/Report"}
{"level":"info","time":"2018-04-10T22:17:18.228212Z","instance":"accesslog.logentry.mixer-test-0dd70a4d88fa46a493cb8c1516","connectionMtls":true,"destinationIp":"<IP_ADDRESS>","latency":"14.259576ms","method":"POST","protocol":"https","requestSize":22326,"responseCode":200,"responseSize":5,"sourceIp":"<IP_ADDRESS>","sourceUser":"cluster.local/ns/mixer-test-0dd70a4d88fa46a493cb8c1516/sa/istio-pilot-service-account","url":"/istio.mixer.v1.Mixer/Report"}
mixer_test.go:762: Validating metrics with 'istio-policy' have been generated...
mixer_test.go:764: Prometheus query: sum(istio_request_count{destination_service="istio-policy.mixer-test-0dd70a4d88fa46a493cb8c1516.svc.cluster.local"}) by (source_service)
mixer_test.go:779: Validating metrics with 'istio-telemetry' have been generated...
mixer_test.go:781: Prometheus query: sum(istio_request_count{destination_service="istio-telemetry.mixer-test-0dd70a4d88fa46a493cb8c1516.svc.cluster.local"}) by (source_service)
mixer_test.go:801: Validating Mixer access logs show Check() and Report() calls...
mixer_test.go:809: Expected at least 4 lines of Mixer-specific access logs, got 2

Maybe it needs to wait a bit longer to get access logs?
Or is there a signal that mixer crashed and lost some logs?

The test current sleeps 30 seconds.
I0410 22:18:10.103] 2018-04-10T22:18:10.102641Z	info	Sleeping to allow prometheus to record metrics...
I0410 22:18:40.113] 2018-04-10T22:18:40.112553Z	info	Running command kubectl -n mixer-test-0ffce2e48d8749b7b4b3118dce get pod -l istio-mixer-type=telemetry -o jsonpath='{.items[0].metadata.name}'

No immediate signs of a crash
I0410 22:18:40.497] 2018-04-10T22:18:40.494697Z	info	Running command kubectl get ingress --all-namespaces
I0410 22:18:40.637] 2018-04-10T22:18:40.636685Z	info	Command output:
I0410 22:18:40.637] NAMESPACE                               NAME      HOSTS     ADDRESS         PORTS     AGE
I0410 22:18:40.637] mixer-test-0ffce2e48d8749b7b4b3118dce   gateway   *         <IP_ADDRESS>   80        11m
I0410 22:18:40.637] 2018-04-10T22:18:40.636760Z	info	Running command kubectl get pods -n mixer-test-0ffce2e48d8749b7b4b3118dce
I0410 22:18:40.840] 2018-04-10T22:18:40.839800Z	info	Command output:
I0410 22:18:40.840] NAME                                        READY     STATUS    RESTARTS   AGE
I0410 22:18:40.840] details-v1-5c6dd859db-srjdv                 2/2       Running   0          11m
I0410 22:18:40.840] istio-ca-5c6db9dd7f-dcn6l                   1/1       Running   0          12m
I0410 22:18:40.841] istio-ingress-586d7cbb57-d6tzk              1/1       Running   0          12m
I0410 22:18:40.841] istio-pilot-d89cc574b-hlp2z                 2/2       Running   0          12m
I0410 22:18:40.841] istio-policy-cd7698dc9-w46bc                2/2       Running   0          12m
I0410 22:18:40.841] istio-statsd-prom-bridge-6dbb7dcc7f-kbflg   1/1       Running   0          12m
I0410 22:18:40.841] istio-telemetry-744b6b7d6b-5bz2j            2/2       Running   0          12m
I0410 22:18:40.841] mongodb-v1-75b6d5b7cb-h86b5                 2/2       Running   0          11m
I0410 22:18:40.842] productpage-v1-5f978487fd-5hslp             2/2       Running   0          11m
I0410 22:18:40.842] prometheus-586d95b8d9-c8rc4                 1/1       Running   0          12m
I0410 22:18:40.842] ratings-v1-6ff66976fd-q7hll                 2/2       Running   0          11m
I0410 22:18:40.842] ratings-v2-868fbb757c-9rhv4                 2/2       Running   0          11m
I0410 22:18:40.842] reviews-v1-548b87d4d6-gb4s9                 2/2       Running   0          11m
I0410 22:18:40.842] reviews-v2-58f698fcd6-zj4xm                 2/2       Running   0          11m
I0410 22:18:40.842] reviews-v3-f8f7f86f8-jv27j                  2/2       Running   0          11m
I0410 22:18:40.843] sleep-798495fbdb-nwr99                      2/2       Running   0          11m
I0410 22:18:40.843] zipkin-7988c559b7-qzrfz                     1/1       Running   0          11m

https://storage.googleapis.com/istio-prow/e2e-suite-rbac-no_auth/1326/artifacts/mixer-test-0ffce2e48d8749b7b4b3118dce/istio-telemetry-744b6b7d6b-5bz2j_container:mixer.log has 65 occurrences of the target log entry (see below). But the test only searches the 100 most recent entries (tail -100) at that moment in the test run.
$ grep 'istio.mixer.v1.Mixer/Report' istio-telemetry-744b6b7d6b-5bz2j_container\:mixer.log |grep <IP_ADDRESS> | wc -l
65


TA.2.4 Add a button the to overview page which is linked to the new page

@najma98 add commit code


add atto

passed locally, but let's do a Jenkins run to be sure: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1133/consoleFull (404 til Jenkins finishes waxing his protractor)
fyi @tpolecat

before this is merged, we should:

wait for https://github.com/tpolecat/atto/pull/48 to be merged
change project-refs.conf not to point to my fork anymore

new test run: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1134/consoleFull


Fix timestamp bulk reset of all inbox emails

Fixes #61
Changes the query from or_ to in_ to select only the new emails for updating the field sent_at.

Codecov Report

Merging #72 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master     #72   +/-   ##
======================================
  Coverage    72.3%   72.3%
======================================
  Files          19      19
  Lines        1217    1217
======================================
  Hits          880     880
  Misses        337     337

Impacted Files
Coverage Δ

opwen_email_client/domain/email/sql_store.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Output File CLI Option

Issue #, if available: None
Description of changes: Add --output-file argument, that writes the main output to the file rather than stdout, whilst allowing exceptions and other text to still be written to stdout/stderr. This is useful when producing test reports for consumption by CI/CD systems.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Tro95 is everything currently being written to stdout? Think it'd make sense to utilize stderr if so

@PatMyron I can only see two places where something is directly outputted to stdout, which is https://github.com/aws-cloudformation/cfn-python-lint/blob/c32ce78e0b5e87b67f3ea4ddb43d8d1954dfc4ef/src/cfnlint/core.py#L142 and https://github.com/aws-cloudformation/cfn-python-lint/blob/c32ce78e0b5e87b67f3ea4ddb43d8d1954dfc4ef/src/cfnlint/main.py#L33
Everything else is handled by the logger, which uses stderr by default for all levels. You should be able to test this PR by trying cfn-lint -t template.yml -D --output-file output.txt, and seeing the debug information displayed in the console via stderr whilst the results of the linting are written to output.txt

The value of this is to help with CI/CD tooling. A lot of these tools will support "uploading" junit reports to more easily show the test results.  I'm in agreement that this should be an option.  @PatMyron any other concerns before I merge this one?


Support for declaring minSdk of the latest/minimum version

Right now if you upload a new update to play store which raises the minSdk, users below the minSdk will get a notification that there is a new update - however there is no update available for them.
cc @kjurkovic @ikocijan

@skliba please take care of this. The new json should look like this:
{
    "android": {
        "minimum_version": "1.2.3",
        "minimum_version_min_sdk": 15,
        "latest_version": {
            "version": "2.4.5",
            "notification_type": "ONCE",
            "min_sdk": 16
        }
    }
}

The new properties are optional.
Make sure you write tests for it.

👍


Fix for 3891 - added project relationship to kubernets provider UI

Fixes #3891

@simon3z @abonas
Its a little awkward since kubernetes has namespaces and not projects so I'm a little unsure about this change.

I think it's following this https://github.com/ManageIQ/manageiq/pull/3048
@simon3z ?

@miq-bot add_label providers/containers
@miq-bot add_label ui

:+1: in general (not review in the specifics but it seems trivial enough)

code wise and functionality wise it LGTM (I also verified it locally) and ready to merge.
However (and that is not in the scope of this patch), @simon3z it does look weird to have projects in k8s. if a user works with only plain k8s, how can that user know what is a project?
perhaps we need a different title or tooltip or some comment in brackets to clarify.

it does look weird to have projects in k8s.

@abonas thats what I meant by:

Its a little awkward since kubernetes has namespaces and not projects so...

Is there an easy way to make context based translations in this instance?
We don't separate openshift and k8s at all.

it does look weird to have projects in k8s.
@abonas thats what I meant by:
Its a little awkward since kubernetes has namespaces and not projects so...
Is there an easy way to make context based translations in this instance?
We don't separate openshift and k8s at all.

I know that this is what you meant :)
the problem here is not technical but functional.

@serenamarie125 can you share your thoughts? a while ago, project and namespace were merged from a technical point of view as well as functional (like container groups and pods). but see the comments above - are we ok going forward with k8s provider having projects?

@abonas @zeari going back to the "best of breed management" which John Hardy talks about, our end goal should be when looking at K8S, use their terminology.  In a perfect world, things should be context based.
Of course since we have a global dashboard which shows mixed providers, we definitely have issues  with condensing terminology there.
This is something we should follow up on with @jonnyfiveiq, but i think he's out for another week.  This is also something that I am hoping to be able to talk to customers about in the future.
If we currently don't distinguish between K8S/OpenShift at all, I'm not sure there is a choice for Beta1.  Do we have plans to distinguish between provider types in the future?  I was under the impression that going forward our K8S and OpenShift dashboards would differ ...

If we currently don't distinguish between K8S/OpenShift at all, I'm not sure there is a choice for Beta1. Do we have plans to distinguish between provider types in the future? I was under the impression that going forward our K8S and OpenShift dashboards would differ ...

@serenamarie125 thanks for your detailed answer!
we do distinguish providers - user can create a k8s provider or an ose provider. they have different a different icon, and openshift has more entities than k8s.
my concern is that potentially a user could work only against k8s without knowing what openshift is, and will have to guess what is a project
so, yes lets take it with  @jonnyfiveiq
But this should NOT block this patch.

LGTM
@blomquisg imo ready for merge


multiple double quotes in a field corrupts CSV file

Please provide a general summary of the issue in the Issue Title above
fill out the headings below as applicable to the issue you are reporting,
deleting as appropriate but offering us as much detail as you can to help us resolve the issue

If a user places a single double quote in a cell then it is correctly escaped e.g.
word " word
==>
"word "" word"
But if multiple double quotes exist then only the first one is escaped
word " word " word " word
==>
"word "" word " word " word"
We would expect each of the double quotes to be escaped as follows
"word "" word "" word "" word"
I have only tested this on the Linux version so the behavior may be different in the other versions.
I know this project is dead (no code commits in a year) but I think this tool still has a large user base. If this problem isn't fixed then a warning should be put on the home page indicating that the tool can silently corrupt CSV files.
FYI. I found this tool by reviewing many different CSV editors for my organization. This tool beat other in terms of transparency (available code), simplicity and support for multiple platforms (including Linux). I was heartbroken when I found this bug because there's no good second choice. I'm not sure we'll be able to use Data Curator as it has no Linux version.

Hello @sizezero.
As you've correctly pointed out, development for this tool is no longer happening.
However, there is a tool called 'Data Curator', that was inspired by 'Comma Chameleon', that is receiving ongoing development. Can I suggest that you look at it as an option for suit your needs?
It can be found here - https://github.com/ODIQueensland/data-curator

Thanks. I had previously looked at Data Curator. There's no downloadable linux version and I haven't had a chance to build a linux version so I haven't run the program yet.
I didn't expect this bug to be fixed in Comma Chameleon but the effect is bad enough that I think you should consider warning your remaining users, perhaps via a note on the home page. Silent file corruption is awful.


Fix an issue with .po files that ignored all strings, once a comment is ...

...contained
in the gettext file

Actually, this behavior is intentional -- extract_po_blocks extracts
messages preceded by a comment identifier, and extract_po_strings
extracts messages NOT preceded by a comment. If you need both just
concatenate the results of both functions. This should probably be
cleaned up/clarified.
On Sat, Feb 11, 2012 at 3:26 PM, Sebastian Hoitz
<EMAIL_ADDRESS>wrote:

...contained
in the gettext file
You can merge this Pull Request by running:
git pull https://github.com/komola/ChicagoBoss extract_po_strings_bug
Or you can view, comment on it, or merge it online at:
https://github.com/evanmiller/ChicagoBoss/pull/73
-- Commit Summary --

Fix an issue with .po files that ignored all strings, once a comment is contained

-- File Changes --
M src/boss/boss_lang.erl (2)
-- Patch Links --
https://github.com/evanmiller/ChicagoBoss/pull/73.patch
 https://github.com/evanmiller/ChicagoBoss/pull/73.diff

Reply to this email directly or view it on GitHub:
https://github.com/evanmiller/ChicagoBoss/pull/73

--
Evan Miller
http://www.evanmiller.org/

Looking into it, I don't think the po_block stuff is used anymore. So, I've ripped it out. Try this:
https://github.com/evanmiller/ChicagoBoss/commit/cb531b1916153f65fb510d53f58081532f018c88

Ok, I've done a pretty big refactor to eliminate the strings/blocks distinction; you should now be able to use Poedit-created files without a problem. Open a new issue if you still have trouble.


Boxy for Atom editor

I really loved Boxy when I used Sublime Text, but I am using Atom for several months now. Any chance to get an Atom version?

Currently I have no time. Maybe later or someone else will port it.

I have no plans to port it to an another editor.


Call for discussion: Security sandbox for extensions

I think it's time to think about security and sandboxes around vscode extensions. Currently, it is possible to develop extensions that:

Can invoke any OS command automatically upon installation/activation thanks to the availability of child_process or any number of npm packages such as shelljs
Add persistence so that they can run independent of VS code
Target both local and remote thanks to the likes of vscode-remote

At ShiftLeft, we have been looking into static analysis-based security audit for VS code extensions (both source and vsix). However, any heavily obfuscated code can defeat such static detection. Plus, the payloads could come from any source - even GitHub and Azure Repos!
Any guidance or thoughts from the vscode team on this topic?

/duplicate of #52116


Add user and comment when ACKing alerts

it would be nice when you ACK an alert if the user who did so is appended to this with a way to enter a message about it. see #32

$scope.ackAlert = function(id, name) {
      Alert.status({id: id}, {status: 'ack', text: 'status change via ' +$auth.getPayload().name}, function(data) {
        $route.reload();
      });
    };

This appears to work for appending the name on alert actions. Still left is a message submission.

The fix adds the user name to the text when a message is acked, closed or opened (if authentication is enabled). The second part of allowing users to enter a message is left as an exercise for the reader. See a basic javascript example here.


May need to support TCP without mutual auth

@tcschmid will confirm if this is a requirement

This was complete here: https://github.com/IBM/node-log4js-qradar-syslog-appender/pull/14


Fix key case error in Get-SecretInfo

Get-SecretInfo can error with Get-SecretInfo: Cannot convert the JSON string because it contains keys with different casing. Please use the -AsHashTable switch instead. The key that was attempted to be added to the existing key 'B5UserUUID' was 'b5UserUUID'.
ConvertFrom-Json -AsHashtable isn't available in 5.1, so fix the case.

combined into https://github.com/cdhunt/SecretManagement.1Password/pull/24


Fixes #307: Filter out semicolon separated values to prevent them from showing up as separate options.

This PR fixes #307, where the multivalue control displayed saved semicolon-separated values alongside the predefined list of values. This was due to a change in the getAllowedFieldValues API, which now returns both predefined and user-saved values.
Testing:

Verified that the dropdown no longer shows duplicate values.
Confirmed that predefined values without semicolons are still correctly displayed.
Tested with both 'Allow users to enter custom values' selected and unselected.

@AminTi

Any idea when this will be merged into master such that we can have the fix in Azure Devops Service?


Documentation updates for release schedule, gist contributions, and change management

Note: there is no accompanying release note because the documentation is not included in the release package.

@marksem @Jamie-SA Note that I've put this PR into draft state pending a possible change in the deprecation policy proposed by @marksem.


sample data error

Click on File > Open sample > napari-Sairyscan resulted in the following error:
FileExistsError: [Errno Cannot find the file:] /opt/anaconda3/envs/napari-latest/lib/python3.9/site-packages/sairyscan/data/celegans_airyscan.czi

data were missing in the sairyscan pip package. It is now fixed in the version 0.0.2


Instead of suggesting changes directly from here at GH UI, I have opened a new branch from yours and suggested changes there: https://github.com/sysdiglabs/aws-modernization-with-sysdig/pull/18
Can you please review and check if those make sense to you? Gracias tio!


Question: how to avoid dragging to the left?

I've certain items with a property named 'starred' at the right panel that can't be moved to the left panel. The others can be.
How can I apply this rectriction easily?

dragularService($('#leftContainerPanel'), {
    accepts: function(el){
        return el.not('.starred');
   }
})


Various updates to blocked numbers cmdlet

Various updates to blocked numbers cmdlet.

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

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

@get-itips @dariomws @tseward

Copy review - @JensTrier, kindly commit the minor suggested change. Many thanks.

@JohanFreelancer9 thanks & done!

Docs Build status updates of commit 09c8b28:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

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

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

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

@JensTrier

Docs Build status updates of commit 17fdda9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

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

@tseward thanks! I updated the examples.

Docs Build status updates of commit 02dcf8c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundBlockedNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsInboundExemptNumberPattern.md
:white_check_mark:Succeeded
View (skype-ps)

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

@tiburd Please merge this PR. Thanks


question: dynamically set the height of a panel

Is there a way to dynamically set the height of a panel?
I need to have a click event cause the southern panel to grow to a predetermined height.
Thanks, and great work on this component.

I think think #96 answers this question.


Send promotion is too eager.

As the title says.

Modified both Send and Copy to promote only if we have at least 50 samples for all characters and all characters are over the 90% threshold of proficiency.


fix Fix decimal precision and scale wrong when create table like

Proposed changes
Use field datatype such as decimal(10, 0) to create table like. Because the scale is 0, the precision and scale will lost when create table like done. this will fix the bug.
Before fix, create table with following SQL:
CREATE TABLE IF NOT EXISTS db_test.table_test
(
name varchar COMMENT "1m size",
id SMALLINT COMMENT "[-32768, 32767]",
timestamp0 decimal null comment "c0",
timestamp1 decimal(38, 0) null comment "c1"
)
DISTRIBUTED BY HASH(id) BUCKETS 1
PROPERTIES ('replication_num' = '1');
and Then run
CREATE TABLE db_test.table_test_like LIKE db_test.table_test
SHOW CREATE TABLE db_test.table_test_like;
the field timestamp1 will be decimal(9, 0), it's wrong. this will fix it.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run clickbench


CMake error on depthai-core install

Hi,
i'm getting this kind of error:
[14442C1051280AD100] [56.542] [system] [info] PRINT:LeonMss: Called by: LRT, controller: LOS
[14442C1051280AD100] [56.629] [system] [error] Attempted to start Mono Left camera - NOT detected!
[14442C1051280AD100] [56.629] [system] [error] Attempted to start Mono Right camera - NOT detected!
Do you have any ideas on how to solve this?
Kindly,
Jonathan

I went through this tutorial: https://github.com/luxonis/depthai-ros/blob/noetic-devel/README.md. The only difference was that I had to clone ros2-lux-d-lite_bringup branch of the depthai-core, since the other ros2 branch was not working. Might that be the reason?

Yes. that branch is for lite. it won't work for OAK-D. you need to install ros2 branch only. what was the issue with ros2 branch ?

Fixed in


Magic Checks for Spells on NPC sheets display the wrong Attribution combination, but use the correct one.

Bug Description:
When you create a spell for an NPC, it will display the Magic Check for it as using INS + MIG, no matter what Attributes the Magic Check actually uses. This is a bigger annoyance than I first thought, since it will show the incorrect information to players when using the automated Study function.
Steps to Reproduce:

Create a new spell on an NPC sheet.
Favorite it and expand the tooltip, or Survey it.
You'll see it shows INS + MIG, even if you changed it from its default.

Expected behavior:
The NPC sheets should display the Attribute combination they actually use for Magic Checks.
Attachments (if applicable):
Here's an example: this Cactitan uses INS + WLP for its Noxious Thorns spell, but the Study result says otherwise, accidentally tricking my players into making a tactical blunder that nearly got one of them killed. Oops!

Doesn't seem to be specific to NPC sheets. It's occurring on my PCs' sheets as well.

Also for the PC it's always MIG + MIG no matter what.

Turns out that the internal data structures for spells are unlike those of weapons or basic attacks.
This should be fixed in the next release.


Deploying a pipeline configuration causes confusing and nonsensical errors

I have been trying to deploy Logstash in a Docker container via Compose. The below is the relevant portion of my Compose file, note that I am bind mounting a host directory to completely replace the /usr/share/logstash/pipeline directory with my own configuration as specified in the documentation.
version: '3.3'
services:
  logstash:
    build:
      context: ./opt/docker/logstash
    volumes:
      - ./modules/logstash:/usr/share/logstash/pipeline:ro
    depends_on:
      - elasticsearch
      - rabbitmq
      - mongodb

The host directory contains three files, a pipelines.yml config:
- pipeline.id: first
  path.config: "/usr/share/logstash/pipeline/first.conf"
- pipeline.id: second
  path.config: "/usr/share/logstash/pipeline/second.conf"

And two configuration files, first.conf:
input {
  beats {
    port => 5044
  }
}

output {
  elasticsearch {
    hosts => "elasticsearch"
    index => "my-index"
  }
}

second.conf:
input {
  rabbitmq {
    host => "rabbitmq"
    queue => "logstash-queue"
  }
}

filter {
  json {
    source => "message"
  }
}

output {
  mongodb {
    uri => "mongodb://mongodb"
    collection => "logs"
    database => "logs"
  }
}

When performing docker-compose up, Logstash fails to start:
logstash_1             | Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties
logstash_1             | [2019-03-06T13:13:43,127][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.queue", :path=>"/usr/share/logstash/data/queue"}
logstash_1             | [2019-03-06T13:13:43,143][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.dead_letter_queue", :path=>"/usr/share/logstash/data/dead_letter_queue"}
logstash_1             | [2019-03-06T13:13:43,965][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"6.6.1"}
logstash_1             | [2019-03-06T13:13:44,017][INFO ][logstash.agent           ] No persistent UUID file found. Generating new UUID {:uuid=>"05111c59-04fb-49ad-8238-7a644db27eb4", :path=>"/usr/share/logstash/data/uuid"}
logstash_1             | [2019-03-06T13:13:44,976][WARN ][logstash.monitoringextension.pipelineregisterhook] xpack.monitoring.enabled has not been defined, but found elasticsearch configuration. Please explicitly set `xpack.monitoring.enabled: true` in logstash.yml
logstash_1             | [2019-03-06T13:13:46,446][INFO ][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://elasticsearch:9200/]}}
logstash_1             | [2019-03-06T13:13:46,966][WARN ][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=>"http://elasticsearch:9200/"}
logstash_1             | [2019-03-06T13:13:47,095][INFO ][logstash.licensechecker.licensereader] ES Output version determined {:es_version=>6}
logstash_1             | [2019-03-06T13:13:47,102][WARN ][logstash.licensechecker.licensereader] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type{:es_version=>6}
logstash_1             | [2019-03-06T13:13:47,315][INFO ][logstash.monitoring.internalpipelinesource] Monitoring License OK
logstash_1             | [2019-03-06T13:13:47,318][INFO ][logstash.monitoring.internalpipelinesource] Validated license for monitoring. Enabling monitoring pipeline.
logstash_1             | [2019-03-06T13:13:48,169][ERROR][logstash.agent           ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of #, input, filter, output at line 15, column 1 (byte 176) after ", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:41:in `compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:49:in `compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in `block in compile_sources'", "org/jruby/RubyArray.java:2486:in `map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:10:in `compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:149:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:22:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:90:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:43:in `block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:94:in `block in exclusive'", "org/jruby/ext/thread/Mutex.java:148:in `synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:94:in `exclusive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:39:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:327:in `block in converge_state'"]}
logstash_1             | [2019-03-06T13:13:48,463][ERROR][logstash.agent           ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of #, input, filter, output at line 15, column 1 (byte 176) after ", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:41:in `compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:49:in `compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in `block in compile_sources'", "org/jruby/RubyArray.java:2486:in `map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:10:in `compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:149:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:22:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:90:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:43:in `block in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:94:in `block in exclusive'", "org/jruby/ext/thread/Mutex.java:148:in `synchronize'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:94:in `exclusive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:39:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:327:in `block in converge_state'"]}
logstash_1             | [2019-03-06T13:13:53,277][WARN ][logstash.outputs.elasticsearch] You are using a deprecated config setting "document_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=>"document_type", :plugin=><LogStash::Outputs::ElasticSearch bulk_path=>"/_xpack/monitoring/_bulk?system_id=logstash&system_api_version=2&interval=1s", hosts=>[http://elasticsearch:9200], sniffing=>false, manage_template=>false, id=>"51f66c9ec66feb8fd59be1157c335c1ddc5fb856d2b248254ae6add289cea7b7", document_type=>"%{[@metadata][document_type]}", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_f98631f6-a740-4706-b2e3-7fa50d8a40f4", enable_metric=>true, charset=>"UTF-8">, workers=>1, template_name=>"logstash", template_overwrite=>false, doc_as_upsert=>false, script_type=>"inline", script_lang=>"painless", script_var_name=>"event", scripted_upsert=>false, retry_initial_interval=>2, retry_max_interval=>64, retry_on_conflict=>1, ilm_enabled=>false, ilm_rollover_alias=>"logstash", ilm_pattern=>"{now/d}-000001", ilm_policy=>"logstash-policy", action=>"index", ssl_certificate_verification=>true, sniffing_delay=>5, timeout=>60, pool_max=>1000, pool_max_per_route=>100, resurrect_delay=>5, validate_after_inactivity=>10000, http_compression=>false>}
logstash_1             | [2019-03-06T13:13:53,345][INFO ][logstash.pipeline        ] Starting pipeline {:pipeline_id=>".monitoring-logstash", "pipeline.workers"=>1, "pipeline.batch.size"=>2, "pipeline.batch.delay"=>50}
logstash_1             | [2019-03-06T13:13:53,442][INFO ][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://elasticsearch:9200/]}}
logstash_1             | [2019-03-06T13:13:53,482][WARN ][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://elasticsearch:9200/"}
logstash_1             | [2019-03-06T13:13:53,492][INFO ][logstash.outputs.elasticsearch] ES Output version determined {:es_version=>6}
logstash_1             | [2019-03-06T13:13:53,493][WARN ][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document _type {:es_version=>6}
logstash_1             | [2019-03-06T13:13:53,521][INFO ][logstash.outputs.elasticsearch] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>["http://elasticsearch:9200"]}
logstash_1             | [2019-03-06T13:13:53,615][INFO ][logstash.pipeline        ] Pipeline started successfully {:pipeline_id=>".monitoring-logstash", :thread=>"#<Thread:0x77775 run>"}
logstash_1             | [2019-03-06T13:13:54,067][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}

The container exits after the last line. The same configuration (with directories modified in the pipelines.yml file to correctly point to the configuration files) works fine on the host (macOS 10.14.3) with Logstash 6.6.1. If I bind-mount the configuration elsewhere (so Logstash starts in the container with the default configuration and does not immediately exit), I can run Logstash within the container with the -f parameter pointing to each configuration file, ruling out an actual configuration issue. I did note that the error references the default 'main' pipeline which should not be configured in my setup (or, at least the documentation suggests this):
:action=>LogStash::PipelineAction::Create/pipeline_id:main

The content of the error message is not useful at all:
Expected one of #, input, filter, output at line 15, column 1 (byte 176) after

Only one of the files (second.conf) has enough lines for a line 15 to be relevant, and that line 15 is output {, one of the directives the error specifies is expected but missing.
Is there configuration that's missing or invalid here causing this issue that isn't documented or not in line with what the documentation suggests? Additionally, I think this error message needs to be improved significantly as it is impossible to understand what exactly is the issue. I've given up on pipelining for now and have returned to a single configuration using tags and if-conditions to separate logic, which does work.

Is that the same issue as #64? Could you try https://github.com/elastic/logstash-docker/issues/64#issuecomment-346515009 to see if that fixes it?

I don't think it's the same issue. I set path.config to null in my Compose file to no effect, I'm seeing the same errors.

You could try starting Logstash with the -t command-line flag. This usually gives more useful error messages for configuration errors.


DG Fluids + Parallel-kinetic-perpendicular-moment model

This branch has seen enormous development progress on a variety of fronts and can now be merged (modulo corresponding changes in G2 to facilitate continued functionality of G0 main with G2 g0_merge branch)

We have our first implementation of DG fluids using Lax fluxes at quadrature points before projection back onto our modal basis.
In many places (such as moments, prim_lbo, prim_lbo_calc, and mom_calc) there has been a larger push to standardization of taking a use_gpu boolean in the new method, and then selecting the appropriate host or device method
As a result of all of the increased functionality, various methods that are wrapped by G2 have had to be extended such as dg_updater_vlasov. These changes mostly manifest as an increased number of auxiliary fields but another change is that we have split field_id into both a field_id and a model_id to facilitate easier specification of things like special relativistic or PKPM Vlasov (which still use Maxwell's equations unmodified) from genuine changes to the field equations (such as Vlasov-Poisson)
Many objects in this branch remove indirections that have previously proved meddlesome on GPUs. While the approach has not been totally standardized where possible (especially in volume kernels) I have removed one layer of indirection. The G2 side of things does not care about this but if you're working in a branch of G0 be careful that merging main into your branch does not change this. It's a tedious process and if the kernel selection gets messed up it will be painful to fix.
Other small feature extensions in the G0 app as part of testing, such as applied currents and external electromagnetic fields.

This is a big enough merge that anyone that wants to look this over can do so. We need to merge this branch before the holidays because the gk-nov-7-22 branch has had to make changes to the Vlasov equation object that need to be combined with this branch and it's better to start the review process now.

Smaller merges/PRs are preferable, but OK.
I have a basic question before starting to review, does this pass the g2 regression tests? I think the majority of the GK and Vlasov reg tests run.

I am working on the corresponding G2 pull request so that the Vlasov regression tests run again. There have been a number of changes to the function signatures of things like dg_updater_vlasov, and there are few places throughout G2 that now need to take a boolean for use_gpu in their new method to simplify the initialization

Sounds good. I'll look out for that.
One possible way to set this boolean is as done
in gkyl/Updater/GkSheathBc.lua.
On Mon, 12 Dec 2022 at 22:11, James Juno @.***> wrote:

I am working on the corresponding G2 pull request so that the Vlasov
regression tests run again. There have been a number of changes to the
function signatures of things like dg_updater_vlasov, and there are few
places throughout G2 that now need to take a boolean for use_gpu in their
new method to simplify the initialization
—
Reply to this email directly, view it on GitHub
https://github.com/ammarhakim/gkylzero/pull/127#issuecomment-1347335165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQ6DKESXQ4DDE6JI7EAO3LWM6IJPANCNFSM6AAAAAAS4ER55U
.
You are receiving this because your review was requested.Message ID:
@.***>

@manauref, do you mean this?
local useGPU = xsys.pickBool(tbl.useDevice, GKYL_USE_GPU or 0)

Yeah

On Dec 12, 2022, at 11:30 PM, Petr Cagas @.***> wrote:

@manauref, do you mean this?
local useGPU = xsys.pickBool(tbl.useDevice, GKYL_USE_GPU or 0)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Closing this pull request for now because of some recent breakthroughs in PKPM that require a slight refactoring. Commit coming imminently but now we solve for both the 0th and 1st Laguerre moments so that no equation is required for p_perp, and the dynamics of p_perp are kinetic (retain q_perp and the associated higher v_perp^2 v_parallel^k for all k). Preliminary simulations very promising though implementation is more complicated and there have been significant headaches in tracking down sign errors.


Aborted (core dumped) in tf.raw_ops.CropAndResizeGradBoxes

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.17
Custom code
Yes
OS platform and distribution
Linux Ubuntu 22.04.3 LTS (x86_64)
Mobile device
No response
Python version
3.9.13
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
With specific input, tf.raw_ops.CropAndResizeGradBoxes triggers a crash.
It can be reproduced on tf-nightly.
Standalone code to reproduce the issue
import tensorflow as tf
grads = tf.random.uniform([0, 8, 1, 2], dtype=tf.dtypes.float32, maxval=100000000)
image = tf.random.uniform([0, 8, 1, 2], dtype=tf.dtypes.int32, minval=-100000, maxval=1000000)
boxes = tf.random.uniform([0], dtype=tf.dtypes.float32, maxval=100000000)
box_ind = tf.random.uniform([1, 8, 0, 0], dtype=tf.dtypes.int32, minval=-100000, maxval=1000000)
tf.raw_ops.CropAndResizeGradBoxes(grads=grads,image=image,boxes=boxes,box_ind=box_ind,method="bilinear",)

Relevant log output
2024-11-20 10:20:02.514545: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-11-20 10:20:02.535316: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:485] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-11-20 10:20:02.549411: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:8454] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-11-20 10:20:02.553443: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1452] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-20 10:20:02.586202: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 AVX512F AVX512_VNNI AVX512_BF16 AVX512_FP16 AVX_VNNI AMX_TILE AMX_INT8 AMX_BF16 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-11-20 10:20:09.256556: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2021] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 21903 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 4090, pci bus id: 0000:1f:00.0, compute capability: 8.9
2024-11-20 10:20:09.256908: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2021] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 71 MB memory:  -> device: 1, name: NVIDIA GeForce RTX 4090, pci bus id: 0000:d4:00.0, compute capability: 8.9
2024-11-20 10:20:10.096248: F tensorflow/core/framework/tensor_shape.cc:45] Check failed: NDIMS == dims() (1 vs. 4)Asking for tensor of 1 dimensions from a tensor of 4 dimensions
Aborted (core dumped)

@x0w3n,
I request you to take a look at this https://github.com/tensorflow/tensorflow/issues/65721 where a similar issue has been proposed and it is still open. Also I request to follow the similar issue which has been proposed to have the updates on the similar issue. Thank you!


How to run it?

Hello! Thank you for your question. I'm sorry for being late with my answer. I corrected some things in the Vulkan component. Installation is made by:
composer require osoznan/vulkan-astrosystem
You can use this code like a component demonstration (a random chart creation):

use vulkan\front\Examples\ChartGenerator;
use vulkan\System\Vulkan;
use vulkan\VisualChart\VisualChart;
Vulkan::initialize(); // setup the astrological system
Vulkan::insertCss('light-chart.css'); // insert css to a document for chart display
// run class for a demo which shows in general how to create charts
$ch = new ChartGenerator();
// creation of chart with random params received from the demo class
$vc = new VisualChart(
$ch->randChart(5, 2)
);
// calculate chart and run it with the given width and height
echo $vc->calculate()
->run(800, 800);

I'll try to write the general help about the Vulkan in some days. I've been thinking last year about reanimation of the component's development, you motivated to do it more quickly, thanks :-).
If you have any questions, feel free to ask them.
Best regards.
P.S. A random chart example


The reproduced results on COCO-to-VOC

Hi Fabio,
I would like to ask some questions regarding the COCO-to-VOC results.
I perform the dataset preparation step according to the README.
Then, I run the provided coco.sh to finish the step-0 and step-1 training.
However, the evaluation on coco only achieves 28.59 mIoU. I don't know why the result is too poor compared to your paper result(COCO-All: 40.6), the detailed class IoU are reported as follows.
BTW, since step-1 is trained on voc, how to get the results on COCO(61-80)?
Thanks!

Total samples: 5000.000000
Overall Acc: 0.736741
Mean Acc: 0.355343
Mean Prec: 0.416170
Mean IoU: 0.285934
Class IoU:
class 0: 0.7803624638985466
class 1: 0.0
class 2: 0.8443482556844486
class 3: X
class 4: 0.640725418774259
class 5: 0.3691700312387975
class 6: 0.0
class 7: 0.5545383087403365
class 8: 0.891710913127037
class 9: 0.7955269627722906
class 10: X
class 11: 0.4523464669711819
class 12: X
class 13: 0.05027925978293037
class 14: 0.5580934766980988
class 15: 0.07868707454509988
class 16: 0.022431797846528094
class 17: 0.013974576139435054
class 18: 0.18439521508467552
class 19: 0.321027624490874
class 20: 0.0
class 21: 0.21032159246325077
class 22: 0.10696259954614531
class 23: 0.2789628011267344
class 24: 0.2723383824462526
class 25: 0.0
class 26: 0.3858164062446917
class 27: 0.29245244264889564
class 28: 0.15235938683646286
class 29: 0.1923896367580217
class 30: 0.333419450500088
class 31: 0.5790551316016739
class 32: 0.4472113690318672
class 33: 0.4015514901863279
class 34: 0.6025023241144885
class 35: 0.5289954625680039
class 36: 0.48586341141865
class 37: 0.4239569210117141
class 38: 0.7029962077919376
class 39: 0.5575726970141223
class 40: 0.426860774277874
class 41: 0.0
class 42: X
class 43: X
class 44: 0.4088950087365174
class 45: 0.34208602247562386
class 46: 0.4019400003314785
class 47: 0.4142366906996078
class 48: 0.48391029888071846
class 49: 0.4874306930019723
class 50: 0.07728368419808865
class 51: 0.4535597597215896
class 52: 0.6458672529570286
class 53: X
class 54: 0.6269001245980994
class 55: 0.4486133177752055
class 56: 0.5265071915564131
class 57: 0.6922550138506051
class 58: 0.0
class 59: 0.3159855859270987
class 60: X
class 61: 0.001524282809864177
class 62: 0.0005324307628895296
class 63: 0.004115715609509475
class 64: 2.057941558961252e-05
class 65: 7.361325183386447e-05
class 66: 0.014190666487536205
class 67: 0.011869154551484235
class 68: 0.0
class 69: 0.00020963490414156724
class 70: 0.013198314935404704
class 71: 0.0004973000746272396
class 72: 6.932937232995318e-05
class 73: 0.004596710617840505
class 74: 0.07932975085118488
class 75: X
class 76: 0.022219097505168584
class 77: 0.0005423444474400956
class 78: 0.00019570246468256935
class 79: X
class 80: 0.16938774078738097
Class IoU:'     : 0.2859340187075097
Class Acc:'     : 0.35534273802912
Class Prec:'    : 0.41616983578468136

Thanks for the quick reply.
I have solved the problem, because I forgot replaced the annotations/ with the generated annotations_my/.


Scheduled Reports - should have the option actually include the reports

At the moment, scheduled reports provide links to the reports.  Which when combined with MFA for the admin accounts, etc, it takes more time to pull the reports...might as well just have gone to the portal and requested it since not much value in emailing a report that isn't attached other than to serve as a reminder that you need to pull the report.  Would be significantly more valuable to have the reports attached - can determine quickly if it is the "norm" or if need to investigate more, etc.  Some may like reports to stay out of email, but that can be an option to turn off/on depending on preferences.
Thanks.
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d7b70670-d462-093c-c876-9316d58c5aeb
Version Independent ID: 2104e967-cca7-8cf9-abe6-e0fa55742ff7
Content: Working with Azure ATP Reports
Content Source: ATPDocs/reports.md
Service: azure-advanced-threat-protection
GitHub Login: @shsagir
Microsoft Alias: shsagir

@J-Fedor Thanks for taking the time to leave us documentation feedback.
I believe your intended audience was product feedback, so I forwarded your feedback to the Azure ATP product team. If you had a documentation issue, feel free to add it here.
Appreciate your contribution!
#please-close


Support for Digital Ocean Spaces?

Hi,
Any support for digital ocean spaces?

Please see #20, would appreciate a PR to document this in the README if you
have a sec!
On Sat, Oct 7, 2017 at 2:37 PM Juan Antelo-Justiniano <
<EMAIL_ADDRESS>wrote:

Hi,
Any support for digital ocean spaces?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/phillbaker/digitalocean-node/issues/21, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAFxKXMIMFgapLPoLE4tkV_HIun2zJ09ks5sp8UBgaJpZM4Pxc0w
.


Hotfix for Typescript & Cleaner Package Publish.

Changelog:

Added .npmignore to not let developers confuse accessible files in the src/ directory.
Added new examples for vanilla typescript
Adjust typescript files accordingly for non-react code. Only react code uses a file name called .tsx.
Adjust README.md mistakes.
Remove unnecessary dependencies in glsl-pipeline package. Cleaner package
Remove unused rollup due to preconstruct/cli already having its rollup by running preconstruct build.
Add the types parameter in package.json for r3f and types.

Important Note
I already added a version using yarn changeset(Select Package and add minor notes) and yarn changeset version to implement the version into the package (Similar to the npm version patch command).
You need to run this command:
# Always build the package first before publishing
yarn build

# Publish to npmjs
yarn changeset publish

I will bump the version and push it


Add unit tests for the Angular app

Added unit tests for all relevant component/pages
Configured a CI build on Azure DevOps for the Frontend
Configured Code-coverage reports for the Frontend on Azure DevOps
Changed the build badges to use shields.io

We have now a good coverage state:

Closes #45

Awesome. Now only the backend looks lazy. Thanks for making me look bad :P


{Suggestion} Grenade Tracer

Any thoughts on adding a grenade tracer?

this is easy to add, just paste it.

How to add features p

https://steamcommunity.com/sharedfiles/filedetails/?id=732583079
https://cs.ingame.de/counter-strike-global-offensive/tipps-tricks/grenade-trajectory/


x/gamm: Consider removing DeletePool from GAMM keeper

Closes: #1907
What is the purpose of the change
Remove unused DeletePool from pool.go.
Brief Changelog

Remove unused DeletePool from pool.go

Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not applicable)

Lets close this, and discuss as part of #1927


As a developer, I would like to have access to a demo org where I can play around with the NPSP

All AE and Sales Engineers (and anyone else interested) should have an account created in a demo org where they can try the NPSP.
The org should be preconfigured. It could have Volunteers for Salesforce (and any other package that is free for nonprofits and widely used) also installed.

**lurch: attach W-007258

Tracking W-007258


Deprecate ServiceCardImage url in favor of src

Do have a way of rendering a deprecated tag for props? Looks like we can via https://github.com/thumbtack/thumbprint/blob/e9016e6b8589710641dbd7ded6434095dab5cdf0/www/src/components/thumbprint-components/component-footer/index.jsx#L41 but wasn't sure what the doclet syntax looked like, couldn't find an existing example.

Just fixed the docs issue. I think it broke in a recent react-docgen breaking change. 🤷♂


ipmitool sdr type 'Power Supply'|grep 'Presence detected'

how to get same result by using the library? thanks so much.

You can refer to GetSensors method and Sensor's HumanStr method (since from v0.5.6).
The "Presence detected" string for "Power Supply" type sensors just means the specific discrete event number(offset) is set/active for the sensor.
You can get discrete active events (number) of a sensor by Sensor's DiscreteActiveEvents method and then get the  event string correspoding to the event number by Sensor's EventString method.


Make clippy check tests and fix warnings

Adding --all-targets makes clippy check tests. This results in a quite a few warnings as previously tests were ignored.
TODO: fix warnings

I'm having trouble pushing to that branch to trigger a CI rerun. Closing this in favor of #64.


ImageGallery with Request-Headers Error

When using the ImageGallery with Request-Headers set following error occurs:
Failed to execute 'setRequestHeader' on 'XMLHttpRequest': The object's state must be OPENED.
Because the XMLHttpRequest has to be opened before setting the Request-Headers.

@verti4cal Thank you for your contribution!!
I'll notify you after version update.


This project works too well

Hello, I am here to inform all of you of this critical issue, this project works perfectly fine with no bugs whatsoever, as you can already tell this is very dangerous and should be fixed as soon as possible, I don't know how the authors of this project could've let something like this happen! Please fix this before it causes any damage.

Unfortunately, I have to inform you that introducing bugs is currently totally out of scope.
That being said, I have good news for you: Try Enterprise™. It is non-deterministic-unnecessarily-statically-typed™, which means that you get bugs for free, with having to write minimal code.

Thank you very much. Enterprise™ is now my favorite non-deterministic-unnecessarily-statically-typed™ language, I will recommend this non-deterministic-unnecessarily-statically-typed™ language to everyone else I know!

I knew you would love it if you like bugs. TBH, personally I think that all programming languages should be non-deterministic-unnecessarily-statically-typed™ because non-deterministic-unnecessarily-statically-typed™ languages are pretty much unbeaten in code-to-bug-ratio. And yes, Enterprise™ is definitely the best non-deterministic-unnecessarily-statically-typed™ language.

Why do you need more enterprise-bugs, you should consider to drop-off Typescript and going back to the roots.

What's Typescript?

oo1john is making up programming languages and trying to be funny

Don't forgot to add Azure cloud services with auto-scale app feature.


How switch from zf2 to expressive

Hi. How can I switch from zf2 to expressive, while maintaining a modular system and using all the features of the zf2?

We're working on an Expressive wrapper for ZF2 at this time, but do not have a scheduled date for completion. That wrapper will mainly allow you to expose an existing ZF2 application within an Expressive install, and the migration path would then be to gradually rewrite your controllers as middleware, and attach them directly to the Expressive application.
In the meantime, you can already use any ZF2 components you want within an Expressive application, just by requiring them via composer:
$ composer require zendframework/zend-<component>

This will add it to your list of requirements and install it. Once you have, you can make use of it immediately. In some cases, you may need to expose factories or abstract factories; you can do that within your dependencies configuration. In some cases, in ZF2, we auto-register some configuration for plugin managers which you'll need to duplicate in your Expressive application; we demonstrate one such case with form view helpers in the documentation already.
In terms of modularity, we already have a cookbook recipe covering modular applications; we will likely make this either an option or the default in the skeleton with 1.1.


Need help on setting up my path in nested directory structure

I am following the contribution guide, I just set up my project in the nested directory structure as I am in development mode so I just not set up my virtual host as well.
For e.g.,
- project
   - blog-laravel-app
   - canvas-repo

I just set up everything only my assets path is mismatching. I am just seeing a white screen nothing else on debugging I am able to reproduce that it's looking for the http://localhost and my project is in 'http://localhost/blog-laravel-app/public/canvas'. Even all API routes are also 404.
Is there any way to change the path just for development purposes?

Since not getting any replies ended up setting a virtual host.

Sorry I didn't get a chance to respond to this. I'm glad you figured it out so quickly though, let me know if I can help out with anything else.


chore(main): release X 1.15.5

:robot: I have created a release beep boop
1.15.5 (2024-08-21)
Miscellaneous

X: try auto lock screen (44733f2)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

X-v1.15.5
:sunflower:


Update zio-prelude to 1.0.0-RC8

Updates dev.zio:zio-prelude from 1.0.0-RC6 to 1.0.0-RC8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-prelude" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release

Superseded by #199.


Make ObjectStoreProvider fallible (return Result rather than Option)

Which issue does this PR close?

re https://github.com/apache/arrow-datafusion/issues/3424
Rationale for this change

https://github.com/apache/arrow-datafusion/pull/3540#issuecomment-1254598498
What changes are included in this PR?

Makes ObjectStoreProvider::get_by_url fallible and clarifies some docs
Are there any user-facing changes?

Thanks @tustvold

Codecov Report

Merging #3584 (067a25c) into master (b54a56f) will decrease coverage by 0.00%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master    #3584      +/-   ##
==========================================
- Coverage   86.03%   86.02%   -0.01%
==========================================
  Files         300      300
  Lines       56253    56250       -3
==========================================
- Hits        48395    48390       -5
- Misses       7858     7860       +2

Impacted Files
Coverage Δ

datafusion/core/src/datasource/object_store.rs
85.05% <20.00%> (+0.61%)
:arrow_up:

datafusion/expr/src/logical_plan/plan.rs
77.10% <0.00%> (-0.33%)
:arrow_down:

datafusion/common/src/scalar.rs
85.18% <0.00%> (-0.07%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks @alamb for this info. I think better to change the return type to be
Result<Option<Arc<dyn ObjectStore>>>

Follow on PR and discussion for Result<Option> is https://github.com/apache/arrow-datafusion/pull/3595


Version 1.4.0-pre.2.

Add negation to selector expressions (#1016).
Add negated match criteria (#1003).
Fix next-tier action, which incorrectly accepted packets (#1014).
Update bird config generation scripts.
Fix conntrack entry deletion (#987).
Fix iptables retry on commit (#1010).

LGTM.


Development Strict Mode

Enables TS strict mode
Adds script to check types
Adds workflow to run check-type script
Updates the code-checking workflows to share the same set-up job

This updates the tsconfig.json option to enable strict mode. However, we use TSX for development and SWC for release, which do not type-check, so this option only gives additional linting/visual-feedback in VSCode.
Additionally, I've added a NPM script npm run lint:types and a GitHub workflow that runs it.
This depends on #1005.

I'm done messing with the workflows. Definitely squash this one. 😄


Fix for bugs arising for Super Admins editing Departments of an Orega…

…nisation they did not belong to.
Fix for issue #2088.

@briri Updated code as suggested.


Refactor createCircuitWebWorkerformat for improved initialization

Issue: #4
I was unable to run test in this repo:

Tried to fix it, changes:

Removed async from the initialization function.
Properly typed the return value acc to CircuitWebWorker interface.

@seveibar I am not sure if these changes are required/desirable or i missed something in setting up the project.
Please do let me know

@mrudulpatil18 the fix for this is just adding "await" to the test

but we should get tests working on ci so that i don't break this again 😁

closing in favor of https://github.com/tscircuit/eval-webworker/pull/5


Add less plugin link

I have been working on a less plugin as a proof of concept, I think it would be added to readme.
As less compiler is async, I reused some code from postcss plugin.

Awesome! thank you @erasmo-marin


186939433 display exemplars

This creates and loads Exemplar documents in the Sort Work tab, as described in PT-186939433
Creating Exemplar Documents at runtime:

create-exemplar-docs is a utility file that orchestrates the creation of a an ExemplarDocument,  based on exemplar json
It is also associated with a user, "Ivan Idea."  To do this, anaddUser action was added to class.ts (Class model) so that the exemplar user "Ivan Idea" can be added to the class as needed
The document is given an id that encodes the url of the exemplar json
A loading message is added while exemplars are loading

Structural changes

exemplarPaths is a new property of the problem model
The clue configuration property curriculumBaseUrl is changed to curriculumSiteUrl
The launch-sequence diagram is updated to include createAndLoadExemplarDocs
The changes to the curriculum structure in the qa-config-subtabs unit reflect the overall content structure that will be rolled out with units that include exemplars., content.json for problem sections and exemplars are now in sections and exemplars directories
An example exemplar is included in that unit

Other UX changes

Sortable documents now consistently include name prefix in captions

Yeah anytime we can get rid of those waits we should. Usually there is a way to search for something on the page instead of just blindly waiting.


Wrong calculation on specific value

I'm having an issue on this specific test case:
		{
			Payments: []Payment{
				Payment{mustParseDate("2022-08-26"), -20},
				Payment{mustParseDate("2022-09-26"), 0.12},
				Payment{mustParseDate("2022-10-26"), 0.12},
				Payment{mustParseDate("2022-11-28"), 0.12},
				Payment{mustParseDate("2022-12-26"), 0.12},
				Payment{mustParseDate("2023-01-26"), 20.12},
			},
			Xirr: 1.074,
		},

The calculation returns 1.133 instead of the expected 1.074, that is the correct one.
Increasing the maxRate by a 10 factor (from 1000000 to 10000000) seems to solve the issue.

Thank you very much for the issue!
I found actual reason wrong computation and fix it myself.

Even better, mine was just a try-and-hope approach :)
Thanks!


Improve code base

Changed double quotes to single unless interpolation or special
symbols are used in string
Rename methods prefixed with get (as all method essentially get
something) to find
Use new Ruby (> v1.9) hash syntax
Swap out gsub with tr when there’s no regular expression for
performance
Remove parenthesis for method calls with no argument

The reason why it fails with Travis appears to be an issue with the bundler and the configuration, rather than the code, so should be problem free.

@yatish27


Multiple GitGraph improvements: Exclude PR heads, Add branch/PR links, Show only certain branches,

This PR adds multiple improvements to GitGraphs:

PR heads can be excluded from view
Branch references within the commit list are now rendered as PRs, branches, tags or remotes and are clickable and will go to the branch/tag or PR
Branches/PRs/Tags can be chosen to be focused on
Commit signature verification and trust status is shown as are user avatars.

Also adds backend support for graphs on certain files.
Fix #10327
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>Screenshots
Basic View

Exclude PRs

(as you can see #8 has disappeared)
Select a few Branches

Select a few Branches (exclude PRs)

Select a few Branches+PRs (Exclude the other PRs)

Issues:

As the selection box expands it begins to float over the top of the graph - this is not ideal.
It might be that clicking on the branch should really add it to the selection or have that option.
It would also be good to be able to do the graph of the branch roots. (setting ?branch=refs/heads/branchA...refs/heads/branchB does work but it doesn't include the merge base so you get two disconnected branches.)
The code just uses a pre-rendered div-only=true section which might be usable elsewhere with some further thought.

Codecov Report

Merging #12766 into master will increase coverage by 0.02%.
The diff coverage is 52.34%.

@@            Coverage Diff             @@
##           master   #12766      +/-   ##
==========================================
+ Coverage   43.26%   43.29%   +0.02%
==========================================
  Files         648      648
  Lines       71922    72033     +111
==========================================
+ Hits        31120    31187      +67
- Misses      35762    35792      +30
- Partials     5040     5054      +14

Impacted Files
Coverage Δ

modules/context/pagination.go
85.00% <0.00%> (-15.00%)
:arrow_down:

modules/git/repo.go
48.22% <0.00%> (-1.53%)
:arrow_down:

modules/git/repo_commit.go
50.54% <0.00%> (ø)

modules/templates/helper.go
45.92% <0.00%> (-0.47%)
:arrow_down:

routers/repo/commit.go
29.57% <39.39%> (+0.75%)
:arrow_up:

modules/git/ref.go
53.84% <58.33%> (+53.84%)
:arrow_up:

modules/git/commit.go
54.27% <61.53%> (+0.22%)
:arrow_up:

modules/gitgraph/graph.go
57.14% <64.70%> (-3.52%)
:arrow_down:

modules/context/repo.go
58.52% <83.33%> (+0.30%)
:arrow_up:

modules/gitgraph/graph_models.go
86.51% <100.00%> (+2.73%)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e204398...64cd026.
Also, the buttons/dropdown look too big. Maybe try small/tiny classes on them.

Also, I think using avatars might be nice in that list, e.g.
<avatar> <commit title> <relative time>

Header and buttons are not properly vertically centered, Maybe needs some flexbox.

Done

Also, the buttons/dropdown look too big. Maybe try small/tiny classes on them.

I can't seem to easily change that.

Branch tags also have a centering issue, maybe I'll play with those later.

I've tried making these display: inline-flex; align-items:center; but I think it looks worse.

Also, I think using small avatars (20px) might be nice in that list, e.g.
<avatar> <commit title> <tags> <relative time>

I think that could be quite expensive to do - it might need another PR.

Codecov Report

Merging #12766 into master will increase coverage by 0.00%.
The diff coverage is 52.34%.

@@           Coverage Diff            @@
##           master   #12766    +/-   ##
========================================
  Coverage   42.01%   42.02%
========================================
  Files         683      683
  Lines       75215    75320   +105
========================================
+ Hits        31605    31653    +48
- Misses      38443    38489    +46
- Partials     5167     5178    +11

Impacted Files
Coverage Δ

modules/context/pagination.go
85.00% <0.00%> (-15.00%)
:arrow_down:

modules/git/repo.go
45.17% <0.00%> (-1.02%)
:arrow_down:

modules/git/repo_commit.go
50.91% <0.00%> (ø)

modules/templates/helper.go
46.13% <0.00%> (-1.13%)
:arrow_down:

routers/repo/commit.go
29.57% <39.39%> (+0.75%)
:arrow_up:

modules/git/ref.go
53.84% <58.33%> (+53.84%)
:arrow_up:

modules/git/commit.go
53.61% <61.53%> (-0.44%)
:arrow_down:

modules/gitgraph/graph.go
57.14% <64.70%> (-3.52%)
:arrow_down:

modules/context/repo.go
56.29% <83.33%> (+0.31%)
:arrow_up:

modules/gitgraph/graph_models.go
86.51% <100.00%> (+2.73%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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

@silverwind would you be able to review again?

Please pull in https://github.com/silverwind/gitea/commit/36863be907058e98f5d0147f3555c7a7df63c229, has some fixes to that horribly hackish dropdown:

Also pull in https://github.com/silverwind/gitea/commit/8ad05154851a07c6f66087d03f9531bb07c4c304.

And some more stuff in https://github.com/silverwind/gitea/commit/cb192c2c56916ba1a3c4c00d5ef71a8cb18edbb0.

@silverwind changes pulled in

The trouble is on big trees you do need it - perhaps it should be more subtle instead?

Not sure what to do about it, maybe limit the background change to only the graph parts, not the text?

How about making it:
    li.highlight,
    li.hover {
      background-image: linear-gradient(90deg, rgba(0, 0, 0, .05), transparent 50%);
    }

    li.highlight.hover {
      background-color: linear-gradient(90deg, rgba(0, 0, 0, .1), transparent 50%);
    }

Some tweaks in https://github.com/silverwind/gitea/commit/c2ce5dc3956de93c06e24993c392d0fc2e64f696. I made the highlight row-only, I think it's sufficient and not as distracting.
Also noticed the page is missing a title, which should be fixable by adding ctx.Data["Title"] = ctx.Tr("commit_graph") on line 92 of routers/repo/commit.go but for some reason it won't output the translation string for me (maybe translation needs to be activated for that context somewhere?).

Some more stuff in https://github.com/silverwind/gitea/commit/f6334788810c01f84202c9f590aeeaefd7638ccb.

You needed to prefix the commit_graph with repo.

BTW I think the divider between the hide-pr-requests was better - but I'm not going fight over it.

You needed to prefix the commit_graph with repo.

Ah, good to know. I wouldn't have thought of that because the translation key does not have .repo.

BTW I think the divider between the hide-pr-requests was better - but I'm not going fight over it.

I think it looked slightly odd odd with non-equal spaced dropdown children.
Oh and one more fix in https://github.com/silverwind/gitea/commit/9c772cbfa4e58a61dd8b5bad6ab075829596bd45 which fixes some odd z-index issue with the loading indicator and positions it a bit down so it does not stick to the top of the container.

🚀


Why do I need special permission when using HttpListener?

Hey,
this issue is a little bit C# bashing because some interfaces are design with assumptions that are too specific for most users, HttpListener is one of them.
First of all, I already read about the HTTP namespace system.
HttpListener allows simple and high level creation of HTTP servers, but what if I want to create a HTTP server that can listen on all hosts, without requiring admin permissions or running arbitrary netsh commands?
If I would run this code as an unprivileged user the result would be an access exception.
HttpListener listener = new HttpListener();
listener.Prefixes.Add("http://*:1234/");
listener.Start();

However running the following code proves that an unprivileged user could potentially write his own HTTP server, that allows access from all interfaces.
TcpListener server = new TcpListener(IPAddress.Any, 1234);
server.Start();

I wonder why there is no way to take all the benefits of the HttpListener and skipping the namespacing system. Other languages have such features.
Is there any chance to request an API addition that allows such things?
For example allowing the constructor of HttpListener to take an TcpListener-Instance.

I should have opened this issue in net standard.