[DO NOT MERGE] Fail backup if it already exists in object storage

Fixes #623

I can build this successfully, but can't run it against GCP:
x1c in /home/nrb/go/src/github.com/heptio/ark (git) ncdc-check-for-backup
% GOOGLE_APPLICATION_CREDENTIALS=credentials-ark-gke ./_output/bin/linux/amd64/ark server --log-level debug
INFO[0000] setting log-level to DEBUG
INFO[0000] Starting Ark server v0.9.0-alpha.3-2-ge248811-dirty  logSource="pkg/cmd/server/server.go:100"
INFO[0000] Ensuring namespace exists for backups         logSource="pkg/cmd/server/server.go:250" namespace=heptio-ark
INFO[0000] Namespace already exists                      logSource="pkg/cmd/server/server.go:262" namespace=heptio-ark
INFO[0000] Retrieving Ark configuration                  logSource="pkg/cmd/server/server.go:267"
INFO[0000] Successfully retrieved Ark configuration      logSource="pkg/cmd/server/server.go:285"
INFO[0000] Using default resource priorities             logSource="pkg/cmd/server/server.go:335" priorities="[namespaces persistentvolumes persistentvolumeclaims secrets configmaps serviceaccounts limitranges pods]"
INFO[0000] Configuring cloud provider for backup service  logSource="pkg/cmd/server/server.go:384"
DEBU[0000] starting plugin                               args="[./_output/bin/linux/amd64/ark run-plugin cloudprovider gcp]" logSource="pkg/plugin/logrus_adapter.go:74" path=./_output/bin/linux/amd64/ark
DEBU[0000] waiting for RPC address                       logSource="pkg/plugin/logrus_adapter.go:74" path=./_output/bin/linux/amd64/ark
DEBU[0000] plugin address                                address=/tmp/plugin804103274 logSource="pkg/plugin/logrus_adapter.go:74" network=unix pluginName=ark
2018/06/29 16:04:07 [DEBUG] plugin: waiting for all plugin processes to complete...
DEBU[0000] plugin process exited                         logSource="pkg/plugin/logrus_adapter.go:74" path=./_output/bin/linux/amd64/ark
An error occurred: could not convert gRPC client to cloudprovider.ObjectStore

I notice that pkg/plugin/proto/ObjectStore.proto doesn't have this method added. Should it be there? Likewise, there's no implementation in pkg/plugin/object_store.go

Error came from https://github.com/heptio/ark/blob/master/pkg/plugin/manager.go#L245-L247, which looks like object doesn't conform to the interface to me.

I’ll fix it when I get back to my desk. Thanks for testing!
On Fri, Jun 29, 2018 at 4:23 PM Nolan Brubaker<EMAIL_ADDRESS>wrote:

Error came from
https://github.com/heptio/ark/blob/master/pkg/plugin/manager.go#L245-L247,
which looks like object doesn't conform to the interface to me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/heptio/ark/pull/629#issuecomment-401464375, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAABYog7tYH3DofhMaiLSXkTI8EamGrLks5uBozZgaJpZM4U9ZoP
.

I did some testing and came to the realization that if we have this sequence of events:

