fix: resolution-qa-task-61

Issue
This pull request refers to Issue #

[ ] Does not apply to this pull request

Description
Correction of the response to a mismatched code in account recovery.
Types of changes

[ ] New feature (non-breaking change which adds functionality).
[x] Bug fix (non-breaking change which fixes an issue).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

What changed:

[x] UI
[ ] Business rule
[ ] Documentation
[ ] Gradle or Build
[ ] Navigation
[ ] Tests
[ ] Resource files
[ ] Project architecture
[ ] Code style

Checklist

[x] Have tested the changes.
[x] Met all the acceptance requirements of this task.
[x] Verified if branch is up-to-date with develop (if not - rebase it or merge it).
[x] Resolve git conflicts

If any of the acceptance criteria are not met, please explain why below
What is the criteria? Why it is different?

@edijaniosouza Aprova ai patrão.


[Vote to make it open-source] Object pools

Avoid transfering large objects or even non-serializable objects (e.g. with a mutex) between Rust and Dart. Instead, let it always live in Rust, and Dart only gets an integer as a handle.
Remark: I have written and used it internally in my project (in production environment). If you need to use it, I can make it open-source.

If #243 is done, this is no longer needed

bump since it is #242's dependency


No camera detected

I have this strange problem, where there is no camera detected.
The System is a Ubuntu Server 22.04, running in a proxmox privileged LCX. The instance Does work properly, and I can print, but when trying to add a camera it will not be detected.
One cam has this output of usb-devices

T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 13 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1b3f ProdID=2247 Rev=01.00
S:  Manufacturer=GENERAL
S:  Product=GENERAL WEBCAM
C:  #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=32ms
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
I:  If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I:  If#= 3 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio

the second this one:

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 14 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=328f ProdID=2015 Rev=06.11
S:  Manufacturer=eMeet-200611
S:  Product=eMeet Nova
C:  #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
E:  Ad=87(I) Atr=03(Int.) MxPS=  16 Ivl=16ms
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
I:  If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I:  If#= 3 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio

Thanks for haveing a look

When I briefly looked at LCX I came across issues with integrating with peripherals (though I think that was mainly on making udev rules).
Two things to do:
1.Make sure you are plugging the camera in when it tells you to (verify it is unplugged, y, plug in camera)

You can see what dmesg sees for your camera: sudo dmesg -C plug in camera, sudo dmesg

As long as u use a privileged container it should actually work fine, but there are risks in doing that...
Sure, the first is for the generic the second for the nova..

[88579.865005] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[88580.014213] usb 1-2: config 1 interface 0 altsetting 0 endpoint 0x83 has an i                                          nvalid bInterval 32, changing to 9
[88580.014520] usb 1-2: New USB device found, idVendor=1b3f, idProduct=2247, bcd                                          Device= 1.00
[88580.014528] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[88580.014533] usb 1-2: Product: GENERAL WEBCAM
[88580.014536] usb 1-2: Manufacturer: GENERAL
[88580.015775] usb 1-2: Found UVC 1.00 device GENERAL WEBCAM (1b3f:2247)
[88580.018715] usb 1-2: UVC non compliance - GET_DEF(PROBE) not supported. Enabl                                          ing workaround.
[88580.028609] usb 1-2: Warning! Unlikely big volume range (=5120), cval->res is                                           probably wrong.
[88580.028626] usb 1-2: [5] FU [Mic Capture Volume] ch = 1, val = 7680/12800/1

and

[88695.601491] usb 1-2: new high-speed USB device number 11 using xhci_hcd
[88696.051485] usb 1-2: New USB device found, idVendor=328f, idProduct=2015, bcdDevice= 6.11
[88696.051504] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[88696.051508] usb 1-2: Product: eMeet Nova
[88696.051530] usb 1-2: Manufacturer: eMeet-200611
[88696.274223] usb 1-2: Found UVC 1.00 device eMeet Nova (328f:2015)
[88696.371797] usb 1-2: Warning! Unlikely big volume range (=2816), cval->res is probably wrong.
[88696.371829] usb 1-2: [5] FU [Mic Capture Volume] ch = 1, val = 0/2816/1

Thanks

The cameras are not providing any of the 3 pieces of information that octoprint_deploy uses for auto detection, it would seem. It will identify the serial number, if available, the USB port, or the by-id address. Not sure why that is the case. Might be related to LCX, or might just be the cameras themselves.

Perfect!
So cameras generally might not work wit Proxmox LCX.


Free PLP token early when processing bulk load requests 3x

Description
Backport of #2463 to 3x.
Issues Resolved
#2462
Test Scenarios Covered
No functional changes, no new tests.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Signed-off-by: Alex Kasko<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 11 (0.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 72.933%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdsbulkload.c
0
11
0.0%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdscomm.c
3
73.42%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
41191

Relevant Lines:
56478

💛  - Coveralls


Refactor duplicated order-by code

Refactor duplicated code for parsing query parameters for search ordering. Also adds unit tests.
This will pay off if/when we add more search pages (e.g. searching for an organization's repos)

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5b30964). Click here to learn what that means.
The diff coverage is 58.92%.

@@            Coverage Diff            @@
##             master    #3116   +/-   ##
=========================================
  Coverage          ?   34.86%
=========================================
  Files             ?      274
  Lines             ?    40057
  Branches          ?        0
=========================================
  Hits              ?    13966
  Misses            ?    24094
  Partials          ?     1997

Impacted Files
Coverage Δ

models/user.go
40.45% <0%> (ø)

routers/user/home.go
40.77% <0%> (ø)

models/repo.go
41.36% <100%> (ø)

models/issue_indexer.go
67.1% <100%> (ø)

models/star.go
53.24% <100%> (ø)

models/repo_indexer.go
49.51% <100%> (ø)

routers/home.go
75.78% <100%> (ø)

models/repo_list.go
55.27% <23.07%> (ø)

routers/api/v1/user/repo.go
52.94% <50%> (ø)

routers/utils/utils.go
78% <75.55%> (ø)

... and 1 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 5b30964...7158f6e. Read the comment docs.

@lafriks @lunny Friendly ping

@ethantkoenig friendly pong :) I'm waiting on lunny to approve and then I will review again


Not working with jquery 3.5.0

Not working with jquery 3.5.0

hasOwnProperty is not a function in https://github.com/snapappointments/bootstrap-select/blob/109277978739609110543af7c70cab9ee7d22129/js/bootstrap-select.js#L3083

hasOwnProperty is not a function
https://github.com/snapappointments/bootstrap-select/blob/109277978739609110543af7c70cab9ee7d22129/js/bootstrap-select.js#L3083

@mksmanish79 #2430

@mksmanish79 Please, next time, at least look at the top 5 issues before creating a new issue.


if a setting is required but also ADMIN_WRITEABLE it should be optional in terraform

Add logic here to only count a var "required" if it is not "ADMIN_WRITEABLE" as defined in env-var-docs.json

https://github.com/civiform/cloud-deploy-infra/pull/216


Creating deleting clusters

Addresses https://www.pivotaltracker.com/story/show/163532437.

Thanks @lparis!


Identify best approach for incorporating protected lands data

A few questions/challenges to be addressed:

[ ] Which protected lands categories are we interested in?
[ ] How will we store protected lands data (may be too large for GitHub)?
[ ] How do we decide future areas to consider (minimum number of species)?

Worked on this a bunch in several commits, but mostly this one: 9df52c7. Tough to get PA data for all of North America (and not just one country/state). Best option looked like the data set from CEC (which is based on the PAD database from USGS and similar datasets in Mexico, Canada). I used all the areas that were classified as PAs by the IUCN (categories Ia/Ib - VI), which correspond to GAP status codes 1 and 2. It's a massive dataset, that you can visualize by clicking on the "Map Viewer" button on the CEC website above.
Not sure about storing this dataset. I have the original shapefile zipped on our GoogleDrive folder. For now, there's a section at the top of the protected-areas.R script where you take that unzipped shapefile and process it a bit. I then saved the new shapefile on my computer since it's too big for GitHub. We'll need to figure out where to store this moving forward.
The rest of the protected-areas.R script, calculates the proportion of each insects' distribution (for each climate scenario and type of distribution [overlap with at least one host plant or areas that are climatically suitable for the insect, regardless of host plant suitabilities]) that falls in a protected area. This took a bunch of fussing as R kept crashing when I tried to crop spatial data and/or do extraction calculations with terra.  I got things to work eventually with the exactextractr package, though it does take a long time to run (few hours for all species, distributions). The script produces a csv with summary statistics (output/summary-stats/protected-areas-allspp.csv), which is under version control so you should be able to look at it. You'll see that the proportions of areas protected are pretty low, but I think that's because of the fairly strict IUCN categories.

For storage, three options (listed in relative order of preference):

ReDATA. Creates DOI and API allows fairly easy retrieval of compressed files.
Zenodo. Creates DOI, maybe be relatively easy to use API.
Google Drive. Least amount of metadata & curation, but technically not an "archive".

@jcoliver will look at ReDATA submission as option.

@ezylstra For exploring how the proportion of range in protected areas changes, there is a start at src/summary/plot-protected-proportion.R.

I edited the script that Jeff started to plot changes in protected area coverage over time in beccac4.
I also added a new script that will calculate protected area coverage for swallowtail diversity "hotspots" (with options to define hotspots by varying the minimum number of species present) in 1d2e14e.
Finally, I downloaded the shapefile with "other" protected areas that don't have an IUCN classification and generally fall into GAP status 3 or 4 if in the US. This shapefile is even bigger than the file with IUCN-classified areas, so I haven't done anything more with this dataset.

With categorization of areas into four groups (National, State, Local, and Private), the current version of the shapefile lives on Google Drive. ReDATA is probably the the way to go for longer term storage.


Source of Text Prompts

Hi, great work and great project! 👍
I am interested in how you curated the text prompts for the recordings in your dataset. For example, from where did you source the prompts? Did you collect prompts from multiple domains? Did you select all the prompts you found in a source, a random subset, or did you filter some out in a pre-processing step?
Thanks for any hints! Much appreciated.

Hi, thanks for your nice feedback 😊.
I've taken most phrases from Mozilla Common Voice (Sentence Collector). I hope this helps you.


