InfluxDB grows out of proportion

Describe the bug
I connected speedtest-tracker to influxDB like this:

After a year and a half, this bucket is 39G of size.
I did some diagnostics:
docker exec -it influxdb influx query --org homelab --token "$INFLUX_TOKEN" --csv 'from(bucket: "speedtest-tracker") |> range(start: -2h)' > dump-influxdb.csv

This is just last 2 hours.  So - looking at only 9th column of the CSV, there's only 127 unique measurements:
$ cat dump-influxdb.csv | cut -d ',' -f 9 | sort -u | wc -l
     127

$ cat dump-influxdb.csv | cut -d ',' -f 9 | sort -u
_measurement
_measurement
boltdb_reads_total
boltdb_writes_total
go_gc_duration_seconds
go_goroutines
go_info
go_memstats_alloc_bytes
go_memstats_alloc_bytes_total
go_memstats_buck_hash_sys_bytes
go_memstats_frees_total
go_memstats_gc_cpu_fraction
go_memstats_gc_sys_bytes
go_memstats_heap_alloc_bytes
go_memstats_heap_idle_bytes
go_memstats_heap_inuse_bytes
go_memstats_heap_objects
go_memstats_heap_released_bytes
go_memstats_heap_sys_bytes
go_memstats_last_gc_time_seconds
go_memstats_lookups_total
go_memstats_mallocs_total
go_memstats_mcache_inuse_bytes
go_memstats_mcache_sys_bytes
go_memstats_mspan_inuse_bytes
go_memstats_mspan_sys_bytes
go_memstats_next_gc_bytes
go_memstats_other_sys_bytes
go_memstats_stack_inuse_bytes
go_memstats_stack_sys_bytes
go_memstats_sys_bytes
go_threads
http_api_request_duration_seconds
http_api_requests_total
http_query_request_bytes
http_query_request_count
http_query_response_bytes
http_write_request_bytes
http_write_request_count
http_write_response_bytes
influxdb_buckets_total
influxdb_dashboards_total
influxdb_info
influxdb_organizations_total
influxdb_remotes_total
influxdb_replications_total
influxdb_scrapers_total
influxdb_telegrafs_total
influxdb_tokens_total
influxdb_uptime_seconds
influxdb_users_total
qc_all_active
qc_all_duration_seconds
qc_compiling_active
qc_compiling_duration_seconds
qc_executing_active
qc_executing_duration_seconds
qc_memory_unused_bytes
qc_queueing_active
qc_queueing_duration_seconds
qc_requests_total
query_influxdb_source_read_request_duration_seconds
service_bucket_new_call_total
service_bucket_new_duration
service_onboard_new_call_total
service_onboard_new_duration
service_org_call_total
service_org_duration
service_org_new_call_total
service_org_new_duration
service_password_new_call_total
service_password_new_duration
service_session_call_total
service_session_duration
service_urm_new_call_total
service_urm_new_duration
service_user_new_call_total
service_user_new_duration
speedtest
storage_bucket_measurement_num
storage_bucket_series_num
storage_cache_disk_bytes
storage_cache_inuse_bytes
storage_cache_latest_snapshot
storage_cache_writes_dropped
storage_cache_writes_err
storage_cache_writes_total
storage_compactions_active
storage_compactions_duration_seconds
storage_compactions_failed
storage_compactions_queued
storage_retention_check_duration
storage_shard_disk_size
storage_shard_fields_created
storage_shard_series
storage_shard_write_count
storage_shard_write_dropped_sum
storage_shard_write_err_count
storage_shard_write_err_sum
storage_shard_write_sum
storage_tsm_files_disk_bytes
storage_tsm_files_total
storage_wal_size
storage_wal_writes
storage_wal_writes_err
storage_writer_dropped_points
storage_writer_err_points
storage_writer_ok_points
storage_writer_req_points
storage_writer_timeouts
string
string
task_executor_promise_queue_usage
task_executor_total_runs_active
task_executor_workers_busy
task_scheduler_current_execution
task_scheduler_execute_delta
task_scheduler_schedule_delay
task_scheduler_total_execute_failure
task_scheduler_total_execution_calls
task_scheduler_total_release_calls
task_scheduler_total_schedule_calls
task_scheduler_total_schedule_fails
true
true

While the whole file is gigantic:
$ cat dump-influxdb.csv | wc -l
 1438112

This is supposed to only keep the speedtest data:
 cat dump-influxdb.csv | cut -d ',' -f 9 | grep speedtest | wc -l
      30

and there's only 30 real data entries!
Am I doing something wrong? Why does this bucket contain all this unnecessary data? I would appreciate some help on finding out what are those and how do I fix this?
Environment (please complete the following information):

OS: Ubuntu via docker
Architecture: amd64
Browser N/A
Version App: 0.16.5

I found the issue, thanks to the Weird measurements in InfluxDB bucket on the influxdb forum:

Stupid error: Did not get that the measurments of influx are automatically written into the first created bucket if I choose get started on initialization

Actions I took to fix the issue:
First, created a new, temporary bucket:
export INFLUX_TOKEN=<my_admin_token_with_full_perms>
docker exec -it influxdb influx bucket create --name "speedtest-clean" --org homelab --token "$INFLUX_TOKEN"

Then in the Influx GUI, I copied all the speedtest measurement data to new bucket:
import "influxdata/influxdb/schema"

from(bucket: "speedtest-tracker")
  |> range(start: 1970-01-01T00:00:00Z)
  |> filter(fn: (r) => r._measurement == "speedtest")
  |> to(bucket: "speedtest-clean")

To test this out, in Grafana, I cloned the dashboard and set speedtest-clean as the data source. Looks good.
Now, I deleted the old bucket:
docker exec -it influxdb influx bucket delete --name "speedtest-tracker" --org homelab --token "$INFLUX_TOKEN"

It took a while, with no effect. I decided to restarted the influxdb container. After restarting it deleted the bucket immediately, and it freed 40 GB! 🤗
At this point I could reconfigure the speedtest-tracker & grafana to use the new bucket, but I decided to copy the data back to the new bucket with old name:
docker exec -it influxdb influx bucket create --name "speedtest-tracker" --org homelab --token "$INFLUX_TOKEN"

And importing back:
import "influxdata/influxdb/schema"

from(bucket: "speedtest-clean")
  |> range(start: 1970-01-01T00:00:00Z)
  |> filter(fn: (r) => r._measurement == "speedtest")
  |> to(bucket: "speedtest-tracker")

Of course, the whole process required generating new tokens, with permissions for new buckets and setting them in speedtest-tracker and grafana.
At this point, I have no idea where those influxdb internal diagnostic measurements are being saved to :D I'll monitor the situation, I guess ;)


Sinuous Tubers - BioInsights

Im cruising in the galctic center region and I found some Sinuous Tubers - they appear on planets without atmosphere but biological signals. But BioInsights did not gave me a mention.
I guess its not yet implemented or somehow gets lost as its bio but no atmosphere.
Thanks for fixing it eventually

BioInsights is neither maintained by me nor is in this repository. Closing.


Documentation

Intro:

[x] Explain the motivation behind gem5art
[x] Talk about main parts a bit
[ ] Talk about how to install

Artifacts

[x] What this is
[x] How to use
[x] Examples
[x] Search the DB
[ ] Use something from the DB

Run

[x] What it is
[x] How to use
[x] What are the assumptions on the config/run script?
[ ] Simple example in SE mode
[ ] Simple example in FS mode
[ ] Show how to search the DB with getRuns

Tasks

[x] What it is
[x] How to start a server and launch jobs

Disk images

[x] Basically what Hoa has already written

Tutorials: Full examples from start to finish

[x] What we'll talk about and why we're doing it
Testing if gem5 boots linux

[x] Talk about downloading gem5, linux, etc.
[x] Show how to create all of the artifacts
[x] Show how to create a script to run everything
[x] Show what the output is
[ ] Show how to search the DB to see what the results are

@ayaz91: Please update this with [x] and [ ] for what has been done and what hasn't been done. Also, if the docs-stuff branch is stale, please remove it.

Outline updated and docs-stuff removed.

Ping. Can you update this with the current status? If everything is done, let's close it!

Ping again :)

I think, there are a couple of things left here. I will create a PR for the changes and close this afterward.


XState state.exit.actions & micro transitions will be executed in the next state

If the action is sensitive to the current state, then a workaround will be needed.
For example:
createMachine({
  states: {
    idle: {},
    busy: {
      always: {
        10: 'idle',
      },
      exit: {
        actions: [
          Mailbox.actions.send(...), // <- this will be executed with state `idle`
        ],
      },
    },
  },
})

In the above code, the Mailbox.actions.send(...) will be executed within the state idle, instead of in the state busy.
Related discussion:

https://github.com/statelyai/xstate/discussions/3231

Due to the above behavior, I have to react the ACTOR_REPLY event in both idle and busy states:
https://github.com/huan/mailbox/blob/50a2ca5c1b6d282ed12ec97c93c7244f7b7ec53b/src/impls/wrap.ts#L159-L176


CIV-0000 CUI cannot upload ccd def file and camunda bpmns to aat directly