Backup my-backup already exists in object storage but not in Kubernetes
Start ark server (backup sync process hasn't run yet)
Immediately run ark backup create my-backup

then this PR results in a backup in Kubernetes called my-backup that has a phase of FailedValidation. When the backup sync controller runs and tries to sync the backup from object storage to Kubernetes, that will end up being a no-op because there's already a backup called my-backup in Kubernetes, even though it's invalid.
If we decide to continue down this path, I can think of a few options, none of which is fantastic:

When the backup sync controller runs, if it sees a backup in Kubernetes whose phase is FailedValidation, delete it, then try to create the backup using the data from object storage.
If the ark server encounters a backup with the same name in object storage, immediately delete the backup from Kubernetes and then create a FailedBackup custom resource that holds the information on the failure, and incorporate this new CRD when listing/getting/describing backups.
Do nothing. Require the user to delete the FailedValidation backup so the sync process can succeed for the backup in question.

@rosskukulinski @heptio/bluesteelsquad

@rosskukulinski I'll list them but I'm not sure they're relevant (will explain after the list):

overlapping included/excluded namespaces (e.g. include foo, exclude foo)
overlapping included/excluded resources (include pods, exclude pods)
backup.spec.snapshotVolumes=true and ark server isn't configured with a pvProvider for snapshots

If there is a backup good in object storage, it was successfully processed and uploaded. If there is a backup bad in Kubernetes that failed validation, it can't be the same backup that's in object storage. Given that object storage is the source of truth, and there's a valid backup there, any invalid backup with the same name in Kubernetes is something else entirely.

Ok.  I'm leaning towards (3) but I'm wondering how common is this situation?  I guess it happens because you found it while testing.  Does the backup-sync happen when Ark server starts up?

@skriss PTAL when you have a moment. If you think the Azure object store changes are too risky, I can back them out.

Closing this in favor of https://github.com/heptio/velero/pull/1390.


CARLA version question

Hello, thank you for the open-source of this great work. I would like to ask if the Carla version used is 9.14 or higher? When I evaluated route_validation.xml, it said that thereis no Town13 in the map. I am not sure whether this is due to the Carla version problem or something else?

Hi, thanks for your interest in the work.
Yes Town 13 is indeed not part of the 9.14 release. To include Town 13 you can either use the official Carla Leaderboard package (https://leaderboard.carla.org/get_started/) which is based on 9.14 but with Town 13 included or directly use the 9.15 version.


Update for RoomOS 11.17

Cisco has released documentation for a new on-premises endpoint software release.

RoomOS 11.17 API documentation PDF

all PDF versions
API documentation website

Release notes
Software downloads

As of 2024-09-09, there is still no API Reference Guide for RoomOS 11.17, which was available for on-premises download 7 weeks ago on 2024-07-18. In its place is a PDF generated from a crappy Word document that describes the API delta between 11.14 and 11.17, and does not follow the API Reference Guide format.

This means that I still cannot generate a new version of this library to target RoomOS 11.17, because I don't have a PDF in the normal format.

11.14
11.17

API Reference Guide
API Descriptions

<IP_ADDRESS> for on-premise devices not registered to Webex was released on 2024-10-07. No new documentation PDFs have been published, though.

Test message to verify email filters


Clickable links as carousel element?

A simple question :  How can I let anchors be active?  As in clickable carousel elements?  Javascript on click?  Is it just a 'preventDefault' preventing anchors from firing?  I haven't looked for myself as yet.

@leggomuhgreggo Please can you link the old issue you are talking about? I cannot find anything about this issue and I'm struggling with this... thank you!


Usage without @feature attribute in step implementation?

The @feature attribute forces tight coupling of step definitions to a specific feature file, which is a documented Cucumber Anti-Pattern.
Is it possible to remove this limitation, so the steps can be resolved from arbitrary elixir scripts inside a designated step definitions directory?

Is it possible to remove this limitation, so the steps can be resolved from arbitrary elixir scripts inside a designated step definitions directory?

Where there is a will there is a way; but it will require some dedication as the current implementation is fully based around @feature. There may also be some unexpected challenges that come about with the way I handle cucumber_expressions that has certain problematic edge cases yet to be ironed out.
I am supportive of a PR that adds this functionality.
As far as rationale goes for my current approach, I elaborated on a version of that in the docs under:

best_practices.enforce_context?

where I also elaborated an example how you can have a balance between reuse and discoverability.
In summary, the disadvantage of having everything globally accessible is that if not done properly, it can make it very difficult to pinpoint where a step has been implemented. While this is my personal concern for a non-trivial project; I also sympathize that others may have a very different opinion on the matter. As such I would like this project to be supportive of that; especially considering the fact that the original thought-leaders advocate this as a best practice as you aptly linked to. However, it should be implemented in such a way that the current functionality is still supported.


Layer controller refactor (take 2)

Continue work from https://github.com/CartoDB/cartodb/pull/10934
We wanted to start with UserTable, but it was not viable as it used a lot of functionality from Layer. So in #10934 we did the Layer model, which should help make the UserTable easier.
This issue will focus on the Layer controller in order to finish adding functionality to the Layer model which may be missing from the layer model unit tests.

Acceptance: basically smoke tests for all things layer-related. Some must-test:

Test everything with Builder and Editor
Custom basemaps (create / delete)
Basemaps (test variants with layers on top and below)
Data and torque layers
Removing a dataset correctly identifies related maps
Cache/embed invalidation upon making changes (this is specially important in editor, which does not have the publish system)


Docker build failing

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Device: Raspberry Pi B+
OS: Linux raspberrypi 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l GNU/Linux

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
I'm trying to provide custom HostAPD configuration for TLWN725n USB WIFI dongle.

@cecchisandrone Thanks for the report. I'll try to reproduce it tonight. Is it possible you are having network trouble.
Are you able to curl -I https://github.com/bhoriuchi/go-bunyan on the pi and get data?

Yes, just tried it.
Sent from iPhone 8
Il 22 mar 2018, 23:27 +0100, Craig Johnston<EMAIL_ADDRESS>ha scritto:

@cecchisandrone Thanks for the report. I'll try to reproduce it tonight. Is it possible you are having network trouble.
Are you able to curl -I https://github.com/bhoriuchi/go-bunyan on the pi and get data?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I'll try figure out why the go get command is failing. However I will also update the source in a bit and include the dependencies so go get will not be needed.

Seems to be working on my development pi. I'm suspecting that it might be docker and it's network.

Can you try docker run --rm -it arm32v7/golang:1.9 /bin/sh -c "go get github.com/bhoriuchi/go-bunyan/bunyan (should simply return without error)
Or shell directly into the container docker run --rm -it arm32v7/golang:1.9 /bin/sh and try
go get github.com/bhoriuchi/go-bunyan/bunyan to confirm that go was able to download the package you could ls -l /go/src/github.com/bhoriuchi/go-bunyan and git a directory listing of the package.
I'm going to close this as a bug but will be curious if this is happening to anyone else. Like I said earlier I'll update the source with the dependencies so it won't need go get however the fact that it's not working for you make me think it has something to do with the docker install or network on the pi.
I am also curious about your docker version and pi version. Can you send me the output of these commands.
cat /proc/cpuinfo | grep Revision
and
docker --version
Thanks!

@cecchisandrone the build no longer needs to run go get

@cjimti, build fails again with the same error:
Sending build context to Docker daemon  2.689MB
Step 1/14 : FROM arm32v7/golang:1.9 AS builder
 ---> 1ba8d01a7dcf
Step 2/14 : ENV GOPATH /go
 ---> Using cache
 ---> 25c2f05a12e8
Step 3/14 : WORKDIR /go/src
 ---> Using cache
 ---> 2179870dcc15
Step 4/14 : RUN mkdir -p /go/src/github.com/cjimti/iotwifi
 ---> Running in 88a2d84ba596
The command '/bin/sh -c mkdir -p /go/src/github.com/cjimti/iotwifi' returned a non-zero code: 139

If I run docker run --rm -it arm32v7/golang:1.9 /bin/sh -c "go get github.com/bhoriuchi/go-bunyan/bunyan" I receive return code 139.
These are the output of commands you requested:
pi@porterbot:~ $ cat /proc/cpuinfo | grep Revision
Revision        : 0010
pi@porterbot:~ $ docker info
Containers: 4
 Running: 0
 Paused: 0
 Stopped: 4
Images: 24
Server Version: 17.12.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 89623f28b87a6004d4b785663257362d1658a729
runc version: b2567b37d7b75eb4cf325b77297b140ea686ce8f
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.59+
Operating System: Raspbian GNU/Linux 9 (stretch)
OSType: linux
Architecture: armv6l
CPUs: 1
Total Memory: 244MiB
Name: porterbot
ID: RLWE:WUTC:3OS6:SZJG:QOVF:UV4E:H73C:E2CQ:GHAC:AKM6:E2XN:WVKG
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

Anyway I'm pretty sure that everything is due to Rpi B+ that is ARMv6.

I solved using arm32v6/golang:alpine. No I have HostAPD error due to missing driver:
"HOSTAPD GOT: Line 13: invalid/unknown driver 'rtl871xdrv'
I have to check better.

My image will only run on a pi 3 (arm v7) and using the nl80211 driver (with the onboard wifi). I plan to make another public image for the Pi 2 and allow the interface and driver to be configured but it will be a week or so as I am swamped with work at the moment.
In the output you sent it looks like it is having trouble parsing the config. Did you mount the config?
see IOT Wifi Configuration
It was also unable to setup the uap0 interface, this could be due to not running the container with --privileged and --net host. see Docker run
Looks like better error messages are needed on my end. However it is not really intended for a Pi 2 but since I am planning to support the 2 in the future (as well as OrangePi) this helpful, thank you.

I used the command line you suggest:
docker run --rm --privileged --net host
-v $(pwd)/wificfg.json:/cfg/wificfg.json
cjimti/iotwifi
After having edited wificfg.json. It seems that config is parsed correctly but HostAPd fails to run due maybe to a wrong configuration for the USB dongle used.

@cecchisandrone thanks for the update. Looks like you are running an  original Pi Model B+. I'll see if I can dig one up around here and also look into supporting more drivers.
This looks interesting Hostapd driver for RTL8188{C|CU|CUS} wifi chips.
I'll put out a release soon with the ability specify the driver in the config, in your case driver=rtl871xdrv

If you want to hard code it in the source for testing you can find where the driver should be specified
here and here adding driver=rtl871xdrv to the hostapd configuration.

Great, I'll give a try. I just tried modifying wpacfg.go. Thanks

This is the output now:
{"hostname":"porterbot","level":30,"msg":"Starting IoT Wifi...","name":"iotwifi","pid":0,"time":"2018-03-                                                                       23T17:38:22.856Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HTTP Listening on 8080","name":"iotwifi","pid":0,"time":"2018-0                                                                       3-23T17:38:22.867Z","v":0}
{"hostname":"porterbot","level":30,"msg":"Loading IoT Wifi...","name":"iotwifi","pid":0,"time":"2018-03-2                                                                       3T17:38:22.869Z","v":0}
{"hostname":"porterbot","level":30,"msg":"Starting Hostapd.","name":"iotwifi","pid":0,"time":"2018-03-23T                                                                       17:38:22.872Z","v":0}
{"hostname":"porterbot","level":30,"msg":"Hostapd CFG: interface=uap0\nssid=iot-wifi-cfg-3\nhw_mode=g\nch                                                                       annel=6\nmacaddr_acl=0\nauth_algs=1\nignore_broadcast_ssid=0\nwpa=2\nwpa_passphrase=iotwifipass\nwpa_key_                                                                       mgmt=WPA-PSK\nwpa_pairwise=TKIP\nrsn_pairwise=CCMP\ndriver=rtl871xdrv","name":"iotwifi","pid":0,"time":"2                                                                       018-03-23T17:38:23.137Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: random: Trying to read entropy from /dev/random","                                                                       name":"iotwifi","pid":0,"time":"2018-03-23T17:38:23.253Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: Configuration file: /dev/stdin","name":"iotwifi","                                                                       pid":0,"time":"2018-03-23T17:38:23.261Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: Line 13: invalid/unknown driver 'rtl871xdrv'","nam                                                                       e":"iotwifi","pid":0,"time":"2018-03-23T17:38:23.274Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: 1 errors found in configuration file '/dev/stdin'"                                                                       ,"name":"iotwifi","pid":0,"time":"2018-03-23T17:38:23.282Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: Failed to set up interface with /dev/stdin","name"                                                                       :"iotwifi","pid":0,"time":"2018-03-23T17:38:23.287Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: hostapd_init: free iface 0xb6fb4010","name":"iotwi                                                                       fi","pid":0,"time":"2018-03-23T17:38:23.294Z","v":0}
{"hostname":"porterbot","level":30,"msg":"HOSTAPD GOT: Failed to initialize interface","name":"iotwifi","                                                                       pid":0,"time":"2018-03-23T17:38:23.297Z","v":0}

@cecchisandrone yeah invalid/unknown driver 'rtl871xdrv'. need to get
rtl871xdrv driver installed.

...but a rebuild hostapd will also be needed. So I'll take a look at it this weekend. Would be nice to have a version that runs on older Pis.

Cool, thanks for this. Useless to say how many times in IOT projects this task is done, doing that with your approach is really smart and simple.


bugfix: issue #3910

Fixes a regression introduced by the async*/await* feature and changes to the await translation.
The bug was trigged by a pattern matching local async function. Desugar.ml pushes the pattern match into the body of the function, but outside the async expression, obscuring the async body from await.ml.
The fix here is to push the pattern match into the body of the async instead during lowering, as we do for shared functions already. Unfortunately, this does change the semantics - delaying the pattern match (failure) to the async computation where it is reported as an error result, not an eager trap - do we care?
Update: I think we would care since the ast interpreter and ir semantics won't agree unless we

[ ]  reject refutable pattern in local async functions.

Or figure out a better solution.

[ ] minimize test and write some more, including eval

Superseded by #3916


invite me to organization

Contact Details
<EMAIL_ADDRESS>Discord Username
Aditya Mangal#9378
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@harikanani github-action not working

@adityamangal1 it's because the label is not matching I'll change the label according to workflows

As i can check on job status on issue #2 there's something wrong with INVITE_TOKEN.


Collin branch

add css grid styling
add createBoard function with test of object.entries method to loop through category questions and post to html
create board template with two category titles and give questions

Looks good to merge to me!

hey this looks great


Issue with import tsv files containing zero-padded numbers

I'm using clickhouse for the first time, and when I'm doing import like this
cat /home/data/XDR_IMPORT_1001_20001010_000001.tsv | clickhouse-client --password=123 --query="INSERT INTO ts FORMAT TSV";
It gives me error : Column 13, name: dpc, type: Nullable(Int32), parsed text: "0" ERROR: garbage after Nullable(Int32): "3242"
And this is because i have a column (dpc) in type Int32 and the value of this column is 03242, so it seems the import process takes only 0 and trying to find the tap after it
Any help please ?

Confirmed:
clickhouse-client --query='create table x( c1 Nullable(Int32), c2 Nullable(Int32)) Engine=TinyLog'

printf "0123\t01234\n" | clickhouse-client --query='insert into x format TSV' --stacktrace
Code: 27. DB::Exception: Cannot parse input: expected \t before: 123\t01234\n: (at row 1)

Row 1:
Column 0,   name: c1, type: Nullable(Int32), parsed text: "0"
ERROR: garbage after Nullable(Int32): "123<TAB>01234<LINE FEED>"

Stack trace:
0. clickhouse-client(StackTrace::StackTrace()+0x22) [0x7808852]
1. clickhouse-client(DB::Exception::Exception(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x22) [0x39fe402]
2. clickhouse-client(DB::throwAtAssertionFailed(char const*, DB::ReadBuffer&)+0x138) [0x71cb7e8]
3. clickhouse-client(DB::TabSeparatedRowInputStream::read(std::vector<COW<DB::IColumn>::mutable_ptr<DB::IColumn>, std::allocator<COW<DB::IColumn>::mutable_ptr<DB::IColumn> > >&, DB::RowReadExtension&)+0x1cb) [0x6b659cb]
4. clickhouse-client(DB::BlockInputStreamFromRowInputStream::readImpl()+0x168) [0x6e2ec48]
5. clickhouse-client(DB::IBlockInputStream::read()+0x188) [0x6613f28]
6. clickhouse-client(DB::AsynchronousBlockInputStream::calculate()+0x58) [0x660cd68]
7. clickhouse-client() [0x660d140]
8. clickhouse-client(ThreadPoolImpl<ThreadFromGlobalPool>::worker(std::_List_iterator<ThreadFromGlobalPool>)+0x1af) [0x71aaecf]
9. clickhouse-client(ThreadFromGlobalPool::ThreadFromGlobalPool<ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::function<void ()>, int, std::optional<unsigned long>)::{lambda()#3}>(ThreadPoolImpl<ThreadFromGlobalPool>::scheduleImpl<void>(std::function<void ()>, int, std::optional<unsigned long>)::{lambda()#3}&&)::{lambda()#1}::operator()() const+0x3c) [0x71ac31c]
10. clickhouse-client(ThreadPoolImpl<std::thread>::worker(std::_List_iterator<std::thread>)+0x1af) [0x71aa0af]
11. clickhouse-client() [0xb299d6f]
12. /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7fe6e93c06db]
13. /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fe6e8b4788f]

So we dont have any solution right now for this issue ?

Only workarounds. Like use another format (CSV for example), reformat numbers with some simple regexp, read to temporary table as String, or use clickhouse-local as preprocessor: https://www.altinity.com/blog/2019/6/11/clickhouse-local-the-power-of-clickhouse-sql-in-a-single-command

The fix is easy - check here:
https://github.com/yandex/ClickHouse/blob/3c7178a8d1c642b92782e2ae27483e88e14307f0/dbms/src/IO/ReadHelpers.h#L349-L354
But it also require test case.

Could you please elaborate more what should i do to apply this fix in my case ?
Another question, i have around 7800 files, and i need parallel import, how i can do it ? and how i can tell clickhouse to use more cpus ?

@filimonov It is documented behaviour and should not be fixed.

documented? didn't see that.
Indeed it can hit the performance in cases where TSV has a lot of zeros - probably testing performance degradation only for that single border case should be ok.

I also cannot find it in documentation (I thought it was there).
Note that parsing numbers starting with zero can be quite dangerous. Example in JavaScript:
var obj = {"x":0123};
alert(obj.x);

var json = '{"x":0123}';
alert(JSON.parse(json).x);

In the first example, it will output 83, because JavaScript (as well as C, Perl, PHP...) parses 0123 as octal number.
In the second example, it refused to parse string as JSON (in my Firefox browser) because the spec http://json.org/ doesn't allow numbers with extra leading zeros.

High ratio of zeros in datasets is very common case.
In "NYC taxi" dataset, 60% of all integers are zero.
In "Yandex.Metrica" dataset, 76% of all integers are zero.

@MahmoudGoda0
Workaround:

create a temporary table with String data type instead of integer;
load your data as usual;
insert into destination table with INSERT SELECT query and toInt32 function.

Thanks for this workaround, but i have a table with more than 3 billion rows, and by this workaround it will take lot of time, specially we receive a file (~ 700 K rows) every 11 second.

Thanks for this workaround, but i have a table with more than 3 billion rows, and by this workaround it will take lot of time, specially we receive a file (~ 700 K rows) every 11 second.

I've gave you a link above... :\
clickhouse-local can do that in quite a simple and very efficient way:
cat data.csv | clickhouse-local --table='input' \
--structure="col1 String, col2 String, col3 String" \
--input-format='TSV' \
--query="SELECT toUInt64OrZero(col1) a, toFloat64OrZero(col2) b, col3 c FROM input'" --format=Native\
| clickhouse-client --query='INSERT INTO target_table FORMAT Native'

Please pay attention that when passing Native format columns names / types / order should exactly match in selected stream and inserted stream.

Just to make sure I understand these lines correctly, it will copy the data from from a file "data.csv" (in my case it will be the TSV file, then insert it into "target_table" with the correct type, to remove the zero ?
If this is true, this will work if i pass the folder path to insert all files ?
like this cat *.tsv |......

Yes, it will work as expected.
clickhouse-local works in streaming fashion.

Thanks guys for your support.
I have 2 question please :)
1- Do we have parallel import ? So I can speed up the import time ?
2 - After imported all files, i run query that take some time (23 seconds) and i realized the clcikhouse use only 10 CPUs during the query run time, how i tell clickhouse to use more CPUs( i have 32 CPUs)

You need to run several inserts in parallel, i.e. run that pipe on each file separately in parallel.
Check max_threads setting. Also for small enough queries ClickHouse can decrease the number of threads automatically. Also if you can have concurrent queries - using all cores by single query can be suboptimal.

Thank you very much for your kind support.


Final peer for gateway

Peers topic for new gateway service, updates following WebEx with @andrew-coleman
Type of change

New feature
Documentation update

Description
gateway service running on peers in Fabric v2.4
Related issues
https://github.com/hyperledger/fabric/issues/2807

@Mergifyio backport release-2.4


Windows flow - 3 comments

Had a few specific comments but overall on Windows seemed to flow ok.
Three things we should think about for follow on PRs

can we easily alias minikube kubectl -- to kubectl on all platforms. If so we may want to do that to make most of the instructions more kubernetes generic.
Should we add a registry to podman instead of using $ minikube image push $(minikube ip):42631/nodeserver, again that might be more kubenetes generic.
If 1 and 2) work out then I wonder if we could have 2 options.  1 to install minikube and 1 to use the RH sandbox. If the rest of the instructions just used kubectl then there might not be any other differences in the instructions other than how you set up kubectl (aliast for minikube or alias to oc for sandbox) and the registry set up for podman (registry in minikube or your registry in sandbox)

Originally posted by @mhdawson in https://github.com/nodeshift/tutorial/issues/19#issuecomment-1233435402

I think we've explored the different issues mentioned here.  closing


Incorrect Server URL appearing in the Home Page

Environment
IS 5.4.0 Cluster setup (2 nodes) fronted by nginx
JDK - 1.8.0_45
DB - Mysql 5.6
OS - ubuntu
Email as user enabled
Steps to recreate the issue

Configure IS server with hostname
Start the IS server and go to home page

Observations
Server URL not appearing correctly

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


the dataset of CVPR2022 Competition

Are the corresponding datasets of CVPR2022 Competition MOTS and MOT respectively MOTS2020Images and MOT2020Images?
Thanks

Yes

您好，邮件已收到，我会尽快处理，谢谢。

您好，邮件已收到，我会尽快处理，谢谢。


feat: add pre commit hook that checks if make proto-all should be run

Description
Adds pre commit hook that checks if make proto-all should be run.
closes: #6668

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[x] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[x] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

hi @PanGan21, unfortunately we realized that a pre-commit would be very time-consuming and disrupting for the dev workflow and we decided to abandon this issue. Thanks for taking to time to work on it, really appreciated!


Add blog post for responsive_ux feature rollout

Post to announce the changes before the final rollout.

:heavy_check_mark: Deploy preview for openbuildservice ready!
:hammer: Explore the source changes: ce4229c2e7d7b0eb82396c7277af6549a850344c
:mag: Inspect the deploy logs: https://app.netlify.com/sites/openbuildservice/deploys/5ffdda3ccdfccc0008c28aac
:sunglasses: Browse the preview: https://deploy-preview-277--openbuildservice.netlify.app

:heavy_check_mark: Deploy preview for openbuildservice ready!
:hammer: Explore the source changes: ce4229c2e7d7b0eb82396c7277af6549a850344c
:mag: Inspect the deploy logs: https://app.netlify.com/sites/openbuildservice/deploys/5ffdda3ccdfccc0008c28aac
:sunglasses: Browse the preview: https://deploy-preview-277--openbuildservice.netlify.app

Wouldn't it be simpler if you just call it "responsive navigation" instead of making this artificial difference between new navigation and responsiveness?
I think this would greatly simplify the message.

Wouldn't it be simpler if you just call it "responsive navigation" instead of making this artificial difference between new navigation and responsiveness?
I think this would greatly simplify the message.

Wouldn't it be simpler if you just call it "responsive navigation" instead of making this artificial difference between new navigation and responsiveness?

But the navigation is not the only thing we have adapted to become responsive.
The user is going to notice many other changes apart from the navigation areas and I want to warn about that.
Anyway, I'll try to simplify or talk about the new navigation inside a "redesigned responsive layout" instead of about "responsive navigation".

Wouldn't it be simpler if you just call it "responsive navigation" instead of making this artificial difference between new navigation and responsiveness?

But the navigation is not the only thing we have adapted to become responsive.
The user is going to notice many other changes apart from the navigation areas and I want to warn about that.
Anyway, I'll try to simplify or talk about the new navigation inside a "redesigned responsive layout" instead of about "responsive navigation".

@hennevogel, please have a look at the last changes.

@hennevogel, please have a look at the last changes.

@dmarcoux your suggestions are addressed too. Please have a look.

@dmarcoux your suggestions are addressed too. Please have a look.


assert_ok: Remove Debug requirement for Ok() content

This resolves #2 :)
If there is interest, I can create a similar PR for assert_err!() too.

Looks great!
Any ideas what is happening with Rust 1.15.0 build? Not sure what might cause it here

Any ideas what is happening with Rust 1.15.0 build? Not sure what might cause it here

nope, I'm currently trying to figure it out, but I'm starting to get out of ideas 😅

Still haven't found an explanation for why this is breaking on Rust v1.15. https://github.com/rust-lang/rust/issues/34537 is not that helpful either in this case since it does not talk about forbid at all.
I've found a way to work around it for now, which is disabling the tests module when running with Rust v1.15. Certainly not a particularly great solution, but I'm out of ideas. 😞

I've added similar tests for assert_err!() and assert_some!() now too

Awesome investigation! It does looks like some kind of Rust regression (?), skipping these tests for Rust 1.15 is okay for me.
Is there any other changes you want to add also?

Is there any other changes you want to add also?

my goal was to allow us to use claim in the crates.io codebase to replace our custom t!() macro, and I think these changes should be sufficient for now to allow that. if anything else comes up I might open more PRs :)