Create Deploy top level method

Creates deploy top level method for normal and async
Change to_k8s_yaml to manifest
Change remote to predict
Update notebooks and docs

Keeps existing Runtimes as is. Future PR can simply the options and remove unnecessary code.

Just to provide more specific thoughts, the top level deploy is good, the rename k8s to manifest as well, and remote to predict makes sense, only thing that woudl be good to dive into further is the update to SeldonCoreOptions and KFServingOptions instead of having a top level KubernetesOptions or DockerOptions instead with the sc/kfs as a field (instead of the other way around)

lgtm - merging


numpy not listed as a dependency in setup.py

PIP installed kachery into a clean venv environment, attempted to run sample code, and encountered the error below.  Resolved the problem by installing numpy.  Recommend adding numpy to install_requires section of setup.py.
(kachery) ~ $ kachery-store test.py Traceback (most recent call last):   File "/home/rogerhurwitz/venv/kachery/bin/kachery-store", line 7, in <module>     import kachery as ka   File "/home/rogerhurwitz/venv/kachery/lib/python3.8/site-packages/kachery/__init__.py", line 1, in <module>     from .core import set_config, get_config   File "/home/rogerhurwitz/venv/kachery/lib/python3.8/site-packages/kachery/core.py", line 2, in <module>     import numpy as np ModuleNotFoundError: No module named 'numpy'

Thanks @rogerhurwitz  for the report. The reason I left it out is that numpy is a unique package in that some users have a special installation of numpy on their system outside of a virtual environment. Therefore, I am going to add a line in the README explaining that it should be installed ahead of time.


add decimal support

this pull request add decimal floating point support.
without decimal support, 0.1 is not 0.1 as it looks. people from non-C world tend to use decimal directly in their json exchange data, if we don't support decimal, then we lose precision.

Hm, this probably makes more sense as a fork than part of mainline json11. Adding a dependency on boost isn't an option for many users.

I agree with @j4cbo.  I think there's an interesting discussion to be had about possible features to preserve accuracy of decimals (beyond what a double provides), and the trade-offs of complexity vs. correctness.  However, doing so by adding a boost dependency, and apparently turning on exceptions and RTTI if the CMake file is to be believed, would put a burden on many potential users of the library (including Dropbox, which doesn't currently link Boost in our mobile apps), so I think it would be better served as a fork.  Simplicity in implementation and dependencies is one of the goals of this library (as per the opening sentence of the readme: "json11 is a tiny JSON library for C++11").
The license does allow for forks and modifications, though, so have at it.  I'm glad you're finding json11 useful, and thanks for contributing.


Create documentation on registering a data source

Data sources must be registered in the Postgres backbone.data_source table to be used within this framework. Registering can be a confusing, complex task depending on the complexity of the source dataset.
This documentation should probably be created as a vignette in the R package.
This documentation should give a thorough explanation of each column in the data source (geom_spec in particular) and walk a potential user through the process of creating a row in the table, updating the DDL for the backbone schema, and creating a PR for the new DDL.
Depends on

[ ] https://github.com/OHDSI/GIS/issues/276

This introduces the need for a framework for handling new data sources/ features. While a later iteration of this work will likely have an API built around the database to facilitate data source creation and persistence, for now we should have a robust method for requesting and accepting new data sources and features.

Make sure that there is a part of this documentation that addresses how to create data_sources for offline use (use of download_url is different)


[WIP] [feat] Basic IPNS support

I've found planned refactorings in GetRecords https://github.com/libp2p/rust-libp2p/pull/2712 (CC: @dignifiedquire) to make it streaming. In this PR I've supported DhtGet queries to iroh-p2p and gateway. Proposed changes take into account further possible changes in libp2p::GetRecords.
All implemented APIs return Stream<PeerRecord> but streaming is not used yet, I'm just doing usual Quorum query, wait for response and send all received records through stream. It works, but there is also a lot of unwraps() and todo!() that I'll eliminate if general approach would be reviewed and accepted here.

thank you, haven’t reviewed in detail, but high level structure looks good to me 👍

Alright, then I'll add error processing, logs and tag you afterwards

Did you mean bare performance? As far as I know, the bottleneck is inside networking and mostly in quorumed query.
In Kubo IPNS requests are ofter timeouted (60s) if records from DHT are outdated. In result, we have terrible timings and it renders IPNS almost unusable for several cases.
There are several proposals how to fix it, the most reliable approach will use aggressive caching + heuristics like using record from the source of truth as fast-track + stream of PeerRecords from Kademlia event loop that may be aborted after achieving enough records to make a good decision about IPNS value (here "enough" and "good" needed to be precisely defined later).
Kubo thread with the corresponding issue is here, it may be useful

I believe record verification is still missing: https://github.com/ipfs/specs/blob/main/ipns/IPNS.md#record-verification which we definitely need

Is this record owner optimization being considered as part of this implementation? https://github.com/ipfs/specs/issues/274

Yeah, they mention it at https://github.com/n0-computer/iroh/pull/539#issuecomment-1324082959 as "heuristics like using record from the source of truth as fast-track"

Is this record owner optimization being considered as part of this implementation? ipfs/specs#274

Yes. I'm going to finish https://github.com/n0-computer/iroh/pull/546 firstly and then will bring this PR to the end.

Hi, just a heads-up that if you are implementing things, and signatureV2 is present, focus on validating values from data CBOR in V2 records, so it is less painful to refactor when we switch to V2-only and stop duplicating values.
Wrote initial cleanup plan in  https://github.com/ipfs/specs/issues/376.


Security - Two Factor authentication - Copy button not change for Copied after pressing on it

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the App
Login with any account
Go to Settings -> Security -> Two-factor authentication
Press on Copy codes/Download -> Next
Press Copy

Expected Result:
Copy/Download buttons changed for Copied/Downloaded after pressing on it
Actual Result:
Copy/Download buttons did not change for copied after pressing on it
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://platform.applause.com/services/links/v1/external/40439021d04d2d1140a4f6366c2ba20adef7e832b06171961d330d8fd3f8f077
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

I think it will be handled here

I'm gonna close this GH as it should be fixed via this ☝


fix(semantic-tokens): limit comments range

Client requests textDocument/semanticTokens/range service with a range
parameter in order to get the tokens of the visible window, but server
return the additional comments highlighting tokens may be out of range,
we should keep the tokens requested by the client in range.

Please add description.

Sorry, I have added the description in this PR and inside the commit msg.

Thanks


Refactor ModalProvider to remove wrapper div and apply theme props directly

Refactor ModalProvider to remove wrapper div and apply theme props directly
This PR refactors the ModalProvider component to remove the unnecessary wrapper div and apply theme properties directly to its children. This change allows for more flexible use of the ModalProvider throughout the component tree.
Key changes:

Removed the wrapper div from ModalProvider
Used React.Fragment to avoid adding extra DOM elements
Applied theme properties directly to child elements using React.Children.map
Conditionally rendered the style element only when a theme is provided

This refactor improves the flexibility of the ModalProvider, allowing it to be used at any point in the component tree without introducing additional DOM nesting. It maintains all existing theming functionality while providing a cleaner, more efficient implementation.
Testing:

Verified that the ModalProvider works correctly with and without a theme
Ensured that theme properties are correctly applied to child components
Checked that the component renders correctly in different contexts without introducing unexpected DOM elements

Please review and test thoroughly to ensure this change doesn't introduce any unintended side effects in existing implementations.
Fixes https://github.com/rainbow-me/rainbowkit/issues/2164

At this time, we don't need any refactors. If you're interested in contributing, feel free to investigate our open Issues and submit fixes, if necessary.

At this time, we don't need any refactors. If you're interested in contributing, feel free to investigate our open Issues and submit fixes, if necessary.

I think it was part of opened issues about DOM injection.
cc: https://github.com/rainbow-me/rainbowkit/issues/2164


Update query to only look up journal pages, fixes #10

Hi! This PR tries to address #10 by updating the query to only look for journal pages.
I have tested it locally, and it seems to be working for me. This is my first experience in Logseq plugin development, I may be missing or misunderstading something. I would appreciate it if you checked this out and gave me any feedback you can.
Thank you.

Hi! Thanks for the PR but this has already been fixed in v2.0.1.


refactor: to work with<EMAIL_ADDRESS>

ref: https://github.com/ant-design/ant-design/issues/5678

Updated.

Updated.

Changes Unknown when pulling 0810c17f47038ad174101271f1031069ea944d8a on refactor into ** on master**.

Changes Unknown when pulling 23ccb966911b24bcbdc595995d49e1b7c6c64238 on refactor into ** on master**.

CI failed 是因为 karma 无法启动浏览器，先忽略吧。这个 PR 合并后我改成 Jest

ping~


How to find a symbol master by name?

I'm trying to write a plugin that will set overrides in symbol instances in specific layer groups based on data from a JSON file.
The first problem is that overrides in a symbol instance don't have any name or label, it looks like I can only reference them by index in overrides array. I figured out that maybe I could get these names from the symbol master. However, I can't figure out how to get an existing symbol master. The API only mentions how to create one, not how to find one.

It looks like the name property can be accessed via String(this._object.overridePoint().layerName()) but the Override class did not implement the method.
https://github.com/abynim/Sketch-Headers/blob/4a95b06c0d5e620249f40583e25d3dc52e36494b/Headers/MSOverridePoint.h#L21

You can find a symbol master using document.findSymbolMaster(): http://developer.sketchapp.com/reference/api/#find-a-symbol-master.
Be careful when dealing with names because they are not unique.


Inconsistency with Electron

Electron env has require, while Monaco uses require as ADM loaded marker.
Sample: https://github.com/Microsoft/monaco-editor-samples/blob/master/sample-electron/index.html
Some more discussions: https://github.com/Microsoft/monaco-editor/issues/90

Has this been fixed yet? I have the workaround as detailed here in issue 21 working, but then I'm not using MonacoEditor!

@peteboothroyd Absolutely yes! I can add an example of using react-monaco-editor with Electron in the examples folder which includes you changes


Incorrect grammatical form in po/sv.po

