to start the project it's  a take a long time

Hi
i run the project before but when i close my device and come back the next day to runn the project via
./dc-build.sh
it's take a long time , may be 4 hours to run
it's just show things like this
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:07:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:07:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[95519682-75d1-4a61-8287-e93ca4774d1f] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:07:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[95519682-75d1-4a61-8287-e93ca4774d1f] succeeded in 0.05016916399472393s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:08:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:08:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[82140fc7-49cc-4773-aa93-c27de224d6bc] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:08:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[82140fc7-49cc-4773-aa93-c27de224d6bc] succeeded in 0.02522215999488253s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:09:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:09:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[269e3851-e222-47ba-a189-102d30a752d1] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:09:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[269e3851-e222-47ba-a189-102d30a752d1] succeeded in 0.05195289800030878s: None
django-defectdojo-master-postgres-1      | 2024-07-04 06:09:52.604 UTC [26] LOG:  checkpoint starting: time
django-defectdojo-master-postgres-1      | 2024-07-04 06:09:53.483 UTC [26] LOG:  checkpoint complete: wrote 11 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.828 s, sync=0.005 s, total=0.880 s; sync files=10, longest=0.005 s, average=0.001 s; distance=4 kB, estimate=4 kB; lsn=0/26AFBF8, redo lsn=0/26AFBC0
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:10:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:10:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[4336a539-023a-4ad2-90e1-9df7b8ee7e01] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:10:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[4336a539-023a-4ad2-90e1-9df7b8ee7e01] succeeded in 0.04733875899546547s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:11:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:11:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[a7b43712-fabe-4645-9e68-f208f646c2aa] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:11:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[a7b43712-fabe-4645-9e68-f208f646c2aa] succeeded in 0.04769722700439161s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:12:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:12:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[01fd6574-7787-4475-ae9a-86e5c5392453] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:12:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[01fd6574-7787-4475-ae9a-86e5c5392453] succeeded in 0.05397990100027528s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:13:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:13:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[c1d3f5e4-8d81-4d9d-8daf-334658f82d3b] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:13:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[c1d3f5e4-8d81-4d9d-8daf-334658f82d3b] succeeded in 0.024056804002611898s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:14:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:14:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[6f4af533-7d69-42ad-b503-a0d388819caa] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:14:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[6f4af533-7d69-42ad-b503-a0d388819caa] succeeded in 0.05401885900209891s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:15:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:15:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[09416ced-b4d4-4a9d-875d-04c385640162] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:15:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[09416ced-b4d4-4a9d-875d-04c385640162] succeeded in 0.025804536999203265s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:16:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:16:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[d5619c13-d852-4f59-8281-7d3b65e41b8e] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:16:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[d5619c13-d852-4f59-8281-7d3b65e41b8e] succeeded in 0.051120261996402405s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:17:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:17:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[7c51d5c0-c879-44e8-baf1-a5edc4532c57] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:17:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[7c51d5c0-c879-44e8-baf1-a5edc4532c57] succeeded in 0.048265119999996386s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:18:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:18:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[d0bf82d6-d906-4b0a-8421-abb98a4abab2] received
django-defectdojo-master-redis-1         | 1:M 04 Jul 2024 06:18:22.437 * 100 changes in 300 seconds. Saving...
django-defectdojo-master-redis-1         | 1:M 04 Jul 2024 06:18:22.438 * Background saving started by pid 21
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:18:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[d0bf82d6-d906-4b0a-8421-abb98a4abab2] succeeded in 0.047370763997605536s: None
django-defectdojo-master-redis-1         | 21:C 04 Jul 2024 06:18:22.459 * DB saved on disk
django-defectdojo-master-redis-1         | 21:C 04 Jul 2024 06:18:22.461 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
django-defectdojo-master-redis-1         | 1:M 04 Jul 2024 06:18:22.543 * Background saving terminated with success
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:19:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:19:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[9cfb289c-932e-45bd-b069-5995c0184345] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:19:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[9cfb289c-932e-45bd-b069-5995c0184345] succeeded in 0.04852304000087315s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:20:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:20:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[159ce6a7-b4f7-49a5-9957-81089bae9724] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:20:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[159ce6a7-b4f7-49a5-9957-81089bae9724] succeeded in 0.05086795300303493s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:21:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:21:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[7454aa97-62fe-4053-ab2c-81c11e5e05ee] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:21:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[7454aa97-62fe-4053-ab2c-81c11e5e05ee] succeeded in 0.07640753799933009s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:22:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:22:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[629bac14-23fb-4c3e-87a0-0730cfc2b7b0] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:22:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[629bac14-23fb-4c3e-87a0-0730cfc2b7b0] succeeded in 0.046505268997862004s: None
django-defectdojo-master-celerybeat-1    | [04/Jul/2024 06:23:22] INFO [celery.beat:278] Scheduler: Sending due task dedupe-delete (dojo.tasks.async_dupe_delete)
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:23:22] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[718a10b5-50b3-4133-b470-af026c07fd28] received
django-defectdojo-master-celeryworker-1  | [04/Jul/2024 06:23:22] INFO [celery.app.trace:128] Task dojo.tasks.async_dupe_delete[718a10b5-50b3-4133-b470-af026c07fd28] succeeded in 0.050510880995716434s: None

@abdoqaidhaidar
Given the information you provided, it's not possible to provide much help or advice.
You don't mention how you've deployed DefectDojo nor with what resources. I could guess you're running this on a raspberry pi and decide that's why it's running so slow. I have no real information beyond some log output.
I'd also suggest that you as these kind of questions on OWASP Slack on the #defectdojo channel as it appears to be something around how you deployed/configured DefectDojo versus a true issue with the software running the app.
You can get info on joining OWASP's Slack at https://github.com/DefectDojo/django-DefectDojo?tab=readme-ov-file#community-getting-involved-and-updates


FIRCannotCallOnMainThread - "This method must be called on a background thread."

I am using NextLevel for Session Capture - https://github.com/NextLevel/NextLevel
I am using Firebase Vision Face Detection to find the Head Z angle (headEulerAngleZ).
on the callback
func nextLevel(_ nextLevel: NextLevel, didAppendVideoSampleBuffer sampleBuffer: CMSampleBuffer, inSession session: NextLevelSession) {
I am using
let visionImage = VisionImage(buffer: sampleBuffer)
From the code of nextLabel it is clear that the callback is made on the main thread -
 DispatchQueue.main.async {
   self.videoDelegate?.nextLevel(self, didAppendVideoSampleBuffer: sampleBuffer, inSession: session)
 }

On using the same Main Async Callback App crashed with an error message -

Thread 1: Exception: "This method must be called on a background thread."

But if I do process operation on Background
DispatchQueue.global(qos: .background).sync {  }
Again the code crashed at code -

detectedFaces = try faceDetector.results(in: image)

var detectedFaces: [VisionFace]? = nil
      do {
        detectedFaces = try faceDetector.results(in: image)
      } catch let error {
        print("Failed to detect faces with error: \(error.localizedDescription).")
      }

Question - Which is the correct way of calling the

Vision Face Detected

method on a background thread?

I was able to make the code work without crashing by removing the delegate call which was on Main Thread. This was not the desired as that was the only workaround that worked for me.
For example, I have tried following style to cal the VisionFace detector on a background thread as following -
let dict: NSDictionary = [
      "imageWidth": imageWidth,
      "imageHeight": imageHeight,
      "visionImage": visionImage
    ]
    if Thread.isMainThread {
      self.performSelector(inBackground: #selector(detectFace(info:)), with: dict)
    } else {
      self.detectFacesOnDevice(in: visionImage, width: imageWidth, height: imageHeight)
    }

And then the method -
 @objc func detectFace(info: NSDictionary) {
    if let imageWidth = info["imageWidth"] as? CGFloat,
      let imageHeight = info["imageHeight"] as? CGFloat,
      let visionImage = info["visionImage"] as? VisionImage {
      self.detectFacesOnDevice(in: visionImage, width: imageWidth, height: imageHeight)
    }
  }

Even if it works well for most cases. There are cases when it doesn't work and crash on -
detectedFaces = try faceDetector.results(in: image).
For example -
    let options = VisionFaceDetectorOptions()
    //options.landmarkMode = .all
    //options.classificationMode = .all
    //options.contourMode = .all
    options.performanceMode = .accurate

Only

Performance Mode  = .accurate

seems to work, other options will again trigger a crash, as the recording, affected by other Option flags.


fix: Add dependency on upstream simpleeval

See https://github.com/meltano/sdk/issues/1500
It seems the maintainer is now actively developing simpleeval :)

:books: Documentation preview :books:: https://meltano-sdk--1504.org.readthedocs.build/en/1504/

Closing but we can revisit later


How do I update layers？

with(state) {
addLayer(tileStreamProvider)
}
I want to constantly update the layer， But there was a crash： java.lang.OutOfMemoryError: Failed to allocate a 17572876 byte allocation with 8388608 free bytes and 15MB until OOM
at  :
val bitmapForLayer = layerIds.associateWith {
Bitmap.createBitmap(tileSize, tileSize, bitmapConfig)
}

OutOfMemoryError (OOM) means you're using the memory too much. Most probably not due to the library.
There's a stress test of MapCompose which frequently updates layers.


Reconciliation V3

[x] Script to get all ETH events range
[x] Better logging
[x] Filtering out zero priced sales
[x] Reconcile with previous version
[x] Publish to IPFS - QmNPcyZyEJXeytDPuCF1hXEuy3aiJfjmZ7YK6HbhYi6AaA
[ ] Update contract

I have run all the scripts getting 19.94 after merge. I looked through the code and it is looking as expected. I suspect that OpenSea is not surfacing some sales which is why we are getting lower than expected


⚠ Bofrost.de has degraded performance

In 09f9cb2, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 915 ms

Resolved: Bofrost.de performance has improved in 1ba7270 after 54 minutes.


Don't encrypt reaction events for now

Fixes https://github.com/matrix-org/pantalaimon/issues/23

Codecov Report

Merging #25 into master will decrease coverage by 0.11%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
- Coverage   23.97%   23.86%   -0.12%
==========================================
  Files          10       10
  Lines        2181     2183       +2
==========================================
- Hits          523      521       -2
- Misses       1658     1662       +4

Impacted Files
Coverage Δ

pantalaimon/daemon.py
26.66% <0%> (-0.53%)
:arrow_down:

Continue to review full report at Codecov.

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


World Guard support flag

By toggling the world guard support, we can't use rpg items in regions. But, is there a flag that allows rpg items in the regions where this flag is enabled? If not, could you add it for 1.7.10?

In newer version you can disable some powers per region. May be a workaround for this.


TVL strategy

Codecov Report

Merging #120 (e75fc65) into master (789dc5d) will increase coverage by 0.44%.
The diff coverage is 94.88%.

@@            Coverage Diff             @@
##           master     #120      +/-   ##
==========================================
+ Coverage   88.79%   89.24%   +0.44%
==========================================
  Files          45       48       +3
  Lines        2901     2919      +18
  Branches      435      435
==========================================
+ Hits         2576     2605      +29
+ Misses        325      314      -11

Impacted Files
Coverage Δ

...s/weight-strategies/MCapWeightStrategyRebinder.sol
0.00% <0.00%> (ø)

...ontracts/weight-strategies/WeightValueAbstract.sol
94.23% <94.23%> (ø)

...ontracts/weight-strategies/WeightValueStrategy.sol
97.16% <97.16%> (ø)

contracts/weight-strategies/MCapWeightAbstract.sol
72.22% <100.00%> (-16.35%)
:arrow_down:

contracts/weight-strategies/MCapWeightStrategy.sol
100.00% <100.00%> (+15.38%)
:arrow_up:

contracts/weight-strategies/TvlWeightStrategy.sol
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


fix(whitepaper): fix cactus_arch.svg

Describe the bug
The current Cactus architecture diagram (cactus_arch.svg on whitepaper) has a typo. Also, when you apply the black background setting on GitHub, the diagram does not display correctly.
To Reproduce
To post a pull-request for solving this issue.

@takeutak Can this issue be closed now that the PR has been merged?


deployed chart -  undefined_endpoint

After Deploying the chart all i see is
"{"code":"undefined_endpoint","message":"Not Found"}"
by opening the browser on the ingress hosts urls this seems not correct ?

Hi @lachnerd - OpenFGA is an API, and serves nothing at the default GET /, try GET /healthz or GET /stores
This is the list of our API endpoints: https://openfga.dev/api/service
We also have a CLI that can help you interact with the API quickly


Cherry-pick commits from 4.7 branch to master

Description
Cherry-pick changes to master
#1498
#1496
#1495
#1494
#1493

Pull Request Test Coverage Report for Build 95595

13 of 15 (86.67%)  changed or added relevant lines in 9 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.05%) to 84.534%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/botFrameworkHttpClient.ts
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder/src/botFrameworkAdapter.ts
6
74.33%

