timeout when calling libusb libusb_set_interface_alt_setting with some devices

Hi,
I've been suffering this error with my samsung mini plus (GT-S5570i)
https://wiki.postmarketos.org/wiki/Samsung_Galaxy_Pop_Plus_(samsung-s5570i)
The only solution is to comment out the call to libusb_set_al_interface function, as said here https://github.com/Benjamin-Dobell/Heimdall/issues/340 by @joshgav.
As it seems not possible to detect phone's flaky bootloaders, because linux kernel at least seems to be samsung generic, a possible solution could be to set a command line parameter to bypass this function call. So if we execute heimdall and crash here, heimdall can hint to try out again with this bypass command.
The feedback and tests I've got from libusb hackers are here:
https://github.com/libusb/libusb/issues/1024
I hope to be useful :-)
cheers!

Hi @gentooza, heimdall seem to be working well without libusb_set_interface_alt_setting as far as I can tell on newer devices as well, so maybe we can remove it altogether.
Could you at some point try flashing with this heimdall (built from this branch). It will print the actual error code from libusb, and we can then, hopefully, tell heimdall to ignore that particular error code and carry on.

Hi @Grimler91
Ok, already cloned I'll test it and tell you
cheers

@gentooza thanks! (Note that there are two branches in the repo, the master branch and the alt_setting-error branch. alt_setting-error contains the commit with prints the libusb error code)

Hi @Grimler91, I paste what I get:
$ ./heimdall flash --RECOVERY /home/joa/dev/phones/samsung/galaxy\ mini\ s\ -\ gts5570i/boot.img
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
https://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
https://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
libusb: error [op_set_interface] setintf failed error -1 errno 110
ERROR: Setting up interface failed with error code -99!
Releasing device interface...

$ git branch
* alt_setting-error
  master

$ git status
En la rama alt_setting-error
Tu rama está actualizada con 'origin/alt_setting-error'.

nada para hacer commit, el árbol de trabajo está limpio

$ git remote -v
origin	https://git.sr.ht/~grimler/Heimdall (fetch)
origin	https://git.sr.ht/~grimler/Heimdall (push)