The msgstr for msgid "Call a macro", i.e.  https://github.com/newsboat/newsboat/blob/f924b62b05f07585adc0c4a1d2ec6eb14132a9e6/po/sv.po#L1260 should say "Anropa ett makro". See for example the last paragraph of http://www.termado.com/DatatermSearch/?ss=makro, from the Joint Group for Swedish Computer Terminology.

Hi! You are welcome to make a pull request that fixes all the errors you found :) I don't know Swedish (and most other languages Newsboat is translated into), so I rely entirely on users like you who have the knowledge to correct everything.

@Minoru Great, I will do so during this weekend!

Cool, thank you!

Fixed by #247.


Question about overflow reg csr address

Currently, the ”ucode“ reg locates in CSR address 0x801 which may conflict with other customized regs in some implementations. Would it be more appropriate if it can be placed in a standard region similar to the F/D extension or V extension?

v0.8 release has changed the custom ucode CSR in 0x801 to a standard user read/write CSR (vxsat) in 0x009.
Thanks for the question.

In V-spec,  VS bits are used to control accessing vxsat as well as other vector-related csrs and also indicate the context switch status for vector registers.
As vxsat is used,  does it imply VS bits still exist in p-extension and have similar functions?

In P-extension, only vxsat CSR is the additional state that needs to be saved and restored on context switch. So there is no need to do lazy save/restore like vector extension.
My suggestion is that if P-extension is present, then software should always save/restore vxsat CSR.

And the OFF state of VS field should not affect the execution of the P extension instructions.


feat(linter): eslint-plugin-unicorn  switch-case-braces

Rule taken from https://github.com/web-infra-dev/oxc/issues/684.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[FormRecognizer] Cleaning up tests (1/?)

/azp run net - formrecognizer - tests

API change check
API changes are not detected in this pull request.


Bump metallb to 0.13.7 and add bgp password secret support

Issue #, if available:
Description of changes:
Bump metallb
Add passwordSecret partial support
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

https://github.com/aws/eks-anywhere-packages/issues/600


Document the distance module.

Hi there,
Here's just a bit of documentation for the distance module. I'm assuming travis will run cargo test --doc.
Cheers,
Oscar

Thank you so much! It looks like travis is running cargo test --verbose, not sure why that is not working.

@Eh2406 Got it, it was a little semicolon.


Add support for GitHub's SoftU2F

Currently when using this extension in conjunction with GitHub's SoftU2F nothing happens. Adding support for this would be a great addition so it works with Safari!

This appears to have been fixed in github/SoftU2F@d68da398ad7b5a3dfbd4b0499067fddf37b5461d.  The extension now works correctly with SoftU2F.

Seems to be working now! Now only if GitHub would allow me to authenticate my login with SoftU2F in Safari...

Works for me, but for some reason I had to visit the page to set it up twice: the first time it told me my browser didn't support U2F, the second time it worked fine.
It would be really nice if this extension could go in the Safari extensions store, but unfortunately the license currently prevents that (it's actually not 100% clear whether it's legal for GitHub to distribute it at all with the current license).


Cannot start server

I'm trying to start this server so I can mark the associated listing as tested.
Current Behavior
This is my Dockerfile:
FROM python:3.13

RUN pip install uv

WORKDIR /app

RUN git clone https://github.com/iskakaushik/mcp-clickhouse .

WORKDIR /app/

RUN uv sync

CMD ["uv", "run", "mcp-clickhouse"]

When I run it, I get the following error:
error: Failed to spawn: `mcp-clickhouse`
  Caused by: No such file or directory (os error 2)

Expected Behavior
The server should start correctly when using uv run.
Suggested Improvement
Could you provide a complete example in the README showing how to start the server using uv run?
This would improve usability for developers and help automated systems like Glama to test the server

this should be fixed now, could you try rerunning?

I added some automated tests as well.

Can confirm it is working. Thank you!


ciao-cli cannot list network nodes

We should add an option to ciao-cli node list to include any network nodes even if they aren't running any cncis.

https://github.com/01org/ciao/pull/1297 should have fixed this


Roll engine 63b253d907b9..2d6499c50e34 (1 commits)

