Question: how does the sync option work for b2?

This is not a bug report, just a question. Not sure where else is a good place to ask.
How does the B2 sync work? Does it compute a local sha and then get the remote sha from the file metadata? If it does not match it will upload the file? How does the modification time comes into play with this (if sha is the same but modification time is different, or if modification time is the same and sha is different)?
From the B2 page:

Modified times are used in syncing and are fully supported except in the case of updating a modification time on an existing object. In this case the object will be uploaded again as B2 doesn’t have an API method to set the modification time independent of doing an upload.

The SHA1 checksums of the files are checked on upload and download and will be used in the syncing process.

I don't quite understand how this works. Can someone clarify?

rclone (like rsync) checks the modification date and the size first and if those differ does the upload.
If the size is the same, then rclone checks the sha1 and if that is identical then it updates the modification time.  For b2 you can't change the modification time of an object, so that means uploading it again.
If you'd rather use the size and sha1 checksum first then you want the --checksum option which causes rclone to upload if the size or sha1 checksum is different.
As for this part

The SHA1 checksums of the files are checked on upload and download and will be used in the syncing process.

rclone checks the sha1 sums of objects it uploads to make sure they got uploaded properly, and downloads to make sure the data wansn't corrupted.
Hope that helps!
Nick

If you'd rather use the size and sha1 checksum first then you want the --checksum option which causes rclone to upload if the size or sha1 checksum is different.

Does it check modification date after? I would like to avoid downloading again if possible because it would be very expensive.
Other than that thanks for the fast clarification! :)

No --checksum only checks the size and the checksum.

Thanks for letting me know!


Clean up Azure Billing notifications

Describe the issue
At the moment Azure billing notifications are still landing with David E and Andy T.  We would like them to go to Cloud Pathfinder and CSAM roles.
Additional context

Sample email is in Julian's Azure, Billing mail folder from date May 30, 2022, 1:01 PM

Definition of done

Create or use existing CPF shared mailboxen
Find out from Dean P if there's a shared mailbox or account he'd prefer to receive Azure billing notifications at
Change the "Here is a summary of your Azure monetary commitment balance and unbilled charges." mails to go to the appropriate place.

not relevant


[local-db - PART 1] Store new features in local db

Gentle ping. Would like to close the PR soon since I have a few more I'd like to stack. Thanks!

@navinsivakumar, I think I'll abandon this PR in favor of one that incorporates our latest discussion.


when i use bazel to build i got error that  no such package '@protobuf

Please go to Stack Overflow for help and support:
http://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug or a feature request.
The form below must be filled out.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

Please try upgrading bazel, but I apologize but I am having a hard time understanding what the problem is, where the problem is, and what version it affects. Please resubmit and pay attention to the issue template (https://github.com/tensorflow/tensorflow/issues/new) . Please provide all the information it asks.
Thank you.


Problem with children container width

How i can fix this problem?
I need a difference width but not bigger than parrent.

Hi @antoxi4, this kind of question should be asked on http://stackoverflow.com/.
Could you do that and close this issue? Thanks.


chore(deps): Upgrading to go 1.19

The biggest change with 1.19 in our existing codebase is godocs.
Some things to note:

It kinda breaks multiline TODO comments in Goland
Nested lists are not supported, so try to mix list markers instead

Woah, make fmt did something really weird. Going back and checking what happened

Codecov Report

Merging #1067 (74106f1) into main (8657edc) will decrease coverage by 0.04%.
The diff coverage is 55.55%.

@@            Coverage Diff             @@
##             main    #1067      +/-   ##
==========================================
- Coverage   56.56%   56.51%   -0.05%
==========================================
  Files         135      135
  Lines        8965     8971       +6
==========================================
- Hits         5071     5070       -1
- Misses       3359     3365       +6
- Partials      535      536       +1

Impacted Files
Coverage Δ

cmd/env.go
76.47% <ø> (ø)

cmd/flags_misc.go
41.56% <0.00%> (-1.03%)
:arrow_down:

core/testing.go
78.57% <0.00%> (ø)

header/p2p/exchange.go
62.22% <ø> (ø)

header/sync/sync.go
65.50% <ø> (ø)

header/verify.go
81.39% <ø> (ø)

ipld/get_shares.go
90.00% <ø> (ø)

ipld/plugin/test_helpers.go
0.00% <0.00%> (ø)

ipld/retriever.go
91.97% <ø> (ø)

ipld/retriever_quadrant.go
100.00% <ø> (ø)

... and 11 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Woah, make fmt did something really weird. Going back and checking what happened

I think this is related to: https://tip.golang.org/doc/go1.19#go-doc

Go mod tidy will not pass until go is updated in the CI

Ah ok. Some things were already discussed.

Are we going to update CI here?

Not sure how to do that @Wondertan

@distractedm1nd, do you mind if I commit to the branch here then?


Disabled entities incorrectly triggered

Describe the bug
Disabled entities such as pet or vehicle detection are still triggered and cause errors in home-assistant.log
To Reproduce
Disable a motion entity for a camera, log will show errors like:
Entity xxx is incorrectly being triggered for updates while it is disabled. This is a bug in the reolink_dev integration
Expected behavior
No errors for disabled entities
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:
Please provide useful information about your environment, like:

Home Assistant version: 2021.12.0

Additional context
Add any other context about the problem here.

is this new warning since 2021.12.0 or it's brand new installation for you?

Please try 0.46

0.46 seems to have fixed it.


How can I generate CHANGELOG.md when I first time bump version?

Hi. Thanks for your work.
When I try changelogen, I find no way to generate CHANGELOG.md when I first time bump version.
$ npx changelogen --release
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)

 ERROR  Command failed with exit code 128: git describe --tags --abbrev=0                                                                                16:07:45
