On the RTX8000, finetune.py fails during execution even when set with parameters that consume less memory.

I attempted to run finetune.py on BridgeDataV2. Due to previous errors in the code, I changed bfloat16 to float32 and commented out attn_implementation. Despite setting the parameters to minimize memory consumption (--lora_rank 1 --batch_size 1), I still encountered the error shown below.
Is there any other way to reduce memory consumption? Or is it inherently difficult to finetune in this environment?
Environment:

OS: Ubuntu20.04
RAM: 64GB
CPU: Intel(R) Core(TM) i9-10900X
GPU: Quadro RTX 8000
CUDA version: 12.0
torch: 2.2.0+cu121

(openvla) shimizke@linux:~/openvla$ torchrun --standalone --nnodes 1 --nproc-per-node 1 vla-scripts/finetune.py  --vla_path "openvla/openvla-7b"  --data_root_dir "test_dataset"  --dataset_name bridge_orig  --run_root_dir "checkpoints_log"  --adapter_tmp_dir "checkpoints_log/adapter_tmp"  --lora_rank 1  --batch_size 1  --grad_accumulation_steps 1  --learning_rate 5e-4  --image_aug False  --wandb_project xx  --wandb_entity xx  --save_steps 2 --max_steps 2
2024-09-17 12:51:12.271071: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-09-17 12:51:12.910081: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-09-17 12:51:12.910287: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-09-17 12:51:13.006465: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-09-17 12:51:13.185750: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
Fine-tuning OpenVLA Model `openvla/openvla-7b` on `bridge_orig`
Loading checkpoint shards:   0%|                                                                                | 0/3 [00:00<?, ?it/s]Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:32<00:00, 10.97s/it]
trainable params: 3,463,384 || all params: 7,544,700,568 || trainable%: 0.0459
2024-09-17 12:52:14.670779: I tensorflow/core/grappler/optimizers/data/replicate_on_split.cc:32] Running replicate on split optimization
09/17 [12:52:15] INFO     | >> [*] Loading existing dataset statistics from                                                                                data_utils.py:208
                          test_dataset/bridge_orig/1.0.0/dataset_statistics_190b974b6ae7dd751370de88a9c06039c7a7cc8f379a729919e4f11c4b647945.json.
2024-09-17 12:52:15.554584: I tensorflow/core/grappler/optimizers/data/replicate_on_split.cc:32] Running replicate on split optimization

######################################################################################
# Loading the following 1 datasets (incl. sampling weight):                         #
# bridge_orig: =============================================================1.000000 #
######################################################################################

09/17 [12:52:16] INFO     | >> [*] Threads per Dataset: [1]                                                                                dataset.py:531
                 INFO     | >> [*] Reads per Dataset: [1]                                                                                dataset.py:532
                 INFO     | >> [*] Constructing datasets...                                                                                dataset.py:535
2024-09-17 12:52:16.499813: I tensorflow/core/grappler/optimizers/data/replicate_on_split.cc:32] Running replicate on split optimization
09/17 [12:52:17] INFO     | >> [*] Applying frame transforms on dataset...                                                                                dataset.py:575
                 INFO     | >> [*] Saved dataset statistics file at path checkpoints_log/openvla-7b+bridge_orig+b1+lr-0.0005+lora-r1+dropout-0.0/dataset_statistics.json data_utils.py:293
wandb: (1) Create a W&B account
wandb: (2) Use an existing W&B account
wandb: (3) Don't visualize my results
wandb: Enter your choice: 3
wandb: WARNING Invalid choice
wandb: Enter your choice: 3
wandb: You chose 'Don't visualize my results'
wandb: Tracking run with wandb version 0.13.1
wandb: W&B syncing is set to `offline` in this directory.
wandb: Run `wandb online` or set WANDB_MODE=online to enable cloud syncing.
  0%|                                                                                | 0/2 [00:00<?, ?it/s]2024-09-17 12:53:00.466610: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:422] ShuffleDatasetV3:43: Filling up shuffle buffer (this may take a while): 54124 of 100000
2024-09-17 12:53:08.615404: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:452] Shuffle buffer filled.
3it [00:27,  6.42s/it]                                                                                Saving Model Checkpoint for Step 2
/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/peft/utils/save_and_load.py:180: UserWarning: Setting `save_embedding_layers` to `True` as embedding layers found in `target_modules`.
  warnings.warn("Setting `save_embedding_layers` to `True` as embedding layers found in `target_modules`.")
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:10<00:00,  3.66s/it]
Saved Model Checkpoint for Step 2 at: checkpoints_log/openvla-7b+bridge_orig+b1+lr-0.0005+lora-r1+dropout-0.0███████████████████████████████████████████████| 3/3 [00:10<00:00,  3.76s/it]
5it [01:52, 24.11s/it]Saving Model Checkpoint for Step 4
/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/peft/utils/save_and_load.py:180: UserWarning: Setting `save_embedding_layers` to `True` as embedding layers found in `target_modules`.
  warnings.warn("Setting `save_embedding_layers` to `True` as embedding layers found in `target_modules`.")
                                                                                [2024-09-17 12:57:47,877] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: -9) local_rank: 0 (pid: 2693110) of binary: /home/shimizke/miniconda3/envs/openvla/bin/python