Great to hear! Published your changes in the claim = "0.4.0"

https://github.com/rust-lang/crates.io/pull/2962 😉


Update composer dependencies

Because WordPress coding standards 0.13.0 added support for PHP CodeSniffer 3.0.2+

Rebased and bump composer/installers to ^1.4

Thanks 👍


fix: respect base path in the generated OAS

Fixes https://github.com/ardatan/feTS/issues/164

💻 Website Preview
The latest changes are available as preview in: https://533efe55.fets.pages.dev

🚀 Snapshot Release (alpha)
The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package
Version
Info

fets
0.1.4-alpha-20230510121000-0a28784
npm ↗ unpkg ↗

💻 Website Preview
The latest changes are available as preview in: https://f91039a4.fets.pages.dev


[perf] optimise key index

There are two avenues for optimisation here:

There is no need for a reversal and subsequently a copy of the original oplog.values array since this can be handled by a reverse for loop.
Mainly, the handled value instead of being an array it can be an object, resulting in O(1) searches for handled values, instead of having to run a linear search each time an oplog value is added (which actually makes the creation of the index O(1/2 n^2 (n + 1)) - Ι think...)

looks great, thanks for opening this. if you could remove the ; semi-colons to match our standard code style that would be great.

Thanks for merging! Adding some prettier rules would be also nice to enforce these code style rules.