fatal: No tags can describe 'dbd9fa593d64f0a04bb801be556eae775242c48a'.
Try --always, or create some tags.

  fatal: No tags can describe 'dbd9fa593d64f0a04bb801be556eae775242c48a'.
  Try --always, or create some tags.
  at makeError (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/execa/lib/error.js:59:11)
  at handlePromise (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/execa/index.js:124:26)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async execCommand (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/changelogen/dist/shared/changelogen.53701f80.mjs:94:15)
  at async getLastGitTag (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/changelogen/dist/shared/changelogen.53701f80.mjs:13:13)
  at async loadChangelogConfig (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/changelogen/dist/shared/changelogen.53701f80.mjs:415:19)
  at async Module.defaultMain (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/changelogen/dist/chunks/default.mjs:24:18)
  at async main (/Users/wurui/.npm/_npx/fd5a125c5466fd2f/node_modules/changelogen/dist/cli.mjs:22:3)

Can you please give me some advice? Thanks.

Hey i had the same. The tool is looking for a git tag to have start for changelog.md.
Just do git tag 0.0.1 && git push --tags. After that it should work

Thanks for your advice. I am also waiting https://github.com/unjs/changelogen/pull/77 release.


Update the Example project to use CocoaPods 1.0

[Current coverage][cc-pull] is 70.23%