CIV-0000 CUI cannot upload anything that it doesn't own to aat directly unless they use staging pods. CCD def is owned by http://github.com/hmcts/civil-ccd-definition/ and camunda bpmns are owned by https://github.com/hmcts/civil-camunda-bpmn-definition

Superceded by https://github.com/hmcts/civil-citizen-ui/pull/1692


Hardware support

Hello all,
just want to ask if the profinet software here is still working for the Siemens CP1616?
https://mall.industry.siemens.com/mall/en/WW/Catalog/Product/6GK1161-6AA02
Do I have to take care of anything special or can I easily buy it and plug it in to my ROS PC? Or is there maybe another hardware which should be prefered for using profinet with ROS?
Thanks in advance and best regards
matl

Hi mat,
I have already started with CP1626 and I can say the final API in more or less the same as CP1616.
At the beginning, I had difficulties for compiling and running the packages of CP1626 itself and installing it over RTAI but finally it is running. Siemens supports it only on SuSE flawours from 9.2 up to 10.2 and our target system was Ubuntu 16.04.
What have you done?


path/filepath: filepath.Walk does not work on mounted volumes in Windows containers

What version of Go are you using (go version)?
1.10
Does this issue reproduce with the latest release?
Not sure
What operating system and processor architecture are you using (go env)?
windows 386
What did you do?

Cross compile the following program from osx GOOS=windows GOARCH=386 go build -o walk.exe main.go (cross compilation does not really matter, the behaviour outlined below is also consistent even if the binary is produced in a windows)

Created a docker container from microsoft/windowsservercore

docker run --rm -it -v c:\files:c:\files microsoft/windowsservercore

Ran the program on the mounted volume

walk.exe -path c:\files

package main

import (
	"flag"
	"fmt"
	"os"
	"path/filepath"
)

func main() {
	path := flag.String("path", "", "path to walk")
	flag.Parse()
	fmt.Printf("walking path %v\n", *path)

	err := filepath.Walk(*path, func(path string, info os.FileInfo, err error) error {
		if err != nil {
			panic(err)
		}
		fmt.Printf("visiting %v\n", path)
		return nil
	})

	if err != nil {
		panic(err)
	}
}

What did you expect to see?
List of files and directories in c:\files.
What did you see instead?
Just the root directory

You run the walk program outside of the started container, just on the same directory that is also mounted into the container?
The directory search works ok when using other (non-Go) programs? Can you check what this C program would output?

Sorry about the lag in my response. Program is run from the default CWD inside the container. However it's in a mounted directory. To be precise:
Step 1 - Launch the container. c:\files has the items we want to traverse. c:\bin has walk.exe.
docker run --rm -it -v c:\files:c:\files -v c:\bin:c:\bin microsoft/windowsservercore

Step 2 - From cwd, run walk.exe
c:\bin\walk.exe -path c:\files

Using other programs such as dir works just fine on mounted directories.
I will update this thread the with the result of the above program over the next couple of days.
Hopefully this clarifies the situation a bit further.

same issue with mounted docker volume on linux. If i run it from VSCode/command line it works as expected (on the same folder which is not mounted). As long as it's mounted through docker volume, it doesn't work. Logged into docker container to check if folder with files exists inside of it and all is there. Might be permission issues of some sorts?

I've confirmed the same behaviour with go1.15.5 for junction points outside a container. My use-case is for volume mounts that happen to be a WCOW container image.
I mounted a WCOW container image using wclayer, and used the source code in the initial report to test. Walking inside the mount point is fine, but walking the mount point directly or walking a directory above the mount point, the walk stops at the mount.
I suspect the core problem is that filepath.Walk does not follow symbolic links, and to Go, a volume mount point appears to be a symlink back to itself, see https://github.com/containerd/containerd/pull/4419/commits/ac88af7a058e0e724e7e972293284f0768319d07#r485615803 and isSymlink in https://golang.org/src/os/types_windows.go.
Unlike a real Symlink, it's not necessarily feasible to call filepath.Walk on the target of a mount point, as it may be a volume reference.

Thinking about this, one rationale for treating an NTFS Mount Point like a Symlink is that, unlike mount --rbind in Linux, subsequently-created Volume Mounts are visible through that reparse point, so it's possible to introduce an infinite recursion.
I assume that avoiding infinite recursion is why filepath.Walk doesn't follow symlinks in the first place.

After https://go.dev/cl/463177, the fix here is probably to add a trailing separator to the path passed to Walk.

For the record, the above fix was in Go 1.21.


Update hosted website

Description
Hosted website is not up to date
Expected Behavior
Update it to the latest main branch
I will checkout a branch from the PR which changed the credentials from 000webhost to localhost

@sudhay23 there might be 1 more PR, after merging that you can work on this issue

@san-coding Is this ready to be deployed?

now that the .env file is created we must make all the php file use the variables inside .env

after that we will only need the change the .env files for changing credentials

@san-coding Okay fine :)


[CI] notify remote providers only on stable releases

Signed-off-by: Rudraksh Pareek<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers

Triggers only when a stable release is made.
Also fixes the graphQL schema validator workflow

Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #3766 (1f22292) into master (de65207) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3766      +/-   ##
==========================================
- Coverage   21.05%   21.00%   -0.06%
==========================================
  Files          45       45
  Lines        3819     3819
==========================================
- Hits          804      802       -2
- Misses       2803     2805       +2
  Partials      212      212

Flag
Coverage Δ

e2etests
∅ <ø> (?)

gointegrationtests
9.97% <ø> (-0.06%)
:arrow_down:

integrationtests
∅ <ø> (?)

unittests
12.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/start.go
54.07% <0.00%> (-0.75%)
: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 f32cfd5...1f22292. Read the comment docs.

Looks CITY to me.

Cool I trust your CITY : )


Set CPU-only mode

Hi,
I tried to run the demo.py file in python, but I got the following error:
F0311 15:58:18.148229  6000 common.cpp:76] Cannot use GPU in CPU-only Caffe: check mode.

however, I have modified the mode to CPU-only mode. Should I modified some other code to disable GPU mode but enable CPU-only mode?
By the way, the faceboxes model was downloaded from the page you publicized your source code:
https://github.com/sfzhang15/FaceBoxes
os.chdir(caffe_root)
sys.path.insert(0, 'python')
import caffe

caffe.set_device(0)
# caffe.set_mode_gpu()
caffe.set_mode_cpu()

model_def = 'D:/code_cv/face_detection/FaceBoxes/models/faceboxes/deploy.prototxt'
model_weights = 'D:/code_cv/face_detection/FaceBoxes/models/faceboxes/faceboxes.caffemodel'
net = caffe.Net(model_def, model_weights, caffe.TEST)

image = caffe.io.load_image('examples/images/1.jpg')

Thanks and Best Regards,
Ardeal

@ardeal
Try to comment out 'caffe.set_device(0)' ?

Hi Dr. Zhang,
Thank you for your help!
I did the following experiments:
Experiment 1:
Set CPU-only = 0 and re-build caffe. If my understanding is correct, CPU and GPU are both supported by the newly built Caffe.
in demo.py file:
caffe.set_device(0)
caffe.set_mode_gpu()
#caffe.set_mode_cpu()

re-run demo.py, and I got the following error:
I0312 09:00:16.459015  9840 layer_factory.hpp:77] Creating layer input
F0312 09:00:16.459015  9840 layer_factory.hpp:81] Check failed: registry.count(type) == 1 (0 vs. 1) Unknown layer type: Input (known types: MemoryData)
*** Check failure stack trace: ***

when the code went to:
net = caffe.Net(model_def, model_weights, caffe.TEST)

Experiment 2:
using the CPU and GPU version of Caffe and the following configuration:
#caffe.set_device(0)
#caffe.set_mode_gpu()
caffe.set_mode_cpu()

I got the same error.
Experiment 3:
using the CPU and GPU version of Caffe and the following configuration:
# caffe.set_device(0)
# caffe.set_mode_gpu()
caffe.set_mode_cpu()

I got the same error.
In addition, the faceboxes.caffemodel file was download from the link in your code page:
https://github.com/sfzhang15/FaceBoxes

Is the model for CPU or GPU?
Do you have any idea about my issue?
Thanks and Best Regards,
Ardeal

@ardeal
It seems the type of input layer is not registered. Your input type is "data"?

The first a few lines in your deploy.prototxt file are:
name: "deploy"
input: "data"
input_shape {
dim: 1
dim: 3
dim: 640
dim: 480
}
is the input type "data"?
Did I choose the correct input file?
otherwise, what input file should be chosen?

Hi Dr. Zhang,
Thanks for your help!
I am now able to run faceboxes code on VS2015, and the output of algorithms seems to be correct.
But there is something weird. The following is the figure plotted when I run demo.py:

@ardeal
Yes. There are some faces with low scores, maybe becasue they have small scales. You can low the threshold from 0.5 to 0.25 to show all faces, or you can enlarge the image.

i have the same problem can someone help me plz
F0929 20:55:49.671247 6050 base_data_layer.cpp:84] Cannot use GPU in CPU-only Caffe: check mode.
*** Check failure stack trace: ***
Aborted (core dumped)

i have the same problem can someone help me plz
F0929 20:55:49.671247 6050 base_data_layer.cpp:84] Cannot use GPU in CPU-only Caffe: check mode.
*** Check failure stack trace: ***
Aborted (core dumped)