git@github.com:flutter/engine.git/compare/63b253d907b9...2d6499c50e34
git log 63b253d907b9..2d6499c50e34 --no-merges --oneline
2019-08-03<EMAIL_ADDRESS>Roll fuchsia/sdk/core/mac-amd64 from Mzwf3... to c8UZM... (flutter/engine#10618)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (franciscojma@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Error test cases in godwoken-tests

timeout actions

[ ] https://github.com/Flouse/godwoken/runs/3721851298?check_suite_focus=true#step:14:40

[ ] Running transaction: Deploy Create2
err Error: processing response error (body="{"jsonrpc":"2.0","id":53,"error":{"code":-32001,"message":"invalid nonce of account 4 expected 0, actual 9"}}", error={"code":-32001}, requestBody="{"method":"poly_submitL2Transaction","params":""]
https://github.com/Flouse/godwoken/runs/3917567216

outdated


Reorganize ObjC tests

This PR reorganizes gRPC ObjC tests into 4 categories:

Unit tests
Interop tests
Cronet tests
Mac tests

Similar original test suites are combined into as few targets as possible to avoid repeated builds.

Interop Cloud-to-Cloud Tests - #18967
Interop Cloud-to-Prod Tests - #18967


[VK.com] "ERROR: Unable to login, incorrect username and/or password" (My username and password is correct)

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.07.29. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.07.29

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
C:\Users\G>youtube-dl -v -u vk_mycorrectvkusername -p vk_mycorrectvkpassword -vg "https://vk.com/video?q=skrillex%20fuji&z=video-24363586_456239555"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-u', 'PRIVATE', '-p', 'PRIVATE', '-vg', 'https://vk.com/video?q=skrillex%20fuji&z=video-24363586_456239555']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2018.07.29
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: ffmpeg N-91398-gd08d4a8c73, ffprobe N-91398-gd08d4a8c73
[debug] Proxy map: {}
ERROR: Unable to login, incorrect username and/or password
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp4sw50z9e\build\youtube_dl\YoutubeDL.py", line 792, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp4sw50z9e\build\youtube_dl\extractor\common.py", line 501, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp4sw50z9e\build\youtube_dl\extractor\common.py", line 405, in initialize
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp4sw50z9e\build\youtube_dl\extractor\vk.py", line 80, in _real_initialize
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp4sw50z9e\build\youtube_dl\extractor\vk.py", line 77, in _login
youtube_dl.utils.ExtractorError: Unable to login, incorrect username and/or password
<end of log>

Description of your issue, suggested solution and other information
So ive been trying to download a private video from VK and ive followed this thread: https://github.com/rg3/youtube-dl/issues/2206
however, every time i use my CORRECT username and password, it keeps saying my username and password is incorrect.

Obviously you input it incorrectly.
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'https://vk.com/video?q=skrillex%20fuji&z=video-24363586_456239555', u'-u', u'PRIVATE', u'-p', u'PRIVATE', u'-v']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2018.07.29
[debug] Git HEAD: 0fa6860
[debug] Python version 2.7.12 (CPython) - Windows-10-10.0.10240
[debug] exe versions: ffmpeg N-85653-gb4330a0, ffprobe N-85653-gb4330a0, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[vk] Downloading login page
[vk] Logging in
[vk] -24363586_456239555: Downloading webpage
[vk] -24363586_456239555: Downloading m3u8 information
[debug] Default format spec: bestvideo+bestaudio/best
...
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 955
[download] Destination: Skrillex - Live @ Fuji Rock Festival, Japan 2018-456239555.mp4
[download]   0.6% of ~1.88GiB at  4.96MiB/s ETA 01:29
ERROR: Interrupted by user

The authentication algorithm on the site vk.com changed. Now on the start page in the input form you need to specify only the login, after clicking on the button in the next form you need to enter only the password. Please correct the authentication for vk.com in your module vk.py

The authentication algorithm on the site vk.com changed. Now on the start page in the input form you need to specify only the login, after clicking on the button in the next form you need to enter only the password. Please correct the authentication for vk.com in your module vk.py

I agree


Level-Creation Framework

Implement level one. The code for level one which will be used to create all other levels.
Suggestions:

Create a new file for each level (i.e. level1.py, level2.py)

Or, place all levels into one file

Need Player class, AI class, and perhaps a Level class.

Once it is created, it needs to be called upon a player pressing the "Start" button.

I have created level one which can be used as the level framework.
I don't know if it's best to have a separate class for each level then have a level caller function, or just to add each instance of the levels into the main class App.
It might be better to do the former choice as it saves on code in the class App in main.py. I will attempt to implement it first and if it doesn't work, I will try the latter choice.

I decided to go with a class instance for every level. Each level after level one inherits attributes from the first level. The level instances are initiated in the init of class App and are called upon in the main game loop.
When a player completes a level, a level counter goes up by one. Once the player presses the "Start" button again, if/elif statements check to see what level to call.
This might not be the best way to implement the levels, but it works.


FIX-#3619: Fix ValueError when doing loc on empty dataframe

Signed-off-by: Naren Krishna<EMAIL_ADDRESS>
What do these changes do?

[x] commit message follows format outlined here
[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #3619
[ ] tests added and passing
[x] module layout described at docs/developer/architecture.rst is up-to-date

do the loc/iloc assignments perform correctly on empty frames, or we should default to pandas on __setitem__ as well?

@dchigarev Can you re-run the TeamCity Dask test? I believe it's a flake.

@dchigarev Can you re-run the TeamCity Dask test? I believe it's a flake.

done, now it's a green

@dchigarev Added tests for loc and iloc assignments on empty dataframes. Those seem to work without any code changes on my end. @devin-petersohn iloc actually seems to work for the get and set without any code changes.

iloc actually seems to work for the get and set without any code changes, so the only change necessary is for the loc get method.

BTW, the actual problem of why the reported bug occurs is the following way of computing a column lookup for .loc, for empty columns and slice(None) indexer it returns an empty list:
https://github.com/modin-project/modin/blob/41213581b974760928ed36f05c479937dcdfea55/modin/pandas/indexing.py#L698-L701
Pandas backend is failing to process [] instead of a slice(None) since for non-full-axis grabs it tries to do some partitioning stuff under an empty frame and fails.
It's actually pretty lucky, that the scenario from reproducer works well for the .iloc because the only difference from the .loc flow is the _compute_lookup, that suddenly returns a slice(None) indexer for an empty frame and full-axis grab, which is acceptable for pandas backend since it doesn't touch partitioning on a slice(None) indexer:
https://github.com/modin-project/modin/blob/41213581b974760928ed36f05c479937dcdfea55/modin/pandas/indexing.py#L817-L826
So, actually, the reason why iloc.__getitem__ on an empty frame is working is based on two inconsistencies:

iloc's _compute_lookup suddenly returns a slice(None) on an empty frame, instead of a [].
pandas backend suddenly doesn't fail on receiving slice(None) indexer for an empty frame.

I'm actually working on aligning these inconsistencies in #3520 and #3513, but since they aren't merged, this all looks kinda unsafe. We actually don't know how other backends would behave on an attempt to index an empty frame since there is no essential implementation for an empty core modin frame.
Maybe we should bring some safety and consistency in this PR by defaulting to pandas for both: loc and iloc? What do you think?

iloc actually seems to work for the get and set without any code changes, so the only change necessary is for the loc get method.

BTW, the actual problem of why the reported bug occurs is the following way of computing a column lookup for .loc, for empty columns and slice(None) indexer it returns an empty list:
https://github.com/modin-project/modin/blob/41213581b974760928ed36f05c479937dcdfea55/modin/pandas/indexing.py#L698-L701
Pandas backend is failing to process [] instead of a slice(None) since for non-full-axis grabs it tries to do some partitioning stuff under an empty frame and fails.
It's actually pretty lucky, that the scenario from reproducer works well for the .iloc because the only difference from the .loc flow is the _compute_lookup, that suddenly returns a slice(None) indexer for an empty frame and full-axis grab, which is acceptable for pandas backend since it doesn't touch partitioning on a slice(None) indexer:
https://github.com/modin-project/modin/blob/41213581b974760928ed36f05c479937dcdfea55/modin/pandas/indexing.py#L817-L826
So, actually, the reason why iloc.__getitem__ on an empty frame is working is based on two inconsistencies:

iloc's _compute_lookup suddenly returns a slice(None) on an empty frame, instead of a [].
pandas backend suddenly doesn't fail on receiving slice(None) indexer for an empty frame.

I'm actually working on aligning these inconsistencies in #3520 and #3513, but since they aren't merged, this all looks kinda unsafe. We actually don't know how other backends would behave on an attempt to index an empty frame since there is no essential implementation for an empty core modin frame.
Maybe we should bring some safety and consistency in this PR by defaulting to pandas for both: loc and iloc? What do you think?
Sorry, for probably being too picky for a small-change PR, I would also be okay with the "if it works, don't touch it" approach 😄

I was wondering about this myself, thanks for the explanation! Let me make that change -- I think it would be better stability-wise :)


Updated collection item component to use <li tag instead of div for accessibility

fixes issue https://github.com/appitierre/bloomPlatform/issues/1908

+1


upgrade to latest version of the packages

The advantages are:

less security issues with the image
the local diffdisk size will be now smaller (as basedisk will have the package updates)

Thanks


Set permissions for Get Involved views

Fixes #2493. Requires #2492 to be merged first.

@pbanaszkiewicz I implemented your suggestions, thank you! Ready for a re-review.
Note that 83dc220 is a refactoring commit that combines the Test...View and Test...ViewPermissions classes for each view to clean things up, so you might prefer to look at the other commits separately to that one to understand all the changes.


Add support of CH390H both in esp_eth and its examples . Latest PR! (IDFGH-12264)

Due to my lack of experience with PRs, I mistakenly submitted the master branch directly to the PR, which directly caused the pre-commit to fail. The PR session was submitted by the new branch.
Legacy session: #13306

https://github.com/espressif/esp-eth-drivers/pull/23


thoughts on ollama or other open source llm integration

hey - we're starting to use BPMN Assistant to generate models for - https://lexipedia.xyz/ = I'd like to add an ollama llm integration point = could you help advise on how best to approach that?  we have 4 data science masters students and i want to get them testing new process extraction ideas and see how they fit in =
thank you for considering!

Hey, that's very cool! I think the Ollama integration idea is a good one and something I’d definitely do if I had the time, but right now I’m tied up with other things. Maybe I’ll have some time to look into it soon. Feel free to tag me if you run into specific questions, and I’ll try to assist when I can.
Thanks!

right on - looks like the main thing is getting ollama's functionality in the provider_impl directory and then updating the configs
i'm basing the new product on openai since there should be reasonable compatability there?  the ollama library in python includes some chat functions too...

Added Llama 3.3 70B, Qwen 2.5 72B and QwQ 32B, provided by Fireworks AI. Running these models locally would probably not be feasible for most users, so I’m not planning to add Ollama at this time. Open to exploring it further if the need arises.


Add pandas Extension to support df.to_datatable

Pandas has an extension functionality which can allow us to register functions to dataframes.
This would allow a user to do dataframe.to_datatable
Pandas Doc Link

#483 addresses this. Closing


The disableVerticalSwipe method cannot be used

Telegram Application
Telegram for Android, Telegram for iOS, Telegram Desktop, Telegram Web A, Telegram Web K
Describe the Bug
When I try to use the new disableVerticalSwipe method, I get an error
To Reproduce
I have added a new method disableVerticalSwipe. But when I log into the web version of telegram in my mini application, I get an error: Changing swipes behavior is not supported in version 7.6.
Expected Behavior
The mini application should not collapse when swiping vertically inside the application

Telegram applications are not supporting this method still

Ah I was just looking for this thanks for the confirmation @heyqbnk


Add Intrinsic and Extrinsic CSS values

This is fairly green with prefixes here (Caniuse). I think it would be helpful to add to the list, although I can't seem to find a polyfill for it anywhere.

@silenceisgolden You're still interested?

@arthurvr totally forgot. Go for it if you want!


CAMEL-12834: Fix failing CDI tests

Test were failed because they run with different maven profiles: weld-1.0, weld-1.2, weld-2.0.
Different versions of WELD have different exception messages.
Failing tests:

UriWithWrongContextTest - removed unnesesary checks, checking only error code and injection point
UnsatisfiedContextForEndpointInjectTest - fixed by adding cause exception message at ExpectedDeploymentException

Thanks!


Add trailingDelta to order params

According to Binance API docs, it seems trailingDelta is missing from NewSpotOrderParams.
I propose adding it, as well as changing the case for NewOCOParams to trailingDelta for consistency.
@tiagosiebler

Fixed already thanjs to your PR #347, closing this


Examples shown in docs will result in "ctx declared but not used"

Describe the bug
Take the most basic example, to validate an API key: https://github.com/DataDog/datadog-api-client-go/blob/master/api/v1/datadog/docs/AuthenticationApi.md#example
ctx is not used and will result in error ctx declared but not used.
I can guess that ctx is supposed to be used in place of context.Background() but is this really good documentation, for every single example in this repo and on docs.datadoghq.com/api/v1?
Expected behavior
Example that is ready to be copy, pasted and work without error 🙂

Hi, this has been fixed in your repo, should be pushed to the doc website shortly. Thanks.


Supervise Existing Policies Before Validating New Deployments

Currently, Admitik validates or modifies Kubernetes resources based on conditions defined through Helm templates. However, we need to extend functionality to ensure policies are audited and supervised on already deployed resources before validating any new deployments.
Requirements:

Develop a feature to allow Admitik to audit and evaluate policies on existing resources within the Kubernetes cluster.
Ensure this audit happens prior to validating new resources to maintain consistency and compliance across the environment.
Provide detailed reports or logs highlighting policy compliance status, including any violations or improvement areas.

This enhancement will enable more proactive and comprehensive policy management across both existing and future resources in the cluster.

Hi there!
How are your expectations on this feature? (the expected behavior, etc)
Currently, the ClusterAdmissionPolicy supports two modes: Enforce and Permissive, and for each captured watched resource, it triggers a request against a webserver that process the conditions, and decides if it's accepted or not to enter
During the conditions evaluation, several useful things are injected, such as .object or .oldObject (in case of updates), so this allows you to compare it against even the rest of all the resources of the same kind.
Let's talk about your request. From my POV, if it needs to run in the background periodically or so, we can not inject mentioned objects, as they don't exist. That being said, we could inject the .sources in the same way, so you should iterate on them, and perform actions to have such a report, or similar as an output.
May be it should be a different resource, something as ClusterPeriodicReviewPolicy or something similar.
It that what you expect or covering your needs? what is the use case you detected?


Consider supporting SPARQL 1.1 Update

A useful feature in tarql can be support of SPARQL 1.1 Update. Currently, tarql is limited to (a series of) CONSTRUCT queries. Supporting SPARQL 1.1 Update would open many useful ways of processing data. An example use case that I'm considering is producing data in multiple named graphs, which is currently not possible with CONSTRUCT queries.
The output could be serialized to any standard serialization of RDF quads, possibly N-Quads to allow streaming serialization.
If support of the complete SPARQL 1.1 Update would introduce too much complexity to tarql, supporting only (a series of) INSERT operations would still deliver a lot of value.

Updating a graph is useful in pipelines that need to update data.
However, tarql cannot join CSV data to real data in a repo, and N-Quads cannot carry DELETE statements.
So I think you mean only INSERT: or @jindrichmynarz do you have an example with graph update?

Jena supports GRAPH in CONSTRUCT. So it may be easier to implement #98.
As a workaround, one can save turtle, then can use the SPARQL Graph Store Protocol to overwrite the respective graph

Yes, I meant only INSERT statements. CONSTRUCT GRAPH statements would work the same.


Updating package references changes the order of packages in the csproj file

Updating package references in a csproj file can changes the order of the referenced projects which in turn can lead to merge conflicts and additional line noise. For example:
<ItemGroup>
  <PackageReference Include="A" />
  <PackageReference Include="B" />

  <!-- a comment -->
  <PackageReference Include="ThePackageToUpgrade" />
</ItemGroup>

will result in:
<ItemGroup>
  <PackageReference Include="A" />
  <PackageReference Include="B" />
  <PackageReference Include="ThePackageToUpgrade" />

  <!-- a comment -->
</ItemGroup>

I believe this is a side effect of removing the package reference and re-adding it (in DotNetUpdatePackageCommand). I think you should be able to use add to update if the version is specified, however I'm not an expert on doing this programatically.
Let me know if you need any more info.

That would be neat, there's a problem, though. While this works for dotnetcore projects, currently it breaks .NET classic projects that use <PackageReference/> syntax. For those, not running the dotnet remove step results in the reference being installed twice. Test that catches this: https://github.com/NuKeeperDotNet/NuKeeper/blob/master/NuKeeper.Integration.Tests/NuGet/Process/DotNetUpdatePackageCommandTests.cs#L92
NuKeeper would need to distinguish between those two file formats in order for this to work.

The PackageReferenceType should tell you how the reference works.

Good spot. I've forgotten that we do treat the differently. PR waiting.

Eagerly anticipating the next release so I can try it out again!

The way that the commandline options works is all changed in the next version.


Claim: Preventing tenant eviction due to false landlord claims

Description
As a user, I would like the system to see/[insert verb]+[insert object]
Scope of Work

[ ] Task 1
[ ] Task 2
[ ] Task n-1
[ ] Task n

Demo requirement

The user does x
The system does y
n. Rest of a use case of a flow chart

Acceptance Criteria

The user is able to x
The user sees y
The user hears z

Documentation, files, diagrams, etc. relating to this feature:
Url, books, etc.
Changes:

[Optional]

Blocked as we need legal resources to complete such a task

This story is highly related to #186, as the features will most probably overlap. Therefore, work on that user story should be completed prior to starting this one

We've determined that this is infeasable using statistical AI. Rather a rule-based system can solve this. Further work is needed, as well as an expert in the domain


Show make bench logs in current UI

This implements a custom docker run and read mechanism that is similar to ocurrent's Docker.pread, but logs the output in addition to returning it.
Based on: https://github.com/ocurrent/ocurrent/blob/master/plugins/docker/pread.ml
Here's an example output from a benchmark execution with this change:
2021-03-23 15:32.41: New job: "docker" "run" "--security-opt"
                     "seccomp=./aslr_seccomp.json" "--tmpfs"
                     "/dev/shm:rw,noexec,nosuid,size=4g" "--cpuset-cpus"
                     "1" "--rm" "-i"
                     "sha256:3722427047f8eaf4230c9e9465ec554c04e5fca236f03621f11f8ba1c4122bd9"
                     "make" "bench"
2021-03-23 15:32.41: Exec: "docker" "run" "--security-opt" "seccomp=./aslr_seccomp.json"
                           "--tmpfs" "/dev/shm:rw,noexec,nosuid,size=4g"
                           "--cpuset-cpus" "1" "--rm" "-i" "sha256:3722427047f8eaf4230c9e9465ec554c04e5fca236f03621f11f8ba1c4122bd9"
                           "make" "bench"
2021-03-23 15:32.44: Output:
{
  "config": {  },
  "results": [
    {
      "name": "bench_1_test_1",
      "metrics": {
        "time": 4.02,
        "ops_per_sec": 690.0,
        "mbs_per_sec": 199.0
      }
    },
    {
      "name": "bench_1_test_2",
      "metrics": {
        "time": 10.04,
        "ops_per_sec": 1455.0,
        "mbs_per_sec": 17.0
      }
    }
  ]
}
{
  "config": {  },
  "results": [
    {
      "name": "bench_2_test_1",
      "metrics": {
        "time": 0.01,
        "ops_per_sec": 50.0,
        "mbs_per_sec": 3.0
      }
    },
    {
      "name": "bench_2_test_2",
      "metrics": {
        "time": 0.07,
        "ops_per_sec": 877.0,
        "mbs_per_sec": 23.0
      }
    }
  ]
}

2021-03-23 15:32.44: Job succeeded
``

Addresses https://github.com/ocurrent/current-bench/issues/68


com.azure.storage.blob.BlobClient.download(OutputStream stream) returns exception java.lang.UnsupportedOperationException

This bug was filed from an ICM. This is a bug on our side and will be fixed for GA.

This happens when ByteBuffer streamed from the underlying Flux has a null hb, which is non-null only for heap buffers.

@vhvb1989 Role this into your PR that is adding additional tests.


Vite 5 in fragments

Closes #552

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[X] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[X] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information

Thank you


feat(health checks): implement new kubernetes 1.2 health check features

Added the following new functionalities

HEALTHCHECK_PERIOD_SECONDS - How often (in seconds) to perform the probe
HEALTHCHECK_SUCCESS_THRESHOLD - How many probe runs need to be done after failure to consider it a success again
HEALTHCHECK_FAILURE_THRESHOLD - How many times a probe should fail before considered being down

These defaults are all copied from kubernetes but may have to be adjusted due to our high default timeout, or we bring the default timeout down
Closes #251
Depends on #591 being merged first

Current coverage is 83.62%

Merging #600 into master will increase coverage by +0.26% as of cf515fd

@@            master    #600   diff @@
======================================
  Files           36      36
  Stmts         2417    2431    +14
  Branches       350     351     +1
  Methods          0       0
======================================
+ Hit           2015    2033    +18
+ Partial        116     114     -2
+ Missed         286     284     -2

Review entire Coverage Diff as of cf515fd

Powered by Codecov. Updated on successful CI builds.

Can you drop a deis/workflow issue to track adding these to the docs?

Yeah, I have https://github.com/deis/controller/issues/570 but realised just now these are not ENV Vars :P  I need to turn Health Checks into a section of the config instead of general configuration

Created https://github.com/deis/workflow/issues/134 to track documentation needs

Wrote https://github.com/deis/workflow/pull/135 for the documentation

This lgtm.
In case it helps anyone else, I asked @helgi for some additional information on what's going on here, so adding that info here in case it helps anyone else:
this PR adds the above env variables that are settable via config:set, which tell the controller how to configure app pods w.r.t. health check information. There is also a plan in #603 to move these config values to a top level config element, similar to what we do for tags.


BingMap

Thanks for contributing to the Cesium Community!
If you have a question, please search the forum:
http://cesiumjs.org/forum.html
and start a new forum thread, if needed, instead of creating this issue.
Otherwise, we look forward to your bug report or feature request in this issue.

Delete this message before clicking Submit.

Why can't BingMap load it out?

Perhaps the Bing key expired?  Check the console:

This application is using Cesium's default Bing Maps key.  Please create a new key for the application as soon as possible and prior to deployment by visiting https://www.bingmapsportal.com/, and provide your key to Cesium by setting the Cesium.BingMapsApi.defaultKey property before constructing the CesiumWidget or any other object that uses the Bing Maps API.

In the future, please post questions to the Cesium forum.  You'll get a faster response; the GitHub issues are only used for bugs and features.


CPU / Scheduler dashboard

With more and more CPU related metrics, we should introduce a new CPU dashboard, similar to the IP dashboard we already have.
As a start is can include:

CPU Utilization per (Load)
Foreground CPU Utilization
Time spent in task quota violations
See https://github.com/scylladb/scylla-grafana-monitoring/pull/332 for description and query of each

@tzach can be closed with 2fa144d466cc8db4647fb023ccf8b81e73b3e216


consolidate config in one package

right now config options (for example the api host and port) appear in various places and are affected by various sources:

CLI arguments
ENV variables
viper config files

It's not clear what config values are controlled by what source and we should try to consolidate everything into the config package and have structs for the various things that are "configured"

another example of where we need to clean up: https://github.com/filecoin-project/bacalhau/commit/84844c512c3aa2f459308b19a524613d82760cc5


change SPTP_SERVER into SMTP_SERVER

I found this small issue when checking environment variables in heroku app

:+1:

Thanks for the PR @TranDinhKhang!
This got fixed in the patch for Mattermost 3.6.0
I'm sorry it took so long to get to this PR!


Social Tree

Please update the README.md file
ther are so many images ; tried to remove them.
also there are many font file; use only  2 custom fonts


Add support for public query_vars

Ticket: https://github.com/timber/timber/issues/1249
Reviewer: @
Issue
Problem with pagination and usage of query vars
Solution
Take query_vars into account when deciding if pages need to be removed
Impact
Pagination
Considerations
I've also removed tests I added in the past when working on some other pagination issues, as one of them is in fact doing the wrong thing.
Testing
Unit tests are included.

I've faced some problems locally with some tests: testWPMLurlRemote (in test-timber-image-resize.php) is failing for me, and I can't see how that test could have ever passed. However, it seems the tests is not being executed in Travis, as GD-dependant tests are ignored.

Coverage increased (+0.003%) to 96.109% when pulling 868a00dc8b8d27c95992e144bf2d791055e555d5 on xavivars:support_public_query_vars_in_pagination into 7593ce3a30a012bfc376167ee5a701ca4eb0e3fc on timber:master.

I've identified a better way to handle this. I had to rewrite most of paginate_links, as when looking at it the current logic didn't have much sense: fragment (#) being added before the query strings, trailing/untrailingslashit after adding both fragment and query strings....
I'm making sure all tests pass now, and I'll commit the new code.

Current coverage is 95.81% (diff: 100%)

Merging #1250 into master will decrease coverage by 0.51%

@@             master      #1250   diff @@
==========================================
  Files            44         44
  Lines          3188       3157    -31
  Methods         425        422     -3
  Messages          0          0
  Branches          0          0
==========================================
- Hits           3071       3025    -46
- Misses          117        132    +15
  Partials          0          0

Powered by Codecov. Last update 7593ce3...868a00d

Coverage decreased (-0.003%) to 96.104% when pulling 246d78f2869eb2e24bf7d9a9c31992c9ba71c5a1 on xavivars:support_public_query_vars_in_pagination into 7593ce3a30a012bfc376167ee5a701ca4eb0e3fc on timber:master.

I've done another round of refactor, now changing more stuff (even some tests that, IMHO, were wrongly setup). But I'd like to leave it for a second round of review in case this one gets merged.

Coverage decreased (-0.003%) to 96.108% when pulling b6033ebbbcf7a26da6c0d20aa6df628e2fe571e8 on xavivars:support_public_query_vars_in_pagination into ca60635330cba43e2127b3bf4df4f79e56312721 on timber:master.

Coverage decreased (-0.003%) to 96.108% when pulling b6033ebbbcf7a26da6c0d20aa6df628e2fe571e8 on xavivars:support_public_query_vars_in_pagination into ca60635330cba43e2127b3bf4df4f79e56312721 on timber:master.

Coverage decreased (-0.003%) to 96.108% when pulling b6033ebbbcf7a26da6c0d20aa6df628e2fe571e8 on xavivars:support_public_query_vars_in_pagination into ca60635330cba43e2127b3bf4df4f79e56312721 on timber:master.

So much cleaner, thanks @xavivars — and tests too!!!!


Can not create backup with cinder backend

Hi,
I 'm trying to use velero-plugin-for-openstack for velero. I installed k8s in VM of Openstack Rocky. My openstack uses ceph-backend. I deployed velero include plugin from CLI:
velero install --provider "community.openstack.org/openstack" --plugins lirt/velero-plugin-for-openstack:v0.3.0 --bucket velero-bucket  --no-secret

After authentication is successful, there is error when create backup store. Seem, default plugin use swift but I only want to use cinder driver. How to get that ?
time="2021-10-25T06:58:30Z" level=info msg="Trying to authenticate against Openstack using environment variables (including application credentials) or using files ~/.config/openstack/clouds.yaml, /etc/openstack/clouds.yaml and ./clouds.yaml" cmd=/plugins/velero-plugin-swift controller=backup-sync logSource="/go/src/github.com/Lirt/velero-plugin-swift/src/utils/auth.go:50" pluginName=velero-plugin-swift
time="2021-10-25T06:58:31Z" level=info msg="Authentication successful" cmd=/plugins/velero-plugin-swift controller=backup-sync logSource="/go/src/github.com/Lirt/velero-plugin-swift/src/utils/auth.go:70" pluginName=velero-plugin-swift
time="2021-10-25T06:58:31Z" level=error msg="Error getting backup store for this location" backupLocation=default controller=backup-sync error="rpc error: code = Unknown desc = failed to create swift storage object: No suitable endpoint could be found in the service catalog." logSource="pkg/controller/backup_sync_controller.go:175"

Hope your reply soon, @Lirt

Hello @datle1
sorry for late answer.
Velero at current state must have object storage plugin to create volume snapshots. It is done like that because it needs to store metadata about the backup and then know how to restore the backup from the metadata. It is not documented very well, but you can find multiple issues in their GitHub that says the same.
Here are 2 examples where this is noted.

Velero needs an object storage where to save all resource backups and the information about snapshot backups.
https://tanzucommunityedition.io/docs/latest/package-readme-velero-1.6.3/

Velero needs two things to take a backup with snapshots - an object store plugin for storing the Velero backup metadata and a volume snapshotter plugin to take the actual snapshots.

https://github.com/vmware-tanzu/velero/issues/4287#issuecomment-956922858

Maybe for your use case it would be better to use tool like https://github.com/stashed/stash?
Or as a workaround you can install MinIO which provides object storage where backups can be stored.


Plugins can be added to Rancher after a release

The UI will allow plugins to be added into Rancher after deployment. (ie: the ability to expand Rancher without a new release.) These will be a package of Javascript and other assets. This will be packaged up into a gzipped-tar file (same as would be uploaded as an npm pacakge).
Users will be able to browse a catalog of UI plugins in the UI and install/uninstall/upgrade them.
We should add a new custom resource, something like uipkg.cattle.io - essentially a config map (we could just use config maps if that is easier) that can hold the gzipped-tar file as data. This will allow the plugin to persist across upgrades etc. Where a package is greater than 1MB, it will need to be split into multiple of these resources.
The Helm chart for a plugin would create one or more uipkg.cattle.io resources - essentially storing the gzipped-tar bundle in etcd. These would be stored in the Rancher management cluster in the cattle-system namespace (or we could use a new system namespace - cattle-ui, if that would help with separation).
The custom resource would include the following data (could be stored as annotations, if using config map) - we will refer to this as PLUGIN_METADATA.
Required:
Plugin name
Plugin version
Display name
Creation datetime

Optional:
Icon
Description
Annotations

The backend will need to serve up plugins that have been installed - this should be under the /pkg endpoint. This can just serve up a local folder contents - we'll call this PACKAGE_FOLDER.
The backend should watch for new instances of the custom resources - when any one of them is created/updated/deleted, it should fetch the list of all of the custom ui package resources and:

Create a folder in PACKAGE_FOLDER (if not already existing) for each unique name and version (joined by a hyphen) - e.g. fleet-0.1.0.
Unpack the contents of each resources into the appropriate folder (guznip and untar) - there might be multiple resources with the same name and version when the plugin is large, so these will be unpacked on top of one another.
Iterate through the folders within PACKAGE_FOLDER and remove any which no longer relate to one of the ui package resources - this will clean-up old packages that have been removed

This process will mean the backend will unpack and serve up UI plugins that are stored in the new custom resource.
Additionally, the backend should provide a new endpoint (e.g. /pkgs) which returns a JSON document listing all of the installed plugins - this should return the PLUGIN_METADATA for all of the custom resource s (de-duped so that if there are multiple resources for a single plugin, only one PLUGIN_METADATA is returned - it is assumed that all resources for a single plugin would have the same metadata).
The /pkg and /pkgs endpoints should be public, not requiring any authentication.

@PennyScissors , I was going to split this into multiple tickets, but the bullet points seem very intertwined. If you have an idea how to split this into smaller chunks, let me know.

Closing this as a duplicate of https://github.com/rancher/rancher/issues/36972


Ingest Gaia derived distances from Bailer-Jones 2021

Used the Gaia parallaxes to derive distances. We should ingest the geometric median reported in their distances catalog.
https://ui.adsabs.harvard.edu/abs/2021AJ....161..147B/abstract

@Will-Cooper , maybe we should just ingest these distances instead of Gaia parallaxes.

Parallaxes are more important in my opinion because that's the physical measurement. Calculated distances can be a separate table. Perhaps we should also point to the advice on getting distances from Gaia parallaxes?

There is also the question of parallax bias


github tests takes 10m (used to take5)

Seems the setup phase takes much longer

Running locally, the setup take around around 380s.  The time is spent primarily in

kflex init (109s)
make and create ks image (85s)
installing post create hooks ocm and ks (48s)
create wecs (37s)
wait for wecs to register with ocm (26s)

I created a PR just to test CICD timing.  Checkout https://github.com/kubestellar/kubestellar/actions/runs/8263666672/job/22605609144?pr=1892  and search for the time/dates.
The make build and image takes around 5min (!!!) with most of the time spent in make ko-build-local
if [ "$use_release" != true ]; then
    cd "${SRC_DIR}/../../.."
    pwd
    make ko-build-local
    make install-local-chart KUBE_CONTEXT=kind-kubeflex
    cd -
fi
echo "wds1 created."

The make test part of make ko-build-local is responsible for 80% of the time spent in make ko-build-local.  Removing the test part reduces the make ko-build-local time from 5min to 50sec.

Running CICD tests again today, I no longer see make ko-build-local taking 5min.  Instead it takes around 1.5min.  Here's the breakdown:
actions/setup-go: 0:14
kflex init: 1:23
create imbs1: 0:32
singleton: 0:16
make ko-build-local and image: 1:39
OCM transport: 1:31
create WECs: 0:37
Total time: 7:36 for bash, 8:54 for ginkgo.
I ran the above 5 times and got around the same numbers each time.
Conclusions:
(1) the ko-build-local was an anomaly and we don't need to fuss about it.
(2) We can shave around 5min off by pre-creating images for kind-kubeflex, OCM transport, and the WECs.

Great @effi-ofer . Maybe it's indeed server load?  (It's Sunday :-) )

