Request failed with status 400 due to invalid cookie domain: Cookie 'domain' mismatch - webdriver-io

I am using webdriver io and getting below error.
webdriver: Request failed with status 400 due to invalid cookie domain: invalid cookie domain: Cookie 'domain' mismatch
I have removed node modules and restarted system ,installled again .Still facing issue.These step worked for me earlier but not now.Below are the versions of packages I am using.Chrome version on my system is 91.0.4472.114
── #babel/cli#7.12.10
├── #babel/core#7.12.10
├── #babel/preset-env#7.12.11
├── #babel/register#7.12.10
├── #wdio/allure-reporter#7.7.3
├── #wdio/cli#7.7.4
├── #wdio/devtools-service#7.7.4
├── #wdio/jasmine-framework#7.7.3
├── #wdio/local-runner#7.7.4
├── #wdio/selenium-standalone-service#7.7.4
├── #wdio/spec-reporter#7.7.3
├── #wdio/sync#7.7.4
├── allure-commandline#2.13.8
├── atob#2.1.2
├── eslint-plugin-import#2.22.1
├── eslint#5.16.0
├── fs-extra#7.0.1
├── jasmine-allure-reporter#1.0.2
├── jasmine-expect#4.0.3
├── jasmine#3.7.0
├── lodash#4.17.21
├── prettier#1.18.2
├── randomstring#1.1.5
├── superagent#5.3.1
├── wd#1.13.0
├── wdio-docker-service#2.4.0
├── wdio-timeline-reporter#5.1.4
└── webdriverio#6.12.1

Related

Expo: console.log stopped showing up

SDK Version: 45
Platforms(Android/iOS/web/all): iOS
Add the appropriate "Tag" based on what Expo library you have a question on.
My managed expo project suddenly stopped showing console.log on terminal when I run expo run:ios.
Also, auto bundling on file changes also stopped.
The following is the version information I get when I run npm list.
├── #babel/core#7.18.10
├── #primer/primitives#7.9.0
├── #react-native-async-storage/async-storage#1.17.9
├── #react-native-firebase/analytics#15.3.0
├── #react-native-firebase/app#15.3.0
├── #react-native-firebase/auth#15.3.0
├── #react-native-firebase/firestore#15.3.0
├── #react-navigation/bottom-tabs#6.3.2
├── #react-navigation/native-stack#6.7.0
├── #react-navigation/native#6.0.11
├── #sanity/client#3.3.3
├── #shopify/restyle#2.1.0
├── #types/flat#5.0.2
├── #types/lodash#4.14.184
├── #types/react-native#0.66.21
├── #types/react#17.0.48
├── dotenv#16.0.1
├── expo-apple-authentication#4.2.1
├── expo-av#11.2.3
├── expo-build-properties#0.2.0
├── expo-dev-client#1.0.1
├── expo-splash-screen#0.15.1
├── expo-status-bar#1.3.0
├── expo#45.0.8
├── flat#5.0.2
├── lodash#4.17.21
├── react-dom#17.0.2
├── react-native-pager-view#5.4.15
├── react-native-reanimated#2.8.0
├── react-native-safe-area-context#4.2.4
├── react-native-screens#3.11.1
├── react-native-web#0.17.7
├── react-native#0.68.2
├── react#17.0.2
└── typescript#4.3.5
I solved this problem by upgrading expo sdk from 45 to 46 by executing expo-cli upgrade.
To find more information about expo sdk migration: please refer to "Upgrading your app" section of this post.

Unable to download Tensorflow C Language Bindings as an ExternalProject