Any tutorial to switch to CPU-only caffe?caffe.set_mode_cpu() seems not enough.

i have the same problem can someone help me plz
F0929 20:55:49.671247 6050 base_data_layer.cpp:84] Cannot use GPU in CPU-only Caffe: check mode.
*** Check failure stack trace: ***
Aborted (core dumped)

Any tutorial to switch to CPU-only caffe?caffe.set_mode_cpu() seems not enough.


Possibility to disable secret caching?

Hi,
With typical Kubernetes secrets, mounted Secrets are updated automatically.
I noticed that with the CSI-driver, updating the secret in Key Vault, doesn't make the secret change in the filepath. In my (limited) testing, I was able to get the new version of a secret loaded after recreating the pod (deleting pod and having deployment create a new pod).
This lead to two questions from my side:

Is there the ability to disable secret caching?
By default, how long are secrets cached before getting re-fetched from Key Vault?

@NillsF secrets-store-csi-driver currently doesn't automatically reload when secrets/keys/certs are updated in Key Vault. We have an issue open for this enhancement - https://github.com/kubernetes-sigs/secrets-store-csi-driver/issues/125.  Feel free to chime in on the issue.

What if we could use a sidecar to notify the Azure Key Vault provider for Secret Store CSI driver by using Event Grid? https://docs.microsoft.com/en-us/azure/event-grid/event-schema-key-vault
We use a similar approach for non-Kubernetes workloads but should be an opt-in; if that's feasible ofcourse - I'm not a secret store expert.
https://background-jobs.arcus-azure.net/features/security/auto-invalidate-secrets

Maybe a another option is to watch the secrets in KV and update the K8S secrets accordingly.
For example, with the certificate during renew (app service certificate). The  certs are renew 60 days before the expiration date. So if a check is done every 24h, it can be OK. Of course the frequency to check the secret in KV can be configured. It’s a pull solution, but can help a lot of project to handle TLS secret for ingress :)

This is being tracked in kubernetes-sigs/secrets-store-csi-driver#125. @tomkerkhove @deuch @NillsF Please feel free to chime in on the issue.


Remove custom isort import groups

It seems simpler to use the default isort import groups so that all of the edX repos don't need to maintain the same hand-coded list of library names. The benefit of having additional groups seems small compared to the maintenance burden they introduce.
Note: this is currently the configuration used in edx-platform. Any changes we choose to make here should then be applied to edx-platform too.
FYI @clintonb @doctoryes @robrap

Thanks for the reviews, folks.
@jmbowman, thanks for the suggestions. I've created a doc PR here:
https://github.com/edx/cookiecutter-django-app/pull/17
I also ran isort against the repo but there is still a build failure. I'll look again to see what I've missed.

@andy-armstrong What happened to this?

@robrap I made various attempts to fix the build failures but none of the suggested ideas worked. I then forgot about it. :-)

Got it.  At least that status is recorded here now. :)

An equivalent change with passing tests was merged as part of https://github.com/edx/cookiecutter-django-app/pull/25 .


App crashes when other libraries are added

Is this a bug report?
Yes
Have you read the Installation Instructions?
Yes
Environment
"react": "16.8.3",
"react-native": "0.59.8",
"react-native-geolocation-service": "^2.0.1",
"react-native-maps": "^0.24.2",

Steps to Reproduce

Install and react-native link react-native-maps on an empty rn project
Built, ran and rendered successfully
Install react-native-geolocation-service
react-native link
Built, but crashes.

Other way around

Install react-native-geolocation-service
2.react-native link
Built, ran and rendered successfuly
Install react-native-maps, links
Built, but crashes

Expected Behavior
Built and runs
Actual Behavior
Built but crashes
Reproducible Demo
Empty react-native project
I see that I should exclude all the Google Play Services dependencies from the modules, but where should I do this? thanks for your help

@barakoles
I suppose this is android.
You didn't give any logs to see where/what is crashes, but assuming you are right you might wanna add something like this in your android/app/build.gradle
Please keep in mind that this is for one of my projects, so you might have to tweak the settings. Also it assumes that supportLibVersion is declared in the android/build.gradle  under buildscript { ext { section.

configurations.all {
    resolutionStrategy {
        force 'org.webkit:android-jsc:r225067'
        force "com.android.support:support-compat:${rootProject.ext.supportLibVersion}"
        force "com.android.support:support-core-utils:${rootProject.ext.supportLibVersion}"
        force "com.android.support:support-core-ui:${rootProject.ext.supportLibVersion}"
        force "com.android.support:support-v7:${rootProject.ext.supportLibVersion}"
        force "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
        force "com.android.support:design:${rootProject.ext.supportLibVersion}"
        force "android.arch.lifecycle:livedata-core:1.1.1"
        force "android.arch.lifecycle:viewmodel:1.1.1"

        force "android.arch.lifecycle:runtime:1.1.1"
        force "android.arch.core:runtime:1.1.1"
        force "com.google.android.gms:play-services-base:16.0.1"
        force "com.google.android.gms:play-services-gcm:16.0.0"
        force "com.android.support:customtabs:28.0.0"
    }
}

Hi @rborn thanks for the reply!
I actually got some progress when I changed my build.gradle for this:
`
...
dependencies {
implementation project(':react-native-gesture-handler')
implementation(project(':react-native-geolocation-service')){
exclude group: 'com.google.android.gms'
}
implementation(project(':react-native-maps')){
exclude group: 'com.google.android.gms'
}
implementation 'com.google.android.gms:play-services-base:12.0.1'
implementation 'com.google.android.gms:play-services-basement:12.0.1'
implementation 'com.google.android.gms:play-services-location:12.0.1'
implementation 'com.google.android.gms:play-services-tasks:12.0.1'
implementation 'com.google.android.gms:play-services-maps:12.0.1'
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
implementation "com.facebook.react:react-native:+"  // From node_modules
}
...
`
It is now running the app but it does not render well, it show a gray map and crashes afterwards
I don't quite believe its an API KEY error because the map rendered well when it was only this library
I ran adb logcat and it throws me this:
05-16 15:39:43.545  5925 21394 W ErrorProcessor: onFatalError, processing error from engine(4) 05-16 15:39:43.545  5925 21394 W ErrorProcessor: com.google.android.apps.gsa.shared.speech.b.g: Error reading from input stream 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.staticplugins.microdetection.d.k.a(SourceFile:91) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.staticplugins.microdetection.d.l.run(Unknown Source:14) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.libraries.gsa.runner.a.a.b(SourceFile:32) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.libraries.gsa.runner.a.c.call(Unknown Source:4) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.shared.util.concurrent.b.g.run(Unknown Source:4) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.shared.util.concurrent.b.aw.run(SourceFile:4) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.shared.util.concurrent.b.aw.run(SourceFile:4) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.lang.Thread.run(Thread.java:764) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.shared.util.concurrent.b.i.run(SourceFile:6) 05-16 15:39:43.545  5925 21394 W ErrorProcessor: Caused by: com.google.android.apps.gsa.shared.exception.GsaIOException: Error code: 393238 | Buffer overflow, no available space. 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.speech.audio.Tee.j(SourceFile:103) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.speech.audio.au.read(SourceFile:2) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.io.InputStream.read(InputStream.java:101) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.speech.audio.ao.run(SourceFile:17) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at com.google.android.apps.gsa.speech.audio.an.run(SourceFile:2) 05-16 15:39:43.545  5925 21394 W ErrorProcessor:        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
Is there any other command I should use in order to get more logs? when debugging javascript console does not show anything and the app just crashes

Solved. Was a conflict with react-native-maps loading a google play dependency that was lower than the one used by this package (10.0.1). Had to manually change it inside the react-native-maps node_module build.gradle project file

Originally posted by @fmelp in https://github.com/evollu/react-native-fcm/issues/360#issuecomment-287642293
Should I do the same as this guy did since it's still conflicting?

The crash doesn't seem to be elated to the maps ?


KeyError for extended_circular_fasta.write(header2joined_seq[contig2extended_status[contig]] + '\n')

Hey LinXing,
First, thanks for developing this super useful tool! I've so far ran it on a couple hundred virome samples and it's working great! I have stumbled across an issue with 2 samples though that I was wondering if you could help me with. For each of the 2 metagenomes I get this error (but obviously a different key value differing the messages):
Traceback (most recent call last):
  File ".snakemake/conda/e7dfc9b82d378646d96b58efd8350561_/bin/cobra-meta", line 12, in <module>
    sys.exit(main())
  File ".snakemake/conda/e7dfc9b82d378646d96b58efd8350561_/lib/python3.10/site-packages/cobra.py", line 1598, in m
ain
    extended_circular_fasta.write(header2joined_seq[contig2extended_status[contig]] + '\n')
KeyError: 'NODE_404_length_6556_cov_28.183972'

I checked for these keys in the whole contig set (the scaffold.fasta output by metaspades); query file (all scaffolds >2.5kbp from the metaspades scaffolds.fasta); and the coverage file. It is present in each of those files with no additional characters. So, I'm a bit confused with what the source of the problem could be (especially since the couple of hundred other samples i've processed worked fine!). Any help you could give would be much appreciated!
The the log file looks like this:
1. INPUT INFORMATION
# Assembler: metaSPAdes
# Min-kmer: 21
# Max-kmer: 55
# Overlap length: 55 bp
# Read mapping max mismatches for contig linkage: 2
# Query contigs: /data/san/data0/users/chris/data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds_over_2.5kb.fasta
# Whole contig set: /data/san/data0/users/chris/data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds.fasta
# Mapping file: /data/san/data0/users/chris/data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds_sorted.bam
# Coverage file: /data/san/data0/users/chris/data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds.coverage.formatted.txt
# Output folder: /data/san/data0/users/chris/data/processed/assemblies/spades_CTRLM08LongB03Faeces/cobra

2. PROCESSING STEPS
[01/23] [2024/02/16 00:22:53] Reading contigs and getting the contig end sequences. A total of 255643 contigs were imported.
[02/23] [2024/02/16 00:22:58] Getting shared contig ends.
[03/23] [2024/02/16 00:23:00] Writing contig end joining pairs.
[04/23] [2024/02/16 00:23:00] Getting contig coverage information.
[05/23] [2024/02/16 00:23:00] Getting query contig list. A total of 2314 query contigs were imported.
[06/23] [2024/02/16 00:23:00] Getting contig linkage based on sam/bam. Be patient, this may take long.
[07/23] [2024/02/16 00:23:38] Parsing the linkage information.
[08/23] [2024/02/16 00:23:43] Detecting self_circular contigs.                                                                                "zEQ$" 23:44 15-Feb-24
[09/23] [2024/02/16 00:23:43] Detecting joins of contigs. 10%, 20%, 30%, 40%, 50%, 60%, 70%, 80%, 90%, 100% finished.
[10/23] [2024/02/16 00:23:46] Saving potential joining paths.
[11/23] [2024/02/16 00:23:46] Checking for invalid joining: sharing queries.
[12/23] [2024/02/16 00:23:47] Getting initial joining status of each query contig.
[13/23] [2024/02/16 00:23:47] Getting final joining status of each query contig.
[14/23] [2024/02/16 00:23:47] Getting the joining order of contigs.
[15/23] [2024/02/16 00:23:47] Getting retrieved contigs.
[16/23] [2024/02/16 00:23:47] Saving joined seqeuences.
[17/23] [2024/02/16 00:23:47] Checking for invalid joining using BLASTn: close strains.
[18/23] [2024/02/16 00:23:48] Saving unique sequences of "Extended_circular" and "Extended_partial" for joining checking.

Hi,
Thank you for your interest in COBRA, I am glad it helps for your analyses.
Regarding these two samples, could you please share these files with me , (1) COBRA_end_joining_pairs.txt (2) COBRA_potential_joining_paths.txt and (3) debug file?
Thank you.
Best,
LINXING

Sure, here are those 3 files for sample 1 (key error in this case was 'NODE_67_length_39995_cov_222.169830')
COBRA_end_joining_pairs.txt
COBRA_potential_joining_paths.txt
debug.txt

And here they are for sample 2 (key error here was 'NODE_404_length_6556_cov_28.183972')
COBRA_end_joining_pairs.txt
COBRA_potential_joining_paths.txt
debug.txt

Thank you Chris. I will take a look ASAP and let you know what is the wrong.

And here they are for sample 2 (key error here was 'NODE_404_length_6556_cov_28.183972')
COBRA_end_joining_pairs.txt COBRA_potential_joining_paths.txt debug.txt

Hi Chirs, unfortunately I was not able to locate the bug with the files you provided. Do you mind sharing all the input files of this sample, so I can run COBRA on my end and try to debug it? No worries if you do not want to do so.
LINXING

Yeah sure no problem, I'll send them onto the gmail address you provided in a different issue post. Thanks again for taking a look at the issue!
In case you need it here is the command i'm running for sample 1 (so same for sample 2 except paths to files)
cobra-meta -f data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds.fasta -q data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds_over_2.5kb.fasta -
c data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds.coverage.formatted.txt -m data/processed/assemblies/spades_CTRLM08LongB03Faeces/scaffolds_sorted.bam -a metaspa
des -mink 21 -maxk 55 -t 10 -o data/processed/assemblies/spades_CTRLM08LongB03Faeces/cobra/

Sent :)