Traceback (most recent call last):
  File "/home/shimizke/miniconda3/envs/openvla/bin/torchrun", line 8, in <module>
    sys.exit(main())
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 347, in wrapper
    return f(*args, **kwargs)
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/run.py", line 812, in main
    run(args)
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/run.py", line 803, in run
    elastic_launch(
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 135, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 268, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
========================================================
vla-scripts/finetune.py FAILED
--------------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
--------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-09-17_12:57:47
  host      : linux
  rank      : 0 (local_rank: 0)
  exitcode  : -9 (pid: 2693110)
  error_file: <N/A>
  traceback : Signal 9 (SIGKILL) received by PID 2693110
========================================================
Exception in thread MsgRouterThr:
Traceback (most recent call last):
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
    self.run()
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/threading.py", line 953, in run
    self._target(*self._args, **self._kwargs)
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/wandb/sdk/interface/router.py", line 69, in message_loop
    msg = self._read_message()
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/site-packages/wandb/sdk/interface/router_queue.py", line 32, in _read_message
    msg = self._response_queue.get(timeout=1)
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/multiprocessing/queues.py", line 117, in get
    res = self._recv_bytes()
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/multiprocessing/connection.py", line 212, in recv_bytes
    self._check_closed()
  File "/home/shimizke/miniconda3/envs/openvla/lib/python3.10/multiprocessing/connection.py", line 136, in _check_closed
    raise OSError("handle is closed")
OSError: handle is closed

P.S. Increasing the value of grad_accumulation_steps caused the same error.

mmh I think your GPU has 48GB of memory so I would expect LoRA finetuning to work on it. Could you try putting bfloat16 back in? It should reduce memory usage.
If nothing works QLoRA would be the other way to reduce memory, but it hasn't trained stably for me in the past. LoRA should really just work with the size of your GPU.

I reverted everything back to bfloat16 but encountered the same error as before(#103). When I changed the error point to float32, an out-of-memory error occurred, so I have converted all instances of bfloat16 in the code to float32.
This time, I changed only the bfloat16 within torch.autocast("cuda", dtype=torch.bfloat16): to float16. This adjustment allowed the process to complete fine-tuning without any memory errors.


fix react 15 special props issue

We noticed there were console warnings about keys being issued when using react-pager with react 15. This explains the issue: https://gist.github.com/jimfb/fb2a04fe3fa4637d7d62
This change eliminates the warnings.

@lvhntr, thank you!


[TEST] Make a test fail

Successfully proved the pull_request.yml action works

Successfully proved the pull_request.yml action works


Error: entered unreachable code: R1CS has a gate 1 * 1 = 1

When testing with  the following circom code
include "../../src/rollup-main.circom"
component main = RollupMain(8, 24, 8, 8);

"rollup-main.circom" is https://github.com/hermeznetwork/circuits/blob/master/src/rollup-main.circom
An err will occurr
     Running `/Users/zhangzhuo/repos/fluidex/plonkit/target/release/plonkit prove --srs_monomial_form '../keys/setup/setup_2^20.key' --circuit ./circuit-8-24-8-8.r1cs --witness witness-8-24-8-8.json --proof proof.bin -j proof.json -i public.json`
Loading circuit from ./circuit-8-24-8-8.r1cs...
thread 'main' panicked at 'internal error: entered unreachable code: R1CS has a gate 1 * 1 = 1', /Users/zhangzhuo/.cargo/git/checkouts/bellman-3ff25c59c43002dc/eb9c1db/src/plonk/better_cs/adaptor.rs:852:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I will fix this problem

This problem is due to that circom produced some trivial constraints like 0 * 0 == 0 and 0 * LC == 0.


Boolean APIs

@jsalinaspolo
Not sure if this has been raised before, but is there away to have the same APIs but return a boolean instead?
So instead of
logged(aLog().info().withMessage("a message"))

maybe something like
isLogged(aLog().info().withMessage("a message")) == true

The reason is that this will give more flexibility to work with other frameworks like kotest where I can have a precondition like
until(10.seconds) {
    isLogged(aLog().info().withMessage("a message"))
}

Do let me know if this is something we can have or not.
Thanks.

I never had to return Booleans as using Matchers have been easy to decouple from other frameworks.
It would not work with kotest the eventually like this test
  "use eventually to verify logs" {
    var i = 0
    eventually(1.seconds) {
      i += 1
      logMessageWhenCondition(log, i == 5)
      logCaptureListener.logged(aLog().info().withMessage("a message"))
    }
  }

https://github.com/jsalinaspolo/logcapture/blob/main/logcapture-kotest/src/test/kotlin/org/logcapture/kotest/LogCaptureListenerSpec.kt#L30

Closing the issue, feel free to open with comments if needed 🙇


⚠ Secret Website 3 has degraded performance

In 6ed4d3f, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3272 ms

Resolved: Secret Website 3 performance has improved in 30f51a2.


Module fails to load on Python 3.12

I get the following error trying to import mongomock-motor in Python 3.12. I have run python3.12 -m ensurepip --upgrade, which is a commonly suggested fix for this issue with pkgutil.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/tiltowait/Library/Caches/pypoetry/virtualenvs/botch-no4dKFGX-py3.12/lib/python3.12/site-packages/mongomock_motor/__init__.py", line 7, in <module>
    from mongomock import Collection as MongoMockCollection
  File "/Users/tiltowait/Library/Caches/pypoetry/virtualenvs/botch-no4dKFGX-py3.12/lib/python3.12/site-packages/mongomock/__init__.py", line 79, in <module>
    from mongomock.__version__ import __version__
  File "/Users/tiltowait/Library/Caches/pypoetry/virtualenvs/botch-no4dKFGX-py3.12/lib/python3.12/site-packages/mongomock/__version__.py", line 1, in <module>
    import pkg_resources
  File "/Users/tiltowait/Library/Caches/pypoetry/virtualenvs/botch-no4dKFGX-py3.12/lib/python3.12/site-packages/pkg_resources/__init__.py", line 2191, in <module>
    register_finder(pkgutil.ImpImporter, find_on_path)
                    ^^^^^^^^^^^^^^^^^^^
AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?

I'm using mongomock-motor 0.0.30, poetry 1.8.3, and Python 3.12.3.

Looks like an issue with mongomock that can be fixed in https://github.com/mongomock/mongomock/issues/889. While this version is unavailable, did you try to install setuptools? It seems to help:
$ python3 -V
Python 3.12.4
$ python3 -m venv .venv
$ source .vent/bin/activate
$ python3 -m pip install -r requirements.txt setuptools
...
$ make test
... 32 passed ...

@michaelkryukov that seems to work. Thanks!


Image streaming over websocket

depends on https://github.com/ignitionrobotics/ign-common/pull/139
🎉 New feature
Summary
Adds support for streaming images from an ign topic.
Added keyword image for requesting data from an image topic. The websocket server plugin will subscribe to the topic in the request and republish the image data over to the client.
A better solution maybe to use a proper streaming server like HTTP Live Streaming (HLS) protocol in the future.
Test it
Launch ign gazebo camera sensor example world:
ign gazebo -v 4 -r src/ign-gazebo/examples/worlds/camera_sensor.sdf

Launch ign websocket server example launch file
ign launch -v 4 src/ign-launch/examples/websocket.ign

See the image stream using this demo image_stream_websocket_client.html file

Note the red and blue channels are reversed in the image stream, which may be fixed by https://github.com/ignitionrobotics/ign-common/pull/162
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Would it be more efficient to base64 encode the image on the server side rather than on the client side? This could also be captured as a future improvement.


[request] mod support

hello, could you accept [item=tiberium-fuel-cell] from tiberium dawn has alternative to nuclear cell ?

how you want it to be an alternative? an option in settings? or a alternative recipe? or just replace the recipe? you know, there are other people who use this mod. so can you give me a reason why this is better? :)

do you have a way of adding something like ‘si tiberium mod detected’ alternative recipe enable.
in some scenarios there is only tiberium for example.

oh, its another mod's item, i thought that was on vanilla, then i can do it no doubt, just need add a if statement.

cool, thanks you

hi, would you mind tell me witch mod you use? I can see lots of mods have tiberium.

Tiberium Dawn

MD2R and MD are 2 mods for Tiberian Dawn

I see, the support have been added, but I have other features need to add, so will release a new version after


Issue when downloading snaps

When downloading some stories using "$snapchat->getFriendStories(true);" or with getStory(...), the file is not correctly downloaded, and thus not correctly decrypted. No errors are outputted by any function. This does not happen often with other user's stories, but for some reason, it happens with this specific user.
Here is the story_blob: https://mega.nz/#!9RQCGLgY!7EVAY2w7icKPtho6Q8uKF_0gdCrr9Z380VpZAP56FrE
Here is the file as obtained from php curl: https://mega.nz/#!BJoBCAaL!YqLTbCygVrwOA_5N_aQp8YqoEeuyKislN4ppMZz_8mg
Notice the 404 error shown in the curl file, but not returning an error when running 'get($endpoint)'. Downloading the blob from the browser works. At first I thought it was because curl was downloading from https://feelinsonice-hrd.appspot.com instead of https://app.snapchat.com, but that made no difference.
And here is the final file: https://mega.nz/#!cBIBGQDQ!179eJtospb7ANjSj2Ced6QUJ1Fs8Qll8GxwCIBLmD6k
Details on the specific story:
[197] => stdClass Object
    (
        [id] => cpslo_chat~1446102001077
        [username] => cpslo_chat
        [mature_content] =>
        [client_id] => CPSLO_CHAT~08354A9F-FE4E-4B5A-B0CB-6C8D3EFC7D0D
        [timestamp] =><PHONE_NUMBER>077
        [media_id] =><PHONE_NUMBER>372800
        [media_key] => SeUNPnmyWfqMXj+KhMaLLdQtfq1cGv/RqyGt7El0DLQ=
        [media_iv] => Xv9T0R6BiWUOzLha4aXbdA==
        [thumbnail_iv] => vOWNvFGoSFZGdXyteESRuw==
        [media_type] => 1
        [time] => 9.8750113378685
        [caption_text_display] => Send in your halloween snaps Ã°ÂŸÂŽÂƒ
        [zipped] => 1
        [story_filter_id] =>
        [time_left] => 72539622
        [is_shared] =>
        [media_url] => https://app.snapchat.com/bq/story_blob?story_id=6652167175372800&t=3&mt=1
        [thumbnail_url] => https://app.snapchat.com/bq/story_thumbnail?story_id=6652167175372800&t=3&mt=1
        [needs_auth] => 1
        [ad_can_follow] => 1
    )

Duplicate of #233

If you're getting a 404, the story no longer exists.

But it is still viewable on the Android app with over 12 hrs left
On Oct 29, 2015 6:05 AM, "Liam Cottle"<EMAIL_ADDRESS>wrote:

If you're getting a 404, the story no longer exists.
—
Reply to this email directly or view it on GitHub
https://github.com/mgp25/SC-API/issues/246#issuecomment-152174139.


middleware provideDocumentSymbols doesn't display children symbols

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.72.2
OS Version: Windows 11 / Ubuntu 22.04 LTS (I work on 2 machines)

Steps to Reproduce:

Follows the documentation here (request forwarding): https://code.visualstudio.com/api/language-extensions/embedded-languages
My repository: https://github.com/TechTheAwesome/code-yew-server

Issue https://github.com/TechTheAwesome/code-yew-server/issues/2
Expects symbols parsing by HTML Language Server to display correctly:

Got only top-level symbols:

Concerning piece of code
async provideDocumentSymbols(document, token, next) {
let result: undefined | DocumentSymbol[] = undefined;

result = await commands.executeCommand<DocumentSymbol[]>(
'vscode.executeDocumentSymbolProvider',
vdocUri(document),
);

return result;
}

What I've found
vscode.executeDocumentSymbolProvider returns a hierarchical array of symbols.
DocumentSymbol {
   children: DocumentSymbol[]
}

But provideDocumentSymbols() seems to expect (only displaying) flat arrays. Ignoring the children property.
   middleware: {
      async provideDocumentSymbols(document, token, next)  {
         //...
      },
      //...
   }

Detailed example
So if i pass into vscode.executeDocumentSymbolProvider a piece of HTML such as:

      </ul

vscode.executeDocumentSymbolProvider returns:
let result = [{
   name: "div",
   children: [{
      name: "ul",
      children: [{ name: "li", children: [] }]
}]

But vscode only display div symbol.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

That structure should be flat.

That structure should be flat.

Yes, which is why i was confused when HTML Language Service returned to me a tree. Is there a better way to solve this other than manually flattening the list?

The Goto Symbol in Editor command always shows a flat list even if the returned document symbols form a hierarchy. The Outline view (which calls the same API) shows a hierarchy if the document symbol provider provides a symbol hierarchy.
Does that explain it?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Visible property for toggle split area on and off, which changing structure of the view

The need arises due to the need of place router outlets inside split areas that need to be toggled on/off.
Since Router v3, router outlet inside a conditional area will not persist. This make routing on that outlet generating errors.
The purpose of this change is to simply hide the split area, not removing it, this way the router outlet will always be a there, and any other view children that need to persist will be always there too.

Nice,
Yes I understand the need, I will take time to test it and then, if everything's fine, merge it and add an example into website.
Do you try to mix 'conditionnal areas' and 'visibibity areas' and toggling them?

I didn't want take conditional areas out, fear that will break existing
implementations.
Visible areas just sit side by side with conditional areas
On Fri, Jan 20, 2017, 12:59 AM bertrandg<EMAIL_ADDRESS>wrote:

Nice,
Yes I understand the need, I will take time to test it and then, if
everything's fine, merge it and add an example into website.
Do you try to mix 'conditionnal areas' and 'visibibity areas' and toggling
them?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bertrandg/angular-split/pull/8#issuecomment-274015079,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APGpoZ9MklN-m4eiW2cYXiVyegqTtd-Eks5rUHd7gaJpZM4Lot6w
.

hi @jitsmaster
I've just played with your [visible] feature and it seems to works fine mixed with *ngIf:
https://plnkr.co/edit/GyQnxE?p=preview
What did you mean by: "I didn't want take conditional areas out, fear that will break existing implementations." ?
I've seen you add an other feature about animation and changed styles, can you keep it for an other pull request please.

Sorry for the confusion. Just meant I didn't touch the Ngif part at all and
make sure it still works.
I am waiting for you to approve the visibility feature first before I
create the pull request for animations.
I will create the pull request after this one is approved.
Thank you
Arnold
On Fri, Jan 27, 2017, 3:31 PM bertrandg<EMAIL_ADDRESS>wrote:

hi @jitsmaster https://github.com/jitsmaster
I've just played with your [visible] feature and it seems to works fine
mixed with *ngIf:
https://plnkr.co/edit/GyQnxE?p=preview
What did you mean by: "I didn't want take conditional areas out, fear that
will break existing implementations." ?
I've seen you add an other feature about animation and changed styles, can
you keep it for an other pull request please.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bertrandg/angular-split/pull/8#issuecomment-275802755,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APGpodBpFIh6mKP3cQKM9n1MUqbPzic2ks5rWn5hgaJpZM4Lot6w
.

Checking on how soon you can merge in my pull request. My app is getting pretty close to production state. Would really get the NPM package to be updated.
Also, I have created a new 'layoutEnd' event for split component. It is trigger after the animation ended for split area show/hide. Would love to pull this one into master too.

Yes I understand, I do that before the end of the week! :)

hi @jitsmaster
I'm finally on it! :flushed:
I would like to first merge your 3 commits from 19 January (only about toggling visibility) but there are 2 more about animation/layoutEnd in the pull request..
https://github.com/bertrandg/angular-split/pull/8/commits
Is it possible to lock your pull request to specific commit (e539e795e13438ed0723316a3f3e62c711868690) ?
About animation/layoutEnd, I haven't test it already but it seems to change a lot of things I need to test because I use it too on a prod app at work. (multi browser animation / multiple "soft removed" at same time)
And is there a specific reason to update dependencies to 2.4.3?

Let me create a branch just for the first 3 commits and send a new pull
request.
On Fri, Feb 3, 2017, 4:01 AM bertrandg<EMAIL_ADDRESS>wrote:

hi @jitsmaster https://github.com/jitsmaster
I'm finally on it! 😳
I would like to first merge your 3 commits from 19 January (only about
toggling visibility) but there are 2 more about animation/layoutEnd in the
pull request..
https://github.com/bertrandg/angular-split/pull/8/commits
Is it possible to lock your pull request to specific commit (e539e79
https://github.com/bertrandg/angular-split/commit/e539e795e13438ed0723316a3f3e62c711868690)
?
About animation/layoutEnd, I haven't test it already but it seems to
change a lot of things I need to test because I use it too on a prod app at
work. (multi browser animation / multiple "soft removed" at same time)
And is there a specific reason to update dependencies to 2.4.3?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bertrandg/angular-split/pull/8#issuecomment-277231365,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APGpoSh6kqebquoZGjYirCURdmubxnX1ks5rYxcIgaJpZM4Lot6w
.

Done. A new pull request is created, that includes only the visibility feature. Let me know if you want to reject this pull request and let me create another one after visiblity feature is merged.

simple visibility toggle feature (c7c92b9a1d1c00623660aeb7bc048509255e763b + e539e795e13438ed0723316a3f3e62c711868690)
I tested it more today and found a bug, check this plunker:
https://plnkr.co/edit/GyQnxE?p=preview
Click button "toggle visible C", areaC disapears but there's still a gutter on the right that shouldn't be there:

Should be solvable with this but need to be tested:

animation/layoutEnd feature (ee1400241073b5a753b91abd5c03707fff404168 + cee8d50af951136c835a662e59a93339a303d116)

Inside split.component.ts, I hade to import these 3 rxjs operator to make it works:

I found the way you emit your layoutEnd inside split.component.tsusing merge/debounceTime/... a bit "overengineered". I'm sure we can do it easily without subscribing an observable with many operators.
Why not inside splitArea.component.ts > function onSizingTransitionEnd() directly call this.split.notify('sizingEnd') only from areas you know visibility boolean just changed?

You used several times /deep/ inside styles, not sure if that's "future proof"..
It only works with ViewEncapsulation.Emulated:
https://angular.io/docs/ts/latest/guide/component-styles.html#!#special-selectors

I think the best way to merge it quickly is to first make a new pull-request with c7c92b9a1d1c00623660aeb7bc048509255e763b + e539e795e13438ed0723316a3f3e62c711868690 + bug fix.
And then an other.
And sorry for the time it took me to answer you with details.

Thank you for finding that bug. I will put in the fix in the other pull request.
Regarding the layoutEnd event firing, it was caused by transitionend event somehow fired multiple time on both chrome and firefox, so I had to debounceTime on it.
Also I had to merge all events together in case 2 or more areas are toggled in the same time, and their transitionend firing will not be in the same time.
I will test the css changes in shadow dom scenario

Cool, I wait for your commit on the other PR and will merge it quickly.
I will close this one.

That is weird you still have to import the specific operators. I haven't needing to do it for quite a while.
Angular 2.4.1 had a very strange bug of sometimes AOT build put ngfactory files in the source folder.
2.4.3 seems to fix the issue.

You are right that /deep/ indeed doesn't work on native view encapsulation. What is even worse if the flex direction will not be set with class.
I see you are directly setting the style of flex direction on hostbinding. Is it your recommended approach?

Actually, take that back. The only thing that wasn't working was the vertical direction. As soon as I use the same way of hostbinding seting flex direction. Everything works, including animation, in native mode.
I am creating a pull request now

Ok, yes Hostbinding() is a good way to achieve it.


[FEATURE] Remove event related data from the User or Student

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@SaintAngeLs Please, try to provide more descriptive features of what the integrity we are performing.


sniproxy: init at 0.4.0 with dependency udns: init at 0.4

Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Looks great to me, overall, having scanned the PR briefly.

Thanks for the review @joachifm. Everything seems to work as expected after all the changes.

Looks good to me. Thank you

Thanks!


Typo "Jupyter notebook"→"Jupyter Notebook"

https://docs.microsoft.com/en-us/azure/hdinsight/spark/apache-spark-microsoft-cognitive-toolkit

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Add Contribution guidelines

Hey Hi  Bibhuti9, you are doing great work this will be helpful for many job seekers.
Add Contribution guidelines:
Question you might get what should Add !
Answer to below question and make a contribution guidelines using this answers.

Who should contribute ?
Do you stick only with Javascript solution or will you accept other programming languages.
What are topics that are really important to crack the interview
Suggest some of the resource and website that will help to ace the interviews (include both paid and free). etc..

Thanks for your suggestion #1 ManoBharathi890 now I added all points


Feature request  # Feature Using Computer Vision to Detect Bad Posture

:red_circle: Title : Computer Vision to Detect Bad Posture
:red_circle: Aim : Implement a feature using computer vision techniques to detect bad posture in real-time using a webcam feed.
:red_circle: Brief Explanation : The feature will leverage machine learning models to analyze the user's posture through a webcam feed. It will provide real-time feedback and suggestions to correct posture, helping users avoid potential health issues associated with bad posture. The implementation will involve training a posture detection model, integrating it with the PyVerse project, and creating a user-friendly interface for real-time monitoring and feedback.
Screenshots 📷

can you pls add the level

closing via #171


[New game]: Pixel Smash

PR Description 📜
I Have Added Neon Pixel Smash game! Perfect for quick gaming sessions or long playthroughs, Pixel Smash keeps you hooked with its retro charm and modern twists.
Fixes #4884

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @vivekvardhan2810 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@ishita-43 please review my pull request

/assign

@kunjgit

@kunjgit Please merge it

@kunjgit solved the conflict please merge it

Thank you  @vivekvardhan2810 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Block library descriptions get cropped

Block library descriptions get cropped.
Here's a long description of the feedblock at feed.docx
But only the first few lines of this description are shown in the block library here

Thanks @dnbute . Indeed I see them now.


improvement(semantic/cfg): better control flow for DoWhileStatements.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3452  👈
#3451
#3381
#3407
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rzvxa and the rest of your teammates on  Graphite


chore: Removed comment feature codes

Description
Removed the codes related the comment feature
Fixes #20140
Type of change

Chore (housekeeping or task changes that don't impact user perception)

How Has This Been Tested?

Jest

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] 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
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=2beffbf

/ok-to-test sha=4d32c825ed3489c11feb5a2b10a2b01d90e1b141

/ok-to-test sha=97625a4caa37add8b5acf7476bd016590296d86b


I don't want to show all the categories.

hi
I have ".category_1" ".category_2" ".category_3"
I don't want all categories to be displayed at runtime, and I want the first category (.category_1) to be active.
  <button class="filter button" data-filter=".category_1">category 1</button>     <button class="filter button active" data-filter=".category_2">category 2</button>      <button class="filter button" data-filter=".category_3">category 3</button>
But during the first run, all categories are displayed.

On mixitup.js
load: {
filter: '.coaching',//put your own class with dot
},


Add dataTypeCase & functionCase

Continuation of PR #673

I'm still not sure how to best handle the ARRAY keyword/type.
In many dialects array literals are written as ARRAY[1, 2, 3] - here ARRAY is not a type, it's part of the literal syntax.
In BigQuery one can write just [1, 2, 3], but also ARRAY[1, 2, 3] and ARRAY<INT64>[1, 2, 3] - here ARRAY is a type.
At the moment in this PR the ARRAY[] is formatted as keyword, but ARRAY<INT64>[] as data type. Which isn't ideal.
Will need to do more research into how the ARRAY keyword is used in other dialects.


Disclose login page for not authenticated users

Describe the bug
Although the login page is publicly accessible, after the authorization with Keycloak and the redirect to the client, the authentication errors may occur (e.g. token not valid). In this case, the user remains logged in to Keycloak, but cannot use the client. Moreover, logging in again or logging out is no longer possible.
To Reproduce
Steps to reproduce the behavior:

Open client
Bring some service down (UM or Kong)
Login through Keycloak
After redirect to client error is shown, authentication not possible
Client not usable

Expected behavior
We should at least provide the option to navigate to login page for another try or to log out
Additional context
Most likely, the error will occur only in case of DIVA misconfiguration. In this case, nothing helps except contacting the administrator. Nevertheless, let's get rid of this limitation

Error would also occur on network errors. Should make it clean here.


AUTH-5403 added access custom pages as a new resource

corresponding cf-go PR - https://github.com/cloudflare/cloudflare-go/pull/1343

we will need to update this a little bit since the upstream PR changed the method signatures slightly.

acceptance tests all looking good
TEST="./internal/sdkv2provider" TESTARGS='-run "^TestAccCloudflareAccess(Application|CustomPage|Organization)_" -count 1' make testacc
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareAccess(Application|CustomPage|Organization)_" -count 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflareAccessApplication_BasicZone
--- PASS: TestAccCloudflareAccessApplication_BasicZone (14.90s)
=== RUN   TestAccCloudflareAccessApplication_BasicAccount
--- PASS: TestAccCloudflareAccessApplication_BasicAccount (16.59s)
=== RUN   TestAccCloudflareAccessApplication_WithCORS
--- PASS: TestAccCloudflareAccessApplication_WithCORS (18.88s)
=== RUN   TestAccCloudflareAccessApplication_WithSaas
--- PASS: TestAccCloudflareAccessApplication_WithSaas (18.40s)
=== RUN   TestAccCloudflareAccessApplication_WithAutoRedirectToIdentity
--- PASS: TestAccCloudflareAccessApplication_WithAutoRedirectToIdentity (16.05s)
=== RUN   TestAccCloudflareAccessApplication_WithEnableBindingCookie
--- PASS: TestAccCloudflareAccessApplication_WithEnableBindingCookie (15.25s)
=== RUN   TestAccCloudflareAccessApplication_WithCustomDenyFields
--- PASS: TestAccCloudflareAccessApplication_WithCustomDenyFields (15.80s)
=== RUN   TestAccCloudflareAccessApplication_WithADefinedIdps
--- PASS: TestAccCloudflareAccessApplication_WithADefinedIdps (16.60s)
=== RUN   TestAccCloudflareAccessApplication_WithMultipleIdpsReordered
--- PASS: TestAccCloudflareAccessApplication_WithMultipleIdpsReordered (31.05s)
=== RUN   TestAccCloudflareAccessApplication_WithHttpOnlyCookieAttribute
--- PASS: TestAccCloudflareAccessApplication_WithHttpOnlyCookieAttribute (14.85s)
=== RUN   TestAccCloudflareAccessApplication_WithHTTPOnlyCookieAttributeSetToFalse
--- PASS: TestAccCloudflareAccessApplication_WithHTTPOnlyCookieAttributeSetToFalse (14.45s)
=== RUN   TestAccCloudflareAccessApplication_WithSameSiteCookieAttribute
--- PASS: TestAccCloudflareAccessApplication_WithSameSiteCookieAttribute (14.80s)
=== RUN   TestAccCloudflareAccessApplication_WithLogoURL
--- PASS: TestAccCloudflareAccessApplication_WithLogoURL (17.75s)
=== RUN   TestAccCloudflareAccessApplication_WithSkipInterstitial
--- PASS: TestAccCloudflareAccessApplication_WithSkipInterstitial (14.19s)
=== RUN   TestAccCloudflareAccessApplication_WithAppLauncherVisible
--- PASS: TestAccCloudflareAccessApplication_WithAppLauncherVisible (19.35s)
=== RUN   TestAccCloudflareAccessApplication_WithSelfHostedDomains
--- PASS: TestAccCloudflareAccessApplication_WithSelfHostedDomains (16.26s)
=== RUN   TestAccCloudflareAccessCustomPage_IdentityDenied
--- PASS: TestAccCloudflareAccessCustomPage_IdentityDenied (17.05s)
=== RUN   TestAccCloudflareAccessCustomPage_Forbidden
--- PASS: TestAccCloudflareAccessCustomPage_Forbidden (16.94s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	310.138s


test_read_request_tracing is flaky

A recent failure in main: https://github.com/neondatabase/neon/actions/runs/3578774624/jobs/6019408139
main seems failing:passing about 50:50 at the moment, each failure is unique in its flakiness.
__________________________ test_read_request_tracing ___________________________
test_runner/performance/test_read_trace.py:31: in test_read_request_tracing
    assert trace_path.exists()
E   AssertionError: assert False
E    +  where False = <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/6f601be5c98fe141d31f86d632a6f4e9/06f46d611991a8acce8aa3ec235f2f5e')>()
E    +    where <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/6f601be5c98fe141d31f86d632a6f4e9/06f46d611991a8acce8aa3ec235f2f5e')> = PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/6f601be5c98fe141d31f86d632a6f4e9/06f46d611991a8acce8aa3ec235f2f5e').exists
------------------------------ Captured log setup ------------------------------
2022-11-29 23:41:09.58  INFO [neon_fixtures.py:2715] get_test_output_dir is /tmp/test_output/test_read_request_tracing
2022-11-29 23:41:09.58  INFO [neon_fixtures.py:2736] test_output_dir is /tmp/test_output/test_read_request_tracing
------------------------------ Captured log call -------------------------------
2022-11-29 23:41:09.64  INFO [neon_fixtures.py:910] Config:
default_tenant_id = '930b0a16c07d6dcbebaf41aef2b4c18e'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001/']
etcd_binary_path = '/usr/local/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:15211'
listen_http_addr = 'localhost:15212'
auth_type = 'Trust'

[[safekeepers]]
id = 1
pg_port = 15213
http_port = 15214
sync = false
2022-11-29 23:41:09.65  INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local init --config=/tmp/tmp_3fu7hau --pg-version 14"
2022-11-29 23:41:09.65  INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:09.826 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12770
Successfully initialized timeline 47251593d2df1663fddbb0baa620e38b
Stopped pageserver 1 process with pid 12770

2022-11-29 23:41:09.826 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver start"
2022-11-29 23:41:09.826 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:09.933 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12821

2022-11-29 23:41:09.934 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper start 1"
2022-11-29 23:41:09.934 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:10.40  INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15213' in '/tmp/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 12858

2022-11-29 23:41:10.43  INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local tenant create --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --timeline-id 442541c90a6d43599e26f34a318c4851 --pg-version 14 -c trace_read_requests:true"
2022-11-29 23:41:10.43  INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:10.603 INFO [neon_fixtures.py:1347] Run success: tenant 6f601be5c98fe141d31f86d632a6f4e9 successfully created on the pageserver
Created an initial timeline '442541c90a6d43599e26f34a318c4851' at Lsn 0/16960E8 for tenant: 6f601be5c98fe141d31f86d632a6f4e9

2022-11-29 23:41:10.603 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local timeline create --branch-name test_trace_replay --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --pg-version 14"
2022-11-29 23:41:10.604 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:11.167 INFO [neon_fixtures.py:1347] Run success: Created timeline '06f46d611991a8acce8aa3ec235f2f5e' at Lsn 0/16960E8 for tenant: 6f601be5c98fe141d31f86d632a6f4e9

2022-11-29 23:41:11.167 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg create --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --branch-name test_trace_replay --pg-version 14 --port 15215 main"
2022-11-29 23:41:11.167 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:11.172 INFO [neon_fixtures.py:1347] Run success:
2022-11-29 23:41:11.173 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-11-29 23:41:11.173 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg start --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --pg-version 14 --port=15215 main"
2022-11-29 23:41:11.173 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:11.308 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/tmp/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/6f601be5c98fe141d31f86d632a6f4e9/main port=15215
Starting postgres node at 'host=<IP_ADDRESS> port=15215 user=cloud_admin dbname=postgres'

2022-11-29 23:41:11.309 INFO [neon_fixtures.py:2377] Postgres startup took 0.14138293266296387 seconds
2022-11-29 23:41:11.953 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg stop --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 main"
2022-11-29 23:41:11.953 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:12.60  INFO [neon_fixtures.py:1347] Run success:
---------------------------- Captured log teardown -----------------------------
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper stop 1 -m immediate"
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 12858 immediately...
safekeeper 1 stopped

2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver stop -m immediate"
2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:12.339 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 12821 immediately...
pageserver stopped

2022-11-29 23:41:12.339 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup

Another one: https://github.com/neondatabase/neon/actions/runs/3576711906/jobs/6015134761
__________________________ test_read_request_tracing ___________________________
test_runner/performance/test_read_trace.py:31: in test_read_request_tracing
    assert trace_path.exists()
E   AssertionError: assert False
E    +  where False = <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/4ec607dc470ec1898082846cc2ad64e1/3d36ef1109fef4c361d7bb192e90d208')>()
E    +    where <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/4ec607dc470ec1898082846cc2ad64e1/3d36ef1109fef4c361d7bb192e90d208')> = PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/4ec607dc470ec1898082846cc2ad64e1/3d36ef1109fef4c361d7bb192e90d208').exists
------------------------------ Captured log setup ------------------------------
2022-11-29 18:33:20.220 INFO [neon_fixtures.py:2715] get_test_output_dir is /tmp/test_output/test_read_request_tracing
2022-11-29 18:33:20.220 INFO [neon_fixtures.py:2736] test_output_dir is /tmp/test_output/test_read_request_tracing
------------------------------ Captured log call -------------------------------
2022-11-29 18:33:20.226 INFO [neon_fixtures.py:910] Config:
default_tenant_id = 'a02fbc35183e1753fb35e81a23001414'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001/']
etcd_binary_path = '/usr/local/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:15211'
listen_http_addr = 'localhost:15212'
auth_type = 'Trust'

[[safekeepers]]
id = 1
pg_port = 15213
http_port = 15214
sync = false
2022-11-29 18:33:20.226 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local init --config=/tmp/tmp3zcrhliv --pg-version 14"
2022-11-29 18:33:20.226 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:20.999 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12732
Successfully initialized timeline a0d40fa11ba538bcd586fcf5727e4a2a
Stopped pageserver 1 process with pid 12732

2022-11-29 18:33:21.0   INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver start"
2022-11-29 18:33:21.0   INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:21.107 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12783

2022-11-29 18:33:21.107 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper start 1"
2022-11-29 18:33:21.108 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:21.214 INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15213' in '/tmp/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 12820

2022-11-29 18:33:21.216 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local tenant create --tenant-id 4ec607dc470ec1898082846cc2ad64e1 --timeline-id b89387a0568b0d64bffc697e96b1e951 --pg-version 14 -c trace_read_requests:true"
2022-11-29 18:33:21.217 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:21.783 INFO [neon_fixtures.py:1347] Run success: tenant 4ec607dc470ec1898082846cc2ad64e1 successfully created on the pageserver
Created an initial timeline 'b89387a0568b0d64bffc697e96b1e951' at Lsn 0/16960E8 for tenant: 4ec607dc470ec1898082846cc2ad64e1

2022-11-29 18:33:21.784 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local timeline create --branch-name test_trace_replay --tenant-id 4ec607dc470ec1898082846cc2ad64e1 --pg-version 14"
2022-11-29 18:33:21.784 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:22.346 INFO [neon_fixtures.py:1347] Run success: Created timeline '3d36ef1109fef4c361d7bb192e90d208' at Lsn 0/16960E8 for tenant: 4ec607dc470ec1898082846cc2ad64e1

2022-11-29 18:33:22.347 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg create --tenant-id 4ec607dc470ec1898082846cc2ad64e1 --branch-name test_trace_replay --pg-version 14 --port 15215 main"
2022-11-29 18:33:22.347 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:22.352 INFO [neon_fixtures.py:1347] Run success:
2022-11-29 18:33:22.352 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-11-29 18:33:22.352 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg start --tenant-id 4ec607dc470ec1898082846cc2ad64e1 --pg-version 14 --port=15215 main"
2022-11-29 18:33:22.353 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:22.488 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/tmp/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/4ec607dc470ec1898082846cc2ad64e1/main port=15215
Starting postgres node at 'host=<IP_ADDRESS> port=15215 user=cloud_admin dbname=postgres'

2022-11-29 18:33:22.489 INFO [neon_fixtures.py:2377] Postgres startup took 0.14180541038513184 seconds
2022-11-29 18:33:23.127 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg stop --tenant-id 4ec607dc470ec1898082846cc2ad64e1 main"
2022-11-29 18:33:23.128 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:23.236 INFO [neon_fixtures.py:1347] Run success:
---------------------------- Captured log teardown -----------------------------
2022-11-29 18:33:23.317 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-11-29 18:33:23.318 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-11-29 18:33:23.318 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper stop 1 -m immediate"
2022-11-29 18:33:23.318 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:23.424 INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 12820 immediately...
safekeeper 1 stopped

2022-11-29 18:33:23.425 INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-11-29 18:33:23.425 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver stop -m immediate"
2022-11-29 18:33:23.425 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 18:33:23.530 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 12783 immediately...
pageserver stopped

2022-11-29 18:33:23.530 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup

And another: https://github.com/neondatabase/neon/actions/runs/3578774624/jobs/6019408139
__________________________ test_read_request_tracing ___________________________
test_runner/performance/test_read_trace.py:31: in test_read_request_tracing
    assert trace_path.exists()
E   AssertionError: assert False
E    +  where False = <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/6f601be5c98fe141d31f86d632a6f4e9/06f46d611991a8acce8aa3ec235f2f5e')>()
E    +    where <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/6f601be5c98fe141d31f86d632a6f4e9/06f46d611991a8acce8aa3ec235f2f5e')> = PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/6f601be5c98fe141d31f86d632a6f4e9/06f46d611991a8acce8aa3ec235f2f5e').exists
------------------------------ Captured log setup ------------------------------
2022-11-29 23:41:09.58  INFO [neon_fixtures.py:2715] get_test_output_dir is /tmp/test_output/test_read_request_tracing
2022-11-29 23:41:09.58  INFO [neon_fixtures.py:2736] test_output_dir is /tmp/test_output/test_read_request_tracing
------------------------------ Captured log call -------------------------------
2022-11-29 23:41:09.64  INFO [neon_fixtures.py:910] Config:
default_tenant_id = '930b0a16c07d6dcbebaf41aef2b4c18e'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001/']
etcd_binary_path = '/usr/local/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:15211'
listen_http_addr = 'localhost:15212'
auth_type = 'Trust'

[[safekeepers]]
id = 1
pg_port = 15213
http_port = 15214
sync = false
2022-11-29 23:41:09.65  INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local init --config=/tmp/tmp_3fu7hau --pg-version 14"
2022-11-29 23:41:09.65  INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:09.826 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12770
Successfully initialized timeline 47251593d2df1663fddbb0baa620e38b
Stopped pageserver 1 process with pid 12770

2022-11-29 23:41:09.826 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver start"
2022-11-29 23:41:09.826 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:09.933 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12821

2022-11-29 23:41:09.934 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper start 1"
2022-11-29 23:41:09.934 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:10.40  INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15213' in '/tmp/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 12858

2022-11-29 23:41:10.43  INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local tenant create --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --timeline-id 442541c90a6d43599e26f34a318c4851 --pg-version 14 -c trace_read_requests:true"
2022-11-29 23:41:10.43  INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:10.603 INFO [neon_fixtures.py:1347] Run success: tenant 6f601be5c98fe141d31f86d632a6f4e9 successfully created on the pageserver
Created an initial timeline '442541c90a6d43599e26f34a318c4851' at Lsn 0/16960E8 for tenant: 6f601be5c98fe141d31f86d632a6f4e9

2022-11-29 23:41:10.603 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local timeline create --branch-name test_trace_replay --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --pg-version 14"
2022-11-29 23:41:10.604 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:11.167 INFO [neon_fixtures.py:1347] Run success: Created timeline '06f46d611991a8acce8aa3ec235f2f5e' at Lsn 0/16960E8 for tenant: 6f601be5c98fe141d31f86d632a6f4e9

2022-11-29 23:41:11.167 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg create --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --branch-name test_trace_replay --pg-version 14 --port 15215 main"
2022-11-29 23:41:11.167 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:11.172 INFO [neon_fixtures.py:1347] Run success:
2022-11-29 23:41:11.173 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-11-29 23:41:11.173 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg start --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 --pg-version 14 --port=15215 main"
2022-11-29 23:41:11.173 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:11.308 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/tmp/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/6f601be5c98fe141d31f86d632a6f4e9/main port=15215
Starting postgres node at 'host=<IP_ADDRESS> port=15215 user=cloud_admin dbname=postgres'

2022-11-29 23:41:11.309 INFO [neon_fixtures.py:2377] Postgres startup took 0.14138293266296387 seconds
2022-11-29 23:41:11.953 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg stop --tenant-id 6f601be5c98fe141d31f86d632a6f4e9 main"
2022-11-29 23:41:11.953 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:12.60  INFO [neon_fixtures.py:1347] Run success:
---------------------------- Captured log teardown -----------------------------
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper stop 1 -m immediate"
2022-11-29 23:41:12.127 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 12858 immediately...
safekeeper 1 stopped

2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver stop -m immediate"
2022-11-29 23:41:12.233 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-29 23:41:12.339 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 12821 immediately...
pageserver stopped

2022-11-29 23:41:12.339 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup

And another: https://github.com/neondatabase/neon/actions/runs/3581935241
__________________________ test_read_request_tracing ___________________________
test_runner/performance/test_read_trace.py:31: in test_read_request_tracing
    assert trace_path.exists()
E   AssertionError: assert False
E    +  where False = <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/d6f95370eefa0b810163fe8bfcbb5c11/d2ea7abaae00f2abfb2ef480105595e4')>()
E    +    where <bound method Path.exists of PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/d6f95370eefa0b810163fe8bfcbb5c11/d2ea7abaae00f2abfb2ef480105595e4')> = PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/d6f95370eefa0b810163fe8bfcbb5c11/d2ea7abaae00f2abfb2ef480105595e4').exists
------------------------------ Captured log setup ------------------------------
2022-11-30 10:09:01.559 INFO [neon_fixtures.py:2715] get_test_output_dir is /tmp/test_output/test_read_request_tracing
2022-11-30 10:09:01.560 INFO [neon_fixtures.py:2736] test_output_dir is /tmp/test_output/test_read_request_tracing
------------------------------ Captured log call -------------------------------
2022-11-30 10:09:01.565 INFO [neon_fixtures.py:910] Config:
default_tenant_id = '6fe5d9eb01f0e2e704c727e9caaceff5'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001/']
etcd_binary_path = '/usr/local/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:15211'
listen_http_addr = 'localhost:15212'
auth_type = 'Trust'