Totals

Change from base Build 94922:
0.05%

Covered Lines:
8429

Relevant Lines:
9647

💛  - Coveralls


update(rules): add container check to Clear Log Activities rule

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

Proposed rule maturity level

Uncomment one (or more) /area <> lines (only for PRs that add or modify rules):

/area maturity-stable

/area maturity-incubating

/area maturity-sandbox

/area maturity-deprecated

What this PR does / why we need it:
This PR adds the container check to the Clear Log Activities rule as we have noticed that the rule is being triggered by containerd activities in the host, example json output:
{"uuid":"72b27712-9a80-4180-ab2f-c7d298114fb9","output":"18:31:35.698169341: Warning Log files were tampered (file=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/338/fs/var/log/dpkg.log evt_type=openat user=root user_uid=0 user_loginuid=-1 process=containerd proc_exepath=/usr/bin/containerd parent=systemd command=containerd terminal=0 exe_flags=O_TRUNC|O_CREAT|O_WRONLY|O_CLOEXEC|O_F_CREATED container_id=host container_image=<NA> container_image_tag=<NA> container_name=host k8s_ns=<NA> k8s_pod_name=<NA>)","priority":"Warning","rule":"Clear Log Activities","time":"2023-09-27T18:31:35.698169341Z","source":"syscall","output_fields":{"container.id":"host","container.image.repository":null,"container.image.tag":null,"container.name":"host","evt.arg.flags":"O_TRUNC|O_CREAT|O_WRONLY|O_CLOEXEC|O_F_CREATED","evt.time":1695839495698169300,"evt.type":"openat","fd.name":"/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/338/fs/var/log/dpkg.log","k8s.ns.name":null,"k8s.pod.name":null,"proc.cmdline":"containerd","proc.exepath":"/usr/bin/containerd","proc.name":"containerd","proc.pname":"systemd","proc.tty":0,"user.loginuid":-1,"user.name":"root","user.uid":0},"hostname":"production-us-cluster-0-falco-sf9n5","tags":["NIST_800-53_AU-10","T1070","container","filesystem","host","maturity_stable","mitre_defense_evasion"]}

Which issue(s) this PR fixes: I haven't raised one as it seems quite simple

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: brennoo
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @brennoo! It looks like this is your first PR to falcosecurity/rules 🎉

could we perhaps exclude the specific fd path.
Excluding something like (proc.name=containerd and fd.name endswith /var/log/dpkg.log)
As far as I know the noise is just on this file. It might not worth it reduce the overall rule use case for one file.

hi there, thanks for reviewing my first PR :-)

could we perhaps exclude the specific fd path. Excluding something like (proc.name=containerd and fd.name endswith /var/log/dpkg.log) As far as I know the noise is just on this file. It might not worth it reduce the overall rule use case for one file.

this is what I did in my local rules (fd.path startswith "/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/") but it seems containerd also touch other paths, so far only one extra prefix:
$ jq '.[].output_fields | ."fd.name"' falco_events.json | sort | uniq -c | sort -rn | head
   1 "/var/lib/containerd/tmpmounts/containerd-mount991927798/var/log/yum.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount980514857/var/log/dpkg.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount83416718/var/log/yum.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount826255972/var/log/dpkg.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount813808526/var/log/anaconda/syslog"
   1 "/var/lib/containerd/tmpmounts/containerd-mount807056178/var/log/yum.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount709329761/var/log/yum.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount661173829/var/log/dpkg.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount61672547/var/log/dpkg.log"
   1 "/var/lib/containerd/tmpmounts/containerd-mount587022222/var/log/dpkg.log"

I'm adding this prefix to allowed_clear_log_files and will monitor during the day, for some reason I had the impression that this rule was meant for containers only but it makes sense it would also good to use it for host detection.

OK, this macro fixed the false positives:
- macro: allowed_clear_log_files
  condition: (proc.name=containerd and (fd.name startswith "/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/" or
              fd.name startswith "/var/lib/containerd/tmpmounts/"))

is this something you would consider adding upstream as a dedicated macro or such cases must be handled locally?

Yes from my side +1, ty!

+1 from my side as well! Thanks @brennoo

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

1031c9c Add macro dedicated to containerd activities

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

@jasondellaluce what is current guidance re failing CI because of the required engine version format cutover?Thanks!

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: brennoo, incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 59ffcab70ba72f84f9fb58adb1ed386e32815b5d


Getting wetty to work on an Electron shell

@krishnasrinivas , I am trying to use wetty to work from an electron shell. hterm is dependent on chrome. are there any alternatives that I could use to make it browser independent?

you can use https://github.com/rabchev/wetty till those changes are merged in. I have not yet taken those changes in as copy/paste does not work there yet.

Thank you. Works like magic! :-)


Camera area limitation

Leader
@issmail-basel
User story
The user creates, edits and publishes the map with Re:Earth. However, Re:Earth supports the 3D globe and it's not needed for some users. Users want to restrict the area the viewers can go around the map not to get them lost. With this feature user can define where the viewers go around and let them focus on what they want to show.
Requirements

can capture the area
can turn on and off this feature
can re-capture the area
On published page
can't go else where except the captured area

Test list
Development outline

[ ] Create boundary shape and add visualize the boundary as an entity (for users and depending on scene properties)
[ ] Hide visualized boundaries on preview and publish mode
[ ] Listen to the camera on change event and prevent the camera from exceeding the limits (with a simple hook)
[ ] Find a smooth way to prevent the camera from bouncing on edges (on mouse move)
[ ] Fly the camera to the allowed space on initial load?
[ ] Add UI options
[ ] Check and discuss edge cases as (if storytelling is enabled and some layers outside the limits, initial flight outside the limits)
[ ] try 2d plane of globe???
[ ] Discuss UI

Questions from previous points:

Should I restrict Z-axis so the user can’t zoom out as much as he can? (it is restricted right now)
Should I try a 2d plane of the globe as this feature is designed to limit an area?
What if use using storytelling mode with layers outside the limit, or has initial flight to a place outside the limit boundaries?

Inspired by camera-limiter branch inside cesium JS
https://github.com/CesiumGS/cesium/pull/6172/files

Since we had released this feature, I close this PBL.


Fix trigger screenshot

The previous image used "trim" and this one uses "latest" as the instructions state.

Done


Break from stream loop early if we encounter an error