Sent :)

Hi Chris, unfortunately I do not see the email. Could you please confirm?

I sent it to the linkingchanATgmailDOTcom address you posted in another email. Is this not the correct email?

i sent it via wetransfer so may be in your spam if that is the correct email

Hi Chris, I think I was able to fix the bug. Could you please try this version and let me know if it works for you or not? Thank you.
cobra_test.py.zip

Hey LinXing,
Yeah, that seems to have fixed the issue! Both sample now run to completion 😄

That's good to know. Thank you for help. I will release a new version asap.

No problem and thank you for the rapid fix!


How about Proxy Functions?

I could not easily find a guide for developing a Proxy type Function in Visual Studio. Probably it the same as normal Functions, but there is nothing indicating that. Any guide? Thanks.

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

ID: 369aefa6-74da-3001-f835-15abdfffd5d6
Version Independent ID: 2cc2a2db-d059-3252-7a1a-4261b7d3c37c
Content: Develop Azure Functions using Visual Studio
Content Source: articles/azure-functions/functions-develop-vs.md
Service: functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thanks for the feedback! We are currently investigating and will update you shortly.

Are you looking for something like this?
https://docs.microsoft.com/en-us/azure/azure-functions/functions-proxies

Hi
This describes how to do it in Azure portal.
I am want tutorial to build proxy functions in Visual Studio
On Tue 3 Jul 2018 at 20:43, Micah<EMAIL_ADDRESS>wrote:

Are you looking for something like this?
https://docs.microsoft.com/en-us/azure/azure-functions/functions-proxies
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/11144#issuecomment-402271477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARO6rD-CUa9UG6hWX3oMpCGYbkvLy15Yks5uC8lbgaJpZM4VBGSU
.

--
Hesham

Got it. I am not finding anything for Visual Studio as well. Everything seem to just go via the portal
https://blogs.msdn.microsoft.com/appserviceteam/2017/11/15/azure-functions-proxies-is-now-generally-available/
https://github.com/mattchenderson/azure-functions-proxies-intro
@ggailey777 any idea of we have info on this topic for Visual Studio?

@hshokry I am working offline to find an answer on this. I will update as soon as I have more information.

So I am not finding any documentation specifically on creating proxies in visual studio. However, I have found that you only need to include the proxies.json in your function template to deploy them via visual studio
https://docs.microsoft.com/en-us/azure/azure-functions/functions-proxies#advanced-configuration

@hshokry I will close this for now. But if you feel you need more info just let me know and we can reopen and continue.

I don’t think this should be closed until a doc is issued.
On Fri 6 Jul 2018 at 17:20, Micah<EMAIL_ADDRESS>wrote:

@hshokry https://github.com/hshokry I will close this for now. But if
you feel you need more info just let me know and we can reopen and continue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/11144#issuecomment-403081166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARO6rHYvkbhkKI1VMsTvHjXoypEN9QLXks5uD45rgaJpZM4VBGSU
.

--
Hesham

@tysonn can you get this to the correct team for the doc idea?

@ggailey777 - Could you look at this request for a doc? It may be something to log as a request in the internal backlog.

@hshokry since function proxies are simply defined as proxies.json files in the root of the function app, we will track the additional VS documentation requirements in this issue: https://github.com/MicrosoftDocs/azure-docs/issues/24975.
#please-close


enhance(arbiter-engine): remove use of Artemis in favor of our own agent design

Give an overview of the tasks completed
This PR started off as me just wanting to improve the Messager. Midway through, we found that dealing with Artemis was going to be quite a headache since the repo is seemingly inactive. So this PR became a lot more work. Nonetheless, we are getting close to a working different abstraction, but this does not pass completely yet.

Changes in arbiter-core reflect the additional feature added to the EventLogger that enables a streaming mode.

I added a decent amount of docs around arbiter-engine as to help understand the structure here.
Link to issue(s) that this PR closes

Closes #750
Closes #785
Closes #786
Closes #787

What is the difference/relationship between running specific states (run_state) and the transition function? Is it primarily to allow for the testing and the development? When we run the sim say over a bunch of "transitions" will we need to be sure to await the transition after running a state? What is the flow you are thinking here?

This by no means has to be the correct way to do this, but it is a working way to do things. Let's break it down for a sec and think about the Rust async model.

Note that run_state() is NOT async. What happens in the run_state functions is we wrap a blocking/awaited future in a tokio::task which allows tokio to take this and run it concurrently in its runtime. In essence, run_state starts running whatever state we want it to (e.g., syncing or processing). The task is placed back into the relevant struct as a JoinHandle<..> (or a JoinAll).
transition() is async and blocking. When we call transition(), we grab the Join, and await it to finish its execution and ultimately return the inner object back to the struct. For instance, for the behavior we have JoinHandle<B> and when we await this, we get back B and place this into the Engine<B, E>.

I think this could probably be simplified, but it might not matter much since on top of this we can abstract away the user ever having to call these themselves by having a manager manage worlds (or something).


Magic Number

What's done:
Magic number
Actions checklist