[[safekeepers]]
id = 1
pg_port = 15213
http_port = 15214
sync = false
2022-11-30 10:09:01.566 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local init --config=/tmp/tmpoaxgtxt_ --pg-version 14"
2022-11-30 10:09:01.566 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:02.404 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12714
Successfully initialized timeline 6932f747e158e2434ea0a1a3fa83b536
Stopped pageserver 1 process with pid 12714

2022-11-30 10:09:02.405 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver start"
2022-11-30 10:09:02.405 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:02.511 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12765

2022-11-30 10:09:02.511 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper start 1"
2022-11-30 10:09:02.511 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:02.617 INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15213' in '/tmp/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 12802

2022-11-30 10:09:02.620 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local tenant create --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --timeline-id 241baad01ad42c836df94b7a5542fedb --pg-version 14 -c trace_read_requests:true"
2022-11-30 10:09:02.620 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.204 INFO [neon_fixtures.py:1347] Run success: tenant d6f95370eefa0b810163fe8bfcbb5c11 successfully created on the pageserver
Created an initial timeline '241baad01ad42c836df94b7a5542fedb' at Lsn 0/16960E8 for tenant: d6f95370eefa0b810163fe8bfcbb5c11

2022-11-30 10:09:03.205 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local timeline create --branch-name test_trace_replay --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --pg-version 14"
2022-11-30 10:09:03.205 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.767 INFO [neon_fixtures.py:1347] Run success: Created timeline 'd2ea7abaae00f2abfb2ef480105595e4' at Lsn 0/16960E8 for tenant: d6f95370eefa0b810163fe8bfcbb5c11