Adding some prettier rules would be also nice to enforce these code style rules.

Yes, in the main repo we have some eslint rules in the package. this package may eventually be a part of the main repo with the other stores and orbit-db-store.


resources: update "How to restore a wallet from mnemonic seed" user guide

Ready for review

I think this guide could be shorter.

I agree.

It would also be better if the original structure could be preserved. We have multiple translations for this guide and will be a waste to lose them because styiling changes.
Personally, where possible, i would prefer to keep the structure as it is (maybe keeping the additional 'When should I restore a wallet?') to avoid completely disregarding the translations we have, some of which were made by CCS funded contributors and funded by the community not long ago (for example German and Dutch).

Current guide is really low-quality and with outdated screenshots. I don't think it needs to be preserved.

Also, some sections that include more than 1 paragraph and images are duplicated for CLI and GUI. Would be better to have structure that include both, so that the text is not unnecessarely longer

Created a dedicated section to explain restore height in details.

Ready to be reviewed

I forgot to mention before that you don't have to update every single translation manually. We have po4a which does that work for us (we will have to run it anyway). See https://github.com/monero-project/monero-site/blob/master/po/po-update.sh. The config file will be added after the changes to the english file are merged.

Ok, I left only the English version changes.


ImportError: cannot import name 'multiarray'