Fixes #2144
Consider the following. Let's say we are looping over a stream and checking for eof():
std::string message("hi there i am a message whoo hoo\nhi there i am a message whoo hoo\nhi there i am a message whoo hoo\nhi there i am a message whoo hoo\n");
std::vector<std::string> log_lines;
std::istringstream is(message);

while (!is.eof()) {
  std::string line;
  std::getline(is, line);
  log_lines.emplace_back(std::move(line));
}

This will output:
hi there i am a message whoo hoo|hi there i am a message whoo hoo|hi there i am a message whoo hoo|hi there i am a message whoo hoo||

Notice the extra blank entry at the end. It is incorrect to loop on eof() because if an error in the stream occurred, we will do an extra read on an invalid stream before the loop ends. One approach is to refactor the loops but this can result in performance degradation. Instead, we just check the stream state inside the loop and break early.

This change is

FYI, there is one more instance I didn't tackle in this PR because it is a little bit more complicated to refactor, so I would like to leave it to someone else: https://github.com/googleapis/google-cloud-cpp/blob/master/google/cloud/storage/client.cc#L125.


phonegap build complains that it does not support v 1.0.3

It's great that v1.0.3 added support to show the keyboard on Android and it resolves a number of issues I was having. However, phonegap build is complaining that it does not support v1.0.3.
Can you please fix that?

Hello,
Didn't want to open a new bug for it: seems like phonegap build does not any version > 1.0.3.
Is it a matter of submitting an new update? @adamdbradley
Thanks in advance.
Ithav


[enhancement] refactor bert finetuning script

Description
summary of changes:

introduce GlueTask class which stores the metadata of the task (class labels, is_pair, etc)
reuse the Dataset API for glue datasets introduced in #682
fix bert transform for the case when label is not available
add script test

Checklist
Essentials

[ ] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@Gpwner here is the fix for the BERTTransform bug. Thanks for reporting

Job PR-692/10 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-692/10/index.html

I try the new script, and found the error:
@eric-haibin-lin
INFO:root:processing dataset...
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/home/pengxiny/anaconda3/envs/mxnet-cpu/lib/python3.6/multiprocessing/pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "/home/pengxiny/anaconda3/envs/mxnet-cpu/lib/python3.6/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/home/pengxiny/autotest_gluonnlp/gluon-nlp/scripts/bert/dataset.py", line 432, in __call__
    return self._bert_xform(line)
  File "/home/pengxiny/anaconda3/envs/mxnet-cpu/lib/python3.6/site-packages/gluonnlp-0.6.0-py3.6.egg/gluonnlp/data/transforms.py", line 1089, in __call__
    assert len(line) == 2