Sorry, I've Spanish locale set in my GNU/Linux, the last commands are git orders simply to show I'm working in origin/alt_setting-error branch.
with libusb folks we were already trying to debug this and finally thought it's the flaky bootloader in the device.
ps: error -99 seems to be  LIBUSB_ERROR_OTHER  (https://libusb.sourceforge.io/api-1.0/group__libusb__misc.html)

For future reference: the same issue was reported here: https://gitlab.com/BenjaminDobell/Heimdall/-/issues/517, and a similar fix (don't run libusb_set_interface_alt_setting if alt_setting is 0) was suggested.

the related merge request seems promising!
It has been approved? (sorry my head's going to explode between github, bitbucket, savannah, gitlab... GUIs)
cheers!

I have created a fork and merged a few crucial pull requests. Feel free to create further pull requests there if need be.


Package request: Proton Pass Linux client

Project description
Native Linux desktop client for accessing your Proton Pass vault.
Metadata

homepage URL: https://proton.me/pass/download
source URL: https://github.com/protonpass
license: n/a
platforms: Linux

Add a :+1: reaction to issues you find important.

I see repos for iOS, Android and Web builds, but not the Windows/macOS/Linux ones. Are you sure these are actually open-source? Building from the provided .deb is an option but is discouraged if building from source is viable

I see repos for iOS, Android and Web builds, but not for the Windows/macOS/Linux ones. Are you sure these are actually open-source? Building from the provided .deb is an option but is discouraged if building from source is viable

According to Proton the source code for the Proton Pass linux client is here:
https://github.com/ProtonMail/WebClients/tree/main/applications/pass-desktop

Hmmm... looks like they use Yarn but don't ship their own yarn.lock file. We might have to vendor that, which is annoying but not impossible to do

Unfortunately, building from source doesn't seem like a viable option right now — the Yarn infrastructure in Nixpkgs currently is very shoddy and frankly, nobody knows Yarn well enough to make it work reliably. Upstream uses both a monorepo structure and v2 lockfiles, neither of which are really natively supported in Nixpkgs right now (see #254369). Unpacking the upstream .deb file seems like the only way forward


More flexibility with custom keybindings

previously I had cmd+/ bound to a set of character codes which in turn commented lines in vim. As far as I know, Warp does not provide any way to set custom characters as keybindings. Additionally, I have not found a way to override the current cmd+/ opening the keyboard shortcuts panel key bind. Because of this I am would be unable to preform necessary tasks from my old workflow.
I love the idea of warp, but this would be the decision-making feature for me.

Moving this to Warp repo:
https://github.com/warpdotdev/Warp/issues/2811


Adding new services?

If I wanted to add a new service, in this case GoAccess, how is that done?
In the compose file, I added:
goaccess:
    image: allinurl/goaccess
    labels:
      - 'traefik.backend=goaccess'
      - 'traefik.port=7890'
      - 'traefik.frontend.rule=Host:goaccess.drupal.docker.localhost'

I checked in Portainer, and the container was not started. I started the container, and could not access it at that address in the browser.

I think it's a question about traefik rather than docker4drupal. In your case, you should just add goaccess.drupal.docker.localhost to /etc/hosts


Unable to set step1 premade predictions

When setting the path in the configuration variable:
regenie_premade_predictions = '/my/absolute/path/regenie_step1_preds/regenie_step1_out_pred.list'
and restarting the pipeline, it crashes with the error indicating that it cannot find the file "regenie_step1_out_phenotype_1.loco.gz".
The temporary workaround is to modify the contents of the file regenie_step1_out_pred.list by providing the absolute path to the file regenie_step1_out_phenotype_1.loco.gz. For instance, changing the content from:
phenotype regenie_step1_out_phenotype_1.loco.gz
to:
phenotype /my/absolute/path/regenie_step1_preds/regenie_step1_out_phenotype_1.loco.gz
I believe the problem is that the .gz file is not copied to the temporary folder where the operation is performed.

Hi.
The value passed to regenie_premade_predictions should contain a glob-matching pattern, not an exact file path.
Usually, you will use something like regenie_premade_predictions = '/results/regenie_step1_preds/regenie_step1_out*'
Given that the pipeline will expect the following files to be present in /results/regenie_step1_preds:

A file named regenie_step1_out_pred.list must be present
One file per phenotype is expected named regenie_step1_out_1.loco.gz regenie_step1_out_2.loco.gz, ...

Can you try again with this adjustment and let me know if it works as expected?
Thanks

Hello,
Thank you very much. I can confirm that it works as expected.


Adding an incident by clicking the checkbox doesn't update the graph

Should update and be added to the list of selected ISPs

fixed!


🚀 Add information about payment plan

Is your feature request related to a problem? Please describe.
Need to add a feature to mention if the API is entirely free, is entirely paid or has a free as well as paid plan.
Describe the solution you'd like
The first solution is to add the key payment key with the following values:

free (e.g. Discord)
paid (e.g. Stripe)
upgradable (e.g. IP-API)

I guess we might need to add another key for the case when the paid APIs have option of free testing. For e.g. Stripe
Describe alternatives you've considered
N/A. Feedbacks are welcome though
Additional context
Anyone working on this issue will have to proof-read all the existing API files and add the key-value to those files.
And also update the frontend to display the data properly on the cards.

I would like to work on this issue.

Hi @shahGnp 👋
I have assigned the issue to you ✌


After upgrade / installation of Kong Mesh 2.1 Prometheus server did not start due to missing / broken PVC on EKS

What happened?
I have upgraded my whole cluster to 2.1 including fresh reinstall of observability by applying
kumactl install observability | kubectl delete -f -
kumactl install observability | kubectl apply -f -

No pods were created and after some search it turned out the EKS cluster was missing a  role as described at https://docs.aws.amazon.com/eks/latest/userguide/managing-ebs-csi.html

Triage: there is not much we can do in the code. Let's document it

Couldn't find a PR for this, still relevant.


Help

Where i need to Put Toekn of the Bot?

You need to create a config.json in the main directory. Contents should be:
{   "DiscordBot": {     "Token": "Your bot token",     "Prefix": "bot prefix",     "password": "a random password, This is for sending data from nodes to the bot"   },   "Port": 80 }


Cannot connect to beacon node

running eth2stats gives the following error:
FATA[0000] [core] invalid node URL: localhost:5052
I run eth2stats with the following parameter:
./eth2stats-client run
--eth2stats.node-name="ethnode-c65e37164"
--eth2stats.addr="grc.summer.eth2stats.io:443"
--eth2stats.tls=true
--beacon.type="lighthouse"
--beacon.addr="localhost:5052"
--beacon.metrics-addr="http://localhost:8080/metrics"
lighthouse is up and running fine.
A short glimpse to the used ports with sudo lsof -i -P -n | grep LISTEN
gives the following output
lighthous  3962          ubuntu   30u  IPv4  728231      0t0  TCP *:9000 (LISTEN)
lighthous  3962          ubuntu   35u  IPv4  728237      0t0  TCP <IP_ADDRESS>:5052 (LISTEN)
Do you have any ideas what it could be?

Seeing a similar error
time="2020-04-16T15:56:34Z" level=error msg="[main] setting up: prysm: getting version: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: address http://localhost:4000: too many colons in address\""

with --beacon.addr=http://localhost:4000

hey
@Youllneverknow0 for lighthouse we are connecting over http so the beacon.addr flag should be --beacon.addr="http://localhost:5052"
@timmyers for prysm we are using grpc so the relevant flags should be something like
--beacon.addr="localhost:4000" \
--beacon.metrics-addr="http://localhost:8080/metrics"

i get how this is confusing, it mostly stems from lack of stndardisation but it of course could do with some better error messages. in the mean time I have also added a new onboarding page https://eth2stats.io/add-node which should help with small but annoying things like these
(will leave this open till i add more meaningful error messages)

This does indeed help. Thank you tzapu.
It seems to be running now but not connecting.
INFO[0000] Could not load config file. Falling back to args. Error: Config File "config" Not Found in "[/home/ubuntu/eth2stats-client]"  module=main
INFO[0000] [core] setting up eth2stats server connection
WARN[0001] [core] token file not found; will register as new client
INFO[0001] [core] getting beacon client version
INFO[0001] [core] got beacon client version              version=Lighthouse/v0.1.0-unstable/aarch64-linux
INFO[0001] [core] getting beacon client genesis time
INFO[0001] [core] got beacon client genesis time         genesisTime=1581670800
INFO[0001] [core] awaiting connection to eth2stats server
With this message it gets stuck.

hey, in your intial post i m seeing --eth2stats.addr="grc.summer.eth2stats.io:443"
that should be --eth2stats.addr="grc.summer.eth2stats.io:443"
let me know how you get on
cheers
alex

That was it. Didn‘t see the typo.
It was very attentive of you.
Now it works.
Thank you!


make substraTEE-worker path independent

Currently, the substraTEE-worker can only run when placed inside a bin folder. Remove this restriction.

Closed with #262.


Broken upgrade path for Homebrew Cask: sublime-text3

Lyra and old rpco box are still stuck on removed Cask: sublime-text3.
It appears that 2 things happened:

sublime-text3 Cask was removed in: Homebrew/homebrew-cask-versions@8d7ef627f6889b3ceabe0a7c4ad2ea9c1f2992b5
Cask was replaced with sublime-text in Homebrew/homebrew-casks

This was both a Cask rename, and Tap migration.  However, the updates to tap_migrations.json, and cask_renames.json must have been missed.
As a result, old systems still stuck on the removed sublime-text3 were left without an upgrade path, and files were leftover on the system:

/usr/local/Caskroom/sublime-text3/.metadata/Build 3083/20150608071345.171/Casks/sublime-text3.rb
/Applications/Sublime Text (3143).app

Additionally, Homebrew itself changed over the years and deprecated many DSL constructs that this old Cask definition was using, and this version was still leftover in the $(brew --caskroom)/sublime-text3/.metadata folder.  A copy of the old deprecated and broken Cask.  Therefore, brew was stuck in a state of throwing errors every operation that involved reading this Cask, including on brew update, brew remove sublime-text3, brew zap sublime-text3, brew upgrade sublime-text3, etc...
Goals of this task:

Add proper upgrade path for this Cask:

Add to Homebrew/homebrew-cask/cask_renames.json to flag as a renamed Cask
Add to Homebrew/homebrew-cask-versions/tap_migrations.json to pave way for brew upgrade path to homebrew-cask

Migrate old systems off the old sublime-text3 to sublime-text

brew upgrade  --verbose --debug --force  sublime-text3

Check and/or Fix any breakages for lyraphase_workstation::sublime_text_settings recipe & config files.

Pushed PRs:

Homebrew/homebrew-cask-versions#17278
Homebrew/homebrew-cask#151961

Status: Waiting on review

Moving out target date to next week

Bumped PRs to avoid github-actions stale bot
Posted RFC w/ping to Homebrew maintainers
Pushed target date out to end of week

Status: Waiting on response + review

👏 🎉 Merged! Many thanks to @bevanjkay 🙏


Add local stats for augment combinations

Closes #612

prevent users from quitting a match early and saving weird data

prevent users from quitting a match early and saving weird data

Won't do this now as it requires further work on the stat-storing code, which shouldn't be prioritized right now.


Support for autoprefixer/postcss for -webkit-* css rules

Generating for an element that has a class requiring -webkit-* css rules to work in a specific browser, doesn't work as expected.
Required is adding 'autoprefixer' package to the plugins list of PostCSS.
https://tailwindcss.com/docs/browser-support#vendor-prefixes
example
Input:

Output:
.bg-clip-text {
    background-clip: text
}

Expected output (in Chrome):
.bg-clip-text {
    -webkit-background-clip: text;
    background-clip: text;
}

Hi, for that usecase i think you have to use the lower level api to create your own postcss instance:
https://github.com/mhsdesign/jit-browser-tailwindcss/tree/main#lower-level-api-to-create-tailwind-post-css-plugin
const processor = postcss([
    createTailwindcssPlugin({ tailwindConfig, content }),
    // autoPrefixerPlugin
]);
const { css } = await processor.process(css, { from: undefined });


Add deeplinking capture for Open Products Facts, Open Pet Food Facts and Open Beauty Facts in the mobile app

What

Add deeplinking capture for Open Products Facts, Open Pet Food Facts and Open Beauty Facts in the mobile app

@teolemon prices, beauty, products and petfood URLs are deeplinked the same way as food URLs from #5734.
If there are specific pages you would like to support, please list them.


[docs] Improve Grid limitations description

[x] I have followed (at least) the PR section of the contributing guide.

Closes #13277

@ryancogswell Thanks


It doesn't work

It doesn't work and report error.

What error are you facing?

I have recharged it, and it will continue to work for a while. However, in the long run, the ultimate solution is for skilled individuals to deploy their own backend and share it on a small scale.


Update to Gradle 8

My project is using Gradle 8 and I'm receiving this error.  We can prevent it by updating this package to Gradle 8 and add an optional check if the namespace exists for backwards compatibility.
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':file_saver'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 15s
Exception: Gradle task assembleDebug failed with exit code 1

Okay will do asap thank! @quoc-huynh-cosee

@incrediblezayed Any updates so far?

Hey @incrediblezayed it's been a month? Do you need any help for that?

Hey @incrediblezayed it's been a month? Do you need any help for that?

Yes yes, I'd love that, I'm so sorry I've been very busy, please create a PR and I'll merge it asap

Merged


Search in APIView does not match on PR number

If I choose Type = PullRequest in the APIView filters

And then search on the PR number -- which is shown in the "Name" column -- I get no hits for PRs that are shown prior to the search (here 28668).

Dup of #5465


[Email] - Users got duplicate emails of receiving donation

Report is here.

This shall have been fixed in https://github.com/thematters/matters-server/commit/ae1005418e3f5ae6f100e2381b3166f9a2bba5d2

I see. Closed it.


mllama patch modifies nn.LayerNorm globally

🐛 Describe the bug
Instead of only patching the transformers mllama module (transformers.models.mllama.modeling_mllama), apply_liger_kernel_to_mllama modifies torch.nn.LayerNorm globally.
The issue is here.
The fix would be to:
(1) Not patch LayerNorm in Liger by assigning to modeling_mllama.nn.LayerNorm
(2) Change transformers.models.mllama.modeling_mllama to not use from torch import nn and to instead just import layernorm like from torch.nn import LayerNorm
(3) instead patch layernorm in Liger by assigning to modeling_mllama.LayerNorm
Reproduce
pip install transformers==4.45 liger-kernel-nightly

from liger_kernel.transformers import apply_liger_kernel_to_mllama
from torch import nn

apply_liger_kernel_to_mllama()
print(nn.LayerNorm)
<class 'liger_kernel.transformers.layer_norm.LigerLayerNorm'>

Versions
Environment Report:
Operating System: Linux-6.1.85+-x86_64-with-glibc2.35
Python version: 3.10.12
PyTorch version: 2.4.1+cu121
CUDA version: Not available
Triton version: 3.1.0
Transformers version: 4.45.0

curious does it require to change transformer source code? i think we can maybe raise a request

Yeah the proposed fix would require a change to transformers unfortunately. How mllama was implemented differs very slightly from the conventions in other transformers modeling files.

sounds good. let us try to send a PR there


provide a CLI tool to compute SWHIDs easily

Would provide two sub-commands: swhid compute and swhid download. The compute sub-command should also let the user specify which kind of content is being worked on (directory, cnt, directory_deep etc.).
cc @kit-ty-kate
@rjbou I remember you wrote a one-liner to allow computing the swhid of a directory by calling directory_identifier_deep. For some reason I can't find it again, could you post it here ? It could be useful to others until I write the CLI tool.

Actually, @RadioPotin, maybe you would like to work on this ?

ocaml -e '#use "topfind";; #require "digestif.ocaml";; #require "swhid";; Swhid_core.Object.pp Format.std_formatter (Result.get_ok (Swhid.Compute.directory_identifier_deep "."))'

It was here .


C++11 & HPP_POSTCONDITION with  BOOST_SCOPE_EXIT

Hi,
If we try to compile this project in c++11, the tests do not pass, because at
https://github.com/humanoid-path-planner/hpp-util/blob/master/include/hpp/util/assertion.hh#L71 if an exception is raised, it can't be catched there:
https://github.com/humanoid-path-planner/hpp-util/blob/master/tests/assertion.cc#L101
Boost's doc on BOOST_SCOPE_EXIT provides the following warning since at least 1.50 (released in 2012):

Warning: The implementation executes the scope exit body within a destructor thus the scope exit body must never throw in order to comply with STL exception safety requirements.

I don't think that this HPP_POSTCONDITION is used anywhere, so I think that we should remove it, otherwise we would have to add CMAKE_CXX_STANDARD=98 to the CMakeLists (and to the packages that use this HPP_POSTCONDITION), to allow compilation of this package on compilers which have c++11 as the default standard, which is the case for the those provided with ubuntu 18.04.

PS: in the last HPP-Meeting, I recall that we agreed on the idea that "HPP should compile on both C++98 & C++11" :)


help with #1802

Tried to add bypass sv_pure. Did everything, besides the backtrack related stuffs, giving me errors lol. can't do much on github, so dm Vicarious#002. type your tag below btw so i know

Tried to add bypass sv_pure. Did everything, besides the backtrack related stuffs, giving me errors lol. can't do much on github, so dm Vicarious#002. type your tag below btw so i know

you need to put the backtrack stuff in too


Yarn v2 error because unist-util-stringify-position is not in package.json

When using Yarn v2, I get the following error:
Error: mdast-util-mdx-jsx tried to access unist-util-stringify-position, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
I can see that from-markdown.js has var stringifyPosition = require('unist-util-stringify-position')
Should this be added to package.json?

Yup, thanks!


Simplify minikube getting started guide

Depends on #6495

This change is

test-me-please

Coverage increased (+0.004%) to 43.792% when pulling 73e118d56fc77eeafa56e12450cc983d50017286 on pr/tgraf/simmplify-gsg-minikube into f576a1c5f0a1c5981405dae0257c450d8151ebf1 on master.

test-me-please

test-me-please


Feature | Refactor credentials setup tasks to favor a better UX

What?

✅ Ensure the best user experience covering the following use cases:

bootstrap credentials
onboard new user
rotate credentials

Design requirements

The current leverage credentials command is useful for the bootstrap ones but then for management and security gets complicated.
The process of configuring the different types of AWS credentials needs to be more decoupled.
It will support the ability to create management and security credentials without having the bootstrap credentials.
Support the case of renewing creds, for instance a user who already has the credentials in place only needs his programmatic keys to be modified.

How?
Design proposed by @diego-ojeda-binbash
$ leverage credentials configure
  \ --type [BOOTSTRAP | MANAGEMENT | SECURITY]
  \ [--skip-assumable-roles-setup]

If type == BOOTSTRAP

configure a profile for BOOTSTRAP in .aws/credentials -- read bootstrap creds from csv or allow manual input
no need to create/update profiles in .aws/config
verify or show instructions on how to do that

If type == (MANAGEMENT | SECURITY)

configure a profile for MANAGEMENT or SECURITY in .aws/credentials -- read from csv or allow manual input
If skip-assumable-roles-setup, do NOT create/update profiles in .aws/config
If not skip-assumable-roles-setup, do create/update profiles in .aws/config

Then one could run:

$ leverage credentials configure --type BOOTSTRAP for when to deploy the LZ
$ leverage credentials configure --type MANAGEMENT to set permanent credentials and roles in .aws/config for management user
$ leverage credentials configure --type SECURITY same as above but for security
and optionally one can pass the flag --skip-assumable-roles-setup to skip the update to the .aws/config file that has the roles profiles.

Considerations

We still need the project.yaml for the BOOTSTRAP credentials (there is still no other file that has that info at bootstrap time).
After everything is deployed we already have the config/common.tfvars, that already has the necessary data to set the credentials and we could take it from there.
We can still use the project.yaml for the BOOTSTRAPcreds but for MANAGEMENT and SECURITY we can take from the files that will be permanent in the repo line common.tfvars.
In the near future we should let go the project.yaml, but at this point it might take a lot of work.

Before being able to remove the project.yml please consider that  currently there is data from the project.yaml that is needed and we should move it somewhere else, and common.tfvars may not be the best option to host that info.
But if possible we should try to remove the project.yaml and let the config/common.tfvars have most of the info.

CC: @binbashar/leverage-ref-architecture-aws-dev @binbashar/leverage-ref-architecture-aws-admin

After reviewing the implementation one extra behavior was found to be needed.
If for whatever reason AWS Organizations is unreachable/unresponsive, or if no management or bootstrap credentials with the required permissions are found to be configured in the system, then the CLI should trust the information found in config/common.tfvars regarding accounts and their ids to configure each accounts profiles.


Added public goods for Band Protocol

Thanks for the submission. Maybe next time sync your branch so we don't see all these commits listed


Secrets exposed in server only load fetch dependencies

Describe the bug
Thanks for the awesome open source work.
I'm quite new to Svelte and SvelteKit and recently decided to use in a project to learn it more. I think, I've discovered some bug or issue in SvelteKit with my very limited experience using it.
I'm loading some data in +layout.server.ts from an external url which requires sending api key as query param. I've stored the api key in .env file. I'm loading the data in +layout.server.ts specifically because I don't want to expose api key to the client. But even this file is also exposing it to client as part of url dependency for the fetch.
I tried calling depends inside load but it adds additional dependencies along with fetch url. I couldn't find any way to prevent SvelteKit using url as dependency.
As an alternate solution to this, I could've created an internal api route which calls the external api with api key but I think +layout.server.ts shouldn't expose the url (and secrets certainly not) to client as it guarantees to run the code only server side. I don't see any benefit of using server only load of +layout.server.ts over universal load in +layout.ts, if it exposes the url (and secrets) to client.
Reproduction

Create an .env file and add a secret such as API_KEY=top-secret-key.
Create a load function in +layout.server.ts which uses fetch to load data from external api. Import and pass API_KEY environment variable to fetch url as query param.
Use the server fetched data in +layout.svelte.
Open the browser dev tools and view source. At the bottom in script tag, you'll find that your secret API_KEY is exposed to the client.

const data = [
	{
		type: 'data',
		data: {
			todos: [
				{ id: 1, title: 'one' },
				{ id: 2, name: 'two' }
			]
		},
		uses: {
			dependencies: [
				'https://jsonplaceholder.typicode.com/todos?api_key=top-secret-key'        // <---- Secret exposed
			]
		}
	},
	null
]

Here's a demo project I've created to reproduce this issue:
https://stackblitz.com/edit/sveltejs-kit-template-default-eeb3rv?file=src/routes/+layout.server.js
Also note that in my testing with @sveltejs/kit@next version the dependencies array is empty which is what I was expecting.
Logs
No response
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.0.1
    @sveltejs/kit: ^1.5.0 => 1.15.9
    svelte: ^3.54.0 => 3.58.0
    vite: ^4.3.0 => 4.3.3

Severity
blocking all usage of SvelteKit
Additional Information
No response

Dependencies have to be sent to the client to be able to invalidate data properly.
You can use the handleFetch hook to rewrite any requests that are sent from your server. So your +layout.server.js load function can just call the URL without the key, and the dependencies will have that link instead, then inside handleFetch you can add your API key to the url.
https://stackblitz.com/edit/sveltejs-kit-template-default-iad1ko?file=src%2Froutes%2F%2Blayout.server.js
I suppose we could document this behaviour better to prevent users leaking their keys. Feel free to send a PR or point out where in the documentation you would expect it.

Put your actual fetch inside +server and call that from your load function

@gtm-nayan
Thanks for your reply.
I understand that dependencies are required to invalidate the data.
I'm aware of handleFetch hook. As I've mentioned that I was not looking for a workaround (or an alternative way to fetch from external api) to prevent leaking the secret to client.
What I'm expecting is that there should be some way to override the invalidation key (which I guess is by default the fetch url). There's already a depends function provided by ServerLoadEvent in load but it doesn't facilitates the override behaviour. Other solution which I can think of is that SvelteKit should allow hashing the url (or by default hash all if not a performance issue) before using as invalidation key, so that urls are not exposed.

I was not aware of this behavior. I don’t think any value or code that is added to +layout.server.js or +server.js file should be exposed to the client under no circumstances. This is going to cause a lot of secret leak even if it’s documented.

I still need to digest this, but what's the point of "private", "server" and "public" if everything is exposed to the client by default?

It would be nice if this could be automatically done/intercepted by compiler itself and replace any secret with a unique placeholder and automatically map and rewrite URLs in a similar way as in handleFetch, instead of just documenting it and when major security leak happens pointing to people and telling them to RTFM

This was added in https://github.com/sveltejs/kit/pull/8420
Invalidation by url for urls passed into server only fetch calls seems like a rare usecase that should be opt-in rather than default, especially if it leaks information about service urls to the client.
This is not only problematic if the url contains a secret token, but in general, as the url itself gives an attacker additional information that could be used in a chained attack.

This was an oversight, thanks for bringing it to our attention.
I think there are a few possible approaches:

Don't include implicit dependencies at all when serializing data. This would be a breaking change, but a reasonable one under the circumstances
Don't include implicit dependencies for external URLs. That is, fetch('/api/foo') would continue to add /api/foo to dependencies, allowing for easy invalidation, but fetch('https://example.com/api/foo?key=<SECRET>') would not. This assumes that you're not passing secrets to your own endpoints, which isn't bulletproof but seems like a fair assumption. This would still be a breaking change, but less so.
Strip out query parameters. Again, not bulletproof, but would prevent leakage in all realistic cases, though it would (to @dominikg's point above) still leak information about the URLs being used
Hash URLs. In other words, fetch('https://example.com/api/foo?key=<SECRET>') creates a abc123 dependency, while fetch('/api/foo') creates a def456 dependency. In the client, calling invalidate('/api/foo') would cause def456 to be invalidated, because we'd use the same hashing function. However, invalidating with a function, as in invalidate((url) => url.startsWith('/api')), would not work with this approach
Some combination of the above

Thoughts?
In #9850 @malviyaritesh adds a new svelte key to the fetch options. I don't think we should do this — adding arbitrary stuff to standard interfaces rarely ages well in my experience, and I don't think there's any reason to prefer this...
import { PRIVATE_STATIC } from '$env/static/private';

export async function load({ fetch }) {
  return {
    time: fetch(`http://worldtimeapi.org/api/ip?PRIVATE=${encodeURIComponent(PRIVATE_STATIC)}`, {
      svelte: { depends: 'app:hidden-time-api' }
    }).then((res) => res.json())
  };
}

...over this:
import { PRIVATE_STATIC } from '$env/static/private';

export async function load({ fetch, depends }) {
  depends('app:hidden-time-api');
  return {
    time: fetch(`http://worldtimeapi.org/api/ip?PRIVATE=${encodeURIComponent(PRIVATE_STATIC)}`).then((res) => res.json())
  };
}

I would make this an option like dangerouslyTrackServerFetches which you can opt in to but it's removed in 2.0 and then we also print some kind of warning so people know they can opt into it - so the breaking change could easily be reverted for people who need the current behavior.
We could also make it opt in to track so we don't break people but warn that people should opt into it.


⚠ ClamAV has degraded performance

In e3130af, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 317 ms

Resolved: ClamAV performance has improved in 4af4696.


Input Support for Double2dArray

[ ] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
TODO: Include high-level description of the changes in this pull request.
Why should this Pull Request be merged?
TODO: Justify why this contribution should be part of the project.
What testing has been done?
TODO: Detail what testing has been done to ensure this submission meets requirements.

For parsing Double2DArray value we are converting the default_value to string in _support.py. Also, handling repr(value) conversions in get_configuration_metadata_with_index_values. This is one of the approach that we think is the best way to handle these conversions.
Another way, we can handle the parsing of Double2DArray value is to handle it after render_template method creates the output then we fix all the instance in the generated template output through regex. But this happens during the _create_file method call, which may or may not be the best place to handle this case.


Template with multiparagraph description isn't working with LF line endings

Description
When a paket.template with multiparagraph description is saved with Unix line endings paket pack command fails with the following error message:
Paket failed with:
	Unable to parse template file C:\Work\PaketRepro\ConsoleApplication1\paket.template: Indented block with no name line 7.

Repro steps

Create a template with multiparagraph description and save the file with LF line endings.

Run paket pack output dist command.

Expected behavior
I would expect the command to execute without errors like it does if the description has only one paragraph and LF line endings.
Actual behavior
The command fails with the error message described above.
Known workarounds
Save the template with Windows line endings (CRLF).

Could you please upload a zip with a repro?

Can be reproduced with issue#2104 branch in scoobadog/PaketRepro repository.


Problem compiling with Vulkan SDK version 1.3.261.1

Unfortunately i think this is a CMake issue on linux. Apparently Ubuntu ships with a very outdated version of the dxc compiler, which is added to the path by default.
However, we need to explicitly select the dxc version that comes with the Vulkan SDK in the bin folder.

Strange, it seems to work fine with <IP_ADDRESS>. I reverted to that version b/c it's the one used in CI. Though I do recall that being an issue...

I can try to update on my machine and see if I can reproduce locally.

@pshriwise could you try to test this out again with latest GPRT? I have a fix pushed to master now that I believe fixes the issue.
There was a change with DXC on trunc that unfortunately caused a regression... The change is that we now are locked into a more stable DXC version, which we download as part of the cmake configure step.

Confirmed fixed 👍🏻 on Linux


docs: add requirements around strong time synchronisation

Resolves #91

I was going to say that consistent zedification was just as important as consistent timing, but I guess I mean consistent zeeification :-/

I was going to say that consistent zedification was just as important as consistent timing, but I guess I mean consistent zeeification :-/


AttributeError: 'NoneType' object has no attribute 'get'

Expected Behavior
Catching a pokemon
Actual Behavior
[14:36:21] A Wild Spearow appeared! [CP 175] [Potential 0.62]
[14:36:21] IV [Stamina/Attack/Defense] = [15/11/2]
Traceback (most recent call last):
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokecli.py", line 283, in <module>
    main()
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokecli.py", line 249, in main
    bot.take_step()
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\__init__.py", line 47, in take_step
    self.process_cells(work_on_forts=True)
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\__init__.py", line 67, in process_cells
    "catchable_pokemons": catchable_pokemons}, location, work_on_forts)
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\__init__.py", line 174, in work_on_cell
    if worker.work() == WorkerResult.RUNNING:
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\cell_workers\catch_visible_pokmeon_worker.py", line 39, in work
    return self.catch_pokemon(self.cell['catchable_pokemons'][0])
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\cell_workers\catch_visible_pokmeon_worker.py", line 51, in catch_pokemon
    return_value = worker.work()
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\cell_workers\pokemon_catch_worker.py", line 98, in work
    if not self.should_capture_pokemon(pokemon_name, cp, pokemon_potential, response_dict):
  File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot\cell_workers\pokemon_catch_worker.py", line 292, in should_capture_pokemon
    cp_iv_logic = catch_config.get('logic')