[x] Implemented Rule, added Warnings
[x] Added tests on checks
[ ] Added tests on fixers
[x] Updated diktat-analysis.yml
[x] Updated available-rules.md
[x] closes #767

No, we didn't have a rule for that. So I added this rule to chapter 3


Add v0.9.0 to cargo

I am having problems running remodel with foreman issue And my workaround was to use cargo.
But sadly it does not contains latest version.
Can you please add it to cargo?

Fixed, thank you for letting me know that I missed this!


Add the resistor-color-trio exercise.

See the specification: https://github.com/exercism/problem-specifications/tree/main/exercises/resistor-color-trio

Hey @MichaelBunker, github won't let me reopen this:

I had rebased to fix an error.
See new PR https://github.com/exercism/php/pull/541 which shouldn't have an issue reopening.


Usage Data Section needs to be reordered

https://docs.pivotal.io/runtimes/pks/1-1/installing-pks.html#install
The usage data section needs to go all the way at the bottom.

Thanks @rjain-pivotal! The location of this section has been fixed: https://github.com/pivotal-cf/docs-pks/commit/06973c0d8719e45955a0d765447f3ff1fb049c14


Init breaks js execution

Hi!
Thanks for updating with examples.
I've used your examples to test a dummy implementation:
function onDeviceReady() {
    console.log('Device ready);
    var items = [{
        domain: 'com.pillerkollen.drugname',
        identifier: 'NPLID01',
        title: 'Alvedon',
        description: 'Paracetamol',
        keywords: ['Paracetamol'],
        url: 'http://pk.se/images/logo_dark.png',
    }, {
        domain: 'com.pillerkollen.drugname',
        identifier: 'NPLID02',
        title: 'Bisoprolol actavis',
        description: 'Bisoprolol',
        keywords: ['bisoprolol'],
        url: 'http://pk.se/images/logo_dark.png',
    }];
    window.plugins.indexAppContent.init();
    window.plugins.indexAppContent.setItems(items, function() {
        console.log('Successfully set items');
    }, function(error) {
        console.log('Error: ' + error);
    });
}

Maybe I'm missing something but as soon as I pass the init call that breaks the rest of the js execution.
Tried with and without success and error callbacks, the xcode terminal output doesn't output anything after the plugins loaded msgs - not even the "console ready" output. Tried to un- and reinstall the plugin with the same results.
Initially thought it was due to MobileCoreServices.framework not being added during installation but manually adding it didn't change anything.
I'm on cordova cli 6.0.0, cordova iOS 4.0.1, tested on device and simulator

@hessius The issue is caused by Cordova adding another cordova.define wrapper around the plugin javascript. The plugin is designed for being loaded from a remote source and thus need the cordova.define statement.
Remove the "cordova.define("cordova-plugin-indexappcontent", function(require, exports, module) {....}" wrapper function and it should work fine.

Pull request #3 should resolve the issue.

Pull request #4 resolves another issue where the plugin path was wrong.


Java client, create component security schemes

Is your feature request related to a problem? Please describe.
Java client, create component security schemes
Describe the solution you'd like

Describe alternatives you've considered

Additional context

Closed by https://github.com/openapi-json-schema-tools/openapi-json-schema-generator/pull/383


Cosmos Troubleshooting for Forbidden could use some detail

OS: Windows 10 Pro Insider Preview 20221.1000
Browser: Edge (chromium), canary version 87.0.651.0
I am currently having an issue with looking at my databases/collections in browser and receiving the following error in the notifications area of the data explorer:
Error while refreshing databases: {"code":403,"body":{"code":"Forbidden","message":"Request is being made with a forbidden encryption in transit protocol or cipher. Check account SSL/TLS minimum allowed protocol setting.

The third bullet in the Troubleshoot connectivity issues section appears to be exactly dealing with this, but the current documentation suggests:
The recommended work-around is to change the settings and default to TLS 1.2; for
instance, in IIS Manager navigate to "Sites" -> "Default Web Sites" and locate the
"Site Bindings" for port 8081 and edit them to disable TLS 1.3. Similar operation can
be performed for the Web browser via the "Settings" options.

So firstly I did not have IIS installed locally, and so I added the IIS Manager tools from the windows features in order to try out this fix, but there was no "Site Bindings" for port 8081 that I could find or configure, so the information appears to be incorrect, or at least not clear about how to apply this 'fix'.
Could we have some images or more descriptive text on how to fix this issue?
Please note, my code (C#, .NET Core 3.1) can connect and use the collections just fine.
Thanks!
Max

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

ID: 38fd2656-4d93-0a58-99ca-b5d1bcd06850
Version Independent ID: e80e2a9b-182d-993b-3395-9d716576de92
Content: Troubleshoot issues when using the Azure Cosmos emulator
Content Source: articles/cosmos-db/troubleshoot-local-emulator.md
Service: cosmos-db
GitHub Login: @markjbrown
Microsoft Alias: mjbrown

Thanks for the feedback! I have assigned the issue to the doc author to update appropriately.

I cannot update our docs without first knowing what your issue really is.
Please raise a support ticket to resolve your issue. Updates to our docs occurs when we see repeating patterns in customer issues when we review closed support tickets.
Thanks.

@maxcalvin Please convey if you were able to go to Support and got a resolution for your issue.

Thanks for the ping. I don't know how to contact support so I have not done so.
Feel free to close this issue. I was only looking for the instructions to be clarified, not for someone to help me with my specific issue, as it was not possible given the current documentation to know if the solution being proposed was actually relevant to the problem that was occurring on my machine.
I have just stopped using the data explorer.

If you're still looking to find a resolution you can file a support ticket by going to Azure Portal. Click on your Cosmos DB account and then scroll down. It's on left side bar at the bottom of the page.
Thanks.
#please-close


[Tumblr] some links returning Unable to download webpage: HTTP Error 403: Forbidden

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

youtube-dl -v -F https://everythingfox.tumblr.com/post/656964996113301504/i-am-fierce-via
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-F', 'https://everythingfox.tumblr.com/post/656964996113301504/i-am-fierce-via']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Git HEAD: 7d37d0970
[debug] Python version 3.9.6 (CPython) - macOS-11.4-arm64-arm-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[Tumblr]<PHONE_NUMBER>13301504: Downloading webpage
[Tumblr]<PHONE_NUMBER>13301504: Downloading iframe page
ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: 'Forbidden'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/opt/homebrew/Cellar/youtube-dl/2021.6.6/libexec/lib/python3.9/site-packages/youtube_dl/extractor/common.py", line 634, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/opt/homebrew/Cellar/youtube-dl/2021.6.6/libexec/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 2288, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File<EMAIL_ADDRESS>line 523, in open
    response = meth(req, response)
  File<EMAIL_ADDRESS>line 632, in http_response
    response = self.parent.error(
  File<EMAIL_ADDRESS>line 561, in error
    return self._call_chain(*args)
  File<EMAIL_ADDRESS>line 494, in _call_chain
    result = func(*args)
  File<EMAIL_ADDRESS>line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

Description

Test link:
https://everythingfox.tumblr.com/post/656964996113301504/i-am-fierce-via
same link but a bit different format:
https://everythingfox.tumblr.com/post/656964996113301504/embed
However these links work, even though the structure seems to be the save (subdomain, post, ID, video name):
https://dumbasscats.tumblr.com/post/638777506589229056/a-true-captain-goes-down-with-his-ship-via-reddit
https://cuteanimalshare.tumblr.com/post/656841552268869632/who-doesnt-like-ginger-cats

The failing URL https://everythingfox.tumblr.com/post/656964996113301504/i-am-fierce-via needs the Referer header to be added when fetching the iframe URL (the value being the URL of the original page).
Also, the page has 10 video iframes, but the extractor only finds the first (top) one. The extractor should default to selecting the first video unless a playlist is requested, but, because --yes-playlist isn't distinguishable from failing to say --no-playlist, there is no way for yt-dl to do that.

You can use the api-http2.tumblr.com host instead, and avoid having to parse HTML or JavaScript:
https://github.com/89z/mech/blob/v1.46.9/tumblr/tumblr.go#L80-L92

Most extractors follow the browser's access paths, so that we know the extracted item corresponds to the resource indicated by the extracted URL.
When using an API that isn't directly invoked in the browser access path, we need to understand what metadata is available, in case the webpage needs to be searched for missing fields, and to what extent the API is supported/documented.
In this case, just pulling the yt-dlp fixes looks like a simple solution and would avoid duplicate code.

Most extractors follow the browser's access paths, so that we know the extracted item corresponds to the resource indicated by the extracted URL.

That seems like an arbitrary decision. Using deep linking [1], if a user is on a mobile device, they could have the app installed. If they do, and they visit the link in the original post here, the mobile browser is going to give the user the option to visit the page in the app.
If the user accepts, then the page will be opened in the app, using the app API or internal logic as needed. However each project such as YouTube-DL, can of course choose how they want to implement an extractor. I just wanted to point out that the issue isn't as black and white and some might paint it to be.
https://wikipedia.org/wiki/Mobile_deep_linking

If the site/app has a function like that I'd count it as a documented API. But such deep link URLs can be handled by adding an extractor, or extending an existing URL pattern. The default approach I described follows since yt-dl pre-dates the smartphone app era.
Of course, yt-dl has its own custom links, such using just the YT ID, or ytsearchall:..., or kaltura:partner:id.


feat: Add aliases decorator

Add a compatibility decorator
Provide a way to alias kwargs in functions.
Examples
    @aliases(a="b", c=["d", "e"])
    def func(a, c):
        return a, c

    func(a=1, c=2)  # (1, 2)
    func(b=1, d=2)  # (1, 2)

Codecov Report
Attention: Patch coverage is 93.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 89.75%. Comparing base (944f77c) to head (20dd947).

Files with missing lines
Patch %
Lines

tests/test_compatibility.py
93.33%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #40      +/-   ##
===========================================
+ Coverage    89.40%   89.75%   +0.35%
===========================================
  Files            5        6       +1
  Lines          151      166      +15
===========================================
+ Hits           135      149      +14
- Misses          16       17       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


init.txt won't be executed when specifying the test suite file under the directory

i.e.,
for test suite structured this like:
tests/
__init__.txt
demo1.txt
demo2.txt
real1.txt
the setup/teardown in __init__.txt won't get executed when running tests as below:
robot tests/demo*
When running any part of a test suite (here 'tests' is a test suite in RF), the suite setup/teardown should always be executed as by definition.
Think the current behavior breaks the concept of a test suite in RF.

This is by design. Robot cannot really start going through parent directories for init files. You can run the directory and use --suite option to select the child suite you want.


SAP Sandbox

Hello everyone, I'm working on a deployment of SAP Fiori and I need some serious SAP Sandbox providers, any suggestions?

This may be a more general question and not about the tutorial itself. Feel free to continue the discussion in the SAP Community or in the SAP Questions & Answers.
https://www.sap.com/community.html
https://answers.sap.com/index.html


Change scanner not picking up files in index

For some reason if a file is externally added and put into the index (usually via my IDE prompting to "Add file to git") the scanner will not pick up that this file now exists and the state should be updated...

I think this actually only happens for newly added empty files

It looks like these empty files actually just don't show up in the index at all

This is fixed with the scanner changes


fix WsUtility ns

fix: #1119

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

@616b2f Could you please squash your commits and issue this PR against our dev5x branch?

/azp run

@mafurman done. First I messed it up with changing the base to dev5x and have to force push 2 times, but now it looks good :)

@616b2f Thanks! :) I just merged in your PR.


does DRM allow to take screenshot?

I test to use canvas to take screenshot as playing the DRM dash video, the image of screenshot is black,  does DRM allow to take screenshot in the chrome browser?

I expect not, based on your experience.  I don't have an authoritative answer, though, and I would guess that this may vary from one DRM system to another.


Unbreak intro notebook, use latest index

Hard to review, but updated the intro notebook so it works oob with the latest code changes; the first 6 cells.
There is a fairly advanced part at the bottom that is also pretty out of date and has a TODO to maybe move it to another notebook on continuous time-modelling. Should we get rid of that?

Thank you. I imagine by the advanced part, you mean "putting it all together" and beyond? If so, feel free to delete. I will re-do it in the near future. Thanks!

Ok! Will delete that part and merge 😄


Timestamps for fetch and save don't match

When you do a fetch the createdAt and updatedAt timestamps are numbers but they are date objects when you do a save.
User.forge({ name: 'bsiddiqui' })
.fetch()
.then(function (m) {
   console.log(m.get('createdAt')) //<PHONE_NUMBER>873
})

User.save({ name: 'bsiddiqui' })
.save()
.then(function (m) {
   console.log(m.get('createdAt')) // Mon Jan 12 2015 21:06:47 GMT-0800 (PST)
})

Just from looking at this I think it's almost certain that this has to do with the column type in the database. Please post the schema. Certain types can be parsed automatically by node-pg and others you'll need to handle manually in model.parse.

  return knex.schema.createTable('test_table', function (table) {
    table.increments('id');
    table.string('name');
    table.timestamps();
  });

Hmm. Never seen anything like that before. It's basically no different than my setup. You sure there isn't something custom that might be interfering?

@bendrucker only customizations to the model here: https://github.com/enjoy/bookshelf-modelbase/blob/master/lib/index.js

@bendrucker were you able to reproduce?

You'll get dates with MySQL and Postgres. You have to manually parse with SQLite.
https://github.com/bendrucker/bookshelf-issue-572
Closing this but feel free to post more if you're on PG

Great thanks!
On Fri, Jan 16, 2015 at 9:52 AM Ben Drucker<EMAIL_ADDRESS>wrote:

Closed #572 https://github.com/tgriesser/bookshelf/issues/572.
—
Reply to this email directly or view it on GitHub
https://github.com/tgriesser/bookshelf/issues/572#event-220222511.


Report points in dashboard

Along with reporting how many miles walked, we should report how many points the user currently has. Each bag of trash is worth 3 points, each mile walked is worth 1 point.

@stevensona As you might have seen from my commit, they've decided that trash bags are now worth 4 points instead of three. I went in and updated the function myself because I was testing something out for Heroku support (related to review apps).


KeyURL should be using Key.Kid rather than ID

In the PowerShell sample on "Azure Key Vault without Role Separation (Example)" it states
$cmkSettings = New-SqlAzureKeyVaultColumnMasterKeySettings -KeyURL $akvKey.ID
This will work for most connections and drivers, but not for all. For example, the ODBC driver has an issue with it. A better setting should be
$cmkSettings = New-SqlAzureKeyVaultColumnMasterKeySettings -KeyURL $akvKey.Key.Kid
The difference between the two is that $avkKey.ID will include the port number (:443) in the url while akvKey.Key.Kid does not. Next to being the more correct and logical representation, it will also avoid potential issues with drivers like the ODBC one.
Actually, it might be best to extend the documentation with a note on this. The exact same problem exists for Azure Disk Encryption and is well documented over there. See the last paragraph of the Set up a key encryption key (optional) . The accompanying sample on that page does it correctly:
$keyEncryptionKeyUrl = (Get-AzKeyVaultKey -VaultName $KeyVaultName -Name $keyEncryptionKeyName).Key.kid;

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

ID: f1572cf3-2c25-0de0-691c-10d6bf3388bc
Version Independent ID: 759b556c-4077-48b5-dc17-d5886d123a6b
Content: Provision Always Encrypted keys using PowerShell - SQL Server
Content Source: docs/relational-databases/security/encryption/configure-always-encrypted-keys-using-powershell.md
Product: sql
Technology: security
GitHub Login: @jaszymas
Microsoft Alias: jaszymas

@ydhondt -- thank you for your considered feedback.
@jaszymas -- please look into this issue.

@ydhondt -- thank you for your considered feedback.
@jaszymas -- please look into this issue.

This has been addressed in https://github.com/MicrosoftDocs/sql-docs-pr/pull/18481#issuecomment-773511729.

#please-close


Raise warning when size_index set to non-numeric dimension

As suggested in https://github.com/ioam/holoviews/issues/982 currently you get an uninformative exception when setting the size_index option to a non-numeric dimension. This raises a warning and adds unit tests to ensure the warning is raised.

I think you could shorten this a bit and avoid some repetition with something like this:
sizes =  self._apply_size_index(element, self.size_index)

This could be implemented in a common base class and would always return sizes, issuing the warning when  the dimension type is inappropriate.

This could be implemented in a common base class and would always return sizes, issuing the warning when the dimension type is inappropriate.

I've so far refrained from shared baseclasses for ElementPlots because a fair amount of the API is different. I'd be happy to factor it out into the shared compute_sizes function that already exists.

I'd be happy to factor it out into the shared compute_sizes function that already exists.

That also makes sense.

Unfortunately I didn't manage to factor out much, the warning needs the dimension and element name to be useful and I didn't want to add even more arguments to the compute_sizes function.

Ok, nevermind then. Merging.


feature request: Cast plain object to mongoose document

RE: http://stackoverflow.com/questions/24190478/cast-plain-object-to-mongoose-document
When mongoose loads data from the database, it converts (casts) that data into instances of mongoose Document.  It would be nice if this functionality was exposed to the outside world, or if mongoose would provide some sort of best practices recommendation.  I am posting this request because other users on SO voted for it.

There's a Model.hydrate() function in 4.0.0-rc1 that should be helpful. See unstable docs

Well, there's no way to mark fields as modified originally, because you don't know what was modified before you hydrated the raw data.  I don't understand what you mean by non-hydrated fields though - hydrate works pretty much the same as new Model(data) AFAIK

Thanks for the quick response.  Imagine a basic Person model: _id, first_name, last_name, email - all fields are required.  A user of my app updates the email address for an existing record and clicks Save.  Here is the data which is posted to the server:
{ "_id": "7qhjf...89s", "email"<EMAIL_ADDRESS>}

My service then hydrates a Person document with _id and email fields only.  At this point I would manually mark the email field as modified and then call save().  I would expect the new email address to be validated and persisted to the database without triggering validation errors on the other fields.  It would be analogous to the following:
Person.findById("7qhjf...89s", "email", function(err, person) {
    if(err) // throw error
    person.email =<EMAIL_ADDRESS>    person.save();
});

The "second" parameter I am suggesting is for hydrate to assume that everything is modified and save us the step of marking fields as dirty.  Here's a simplified implementation - extending code you referenced earlier:
Model.hydrate = function (obj, allModified) {
  var model = require('./queryhelpers').createModel(this, obj);
  model.init(obj);

  if(allModified) {
    for(var prop in obj) {
      model.markModified(prop);
    }
  }
  return model;
};

Why don't you just use new Person(req.body)? Hydrate is mostly meant to take raw data from the database.

Correct me if I'm wrong, but mongoose would treat that object as a "new" person.  Not only is isNew === true, but the version starts at 1, the doc will be inserted vs. updated, and [who knows what else mongoose does internally with new documents].  The use case in my last example is simple and I would really use Model.update in that scenario - so please don't get bogged down on the implementation details.  Here's the broader use case which drove me to create the SO question I referenced earlier:
I have data: a plain 'ol javascript object.  At one point in time this object came from a mongo database - this I know for sure.  The data has been to the front end, around the world, and back to me for persisting into the originating database.
As it stands, the hydrate() method will allow for this... but hydrate seems to assume that the data is coming directly from the database: none of the fields have been modified yet, all paths will undergo validation on save, etc.  What about data that came from [anywhere not the database] but we know originated in the database?  The data may or may not have all fields with it.

Ahhhh I see your point. So how hydrate works is that all fields are in "init" state when the model is hydrated, which means validation runs as shown in the commit I just pushed, but no fields are marked as dirty to be saved to the db initially, unless you make changes. IMO this makes sense with how hydrate() is supposed to work: its assumed the data is saved in the db and you got it using the node driver or some other tool.
I think a better tool for your use case would be to simply look up the document from the db by its id, no?

Yes, which is currently what happens: look up a document, update some fields, save().  I guess this is the best pattern.  Another test you might consider is if the "food" field is required and you hydrate a document without it.  I would expect a validation failure there too, right?
If I can imagine a use case where I wouldn't want the error (because the document in the database already contains a valid "food" property), I will post it here.  Otherwise I'm good to close this one out.  Thanks for the discussion, and thanks again for a wonderful open source project.

IMO that's the best pattern. If you really want to avoid the overhead of loading the doc, I'd recommend you just use new MyModel(req.body) and manually set isNew to false. There's also the alternative of using 4.0's update validators.
As for not wanting the error, that's really a case where you should load the doc from the database. You're going to have to ask the database at some point whether there's a valid food property or not, and right now the best way to do that with mongoose is to load the doc. You can get more fine-grained control by asking the node driver to do a count() if you really only want to know if one doc has one property, but this only gives you a performance benefit in a really limited use case.


PHOENIX-6171 Child views should not be allowed to override the parent view PHOENIX_TTL attribute.

@yanxinyi @ChinmaySKulkarni

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
27m  2s
4.x passed

+1 :green_heart:
compile
0m 58s
4.x passed

+1 :green_heart:
checkstyle
2m 45s
4.x passed

+1 :green_heart:
javadoc
0m 43s
4.x passed

+0 :ok:
spotbugs
2m 52s
phoenix-core in 4.x has 957 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
22m 57s
the patch passed

+1 :green_heart:
compile
0m 55s
the patch passed

+1 :green_heart:
javac
0m 55s
the patch passed

-1 :x:
checkstyle
2m 49s
phoenix-core: The patch generated 27 new + 5445 unchanged - 4 fixed = 5472 total (was 5449)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 43s
the patch passed

+1 :green_heart:
spotbugs
3m  3s
the patch passed

_ Other Tests _

-1 :x:
unit
124m  4s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 37s
The patch does not generate ASF License warnings.

192m 37s

Reason
Tests

Failed junit tests
phoenix.end2end.RowValueConstructorOffsetIT

phoenix.end2end.AlterTableWithViewsIT

phoenix.end2end.ConcurrentMutationsExtendedIT

phoenix.end2end.DerivedTableIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/916

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux b072fbaa2ce8 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / fc3d25c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/testReport/

Max. process+thread count
6934 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 16s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
26m 20s
4.x passed

+1 :green_heart:
compile
0m 56s
4.x passed

+1 :green_heart:
checkstyle
2m 44s
4.x passed

+1 :green_heart:
javadoc
0m 44s
4.x passed

+0 :ok:
spotbugs
2m 47s
phoenix-core in 4.x has 956 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
22m 52s
the patch passed

+1 :green_heart:
compile
0m 55s
the patch passed

+1 :green_heart:
javac
0m 55s
the patch passed

-1 :x:
checkstyle
2m 33s
phoenix-core: The patch generated 32 new + 5445 unchanged - 4 fixed = 5477 total (was 5449)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 44s
the patch passed

+1 :green_heart:
spotbugs
3m 45s
the patch passed

_ Other Tests _

-1 :x:
unit
127m 26s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 36s
The patch does not generate ASF License warnings.

199m 22s

Reason
Tests

Failed junit tests
phoenix.end2end.AlterTableWithViewsIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/916

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 3b7e04256ddc 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 2359f54

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/2/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/2/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/2/testReport/

Max. process+thread count
7321 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/2/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@yanxinyi @ChinmaySKulkarni rebased and fixed conflicts

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
5m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
12m 11s
4.x passed

+1 :green_heart:
compile
1m  3s
4.x passed

+1 :green_heart:
checkstyle
2m 37s
4.x passed

+1 :green_heart:
javadoc
0m 59s
4.x passed

+0 :ok:
spotbugs
3m 53s
phoenix-core in 4.x has 954 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
7m 22s
the patch passed

+1 :green_heart:
compile
1m 12s
the patch passed

+1 :green_heart:
javac
1m 12s
the patch passed

-1 :x:
checkstyle
2m 29s
phoenix-core: The patch generated 28 new + 5288 unchanged - 0 fixed = 5316 total (was 5288)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 54s
the patch passed

+1 :green_heart:
spotbugs
3m 56s
the patch passed

_ Other Tests _

-1 :x:
unit
130m  2s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 36s
The patch does not generate ASF License warnings.

175m 25s

Reason
Tests

Failed junit tests
phoenix.end2end.CaseStatementIT

phoenix.end2end.OrphanViewToolIT

phoenix.end2end.OrderByWithServerClientSpoolingDisabledIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/916

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 76c0bc3a23a7 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 135692c

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/testReport/

Max. process+thread count
7005 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@ChinmaySKulkarni @yanxinyi Addressed review comments and rebased to resolve merge conflicts.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
10m 50s
4.x passed

+1 :green_heart:
compile
0m 56s
4.x passed

+1 :green_heart:
checkstyle
2m 14s
4.x passed

+1 :green_heart:
javadoc
0m 46s
4.x passed

+0 :ok:
spotbugs
2m 56s
phoenix-core in 4.x has 953 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 59s
the patch passed

+1 :green_heart:
compile
1m 12s
the patch passed

+1 :green_heart:
javac
1m 12s
the patch passed

-1 :x:
checkstyle
2m 23s
phoenix-core: The patch generated 57 new + 5253 unchanged - 34 fixed = 5310 total (was 5287)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 51s
the patch passed

+1 :green_heart:
spotbugs
4m  5s
the patch passed

_ Other Tests _

-1 :x:
unit
133m 21s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 33s
The patch does not generate ASF License warnings.

169m 20s

Reason
Tests

Failed junit tests
phoenix.end2end.index.GlobalMutableNonTxIndexIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/916

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 9345c7de816f 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / ac0538b

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/3/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/3/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/3/testReport/

Max. process+thread count
6942 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/3/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 46s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
11m 16s
4.x passed

+1 :green_heart:
compile
0m 55s
4.x passed

+1 :green_heart:
checkstyle
2m 22s
4.x passed

+1 :green_heart:
javadoc
0m 44s
4.x passed

+0 :ok:
spotbugs
3m  6s
phoenix-core in 4.x has 953 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 41s
the patch passed

+1 :green_heart:
compile
0m 54s
the patch passed

+1 :green_heart:
javac
0m 54s
the patch passed

-1 :x:
checkstyle
2m 45s
phoenix-core: The patch generated 21 new + 5287 unchanged - 0 fixed = 5308 total (was 5287)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 42s
the patch passed

+1 :green_heart:
spotbugs
3m  1s
the patch passed

_ Other Tests _

-1 :x:
unit
123m 38s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 38s
The patch does not generate ASF License warnings.

159m  9s

Reason
Tests

Failed junit tests
phoenix.end2end.UpsertSelectIT

phoenix.end2end.AlterTableWithViewsIT

phoenix.end2end.DropIndexedColsIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/916

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 09a9e4931dde 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / ac0538b

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/4/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/4/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/4/testReport/

Max. process+thread count
7250 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-916/4/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

JIRA appears to be closed as fixed. Closing PR.


Is this method applicable for multi-camera calibration with inconsistent internal parameters?

I ran the code on a multi-camera dataset. However, the results were terrible. I output the camera parameters and found that all the internal parameters were the same. How can I adjust the config to improve this situation?

FlowMap is designed to be run on continuous video sequences that come from a single camera. It doesn't support unstructured image collections from multiple cameras. The usual approach for that kind of data is to just run COLMAP.


Windows 10, Docker and Mongo: Operation not permitted, terminating

We are running Windows 10 with HyperV and Mongo.
There is a mounted volume to a local data directory. This works in Unix and Mac just fine. We read that this doesn't work in Windows 10 and it's simply not true.
The first time, it works. Then when we stop down mongo and recompose, we get the following error.
If we restart the Docker Service, then it works again until we stop and start Mongo.
mongo      | 2017-07-12T01:55:17.504+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating

Any thoughts or work arounds would be greatly appreciated. Thanks!
Attaching to mongo
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=0bb1e3123750
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] db version v3.5.9
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] git version: d5e9b4994557285017795d9ed9129341314da202
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] modules: none
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] build environment:
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten]     distmod: debian81
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongo      | 2017-07-12T01:55:17.485+0000 I CONTROL  [initandlisten] options: { net: { bindIpAll: true } }
mongo      | 2017-07-12T01:55:17.489+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=481M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
mongo      | 2017-07-12T01:55:17.502+0000 E STORAGE  [initandlisten] WiredTiger error (1) [1499824517:502361][1:0x7f24061bed40], connection: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted
mongo      | 2017-07-12T01:55:17.504+0000 E -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 325
mongo      | 2017-07-12T01:55:17.504+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
mongo      | 2017-07-12T01:55:17.504+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
mongo      | 2017-07-12T01:55:17.504+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
mongo      | 2017-07-12T01:55:17.504+0000 I CONTROL  [initandlisten] now exiting
mongo      | 2017-07-12T01:55:17.504+0000 I CONTROL  [initandlisten] shutting down with code:100
mongo exited with code 100