I'm trying to include the C language bindings for Tensorflow found at https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-gpu-linux-x86_64-2.5.0.tar.gz in my CMake Project. Unfortunately, it seems as thought nothing is being downloaded, as the TENSORFLOW-prefix/src/TENSORFLOW directory is empty. I'm new to CMake and am not sure where I am going wrong. Any help would be appreciated.
Relevant source:
cmake_minimum_required(VERSION 3.17)
include(ExternalProject)
project(tfexec)
set(CMAKE_CXX_STANDARD 17)
ExternalProject_Add(TENSORFLOW
URL "https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-gpu-linux-x86_64-2.5.0.tar.gz"
CONFIGURE_COMMAND ""
BUILD_COMMAND ""
INSTALL_COMMAND ""
LOG_DOWNLOAD 1
LOG_CONFIGURE 1
LOG_BUILD 1
LOG_INSTALL 1
)
ExternalProject runs at build time, so you actually need to run your build for this to do anything. This is what I see; it seems to be working fine:
alex#Alex-Desktop:~/test$ cmake-3.17 -S . -B build -DCMAKE_BUILD_TYPE=Release
...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/alex/test/build
alex#Alex-Desktop:~/test$ cmake --build build/ -- -v
...
alex#Alex-Desktop:~/test$ tree build/TENSORFLOW-prefix/src/TENSORFLOW
build/TENSORFLOW-prefix/src/TENSORFLOW
├── LICENSE
├── THIRD_PARTY_TF_C_LICENSES
├── include
│   └── tensorflow
│   ├── c
│   │   ├── c_api.h
│   │   ├── c_api_experimental.h
│   │   ├── c_api_macros.h
│   │   ├── eager
│   │   │   ├── c_api.h
│   │   │   ├── c_api_experimental.h
│   │   │   └── dlpack.h
│   │   ├── tensor_interface.h
│   │   ├── tf_attrtype.h
│   │   ├── tf_datatype.h
│   │   ├── tf_file_statistics.h
│   │   ├── tf_status.h
│   │   ├── tf_tensor.h
│   │   └── tf_tstring.h
│   └── core
│   └── platform
│   ├── ctstring.h
│   └── ctstring_internal.h
└── lib
├── libtensorflow.so -> libtensorflow.so.2
├── libtensorflow.so.2 -> libtensorflow.so.2.5.0
├── libtensorflow.so.2.5.0
├── libtensorflow_framework.so -> libtensorflow_framework.so.2
├── libtensorflow_framework.so.2 -> libtensorflow_framework.so.2.5.0
└── libtensorflow_framework.so.2.5.0
7 directories, 23 files

Which elm package versions are installed?

elm-package can manage dependencies for elm, but the only commands it supports (as of version 0.18.0) are install, publish, bump and diff according to running it without arguments. I was expecting something like elm-package list to show the installed packages.
Is there a command to list the currently installed elm package versions?
I think there is no one, but you can execute tree elm-stuff/packages -L 3 --noreport in your command line.
You will get a tree like this:
elm-stuff/packages
├── debois
│   ├── elm-dom
│   │   └── 1.2.3
│   └── elm-mdl
│   └── 8.1.0
├── elm-lang
│   ├── core
│   │   └── 5.1.1
│   ├── dom
│   │   └── 1.1.1
│   ├── html
│   │   └── 2.0.0
│   ├── http
│   │   └── 1.0.0
│   ├── mouse
│   │   └── 1.0.1
│   ├── virtual-dom
│   │   └── 2.0.4
│   └── window
│   └── 1.0.1
├── mgold
│   └── elm-date-format
│   └── 1.2.0
└── thaterikperson
└── elm-strftime
You can also just do cat elm-stuff/exact-dependencies.json, but there is no guarantee of have them installed:
{
"debois/elm-mdl": "8.1.0",
"elm-lang/virtual-dom": "2.0.4",
"elm-lang/mouse": "1.0.1",
"mgold/elm-date-format": "1.2.0",
"elm-lang/dom": "1.1.1",
"elm-lang/html": "2.0.0",
"elm-lang/http": "1.0.0",
"debois/elm-dom": "1.2.3",
"elm-lang/window": "1.0.1",
"elm-lang/core": "5.1.1"
}
If you use the Lighttable editor with the elm-light plug in then you would have a command to show (and add) packages.

ansible: roles structure and variables