AttributeError: 'NoneType' object has no attribute 'get'

Steps to Reproduce
just running the bot as usual
Other Information
OS:  windows 10
Git Commit: 15a034427d805e0bacb79fc0a1f3c96a6c93f0e3
What is tried before

Changing the config file
Reinstalling everything

Same error on OSX 10.11.5 after a long walking time

That's a server issue : NoneType means the server didn't respond.
Try again when servers are stable again.

Why can i visit pokestops, log in, ... But not catch pokemon then?

I'm guessing catching is a "heavier" request server-side.
It's the same bug you get if you use the client and it freezes on the pokeball screen.

ahn ok it makes sense then

Will close the issue when I get it to work. but for now the servers having issues for over 6 hours

At this point i can't even open my inventory
Traceback (most recent call last):
File "C:\PokemonGo\PokemonGo-Bot-dev\pokecli.py", line 283, in
main()
File "C:\PokemonGo\PokemonGo-Bot-dev\pokecli.py", line 243, in main
bot.start()
File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot_init_.py", line 42, in start
self.setup_api()
File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot_init.py", line 259, in _setup_api
self.print_character_info()
File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot_init.py", line 289, in print_character_info
items_stock = self.current_inventory()
File "C:\PokemonGo\PokemonGo-Bot-dev\pokemongo_bot_init.py", line 359, in current_inventory
inventory_dict = inventory_req['responses']['GET_INVENTORY'][
KeyError: 'GET_INVENTORY'

Please upgrade to the latest dev branch by running this command:
git reset --hard
git pull -f

Then run this command:
pip install --upgrade -r requirements.txt
If issue persists, open a new issue.
/closed

How did you resolve this issue? I tried updating to no avail. Was this only a server-side error?

It's only a server-side issue. If you're on the latest dev, you shouldn't be seeing this error anymore.


RuneWatch lookup

Is your feature request related to a problem? Please describe.
As a member of staff in the largest discord of OSRS raiding (WeDoRaids) I have witnessed many people sneak into raids hosted in the discord and continue to scam items as people are too lazy to check the discords ban list as well as use the bots provided in the discord, this leads to people scamming millions of gp, playing on peoples laziness
Describe the solution you'd like
It would be nice if the client could look up players in your cc against the RuneWatch database and flag any members that show up by changing the colour of their name or having a message in chat
Describe alternatives you've considered
An alternative solution which I am not sure if would be simpler to implement is to have a sidebar for this plugin that allows you to individually look up players by clicking on their name in the sidebar, where names would be retrieved from the cc

We don't really want to depend on 3rd party service that is flagging people as "bad", that seems like very dangerous thing to rely on, and I believe we discussed this already before.

We have refactored our case system and are now able to support this feature.
Here's a case list you can use: https://www.runewatch.com/api/cases/list
If you would like to query a single rsn please let us know via twitter @RuneWatch or dm Will osrs#0480 on Discord.
(I do not wish to re-open an issue/request for this, so pick it up if you'd like to move forward with it)


Release uPickle 3.1.0

Targeting a release end-April. Since none of the fixes are showstoppers (the bugs have workarounds, and perf improvements are always just a nice-to-have) there isn't any real urgency to push them out, and we can wait a bit to see if anyone else has changes they want to get in

Since nothing much has merged since this opened, I'm inclined to release this sooner rather than later. Will merge and release 3.1.0 tomorrow


Update and fix tensorflow dockerfile

The tensorflow dockerfile is currently broken because libcudnn7 is no longer provided by Nvidia in their repos
This PR updates the tensorflow dockerfile to use a combination of packages that currently works and is available from Nvidia

Ping? @DrJimFan @fxia22 apologies for tagging, not sure who to poke for a review :)


v1.15: run CI automatically for renovate

Backported #33287 and #33309 adjusted to the v1.15 branch
 33287 33309

/test-backport-1.15


Removed custom repositories

I removed the custom repositories from the pom.xml file, deleted my ~/.m2/repository directory and ran:
mvn clean package -Pspark-1.3 -Dhadoop.version=2.2.0 -Phadoop-2.2 -DskipTests
which succeeded.

+1
Will we end up having profile for Cloudera or Hortonworks of Spark? Cloudera CDH for example has a different akka build and we might need to pull from their repo.

Thanks for contribution.
One question, will this changes still build zeppelin with cdh hadoop dependencies?
for example mvn package -Dhadoop.version=2.0.0-mr1-cdh4.7.1
?

Running the command:
mvn clean package -Dhadoop.version=2.0.0-mr1-cdh4.7.1 -DskipTests
I get:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ........................................... SUCCESS [  1.617 s]
[INFO] Zeppelin: Interpreter .............................. SUCCESS [  5.463 s]
[INFO] Zeppelin: Zengine .................................. SUCCESS [  2.345 s]
[INFO] Zeppelin: Spark .................................... SUCCESS [ 15.725 s]
[INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [  1.194 s]
[INFO] Zeppelin: Angular interpreter ...................... SUCCESS [  1.121 s]
[INFO] Zeppelin: Shell interpreter ........................ SUCCESS [  1.219 s]
[INFO] Zeppelin: Hive interpreter ......................... SUCCESS [  1.541 s]
[INFO] Zeppelin: Tajo interpreter ......................... SUCCESS [  1.305 s]
[INFO] Zeppelin: web Application .......................... SUCCESS [ 38.142 s]
[INFO] Zeppelin: Server ................................... SUCCESS [  6.217 s]
[INFO] Zeppelin: Packaging distribution ................... SUCCESS [  0.229 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:16 min
[INFO] Finished at: 2015-05-02T09:41:32-04:00
[INFO] Final Memory: 109M/1809M
[INFO] ------------------------------------------------------------------------
Now, when I leave off the -DskipTests, I get some failure because it seems to be trying to load some JS testing framework in Safari and it can't find a "driver", so I need to get that all set up so that I can run a full build.  But, it seems to be able to download everything it needs.

Looks good to me.
@jwcarman
Are you interested in removal of custom pluginRepository, too?

Yeah, I was going to remove that also.  I'll create a separate pull request for that.

Okay, maybe I won't :)

Custom plugin repository were for "s3-upload-maven-pugin" which is used in zeppelin-distribution module.
Could you change s3-upload-maven-pugin plugins version from '1.2-SNAPSHOT' to '1.2' ? then i think i can merge this PR.

Done.

LGTM.
If there're no more discussions, i'm merging it.


add 'use' prefix for any auto-import

Fixes #9643
looks like there was an if condition that had to be removed.

Thanks!
bors r+

Can we display "use foo::Bar" instead of "Bar (use foo::Bar)"? Would that look too weird?


[Bug]: DEFERRABILITY column in sp_fkeys

What happened?
I am running BABEL_2_2_1__PG_14_5 on Fedora 36.
sp_fkeys result set in Babelfish returns 13 columns that correspond to the MSSQL sp_fkeys docs. But MSSQL itself does not follow these docs, sp_fkeys there returns 14 columns, additional column being DEFERRABILITY smallint, actual result set from sp_fkeys is the same as from sp_foreignkeys.
The problem is that mssql-jdbc driver expects DEFERRABILITY to be present in sp_fkeys output, otherwise getCrossReference JDBC call fails on Babelfish with:
2023-01-04 16:30:48.945 GMT [64885] ERROR:  structure of query does not match function result type
2023-01-04 16:30:48.945 GMT [64885] DETAIL:  Number of returned columns (13) does not match expected column count (14).
2023-01-04 16:30:48.945 GMT [64885] CONTEXT:  PL/tsql function sp_fkeys(sysname,sysname,sysname,sysname,sysname,sysname) line 15 at SQL statement
	SQL statement "INSERT INTO "@jdbc_temp_fkeys_result" EXEC sp_fkeys @P0,@P1,@P2,@P3,@P4,@P5;"
	PL/tsql function inline_code_block line 1 at SQL statement
	TDS Protocol: Message Type: RPC, SP Type: SP_EXECUTESQL, Phase: TDS_REQUEST_PHASE_PROCESS. Processing SP_EXECUTESQL Request

If I modify sp_fkeys adding something like this to its output:
cast(7 as smallint) as DEFERRABILITY

then getCrossReference call works correctly.
It would be great to add DEFERRABILITY column to sp_fkeys to have this working out of the box with Babelfish.
Version
BABEL_1_X_DEV (Default)
Extension
babelfishpg_tsql (Default)
Which flavor of Linux are you using when you see the bug?
Fedora
Relevant log output
No response
Code of Conduct

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

Thank you for reporting the issue. We'll work on a fix.

@staticlibs: A fix to this issue should be available in the next release and has been checked in with this commit (https://github.com/babelfish-for-postgresql/babelfish_extensions/commit/ff63f17a1abecf7484cf4e9f8ec4739bb3241cc7).

Thanks for fixing this! I can confirm that with the current mainline version (18fcfe8) corresponding JDBC calls (getImportedKeys, getExportedKeys, getCrossReference) work correctly now. Closing the issue.


socketServer.clients is not exposed?

How can I iterate over the connected clients?
Something like:
https://github.com/websockets/ws#server-sending-broadcast-data

You can send a broadcast using the broadcast method. It hasn't been optimized yet but it does exactly that.
https://github.com/alexhultman/uWebSockets/blob/master/nodejs/dist/uws.js#L335

I'm aware of that but I need to do some pre-checks eg:
for (var i in this.clients)
if (this.clients[i]._channel == channel)
this.clients[i].send(data, opts);
}

I currently just put the socket objects in sets in onConnection or onMessage and loop over the set.
That way I don't have to loop over every socket to broadcast to a subset.
A socketServer.clients method would be more convenient I suppose.

There is no JavaScript vector of sockets, you have to build that yourself if you need one. In any case, you shouldn't have to loop over all vectors doing checks, just sort the sockets in a vector of vector of sockets.


Vibrational analysis recipe for VASP

Summary of Changes
>> New VASP recipe for performing vibrational analysis (using ASE Vibrations) to obtain thermodynamic properties.

Can one of the admins verify this patch?

Closing in favor of https://github.com/Quantum-Accelerators/quacc/pull/2362.


All Slaves follow only from node1

I run the docker-compose.yml from the lastest.yml. Look like it cannot connect to the 1st tier slave node.
# gosu postgres repmgr cluster show
 ID | Name  | Role    | Status    | Upstream | Location | Connection string
----+-------+---------+-----------+----------+----------+-----------------------------------------------------------------------------------------------------------------
 1  | node1 | primary | * running |          | default  | user=replication_user password=replication_pass host=pgmaster dbname=replication_db port=5432 connect_timeout=2
 2  | node2 | standby |   running | node1    | default  | user=replication_user password=replication_pass host=pgslave1 dbname=replication_db port=5432 connect_timeout=2
 3  | node3 | standby |   running | node1    | default  | user=replication_user password=replication_pass host=pgslave2 dbname=replication_db port=5432 connect_timeout=2
 4  | node4 | standby |   running | node1    | default  | user=replication_user password=replication_pass host=pgslave3 dbname=replication_db port=5432 connect_timeout=2
 5  | node5 | standby |   running | node1    | default  | user=replication_user password=replication_pass host=pgslave4 dbname=replication_db port=5432 connect_timeout=2

Here is what is shown in pgslave2
pgslave2_1_645dab692bcb | >>> Setting up STOP handlers...
pgslave2_1_645dab692bcb | >>> STARTING SSH (if required)...
pgslave2_1_645dab692bcb | cp: cannot stat '/home/postgres/.ssh/keys/*': No such file or directory
pgslave2_1_645dab692bcb | No pre-populated ssh keys!
pgslave2_1_645dab692bcb | >>> SSH is not enabled!
pgslave2_1_645dab692bcb | >>> STARTING POSTGRES...
pgslave2_1_645dab692bcb | >>> SETTING UP POLYMORPHIC VARIABLES (repmgr=3+postgres=9 | repmgr=4, postgres=10)...
pgslave2_1_645dab692bcb | >>> TUNING UP POSTGRES...
pgslave2_1_645dab692bcb | >>> Cleaning data folder which might have some garbage...
pgslave2_1_645dab692bcb | >>> Auto-detected master name: ''
pgslave2_1_645dab692bcb | >>> Setting up repmgr...
pgslave2_1_645dab692bcb | >>> Setting up repmgr config file '/etc/repmgr.conf'...
pgslave2_1_645dab692bcb | >>> Setting up upstream node...
pgslave2_1_645dab692bcb | cat: /var/lib/postgresql/data/standby.lock: No such file or directory
pgslave2_1_645dab692bcb | >>> Previously Locked standby upstream node LOCKED_STANDBY=''
pgslave2_1_645dab692bcb | >>> Waiting for upstream postgres server...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.repmgr on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 30 times more)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 29 times more)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 28 times more)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 27 times more)
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.repmgr exists on host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> Waiting for upstream node id replication_db on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id is still not accessible on host pgslave1:5432 (will try 30 times more)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id is still not accessible on host pgslave1:5432 (will try 29 times more)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id is still not accessible on host pgslave1:5432 (will try 28 times more)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id 2 received from host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> REPLICATION_UPSTREAM_NODE_ID=2
pgslave2_1_645dab692bcb | >>> Sending in background postgres start...
pgslave2_1_645dab692bcb | >>> Waiting for upstream postgres server...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.repmgr on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.repmgr exists on host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> Starting standby node...
pgslave2_1_645dab692bcb | >>> Instance hasn't been set up yet.
pgslave2_1_645dab692bcb | >>> Clonning primary node...
pgslave2_1_645dab692bcb | >>> Waiting for upstream postgres server...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.repmgr on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | NOTICE: destination directory "/var/lib/postgresql/data" provided
pgslave2_1_645dab692bcb | INFO: connecting to source node
pgslave2_1_645dab692bcb | DETAIL: connection string is: host=pgslave1 user=replication_user port=5432 dbname=replication_db
pgslave2_1_645dab692bcb | DETAIL: current installation size is 37 MB
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.repmgr exists on host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> Waiting for cloning on this node is over(if any in progress): CLEAN_UP_ON_FAIL=, INTERVAL=30
pgslave2_1_645dab692bcb | >>> Replicated: 0
pgslave2_1_645dab692bcb | INFO: checking and correcting permissions on existing directory "/var/lib/postgresql/data"
pgslave2_1_645dab692bcb | NOTICE: starting backup (using pg_basebackup)...
pgslave2_1_645dab692bcb | INFO: executing:
pgslave2_1_645dab692bcb |   /usr/lib/postgresql/10/bin/pg_basebackup -l "repmgr base backup"  -D /var/lib/postgresql/data -h pgslave1 -p 5432 -U replication_user -c fast -X stream -S repmgr_slot_3
pgslave2_1_645dab692bcb | NOTICE: creating replication slot "repmgr_slot_3" on upstream node 1
pgslave2_1_645dab692bcb | NOTICE: replication slot "repmgr_slot_3" deleted on source node
pgslave2_1_645dab692bcb | NOTICE: standby clone (using pg_basebackup) complete
pgslave2_1_645dab692bcb | NOTICE: you can now start your PostgreSQL server
pgslave2_1_645dab692bcb | HINT: for example: pg_ctl -D /var/lib/postgresql/data start
pgslave2_1_645dab692bcb | HINT: after starting the server, you need to register this standby with "repmgr standby register"
pgslave2_1_645dab692bcb | INFO: executing notification command for event "standby_clone"
pgslave2_1_645dab692bcb | DETAIL: command is:
pgslave2_1_645dab692bcb |   /usr/local/bin/cluster/repmgr/events/router.sh 3 standby_clone 1 "2018-12-26 23:57:47.269342+00" "cloned from host \"pgslave1\", port 5432; backup method: pg_basebackup; --force: Y"
pgslave2_1_645dab692bcb | [REPMGR EVENT] Node id: 3; Event type: standby_clone; Success [1|0]: 1; Time: 2018-12-26 23:57:47.269342+00;  Details: cloned from host "pgslave1", port 5432; backup method: pg_basebackup; --force: Y
pgslave2_1_645dab692bcb | >>> Configuring /var/lib/postgresql/data/postgresql.conf
pgslave2_1_645dab692bcb | >>>>>> Will add configs to the exists file
pgslave2_1_645dab692bcb | >>>>>> Adding config 'listen_addresses'=''*''
pgslave2_1_645dab692bcb | >>>>>> Adding config 'shared_preload_libraries'=''repmgr''
pgslave2_1_645dab692bcb | >>> Starting postgres...
pgslave2_1_645dab692bcb | >>> Waiting for local postgres server recovery if any in progress:LAUNCH_RECOVERY_CHECK_INTERVAL=30
pgslave2_1_645dab692bcb | >>> Recovery is in progress:
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.303 UTC [195] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.304 UTC [195] LOG:  listening on IPv6 address "::", port 5432
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.308 UTC [195] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.340 UTC [204] LOG:  database system was interrupted while in recovery at log time 2018-12-26 23:57:06 UTC
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.340 UTC [204] HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.360 UTC [204] LOG:  entering standby mode
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.362 UTC [204] LOG:  redo starts at 0/3000028
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.363 UTC [204] LOG:  consistent recovery state reached at 0/5000908
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.363 UTC [204] LOG:  invalid record length at 0/5000908: wanted 24, got 0
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.364 UTC [195] LOG:  database system is ready to accept read only connections
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.376 UTC [208] LOG:  started streaming WAL from primary at 0/5000000 on timeline 1
pgslave2_1_645dab692bcb | 2018-12-26 23:57:48.097 UTC [209] LOG:  incomplete startup packet
pgslave2_1_645dab692bcb | >>> Cloning is done
pgslave2_1_645dab692bcb | >>>>>> WAL id:<PHONE_NUMBER>00000000000005
pgslave2_1_645dab692bcb | >>>>>> WAL_RECEIVER_FLAG=1!
pgslave2_1_645dab692bcb | >>> Not in recovery state (anymore)
pgslave2_1_645dab692bcb | >>> Waiting for local postgres server start...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.public on pgslave2:5432(user: replication_user,password: *******), will try 9 times with delay 10 seconds (TIMEOUT=90)
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.public exists on host pgslave2:5432!
pgslave2_1_645dab692bcb | >>> Unregister the node if it was done before
pgslave2_1_645dab692bcb | ERROR:  cannot execute DELETE in a read-only transaction
pgslave2_1_645dab692bcb | >>> Registering node with role standby
pgslave2_1_645dab692bcb | INFO: connecting to local node "node3" (ID: 3)
pgslave2_1_645dab692bcb | INFO: connecting to primary database
pgslave2_1_645dab692bcb | WARNING: --upstream-node-id not supplied, assuming upstream node is primary (node ID 1)
pgslave2_1_645dab692bcb | INFO: executing notification command for event "standby_register"
pgslave2_1_645dab692bcb | DETAIL: command is:
pgslave2_1_645dab692bcb |   /usr/local/bin/cluster/repmgr/events/router.sh 3 standby_register 1 "2018-12-26 23:58:17.474092+00" "standby registration succeeded (-F/--force option was used)"
pgslave2_1_645dab692bcb | [REPMGR EVENT] Node id: 3; Event type: standby_register; Success [1|0]: 1; Time: 2018-12-26 23:58:17.474092+00;  Details: standby registration succeeded (-F/--force option was used)
pgslave2_1_645dab692bcb | INFO: standby registration complete
pgslave2_1_645dab692bcb | NOTICE: standby node "node3" (id: 3) successfully registered
pgslave2_1_645dab692bcb |  Locking standby (NEW_UPSTREAM_NODE_ID=1)...
pgslave2_1_645dab692bcb | >>> Starting repmgr daemon...
pgslave2_1_645dab692bcb | INFO: looking for configuration file in /etc
pgslave2_1_645dab692bcb | INFO: configuration file found at: "/etc/repmgr.conf"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [NOTICE] repmgrd (repmgr 4.0.6) starting up
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [INFO] connecting to database "user=replication_user password=replication_pass host=pgslave2 dbname=replication_db port=5432 connect_timeout=2"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [NOTICE] starting monitoring of node "node3" (ID: 3)
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [INFO] executing notification command for event "repmgrd_start"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [DETAIL] command is:
pgslave2_1_645dab692bcb |   /usr/local/bin/cluster/repmgr/events/router.sh 3 repmgrd_start 1 "2018-12-26 23:58:17.577402+00" "monitoring connection to upstream node \"node1\" (node ID: 1)"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [INFO] monitoring connection to upstream node "node1" (node ID: 1)
pgslave2_1_645dab692bcb | >>> Setting up STOP handlers...
pgslave2_1_645dab692bcb | >>> STARTING SSH (if required)...
pgslave2_1_645dab692bcb | cp: cannot stat '/home/postgres/.ssh/keys/*': No such file or directory
pgslave2_1_645dab692bcb | No pre-populated ssh keys!
pgslave2_1_645dab692bcb | >>> SSH is not enabled!
pgslave2_1_645dab692bcb | >>> STARTING POSTGRES...
pgslave2_1_645dab692bcb | >>> SETTING UP POLYMORPHIC VARIABLES (repmgr=3+postgres=9 | repmgr=4, postgres=10)...
pgslave2_1_645dab692bcb | >>> TUNING UP POSTGRES...
pgslave2_1_645dab692bcb | >>> Cleaning data folder which might have some garbage...
pgslave2_1_645dab692bcb | >>> Auto-detected master name: ''
pgslave2_1_645dab692bcb | >>> Setting up repmgr...
pgslave2_1_645dab692bcb | >>> Setting up repmgr config file '/etc/repmgr.conf'...
pgslave2_1_645dab692bcb | >>> Setting up upstream node...
pgslave2_1_645dab692bcb | cat: /var/lib/postgresql/data/standby.lock: No such file or directory
pgslave2_1_645dab692bcb | >>> Previously Locked standby upstream node LOCKED_STANDBY=''
pgslave2_1_645dab692bcb | >>> Waiting for upstream postgres server...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.repmgr on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 30 times more)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 29 times more)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 28 times more)
pgslave2_1_645dab692bcb | psql: could not connect to server: Connection refused
pgslave2_1_645dab692bcb |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave2_1_645dab692bcb |       TCP/IP connections on port 5432?
pgslave2_1_645dab692bcb | >>>>>> Host pgslave1:5432 is not accessible (will try 27 times more)
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.repmgr exists on host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> Waiting for upstream node id replication_db on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id is still not accessible on host pgslave1:5432 (will try 30 times more)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id is still not accessible on host pgslave1:5432 (will try 29 times more)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id is still not accessible on host pgslave1:5432 (will try 28 times more)
pgslave2_1_645dab692bcb | >>>>>> Upstream node id 2 received from host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> REPLICATION_UPSTREAM_NODE_ID=2
pgslave2_1_645dab692bcb | >>> Sending in background postgres start...
pgslave2_1_645dab692bcb | >>> Waiting for upstream postgres server...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.repmgr on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.repmgr exists on host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> Starting standby node...
pgslave2_1_645dab692bcb | >>> Instance hasn't been set up yet.
pgslave2_1_645dab692bcb | >>> Clonning primary node...
pgslave2_1_645dab692bcb | >>> Waiting for upstream postgres server...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.repmgr on pgslave1:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave2_1_645dab692bcb | NOTICE: destination directory "/var/lib/postgresql/data" provided
pgslave2_1_645dab692bcb | INFO: connecting to source node
pgslave2_1_645dab692bcb | DETAIL: connection string is: host=pgslave1 user=replication_user port=5432 dbname=replication_db
pgslave2_1_645dab692bcb | DETAIL: current installation size is 37 MB
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.repmgr exists on host pgslave1:5432!
pgslave2_1_645dab692bcb | >>> Waiting for cloning on this node is over(if any in progress): CLEAN_UP_ON_FAIL=, INTERVAL=30
pgslave2_1_645dab692bcb | >>> Replicated: 0
pgslave2_1_645dab692bcb | INFO: checking and correcting permissions on existing directory "/var/lib/postgresql/data"
pgslave2_1_645dab692bcb | NOTICE: starting backup (using pg_basebackup)...
pgslave2_1_645dab692bcb | INFO: executing:
pgslave2_1_645dab692bcb |   /usr/lib/postgresql/10/bin/pg_basebackup -l "repmgr base backup"  -D /var/lib/postgresql/data -h pgslave1 -p 5432 -U replication_user -c fast -X stream -S repmgr_slot_3
pgslave2_1_645dab692bcb | NOTICE: creating replication slot "repmgr_slot_3" on upstream node 1
pgslave2_1_645dab692bcb | NOTICE: replication slot "repmgr_slot_3" deleted on source node
pgslave2_1_645dab692bcb | NOTICE: standby clone (using pg_basebackup) complete
pgslave2_1_645dab692bcb | NOTICE: you can now start your PostgreSQL server
pgslave2_1_645dab692bcb | HINT: for example: pg_ctl -D /var/lib/postgresql/data start
pgslave2_1_645dab692bcb | HINT: after starting the server, you need to register this standby with "repmgr standby register"
pgslave2_1_645dab692bcb | INFO: executing notification command for event "standby_clone"
pgslave2_1_645dab692bcb | DETAIL: command is:
pgslave2_1_645dab692bcb |   /usr/local/bin/cluster/repmgr/events/router.sh 3 standby_clone 1 "2018-12-26 23:57:47.269342+00" "cloned from host \"pgslave1\", port 5432; backup method: pg_basebackup; --force: Y"
pgslave2_1_645dab692bcb | [REPMGR EVENT] Node id: 3; Event type: standby_clone; Success [1|0]: 1; Time: 2018-12-26 23:57:47.269342+00;  Details: cloned from host "pgslave1", port 5432; backup method: pg_basebackup; --force: Y
pgslave2_1_645dab692bcb | >>> Configuring /var/lib/postgresql/data/postgresql.conf
pgslave2_1_645dab692bcb | >>>>>> Will add configs to the exists file
pgslave2_1_645dab692bcb | >>>>>> Adding config 'listen_addresses'=''*''
pgslave2_1_645dab692bcb | >>>>>> Adding config 'shared_preload_libraries'=''repmgr''
pgslave2_1_645dab692bcb | >>> Starting postgres...
pgslave2_1_645dab692bcb | >>> Waiting for local postgres server recovery if any in progress:LAUNCH_RECOVERY_CHECK_INTERVAL=30
pgslave2_1_645dab692bcb | >>> Recovery is in progress:
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.303 UTC [195] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.304 UTC [195] LOG:  listening on IPv6 address "::", port 5432
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.308 UTC [195] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.340 UTC [204] LOG:  database system was interrupted while in recovery at log time 2018-12-26 23:57:06 UTC
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.340 UTC [204] HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.360 UTC [204] LOG:  entering standby mode
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.362 UTC [204] LOG:  redo starts at 0/3000028
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.363 UTC [204] LOG:  consistent recovery state reached at 0/5000908
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.363 UTC [204] LOG:  invalid record length at 0/5000908: wanted 24, got 0
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.364 UTC [195] LOG:  database system is ready to accept read only connections
pgslave2_1_645dab692bcb | 2018-12-26 23:57:47.376 UTC [208] LOG:  started streaming WAL from primary at 0/5000000 on timeline 1
pgslave2_1_645dab692bcb | 2018-12-26 23:57:48.097 UTC [209] LOG:  incomplete startup packet
pgslave2_1_645dab692bcb | >>> Cloning is done
pgslave2_1_645dab692bcb | >>>>>> WAL id:<PHONE_NUMBER>00000000000005
pgslave2_1_645dab692bcb | >>>>>> WAL_RECEIVER_FLAG=1!
pgslave2_1_645dab692bcb | >>> Not in recovery state (anymore)
pgslave2_1_645dab692bcb | >>> Waiting for local postgres server start...
pgslave2_1_645dab692bcb | >>> Wait schema replication_db.public on pgslave2:5432(user: replication_user,password: *******), will try 9 times with delay 10 seconds (TIMEOUT=90)
pgslave2_1_645dab692bcb | >>>>>> Schema replication_db.public exists on host pgslave2:5432!
pgslave2_1_645dab692bcb | >>> Unregister the node if it was done before
pgslave2_1_645dab692bcb | ERROR:  cannot execute DELETE in a read-only transaction
pgslave2_1_645dab692bcb | >>> Registering node with role standby
pgslave2_1_645dab692bcb | INFO: connecting to local node "node3" (ID: 3)
pgslave2_1_645dab692bcb | INFO: connecting to primary database
pgslave2_1_645dab692bcb | WARNING: --upstream-node-id not supplied, assuming upstream node is primary (node ID 1)
pgslave2_1_645dab692bcb | INFO: executing notification command for event "standby_register"
pgslave2_1_645dab692bcb | DETAIL: command is:
pgslave2_1_645dab692bcb |   /usr/local/bin/cluster/repmgr/events/router.sh 3 standby_register 1 "2018-12-26 23:58:17.474092+00" "standby registration succeeded (-F/--force option was used)"
pgslave2_1_645dab692bcb | [REPMGR EVENT] Node id: 3; Event type: standby_register; Success [1|0]: 1; Time: 2018-12-26 23:58:17.474092+00;  Details: standby registration succeeded (-F/--force option was used)
pgslave2_1_645dab692bcb | INFO: standby registration complete
pgslave2_1_645dab692bcb | NOTICE: standby node "node3" (id: 3) successfully registered
pgslave2_1_645dab692bcb |  Locking standby (NEW_UPSTREAM_NODE_ID=1)...
pgslave2_1_645dab692bcb | >>> Starting repmgr daemon...
pgslave2_1_645dab692bcb | INFO: looking for configuration file in /etc
pgslave2_1_645dab692bcb | INFO: configuration file found at: "/etc/repmgr.conf"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [NOTICE] repmgrd (repmgr 4.0.6) starting up
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [INFO] connecting to database "user=replication_user password=replication_pass host=pgslave2 dbname=replication_db port=5432 connect_timeout=2"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [NOTICE] starting monitoring of node "node3" (ID: 3)
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [INFO] executing notification command for event "repmgrd_start"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [DETAIL] command is:
pgslave2_1_645dab692bcb |   /usr/local/bin/cluster/repmgr/events/router.sh 3 repmgrd_start 1 "2018-12-26 23:58:17.577402+00" "monitoring connection to upstream node \"node1\" (node ID: 1)"
pgslave2_1_645dab692bcb | [2018-12-26 23:58:17] [INFO] monitoring connection to upstream node "node1" (node ID: 1)