I am getting an error.  I have ran the requirements without issues and I am running it with Python 3.6 on Ubuntu 16.04 LTS.  What is wrong?
$ python3.6 src/chess_zero/run.py sl
Traceback (most recent call last):
File "src/chess_zero/run.py", line 19, in
from chess_zero import manager
File "src/chess_zero/manager.py", line 10, in
from .config import Config
File "src/chess_zero/config.py", line 6, in
import numpy as np
File "/usr/lib/python3/dist-packages/numpy/init.py", line 180, in
from . import add_newdocs
File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in
from numpy.lib import add_newdoc
File "/usr/lib/python3/dist-packages/numpy/lib/init.py", line 8, in
from .type_check import *
File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in
import numpy.core.numeric as _nx
File "/usr/lib/python3/dist-packages/numpy/core/init.py", line 14, in
from . import multiarray
ImportError: cannot import name 'multiarray'

It looks like you can't import numpy.. try reinstalling the package?


Implement a new storage type for Datanodes supporting Cassandra DB

Description
Apache Cassandra is a widely used NoSQL Database. The purpose of this issue is to implement a Cassandra Datanode similar to the MongoDatanode.
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%.
[ ] Create related issue in taipy-doc for documentation and Release Notes.
[ ] Check if a new demo could be provided based on this, or if legacy demos could be benefit from it.
[ ] Ensure any change is well documented.

Code of Conduct

[x] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

Hi @jrobinAV , I would like to work on this issue under Hacktoberfest

Hi @jrobinAV If not yet taken up by anyone I would love to take it up.

This sounds interesting to me please assign it to me @jrobinAV

@Saloni0512 Thanks for your help. You are assigned.
@RaedenCodes Do not hesitate to look at the many other issues open to contribution. They are labeled "good first issue" or "Help wanted". The ones rewarded for the Hacktoberfest event also have the "hacktoberfest " label.

Assign this to me i interested

@snehaamujri, sorry, this issue has already been assigned

Hey @jrobinAV, in order to solve the given issue, I just need to push code in the data_node_config.py file right? It's my first time contributing to a large code base, so want to make sure of it.

Hi @Saloni0512,
The data_node_config.py file should contain the method to configure the CassandraDatanode.
However the CassandraDatanode should be implemented in a dedicated file taipy/core/data/cassandra.py.

Hey @jrobinAV I have been sick since the past few days, I am working on my PR as of now, will definitely create a PR by tonight. Sorry for the delay

@Saloni0512 No problem. The previous message was an automatic reminder.
Take the time you need.

Description
Apache Cassandra is a widely used NoSQL Database. The purpose of this issue is to implement a Cassandra Datanode similar to the MongoDatanode.
Acceptance Criteria

[ ]  Ensure new code is unit tested, and check code coverage is at least 90%.
[ ]  Create related issue in taipy-doc for documentation and Release Notes.
[ ]  Check if a new demo could be provided based on this, or if legacy demos could be benefit from it.
[ ]  Ensure any change is well documented.

Code of Conduct

[x]  I have checked the existing issues.
[ ]  I am willing to work on this issue (optional)

I am willing to work on this issue @jrobinAV

@hustler0109 You have been assigned. Thank you for your help. Feel free to submit your PR or collaborate with the other assignees.


mobile view navbar fixed

FIXES: #1736
Before:
https://github.com/anuragverma108/SwapReads/assets/169196836/8a09d914-3f12-43a9-b973-241c24d614fa
After:
https://github.com/anuragverma108/SwapReads/assets/169196836/d30a9fe2-76c6-4fed-b8f0-689e160d7f9f
Type of PR

[X] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes. Make sure to attach before & after screenshots in your PR.]
Checklist:

[X] I have made this change from my own.
[X] I have taken help from some online resources.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

Conflicting files
index.html
Please see the conflicts highlighted in the image above. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


[DE] Add missing window sentences

It seems that the window device_class isn't handled in de at all.