Currently experiencing a similar issue with Arch Linux.
% docker -v
Docker version 17.07.0-ce, build 87847530f7

% docker volume create mongodb-data
mongodb-data

% docker pull mongo:latest
latest: Pulling from library/mongo
Digest: sha256:bb962ca3964c70069e652e814f7a495db19643ecb5bb62d799f621a68f4da90c
Status: Image is up to date for mongo:latest

% docker run --name mongodb --mount source=mongodb-data,target=/data/db -it mongo:latest --auth
2017-09-24T07:54:43.693+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=3c184948ce5a
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] db version v3.4.9
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] git version: 876ebee8c7dd0e2d992f36a848ff4dc50ee6603e
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] modules: none
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] build environment:
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten]     distmod: debian81
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten]     distarch: x86_64
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2017-09-24T07:54:43.694+0000 I CONTROL  [initandlisten] options: { security: { authorization: "enabled" } }
2017-09-24T07:54:43.699+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=5475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2017-09-24T07:54:43.998+0000 E STORAGE  [initandlisten] WiredTiger error (1) [1506239683:998366][1:0x7f124d450d40], connection: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted
2017-09-24T07:54:43.999+0000 I -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 269
2017-09-24T07:54:44.001+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
2017-09-24T07:54:44.001+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2017-09-24T07:54:44.001+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2017-09-24T07:54:44.001+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2017-09-24T07:54:44.001+0000 I CONTROL  [initandlisten] now exiting
2017-09-24T07:54:44.001+0000 I CONTROL  [initandlisten] shutting down with code:100