pgslave1_1_d43e93f50353 | >>> Setting up STOP handlers...
pgslave1_1_d43e93f50353 | >>> STARTING SSH (if required)...
pgslave1_1_d43e93f50353 | >>> TUNING UP SSH CLIENT...
pgslave1_1_d43e93f50353 | >>> STARTING SSH SERVER...
pgslave1_1_d43e93f50353 | >>> STARTING POSTGRES...
pgslave1_1_d43e93f50353 | >>> SETTING UP POLYMORPHIC VARIABLES (repmgr=3+postgres=9 | repmgr=4, postgres=10)...
pgslave1_1_d43e93f50353 | >>> TUNING UP POSTGRES...
pgslave1_1_d43e93f50353 | >>> Cleaning data folder which might have some garbage...
pgslave1_1_d43e93f50353 | >>> Check all partner nodes for common upstream node...
pgslave1_1_d43e93f50353 | >>>>>> Checking NODE=pgmaster...
pgslave1_1_d43e93f50353 | psql: could not connect to server: Connection refused
pgslave1_1_d43e93f50353 |       Is the server running on host "pgmaster" (<IP_ADDRESS>) and accepting
pgslave1_1_d43e93f50353 |       TCP/IP connections on port 5432?
pgslave1_1_d43e93f50353 | >>>>>> Skipping: failed to get master from the node!
pgslave1_1_d43e93f50353 | >>>>>> Checking NODE=pgslave1...
pgslave1_1_d43e93f50353 | psql: could not connect to server: Connection refused
pgslave1_1_d43e93f50353 |       Is the server running on host "pgslave1" (<IP_ADDRESS>) and accepting
pgslave1_1_d43e93f50353 |       TCP/IP connections on port 5432?
pgslave1_1_d43e93f50353 | >>>>>> Skipping: failed to get master from the node!
pgslave1_1_d43e93f50353 | >>>>>> Checking NODE=pgslave3...
pgslave1_1_d43e93f50353 | psql: could not connect to server: Connection refused
pgslave1_1_d43e93f50353 |       Is the server running on host "pgslave3" (<IP_ADDRESS>) and accepting
pgslave1_1_d43e93f50353 |       TCP/IP connections on port 5432?
pgslave1_1_d43e93f50353 | >>>>>> Skipping: failed to get master from the node!
pgslave1_1_d43e93f50353 | >>> Auto-detected master name: ''
pgslave1_1_d43e93f50353 | >>> Setting up repmgr...
pgslave1_1_d43e93f50353 | >>> Setting up repmgr config file '/etc/repmgr.conf'...
pgslave1_1_d43e93f50353 | >>> Setting up upstream node...
pgslave1_1_d43e93f50353 | cat: /var/lib/postgresql/data/standby.lock: No such file or directory
pgslave1_1_d43e93f50353 | >>> Previously Locked standby upstream node LOCKED_STANDBY=''
pgslave1_1_d43e93f50353 | >>> Waiting for upstream postgres server...
pgslave1_1_d43e93f50353 | >>> Wait schema replication_db.repmgr on pgmaster:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave1_1_d43e93f50353 | psql: could not connect to server: Connection refused
pgslave1_1_d43e93f50353 |       Is the server running on host "pgmaster" (<IP_ADDRESS>) and accepting
pgslave1_1_d43e93f50353 |       TCP/IP connections on port 5432?
pgslave1_1_d43e93f50353 | >>>>>> Host pgmaster:5432 is not accessible (will try 30 times more)
pgslave1_1_d43e93f50353 | >>>>>> Schema replication_db.repmgr is still not accessible on host pgmaster:5432 (will try 29 times more)
pgslave1_1_d43e93f50353 | >>>>>> Schema replication_db.repmgr is still not accessible on host pgmaster:5432 (will try 28 times more)
pgslave1_1_d43e93f50353 | >>>>>> Schema replication_db.repmgr exists on host pgmaster:5432!
pgslave1_1_d43e93f50353 | >>> Waiting for upstream node id replication_db on pgmaster:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave1_1_d43e93f50353 | >>>>>> Upstream node id 1 received from host pgmaster:5432!
pgslave1_1_d43e93f50353 | >>> REPLICATION_UPSTREAM_NODE_ID=1
pgslave1_1_d43e93f50353 | >>> Sending in background postgres start...
pgslave1_1_d43e93f50353 | >>> Waiting for upstream postgres server...
pgslave1_1_d43e93f50353 | >>> Wait schema replication_db.repmgr on pgmaster:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave1_1_d43e93f50353 | >>>>>> Schema replication_db.repmgr exists on host pgmaster:5432!
pgslave1_1_d43e93f50353 | >>> Starting standby node...
pgslave1_1_d43e93f50353 | >>> Instance hasn't been set up yet.
pgslave1_1_d43e93f50353 | >>> Clonning primary node...
pgslave1_1_d43e93f50353 | >>> Waiting for upstream postgres server...
pgslave1_1_d43e93f50353 | >>> Wait schema replication_db.repmgr on pgmaster:5432(user: replication_user,password: *******), will try 30 times with delay 10 seconds (TIMEOUT=300)
pgslave1_1_d43e93f50353 | NOTICE: destination directory "/var/lib/postgresql/data" provided
pgslave1_1_d43e93f50353 | INFO: connecting to source node
pgslave1_1_d43e93f50353 | DETAIL: connection string is: host=pgmaster user=replication_user port=5432 dbname=replication_db
pgslave1_1_d43e93f50353 | DETAIL: current installation size is 37 MB
pgslave1_1_d43e93f50353 | INFO: checking and correcting permissions on existing directory "/var/lib/postgresql/data"
pgslave1_1_d43e93f50353 | NOTICE: starting backup (using pg_basebackup)...
pgslave1_1_d43e93f50353 | INFO: executing:
pgslave1_1_d43e93f50353 |   /usr/lib/postgresql/10/bin/pg_basebackup -l "repmgr base backup"  -D /var/lib/postgresql/data -h pgmaster -p 5432 -U replication_user -c fast -X stream -S repmgr_slot_2
pgslave1_1_d43e93f50353 | >>>>>> Schema replication_db.repmgr exists on host pgmaster:5432!
pgslave1_1_d43e93f50353 | >>> Waiting for cloning on this node is over(if any in progress): CLEAN_UP_ON_FAIL=, INTERVAL=30
pgslave1_1_d43e93f50353 | >>> Replicated: 0
pgslave1_1_d43e93f50353 | NOTICE: standby clone (using pg_basebackup) complete
pgslave1_1_d43e93f50353 | NOTICE: you can now start your PostgreSQL server
pgslave1_1_d43e93f50353 | HINT: for example: pg_ctl -D /var/lib/postgresql/data start
pgslave1_1_d43e93f50353 | HINT: after starting the server, you need to register this standby with "repmgr standby register"
pgslave1_1_d43e93f50353 | INFO: executing notification command for event "standby_clone"
pgslave1_1_d43e93f50353 | DETAIL: command is:
pgslave1_1_d43e93f50353 |   /usr/local/bin/cluster/repmgr/events/router.sh 2 standby_clone 1 "2018-12-26 23:57:06.86315+00" "cloned from host \"pgmaster\", port 5432; backup method: pg_basebackup; --force: Y"
pgslave1_1_d43e93f50353 | [REPMGR EVENT] Node id: 2; Event type: standby_clone; Success [1|0]: 1; Time: 2018-12-26 23:57:06.86315+00;  Details: cloned from host "pgmaster", port 5432; backup method: pg_basebackup; --force: Y
pgslave1_1_d43e93f50353 | >>> Configuring /var/lib/postgresql/data/postgresql.conf
pgslave1_1_d43e93f50353 | >>>>>> Will add configs to the exists file
pgslave1_1_d43e93f50353 | >>>>>> Adding config 'max_replication_slots'='10'
pgslave1_1_d43e93f50353 | >>>>>> Adding config 'shared_preload_libraries'=''repmgr''
pgslave1_1_d43e93f50353 | >>> Starting postgres...
pgslave1_1_d43e93f50353 | >>> Waiting for local postgres server recovery if any in progress:LAUNCH_RECOVERY_CHECK_INTERVAL=30
pgslave1_1_d43e93f50353 | >>> Recovery is in progress:
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:06.984 UTC [187] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:06.985 UTC [187] LOG:  listening on IPv6 address "::", port 5432
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:06.986 UTC [187] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.050 UTC [197] LOG:  database system was interrupted; last known up at 2018-12-26 23:57:06 UTC
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.068 UTC [197] LOG:  entering standby mode
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.071 UTC [197] LOG:  redo starts at 0/3000028
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.071 UTC [197] LOG:  consistent recovery state reached at 0/4000248
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.072 UTC [187] LOG:  database system is ready to accept read only connections
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.085 UTC [201] LOG:  started streaming WAL from primary at 0/5000000 on timeline 1
pgslave1_1_d43e93f50353 | 2018-12-26 23:57:07.710 UTC [202] LOG:  incomplete startup packet
pgslave1_1_d43e93f50353 | >>> Cloning is done
pgslave1_1_d43e93f50353 | >>>>>> WAL id:<PHONE_NUMBER>00000000000005
pgslave1_1_d43e93f50353 | >>>>>> WAL_RECEIVER_FLAG=1!
pgslave1_1_d43e93f50353 | >>> Not in recovery state (anymore)
pgslave1_1_d43e93f50353 | >>> Waiting for local postgres server start...
pgslave1_1_d43e93f50353 | >>> Wait schema replication_db.public on pgslave1:5432(user: replication_user,password: *******), will try 9 times with delay 10 seconds (TIMEOUT=90)
pgslave1_1_d43e93f50353 | >>>>>> Schema replication_db.public exists on host pgslave1:5432!
pgslave1_1_d43e93f50353 | >>> Unregister the node if it was done before
pgslave1_1_d43e93f50353 | DELETE 0
pgslave1_1_d43e93f50353 | >>> Registering node with role standby
pgslave1_1_d43e93f50353 | INFO: connecting to local node "node2" (ID: 2)
pgslave1_1_d43e93f50353 | INFO: connecting to primary database
pgslave1_1_d43e93f50353 | WARNING: --upstream-node-id not supplied, assuming upstream node is primary (node ID 1)
pgslave1_1_d43e93f50353 | INFO: executing notification command for event "standby_register"
pgslave1_1_d43e93f50353 | DETAIL: command is:
pgslave1_1_d43e93f50353 |   /usr/local/bin/cluster/repmgr/events/router.sh 2 standby_register 1 "2018-12-26 23:57:37.128943+00" "standby registration succeeded (-F/--force option was used)"
pgslave1_1_d43e93f50353 | [REPMGR EVENT] Node id: 2; Event type: standby_register; Success [1|0]: 1; Time: 2018-12-26 23:57:37.128943+00;  Details: standby registration succeeded (-F/--force option was used)
pgslave1_1_d43e93f50353 | INFO: standby registration complete
pgslave1_1_d43e93f50353 | NOTICE: standby node "node2" (id: 2) successfully registered
pgslave1_1_d43e93f50353 |  Locking standby (NEW_UPSTREAM_NODE_ID=1)...
pgslave1_1_d43e93f50353 | >>> Starting repmgr daemon...
pgslave1_1_d43e93f50353 | INFO: looking for configuration file in /etc
pgslave1_1_d43e93f50353 | INFO: configuration file found at: "/etc/repmgr.conf"
pgslave1_1_d43e93f50353 | [2018-12-26 23:57:37] [NOTICE] repmgrd (repmgr 4.0.6) starting up
pgslave1_1_d43e93f50353 | [2018-12-26 23:57:37] [INFO] connecting to database "user=replication_user password=replication_pass host=pgslave1 dbname=replication_db port=5432 connect_timeout=2"
pgslave1_1_d43e93f50353 | [2018-12-26 23:57:37] [NOTICE] starting monitoring of node "node2" (ID: 2)
pgslave1_1_d43e93f50353 | [2018-12-26 23:57:37] [INFO] executing notification command for event "repmgrd_start"
pgslave1_1_d43e93f50353 | [2018-12-26 23:57:37] [DETAIL] command is:
pgslave1_1_d43e93f50353 |   /usr/local/bin/cluster/repmgr/events/router.sh 2 repmgrd_start 1 "2018-12-26 23:57:37.238597+00" "monitoring connection to upstream node \"node1\" (node ID: 1)"
pgslave1_1_d43e93f50353 | [2018-12-26 23:57:37] [INFO] monitoring connection to upstream node "node1" (node ID: 1)
pgslave1_1_d43e93f50353 | 2018-12-26 23:58:17.426 UTC [314] ERROR:  cannot execute DELETE in a read-only transaction
pgslave1_1_d43e93f50353 | 2018-12-26 23:58:17.426 UTC [314] STATEMENT:  DELETE FROM repmgr.nodes WHERE conninfo LIKE '%host=pgslave2%'