superseded by #2266


Need ownerRef in GET /layout/{layoutId}

In a distributed multi carrier landscape Meta data end points is missing an owner attribute and parameter to divide the data between different owner (carriers).
The most important resource to handle in Sweden is layouts. We suggest to make a new endpoint

Also the response need the ownerRef to make it more transparent

We currently do not use any other Metadata endpoints but probably the same problem are applicable for at least products resources.
This is quite urgent in Sweden since the place-map is on top of our development this summer/autumn, so we want to have this in version 3.0.*

Proposal
Model layout-id as a pair consisting of (layout,provider)


Camera Zones

Only enabled in cinematic mode, or when Twinsen dirMode is not manual, for now.
Will try to apply it in regular gameplay in a nice way in a future PR.
Preview here: https://pr-520.lba2remake.net

Playing the Trulu exit scene through the camera still does some weird stuff I guess this is because we're tracking Twinsen rather than leaving the camera static like in the original game. This results in some strange camera angles that don't look great (clipping through things etc.).
Not sure what's best to do but this is a decent start.
The other thing we need is the CAMERA_FOLLOW life script command implemented e.g. so the camera follows the boat when it leaves the harbour etc.

Yeah, definitely not perfect, I'll iterate on this.


2023-07-17 16:02:49.951   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ REQUEST id=8, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:49.951   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ REQUEST id=8, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:49.951   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=11, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:49.952   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=11, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:49.952   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=12, [ Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.952   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=12, [ Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.952   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=13, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.952   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=13, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.954   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=14, [ Transports: WIFI Capabilities: INTERNET&TRUSTED&NOT_VPN Uid: 1001] ]
2023-07-17 16:02:49.954   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=14, [ Transports: WIFI Capabilities: INTERNET&TRUSTED&NOT_VPN Uid: 1001] ]
2023-07-17 16:02:49.955   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&VALIDATED Uid: 1000] ]
2023-07-17 16:02:49.955   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&VALIDATED Uid: 1000] ]
2023-07-17 16:02:49.956   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=16, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.956   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=16, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.956   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=17, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.956   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=17, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.956   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=18, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.957   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=18, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.971   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=19, [ Transports: WIFI Capabilities: NOT_VPN] ]
2023-07-17 16:02:49.972   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=19, [ Transports: WIFI Capabilities: NOT_VPN] ]
2023-07-17 16:02:49.972   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=20, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10054] ]
2023-07-17 16:02:49.973   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=20, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10054] ]
2023-07-17 16:02:49.973   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=22, [] ]
2023-07-17 16:02:49.974   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=22, [] ]
2023-07-17 16:02:49.978   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=23, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.978   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=23, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.979   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.979   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.980   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=25, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.980   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=25, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.980   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ REQUEST id=26, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.980   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ REQUEST id=26, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:49.980   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=28, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.980   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=28, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:49.981   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=58, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 5013] ]
2023-07-17 16:02:49.981   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=58, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 5013] ]
2023-07-17 16:02:49.983   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=126, [ Transports: CELLULAR|WIFI|ETHERNET Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10165] ]
2023-07-17 16:02:49.983   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=126, [ Transports: CELLULAR|WIFI|ETHERNET Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10165] ]
2023-07-17 16:02:49.984   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1074, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10175] ]
2023-07-17 16:02:49.984   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1074, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10175] ]
2023-07-17 16:02:49.985 18298-18388 HONEYBOARD              com.samsung.android.honeyboard       I  c onCapabilitiesChanged network : 601 current network state : -1
2023-07-17 16:02:49.986   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1079, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:49.986   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1079, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:49.987   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1099, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:49.987   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1099, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:49.988   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1100, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:49.988   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1100, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:49.989   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1101, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:49.990 22212-22255 Carnival-N...rManager() com.samsung.android.app.spage        I  onAvailable
2023-07-17 16:02:49.991  1382-1382  SecStatusBarWifiView    com.android.systemui                 D  updateState: WifiIconState(resId=2131232731, visible=true, activityId=2131232737)
2023-07-17 16:02:49.995   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1101, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:49.996   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1102, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:49.997   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1102, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:49.997   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1181, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:49.998   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1181, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:49.998   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1182, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:49.999   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1182, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:49.999 22212-22255 Carnival-N...rManager() com.samsung.android.app.spage        I  onNetworkRecovered
2023-07-17 16:02:50.000 22212-22255 Carnival-S...tManager() com.samsung.android.app.spage        I  onNetworkRecovered
2023-07-17 16:02:50.001   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1242, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.002   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1242, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.002   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1243, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.002   971-1249  WifiConnec...Controller system_server                        I  mNetworkCallback onCapabilitiesChanged: 601[ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps SignalStrength: -63 SSID: "ssid name removed"]
2023-07-17 16:02:50.003   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1243, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.003   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1764, [ Capabilities: NOT_RESTRICTED Uid: 10088] ]
2023-07-17 16:02:50.003   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1764, [ Capabilities: NOT_RESTRICTED Uid: 10088] ]
2023-07-17 16:02:50.004   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1768, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.006   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1768, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.008   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.008   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.009   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=2128, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.010   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=2128, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.010   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=2129, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.011   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=2129, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.011   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=3094, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10175] ]
2023-07-17 16:02:50.012   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=3094, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10175] ]
2023-07-17 16:02:50.013   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=3326, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10074] ]
2023-07-17 16:02:50.014   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=3326, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10074] ]
2023-07-17 16:02:50.014   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=3390, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247] ]
2023-07-17 16:02:50.015   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=3390, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247] ]
2023-07-17 16:02:50.086 18298-18298 HONEYBOARD              com.samsung.android.honeyboard       I  c onCapabilityChanged network = 601
2023-07-17 16:02:50.086 18298-18298 HONEYBOARD              com.samsung.android.honeyboard       I  c onCapabilityChanged  resetStates
2023-07-17 16:02:50.089 18298-18298 HONEYBOARD              com.samsung.android.honeyboard       E  c activeNetwork is null
2023-07-17 16:02:50.160 20035-20035 BoundBrokerSvc          com.google.android.gms               D  onBind: Intent { act=com.google.android.gms.safetynet.service.START pkg=com.google.android.gms }
2023-07-17 16:02:50.161 20035-20035 BoundBrokerSvc          com.google.android.gms               D  Loading bound service for intent: Intent { act=com.google.android.gms.safetynet.service.START pkg=com.google.android.gms }
2023-07-17 16:02:50.304   971-1250  ConnectivityService     system_server                        D  updateCapabilities: oldCap = [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps Specifier: <WifiNetworkAgentSpecifier [WifiConfiguration=, SSID="ssid name removed", identifier=80:20:da:f0:cf:ff, mOriginalRequestorUid=-1, mOriginalRequestorPackageName=]> SignalStrength: -63 SSID: "ssid name removed"], newCap = [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&NOT_CONGESTED LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps Specifier: <WifiNetworkAgentSpecifier [WifiConfiguration=, SSID="ssid name removed", identifier=80:20:da:f0:cf:ff, mOriginalRequestorUid=-1, mOriginalRequestorPackageName=]> SignalStrength: -64 SSID: "ssid name removed"]
2023-07-17 16:02:50.310   971-1250  ConnectivityService     system_server                        D  notifyType CALLBACK_CAP_CHANGED for NetworkAgentInfo [WIFI () - 601]
2023-07-17 16:02:50.311   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ REQUEST id=1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:50.311   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=4, [ Capabilities: FOREGROUND] ]
2023-07-17 16:02:50.311   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=4, [ Capabilities: FOREGROUND] ]
2023-07-17 16:02:50.311   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=5, [ Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 1000] ]
2023-07-17 16:02:50.312   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=5, [ Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 1000] ]
2023-07-17 16:02:50.312   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=6, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 1000] ]
2023-07-17 16:02:50.312   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=6, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 1000] ]
2023-07-17 16:02:50.312   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=7, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 1000] ]
2023-07-17 16:02:50.313   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=7, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 1000] ]
2023-07-17 16:02:50.313   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ REQUEST id=8, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:50.313   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ REQUEST id=8, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:50.314   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=11, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:50.314   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=11, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ]
2023-07-17 16:02:50.322  1382-1382  SecStatusBarWifiView    com.android.systemui                 D  updateState: WifiIconState(resId=2131232729, visible=true, activityId=2131232737)
2023-07-17 16:02:50.326   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=12, [ Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.326   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=12, [ Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.327   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=13, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.327   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=13, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.328   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=14, [ Transports: WIFI Capabilities: INTERNET&TRUSTED&NOT_VPN Uid: 1001] ]
2023-07-17 16:02:50.329   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=14, [ Transports: WIFI Capabilities: INTERNET&TRUSTED&NOT_VPN Uid: 1001] ]
2023-07-17 16:02:50.330   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&VALIDATED Uid: 1000] ]
2023-07-17 16:02:50.330   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=15, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&VALIDATED Uid: 1000] ]
2023-07-17 16:02:50.330   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=16, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.330   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=16, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.331   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=17, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.331   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=17, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.331   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=18, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.331   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=18, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.332   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=19, [ Transports: WIFI Capabilities: NOT_VPN] ]
2023-07-17 16:02:50.332   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=19, [ Transports: WIFI Capabilities: NOT_VPN] ]
2023-07-17 16:02:50.333   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=20, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10054] ]
2023-07-17 16:02:50.333   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=20, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10054] ]
2023-07-17 16:02:50.334   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=22, [] ]
2023-07-17 16:02:50.334   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=22, [] ]
2023-07-17 16:02:50.336   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=23, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.337   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=23, [ Transports: WIFI Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.338   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.339   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.348   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=25, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.348   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=25, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.348   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ REQUEST id=26, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.349   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ REQUEST id=26, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 1000] ]
2023-07-17 16:02:50.349   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=28, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.349   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=28, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 1000] ]
2023-07-17 16:02:50.349   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=58, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 5013] ]
2023-07-17 16:02:50.350   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=58, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 5013] ]
2023-07-17 16:02:50.351   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=126, [ Transports: CELLULAR|WIFI|ETHERNET Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10165] ]
2023-07-17 16:02:50.351   971-1249  WifiConnec...Controller system_server                        I  mNetworkCallback onCapabilitiesChanged: 601[ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps SignalStrength: -64 SSID: "ssid name removed"]
2023-07-17 16:02:50.352   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=126, [ Transports: CELLULAR|WIFI|ETHERNET Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10165] ]
2023-07-17 16:02:50.352   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1074, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10175] ]
2023-07-17 16:02:50.353   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1074, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10175] ]
2023-07-17 16:02:50.354 18298-18388 HONEYBOARD              com.samsung.android.honeyboard       I  c onCapabilitiesChanged network : 601 current network state : -1
2023-07-17 16:02:50.356 22212-22255 Carnival-N...rManager() com.samsung.android.app.spage        I  onAvailable
2023-07-17 16:02:50.357 22212-22255 Carnival-N...rManager() com.samsung.android.app.spage        I  onNetworkRecovered
2023-07-17 16:02:50.357 22212-22255 Carnival-S...tManager() com.samsung.android.app.spage        I  onNetworkRecovered
2023-07-17 16:02:50.359   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1079, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:50.360   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1079, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:50.360   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1099, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:50.361   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1099, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:50.361   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1100, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:50.362   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1100, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:50.362   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1101, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:50.362   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1101, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10189] ]
2023-07-17 16:02:50.363   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1102, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:50.363   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1102, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&FOREGROUND Uid: 10189] ]
2023-07-17 16:02:50.364   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1181, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:50.364   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1181, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:50.364   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1182, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:50.365   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1182, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10156] ]
2023-07-17 16:02:50.371   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1242, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.372   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1242, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.373   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1243, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.375   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1243, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10108] ]
2023-07-17 16:02:50.375   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1764, [ Capabilities: NOT_RESTRICTED Uid: 10088] ]
2023-07-17 16:02:50.376   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1764, [ Capabilities: NOT_RESTRICTED Uid: 10088] ]
2023-07-17 16:02:50.377   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=1768, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.378   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=1768, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.379   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=1769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.379   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=1769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.381   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=2128, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.381   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=2128, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.382   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=2129, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.383   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=2129, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10088] ]
2023-07-17 16:02:50.383   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ LISTEN id=3094, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10175] ]
2023-07-17 16:02:50.384   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ LISTEN id=3094, [ Transports: WIFI Capabilities: NOT_RESTRICTED&TRUSTED&NOT_VPN&FOREGROUND Uid: 10175] ]
2023-07-17 16:02:50.385   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=3326, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10074] ]
2023-07-17 16:02:50.386   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=3326, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10074] ]
2023-07-17 16:02:50.386   971-1250  ConnectivityService     system_server                        D   sending notification for NetworkRequest [ TRACK_DEFAULT id=3390, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247] ]
2023-07-17 16:02:50.387   971-1250  ConnectivityService     system_server                        D  sending notification CALLBACK_CAP_CHANGED for NetworkRequest [ TRACK_DEFAULT id=3390, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247] ]
2023-07-17 16:02:50.453 18298-18298 HONEYBOARD              com.samsung.android.honeyboard       I  c onCapabilityChanged network = 601
2023-07-17 16:02:50.454 18298-18298 HONEYBOARD              com.samsung.android.honeyboard       I  c onCapabilityChanged  resetStates
2023-07-17 16:02:50.456 18298-18298 HONEYBOARD              com.samsung.android.honeyboard       E  c activeNetwork is null