Merging [#674][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #674   diff @@
==========================================
  Files             2          2
  Lines           944        944
  Methods         112        112
  Messages          0          0
  Branches        225        225
==========================================
  Hits            663        663
  Misses          128        128
  Partials        153        153

[][cc-pull]

Powered by Codecov. Last updated by [fe0d562...8682b4d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/TTTAttributedLabel/TTTAttributedLabel/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/TTTAttributedLabel/TTTAttributedLabel/compare/fe0d56240622e3e38ec9654311f2faf10d2549ad...8682b4dcf9c89bc6e10882a85bbb9436ec8078f2
[cc-pull]: https://codecov.io/gh/TTTAttributedLabel/TTTAttributedLabel/pull/674?src=pr

❗ ❗ ❗ ❗ ❗  🎉

@segiddins -- how do you feel about including Pods/ in the repo for the example project?

@jessesquires I'd rather not


read_sql() parallelism parameter

Add a parameter which will limit the maximum number of sessions for concurrent partitioned read.
RD
Thanks @rd5802 that sounds good to me. Would you mind to create a new issue so we can track that specific request? I think we can leave this conversation open for the sake of keeping the conversation on parallel read_sql alive.
Originally posted by @devin-petersohn in https://github.com/modin-project/modin/issues/418#issuecomment-460400546

Thanks @rd5802! It should be relatively straightforward, and a couple of people have recently come to me about contributing so I will let someone take it.
All we really need to do for this is to add a max_sessions parameter to modin.experimental.pandas.io.read_sql.

That's really great @devin-petersohn . Looking forward to see whats next 👍 .

Looks like this was fixed in #594 and can be closed?

Yes, thank you @itamarst


deposit cellxgene using nginx

As in your readme, First, the flask application which is deployed on your server (found in the ‘prep your project’ section of the linked article) should be cellxgene with an appropriate wsgi.py file added as described in the article.
I don't know how to modify this to make it run cellxgene
from myapp import create_app

app = create_app()

if __name__ == "__main__":
    app.run(host='<IP_ADDRESS>')

Any help?
Thanks!

Hey @brainfo - I think this might have been addressed in this czi science slack thread
For completeness in this github discussion - check out this example of self-hosting cellxgene using nginx
Also, it is worth noting that the cellxgene team does not provide dedicated help for self-hosting, so it is likely we won't be able to provide "official" guidance past this point - but hopefully this resource should get you started!

已收到，谢谢。


fix(client): issues with storing meta in leveldb

Store meta in json file instead
Signed-off-by: Alexey Igrychev<EMAIL_ADDRESS>rel https://github.com/werf/trdl/issues/212 https://github.com/werf/trdl/issues/226

rejected


Subject in custom badge forces lowercase

Not sure if this is a bug or a stylistic choice, but I noticed that custom badges only respect the case of the status, not the subject.
Example: https://img.shields.io/badge/TEST-CASE-green.svg
I swear I've used badges with uppercase in the subject line, but maybe I'm remembering incorrectly. I first noticed the issue on http://makeapullrequest.com/ the URL Kent uses has PRs in it, but the badge looks odd rendering at prs. Which makes me think it's a bug that was introduced over time

The same has happend to all my badges. They were nicely formated like  "MyTitle | 1234"  and now they're all lowercased during last week or two somehow.  and read "mytitle | 1234"
e.g.:
<img src="https://img.shields.io/badge/EQ BankCard 8 - 735 | 1-6b8b08.svg">

Hi thanks for reporting this. It looks like this was introduced in #2058 although it is not the intended behaviour. I've proposed a fix in #2116


changed web3.sha3 to web3.util.sha3 as per web3 1.0.0 change

web3 1.0.0 update moved web3.sha3 to web3.util.sha3, all new users that do npm install will get the most recent version of web3

bigger refractor of testcases needed


data download

The data set cannot be downloaded from the link. Where can I download the dataset of caption_test_a_annotations_20180103 and caption_test_b_annotations_20180103?

You have to contact the dataset owner. I am not authorized to redistribute this dataset.


Add test suite

I never really tackled the testing of this library since a lot of the gesture driven behaviours are pretty hard to test, but it's time to.
Tooling: Quick + Nimble + Snapshot
Areas to look at:

Add test suite
Add coveralls.io

Commit 4c42133 adds the base for the test suite, using Quick, Nimble and Nimble-Snapshots.


Corrected color theme.

Issue Number: 10
Issue Description: Create App Color Scheme
Summary of solution:
Fixed broken links and added easy to read tables of values.
Can this issue be closed? Yes
Should any new issues be added as a result of this solution? No

Color Scheme to go with new NAVI Logo -- Looking for some feedback

@TheDevPath/grow-with-google let's give some feedback on your favorite color scheme

my top two votes are
1- first scheme
2 - second scheme

I am personally leaning toward the first one-- I don't think a green tone is needed but the pop of color is a good accent when needed.

I like the first one too

ditto on the first

The first one

Im a fan of the contrast with the green

First is my favorite too


[HIPIFY] Added directory and file exclusion, updated whitelist

-exclude-dirs=dirlist will set up a list of directories to be excluded.
-exclude-files=filelist will set up a list of files to be excluded.
List separator is the , (comma) like for whitespaces.
Populate whitelist with a few more APIs.

Requests completed.


Horizontal list support in IGListCollectionViewLayout

Inspired by #750. If you wanted to have a horizontally scrolling list that put sections on the "same line" (which would actually be a column), this wont work with IGListKit since UICollectionViewFlowLayout doesn't support this.

@rnystrom Isn't this "collection view inside a collection cell" ?

@jessesquires it's actually making IGListCollectionViewLayout work w/ horizontal scrolling (its fixed to vertical using height/y atm).

So I was going to take a crack at this one, if no one is working on it... If we generalize IGListCollectionViewLayout, what's the desired behavior for section headers when scrolling horizontally -- always fill vertically (minus insets) and, if sticky, pin to the left (offset by stickyHeaderOriginAdjustment)?

@rnystrom @jessesquires @edmonston With UICollectionViewFlowLayout, supplementary views are placed on the left/right side of each section. But that's kind of lame... If you take a look at built-in emoji keyboard, each section has a sticky header on top. It looks nice but might not be easy to copy? (For example, headers have to have same height?)

Yeah I agree @zhubofei that UICollectionViewFlowLayout's way of handling horizontal scrolling with supplementary views is not super useful from UI perspecive (see video). But as you point out, keeping the headers horizontal would need them to be the same height (and could be strange with short/narrow sections)... I have a local branch that generalizes IGListCollectionViewLayout to behave more like UICollectionViewFlowLayout in the horizontal axis. @rnystrom was that what you had in mind with this enhancement? If so I can work it into a PR...


[W6.10][W12-3] update read me

Finalised read-me for week 6. Added mock up UI screenshot and edited the contents of the read-me to suit our product.

Pull Request Test Coverage Report for Build 78

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.811%

Totals

Change from base Build 66:
0.0%

Covered Lines:
1433

Relevant Lines:
1544

💛  - Coveralls


issue getting denomailer running

@Enyorose Your code looks good (also the debug-output).
Could you try it again with the debug.encodeLB option  set to true?

Just for your information it looks like a bug / issue with your specific smtp-server.

Hello here is the document requested, we are using an individually owned company mailer that we host on site. I read that we are unable to use the Microsoft servers and the google servers so we moved it to a different one. Would you have any idea what it may be specifically blocking so I can get my IT guys to look for it?
debug with true.txt

Just some quick info:

I can see the send functions runs until here https://github.com/EC-Nordbund/denomailer/blob/main/client/basic/client.ts#L321
The server doesn't have reacted to sending ".\r\n".

Some ideas to test (just use deno vendor so you can modify the code)
at https://github.com/EC-Nordbund/denomailer/blob/main/client/basic/client.ts#L316
try adding await this.#connection.writeCmd("\r\n");.
If you can send me some server-credentials so I can test directly on your smtp-server it will be faster fixed.
(email<EMAIL_ADDRESS>

So I did as you requested and added that piece into the spot you suggested, I have also attached the .debug document.
I'm talking with my smtp server tech, what kinds of settings would you look for to fix this issue?
afteraddingsourcecode.txt

I have theory, I have been researching with my tech guy and it looks its recieving the message and waiting for a '.' at the end to be able to send it. I found a document on the smtp command https://www.shellhacks.com/send-email-smtp-server-command-line/ and it mentions their needs to be a period on a line by its self to signify the end. Both the server and I are getting that request, I'm sure you've built that in somewhere I'm just not sure why its not running.

I'm sure you've built that in somewhere I'm just not sure why its not running.

I can see that denomailer sends this message:
(1) ['.
']

at end of your log.
So we are here https://github.com/EC-Nordbund/denomailer/blob/main/client/basic/client.ts#L315
from there on the following happens:
  try { // started in L75
   await this.#connection.writeCmd(".\r\n"); // send . to server to end data mode (the server did not end data mode)

   this.#connection.assertCode( // the server is in "DATA-MODE" so it sends nothing so this will throw
        await this.#connection.readCmd(),
        CommandCode.OK,
      );
      await this.#cleanup();
      this.#que.next();
    } catch (ex) {
      await this.#cleanup(); // as server is still in "DATA-MODE" this is an infinite loop.
      this.#que.next();
      throw ex;
    }
  }

Try import denomailer from https://raw.githubusercontent.com/EC-Nordbund/denomailer/fix/data-mode/mod.ts this should give an error and logs "Error while in datamode - connection not revoverable"

So I ran that test mod, and it provided the error code. Is there any ideas on how to make it work?

No more reproduction provided so closing this.


Changed ChatMessageRole to String constants

It makes more sense to use String constants instead of an enum with the "value()" method.

I think it would be better to make the ChatMessage take the enum instead, then convert to the .value() during serialization.

I think it would be better to make the ChatMessage take the enum instead, then convert to the .value() during serialization.

It could definitely be another option. I think I'll elaborate both, make another pull request, and let @TheoKanning decide between the two.


nearcore: 1.26.0 -> 1.26.1 [security update]

Description of changes

Things done
https://github.com/near/nearcore/releases/tag/1.26.1

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

cc @mikroskeem


HAWKULAR-798 Make default time period 12 hours instead of 1 hour. (1 …

…hour didn't really give us anything to drill into).

lgtm


Added the fix for the search button per QA bug

https://www.notion.so/cos/0de7c99478234fd7be57029dd96aa2d3?v=a4e6d7c70c004d27a0955aa2742775a4&p=8915343789724fc6bba353dd643bde80&pm=c

Ticket: [See Above]
Feature flag: n/a

Purpose
The search button was not working on the new branded header
Summary of Changes
Added a search button with sytling
Screenshot(s)

Side Effects
None
QA Notes
Searching on the preprints page should now work by clicking the button and hitting enter

The bug is for branded landing pages (https://staging3.osf.io/preprints/biohackrxiv), not the general OSF Preprints landing page


Add support cluster query param in TurbineStream

Brief Description
Add support cluster parameter into Turbine Stream server.
Background
Turbine Stream server doesn't support a cluster query parameter, unlike Turbine server until now. It means that we have to receive all Hystrix metrics at the same time from Turbine Stream server.  It is not a critical problem in the most environment. But in a production environment like us -  we have over hundreds of circuit breaks and dozens of thread pools - Turbine dashboard is frozen when we try to load the page because too many metrics are delivered to the browser at the same time and it makes our turbine dashboard unusable.
Description
This PR adds the support of cluster parameter for Turbine Stream server.  So users can specify URL on their Turbine dashboard like below.
http://my.turbine.sever:8989/turbine.stream?cluster=customers

If query parameter is not provided or default is provided, all metrics will be delivered and it is the default behavior of current release.
The limitation is that user cannot configure how to extract cluster name. The implementation uses Eureka's serviceId as cluster name and these are not configurable. The limitation was described in the document.
Etc
The implementation has the limitation about how to define and extract cluster name from instances.
Nevertheless, it might be very useful for users who are using Turbine Stream servers in the production environment like us. Moreover, the change doesn't have any side effect on user side because the default behavior without parameter is same as current release.

Actually, turbine-stream has always been java 8. https://github.com/spring-cloud/spring-cloud-netflix/blob/1.4.x/spring-cloud-netflix-turbine-stream/pom.xml#L25-L26

Hmmm i wonder why CircleCI if failing then...
[ERROR] Failed to execute goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.14:check (enforce-java-7) on project spring-cloud-netflix-turbine-stream: Execution enforce-java-7 of goal org.codehaus.mojo:animal-sniffer-maven-plugin:1.14:check failed. NullPointerException -> [Help 1]

Looks like the .jdk8 files was accidentally removed here https://github.com/spring-cloud/spring-cloud-netflix/commit/bbac5a730f673f55f0ff86cb5f94fa21aecf135c

@yongsungyoon please rebase against 1.4.x

Codecov Report

Merging #3001 into 1.4.x will increase coverage by 0.21%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##              1.4.x    #3001      +/-   ##
============================================
+ Coverage     69.38%   69.59%   +0.21%
+ Complexity     1923     1863      -60
============================================
  Files           240      229      -11
  Lines          8489     8249     -240
  Branches       1053     1018      -35
============================================
- Hits           5890     5741     -149
+ Misses         2196     2121      -75
+ Partials        403      387      -16

Impacted Files
Coverage Δ
Complexity Δ

...cloud/netflix/turbine/SpringAggregatorFactory.java
58.13% <0%> (-2.33%)
5% <0%> (ø)

...cloud/netflix/zuul/filters/ProxyRequestHelper.java
91.33% <0%> (-0.07%)
53% <0%> (-1%)

...oud/netflix/turbine/stream/TurbineApplication.java

...turbine/stream/TurbinePortApplicationListener.java

...rk/cloud/netflix/sidecar/SidecarConfiguration.java

...etflix/turbine/stream/HystrixStreamAggregator.java

...etflix/turbine/stream/TurbineStreamProperties.java

...ix/sidecar/LocalApplicationHealthCheckHandler.java

...tflix/sidecar/LocalApplicationHealthIndicator.java

...turbine/stream/TurbineStreamAutoConfiguration.java

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2df8103...f57a092. Read the comment docs.

@spencergibb I've rebased the PR against 1.4.x.

@yongsungyoon I was not able to merge this forward into the 2.0.x branch, it was outside of my knowledge.  Would you mind submitting another PR against that branch with the correct changes?


Command was killed with SIGABRT (Aborted): pkg-pr-new publish --compact --pnpm

Hi there, we are getting this error on most of our pkg.pr.new repo github actions, did something change?
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +53
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 53, reused 2[8](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:9), downloaded 25, added 53, done

<--- Last few GCs --->

[1[9](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:10)48:0x5eb7010]   314616 ms: Scavenge 4013.7 (4131.2) -> 40[10](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:11).3 (4131.2) MB, 13.47 / 0.00 ms  (average mu = 0.696, current mu = 0.773) allocation failure;
[1948:0x5eb7010]   314643 ms: Scavenge 4015.8 (4131.2) -> 40[11](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:12).3 (4131.2) MB, 9.11 / 0.00 ms  (average mu = 0.696, current mu = 0.773) allocation failure;
[1948:0x5eb7010]   314687 ms: Scavenge 4017.9 (4131.2) -> 40[12](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:13).4 (4147.2) MB, 15.40 / 0.00 ms  (average mu = 0.696, current mu = 0.773) allocation failure;

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0xb86ecf node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0xef74d0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0xef77b7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x1109355  [node]
 5: 0x11211d8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 6: 0x10f72f1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 7: 0x10f8485 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0x10d4ba6 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
 9: 0x10c67d4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [node]
10: 0x10c8fb6 v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [node]
11: 0x141a297 v8::internal::String::SlowFlatten(v8::internal::Isolate*, v8::internal::Handle<v8::internal::ConsString>, v8::internal::AllocationType) [node]
12: 0x155334d v8::internal::Runtime_StringCharCodeAt(int, unsigned long*, v8::internal::Isolate*) [node]
[13](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:14): 0x7fef918d9ef6
 ERROR  Command was killed with SIGABRT (Aborted): pkg-pr-new publish --compact --pnpm

pnpm: Command was killed with SIGABRT (Aborted): pkg-pr-new publish --compact --pnpm
    at makeError (/home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:19342:17)
    at handlePromise (/home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:19913:33)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.handler [as dlx] (/home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:2196[17](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:18):9)
    at async /home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:229028:[21](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:22)
    at async main (/home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:[22](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:23)8991:34)
    at async runPnpm (/home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:229242:5)
    at async /home/runner/.cache/node/corepack/v1/pnpm/9.1.4/dist/pnpm.cjs:229[23](https://github.com/Tresjs/tres/actions/runs/11113957016/job/30879427296?pr=845#step:7:24)4:7
Error: Process completed with exit code 1.

ok, vitest just got this too! let me see what's going on!
Thank you so much!

Thanks for solving this so quick


[DPE-5386] Bump pgbackrest version to 2.53

See https://github.com/canonical/postgresql-operator/pull/633 For relevant context and integration test.

LGTM, postfactum. :-D


Google Apps Script compatibility

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
"Importing" algoliasearch into an Apps Script fails with the error document is not defined.
What is the expected behavior?
It would be nice to have an App Scripts compatible build that uses the APIs provided by Google to integrate with their different platforms.
Happy to help on the subject as I have already started an overly simple Apps Script client for a small project!

I never heard of App Scripts before, so here's a link for future reference.
document is used for two things by looking through the code:

document.location.protocol in a few places.

won't be needed in the next version, since we'll do https alone

document.write for the crazy v3 -> v2 fallback on /latest

will be dropped in v4

JSONP fallback

will be harder to avoid, but maybe that code won't be relevant in Google Apps, and thus not needed

Relevant issue to track: #195

Have you tried any of the alternative build @olance ? (server, parse...)

Well the thing is, Apps Script does not provide APIs such as Promises, fetch and so on.
So I think it would require its own build...
I have done a quick, dirty and incomplete client for my own purposes in the past few days, if you want to see what it looks like:
/******* CLIENT *******/

function AlgoliaClient(appID, apiKey) {
  this.appID = appID;
  this.apiKey = apiKey;
}

var p = AlgoliaClient.prototype;

p.initIndex = function initIndex(indexName) {
  return new AlgoliaIndex(this, indexName);
};

p.hostName = function hostName() {
  return this.appID + '.algolia.net';
};

p.authHeaders = function authHeaders() {
  return {
    'X-Algolia-Application-Id': this.appID,
    'X-Algolia-API-Key': this.apiKey
  };
};

/******* INDEX *******/

function AlgoliaIndex(client, indexName) {
  this.client = client;
  this.name = indexName;
}

p = AlgoliaIndex.prototype;

p.clearIndex = function clearIndex() {
  var headers = this.client.authHeaders();

  var res = UrlFetchApp.fetch('https://' + this.client.hostName() + '/1/indexes/' + encodeURIComponent(this.name) + '/clear', {
      contentType: 'application/json',
      headers: headers,
      method: 'post',
  });

  return JSON.parse(res.getContentText());
};

p.addObjects = function addObjects(objects) {
  var requests = objects.map(function(obj) {
    return {
      action: 'addObject',
      body: obj
    }
  });

  var headers = this.client.authHeaders();
  var res = UrlFetchApp.fetch('https://' + this.client.hostName() + '/1/indexes/' + encodeURIComponent(this.name) + '/batch', {
    contentType: 'application/json',
    method: 'POST',
    headers: headers,
    payload: JSON.stringify({ requests: requests })
  });

  return JSON.parse(res.getContentText());
};

p.partialUpdateObject = function partialUpdateObject(object) {
  var headers = this.client.authHeaders();

  var res = UrlFetchApp.fetch('https://' + this.client.hostName() + '/1/indexes/' + encodeURIComponent(this.name) + '/' + encodeURIComponent(object.objectID) + '/partial' , {
      contentType: 'application/json',
      headers: headers,
      method: 'post',
      payload: JSON.stringify(object),
  });

  return JSON.parse(res.getContentText());
};

p.partialUpdateObjects = function partialUpdateObjects(objects) {
  var requests = objects.map(function(obj) {
    return {
      action: 'partialUpdateObject',
      objectID: obj.objectID,
      body: obj
    }
  });

  var headers = this.client.authHeaders();
  var res = UrlFetchApp.fetch('https://' + this.client.hostName() + '/1/indexes/' + encodeURIComponent(this.name) + '/batch', {
    contentType: 'application/json',
    method: 'POST',
    headers: headers,
    payload: JSON.stringify({ requests: requests })
  });

  return JSON.parse(res.getContentText());
};

p.deleteObjects = function deleteObjects(objects) {
  var requests = objects.map(function(obj) {
    return {
      action: 'deleteObject',
      objectID: obj.objectID,
      body: { objectID: obj.objectID }
    }
  });

  var headers = this.client.authHeaders();
  var res = UrlFetchApp.fetch('https://' + this.client.hostName() + '/1/indexes/' + encodeURIComponent(this.name) + '/batch', {
    contentType: 'application/json',
    method: 'POST',
    headers: headers,
    payload: JSON.stringify({ requests: requests })
  });

  return JSON.parse(res.getContentText());
};

So basically here the main differences are:

synchronous fetches
UrlFetchApp.fetch instead of fetch

😭😛

I think if you add all polyfills as expected, you might be able to do this (pseudo code):
function createGappScriptRequester() {
  return {
    send(request) {
      return new Promise((resolve, reject) => {
        try {
          const response = UrlFetchApp.fetch(request.url, {
            method: 'post',
            headers: request.headers,
            // uses form by default already
            payload: request.data,
          });

          // response seems to be synchronous from docs
          const text = response.getContentText('UTF-8');
          resolve(JSON.parse(text));
        } catch (e) {
          reject(e);
        }
      });
    },
  };
}

const client = createSearchClient({
  appId,
  apiKey,
  requester: createGappScriptRequester(),
});

client.search([
  {
    indexName: 'instant_search',
    params: { query: 'hello' },
  },
]);

I haven't tried this yet since I can't figure out where to run it, but I think it might work, or be close.

Hehe thanks @Haroenv 🙂
I'm not sure Google Apps Script supports Promises though... however the script I had provided back in the days was enough for my needs, and I was just sad to see one of my old issues go bye-bye 😉

Yes, you need polyfills for promises etc. already, since we are no longer bundling it with algoliasearch


Unable to Re-import Project from Github Repository After Deleting

Describe the bug
After I deleted a project deployed to Nuxthub (as I wasn't allowed to change the deployment region), I am not able to reimport the project from the same repository again.
Steps to reproduce
Steps to reproduce the behavior:

Go to 'Import A Github Repository'
Click on 'Select a repository'
See " (in use)" when it's not in use

Expected behavior
I expect that the list resets after deleting a project previously imported via Github repo.

Is the project still on your Cloudflare Pages account @Sidebridge ? I guess you did not check "Delete project's data on Cloudflare" ?

@Atinux yes, I didn't select the "Delete project's data on Cloudflare" option while deleting. But I also can't find any project data looking through my Cloudflare dashboard.
Where do I check, How can i fix?

This works, thank you


issue-23: base Makefile

Ready for review. Will add a "setup" target once the docker-compose stuff is merged.


Missing Comment box, reviewer list in left pane when checked out PR for review

Type: Bug
In all but one of my repos, when I go to the GH PR extension and open a PR waiting for my review, I can then open the description page for it and click Check Out.  Once I have done that, I am given a pane in the left-hand pane which includes a comment box/button and a list of reviewers.
In one particular repo, I don't get this comment box/button/list of reviewers pane when I Check Out a PR waiting on my review.
The OUTPUT tab for GitHub Pull Request displays the following when I click Check Out:
2023-06-30 14:11:21.706 [info] Review> Switch to Pull Request #12561 - start
2023-06-30 14:11:25.589 [info] Review> Switch to Pull Request #12561 - done
2023-06-30 14:11:25.590 [info] Review> Validate state in progress
2023-06-30 14:11:25.590 [info] Review> Validating state...
2023-06-30 14:11:25.642 [info] Found GitHub remote for folder /home/brian/daos/daos
2023-06-30 14:11:25.660 [info] Trying to use globalState for mentionable users.
2023-06-30 14:11:25.868 [info] No globalState for mentionable users.
2023-06-30 14:11:25.983 [info] Review> current branch jemalmbe/sre-1904 is associated with pull request #12561
2023-06-30 14:11:25.983 [info] Review> Resolving pull request
2023-06-30 14:11:26.930 [info] Review> Fetching pull request data
2023-06-30 14:11:26.930 [info] PullRequestTree> Adding PR #12561 to tree
2023-06-30 14:11:26.954 [info] Review> Register comments provider
2023-06-30 14:11:27.036 [info] PullRequestTree> Creating file and commit nodes for PR #384
2023-06-30 14:11:27.037 [info] PullRequestTree> Creating file and commit nodes for PR #12561
2023-06-30 14:11:27.040 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:27.040 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:11:27.041 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:27.041 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:11:27.723 [info] PullRequestTree> Local files have changed, refreshing Files node
2023-06-30 14:11:27.865 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:27.865 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:11:27.871 [info] PullRequestTree> Review threads have changed, refreshing Files node
2023-06-30 14:11:27.872 [info] PullRequestTree> Review threads have changed, refreshing Commits node
2023-06-30 14:11:27.872 [info] Review> Display pull request status bar indicator and refresh pull request tree view.
2023-06-30 14:11:27.873 [info] Review> Using focus mode = true.
2023-06-30 14:11:27.873 [info] Review> State validation silent = true.
2023-06-30 14:11:27.873 [info] Review> PR show should show = false.
2023-06-30 14:11:28.073 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:28.073 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:11:28.138 [info] PullRequestTree> Comments have changed, refreshing Files node
2023-06-30 14:11:28.139 [info] PullRequestTree> Comments have changed, refreshing Commits node
2023-06-30 14:11:28.139 [info] PullRequestTree> Review threads have changed, refreshing Files node
2023-06-30 14:11:28.139 [info] PullRequestTree> Review threads have changed, refreshing Commits node
2023-06-30 14:11:28.296 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:28.297 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:11:28.373 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:28.373 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:11:28.613 [info] PullRequestTree> Review threads have changed, refreshing Files node
2023-06-30 14:11:28.613 [info] PullRequestTree> Review threads have changed, refreshing Commits node
2023-06-30 14:11:28.616 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:11:28.616 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:24.396 [info] PullRequestTree> Local files have changed, refreshing Files node
2023-06-30 14:12:24.445 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:24.446 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:24.697 [info] PullRequestTree> Comments have changed, refreshing Files node
2023-06-30 14:12:24.697 [info] PullRequestTree> Comments have changed, refreshing Commits node
2023-06-30 14:12:24.697 [info] PullRequestTree> Review threads have changed, refreshing Files node
2023-06-30 14:12:24.697 [info] PullRequestTree> Review threads have changed, refreshing Commits node
2023-06-30 14:12:24.701 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:24.701 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:24.894 [info] PullRequestTree> Local files have changed, refreshing Files node
2023-06-30 14:12:25.097 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:25.097 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:25.097 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:25.097 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:25.251 [info] PullRequestTree> Comments have changed, refreshing Files node
2023-06-30 14:12:25.251 [info] PullRequestTree> Comments have changed, refreshing Commits node
2023-06-30 14:12:25.254 [info] PullRequestTree> Review threads have changed, refreshing Files node
2023-06-30 14:12:25.254 [info] PullRequestTree> Review threads have changed, refreshing Commits node
2023-06-30 14:12:25.420 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:25.420 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:25.638 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:25.638 [info] PullRequestTree> Got all children for Files node
2023-06-30 14:12:25.881 [info] PullRequestTree> Review threads have changed, refreshing Files node
2023-06-30 14:12:25.881 [info] PullRequestTree> Review threads have changed, refreshing Commits node
2023-06-30 14:12:25.883 [info] PullRequestTree> Getting children for Files node
2023-06-30 14:12:25.883 [info] PullRequestTree> Got all children for Files node

Extension version: 0.66.2
VS Code version: Code 1.79.2 (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:59:55.818Z)
OS version: Linux x64 6.3.4-201.fc38.x86_64
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 2404)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
3, 13, 10

Memory (System)
62.44GB (25.05GB free)

Process Argv
--unity-launch --crash-reporter-id d33a766b-28e9-45e5-942d-3a9085ddc0c0

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30776702
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30610678
282f8724:30602487
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
2i9eh265:30646982
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
hideindicator:30766889
pythongtdpath:30769146
i26e3531:30780429
pythonnosmt12:30779714
pythonidxptcf:30772540
pythonnoceb:30776495

@brianjmurrell thanks for including logs!
It looks like the workspace you have open actually has two GitHub repositories and both of those repositories have PRs open from the branch that you have checked out, respectively:

For repo A, you have PR #384 checked out
For repo B, you have PR #12561 checked out

The sidebar view that you are describing with the comment box and the reviewers does not have much space, so we only show it when you have only 1 PR checked out. You can get the same functionality that's in that view from the PR description.

Using the same branch name shouldn't make any difference at all. It's the fact that you are using a multi-repo workspace and you have a PR checked out in each repo.
You can get the same functionality that's available in the sidebar from the PR description.

Could the sidebar view have expanders for the checked out PRs in the same was as the source view, and many other views have?

Yes we could do something like this. I can re-open this issue and re-purpose it as a feature request for this. However, I think users do not often have:

a multi-repo workspace
a PR checked out in more than one repo
so such a feature request is not very high priority.

Can I "un"-checkout a PR in one of the repos?

@brianjmurrell to un-checkout a PR you can checkout a branch that doesn't have a PR created from it, usually your default branch is what you'd use.
If you're already on your default branch, meaning that you have a PR from your default branch to another branch, then you can add your default branch to the exclude setting. For example:
"githubPullRequests.ignoredPullRequestBranches": [
  "main"
]

Finally, if you don't want to ignore all PRs on this branch, but you do want to ignore all closed PRs, you could set:
	"githubPullRequests.useReviewMode": {
		"closed": false,
		"merged": false
	},

Could the sidebar view have expanders for the checked out PRs in the same was as the source view, and many other views have?

Yes we could do something like this. I can re-open this issue and re-purpose it as a feature request for this. However, I think users do not often have:

a multi-repo workspace
a PR checked out in more than one repo

so such a feature request is not very high priority.

We also have the multi-repo workspace (~80 repos) and the extension notify me due to rate limiting and then crash. It would be nice to select which repository should be currently fetched as in the Source Control View :)
Should I create a new feature request ticket for that or this ticket fits well?

extension notify me due to rate limiting and then crash.

This is a separate issue. Please do open a new issue for it and add share the exact error you're getting!

Closing as out of scope since we don't plan to address this.


http3: support HTTP CONNECT and CONNECT-UDP (masque) protocols

This commit makes changes to the HTTP3 stack so that HTTP CONNECT and CONNECT-UDP requests will not fail due to internal checks. Also, it modifies the HTTP3 setting frame code to reflect the up-to-date setting for HTTP3 datagram over QUIC datagram. Finally, it adds two examples to run proxies TCP and UDP connections via HTTP3.

Do you have the server-side implementation for this as well?