I'm having the same issue...


Update information on the new Bulk updates method in the Efficient Updating section

This page Efficient Updating include outdated information like "Unfortunately, EF doesn't currently provide APIs for performing bulk updates. Until these are introduced, you can use raw SQL to perform the operation where performance is sensitive". New documentation for ExecuteUpdate are needed.

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

ID: f37e820a-137f-92c9-6662-06fafeac097a
Version Independent ID: 0df73aed-692f-0e53-7562-ed3d8b89c6df
Content: Efficient Updating - EF Core
Content Source: entity-framework/core/performance/efficient-updating.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

Duplicate of #4032


Android build tools outdated

I see Android build tools are outdated, currently here it's 2.2.0, but the world is on 3.6.3.
so I updated it locally and run into this gradle-fury which is 4 years old on only support

Using such a helper tools is a future blocker to modernize. Now this repo is in this situation.
Ok, want to  modernize, remove at least this helper, probable more and simplify build and setup.
Which means it will change a lot
But I want to save my time and I'm afraid about a lot of doubt on maintainer side and the pull request will never merged.
So I ask you, what are you thinking about this ?

@hannesa2 Does it solve #1560 ?

I made a pull request for it https://github.com/osmdroid/osmdroid/pull/1594

@hannesa2 Does it solve #1560 ?