I have removed some SSID names, mac addresses etc. Essentially seems like it's trying to connect and failing? I'm not  really sure. None of that happens when the push notification is delivered and appears on the device successfully; when it works, I get logs like
2023-07-17 15:54:07.026   971-1053  ActivityManager         system_server                        I  Start proc 18794:com.app.id/u0a689 for broadcast {com.app.id/com.google.firebase.iid.FirebaseInstanceIdReceiver}

2023-07-17 15:54:07.124 18794-18794 FirebaseApp             pid-18794                            I  Device unlocked: initializing all Firebase APIs for app [DEFAULT]
2023-07-17 15:54:07.153 18794-18794 FirebaseInitProvider    pid-18794                            I  FirebaseApp initialization successful

stopApp runs adb shell am force-stop {appId}, source here. It seems like this interferes with notifications in some way; if there is a notification in the notification tray/centre it will remove it. Also I have observed that if you kill the app using this/stopApp, then send a notification and then start the app, sometime later it might appear in the notification tray. This seems to be very inconsistent though and not good enough for an automated test.

Firstly, I realise now this isn't a Maestro issue. However, it would be useful if Maestro could improve the stopApp command to fix it maybe?
Anyway, the workaround I have come up with so far is to use the server approach hinted at in from #576 and explained here to run some adb commands so that instead of running the stopApp command it will instead run this via the express server:
- pressKey: Home
- runScript:
     file: ../scripts/terminal.js
     env:
       exec: "adb shell am kill com.app.id; adb shell am stack remove $(adb shell \"dumpsys activity recents | sed -n -e '/com.app.id/,/* Recent/ p' | grep stackId | cut -d = -f 2\")"
       async: false