2022-11-30 10:09:03.768 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg create --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --branch-name test_trace_replay --pg-version 14 --port 15215 main"
2022-11-30 10:09:03.768 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:1347] Run success:
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg start --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --pg-version 14 --port=15215 main"
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.913 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/tmp/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/d6f95370eefa0b810163fe8bfcbb5c11/main port=15215
Starting postgres node at 'host=<IP_ADDRESS> port=15215 user=cloud_admin dbname=postgres'

2022-11-30 10:09:03.914 INFO [neon_fixtures.py:2377] Postgres startup took 0.1457674503326416 seconds
2022-11-30 10:09:04.529 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg stop --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 main"
2022-11-30 10:09:04.529 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:04.636 INFO [neon_fixtures.py:1347] Run success:
---------------------------- Captured log teardown -----------------------------
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper stop 1 -m immediate"
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:04.810 INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 12802 immediately...
safekeeper 1 stopped

2022-11-30 10:09:04.810 INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-11-30 10:09:04.811 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver stop -m immediate"
2022-11-30 10:09:04.811 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:04.916 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 12765 immediately...
pageserver stopped

2022-11-30 10:09:04.916 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup

And another: https://github.com/neondatabase/neon/actions/runs/3581935241/jobs/6026019140

Logs
```
__________________________ test_read_request_tracing ___________________________
test_runner/performance/test_read_trace.py:31: in test_read_request_tracing
    assert trace_path.exists()
E   AssertionError: assert False
E    +  where False = ()
E    +    where  = PosixPath('/tmp/test_output/test_read_request_tracing/repo/traces/d6f95370eefa0b810163fe8bfcbb5c11/d2ea7abaae00f2abfb2ef480105595e4').exists
------------------------------ Captured log setup ------------------------------
2022-11-30 10:09:01.559 INFO [neon_fixtures.py:2715] get_test_output_dir is /tmp/test_output/test_read_request_tracing
2022-11-30 10:09:01.560 INFO [neon_fixtures.py:2736] test_output_dir is /tmp/test_output/test_read_request_tracing
------------------------------ Captured log call -------------------------------
2022-11-30 10:09:01.565 INFO [neon_fixtures.py:910] Config:
default_tenant_id = '6fe5d9eb01f0e2e704c727e9caaceff5'
[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001/']
etcd_binary_path = '/usr/local/bin/etcd'
[pageserver]
id=1
listen_pg_addr = 'localhost:15211'
listen_http_addr = 'localhost:15212'
auth_type = 'Trust'
[[safekeepers]]
id = 1
pg_port = 15213
http_port = 15214
sync = false
2022-11-30 10:09:01.566 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local init --config=/tmp/tmpoaxgtxt_ --pg-version 14"
2022-11-30 10:09:01.566 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:02.404 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12714
Successfully initialized timeline 6932f747e158e2434ea0a1a3fa83b536
Stopped pageserver 1 process with pid 12714
2022-11-30 10:09:02.405 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver start"
2022-11-30 10:09:02.405 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:02.511 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15211' in '/tmp/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 12765
2022-11-30 10:09:02.511 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper start 1"
2022-11-30 10:09:02.511 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:02.617 INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15213' in '/tmp/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 12802
2022-11-30 10:09:02.620 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local tenant create --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --timeline-id 241baad01ad42c836df94b7a5542fedb --pg-version 14 -c trace_read_requests:true"
2022-11-30 10:09:02.620 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.204 INFO [neon_fixtures.py:1347] Run success: tenant d6f95370eefa0b810163fe8bfcbb5c11 successfully created on the pageserver
Created an initial timeline '241baad01ad42c836df94b7a5542fedb' at Lsn 0/16960E8 for tenant: d6f95370eefa0b810163fe8bfcbb5c11
2022-11-30 10:09:03.205 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local timeline create --branch-name test_trace_replay --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --pg-version 14"
2022-11-30 10:09:03.205 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.767 INFO [neon_fixtures.py:1347] Run success: Created timeline 'd2ea7abaae00f2abfb2ef480105595e4' at Lsn 0/16960E8 for tenant: d6f95370eefa0b810163fe8bfcbb5c11
2022-11-30 10:09:03.768 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg create --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --branch-name test_trace_replay --pg-version 14 --port 15215 main"
2022-11-30 10:09:03.768 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:1347] Run success:
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg start --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 --pg-version 14 --port=15215 main"
2022-11-30 10:09:03.773 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:03.913 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/tmp/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/d6f95370eefa0b810163fe8bfcbb5c11/main port=15215
Starting postgres node at 'host=<IP_ADDRESS> port=15215 user=cloud_admin dbname=postgres'
2022-11-30 10:09:03.914 INFO [neon_fixtures.py:2377] Postgres startup took 0.1457674503326416 seconds
2022-11-30 10:09:04.529 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pg stop --tenant-id d6f95370eefa0b810163fe8bfcbb5c11 main"
2022-11-30 10:09:04.529 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:04.636 INFO [neon_fixtures.py:1347] Run success:
---------------------------- Captured log teardown -----------------------------
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local safekeeper stop 1 -m immediate"
2022-11-30 10:09:04.704 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:04.810 INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 12802 immediately...
safekeeper 1 stopped
2022-11-30 10:09:04.810 INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-11-30 10:09:04.811 INFO [neon_fixtures.py:1319] Running command "/tmp/neon/bin/neon_local pageserver stop -m immediate"
2022-11-30 10:09:04.811 INFO [neon_fixtures.py:1320] Running in "/tmp/test_output/test_read_request_tracing/repo"
2022-11-30 10:09:04.916 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 12765 immediately...
pageserver stopped
2022-11-30 10:09:04.916 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup
</details>

@hlinnaka @LizardWizzard @problame Are you sure this is not caused by https://github.com/neondatabase/neon/commit/9a6c0be823fb1b11f7d0ab6bb5a98605387c08d5 ? This benchmark fails consistently since this commit. It fails on my machine as well:

Full local `pytest` logs
The currently activated Python version 3.8.10 is not supported by the project (^3.9).
Trying to find and use a compatible version.
Using python3.9 (3.9.15)
============================= test session starts ==============================
platform linux -- Python 3.9.15, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
rootdir: /home/yeputons/neon/neon, configfile: pytest.ini
plugins: xdist-3.0.2, timeout-2.1.0, allure-pytest-2.10.0, asyncio-0.19.0, order-1.0.1, lazy-fixture-0.6.3
timeout: 300.0s
timeout method: signal
timeout func_only: False
asyncio: mode=strict

----------------------------- live log collection ------------------------------
2022-12-01 02:52:09.345 INFO [neon_fixtures.py:507] Using mock implementations to test remote storage
2022-12-01 02:52:09.349 INFO [neon_fixtures.py:507] Using mock implementations to test remote storage
2022-12-01 02:52:09.353 INFO [neon_fixtures.py:507] Using mock implementations to test remote storage
2022-12-01 02:52:09.355 INFO [neon_fixtures.py:507] Using mock implementations to test remote storage
2022-12-01 02:52:09.363 INFO [neon_fixtures.py:507] Using mock implementations to test remote storage
2022-12-01 02:52:09.363 INFO [neon_fixtures.py:507] Using mock implementations to test remote storage
collected 270 items / 269 deselected / 1 selected

performance/test_read_trace.py::test_read_request_tracing
-------------------------------- live log setup --------------------------------
2022-12-01 02:52:09.378 INFO [neon_fixtures.py:87] base_dir is /home/yeputons/neon/neon
2022-12-01 02:52:09.378 INFO [neon_fixtures.py:133] top_output_dir is /home/yeputons/neon/neon/test_output
2022-12-01 02:52:09.380 INFO [neon_fixtures.py:105] neon_binpath is /home/yeputons/neon/neon/target/debug
2022-12-01 02:52:09.381 INFO [neon_fixtures.py:120] pg_distrib_dir is /home/yeputons/neon/neon/pg_install
2022-12-01 02:52:09.381 INFO [neon_fixtures.py:144] pg_version is 14
2022-12-01 02:52:09.381 INFO [neon_fixtures.py:2715] get_test_output_dir is /home/yeputons/neon/neon/test_output/neon
2022-12-01 02:52:09.382 INFO [neon_fixtures.py:2715] get_test_output_dir is /home/yeputons/neon/neon/test_output/test_read_request_tracing
2022-12-01 02:52:09.382 INFO [neon_fixtures.py:2736] test_output_dir is /home/yeputons/neon/neon/test_output/test_read_request_tracing
-------------------------------- live log call ---------------------------------
2022-12-01 02:52:09.391 INFO [neon_fixtures.py:225] Port 15005 is in use, skipping
2022-12-01 02:52:09.392 INFO [neon_fixtures.py:910] Config:
default_tenant_id = '9e56ec99da720db1eeb510be6f7dbe05'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001']
etcd_binary_path = '/usr/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:15003'
listen_http_addr = 'localhost:15004'
auth_type = 'Trust'

[[safekeepers]]
id = 1
pg_port = 15006
http_port = 15007
sync = false
2022-12-01 02:52:09.392 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local init --config=/tmp/tmpp5iijccl --pg-version 14"
2022-12-01 02:52:09.392 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:10.479 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15003' in '/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 14539
Successfully initialized timeline c7d07f553659a7b7afc7bed1b4fbc1a5
Stopped pageserver 1 process with pid 14539

2022-12-01 02:52:10.480 INFO [neon_fixtures.py:2677] Starting etcd to listen incoming connections at "http://<IP_ADDRESS>:15001"
2022-12-01 02:52:11.696 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pageserver start"
2022-12-01 02:52:11.697 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:11.801 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15003' in '/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 14696

2022-12-01 02:52:11.802 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local safekeeper start 1"
2022-12-01 02:52:11.802 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:11.906 INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15006' in '/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 14825

2022-12-01 02:52:11.908 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local tenant create --tenant-id c0325f822fe3de578c6df2d0ef815414 --timeline-id 60103f9ac66c0df8d8574864167ce027 --pg-version 14 -c trace_read_requests:true"
2022-12-01 02:52:11.908 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:13.3   INFO [neon_fixtures.py:1347] Run success: tenant c0325f822fe3de578c6df2d0ef815414 successfully created on the pageserver
Created an initial timeline '60103f9ac66c0df8d8574864167ce027' at Lsn 0/1696628 for tenant: c0325f822fe3de578c6df2d0ef815414

2022-12-01 02:52:13.3   INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local timeline create --branch-name test_trace_replay --tenant-id c0325f822fe3de578c6df2d0ef815414 --pg-version 14"
2022-12-01 02:52:13.4   INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.148 INFO [neon_fixtures.py:1347] Run success: Created timeline '87066ec498b65f574f706e32bc727134' at Lsn 0/1696628 for tenant: c0325f822fe3de578c6df2d0ef815414

2022-12-01 02:52:14.148 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pg create --tenant-id c0325f822fe3de578c6df2d0ef815414 --branch-name test_trace_replay --pg-version 14 --port 15008 main"
2022-12-01 02:52:14.149 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:1347] Run success:
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pg start --tenant-id c0325f822fe3de578c6df2d0ef815414 --pg-version 14 --port=15008 main"
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.278 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/c0325f822fe3de578c6df2d0ef815414/main port=15008
Starting postgres node at 'host=<IP_ADDRESS> port=15008 user=cloud_admin dbname=postgres'

2022-12-01 02:52:14.278 INFO [neon_fixtures.py:2377] Postgres startup took 0.12995028495788574 seconds
2022-12-01 02:52:14.829 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pg stop --tenant-id c0325f822fe3de578c6df2d0ef815414 main"
2022-12-01 02:52:14.830 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.936 INFO [neon_fixtures.py:1347] Run success:
FAILED                                                                   [100%]
------------------------------ live log teardown -------------------------------
2022-12-01 02:52:14.959 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-12-01 02:52:14.959 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-12-01 02:52:14.959 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local safekeeper stop 1 -m immediate"
2022-12-01 02:52:14.960 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:15.64  INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 14825 immediately...
safekeeper 1 stopped

2022-12-01 02:52:15.64  INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-12-01 02:52:15.65  INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pageserver stop -m immediate"
2022-12-01 02:52:15.65  INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:15.170 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 14696 immediately...
pageserver stopped

2022-12-01 02:52:15.171 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup

=================================== FAILURES ===================================
__________________________ test_read_request_tracing ___________________________

neon_env_builder = <fixtures.neon_fixtures.NeonEnvBuilder object at 0x7f102c1ca1c0>

    def test_read_request_tracing(neon_env_builder: NeonEnvBuilder):
        neon_env_builder.num_safekeepers = 1
        env = neon_env_builder.init_start()

        tenant, _ = env.neon_cli.create_tenant(
            conf={
                "trace_read_requests": "true",
            }
        )

        timeline = env.neon_cli.create_timeline("test_trace_replay", tenant_id=tenant)
        pg = env.postgres.create_start("test_trace_replay", "main", tenant)

        with closing(pg.connect()) as conn:
            with conn.cursor() as cur:
                cur.execute("create table t (i integer);")
                cur.execute(f"insert into t values (generate_series(1,{10000}));")
                cur.execute("select count(*) from t;")

        # Stop pg so we drop the connection and flush the traces
        pg.stop()

        trace_path = env.repo_dir / "traces" / str(tenant) / str(timeline)
>       assert trace_path.exists()
E       AssertionError: assert False
E        +  where False = <bound method Path.exists of PosixPath('/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/traces/c0325f822fe3de578c6df2d0ef815414/87066ec498b65f574f706e32bc727134')>()
E        +    where <bound method Path.exists of PosixPath('/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/traces/c0325f822fe3de578c6df2d0ef815414/87066ec498b65f574f706e32bc727134')> = PosixPath('/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/traces/c0325f822fe3de578c6df2d0ef815414/87066ec498b65f574f706e32bc727134').exists

performance/test_read_trace.py:31: AssertionError
------------------------------ Captured log setup ------------------------------
2022-12-01 02:52:09.378 INFO [neon_fixtures.py:87] base_dir is /home/yeputons/neon/neon
2022-12-01 02:52:09.378 INFO [neon_fixtures.py:133] top_output_dir is /home/yeputons/neon/neon/test_output
2022-12-01 02:52:09.380 INFO [neon_fixtures.py:105] neon_binpath is /home/yeputons/neon/neon/target/debug
2022-12-01 02:52:09.381 INFO [neon_fixtures.py:120] pg_distrib_dir is /home/yeputons/neon/neon/pg_install
2022-12-01 02:52:09.381 INFO [neon_fixtures.py:144] pg_version is 14
2022-12-01 02:52:09.381 INFO [neon_fixtures.py:2715] get_test_output_dir is /home/yeputons/neon/neon/test_output/neon
2022-12-01 02:52:09.382 INFO [neon_fixtures.py:2715] get_test_output_dir is /home/yeputons/neon/neon/test_output/test_read_request_tracing
2022-12-01 02:52:09.382 INFO [neon_fixtures.py:2736] test_output_dir is /home/yeputons/neon/neon/test_output/test_read_request_tracing
----------------------------- Captured stderr call -----------------------------
 * Running on http://<IP_ADDRESS>:15000 (Press CTRL+C to quit)
------------------------------ Captured log call -------------------------------
/home/yeputons/neon/neon/test_runner/fixtures/benchmark_fixture.py:475: UserWarning: no out dir provided to store performance test results
  warnings.warn("no out dir provided to store performance test results")
2022-12-01 02:52:09.391 INFO [neon_fixtures.py:225] Port 15005 is in use, skipping
2022-12-01 02:52:09.392 INFO [neon_fixtures.py:910] Config:
default_tenant_id = '9e56ec99da720db1eeb510be6f7dbe05'

[etcd_broker]
broker_endpoints = ['http://<IP_ADDRESS>:15001']
etcd_binary_path = '/usr/bin/etcd'

[pageserver]
id=1
listen_pg_addr = 'localhost:15003'
listen_http_addr = 'localhost:15004'
auth_type = 'Trust'

[[safekeepers]]
id = 1
pg_port = 15006
http_port = 15007
sync = false
2022-12-01 02:52:09.392 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local init --config=/tmp/tmpp5iijccl --pg-version 14"
2022-12-01 02:52:09.392 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:10.479 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15003' in '/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 14539
Successfully initialized timeline c7d07f553659a7b7afc7bed1b4fbc1a5
Stopped pageserver 1 process with pid 14539

2022-12-01 02:52:10.480 INFO [neon_fixtures.py:2677] Starting etcd to listen incoming connections at "http://<IP_ADDRESS>:15001"
2022-12-01 02:52:11.696 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pageserver start"
2022-12-01 02:52:11.697 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:11.801 INFO [neon_fixtures.py:1347] Run success: Starting pageserver at 'localhost:15003' in '/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo'.
pageserver started, pid: 14696

2022-12-01 02:52:11.802 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local safekeeper start 1"
2022-12-01 02:52:11.802 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:11.906 INFO [neon_fixtures.py:1347] Run success: Starting safekeeper at '<IP_ADDRESS>:15006' in '/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/safekeepers/sk1'.
safekeeper 1 started, pid: 14825

2022-12-01 02:52:11.908 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local tenant create --tenant-id c0325f822fe3de578c6df2d0ef815414 --timeline-id 60103f9ac66c0df8d8574864167ce027 --pg-version 14 -c trace_read_requests:true"
2022-12-01 02:52:11.908 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:13.3   INFO [neon_fixtures.py:1347] Run success: tenant c0325f822fe3de578c6df2d0ef815414 successfully created on the pageserver
Created an initial timeline '60103f9ac66c0df8d8574864167ce027' at Lsn 0/1696628 for tenant: c0325f822fe3de578c6df2d0ef815414

2022-12-01 02:52:13.3   INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local timeline create --branch-name test_trace_replay --tenant-id c0325f822fe3de578c6df2d0ef815414 --pg-version 14"
2022-12-01 02:52:13.4   INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.148 INFO [neon_fixtures.py:1347] Run success: Created timeline '87066ec498b65f574f706e32bc727134' at Lsn 0/1696628 for tenant: c0325f822fe3de578c6df2d0ef815414

2022-12-01 02:52:14.148 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pg create --tenant-id c0325f822fe3de578c6df2d0ef815414 --branch-name test_trace_replay --pg-version 14 --port 15008 main"
2022-12-01 02:52:14.149 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:1347] Run success:
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:2262] Starting postgres node main
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pg start --tenant-id c0325f822fe3de578c6df2d0ef815414 --pg-version 14 --port=15008 main"
2022-12-01 02:52:14.152 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.278 INFO [neon_fixtures.py:1347] Run success: Starting existing postgres main...
Safekeepers synced on 0/0
Extracting base backup to create postgres instance: path=/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo/pgdatadirs/tenants/c0325f822fe3de578c6df2d0ef815414/main port=15008
Starting postgres node at 'host=<IP_ADDRESS> port=15008 user=cloud_admin dbname=postgres'

2022-12-01 02:52:14.278 INFO [neon_fixtures.py:2377] Postgres startup took 0.12995028495788574 seconds
2022-12-01 02:52:14.829 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pg stop --tenant-id c0325f822fe3de578c6df2d0ef815414 main"
2022-12-01 02:52:14.830 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:14.936 INFO [neon_fixtures.py:1347] Run success:
---------------------------- Captured log teardown -----------------------------
2022-12-01 02:52:14.959 INFO [neon_fixtures.py:777] Cleaning up all storage and compute nodes
2022-12-01 02:52:14.959 INFO [neon_fixtures.py:2494] Stopping safekeeper 1
2022-12-01 02:52:14.959 INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local safekeeper stop 1 -m immediate"
2022-12-01 02:52:14.960 INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:15.64  INFO [neon_fixtures.py:1347] Run success: Stopping safekeeper 1 with pid 14825 immediately...
safekeeper 1 stopped

2022-12-01 02:52:15.64  INFO [neon_fixtures.py:1590] Stopping pageserver with ['pageserver', 'stop', '-m', 'immediate']
2022-12-01 02:52:15.65  INFO [neon_fixtures.py:1319] Running command "/home/yeputons/neon/neon/target/debug/neon_local pageserver stop -m immediate"
2022-12-01 02:52:15.65  INFO [neon_fixtures.py:1320] Running in "/home/yeputons/neon/neon/test_output/test_read_request_tracing/repo"
2022-12-01 02:52:15.170 INFO [neon_fixtures.py:1347] Run success: Stopping pageserver with pid 14696 immediately...
pageserver stopped

2022-12-01 02:52:15.171 INFO [neon_fixtures.py:722] no remote storage was set up, skipping cleanup
------------------------------ Benchmark results -------------------------------
=========================== short test summary info ============================
FAILED performance/test_read_trace.py::test_read_request_tracing - AssertionE...
====================== 1 failed, 269 deselected in 5.93s =======================

Note that the benchmarks suite was skipped in the PR #2785. Seems like we only run benchmarks on main or PRs labeled run-benchmarks

@hlinnaka are you working on this? I thought you mentioned something about this yesterday.

Yes, see https://github.com/neondatabase/neon/pull/2989. Forgot to link this issue


In Princess Pizza tutorial the pizza is of type "enemy" and not "food"

See title. Makes no sense @jwunderl

@ChaseMor please fix this.

Fixing these ones you linked me now~


Finish username mention autocomplete on type

[x] Back-end
[x] Front-end

Fix https://github.com/nicolasparada/nakama/commit/d9098d33cfbfc0a9450e26c50c2bbac00a1ab249


Add Cake Wallet for iOS to Downloads section?

Should Cake Wallet by @fotolockr for iOS be added to the Mobile/Light Downloads section?
The source is on Github and the developer is active on Github and reddit. However, you're putting your trust in the fact that the file uploaded to Apple is the same as the source on Github.

We could link the Github page directly if this is a concern.
The application has been around for a while and has received positive reception from several longtime community members.
While these should not be treated as comprehensive audits, the application seems to have received a similar amount of scrutiny as Monerujo.
It's concerning that Apple doesn't allow people to run build apps like you can do with android .apks, but someone with an Apple developer account can run from their own builds from source iirc.

@SamsungGalaxyPlayer, I agree that the Github link is a good idea. iOS users are definitely looking for a mobile app and this fills that position.
I don't have an Apple developer account but believe you are correct.

Hi All,
Thank you for the comments. Yes, we think it should be listed there.  Our app has been reviewed by user John_alan.    A link to Github AND a link to the App Store or our website for less sophisticated users would good.

By the way, we will be moving this repo to our official Cake Technologies account within Github shortly.  Will keep all posted.

+resolved


Second paragraph of description not retained on GBIF

The dataset description consists of two paragraphs: https://www.vliz.be/imis?dasid=3117&doiid=826

European Seabirds At Sea (ESAS) assembles offshore monitoring data on ... European-wide data assembly in 1991.
ESAS data are collected by ... to download or request data.

On GBIF only the first paragraph is retained: https://www.gbif.org/dataset/3470d506-e667-4e3f-b178-819669684c05
This is not a major issue, but would it be possible to retain both paragraphs?

Hi @peterdesmet , working on it, I'll let you know when it is fixed


Task7 8

Hello,
I've added a new app.py file in app folder & index.html file in templates folder for task 7.
Please check it.
Regards,

please revert the test commit and ensure you linked the pull request to an issue