CI builds

But this test a questionable (crap) because locally I run currently into

Lint is also in a bad condition

@monsieurtanuki I guess you are a maintainer. Please allow Github actions to run Gradle verification

@hannesa2 My part in the project is about developing in Java and reviewing code. I have not the slightest idea about anything around gradle and I cannot validate or change parameters I do not understand at all.
I know @spyhunter99 has much clearer ideas about the whole process. If you guys could manage to upgrade and improve the build process, that would be awesome!

@spyhunter99
Now I need you review https://github.com/osmdroid/osmdroid/pull/1594 and please enable Github actions

i'll look at it tonight.
On Thu, May 28, 2020 at 5:07 AM hannesa2<EMAIL_ADDRESS>wrote:

@spyhunter99 https://github.com/spyhunter99
Now I need you review #1594
https://github.com/osmdroid/osmdroid/pull/1594 and please enable Github
actions
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/1593#issuecomment-635217788,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPCIGNP4LLJMHOJMFFR7JTRTYSTHANCNFSM4NJ7KHAQ
.

fixed


Update README references for example code

Update README references for example code

👍

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (187630b) 70.98% compared to head (da7578a) 70.98%.

:exclamation: Current head da7578a differs from pull request most recent head 52a5e5a. Consider uploading reports for the commit 52a5e5a to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##               main     #447   +/-   ##
=========================================
  Coverage     70.98%   70.98%
  Complexity      676      676