I use ansible for a while with standalone playbooks and now would like to configure role structure at my environment.
This is folder structure(example, summarised)
├── hosts
├── playbooks
│   ├── project1-staging.yml
│   └── project1-production.yml
├── roles
│   └── project1-compile
│   ├── files
│   │   └── project1.conf
│   ├── handlers
│   │   └── main.yml
│   ├── meta
│   │   └── main.yml
│   ├── tasks
│   │   └── main.yml
│   ├── templates
│   └── vars
│   └── main.yml
│   └── ec2-create
│   ├── handlers
│   │   └── main.yml
│   ├── meta
│   │   └── main.yml
│   ├── tasks
│   │   └── main.yml
│   ├── templates
│   └── vars
│   └── main.yml
│   └── project1-deploy
│   ├── handlers
│   │   └── main.yml
│   ├── meta
│   │   └── main.yml
│   ├── tasks
│   │   └── main.yml
│   ├── templates
│   └── vars
│   └── main.yml
├── vars.yml
It looks straightforward.
I would like to execute project1-staging.yml playbook to create a new staging environment for specific version, like that;
ansible-playbook project1-staging.yml -e 'version=1'
and playbook below;
---
- name: deploy project1 (staging) {{ version }}
hosts: local
connection: local
roles:
#- project1-compile version={{ version }}
- { role: ec2-create, project: project1, count:1 }
- { role: project1-compile, version: {{ version }} }
- { role: project1-deploy, version: {{ version }}, target: {{last_ec2}} }
There are some problem at this structure and also i don't like it.
- Is that proper way?
- how can i use result of ec2-create role, i would like to deploy codes to server which is just created and i don't know id.
- are there another method to pass parameters to roles?
Take a look at Inventory Modules. More specifically add_host module.
Synopsis
Use variables to create new hosts and groups in inventory for use in
later plays of the same playbook. Takes variables so you can define
the new hosts more fully.
Examples
# add host to group 'just_created' with variable foo=42
- add_host: name={{ ip_from_ec2 }} groups=just_created foo=42
# add a host with a non-standard port local to your machines
- add_host: name={{ new_ip }}:{{ new_port }}
# add a host alias that we reach through a tunnel
- add_host: hostname={{ new_ip }}
ansible_ssh_host={{ inventory_hostname }}
ansible_ssh_port={{ new_port }}

Change modules loading priority

I would like to know the right way to change modules loading priorities in Linux. I want to have hdmi and LCD output the most quickly.
For now it take 3 seconds to came, I know it's not delay due to hdmi or TV because the first stuff I see on screen is some lines about mali init (mali is the name of the GPU here).
I use a A10-Olinuxino-Lime board with an homemade rootfs generated using buildroot and a custom Linux made for this kind of processor (linux-sunxi).
The tree of /etc/:
etc/
├── dhcp
│   ├── dhclient.conf
│   └── dhcpd.conf
├── dropbear
├── fstab
├── group
├── hostname
├── hosts
├── init.d
│   ├── rcK
│   ├── rcS
│   ├── S01logging
│   ├── S20urandom
│   ├── S40network
│   ├── S50dropbear
│   ├── S80dhcp-relay
│   ├── S80dhcp-server
│   ├── S80mali
│   └── S99TVOS
├── inittab
├── inittab~
├── inputrc
├── issue
├── ld.so.cache
├── ld.so.conf
├── ld.so.conf.d
├── mtab -> /proc/mounts
├── network
│   ├── if-down.d
│   ├── if-post-down.d
│   ├── if-post-up.d
│   ├── if-pre-down.d
│   ├── if-pre-up.d
│   ├── if-up.d
│   └── interfaces
├── nsswitch.conf
├── os-release
├── passwd
├── profile
├── protocols
├── random-seed
├── resolv.conf -> ../tmp/resolv.conf
├── securetty
├── services
├── shadow
├── ts.conf
└── wpa_supplicant.conf
Do you have any ideas ?
I'd create an /etc/init.d/S00modules script containing a sequence of insmod (or modprobe if your env supports it) lines.
If that doesn't help, then your modules are loaded even earlier,and you'll have to find how and where that happens. I'd first look at /sbin/init or what is used instead.