For commit 5fb21f86d8e9886793f1d27e0e54c5dd96572d44 , following is a line-by-line timing of make test. You see that most of the time (36s) is in go vet ./.... Next biggest is 8 seconds to download and build setup-envtest.
mspreitz@mjs13 kubestellar % make test | while read line; do echo "$(date +%H:%M:%S)| $line"; done
13:14:43| /Users/mspreitz/go/src/github.com/kubestellar/kubestellar/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./api/..." output:crd:artifacts:config=config/crd/bases
13:14:43| cp config/crd/bases/* pkg/crd/files
13:14:43| /Users/mspreitz/go/src/github.com/kubestellar/kubestellar/bin/controller-gen object:headerFile="hack/boilerplate/boilerplate.go.txt" paths="./api/..."
13:14:44| go fmt ./...
13:14:44| go vet ./...
13:15:20| test -s /Users/mspreitz/go/src/github.com/kubestellar/kubestellar/bin/setup-envtest || GOBIN=/Users/mspreitz/go/src/github.com/kubestellar/kubestellar/bin go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest
go: downloading sigs.k8s.io/controller-runtime/tools/setup-envtest v0.0.0-20240318210927-2831a3d9e9bb
13:15:28| KUBEBUILDER_ASSETS="/Users/mspreitz/go/src/github.com/kubestellar/kubestellar/bin/k8s/1.26.1-darwin-arm64" go test ./api/... ./cmd/... ./pkg/... -coverprofile cover.out
13:15:28| ?   	github.com/kubestellar/kubestellar/api/control	[no test files]
13:15:31| ok  	github.com/kubestellar/kubestellar/api/control/v1alpha1	0.430s	coverage: 10.1% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/abstract		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/cmd/controller-manager		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/binding		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/clientset/versioned/typed/control/v1alpha1		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/clientset/versioned/typed/control/v1alpha1/fake	coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/clientset/versioned/fake		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/clientset/versioned/scheme		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/clientset/versioned		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/client		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/crd		coverage: 0.0% of statements
13:15:34| ?   	github.com/kubestellar/kubestellar/pkg/generated/informers/externalversions/internalinterfaces	[no test files]
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/informers/externalversions		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/internal		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/informers/externalversions/control		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/listers/control/v1alpha1		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/generated/informers/externalversions/control/v1alpha1		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/status		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/ocm		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/transport/filtering		coverage: 0.0% of statements
13:15:34| github.com/kubestellar/kubestellar/pkg/transport/cmd		coverage: 0.0% of statements
13:15:40| ok  	github.com/kubestellar/kubestellar/pkg/transport	5.512s	coverage: 32.9% of statements
13:15:40| ok  	github.com/kubestellar/kubestellar/pkg/util	0.715s	coverage: 4.8% of statements


Is it possible to catch correctly FileSystemException when openBox fails?

In my Linux server there are two users allowed to execute a Hive based program. It works okay for both users unless program is executed at the same time. One gets hive.lock file correctly, the other gets FileSystemException.
The trouble came when I tried to implement a 3 attemps logic. I catch this exception, then I wait for 1500 ms and retry again (with 3 maximum attemps). I catch the Exception successfully, but then it came another exception (exactly the same stackTrace). I have been fighting for 2 hours with this issue, asking myself what I was doing bad, even recreating that logic in a test program.
Finally I decided to look at the source code (version 2.2.3). At HiveImpl._openBox method, I can see the catch clause at 116 line and I can see now the trouble:
Future<BoxBase<E>> _openBox<E>(
    String name,
    bool lazy,
    HiveCipher? cipher,
    KeyComparator comparator,
    CompactionStrategy compaction,
    bool recovery,
    String? path,
    Uint8List? bytes,
    String? collection,
  ) async {
    assert(path == null || bytes == null);
    assert(name.length <= 255 && name.isAscii,
        'Box names need to be ASCII Strings with a max length of 255.');
    name = name.toLowerCase();
    if (isBoxOpen(name)) {
      if (lazy) {
        return lazyBox(name);
      } else {
        return box(name);
      }
    } else {
      if (_openingBoxes.containsKey(name)) {
        await _openingBoxes[name];
        if (lazy) {
          return lazyBox(name);
        } else {
          return box(name);
        }
      }

      var completer = Completer();
      _openingBoxes[name] = completer.future;

      BoxBaseImpl<E>? newBox;
      try {
        StorageBackend backend;
        if (bytes != null) {
          backend = StorageBackendMemory(bytes, cipher);
        } else {
          backend = await _manager.open(
              name, path ?? homePath, recovery, cipher, collection);
        }

        if (lazy) {
          newBox = LazyBoxImpl<E>(this, name, comparator, compaction, backend);
        } else {
          newBox = BoxImpl<E>(this, name, comparator, compaction, backend);
        }

        await newBox.initialize();
        _boxes[name] = newBox;

        completer.complete();
        return newBox;
      } catch (error, stackTrace) {
        newBox?.close();
        completer.completeError(error, stackTrace);
        rethrow;
      } finally {
        // ignore: unawaited_futures
        _openingBoxes.remove(name);
      }
    }
  }

Exception is getting rethrowed again (okay). The thing is the completer getting complete with that error, but this time I don't see a way to catch it and an UnhandledException is crashing my app/logic.
Any idea/workaround?
Thank you

I have in mind a workaround: to create a top level lock file, and getting this lock file before exeuting hive logic. It is an acceptable solution but I still think that Hive implementation behavior is not correct (to raise the Exception two times, one of them not manageable)


Revert "Encode newlines for -ojunit as their XML equivalent instead of {newline}"

Reverts cpputest/cpputest#1598

Broke the build in a non-trivial way

Fixed in other way. Closing revert


v1.0.0-rc.7 release

Versioning
How to Increment Versions
Zebra follows semantic versioning. Semantic versions look like: MAJOR.MINOR.PATCH[-TAG.PRE-RELEASE]
The draft zebrad changelog will have an automatic version bump. This version is based on the labels on the PRs in the release.
Check that the automatic zebrad version increment is correct:
If we're releasing a mainnet network upgrade, it is a major release:

Increment the major version of all the Zebra crates.
Increment the patch version of the tower crates.

If we're not releasing a mainnet network upgrade, check for features, major changes, deprecations, and removals. If this release has any, it is a minor release:

Increment the minor version of zebrad.
Increment the pre-release version of the other crates.
Increment the patch version of the tower crates.

Otherwise, it is a patch release:

Increment the patch version of zebrad.
Increment the pre-release version of the other crates.
Increment the patch version of the tower crates.

Zebra's Rust API is not stable or supported, so we keep all the crates on the same beta pre-release version.
Version Locations
Once you know which versions you want to increment, you can find them in the:
zebrad (rc):

[x] zebrad Cargo.toml
[x] zebra-network protocol user agent: https://github.com/ZcashFoundation/zebra/blob/main/zebra-network/src/constants.rs
[x] README.md
[x] book/src/user/docker.md

crates (beta):

[x] zebra-* Cargo.tomls

tower (patch):

[x] tower-* Cargo.tomls

auto-generated:

[x] Cargo.lock: run cargo build after updating all the Cargo.tomls

Version Tooling
You can use fastmod to interactively find and replace versions.
For example, you can do something like:
fastmod --extensions rs,toml,md --fixed-strings '1.0.0-rc.0' '1.0.0-rc.1' zebrad README.md zebra-network/src/constants.rs book/src/user/docker.md
fastmod --extensions rs,toml,md --fixed-strings '1.0.0-beta.15' '1.0.0-beta.16' zebra-*
fastmod --extensions rs,toml,md --fixed-strings '0.2.30' '0.2.31' tower-batch tower-fallback
cargo build

If you use fastmod, don't update versions in CHANGELOG.md or zebra-dependencies-for-audit.md.
README
Update the README to:

[x] Remove any "Known Issues" that have been fixed
[x] Update the "Build and Run Instructions" with any new dependencies.
Check for changes in the Dockerfile since the last tag: git diff <previous-release-tag> docker/Dockerfile.
[x] If Zebra has started using newer Rust language features or standard library APIs, update the known working Rust version in the README, book, and Cargo.tomls

You can use a command like:
      fastmod --fixed-strings '1.58' '1.65'

Checkpoints
With every release and for performance reasons, we want to update the Zebra checkpoints. More information on how to do this can be found in the zebra-checkpoints README.
To do this you will need a synchronized zcashd node. You can request help from other zebra team members to submit this PR if you can't make it yourself at the moment of the release.
Missed Dependency Updates
Sometimes dependabot misses some dependency updates, or we accidentally turned them off.
Here's how we make sure we got everything:

Run cargo update on the latest main branch, and keep the output
If needed, update deny.toml
Open a separate PR with the changes, including the output of cargo update

Change Log
Important: Any merge into main deletes any edits to the draft changelog.
Once you are ready to tag a release, copy the draft changelog into CHANGELOG.md.
We use the Release Drafter workflow to automatically create a draft changelog. We follow the Keep a Changelog format.
To create the final change log:

[x] Copy the latest draft changelog into CHANGELOG.md (there can be multiple draft releases)
[x] Delete any trivial changes. Keep the list of those, to include in the PR
[x] Combine duplicate changes
[x] Edit change descriptions so they are consistent, and make sense to non-developers
[x] Check the category for each change

Prefer the "Fix" category if you're not sure

Change Categories
From "Keep a Changelog":

Added for new features.
Changed for changes in existing functionality.
Deprecated for soon-to-be removed features.
Removed for now removed features.
Fixed for any bug fixes.
Security in case of vulnerabilities.

Create the Release
Create the Release PR
After you have the version increments, the updated checkpoints, any missed dependency updates,
and the updated changelog:

[ ] Make sure the PRs with the new checkpoint hashes and missed dependencies are already merged
[x] Push the version increments and the updated changelog into a branch
(for example: bump-v1.0.0-rc.0 - this needs to be different to the tag name)
[x] Create a release PR by adding &template=release-checklist.md to the comparing url (Example).

[x] Add the list of deleted changelog entries as a comment to make reviewing easier.

[x] Freeze the batched queue using Mergify.
[x] Mark all the release PRs as Critical priority, so they go in the urgent Mergify queue.

Create the Release

[ ] Once the PR has been merged, create a new release using the draft release as a base, by clicking the Edit icon in the draft release
[ ] Set the tag name to the version tag,
for example: v1.0.0-rc.0
[ ] Set the release to target the main branch
[ ] Set the release title to Zebra  followed by the version tag,
for example: Zebra 1.0.0-rc.0
[ ] Replace the prepopulated draft changelog in the release description with the final changelog you created;
starting just after the title ## [Zebra ... of the current version being released,
and ending just before the title of the previous release.
[ ] Mark the release as 'pre-release', until it has been built and tested
[ ] Publish the pre-release to GitHub using "Publish Release"
[ ] Delete all the draft releases from the list of releases

Binary Testing

[ ] Wait until the Docker binaries have been built on main, and the quick tests have passed.
(You can ignore the full sync and lightwalletd tests, because they take about a day to run.)
[ ] Wait until the pre-release deployment machines have successfully launched
[ ] Publish the release to GitHub by disabling 'pre-release', then clicking "Set as the latest release"
[ ] Wait until the Docker images have been published
[ ] Test the Docker image using docker run --tty --interactive zfnd/zebra:1.0.0-rc.<version>,
and put the output in a comment on the PR

[ ] Un-freeze the batched queue using Mergify.

Blog Post
If the release contains new features (major or minor), or high-priority bug fixes:

[ ] Ask the team about doing a blog post

Release Failures
If building or running fails after tagging:

Fix the bug that caused the failure
Increment versions again, following these instructions from the start
Update the code and documentation with a new git tag
Update CHANGELOG.md with details about the fix
Tag a new release

Do you want to skip this step, so we can get the release out before Rust 1.69 goes stable?

I'm okay skipping them but would prefer to update them if you're around later today for a re-approval.

Do you want to skip this step, so we can get the release out before Rust 1.69 goes stable?

I'm okay skipping them but would prefer to update them if you're around later today (in a couple hours) for a re-approval.

I can check back in later today, but I'll only be around for the next 4 hours, because I started early this morning.

@Mergifyio update

Test the Docker image using docker run --tty --interactive zfnd/zebra:1.0.0-rc.,
and put the output in a comment on the PR

Output:
➜ docker run --tty --interactive zfnd/zebra:1.0.0-rc.7
Unable to find image 'zfnd/zebra:1.0.0-rc.7' locally
1.0.0-rc.7: Pulling from zfnd/zebra
26c5c85e47da: Pull complete
7d2eda9da1a8: Pull complete
0c40b2a56142: Pull complete
2bb8165b4c4d: Pull complete
f4be1142cb95: Pull complete
59bba4e60891: Pull complete
Digest: sha256:30c536a65fae51dd919f61f53c0380ea57ea0f419285acd397783d53652fca69
Status: Downloaded newer image for zfnd/zebra:1.0.0-rc.7
[sentry] initialized disabled sentry client due to disabled or invalid DSN
2023-04-19T22:44:39.357452Z  INFO zebrad::components::tracing::component: started tracing component filter="info" TRACING_STATIC_MAX_LEVEL=LevelFilter::INFO LOG_STATIC_MAX_LEVEL=Info
2023-04-19T22:44:39.357528Z  INFO zebrad::components::tracing::component: installed sentry tracing layer
2023-04-19T22:44:39.357534Z  INFO zebrad::application: Diagnostic Metadata:
version: 1.0.0-rc.7
Zcash network: Mainnet
state version: 25
target triple: x86_64-unknown-linux-gnu
build profile: release
2023-04-19T22:44:39.357546Z  INFO zebrad::application: loaded zebrad config config_path=Some("/etc/zebra/zebrad.toml") config=ZebradConfig { consensus: Config { checkpoint_sync: true, debug_skip_parameter_preload: false }, metrics: Config { endpoint_addr: None }, network: Config { listen_addr: <IP_ADDRESS>:8233, network: Mainnet, initial_mainnet_peers: {"dnsseed.z.cash:8233", "dnsseed.str4d.xyz:8233", "mainnet.seeder.zfnd.org:8233", "mainnet.is.yolo.money:8233"}, initial_testnet_peers: {"dnsseed.testnet.z.cash:18233", "testnet.seeder.zfnd.org:18233", "testnet.is.yolo.money:18233"}, peerset_initial_target_size: 25, crawl_new_peer_interval: 61s }, state: Config { cache_dir: "/zebrad-cache", ephemeral: false, debug_stop_at_height: None, delete_old_database: true }, tracing: Config { use_color: true, force_use_color: false, filter: None, buffer_limit: 128000, endpoint_addr: None, flamegraph: None, log_file: None, use_journald: false }, sync: Config { download_concurrency_limit: 50, checkpoint_verify_concurrency_limit: 1000, full_verify_concurrency_limit: 20, parallel_cpu_threads: 0 }, mempool: Config { tx_cost_limit: 80000000, eviction_memory_time: 3600s, debug_enable_at_height: None }, rpc: Config { listen_addr: None, parallel_cpu_threads: 0, debug_force_finished_sync: false } }

See more:

2023-04-19T22:44:39.357676Z  INFO {net="Main"}: zebrad::application: initialized rayon thread pool for CPU-bound tasks num_threads=12
2023-04-19T22:44:39.359886Z  INFO {net="Main"}: zebrad::commands::start: Starting zebrad
2023-04-19T22:44:39.359966Z  INFO {net="Main"}: zebrad::commands::start: initializing node state
2023-04-19T22:44:39.365884Z  INFO {net="Main"}: zebrad::commands::start: opening database, this may take a few minutes
2023-04-19T22:44:39.366373Z  INFO zebra_state::service::finalized_state::disk_db: the open file limit is high enough for Zebra current_limit=1048576 min_limit=512 ideal_limit=1024
2023-04-19T22:44:40.108414Z  INFO zebra_state::service::finalized_state::disk_db: Opened Zebra state cache at /zebrad-cache/state/v25/mainnet
2023-04-19T22:44:40.109027Z  INFO zebra_state::service::finalized_state: loaded Zebra state cache tip=None
2023-04-19T22:44:40.109188Z  INFO zebra_state::service: starting legacy chain check
2023-04-19T22:44:40.109212Z  INFO zebra_state::service: cached state consensus branch is valid: no legacy chain found
2023-04-19T22:44:40.109363Z  INFO {net="Main"}: zebrad::commands::start: initializing network
2023-04-19T22:44:40.109435Z  INFO {net="Main"}:open_listener{addr=<IP_ADDRESS>:8233}: zebra_network::peer_set::initialize: Trying to open Zcash protocol endpoint at <IP_ADDRESS>:8233...
2023-04-19T22:44:40.109804Z  INFO {net="Main"}:open_listener{addr=<IP_ADDRESS>:8233}: zebra_network::peer_set::initialize: Opened Zcash protocol endpoint at <IP_ADDRESS>:8233
2023-04-19T22:44:40.110092Z  INFO {net="Main"}: zebra_network::address_book_updater: starting the address book updater
2023-04-19T22:44:40.364404Z  INFO {net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="dnsseed.z.cash:8233" remote_ip_count=50
2023-04-19T22:44:40.493545Z  INFO {net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="dnsseed.str4d.xyz:8233" remote_ip_count=50
2023-04-19T22:44:40.548600Z  INFO {net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="mainnet.seeder.zfnd.org:8233" remote_ip_count=50
2023-04-19T22:44:40.762369Z  INFO {net="Main"}:add_initial_peers: zebra_network::config: resolved seed peer IP addresses seed="mainnet.is.yolo.money:8233" remote_ip_count=6
2023-04-19T22:44:40.762443Z  INFO {net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: limiting the initial peers list from 56 to 25
2023-04-19T22:44:40.762566Z  INFO {net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: connecting to initial peer set initial_peer_count=25 initial_peers={<IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, [2a01:4f8:b0:920a::5502]:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233}
2023-04-19T22:44:41.493325Z  INFO {net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=9 errors=1 addr=<IP_ADDRESS>:8233 e=Peer offered obsolete version: Version(170002)
2023-04-19T22:44:42.400991Z  INFO {net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: finished connecting to initial seed peers handshake_success_total=23 handshake_error_total=2 outbound_connections=23
2023-04-19T22:44:42.401641Z  INFO {net="Main"}: zebra_network::peer_set::initialize: sending initial request for peers active_initial_peer_count=23
2023-04-19T22:44:42.402755Z  INFO {net="Main"}: zebrad::commands::start: initializing verifiers
2023-04-19T22:44:42.403198Z  INFO {net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::primitives::groth16::params: checking and loading Zcash Sapling and Sprout parameters
2023-04-19T22:44:42.403222Z  INFO {net="Main"}:crawl_and_dial{new_peer_interval=61s}: zebra_network::peer_set::initialize: starting the peer address crawler crawl_new_peer_interval=61s outbound_connections=23
2023-04-19T22:44:42.403271Z  INFO {net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::chain: starting state checkpoint validation
2023-04-19T22:44:42.420234Z  INFO {net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::chain: initializing chain verifier tip=None max_checkpoint_height=Height(2056451)
2023-04-19T22:44:42.420307Z  INFO {net="Main"}: zebrad::commands::start: initializing syncer
2023-04-19T22:44:42.420325Z  INFO {net="Main"}: zebrad::commands::start: initializing mempool
2023-04-19T22:44:42.420381Z  INFO {net="Main"}: zebrad::commands::start: spawned initial Zebra tasks
2023-04-19T22:44:42.420411Z  INFO {net="Main"}: zebra_state::config: checking for old database versions
2023-04-19T22:44:42.420488Z  INFO {net="Main"}: zebrad::components::sync::gossip: initializing block gossip task
2023-04-19T22:44:42.420526Z  INFO {net="Main"}:sync: zebrad::components::sync: starting genesis block download and verify
2023-04-19T22:44:42.420531Z  INFO {net="Main"}: zebrad::components::mempool::queue_checker: initializing mempool queue checker task
2023-04-19T22:44:42.420554Z  INFO {net="Main"}: zebrad::components::mempool::gossip: initializing transaction gossip task
2023-04-19T22:44:42.420561Z  INFO {net="Main"}: zebrad::components::mempool::crawler: initializing mempool crawler task
2023-04-19T22:44:42.434696Z  INFO {net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::chain: state is not fully synced yet, remaining checkpoints will be verified during syncing
2023-04-19T22:44:42.434863Z  INFO {net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::chain: finished state checkpoint validation
2023-04-19T22:44:42.440136Z  INFO {net="Main"}: zebrad::components::sync::progress: initial sync is waiting to download the genesis block sync_percent=0.000 % current_height=None
2023-04-19T22:44:42.493563Z  INFO {net="Main"}: zebra_state::config: finished old database version cleanup task
2023-04-19T22:44:42.575026Z  INFO {net="Main"}:sync:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=1 current_range=(Unbounded, Included(Height(0)))
2023-04-19T22:44:42.683680Z  INFO {net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=Some(Height(0))
2023-04-19T22:44:43.924467Z  INFO {net="Main"}:init{config=Config { checkpoint_sync: true, debug_skip_parameter_preload: false } network=Mainnet debug_skip_parameter_preload=false}: zebra_consensus::primitives::groth16::params: Zcash Sapling and Sprout parameters downloaded and/or verified
2023-04-19T22:44:44.763301Z  INFO {net="Main"}:sync:try_to_sync: zebrad::components::sync: extending tips tips.len=1 in_flight=499 extra_hashes=0 lookahead_limit=1000 state_tip=Some(Height(0))
2023-04-19T22:44:44.902478Z  INFO {net="Main"}:sync:try_to_sync:obtain_tips:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=400 current_range=(Excluded(Height(0)), Included(Height(400)))
2023-04-19T22:44:46.754603Z  INFO {net="Main"}:sync:try_to_sync:extend_tips:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=400 current_range=(Excluded(Height(400)), Included(Height(800)))
2023-04-19T22:44:47.023576Z  INFO {net="Main"}:sync:try_to_sync: zebrad::components::sync: extending tips tips.len=1 in_flight=869 extra_hashes=0 lookahead_limit=1000 state_tip=Some(Height(800))
2023-04-19T22:44:47.441591Z  INFO {net="Main"}: zebrad::components::sync::progress: estimated progress to chain tip sync_percent=0.039% current_height=Height(800) network_upgrade=BeforeOverwinter remaining_sync_blocks=2070157 time_since_last_state_block=0s
2023-04-19T22:44:48.908237Z  INFO {net="Main"}:sync:try_to_sync:extend_tips:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=400 current_range=(Excluded(Height(800)), Included(Height(1200)))