=========================================
  Files           118      118
  Lines          2547     2547
  Branches        195      195
=========================================
  Hits           1808     1808
  Misses          620      620
  Partials        119      119

Flag
Coverage Δ

unittests
70.98% <ø> (ø)

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

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

👍


LogManager error reported during container startup using Keycloak 26.0.1

Describe the bug
Just tried moving my environment to Keycloak 26.0.1. Running my integration tests which starts a Keycloak testcontainer I see an ERROR during startup (see logging output). Also note that this error appears to be benign (the testcontainer starts successfully) except that I had to exclude slf4j-jboss-logmanager to see log output from the testcontainer.
<dependency>
  <groupId>org.keycloak</groupId>
  <artifactId>keycloak-services</artifactId>
  <version>${keycloak.version}</version>
  <scope>provided</scope>
  <exclusions>
    <exclusion>
	<groupId>org.jboss.slf4j</groupId>
	<artifactId>slf4j-jboss-logmanager</artifactId>
    </exclusion>
  </exclusions>
</dependency>

This allows my reload4j dependency to work:
<dependency>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-reload4j</artifactId>
  <version>${slf4j.version}</version>
  <scope>test</scope>
</dependency>

Version
3.4.0
Expected behavior
The testcontainer should start without the ERROR message.
Actual behavior
No response
How to Reproduce?
No response
Relevant log output
Note ERROR at end of logging output