AssertionError
"""

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

Traceback (most recent call last):
  File "finetune_classifier.py", line 328, in <module>
    bert_tokenizer, task, batch_size, dev_batch_size, args.max_len, args.pad)
  File "finetune_classifier.py", line 314, in preprocess_data
    data_test = mx.gluon.data.SimpleDataset(pool.map(test_trans, data))
  File "/home/pengxiny/anaconda3/envs/mxnet-cpu/lib/python3.6/multiprocessing/pool.py", line 266, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/home/pengxiny/anaconda3/envs/mxnet-cpu/lib/python3.6/multiprocessing/pool.py", line 644, in get
    raise self._value
AssertionError

@pengxin99 you may need to install GluonNLP from master branch first. http://gluon-nlp.mxnet.io/install.html#install-from-github

@pengxin99 would you mind sending me the complete command to reproduce it?

@szha  Thanks and i think i run the script at the latest gluonnlp(use python setup.py install)
@eric-haibin-lin I list the env and run command below:
OS: CentOS Linux release 7.4.1708 (Core)
mxnet: pip install mxnet-mkl --pre
gluonnlp: python setup install (latest version)
finetune: GLUE_DIR=glue_data python finetune_classifier.py --task_name MRPC --batch_size 32 --optimizer bertadam --epochs 3 --lr 2e-5

I use the #708 to have a try, and it works well :)
thanks, @eric-haibin-lin @szha


Add seeding and testing of large thread.

Here is a first pass at seeding/testing large threads.
This code adds a Locust Task Set for:

Seeding a large thread.
Reading the large thread.

The seeding was implemented as a Locust Task Set which can be run as a separate test.  This enables the seeding to take advantage of the parallelism of Locust, and we can also compare seeding times.
Here's how to seed:
BASIC_AUTH_USER=XXX BASIC_AUTH_PASSWORD=YYY COURSE_ID=course-v1:edX+DemoX+Demo_Course LOCUST_TASK_SET=SeedForumsTasks LOCUST_MIN_WAIT=1000 LOCUST_MAX_WAIT=1000 locust -c 10 -r 1 -n 4500 -H https://discussions.sandbox.edx.org --no-web

Testing against a large thread just does repeated reads:
BASIC_AUTH_USER=XXX BASIC_AUTH_PASSWORD=YYY LARGE_TOPIC_ID=i4x-edx-eiorguegnru-course-foobarbaz LARGE_THREAD_ID=579f8b6948ee34412e000078 COURSE_ID=course-v1:edX+DemoX+Demo_Course LOCUST_TASK_SET=ForumsLargeThreadTasks LOCUST_MIN_WAIT=1000 LOCUST_MAX_WAIT=1000 locust -c 10 -r 1 -H https://discussions.sandbox.edx.org --no-web

I'll drops some comments in the code as well.
Reviewers (2 of the following):

[ ] @tobz
[ ] @pwnage101
[ ] @ormsbee
[ ] @dianakhuang

FYI: @andy-armstrong @bjacobel

@tobz @pwnage101: I made a pass at fixes.  Let me know if you have any required changes or how to get thumbs.  Thanks!

high level question: why even have a ForumsLargeThreadTasks task set at all if the ForumsTasks can cover large threads now?

@robrap

I'm not sure how to make this configurable.

In the usual way: shell variables.
Sorry I'm being critical, but why would you want the ability to crank up the ratio of one task (large threads)?  Do the results of that tell us anything new?  Why not just run the ForumsTasks with the ratios in this PR all the time?  Running the seed tasks would "configure" whether to test large threads or not.
Just making sure we don't add code where it isn't needed, but please correct me if I'm wrong.

@pwnage101: It's a reasonable question and what you say makes sense.  I think this is just an artifact of how I built this, where integration to the other tests at all was a last minute idea.
I'm going to adjust the ratio to 30 single : 25 large and remove the Large Thread Task Set.  I have a future task to look at load numbers during our peak, and may adjust again at that point.

@pwnage101: On a side note, Locust complains when you call interrupt() on the top-level Task Set, so I'm not sure of the best way to handle that for Task Sets that are sometimes run directly.  I guess instead we'd need LMS Task Sets with single sub-Task Sets, so it remains a sub-Task Set.

@pwnage101 @tobz: I added final fixes and adjusted weightings based on my research.  This is ready for review.  I haven't actually run the latest latest changes, but I plan to shortly with @tobz for our current round of load testing against the sandbox.

@pwnage101: Do you think we should move away from the hard coded course_data, and use the same call during setup of ForumsTasks to determine discussion ids?  I may do this is a separate PR.  Thoughts?

@pwnage101 @tobz: I did a big refactor in the last commit.

Moved to class variables.
Removed discussion_ids (topic_ids) from course_data and dynamically load at the start of a test.  This make it much simpler to run the ForumsTasks against different courses in different environments.

@pwnage101: FYI: Moving to class variables, I no longer need the global call.  However, it was originally needed to avoid the following error:
UnboundLocalError: local variable '_large_thread' referenced before assignment

@tobz @pwnage101: Sorry for the late commit (see above).  I'd like to see if I can get this merged before end of iteration (tomorrow morning), but that may not be possible.
FYI: @dianakhuang

👍

:+1:


Install pyCaffe

Hello and thank you for great effort
I wanted to ask whether pycaffe can be installed on Windows? Have you been able to do so? I couldn't find any documentation on installing the python wrapper after caffe is built and installed. It would be great if you could provide some guidance.

Actually I have try to compile pycaffe on Windows, but some errors always existed. I will check it soon.
Thanks!

Thank you. I am looking forward to it.


Error "t.datetimepicker is not a function"

I'm submitting a ...  (check one with "x")
[ X ] Bug report => search github for a similar issue or PR before submitting
[ ] Feature request
[ ] Other, please describe

Tell about your platform

eonasdan-bootstrap-datetimepicker version : 4.17.47
Vue.js version : 2.4.2
Browser name and version : Chrome|Firefox|Safari x.x.x
This package version : 3.0.0

Current behavior
Plugin is not working on module environment, console shows Error "t.datetimepicker is not a function"
Expected behavior
Plugin should show on module environment
Minimal reproduction of the problem with instructions
Clean installation in webpack module.
// at app.js
import moment from 'moment';
import datePicker from 'vue-bootstrap-datetimepicker';
import 'eonasdan-bootstrap-datetimepicker/build/css/bootstrap-datetimepicker.css';
Vue.use(datePicker);

const app = new Vue({
    el: '#app',
    components: {
        datePicker
    }
    data: function(){
      return { testdate: moment() }
    }
});

// at index.html
<body>
	<div id="app">
             <date-picker v-model="testdate"></date-picker>
        </div>
</body>

error in console

Are you sure you have jQuery installed ?
jQuery not gets automatically installed because of peerDependencies
Tip When you specify -
Vue.use(datePicker);

It means you are registering a global component, so you no need to specify local component.
I have setup  a jsfiddle demo for you -
https://jsfiddle.net/ankurk91/zupazg2u/4/
You can also take a look at examples and my webpack.config
Possibly it webpack configuration issue.

After testing at webpackbin i can implement your plugin without trouble. Maybe is as you say a webpack configuration issue

May be this can fix this ->
https://github.com/ankurk91/vue-bootstrap-datetimepicker/blob/master/webpack.config.dev.js#L71-L75
Feel free to re-open :smile:


Broken key "subnetwork_target_size " in run_parameters

https://github.com/NOAA-OWP/t-route/blob/0d512ba026e3b10a432fb707fc80655a6c2f63e2/src/python_routing_v02/compute_nhd_routing_SingleSeg_v02.py#L652
Extra space in key name breaks usage on the command-line.

@groutr -- this explains the failure with the profiling tests we attempted a few weeks ago.


What is the suggested way of setting ENV variables that are expected to show up in process.env?

I looked over the Shakapacker v7 guide as well as the example applications, but I didn't see any mention on how to set environment variables (i.e process.env.IMPORTANT_VAR) for a react application that rails also needs access to. Is there currently a prescribed approach to accomplishing this?

There shouldn't be any issue unless you are talking about a very specific feature. In this case, a detailed proposal can be a good start.


Update build scripts with better environment checks and build protobufs

Update the Makefiles to process dependencies correctly.
Update the python Makefile to build the protobuf files automatically
Add a number of environment checks to the rebuild script.
Make the rebuild script stop if the make fails.
Fix a couple of the tests.
Signed-off-by: Mic Bowman<EMAIL_ADDRESS>

@tkuhrt - We're stuck waiting for DCO again. Commits have signed-off by lines. Can you squash/merge this with this message:
Update build scripts with better environment checks; build protobufs

Update the Makefiles to process dependencies correctly.
Update the python Makefile to build the protobuf files automatically
Add a number of environment checks to the rebuild script.
Make the rebuild script stop if the make fails.
Fix a couple of the tests.
Add a check for a vaild CONTRACTHOME directory.

Signed-off-by: Mic Bowman<EMAIL_ADDRESS>


Emphasize importance of what we have done

Show that we are guiding the developer rather than describing.

Pushing this to the next milestone.


make --watch work with vim

Vim appears to move/rename the original file on save, resulting
in a  RENAME event from fsnotify. Reacting to this by re-adding
the original file name also catches two CHMOD (but no WRITE).
Not sure what's going on, but re-adding on RENAME and reloading
on CHMOD seems to do the trick.

Hey @mackorone, were you by any chance using vim when you ran into issue #16? I was able to repro this with vim on both ubuntu and macOS, but not with e.g emacs or echo >> in bash.
Not the most elegant solution, but seems to do the trick for now.

Yep, I was using Vim. Good catch!


False positive for some .dll files  when those .dll files in a folder

Reporting False Positives
When we used DependencyCheck CLI (v3.3.2) to scan ssleay.dll(1.0.2p)、sqlites3.dll(3.24.0) and libeay32.dll(1.0.2p)  it reports no vulnerabilities , but if we put those files in a folder and scan this folder ,it will report some vulnerabilities. And when we checked those vulnerabilities, all were false positives.
Example

{
  "reportSchema": "1.1",
  "scanInfo": {
    "engineVersion": "3.3.2",
    "dataSource": [
      {
        "name": "NVD CVE 2002",
        "timestamp": "27/09/2018 15:36:29"
      },
      {
        "name": "NVD CVE 2003",
        "timestamp": "27/09/2018 15:33:08"
      },
      {
        "name": "NVD CVE 2004",
        "timestamp": "27/09/2018 15:32:12"
      },
      {
        "name": "NVD CVE 2005",
        "timestamp": "28/09/2018 15:45:44"
      },
      {
        "name": "NVD CVE 2006",
        "timestamp": "28/09/2018 15:42:53"
      },
      {
        "name": "NVD CVE 2007",
        "timestamp": "28/09/2018 15:38:11"
      },
      {
        "name": "NVD CVE 2008",
        "timestamp": "20/09/2018 15:57:51"
      },
      {
        "name": "NVD CVE 2009",
        "timestamp": "20/09/2018 15:53:18"
      },
      {
        "name": "NVD CVE 2010",
        "timestamp": "20/09/2018 15:49:59"
      },
      {
        "name": "NVD CVE 2011",
        "timestamp": "29/09/2018 15:34:16"
      },
      {
        "name": "NVD CVE 2012",
        "timestamp": "21/09/2018 15:29:54"
      },
      {
        "name": "NVD CVE 2013",
        "timestamp": "27/09/2018 15:27:21"
      },
      {
        "name": "NVD CVE 2014",
        "timestamp": "29/09/2018 15:28:55"
      },
      {
        "name": "NVD CVE 2015",
        "timestamp": "28/09/2018 15:28:42"
      },
      {
        "name": "NVD CVE 2016",
        "timestamp": "29/09/2018 15:23:52"
      },
      {
        "name": "NVD CVE 2017",
        "timestamp": "29/09/2018 15:17:43"
      },
      {
        "name": "NVD CVE 2018",
        "timestamp": "30/09/2018 15:06:10"
      },
      {
        "name": "NVD CVE Checked",
        "timestamp": "30/09/2018 15:39:15"
      },
      {
        "name": "NVD CVE Modified",
        "timestamp": "30/09/2018 13:00:56"
      },
      {
        "name": "VersionCheckOn",
        "timestamp": "1538293155072"
      }
    ]
  },
  "projectInfo": {
    "name": "dependency_check",
    "reportDate": "2018-09-30T15:39:22.518+0800",
    "credits": {
      "NVD": "This report contains data retrieved from the National Vulnerability Database: http://nvd.nist.gov",
      "NSP": "This report may contain data retrieved from the Node Security Platform: https://nodesecurity.io",
      "RETIREJS": "This report may contain data retrieved from the RetireJS community: https://retirejs.github.io/retire.js/"
    }
  },
  "dependencies": [
    {
      "isVirtual": false,
      "fileName": "sqlite3.dll",
      "filePath": "D:\\dependency-check\\bin\\2\\sqlite3.dll",
      "md5": "413755c9fb41bc80d4c5b53b0b91aba7",
      "sha1": "ee5045f63dba589d03ae801986c0424a0ece6c4b",
      "sha256": "daf03da48d335cf54868af6563ef0a83eeb86b86e406a2ff58e5cb68abcfc94d",
      "evidenceCollected": {
        "vendorEvidence": [
          {
            "type": "vendor",
            "confidence": "HIGH",
            "source": "file",
            "name": "name",
            "value": "sqlite3"
          }
        ],
        "productEvidence": [
          {
            "type": "product",
            "confidence": "HIGH",
            "source": "file",
            "name": "name",
            "value": "sqlite3"
          }
        ],
        "versionEvidence": [
          {
            "type": "version",
            "confidence": "MEDIUM",
            "source": "file",
            "name": "version",
            "value": "3"
          },
          {
            "type": "version",
            "confidence": "MEDIUM",
            "source": "file",
            "name": "name",
            "value": "sqlite3"
          }
        ]
      },
      "identifiers": [
        {
          "name": "cpe:/a:sqlite:sqlite:3.22.0",
          "type": "cpe",
          "confidence": "LOW",
          "url": "https://web.nvd.nist.gov/view/vuln/search-results?adv_search=true&cves=on&cpe_version=cpe%3A%2Fa%3Asqlite%3Asqlite"
        }
      ],
      "vulnerabilities": [
        {
          "source": "NVD",
          "name": "CVE-2015-3717",
          "cvssScore": "7.5",
          "cvssAccessVector": "NETWORK",
          "cvssAccessComplexity": "LOW",
          "cvssAuthenticationr": "NONE",
          "cvssConfidentialImpact": "PARTIAL",
          "cvssIntegrityImpact": "PARTIAL",
          "cvssAvailabilityImpact": "PARTIAL",
          "severity": "High",
          "cwe": "CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer",
          "description": "Multiple buffer overflows in the printf functionality in SQLite, as used in Apple iOS before 8.4 and OS X before 10.10.4, allow remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors.",
          "notes": "",
          "references": [
            {
              "source": "CONFIRM",
              "url": "http://support.apple.com/kb/HT204941",
              "name": "http://support.apple.com/kb/HT204941"
            },
            {
              "source": "APPLE",
              "url": "http://lists.apple.com/archives/security-announce/2015/Jun/msg00002.html",
              "name": "APPLE-SA-2015-06-30-2"
            },
            {
              "source": "CONFIRM",
              "url": "http://support.apple.com/kb/HT204942",
              "name": "http://support.apple.com/kb/HT204942"
            },
            {
              "source": "APPLE",
              "url": "http://lists.apple.com/archives/security-announce/2015/Jun/msg00001.html",
              "name": "APPLE-SA-2015-06-30-1"
            },
            {
              "source": "SECTRACK",
              "url": "http://www.securitytracker.com/id/1032760",
              "name": "1032760"
            },
            {
              "source": "BID",
              "url": "http://www.securityfocus.com/bid/75491",
              "name": "75491"
            }
          ],
          "vulnerableSoftware": [
            {
              "software": "cpe:/a:sqlite:sqlite"
            },
            {
              "software": "cpe:/a:apple:mac_os_x:10.10.3",
              "allPreviousVersion": "true"
            },
            {
              "software": "cpe:/a:apple:iphone_os:8.3",
              "allPreviousVersion": "true"
            }
          ]
        },
        {
          "source": "NVD",
          "name": "CVE-2018-8740",
          "cvssScore": "5.0",
          "cvssAccessVector": "NETWORK",
          "cvssAccessComplexity": "LOW",
          "cvssAuthenticationr": "NONE",
          "cvssConfidentialImpact": "NONE",
          "cvssIntegrityImpact": "NONE",
          "cvssAvailabilityImpact": "PARTIAL",
          "severity": "Medium",
          "cwe": "CWE-476 NULL Pointer Dereference",
          "description": "In SQLite through 3.22.0, databases whose schema is corrupted using a CREATE TABLE AS statement could cause a NULL pointer dereference, related to build.c and prepare.c.",
          "notes": "",
          "references": [
            {
              "source": "MISC",
              "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6964",
              "name": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6964"
            },
            {
              "source": "MISC",
              "url": "https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1756349",
              "name": "https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1756349"
            },
            {
              "source": "MISC",
              "url": "https://www.sqlite.org/cgi/src/vdiff?from=1774f1c3baf0bc3d&to=d75e67654aa9620b",
              "name": "https://www.sqlite.org/cgi/src/vdiff?from=1774f1c3baf0bc3d&to=d75e67654aa9620b"
            },
            {
              "source": "MISC",
              "url": "https://www.sqlite.org/cgi/src/timeline?r=corrupt-schema",
              "name": "https://www.sqlite.org/cgi/src/timeline?r=corrupt-schema"
            },
            {
              "source": "BID",
              "url": "http://www.securityfocus.com/bid/103466",
              "name": "103466"
            }
          ],
          "vulnerableSoftware": [
            {
              "software": "cpe:/a:sqlite:sqlite:3.22.0",
              "allPreviousVersion": "true"
            }
          ]
        }
      ]
    }
  ]
}

Sorry about the delayed response.

Where can I download the specific files you listed above?
I am unable to replicate the problem of scanning a DLL directly as opposed to scanning the directory.  Can you provide the exact commands you used?

Hi ,
1.You can download sqlite3.dll from https://www.sqlite.org/download.html(Precompiled Binaries for Windows).
2. (1)dependency-check.bat --project dependency_check -n -o "D:\report\F2018120610242150452.json" -f JSON -s "D:/sqlite3"
The file sqlite3.dll in D:/sqlite3. This command reports some vulnerabilities which were all  false positives.
(2)dependency-check.bat --project dependency_check -n -o "D:\report\F2018120610204824066.json" -f JSON -s "D:/sqlite3.dll"
There is no vulnerability  when run this command.

I am unable to re-produce this using 5.2.2.  Running either scan on a mac (either pointing to a folder or the file itself) produces the same results.


Paper Clarification

@Robert-JunWang Hi
The paper points:
Residual prediction block make it possible for us to apply 1x1 convolutional kernels to predict the category scores and box offsets
Why can use 1*1 here?
The idea of the Residual Prediction Block comes from the paper: Residual features and unified Prediction network for single stage detection
in the code it provids, it is still 3*3.

That 1x1 is used to predict location and classes. You can use 1x1 in the original SSD too. But with ResBlock, the accuracy is almost same between 1x1 and 3x3.

many many thanks


Unable to Add and List Created Roles in Outbound Provisioning

Describe the issue:
There is no option to add and no listing of created roles in Outbound Provisioning, in Connectors.
Although the new UI provides a list for roles, the created roles are not appearing in the list, and it is not possible to add roles using the provided "+" option.
In the management console, the same feature requires users to type the role, but in the new UI, it is expected to be a list.
outboundprovisionrole_issue.webm
How to reproduce:

Navigate to the Outbound Provisioning section in the new UI.
Observe that the list of created roles is not displayed.
Attempt to add a role using the provided "+" option and observe the issue.

Expected behavior:
The new UI should provide a list of created roles in the Outbound Provisioning Connectors, and users should be able to add roles using the provided "+" option.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: wso2is-7.0.0-beta4-SNAPSHOT
OS:Mac
Database: DB2
Userstore: JDBC

This is fixed and verified in wso2is-7.0.0-beta5-SNAPSHOT

still reproduce a particular issue  with a "tenanted path."

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


presubmit-lab-testing job broke

kubevirt-tutorial-presubmit-lab-testing-k8s-1.13.3 is statically set to k8s 1.13.3.
We're now getting job failures.  See failed #118 pull/118 and see link

/assign

Fixed in https://github.com/kubevirt/kubevirt-tutorial/pull/120


Items popping out of pipes

Why are items popping out of pipes when using diamond pipes for example?

I'm experiencing the same issue. The items are popping out of the pipes if the connected container is full. This seems like the logic for the diamond extractor is calculating the available space for the adjacent container incorrectly. Every time a few items are removed from a full container, extractors from other connected containers extract more items than there is space available in the target container, overflowing it and causing the additional items to drop.
So far, my only "fix" has been to set the extract item amount down to 1 item, so when an item pops out, it doesn't eject a whole stack or so. IMO, this really needs to be fixed. The issue kinda makes the mod completely unusable, if you want to transport items in any way. And when it is implemented as the only pipe system in mod packs like the new FTB Direwolf20 1.16, with no other alternatives other than Mekanism pipes, then, for me personally, it makes the whole mod pack sort of unplayable.

I'm experiencing the same issue. The items are popping out of the pipes if the connected container is full. This seems like the logic for the diamond extractor is calculating the available space for the adjacent container incorrectly. Every time a few items are removed from a full container, extractors from other connected containers extract more items than there is space available in the target container, overflowing it and causing the additional items to drop.
So far, my only "fix" has been to set the extract item amount down to 1 item, so when an item pops out, it doesn't eject a whole stack or so. IMO, this really needs to be fixed. The issue kinda makes the mod completely unusable, if you want to transport items in any way. And when it is implemented as the only pipe system in mod packs like the new FTB Direwolf20 1.16, with no other alternatives other than Mekanism pipes, then, for me personally, it makes the whole mod pack sort of unplayable.

Can confirm this as well, even with the basic pipe. It seems it doesn't remember that it already sent items to the storage, it keeps sending till its full. But it should already stop sending items when it should be full, when the last batch arrived.
My setup is fairly simple:
4 Furnaces connected at the back (fuel slot) to a chest with sapplings/sticks using basic item pipes and basic extractor.
Maybe its also related as the sticks/sapplings burn quickly, so the inventory gets updated often.
So it detects 56 sticks in the furnance and start sending one batch of sticks.
Then a stick is burned, but the 8 sticks send before didn't arrived yet, so its 55 sticks in the furnace and so it sends another batch as it didn't remembered there are already 8 sticks on the way.
So it should wait till 48 sticks are in the furnace to send another 8 sticks or the already sent items arrived and its below 56 again.
As you need to keep track of all stuff already on the way maybe as a quickfix instead of poping it out, it just sends the stuff back to the sender?

Can confirm this as well, even with the basic pipe. It seems it doesn't remember that it already sent items to the storage, it keeps sending till its full. But it should already stop sending items when it should be full, when the last batch arrived.
My setup is fairly simple:
4 Furnaces connected at the back (fuel slot) to a chest with sapplings/sticks using basic item pipes and basic extractor.
Maybe its also related as the sticks/sapplings burn quickly, so the inventory gets updated often.
So it detects 56 sticks in the furnance and start sending one batch of sticks.
Then a stick is burned, but the 8 sticks send before didn't arrived yet, so its 55 sticks in the furnace and so it sends another batch as it didn't remembered there are already 8 sticks on the way.
So it should wait till 48 sticks are in the furnace to send another 8 sticks or the already sent items arrived and its below 56 again.
As you need to keep track of all stuff already on the way maybe as a quickfix instead of poping it out, it just sends the stuff back to the sender?

Duplicate of #5


Clone repository

Describe the bug
Hi my friend. Recently the last version is not working as well as pre version. I can't clone any repository. It's not only don't work on phone but on PC have same problem.
Relevant errors (if available) from notifications or console (CTRL+SHIFT+I)
No response
Steps to reproduce
Clone
Expected Behavior
No response
Addition context
No response
Operating system
Windows
Installation Method
None
Plugin version
2.28

Please update to the latest version I released just some minutes ago.


Nest supplier agreements table to apply custom scss only there

Looks like the main scss summary-item-field-* classes were overridden in order to style a single table.
I've nested this table and applied the scss styles only to that nestings child elements. This seems like a better way for now and won't affect every single summary table in the admin.
Before:

After:

Interesting thought.
So it looks like it gives the summary-item-field elements a bit more room. However, the summary-item-field-first is playing by its own rules because it has its own summary-row and that's what the 16.666 is a percentage of.
The parent summary-rowof the summary-item-field-first is inexplicably wider than the parent summary-rowof the 5 summary-item-fields

I changed it though because I think the names and numbers better reflect what we're trying to do.


Key vault get started authorize using the azure portal

This change adds a description on how to authorize an application to use keys and secrets in Key Vault using the portal. I made it after spending way too much time on installing and using Azure PowerShell to do it.

@barclayn - Would you review the proposed changes and add a sign-off comment if approved? Thanks

the changesets you really need are those titled "Update key-vault-get-started.md". the others are just merges from your repo to mine.

Merging per Angela's approval email.


add credential resources

Add the credential resources to the ssclj server.  The core implementation can be taken from the OCCI connector and moved into the main server.  The types of credentials that should be implemented initially are:

[ ] ssh public keys
[ ] ssh private keys (with reference to public key)
[ ] username, hashed password pair
[ ] username, clear password pair

The proxy credentials from OCCI should be left out of the main server and only used with the OCCI connector.

Appropriate credentials resources have been added.


Update resolvePageComponent helper to work with both glob and glogEager

This pull request updates the resolvePageComponent inertia helper to work with the object returned both by the glob and globEager imports.

Hi @Esirei, thanks for the PR!
Could you please explain the use case and benefit of this?

Hi @Esirei, thanks for the PR!
Could you please explain the use case and benefit of this?

Hello @jessarcher , unlike the glob import which compiles each page/component/js into separate files and requests them on demand (lazy loaded), the globEager import compiles all into a single app.js file. Of course this will have a slower initial website load, but faster page responses, it depends on the developer which tradeoff they want.
This PR updates the helper function to work with either technique, I just need to figure out how to tell typescript that the generic cannot be a function to fix the failed tests.

Thanks, @Esirei. That makes sense :+1:

Hi @jessarcher, I finally had some time to get the issue out of the way, also added tests for the helper.

Thanks, @Esirei!


Using Spacy instead of Jieba for chinese text segmentation

Description
Using Spacy instead of Jieba for Chinese text segmentation
Reference: CV2-5247
How has this been tested?
Locally and added unittests
Are there any external dependencies?
Spacy

The code for switching over looks fine, but I wouldn't want to merge it in yet unless we've done some sort of comparison (perhaps you already did?).   We could dump some example text from piyaoba workspace and compare results side by side?


Merge pull request #1 from themikenicholson/master

Update

Not sure you meant to open this... it doesn't change any files.

Sorry, it's a error when I was update my fork .


Does async work in IE11? (slow performance with React)

I have a code block that is taking ~10 seconds to highlight, and when I use the following code (using async set to true) I can't scroll the window while the highlighting takes place.
    let now = performance.now();
    Prism.highlightElement(code, true, () => console.log(performance.now() - now));

I think the reason IE11 takes so long might have something to do with React (currently using v16.4.0).
The "set innerHTML" row for the first load is 57ms, and the reload is 10.45s.
Performance trace from IE11 on first load of the page with highlighting:

Performance trace from IE11 on a reload of the page with highlighting:

The JavaScript call stacks of a different, but also slow, render. It looks like _self.Prism.highlight (and subtree) doesn't take much time, and the culprit lies somewhere else within _self.Prism.highlightElement - probably the assignment to innerHTML if we use the previous chart as evidence (https://github.com/PrismJS/prism/blob/435eb2e6cd94948627b044255aab7605235bdfa5/components/prism-core.js#L261..L270).

I created a fiddle as an example
https://jsfiddle.net/fiddlegrimbo/vhgj510p/20/show
Consistently highlights the HTML in ~500ms on IE11.  So there is something going on in my webpack/React code to slow the highlighting down.

Definitely related to innerHTML, based on your charts, but if you get it @ 500ms consistently normally, but 10s when used w/ React / Webpack, that would suggest it's something about the interaction between those two that's causing the issue. I'll leave this open for other to weigh in, but I'm not sure we can do anything on our end.

Thanks for your reply.
I'm starting to suspect IE11 devtools now. I restarted IE11 and did not open devtools, and both my vanilla test of Prism and my React app are highlighting quickly.
When I open devtools it slows to a crawl.
This slowdown can be reproduced using the test page, https://prismjs.com/test.html, and the content of this gist, https://gist.github.com/gitgrimbo/3ae03923ae1fb3b4865895c07a6e65f2#file-html-html.
When IE11 devtools is not open, this highlights for me in less than a second. With devtools open, it highlights in ~9 seconds.
So in summary I don't think this is a real issue with Prism, although it might be interesting to know why IE11 devtools could cause such a slowdown.

Performance profiling itself can cause slowness, as it has to instrument the code in a way that can impact how fast it runs, but that's the first time I've seen the impact be that large. Admittedly, I'm not entirely surprised IE11's devtools aren't great.

Alright, I think we're ok to close this then, but if you find an issue here we should look it, please reopen. Thanks!


Bug bounty (200€ per problem)

Hi there! :)
I´m working on a larger project and encountered some show-stoppers. I will pay anybody who can fix one or more of these problems until the 4th of November 200€ per problem.
Problem 1: You have to click textfields over and over again: https://github.com/openfl/openfl/issues/1285
Problem 2: Multiline textfields don´t work properly: https://github.com/openfl/openfl/issues/1254
Problem 3: Cursor issues at password fields: https://github.com/openfl/openfl/issues/1316
Thanks a lot in advance,
Jan

I assume you mean the 4th of November, it's almost the end of October :)

You´re right, I fixed that! :)

Isn't #1316 solved already ? @ibilon says he can't replicate.

@ibilon, well, I guess this issue can be closed, all bugs are fixed (including #1316)

Not sure if #1254 is really fixed, tried on my home computer and it looks like it adds two new lines.

Seems like I worked with an outdated version - I´m sorry! I´ll check all 3 problems with the latest version and get back to you if everything works now.

@PlayaJan, try develop-version, it contains fixes for the first and second issues, they are not officially released.

@ibilon now it's totally complete :-)


[FeedItems, Server]: Prepare Server Part of the epic

FeedItem Model
API to get FeedItem through
First attempt to add Updates

FeedItem table: id (uuid), channelId (uuid), body (jsonb), createAt(timestamp), updatedAt (timestamp).
AgentFeedItems table: id (uuid), agentId, channelId, readAt, createdAt, updatedAt

Don'y add type(enum ACTION_REQUIRED, INFO, NONE), we may change it later. Also, I'm not sure if we need AgentFeedItems yet or at all (if we show based on the last time they've seen a list)

Sure, ok


Wrong tags for composer

When trying to update to 2.8 its get overwritten by 2.52 because 52>8
Perhaps you can remove the tags and retag as 2.5.2 and 2.5.1 ?

Yeah, I guess I messed up the versioning. I did as you suggested and retagged the commits for 2.51 and 2.52 as 2.5.1 and 2.5.2 then I deleted the old tags and releases. Hopefully nobody was using 2.51 an 2.52 specifically. I'm not sure why Packagist is still showing 2.52. Maybe it just hasn't caught up yet.
I'll stick with semantic versioning from now on.

Yeah it still wants to install 2.52, so packagist needs to be informed/changed as well.

I think it's good now. I logged into Packagist and deleted 2.52. I don't know why I had to do that because the 2.51 and 2.52 tag no longer exist on GitHub and 2.51 disappeared from Packagist automatically.


merge from konsum-frontend-svelte

package.json

chore(deps): add ^10.7.7 remove ^10.7.6 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.31.18 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.31.18
GitHub release

Your semantic-release bot :package::rocket:


chrore: fix license

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


THREE's renderer and scene could be represented as nodes

Currently the camera creates its own renderer, and every node is added to the same scene. Having dedicated nodes for each would allow to:

more easily change the parameters of a renderers
choose which scene an object is added to, which could help doing post processing after having rendered multiple scenes

a Renderer node context has been added: https://polygonjs.com/docs/nodes/rop. It is currently possible to create a WebGLRenderer node, and edit the same parameters as the THREE.WebGLRenderer. There is also a Css2DRenderer to add HTML labels.
The rendered scene can be set as a parameter on the camera node, such as on the PerspectiveCamera or OrthographicCamera.

a Renderer node context has been added: https://polygonjs.com/docs/nodes/rop. It is currently possible to create a WebGLRenderer node, and edit the same parameters as the THREE.WebGLRenderer. There is also a Css2DRenderer to add HTML labels.
The rendered scene can be set as a parameter on the camera node, such as on the PerspectiveCamera or OrthographicCamera.


*: Add docs for configuring tracing.

Since tracing now requires config or config-file we need to have docs for it before 0.6.0

cc @aditya-konarde when we configure this for our stack, do you mind adding some docs around this?

(similar to https://thanos.io/storage.md/ with autogen)

Crosslinking https://github.com/thanos-io/thanos/issues/1339#issuecomment-513309527 for a point to get started with jaeger documentation.


Unclear error when IMG_UPLOAD_FOLDER env value is missing

When IMG_UPLOAD_FOLDER enviroment doesn't present, there is an error on POST /test-runs
{
  "path": "/test-runs",
  "name": "TypeError",
  "message": "The \"path\" argument must be of type string. Received undefined",
  "exception": {
    "code": "ERR_INVALID_ARG_TYPE"
  },
  "stack": "TypeError [ERR_INVALID_ARG_TYPE]: The \"path\" argument must be of type string. Received undefined\n    at validateString (internal/validators.js:120:11)\n    at Object.resolve (path.js:980:7)\n    at StaticService.ensureDirectoryExistence (/dist/shared/static/static.service.js:60:41)\n    at StaticService.getImagePath (/dist/shared/static/static.service.js:56:14)\n    at StaticService.saveImage (/dist/shared/static/static.service.js:27:33)\n    at TestRunsService.create (/dist/test-runs/test-runs.service.js:174:46)\n    at TestRunsService.postTestRun (/dist/test-runs/test-runs.service.js:56:36)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)\n    at async /node_modules/@nestjs/core/router/router-execution-context.js:46:28"
}

It's unclear by the text of the error what is wrong. Should check for env existence first.

env param is gonna be removed in 4.7.0 release in scope of
https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/issues/160


Fix all compile warnings

Ideally, one should fix all the compile warnings. Especially all "obsolete" warnings in the CADabilty code base itself should be solved by shaping CADability legacy code into the desired patterns as a migration reference for other contributors.

Would it be helpful if I started tackling some of the easy ones? I looked through a handful of them and it looks like most of them are unused fields, events, and variables that date back to the first commit.

That would be helpful, but please don’t spend too much time on it.
I believe there are larger priorities to focus on.

It's really just an excuse to dig into the codebase and learn more about it. I have a couple big projects in the works that I'll be using this for so I'd like to contribute but I don't have a ton of experience collaborating with other programmers so I'd like to ease into it. Cleaning up unused variables seems like an easy win and I can learn more about the structure and do some translations in the process.

Your help is really appreciated. Thanks a lot for spending time on this project.

As the one who opened this: removing private variables is fine. Doing more, especially working on the [obsolete] parts gets tricky quickly. The code base is half-way trough a refactoring which was never finished. That said, any decrease in warnings is highly appreciated.
We ourselves might be able to contribute a substantial rewrite of the UI and rendering parts down the line, splitting Math and UI entirely. I really want to see this fly.

[ ] CS DialogDebuggerVisualizer.DialogDebuggerVisualizer()' is obsolete: 'Visualizers that target Visual Studio 17.6 or newer should use the other DialogDebuggerVisualizer overload and use a non-legacy formatting policy for improved security. #192
[ ] Remove unused fields CS0169
[ ] Remove unused variables CS0219
[ ] Fix CS0219 The variable is assigned but its value is never used
[ x] Fix CS0162 Unreachable code detected

Fixing these issues shouldn't have a big impact on the program itself and are easy to fix.

[ ] CS0618 Remove obsolete properties.
This is going to be hugh. Every single Property/Function has to be checked.

Is the replacement working properly?

Are there parts of the program that still rely on this Property/Function?

We should probably create an issue and PR for each single Property/Function that will be replaced.
12th Dec - 970 Warnings


Add model caching for Stable Diffusion

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Currently the Stable diffusion model is directly fetched from HuggingFace and adds to the latency of the inference.
It would be good to download the model and load it from a storage like S3.
Describe the solution you would like
Update the instructions to download the model from Hugging Face.
Store the model in S3 or any other storage.
Load the model from the storage during inference.

Describe alternatives you have considered

Additional context

I would like to work on this

Using S3 mountpoints and NVMe local storage for storing ML models, it can save cold start times

Thanks @lindarr915; assigning to you. Looking forward to the PR!


Merge 3.12.x into 3.13.x

Issue
NA
Description
Merge 3.12.x into 3.13.x with a dedicated PR as it's the first merge after moving the Gateway inside the monorepo

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.


[BUG/DOC] Agent Download Bug or Confusing Docs

We were running this agent command:
buildkite-agent artifact download --build "0188348b-27ee-42dd-81c4-e43bb25f6df0" shared/shopper-delivering/impl/build/outputs/apk/androidTest/debug/impl-debug-androidTest.apk tmp/

I would expect this to put the file including subfolders under tmp/shared.shopper...etc but it doesn't.
I'm not actually sure where it goes, even after ls -l tmp/ it's empty.
We had to resort too:
- buildkite-agent artifact download --build "0188348b-27ee-42dd-81c4-e43bb25f6df0" shared/shopper-delivering/impl/build/outputs/apk/androidTest/debug/impl-debug-androidTest.apk .
- mv shared/shopper-delivering/impl/build/outputs/apk/androidTest/debug/impl-debug-androidTest.apk tmp/impl-debug-androidTest.apk

Not sure if this is a bug or bad docs for expected behavior ?

Hi @chrisjenx, this does look a bit unusual. You might get more detail by passing --debug flag to your command
buildkite-agent artifact download --debug --build "0188348b-27ee-42dd-81c4-e43bb25f6df0" shared/shopper-delivering/impl/build/outputs/apk/androidTest/debug/impl-debug-androidTest.apk tmp/

We agree this is could be something to fix, but as there is a workaround, it's not our highest priority at the moment.
You're also welcome to contact<EMAIL_ADDRESS>

I checked the debug and it outputs what it suggests that it should be
doing. So I'm guessing it's failing silently after the debug statement
On Tue, May 23, 2023 at 8:05 PM Narthana Epa @.***>
wrote:

Hi @chrisjenx https://github.com/chrisjenx, this does look a bit
unusual. You might get more detail by passing --debug flag to your command
buildkite-agent artifact download --debug --build "0188348b-27ee-42dd-81c4-e43bb25f6df0" shared/shopper-delivering/impl/build/outputs/apk/androidTest/debug/impl-debug-androidTest.apk tmp/
We agree this is could be something to fix, but as there is a workaround,
it's not our highest priority at the moment.
You're also welcome to contact @.***
—
Reply to this email directly, view it on GitHub
https://github.com/buildkite/agent/issues/2099#issuecomment-1560357152,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI5DMO26QEKUFMFYZEQ6JDXHVUFZANCNFSM6AAAAAAYH6N3ZE
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Reporting - API] Add method to determine breakdown of customer browsers/timezones/OS's

Problem
Users should be able to see a breakdown of their customers' browser/OS/timezone in the Reporting Dashboard
Solution
Let's create a method in the Reporting context (https://github.com/papercups-io/papercups/blob/master/lib/chat_api/reporting.ex) that counts the number of customer browsers/OS's/timezones for a given date range.
Basically this just means grouping the customers table by a given field (e.g. :browser/:os/:time_zone) and counting the number of occurrences.
The method might look something like:
def get_customer_breakdown(account_id, field, filters \\ %{}) do
  # `field` will be `:os`, `:browser`, `:time_zone`, etc (fields on the Customer model)
  # `filters` should include a `from_date` and `to_date`
end

The response should look something like this:
get_customer_breakdown(account_id, :browser, %{from_date: ..., to_date: ...})
# =>
[
  %{browser: "Chrome", count: 25},
  %{browser: "Firefox", count: 12},
  # etc
]

Testing
Please add tests to test/chat_api/reporting_test.exs and make sure they pass with mix test :)
Context
See https://github.com/papercups-io/papercups/issues/252
Questions, or need help getting started?
Feel free to ask below, or ping us on Slack :)
(You can also check out our CONTRIBUTING.md)

You can assign this to me.

hey @shivamls -- any updates?

Does it make sense for me to pick this up? It looks stale.

yup go for it @eikooc :)

@reichert621 I have created a draft pull request at #361. I couldn't for the life of me figure out how to make the field an atom or what is needed to make the key of the map dynamic based on the field given as input, so I chose to go with a generic name called field for now. If you can help me, then it would be appreciated :)

hey @eikooc! thanks for the draft PR :) i'll take a look later, but in the meantime if it's easier feel free to use use Enum.map to convert :field to the name of the field (e.g. :browser)


Support phantomjs 2.0

I tried to upgrade to phantomJs 2.0 here https://github.com/netronixgroup/phantomjs-gem/tree/upgrade-to-2.0.0.
Several specs fail, I'm not familiar with the codebase. Can you help to upgrade it to support 2.0?

+1

+1

+1

+1

+1

Looks like this will have to wait until PhantomJS themselves get the static Linux binaries working. See https://github.com/ariya/phantomjs/issues/12948

+1

+1

+1

:+1:

https://github.com/gitromand/phantomjs/releases - available phantomjs-2.0.1-development-linux-x86_64.zip

@dmitry I don't think this gem should use binaries not sanctioned by upstream (you linked to a forked repo).

@betelgeuse thank you for noticing that. Lets wait till the upstream binaries will appear.

+1

Guys, just to understand: what means +1?
Is it's something like:

please implement, but I cannot help you anyhow"

Or there are some other meaning of such comments?

@dmitry It's like Facebook like or the vote functionality in bugzilla. Since Github does not have native support for it, many people have taken to using +1 to signal importance. I am not sure what my personal opinion on such comments is given the current Github feature set.

+1

The main PhantomJS repo builds its binaries from the deploy page page for both Linux and Mac OSX. They have prebuilt it for Mac on their download page. For Linux, but have one remaining issue 12948.

+1

The official 2.1.1 version is out, with official Linux binaries.

Finally, excellent! Would you mind sending in a PR with the updated urls?
On Mon, Jan 25, 2016 at 1:13 PM -0800, "Tamás Sallai"<EMAIL_ADDRESS>wrote:
The official 2.1.1 version is out, with official Linux binaries.
—
Reply to this email directly or view it on GitHub.

Yep, just opened #66 .

Please close this in favor of #66.

We need a new release <IP_ADDRESS> on rubygems

@mgrachev The build on travis CI was failing, it is now fixed with #68 - I will ship the new release in a few minutes.

@colszowka Thanks!


Implement Weak References

👋 Just came across this project, looks really good!
Can you give a bit more info on what Weak References is about?


Deployment-settings.yml file not being recognized

Problem Description
In the section on Runtime Settings, the following is written:
The runtime settings are configured in deployment-settings.yml that is in the directory from where the GitHub app is running.
In the section on Pull Requests, the following is written:
The checks will fail if org-level branch protections are overridden at the repo or suborg level with a lesser number of required approvers.  This second statement mentions nothing about the deployment-settings.yml file.
In any event, I have tried running safe-settings with the deployment-settings.yml file in both the admin directory and in the same directory where I am executing the docker-compose command.
In deployment-settings.yml, if a repo-level .yml file tries to lower the number of required approvers to less than what is set at the org-level, an error should be thrown.
What is actually happening
None of the settings in deployment-settings.yml are being recognized.  The safe-settings check is passing.
What is the expected behavior
An error should be thrown.  I would expect the safe-settings check to fail and prevent the PR from being merged.
Error output, if available
No error output.   Safe-settings check passes.  No evidence that deployment-settings.yml is being recognized at all

@JDunnUKG Does your deployment settings file look similar to this?

The problem was not in the deployment-settings.yml file itself, but that the Docker container running safe-settings could not see it. We resolved this issue by adding a line to the Dockerfile to copy deployment-settings.yml into the container, and setting the DEPLOYMENT_CONFIG_FILE environment variable in the .env file to the location of where the deployment-settings.yml file was copied.


accept objects, not only strings in set()

@rultor release, tag is 0.5.0

@rultor release, tag is 0.5.0

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.5.0

@yegor256 Done! FYI, the full log is here (took me 8min)


[BUG] Doctrine Metadata Cache lifetime should not be passed as null

Signature of \Doctrine\Common\Cache\Cache::save does not accept null (https://github.com/doctrine/cache/blob/6f9810e194acace22e360a1398cf228132e5b4b2/lib/Doctrine/Common/Cache/Cache.php#L55) and pass lifetime as null null works not properly on different cache implementations.
For instance, on \Doctrine\Common\Cache\PhpFileCache.

I guess this came from https://github.com/doctrine/cache/blob/67d7149abee291a92591f0c31cd925f8b52cb745/Cache.php#L59 not sure when this happened

@svycka may be it is time to merge this PR? This repository use a new version of doctrine/common in composer.json.

@andrey-bondar-dron Thank you for the PR!
You've labeled this a bug - is there a specific error or unexpected result occurring from this? Anything we can add a test against?

@AkenRoberts Hi!
When https://github.com/doctrine/cache/blob/master/lib/Doctrine/Common/Cache/PhpFileCache.php is using as doctrine metadata cache, it assumes, that lifetime cannot be null (as in interface) on https://github.com/doctrine/cache/blob/master/lib/Doctrine/Common/Cache/PhpFileCache.php#L112 and has unexpected behavior.
I have viewed all implementations in https://github.com/doctrine/cache/tree/master/lib/Doctrine/Common/Cache and they all expect lifetime as integer.
Anyway, interface does not accept null and client code should not pass it (in order to prevent code smells =))

I'm concerned, perhaps unnecessarily, about how changing the default might modify current behavior. Because of that, and how I'm trying to deprecate the 2.4.x branch in favor of a cleaner 3.0, I've implemented this change in master via 3a3af134e00d7b7d72a7a59c4c3cfe400ccdd91d.
Thank you for the contribution and approval. Keep it up!


Send/receive screens improvements

"send all" rename to "add all", make less attention to the button?
“paste address or find contact” rename to "send to"
"annotation" rename to "comment"
"category" rename to "tag"
"contacts"/"addresses" tabs - make tappable area bigger
"existing addresses", "addresses" rename to "my active addresses"
addresses/contacts view update to addresses/contacts screens (multi-categories, expiration date, etc)
add hint about "local comment" in input field, remove "won't be shared" from comment's header
remove first sentence on receive screens annotation ("Send this address over...")

Updated screens are here:
send https://app.zeplin.io/project/5c73dc8aa74b4b4085a86a91/dashboard?seid=5ce239536c73511dec2404fa
receive https://app.zeplin.io/project/5c73dc8aa74b4b4085a86a91/dashboard?seid=5ce2394739f2e51e01fd8c6f

"won't be shared"  is not removed from transaction comment on SEND screen.
STR

Wallet > SEND > tap on TRANSACTION COMMENT
ER: hint "Local comment".
AR: hint "Won't be shared"

discussed with @alexandrashelenkova
we leave the current text

tested
app: testnet v2.4.24
phone's model: iPhone XR


Fibonacci Search

Algorithm name
Fibonacci Search
Programming language

[ ] C
[X] C++
[ ] Java
[ ] Python

Additional context (OPTIONAL)
searching a particular element in the given list using the Fibonacci Search algorithm.

@deephunt3r can I do this in C language?


CATALOG-160 use query string parameter to transmit suggestion text

https://socrata.atlassian.net/browse/CATALOG-160
use query string parameter to transmit suggestion text
also updated socrata-sbt-plugins and replaced any instances of JavaConversions

Build failed.

spandex #382 FAILURE
Looks like there's a problem with this pull request

spandex #383 SUCCESS
This pull request looks good

This build looks good.


_WD_ElementSelectAction() refactoriong needed

If $iErr = $_WD_ERROR_Success And $sNodeName = 'select' Then
I will do this in a future.

I don't understand what you intend to change here. Please explain.

I will do this in a future.

currently this is just a reminder

I'm trying to understand why it needs refactoring. Is there an issue with the line of code you posted above? What's wrong with the function's current code?

currently there is:
$sNodeName = _WD_ElementAction($sSession, $sSelectElement, 'property', 'nodeName')
	Local $iErr = @error

	If $iErr = $_WD_ERROR_Success And $sNodeName = 'select' Then
........
........
........
........
	Else
		$iErr = $_WD_ERROR_InvalidArgue
	EndIf

In this way you are getting only one kind of @error .... $iErr = $_WD_ERROR_InvalidArgue
I think this should works in this way:
	Local $iErr
	$sNodeName = _WD_ElementAction($sSession, $sSelectElement, 'property', 'nodeName')
	If @error Then
		$iErr = @error
	ElseIf $sNodeName <> 'select' Then
		$iErr = $_WD_ERROR_InvalidArgue
	Else
		..........
	EndIf

Ok. It would have been helpful if you had included some additional details when you original opened the issue. That way we can understand what you are intending to change and can comment if needed. 😄

All is done in https://github.com/Danp2/WebDriver/pull/165


Proposal: --no-color option with docker -d

Currently we're using AWS CloudWatch logging and it's kind of annoying as the logs look like this:
INFO[134448] GET /containers/json?all=1&filters={%22status%22:%5b%22restarting%22%5d}&limit=100
I know I could work some magic and remove the color codes, but it'd be nice if docker -d had an option like docker-compose's --no-color to provide stdout/stderr w/o color.

Makes sense

On the subject, I also think the logging format needs to be consistent. Right now the output is radically different based on whether STDOUT is a TTY or not. Using color when connected to a TTY I can understand, but why change the format?

@phemmer we can ask @Sirupsen :)

@phemmer that's the Logrus defaults for opinionated reasons. I like that format a lot when working locally, but it's not really meant for production usage where the non-coloured key/value is more appropriate.

@Sirupsen :+1: logging out in JSON (or at least the option to) would be nice.

Making the default the key-value pairs would probably be ideal. This is still easy to parse by humans. A custom formatter could also be written, but I don't think that's necessary right off the bat. In /etc/default/docker we could allow configuring to the JSON logger.

@Sirupsen been a while on this one, any chance of getting this in?


Added Security.SetMarket

This enables users to download, convert and use data from providers currently unsupported by Lean (e.g. Oanda, Alpari, etc.)
The location of the custom data is, as usual, \data-folder\security-type\market\resolution\symbol...
Usage example, in algorithm Initialize():
AddSecurity(SecurityType.Forex, "EURUSD", Resolution.Tick);
Securities["EURUSD"].SetMarket("Alpari");

Cool thanks @StefanoRaggi  :) We're actually just about to clean that up now to merge "Country Code" and "Liquidity Provider" into one concept -- "Market". This way we can minimize the variables and switching and its a more generic idea.
Give me 30minutes and I'll commit the new Markets build.

@jaredbroad Ok. I'll wait and adapt the code to the new commits.

Thanks for the PR @StefanoRaggi, its a good addition


Add colgroup to DataTableV2 for styling cols

some times, we need the ability to customize style by columns.
so, It is better have colgroup in DataTableV2 to identify different columns.

Hi 👋 thank you for reporting! Sounds that we need to better understand the underlying requirement. We have issue template for good reasons - Great if you can follow the template. Thanks!


ci: add cancel-previous-workflows.yaml

Description

As written in https://github.com/autowarefoundation/autoware.universe/pull/1669, sometimes CI execution will be jammed.
To resolve this, I'd like to introduce this option.
https://github.com/styfle/cancel-workflow-action#advanced-all-but-latest

Because this action can only cancel workflows if it is actually being run, it only helps if the pipeline isn't saturated and there are still runners available to schedule the workflow.
By default, this action does not cancel any workflows created after itself. The all_but_latest flags allows the action to cancel itself and all later-scheduled workflows, leaving only the latest.

Also, since it's not limited to build-and-test, I try splitting the workflow.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Seems working correctly: https://github.com/autowarefoundation/autoware.universe/actions/workflows/build-and-test-differential.yaml


Bso bonus exp is wrong.

🐛 Bug Report
Write a description of the bug here, give all the information you can about what it is, how it happened.
kiina finished fighting Tempoross 2x times. You received 152,210 :fishing: XP (421k/Hr)
Fishing Bonus XP: 742
i think that fishing bonus exp should be +1k.
this was in bso, not sure if other bonus exps are wrong too.
this was with full spirit angler, which according to osb should give: 2.5% - Full outfit equipped in skilling setup meaning that bonus exp should be nearer 2.5k rather than 742.

I think the bonus xp is applied on the initial xp. And in BSO there is a xp multiplier of 5. Hence why you get 5x less than expected.


Set up AES-128 encryption section not up-to-date.

[Enter feedback here]
In the Set up AES-128 encryption section, the issue with encryption and HLS/DASH CMAF content, which are not playable  has been closed as it has not had recent activity. Thus this page needs to an update accordingly.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d6b24bd7-0e23-9060-f4ec-03b9dd9b330d
Version Independent ID: 75e979bf-a151-7b4f-c953-9948ab5eb020
Content: Use the Video.js player with Azure Media Services - Azure Media Services v3
Content Source: articles/media-services/latest/player-how-to-video-js-player.md
Service: media-services
Sub-service: rest-v3
GitHub Login: @IngridAtMicrosoft
Microsoft Alias: inhenkel

The Video.js team closed it, but We are actively working on a fix for browser based AES-128 Clear Key encryption support this semester and will update this once that feature is completed.  Client should not need to fix this, as we can resolve it on the service side.

I removed the link to the issue for now.

#please-close