Without a data volume:
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=4bb5e913b483
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] db version v3.4.9
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] git version: 876ebee8c7dd0e2d992f36a848ff4dc50ee6603e
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] modules: none
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] build environment:
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten]     distmod: debian81
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten]     distarch: x86_64
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2017-09-24T07:57:09.491+0000 I CONTROL  [initandlisten] options: { security: { authorization: "enabled" } }
2017-09-24T07:57:09.504+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=5475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2017-09-24T07:57:09.745+0000 E STORAGE  [initandlisten] WiredTiger error (1) [1506239829:744983][1:0x7fbbf2b81d40], connection: /data/db/WiredTiger.wt: handle-open: open: Operation not permitted
2017-09-24T07:57:09.746+0000 I -        [initandlisten] Assertion: 28595:1: Operation not permitted src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 269
2017-09-24T07:57:09.749+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 1: Operation not permitted, terminating
2017-09-24T07:57:09.749+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2017-09-24T07:57:09.749+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2017-09-24T07:57:09.749+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2017-09-24T07:57:09.749+0000 I CONTROL  [initandlisten] now exiting
2017-09-24T07:57:09.749+0000 I CONTROL  [initandlisten] shutting down with code:100

This issue seems to be related to NTFS filesystems.
I was starting docker with /usr/bin/dockerd -H fd:// -g <path-to-ntfs-mount> (-g <path> saves images, containers, etc. at <path>)
After changing -g <path> to an ext4 formatted drive, the permission issue was gone.