In short:  the command in exec firstly kills the app - which is required to be in the background for that to work. That caused some issues (app crashed after relaunching). I found that after running shell am kill it was still present in the app switcher. So the second command removes it from the app switcher. After this, triggering a notification and it getting delivered, and appearing on the device within a few seconds, seems to be fairly consistent.
I'm not sure this is the best way. I have also considered using adb to show the app switcher with adb shell input keyevent KEYCODE_APP_SWITCH (via the server, although maybe it should be added to maestro's pressKey command). And then swipe on the app to remove it. The app switcher seems slightly inconsistent among Android versions and skins/launchers so I haven't tried it properly yet.
Would appreciate any other views. I will close this for now as I don't think it's a Maestro issue.


Added area-init-size

Added area-init-size option to start with a standard size instead of 200x200
Also did some code rectification. Some things weren't nicely closed.
Removed a console.log that was firing always.

Have you tested this code with all my codepens?

How to test it in all codepens? I didn't change it that much.
And i tested it on my project. Because i need the init functionality.

I tested your codepens with this url.
https://rawgit.com/rickerd/ngImgCropFullExtended/master/compile/unminified/ng-img-crop.js
It works, the circle isn't affected only the rectangle version if altered.
http://codepen.io/anon/pen/bEzvEP

Thank you!
I would try to bring more features as time passes


NoMethodError: undefined method `thread_mattr_accessor' when generating migrations

Whenever you run rails console1984:install:migrations, you receive a NoMethodError.
Output of the command:
rails aborted!
NoMethodError: undefined method `thread_mattr_accessor' for Console1984:Module
/home/robert/critter/config/application.rb:18:in `<main>'
/home/robert/critter/Rakefile:6:in `<main>'
bin/rails:6:in `<main>'
(See full trace by running task with --trace)

@lunaisnotaboy v0.1.20 should fix this problem. We hit it ourselves after updating to official Rails 7.0 😅. I gave it a try and it worked for me but please let me know if it's still failing for you.

@jorgemanrubia The problem occured on v0.1.20. Apologies for not saying so in the beginning.

On a fresh Rails app it worked for me with 0.1.20. Are you certain you are on that version (you can check Gemfile.lock and, also, make sure you stop spring spring stop if you are using it):
[main][~/Projects/test_console]$ bin/rails console1984:install:migrations
Copied migration<PHONE_NUMBER>4357_create_console1984_tables.console1984.rb from console1984
[main][~/Projects/test_console]$ cat Gemfile.lock | grep console1984
    console1984 (0.1.20)
  console1984
[main][~/Projects/test_console]$ bin/rails --version
Rails 7.0.0

Still no. I reinstalled everything, and made sure that it wasn't just the project.
The following link contains my Gemfile and Gemfile.lock files: https://gist.github.com/lunaisnotaboy/7dd1097eed415fa43816fa02fed63070
I am running everything with the latest versions, and Spring was not running.

Hey Luna I can reproduce with that Gemfile, thanks! Taking a look.

Would the project help? Nothing else is in there, as it's a project that was recently generated.

No it's ok, I can work with this, thanks!

Released version 0.1.22 addressing this problem. I'll update audits1984 next (there is another error with the upgrade).

Oh no sorry, it was a problem with my test project and web packer. I think it all should be good if you fetch the latest console1984 @lunaisnotaboy

Thanks!


Documents Get() & GetAll returns nil

We should implement it 🤓
https://github.com/ioki-mobility/go-outline/blob/4bf018c9998aca9fee1be333048e860f44d5ca61/documents.go#L21-L29

this is not part of first milestone ;)

Second milestone is for documents related functionality :)

That is why I labelled https://github.com/ioki-mobility/go-outline/pull/20 with v0.2.0

But it is already merged 🤔
On Sun, Aug 6, 2023, 12:58 PM Ravi Shekhar Jethani @.***>
wrote:

That is why I labelled #20
https://github.com/ioki-mobility/go-outline/pull/20 with v0.2.0
—
Reply to this email directly, view it on GitHub
https://github.com/ioki-mobility/go-outline/issues/34#issuecomment-1666815094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACOBQ66GTGU2VMMDZPPTKWDXT52DRANCNFSM6AAAAAA3F2SCMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You merged it :smile:  , I wanted to wait for next release cycle...but no worries...


bed file

Hello,
Thanks in advance for your time.  I was wondering if I was doing something wrong configuring the bed file.  This is my source configuration:
{name: 'example_bed',
collapseSuperGroups:true,
uri: 'http://localhost/example.bed.gz',
tier_type: 'tabix',
payload: 'BED'}

This is the bed file I bgzipped and created a tabix index file on it.

chr7    127471196  127472363
chr7    127472363  127473530
chr7    127473530  127474697
chr7    127474697  127475864
chr7    127475864  127477031
chr7    127477031  127478198
chr7    127478198  127479365
chr7    127479365  127480532
chr7    127480532  127481699

Please kindly let me know what I'm doing wrong.
Tom

The "payload" names are case sensitive.  Could you try:
        payload: 'bed'

instead.
Will leave this open until I have a chance to look into an error-handling issue this reveals...

Thank you for your help.  I changed the payload to lowercase, but it still doesn't seem to want to display anything.  Attached is a screenshot.

Try another chromosome. I am seeing a bit g where the first contig ( I my case ) is not working for tabix indexed bed files
Andrew

On Sep 14, 2015, at 6:42 PM, Thomas Yu<EMAIL_ADDRESS>wrote:
Thank you for your help. I changed the payload to lowercase, but it still doesn't seem to want to display anything. Attached is a screenshot.
—
Reply to this email directly or view it on GitHub.

@ajo2995 that sounds as though some lines from your file have been interpreted as header data when making the Tabix index.  Do you have a file I could try?

Okay, found a bug which quite likely explains this and also @ajo2995's problem.  Solution implemented on the 'master' branch (although not currently in the release).
Do re-open if you're still having problems.

That fixed it. Thanks!

Thank you for your help.  This seems to work if I have a bed file that includes all the chromosomes.  However, when I just put the above bed file in, it seems to only plot the first line.

That's very odd and doesn't match the results of my own testing using the file you sent.  Any chance you could send me your .bed.gz and tabix files for that (via offline e-mail probably best).


Missing links with smaller IE browser window size

Repro Streps:

Logn as volunteer using IE
Check the upper right side links for Logout/Change Password/Change Contact Info
Resize IE to a smaller size
Check the the upper right side link again

Result:
The links are missing
Expected Result:
The links should be presented

Fixed in Pull Request #255