0    [main] INFO  org.testcontainers.images.PullPolicy  - Image pull policy will be performed by: DefaultPullPolicy()
3    [main] INFO  org.testcontainers.utility.ImageNameSubstitutor  - Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
244  [main] INFO  org.testcontainers.dockerclient.DockerClientProviderStrategy  - Loaded org.testcontainers.dockerclient.UnixSocketClientProviderStrategy from ~/.testcontainers.properties, will try it first
581  [main] INFO  org.testcontainers.dockerclient.DockerClientProviderStrategy  - Found Docker environment with local Unix socket (unix:///var/run/docker.sock)
590  [main] INFO  org.testcontainers.DockerClientFactory  - Docker host IP address is localhost
619  [main] INFO  org.testcontainers.DockerClientFactory  - Connected to docker:
  Server Version: 27.2.0
  API Version: 1.47
  Operating System: Docker Desktop
  Total Memory: 8932 MB
765  [main] INFO  tc.testcontainers/ryuk:0.7.0  - Creating container for image: testcontainers/ryuk:0.7.0
1024 [main] INFO  tc.testcontainers/ryuk:0.7.0  - Container testcontainers/ryuk:0.7.0 is starting: 7b533cb08119bd68840dc79a91a0d60f3f5ee32b8a9aebd7849940ad3e08a87e
1404 [main] INFO  tc.testcontainers/ryuk:0.7.0  - Container testcontainers/ryuk:0.7.0 started in PT0.638728S
1427 [main] INFO  org.testcontainers.utility.RyukResourceReaper  - Ryuk started - will monitor and terminate Testcontainers containers on JVM exit
1428 [main] INFO  org.testcontainers.DockerClientFactory  - Checking the system...
1430 [main] INFO  org.testcontainers.DockerClientFactory  - ✔ Docker server version should be at least 1.6.0
1556 [main] INFO  tc.quay.io/keycloak/keycloak:26.0.1  - Creating container for image: quay.io/keycloak/keycloak:26.0.1
1609 [main] INFO  org.testcontainers.utility.RegistryAuthLocator  - Credential helper/store (docker-credential-desktop) does not have credentials for quay.io
1920 [main] INFO  tc.quay.io/keycloak/keycloak:26.0.1  - Container quay.io/keycloak/keycloak:26.0.1 is starting: 282f9ed8e8348aa17e18bd8ec1935f6f46187dc5f9b106fe6feeb2397898bd24
2045 [docker-java-stream-1392774682] INFO  tc.quay.io/keycloak/keycloak:26.0.1  - STDOUT: JAVA_OPTS_KC_HEAP already set in environment; overriding default settings
2064 [main] INFO  org.testcontainers.containers.wait.strategy.HttpWaitStrategy  - /gifted_goldwasser: Waiting for 120 seconds for URL: http://localhost:57077/health/started (where port 57077 maps to container port 9000)
Oct 23, 2024 3:07:19 PM org.jboss.logmanager.JBossLoggerFinder getLogger
ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected.

Anything else?
No response

Yes, and as I pointed out it's easily worked around, so not a high priority issue at all. If nothing else, might be worth a mention in the README. Thanks for the quick response!

Yes, the workaround is easy, but has to be done in the using project.
I can mention it in the README, and at the same time I have doubts that this is being read by anybody. 😅


Use Go 1.10 for Travis builds.

Updates .travis.yml to use 1.10.3 along with some tweaks to make things work correctly in 1.10.

Coverage increased (+0.01%) to 32.871% when pulling 072cc58db87a9fe48831d5c23dba2859d1c6378a on TS_travis into a3e8af71c0d498e63f066dae5c71079bf4601c25 on master.

Hmm. Tests were working before but are now failing. Need to investigate.

This is showing as failing, but multiples retries have worked. It seems to have been a transient issue.
e.g. https://travis-ci.org/OpenBazaar/openbazaar-go/builds/408207750

All fixed and ready to go.


Footer will be same for all pages

Currently there are different footers for different pages.

@akshathar-navada closing this issue as it is merged.


Add component factory support

Subcomponent factories are about 90% supported with this change, but to keep the diff reviewable I'll leave them out for a follow-up. There's also test coverage missing for all the cases where exceptions could be thrown but that can also come later.

I was going to rebase this on a refactor, but I'll just rebase my refactor on this.


Redesign src/ layout for more efficient builds

I think every binary's main module in src/app/ is causing lots of unnecessary building.

Some work was done for this but is it complete yet?


SUCCESSFULLY ENHANCED THE HEADER

### 📋 Description
Enhanced the header section to improve its interactivity and overall visual appeal. The header now includes advanced CSS features, icons, hover effects, and a responsive design. The changes aim to provide a more engaging and user-friendly experience.
🔨 Changes Made
Added advanced CSS effects for hover and focus on header elements.
Integrated icons from Boxicons to enhance clarity and aesthetics.
Improved header responsiveness for better display on different screen sizes.
✅ Checklist
Before submitting the PR, please make sure you have completed the following:
I have followed all the guidelines mentioned in CONTRIBUTING.md.
My code follows the style guidelines of this project.
I have performed a self-review of my own code.
I have commented my code, particularly in hard-to-understand areas.
I have made corresponding changes to the documentation (if applicable).
I have tested it locally and it works fine.
Any dependent changes have been merged and published in downstream modules.
🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)
Bug fix (non-breaking change which fixes an issue) 🐛
New feature (non-breaking change which adds functionality) ✨
UI enhancement (non-breaking change which enhances UI) 🎨
Documentation update 📚
Fixes #236
solved issue: #236
📸 Screenshots (if applicable)

Thank you for contributing to Research Nexus! We look forward to reviewing your PR and getting it merged!

SIR I HAD SUCCESSFULLT RESOLVED THE ISSUE SO I AM REQUESTING YOU TO PLEASE REVEIW THE CHANGES AND MERGE THE PR.. PLEASE AND PLEASE ENCOURAGE @Harshdev098


Issues URL not working

Issues: https://issues.projectbluefin.io/
Doesn't work, forgot to migrate dns.

🌭


Telecine stops recording and goes into ghost state when the app being recorded crashes

I have experienced this couple of times, not sure 100% of the times
Trying to document a crash in our app and Telecine works great up to the moment the app crashes. It then goes into a "ghost" state - Telecine missing from notification area, can't find a way to stop it, I still see the touch highlights on the screen, don't see the video recording in the pictures folder.
Android N on Nexus 5X (build NPD56N)

I see that show touches remained enabled so I assume that Telecine crashed and that it just haven't disabled the show touches setting. Probably related to #91

It's highly unlikely that it's a crash. What probably happened was the system killed the Telecine process to reclaim memory when your app crashed. You can enable the foreground notification in the app to help prevent against this, but otherwise this is basically impossible to prevent.


Setup pullpo.io

Related to #802

/progress 10
Started the discussion here to get code owners approval

/progress 20
We can set it up in studio and glee, waiting for cli

Hey @Amzani, can I take this up?

Thanks @SamarthAroraa however this is already in progress and this task doesn't require any code.
For more information check this discussion here

/progress 50
I got approval from code owners to set it up in cli, glee and studio : https://github.com/orgs/asyncapi/discussions/920
Next: @fmvilas to help with the setup as we need an admin for that.

/progress 100
Done