Thanks @mkroman -- indeed, any limitations on the underlying filesystem are going to be issues with how MongoDB upstream uses files, and not something specific to this image.
Something that might be of interest is that we do have Windows variants of this image which run MongoDB natively on Windows Server Core, and that will likely have more success with Windows filesystems. :+1:

I "fix it" using "Docker Volumes" instead of mounting a directory.

I "fix it" using "Docker Volumes" instead of mounting a directory.

who do it

I "fix it" using "Docker Volumes" instead of mounting a directory.

who to do


[KED-1745] Autoformat viz python code using black

Description
Make sure viz has consistent code formatting standards as the other kedro products.
Development notes
Added black step to make pylint, blacking package/kedro_viz, package/features and package/tests, then ran make pylint and let the autoformatting happen. Only edited the code in 3 places, which I've highlighted below
QA notes

Checklist

[ ] Read the contributing guidelines
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added new entries to the RELEASE.md file
[ ] Added tests to cover my changes

Legal notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

@ZainPatelQB Hey I was just preparing a patch release and noticed that this PR is related to #193 which would be included in the release. Should I wait on this PR to be merged before releasing? Is this PR ready to be merged?

@ZainPatelQB Hey I was just preparing a patch release and noticed that this PR is related to #193 which would be included in the release. Should I wait on this PR to be merged before releasing? Is this PR ready to be merged?

Hey Richard, you can go ahead and release without this -- it's got 0 functionality attached to it and is purely developer experience, so doesn't matter when this gets merged. It's currently blocked on legal (Snyk license is failing) and we're waiting on that. Ignore for now :)

@ZainPatelQB Great, thanks for the clarification :)

I just got legal approval! Let me update Snyk!


Hc 78 add command line support for queues and instance types

Questions will be asked when running sds cloud asg create.
Remove queues and instance types from config.py

add command line support for sds cloud asg create for queues and instances.


Replace HTTPoison with Tesla for flexibility

Changes

Replace use of HTTPoison with Tesla
Update tests & fixtures to expect httpc as the base HTTP library (the default for Tesla)
Bump exvcr version

Resolves #96

Pull Request Test Coverage Report for Build cb61475a0e6a1c5473f3629c51cf78d57767e082-PR-97

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 80.142%

Totals

Change from base Build<PHONE_NUMBER>ec6f2ef7ac531d66519b6ae05dc4a3:
0.7%

Covered Lines:
113

Relevant Lines:
141

💛  - Coveralls

sorry for taking so long in reviweing this, I am a bit busy and moving the repo to contentful-userland has apparently changed notification settings.
Will try ASAP :)

@OldhamMade Could you rebase/merge latest master? :green_heart:

Thank you - this completely went under as I've been swamped with projects during work time and never received a notification for the status checks to pass (which seem to have hung themselves after the repo was moved to another organization)


Merge prTesting_201906051105 branch to master branch

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

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update the Finnish translation

This PR updates the Finnish localization, adding the missing strings and fixing a few typos.

@tlxo Did you notice that Travis CI failed? See the log via "Details link". Relevant line is: I18n::InvalidLocaleData: can not load translations from /home/travis/build/helpyio/helpy/config/locales/fi.yml: #<Psych::SyntaxError: (/home/travis/build/helpyio/helpy/config/locales/fi.yml): mapping values are not allowed in this context at line 202 column 39>


Make outline and implementation not require symbols_in_winbar

Is your feature request related to a problem? Please describe.
I don't want to use the breadcrumbs on top. It takes space and adds noise to the screen.
Describe the solution you'd like
Outline and implementation should work without symbols_in_winbar enabled.
Why is this a requirement?

I can't reproduce.  which version and how you open outline.

Wow, that was incredibly fast.  Thank you!  I had an error in my config and the plugin wasn't initializing correctly.  Sorry about that :(


Free text tags of camps show code in the camp page [Bug] [Front End]

The Problem:
Free text tags of camps show code in the camp page
Steps:

Go to stage spark page
https://spark.staging.midburn.org/he/login?r=/
login using 'Camp manager' profile:
<EMAIL_ADDRESS>Pass: qa123456
click on menu > my camp > edit camp (or the following link:)
https://spark.staging.midburn.org/he/camps/2045/edit
Click on 'פרטים בסיסיים'
under גיפט המחנה'' mark V on other and enter free text (like 'סבבה')
go back to camp view page

Result:
We see code where the free text tag is shown
Expected:
please show only the free text, without the code
see screenshot

Solved in https://github.com/Midburn/spark/pull/736


Hook up scrub toggle in GUI

A Discussion on whether to have this toggle or not:
https://github.com/MLDSAI/OpenAdapt/pull/211#issuecomment-1573849284