Local editor has lost synchronization with server

problem description
we use leaps (0.6.0) with codemirror (with an old version but also with 5.26). it used to work months ago and then we found that opening the same document in two tabs (one in firefox, the other in chromium) leads to this error message in the javascript error console of tab A:
Local editor has lost synchronization with server

when one enters any letter in tab B (or vice versa) but, and this puzzles me, when both tabs are reloaded i can use del key to remove a letter or space and it keeps the sync.
seeking advice
now i don't know exactly where to search for a solution, any hints what could cause this would be great.
what i've done so far:

in the go code i've added: +       logConf.LogLevel = "ALL" and it prints lots of interesting lines, but no obvious error message
in the frontend code i've also added lots of debugging lines and checked the network messages in the /leaps/ws websocket but nothing obvious either

possible causes

we traverse the /leaps/ws trough a nginx reverse-proxy, maybe this caused it (i will try to remove this but haven't done yet)
we started to update to from leaps 0.6.0 to leaps 0.8.4 but that turns out to be more effort since you are using gorilla websockets and we use the websockets coming with golang.org/x/net
we could try to replace codemirror with ace (seems to be much work though)

Hey @qknight, are there any non-ascii characters inside the content you are editing? Errors like this usually suggest that events being fired from the editor (in this case CodeMirror) are returning unexpected character lengths for certain operations. This has happened a lot in the past when working with large non-ascii characters since support for them in these editors (and JavaScript in general) is often very poor.

ATM it seems that the leaps library on the tab A receives the updates and performs the transaction and in the file
client/leap-bind-codemirror.js
in the function: leap_bind_codemirror.prototype._apply_transform = function(transform) { i see that: this._content = this._leap_client.apply(transform, this._content); is correctly set but the this._codemirror.getDoc().getValue() afterwards returns the old value and thus the Local editor has lost synchronization with server is triggered.
conclusion
the leaps javascript client library, still based on 0.6.0, receives the event properly inside the browser, but the codemirror inside the webpage isn't updated properly.
question
what mechanism is used to update the document inside the codemirror? i see only one reference to update the whole document binder._codemirror.getDoc().setValue(doc.content); found in leap_bind_codemirror which is used initially to set the document. a call to setValue(...) will disrupt the current cursor position so the codemirror document update must touch the internals of codemirror and this is what is probably going wrong.

conclusion
i'm confident that live_document.replaceRange(insert, start_position, end_position); does not work at all for some reason.

found the bug!
the code as it was:
    //if ( typeof(transform.insert) === "string" && transform.insert.length > 0 ) {

the code how it works instead:
    if ( typeof(transform.insert._str) === "string" && transform.insert._str.length > 0 ) {
            insert = transform.insert._str;

solution
typeof(transform.insert) === "string"  is never true, as insert is of type object.

@qknight nice find! It looks as though during version 0.6.0 to 0.6.1 I was making changes to the JS client lib but only porting changes to the ACE binding. If you decide in the future to upgrade to 0.8.4 you should be okay to use the CodeMirror lib that comes with it as it looks as though I eventually updated it, but your fix should work fine for now. Although it might be safer to use transform.insert.str() instead of transform.insert._str.
I'm sorry that you were hit by this, at the time I was racing through major API changes and clearly struggled to keep all the components synced up. Glad you were able to solve it!

we'll about to update to 0.8.4 ASAP but we just didn't do that yet.


Any way to suppress warnings from CVXPY re: ECOS solver?

What are you trying to do?
When using PyPortolioOpt I get the following warning:
Python311\site-packages\cvxpy\reductions\solvers\solving_chain.py:336: FutureWarning:     Your problem is being solved with the ECOS solver by default. Starting in     CVXPY 1.5.0, Clarabel will be used as the default solver instead. To continue     using ECOS, specify the ECOS solver explicitly using the ``solver=cp.ECOS``     argument to the ``problem.solve`` method.
What have you tried?
I posted in the CVXPY Github issues area and they said to come here.  see:  https://github.com/cvxpy/cvxpy/issues/2281
I believe that this could be fixed by explicitly using the solver=cp.ECOS argument to the problem.solve method or solver=cp.CLARABEL .  But I don't know where you would do this.

@wayner9 Which optimizer are you using? You should be able to specify the solver when instantiating the optimizer. See this test case here:
https://github.com/robertmartin8/PyPortfolioOpt/blob/30ab57147ba61eddc8301294a5b1c5ef260b23fa/tests/test_efficient_frontier.py#L101

I am not explicitly specifying an optimizer.  Presumably whatever is the default optimizer is what I am using.
I am calling the optimizer with:
ef = EfficientFrontier(mu, S,weight_bounds=bounds)
raw_weights = ef.efficient_risk(vol)

Right now I am just setting up code to pull in my data and run the optimizer so I haven't been too concerned on exactly what Optimizer I am using.  Once I get a bit further along I will worry about that more.  But it is kind of a pain to get all of these warning lines in my output.

Just do
ef = EfficientFrontier(mu, S,weight_bounds=bounds, solver="Clarabel")

and you should be good.

Perfect that works!


is this integration no longer available in Home Assistant?

I'm an ACWD customer and wanted to set this up to track my water usage as my Flume is not longer supported with the AMI meters, but when I search for this integration, ACWD Water Usage, I don't get any hits in the HA search. Is this still being supported?
HA details

Core 2024.5.5
Supervisor 2024.06.0
Operating System 12.3
Frontend 20240501.1

NM, i realize that I have to manually add it via HACS as a custom repo. I'll submit a PR to the README to clarify the install steps


GH-36916: [C++] Refactor the scan node to make way for adding parquet

Rationale for this change
The rationale is described in the github issue.
What changes are included in this PR?
The scan node is refactored.  A few new unit tests are added.  No functional changes to the new scan node.
Are these changes tested?
Yes, through a combination of existing and new unit tests.
Are there any user-facing changes?
No.  The new scan node is not yet user facing.

Closes: #36916

Some of these CI failures are probably relevant: https://github.com/apache/arrow/actions/runs/5685648635/job/15410968558?pr=36917


Add StateSaver class.

RAII class suggested by @mkoval in personalrobotics/libherb#26.

Coverage decreased (-0.02%) to 80.35% when pulling<PHONE_NUMBER>7ff5c786bbc41fab639d3368137410 on enhancement/brianhou/state-saver into 2af5c55cc52b0e85e1eb84a3379d4f500a23ecb9 on master.

Coverage decreased (-0.02%) to 80.35% when pulling<PHONE_NUMBER>7ff5c786bbc41fab639d3368137410 on enhancement/brianhou/state-saver into 2af5c55cc52b0e85e1eb84a3379d4f500a23ecb9 on master.

Coverage decreased (-0.01%) to 79.153% when pulling c6d21d719a431361205963e47e09478271900408 on enhancement/brianhou/state-saver into 5d19317c365708bff2539fd6ccc1b994a9e441d1 on master.

Coverage remained the same at 78.813% when pulling e5e1b8d9ab72c342dd3a81f6ba90402e58d55193 on enhancement/brianhou/state-saver into 4c08ac570005d74e5622f81f68c7f1bde32a382f on master.

Changes Unknown when pulling 412feea030758ad6dc705e8231c42632bb01f316 on enhancement/brianhou/state-saver into ** on master**.

Changes Unknown when pulling 412feea030758ad6dc705e8231c42632bb01f316 on enhancement/brianhou/state-saver into ** on master**.

Coverage remained the same at 78.813% when pulling 412feea030758ad6dc705e8231c42632bb01f316 on enhancement/brianhou/state-saver into a8060422cbdf1c85c7257df0d92e9685f735a2df on master.


Migration of the Edgent project to be able to build with Apache Maven

I finally managed to solve all problems and untangle all knots I wasn't that happy with.
The current version should be buildable with a simple "mvn package"
This would include running all unit-tests as part of the build.

Please change "/target" to "target/" in the top level .gitignore.  git status is showing the per-module generated artifacts. Thanks!

With the merge from upstream, in the top level pom.xml's java7 Profile (and retrolambda config), can the following now be removed?
line 565
    <configuration>
      <defaultMethods>true</defaultMethods>
    </configuration>

Type= jar is the default. So if you omit the type, that's what have will use. So a type declaration would be redundant.

Please add the following dependency to connectors/jdbc.  With it, the JDBC connector tests then pass and they will also run with the rest of the tests.  Manual setup/run not needed :-)
<!-- https://mvnrepository.com/artifact/org.apache.derby/derby -->
<dependency>
    <groupId>org.apache.derby</groupId>
    <artifactId>derby</artifactId>
    <version><IP_ADDRESS></version>
    <scope>test</scope>
</dependency>

note: above above commits addressed my issues/comments above (or course you'll have to pull the feature branch to update your clone's content to include them)

Chris, I just committed the first round changes for the samples (above).
The desire was to create a separate source release bundle for the samples (perhaps a precursor to migrating them to their own repository at some point). The samples pom's do not have the edgent-parent pom as a parent.  I wasn't able to figure out how to exclude the sample sources from the "core" apache-edgent source bundle.  The sample bundle is built via cd samples; mvnw clean install -papache-release
See comments the edgent-parent/pom.xml related to "samples".
See samples/README.md.
At this moment only topology/run-sample.sh is present.  All non-console-non-http-server topology samples should run successfully.  TODO - other sample categories.

The Edgent console page now comes up in the browser, but there's still a problem.  Following its "loading graph" progress message, no topology graph is rendered.  Reproduce via the topology DevelopmentSample sample.  Is the generated uber jar or servlets.war is missing something?
cd samples
./mvnw clean install
cd topology
./run-samples.sh DevelopmentSample
# open browser to the "http://localhost:<port>/console" that's emitted

Chris, noticed building (now?) reports a warning about duplicate declaration of the maven-assembly-plugin in pom.xml.  There are in fact two decls of it.  Also just a reminder of Edgent Console problem noted above.  Thanks

Chris, when importing into Eclipse there's one residual warning for the top pom.xml: Overriding managed version 3.6 for maven-site-plugin.  The pom is specifying ver 3.4.  If that's intentional can a clarification as to why not 3.6 be added to the file and as well as an annotation to squelch the warning: <version>3.4</version><!--$NO-MVN-MAN-VER$-->.  Thanks.

All Changes have been merged back to the original edgent repo, but to the develop branch instead of the master I created the pull-request for.

WooHoo!  I noticed it's 5 months to the day (and 289 commits) from the first commit on this effort. whew/yikes :-)


fix: Reduce visual noise when loading in new properties in the property grid

PR Details
The property grid is briefly emptied and categories are expanded after a short delay whenever the user swaps between two selected entities:
https://github.com/user-attachments/assets/b03fd1fa-7843-48b9-b83a-90d73704f1c2
This PR ensures the previous one is kept on screen while the other one loads in:
https://github.com/user-attachments/assets/e5b1050d-b9d9-4774-92b1-fd8ed57a3b0b
This improves readability when comparing two objects, or when quickly scanning for a given property or component.
Loading duration has been artificially lengthened in the two clips above for clarity.
This area probably has a bunch of conflicts with your branch @Kryptos-FR , do let me know if I should leave this PR for later! Also I have zero clue about WPF, probably did something wrong, let me know ;)
Related Issue
None afaict
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] I have built and run the editor to try this change out.

I'm a bit sick at the moment so I can't build locally. Let me ask a few questions instead.
Did you check if it had any impacts when selecting entities either from the tree, or picking from the scene? Or with multiple selection as well as "navigating" back and forth with those selection?
Some of the previous code had checks to prevent reentries but I don't remember what scenarii were triggering it

There's a small issue right now where the selection's name label in the property grid is set to no selection when selecting an asset after selecting an entity, not yet sure how to fix that one without replacing the two observable collections with a cleaner pattern


Add resource requirement for running examples

Signed-off-by: Qinziyue Xu<EMAIL_ADDRESS>

@xuqinziyue ping?

@mithro Hi! Sorry haven't checked message for a while. I will commit the fix today

@xuqinziyue Can you please squash your two commits together and force push to your current branch?

Thanks! Sorry for the delay!


No Module named 'eth2deposit' - Unable to generate deposit keys (Windows 10)

sh deposit.sh

msys
Running deposit-cli...
Traceback (most recent call last):
File "./eth2deposit/deposit.py", line 5, in
from eth2deposit.credentials import (
ModuleNotFoundError: No module named 'eth2deposit'

@Dolomites use this binaries https://github.com/ethereum/eth2.0-deposit-cli/releases/tag/v0.2.1

@Dolomites use this binaries https://github.com/ethereum/eth2.0-deposit-cli/releases/tag/v0.2.1

didn't help.

@extremegym could you elaborate on why binaries didn't help? Any error logs?


hls.js configuration support

Are there any plans to make the hls.js implementation configurable? I'm particularly interested in being able to set capLevelToPlayerSize, to save bandwidth for mobile users not on wi-fi.

Allowing to set Hls.js options would be great to finetune the playback options. So definitely +1 for this!
Would be also great is Hls.js player instance could be exposed somewhere so we can grab it and ie. use advanced event listeners.

This has been fixed in v0.11.0: https://github.com/muxinc/videojs-mux-kit/releases/tag/v0.11.0
It allows both the configuration and exposed hlsjs instance on the tech.


Timesheet - 05/09/2021 - Dmitry Mugtasimov

Task 1
https://github.com/thenewboston-developers/thenewboston-node/issues/289
Proof of Work

https://github.com/thenewboston-developers/thenewboston-node/pull/382
https://github.com/thenewboston-developers/thenewboston-node/pull/383
https://github.com/thenewboston-developers/thenewboston-node/pull/385
https://github.com/thenewboston-developers/thenewboston-node/pull/386
https://github.com/thenewboston-developers/thenewboston-node/issues/387

Time Spent
6.5 hours

Task 2
Code review
Proof of Work

https://github.com/thenewboston-developers/thenewboston-node/pull/378
https://github.com/thenewboston-developers/thenewboston-node/pull/380
https://github.com/thenewboston-developers/thenewboston-node/pull/381
https://github.com/thenewboston-developers/thenewboston-node/pull/373
https://github.com/thenewboston-developers/thenewboston-node/pull/374
https://github.com/thenewboston-developers/thenewboston-node/pull/389

Time Spent
1 hours

Total Time Spent
7.5 hours
Account Number
757d598308bf1e2943bd1a9fc34ae7b8951ca864d64228b59e62614b27ddefc4

@manishram pay maybe?


HHL algorithm produces wrong results for certain matrices

Informations

Qiskit Aqua version: 0.5.1
Python version: 3.6.2
Operating system: macOS Mojave 10.14.5

I have noticed this specially for matrices that are non-Hermitian and are expanded to the Hermitian form [[0, M], [M.conj().T, 0]. When trying to solve the system corresponding to the expanded matrix, the algorithm does not produced the correct results (see example below). This may happen too for other matrices.
Steps to reproduce the problem
from qiskit.aqua import run_algorithm
from qiskit.aqua.input import LinearSystemInput
from qiskit.aqua.algorithms.classical import ExactLSsolver
import numpy as np
params = {
'problem': {
'name': 'linear_system'
},
'algorithm': {
'name': 'HHL'
},
'eigs': {
'expansion_mode': 'suzuki',
'expansion_order': 2,
'name': 'EigsQPE',
'num_ancillae': 6,
'num_time_slices': 70,
'negative_evals': True
},
'reciprocal': {
'name': 'Lookup',
'negative_evals': True
},
'backend': {
'provider': 'qiskit.BasicAer',
'name': 'statevector_simulator'
}
}
matrix = [[0.0, 0.0, 1.0, 2.0], [0.0, 0.0, 3.0, 0.5], [1.0, 3.0, 0.0, 0.0], [2.0, 0.5, 0.0, 0.0]]
vector = [1.,1.,1.,1.]
params['input'] = {
'name': 'LinearSystemInput',
'matrix': matrix,
'vector': vector
}
result = run_algorithm(params)
result_ref = ExactLSsolver(matrix, vector).run()
print(result['solution']) # solution produced by HHL
print(result_ref['solution']) # real solution
Which gives:
[ 0.04699195-1.61524943e-06j -0.50764772-6.73817804e-06j
-0.37757465-3.07013204e-06j -0.11781876+1.10893970e-06j]
[0.45454545454545453, 0.18181818181818182, 0.2727272727272727, 0.3636363636363637]

We are already aware of this issue and currently investigating it. We do not have a solution yet, but we highly suspect the peculiar spectrum of the expanded matrix to cause problems with current HHL implementation. The expanded matrices will always have a spectrum of +-\lambda_n, which usually does not happen in the general hermitian case, due to a trace of 0 and thus the sum of all eigenvalues needs to be 0.
In your above example the spectrum of matrix is:
[-3.41385672, -1.61108109, 1.61108109, 3.41385672]
with eigenvalues according to +-\lambda_1 and +-\lambda_2.
You can "help" the HHL algorithm by setting the corners of the expanded matrix to 0.1, such that
matrix = [[0.1, 0.0, 1.0, 2.0], [0.0, 0.0, 3.0, 0.5], [1.0, 3.0, 0.0, 0.0], [2.0, 0.5, 0.0, 0.1]]
which has a spectrum of
[-0.0198939, 0.0066313, 0.27254642, 0.36472149]
Of course the solution will be changed slightly, but the fidelity of the HHL result is now much better.
When I use vector = [1.0, 1.0, 0.0, 0.0]
then I get the following results
result_ref['solution'] = [-0.0198939, 0.0066313, 0.27254642, 0.36472149]
result['solution'] = [-0.03529308+0.01916787j, -0.06791823+0.03004606j, 0.33082563-0.00303213j, 0.24728822-0.00942536j]
fidelity = 0.9207169380787709
Currently, we carry out further testing of the lookup method for calculating the reciprocal and look for bugs in the HHL implementation.

HHL is being reworked under this PR Qiskit/qiskit-terra#5698 where core algorithms have been moved to Terra repo and are being maintained there. The code here will be deprecated and as such is frozen - hence I am closing this issue.

HHL is being reworked under this PR Qiskit/qiskit-terra#5698 where core algorithms have been moved to Terra repo and are being maintained there. The code here will be deprecated and as such is frozen - hence I am closing this issue.


Update customer-key-manage.md

Changes to reflect disabling of new-moverequest cmdlet for local mailbox moves. This was based on the instructions from Exchange MRS team.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@brdesai - please merge the commit on the copy/edit review done by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

@mypil The suggested change has been committed.

Y'all better fix my IEM on my phone before I unsecured all of y'all
On Sun, May 3, 2020, 10:38 PM JohanFreelancer9<EMAIL_ADDRESS>wrote:

@JohanFreelancer9 approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/1800#pullrequestreview-404696723,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL7QJ6EYQIHMWDRDFNUD53TRPY2FDANCNFSM4MXK5L5Q
.

Just because I show you one way of me getting in does it mean I can still
do it fix my phone
On Mon, May 4, 2020, 8:18 AM UserAdminDEUS<EMAIL_ADDRESS>wrote:

Y'all better fix my IEM on my phone before I unsecured all of y'all
On Sun, May 3, 2020, 10:38 PM JohanFreelancer9<EMAIL_ADDRESS>wrote:

@JohanFreelancer9 approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/1800#pullrequestreview-404696723
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AL7QJ6EYQIHMWDRDFNUD53TRPY2FDANCNFSM4MXK5L5Q
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/1800#issuecomment-623458484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL7QJ6EHFSOVJXHFOAYKC3DRP26DBANCNFSM4MXK5L5Q
.

@KCCross - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith


FE-1: Update packages

JIRA
Update packages
There are no breaking changes that affect any of our repositories

Looks good ✅
Side note as we're already touching this repo:  we have package-lock.json in .gitignore. The common approach is to keep it in repo. Maybe we should do that. No sure what was the reason for ignoring it.

Looks good ✅
Side note as we're already touching this repo: we have package-lock.json in .gitignore. The common approach is to keep it in repo. Maybe we should do that. No sure what was the reason for ignoring it.

This was briefly discussed here: https://centrahq.slack.com/archives/C8H0T88P4/p1644610355689529
It's a grey area for libraries I guess


Max width, width and readability matters

Issue description:
The ideal width for readability is between 45 and 70 characters per line. Which is 600px~840px.
For desktop display, current website's width is just too huge for content. 1280px can be a good responsive triggering point. But IMO it is really bad for UX for reading content. At least for any text content, I recommend to use max width 600px~840px. This includes title and images for content as well.
In case of google, they have so many expeirence so they use about 650px.
When we design things, we always need to think about end-users, this is not only about the look, it is also about the any system and operation we design. User experience that's what sells.
URL to the web page (if already existing):
https://www.redotengine.org/news/redot-roadmap

Looks like it only changed the splash.
So I will do it myself.

#201


tour: Provide a dark mode

Context: https://tour.golang.org/basics/5
Provide users with an option to use the tutorial in dark mode (dark background, light colored contrasting fonts)

Thanks for the report. This is a dup of #409, so I'm closing here in favour of the older thread.


Extends the docs on creating modern team sites using the Office365 CLI

Category

[ ] Content fix
[X] New article
Related issues: fixes #X, partially #Y, mentioned in #1

What's in this Pull Request?
Extends SharePoint docs on creating modern team sites using the Office 365 CLI. Text describing how to create modern sites using the Office 365 CLI added after the C# and PowerShell paragraphs.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/solution-guidance/modern-experience-customizations-provisioning-sites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/solution-guidance/modern-experience-customizations-provisioning-sites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Merge conflict fixed

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/solution-guidance/modern-experience-customizations-provisioning-sites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/solution-guidance/modern-experience-customizations-provisioning-sites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Ping. This has been added Apr 20. Its only two new paragraphs. It is not a hard read :+1:  :)

@spdevdocs  what "Merging is blocked" means, should I take any action? @waldekmastykarz

I think it means you are not allowed to merge it yourself 🙂

OPS Build status updates of commit cbe3436:
:clock10: Preparing: average preparing time is 1 min(s) 7 sec(s)

Fixed conflicts to get this merged. Should be good now.

OPS Build status updates of commit cbe3436:
:clock10: Incremental building: average incremental building time is 46 sec(s)

OPS Build status updates of commit cbe3436:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/solution-guidance/modern-experience-customizations-provisioning-sites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[FEAT] Add custom block time  [SBK-262]

Overview
For testing my setup, I'd like to run my environment on a local chain like anvil, hardhat, or even ape networks run. However, due to how block time is calculated, it's quite difficult.
Exact issue
I have an anvil local chain running that I have run with :
anvil -b 2

The -b 2 gives it a block time of 2.
When I run the following command:
silverback run "monitoring:app" --network http://<IP_ADDRESS>:8545

I get the following stack trace
WARNING: Connecting Geth plugin to non-Geth client 'anvil'.
INFO: Loading Silverback App with settings:
  BROKER_CLASS="taskiq:InMemoryBroker"
  NETWORK_CHOICE="http://<IP_ADDRESS>:8545"
WARNING: Connecting Geth plugin to non-Geth client 'anvil'.
INFO: Loaded Silverback App:
  NETWORK="ethereum:adhoc"
  SIGNER=None
INFO: Using LiveRunner: max_exceptions=3
INFO: `ape-cache` database has not been initialized
INFO: block[block=0x45a75375d3e5e314597b98c678d592d35512fe26e4da0f6cd6c5f13aa6a92a9b] - Started
INFO: block[block=0x45a75375d3e5e314597b98c678d592d35512fe26e4da0f6cd6c5f13aa6a92a9b] - 0.010s (0.5%)
Traceback (most recent call last):
  File "/PATH/venv/bin/silverback", line 8, in <module>
    sys.exit(cli())
  File "/PATH/venv/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/PATH/venv/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/PATH/venv/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/PATH/venv/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/PATH/venv/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/PATH/venv/lib/python3.10/site-packages/click/decorators.py", line 92, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/PATH/venv/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/PATH/venv/lib/python3.10/site-packages/silverback/_cli.py", line 59, in run
    asyncio.run(runner.run())
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
    return future.result()
  File "/PATH/venv/lib/python3.10/site-packages/silverback/runner.py", line 61, in run
    await asyncio.gather(*tasks)
  File "/PATH/venv/lib/python3.10/site-packages/silverback/runner.py", line 87, in _block_task
    async for block in async_wrap_iter(
  File "/PATH/venv/lib/python3.10/site-packages/silverback/utils.py", line 21, in yield_queue_items
    raise exception
  File "/PATH/venv/lib/python3.10/site-packages/silverback/utils.py", line 26, in iter_to_queue
    for item in it:
  File "/PATH/venv/lib/python3.10/site-packages/ape/managers/chain.py", line 346, in poll_blocks
    _try_timeout()
  File "/PATH/venv/lib/python3.10/site-packages/ape/managers/chain.py", line 326, in _try_timeout
    raise ChainError(message)
ape.exceptions.ChainError: Timed out waiting for new block (time_waited=0.0144).

This is because the timeout variable in ape/managers/chain.py::poll_blocks is set as such:
timeout = (
            (
                10.0
                if network_name == LOCAL_NETWORK_NAME or network_name.endswith("-fork")
                else 50 * block_time
            )
            if new_block_timeout is None
            else new_block_timeout
        )

I'm not sure how to tell silverback that the anvil chain block time is 2.
Request / Ask
Is there a way to tell silverback/ape that the ad-hoc's block time is X?

You can add new_block_timeout kwargs to app.on_ decorators, but in general make sure when you run anvil you are running it in a mode where it continuously mines blocks and not based on transactions occuring (e.g. "automine" functionality)

Some further information: Silverback uses Ape's config system to detect timing, falling back to automatic detection if not available
https://github.com/ApeWorX/silverback/blob/8b22872a44afaf54c0c71487808a6418f8c1be77/silverback/middlewares.py#L9-L18
So make sure you've configured Ape correctly


Format http file

Currently comments are left while formatting.

traversing is a tricky part, textx is not providing, its excluding comments while traversal. we have to implement our own traversal.
keeping current line number, we have to format.

Farmateer already available, except for removing comments, upon future interest it can ve reopened


Python UDF Occasionally Hangs at Job Submission

It has been noticed on production server recently that Python UDF would be stuck at "Submitting" after starting the workflow. It happens randomly when worker number is below 8, and when worker number is set to a higher value, the chance of Python UDF hanging is higher. This could happen on any workflow.
Will add more backend details if I find it to happen again.

I tested on my local machine and it successfully ran 16 and 32 workers without encountering this issue. I believe the root issue is that the new Python processes need time to establish a connection with Java. With more workers, more Python processes are started and need to be connected, which can cause delays. Currently, we use a timeout strategy in case of an unconnected Python UDF process. For a short-term solution, we can increase the timeout to reduce the likelihood of this issue happening.

#2030 Solve this issue.


BugFix: fatal error when the delta writer is busy

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #3877
Problem Summary(Required) ：

This PR make retry when the AsyncDeltaWriter is busy to avoid the bthread's fatal error.

@mergifyio backport branch-2.1


Add reverse zip feature to pdfzip.py [-r]

I added a reverse zip feature in order to be able to merge a multiple page document which is scanned with a non-duplex scanner. In this case you get e.g. one pdf with pages 1,3 and 5 and another pdf with the pages 6,4 and 2. In order to merge/zip them correctly the second pdf needs to be reversed, for which I added the -r switch.
You could directly merge 598f33b. The last commit was just to check if it merged correctly.

Hello Christian,
thanks for the PR. Looks good to me. I think this could be a good feature. Actually it makes me think of introducing a pdf_reverse script.
Greetings


Click self -> edit profile dropdown

Communicating with oneself is an unusual user pattern; it might make more sense to get, say, a link to edit ones' profile instead.

Yeah agreed. Out of

Send private message
Reply mentioning user
View private messages
View messages sent

The only really one that makes sense for the user is View messages sent.

Agreed.  Some of the others make sense, but are unlikely enough to be not particularly useful (you can, technically, send a message to yourself, and view the list of such messages).
We should be able to provide a direct link to /#settings/your-account pretty easily, so I think this is a reasonable bite-size issue.

@zulipbot claim

@zulip abandon

@zulipbot abandon

@zulipbot claim


can't run the webui

Installation went without error but when I try to run the webui:
Traceback (most recent call last):
File "C:\Users\Paul\Documents\Coding\xtts\xtts-webui\app.py", line 67, in
from xtts_webui import demo
File "C:\Users\Paul\Documents\Coding\xtts\xtts-webui\xtts_webui.py", line 3, in
from scripts.tts_funcs import TTSWrapper
File "C:\Users\Paul\Documents\Coding\xtts\xtts-webui\scripts\tts_funcs.py", line 3, in
import torch
File "C:\Users\Paul\Documents\Coding\xtts\xtts-webui\venv\Lib\site-packages\torch_init_.py", line 139, in
raise err
OSError: [WinError 126] The specified module could not be found. Error loading "C:\Users\Paul\Documents\Coding\xtts\xtts-webui\venv\Lib\site-packages\torch\lib\torch_python.dll" or one of its dependencies

there is an issue with transformers at the moment:
https://github.com/huggingface/transformers/issues/28649
the solution I have found is NOT to install 4.37.0
pip install transformers==4.36.2


Can't be used with @formkit v1.0.0-beta.9

After upgrade to beta-9 I can't start the application.

Breaking changes

Composables from @formkit/inputs have been replaced with "sections". This should only affect users who were creating their own inputs from pre-existing composables.

Composable useSchema require a function as first param.
Can you fix it or tell how to do that and I can make a PR?.
Thanks

Hi, thanks for the report, I'll gonna have a look at it tomorrow morning.

This issue should be fixed with version 0.3.3. Please be aware depending on the version you used before, that I changed the single image input behaviour to only return a string as value instead of an object.

Great @kgierke many thanks, I will update!


Can't roll back

Rancher Server Setup

Rancher version: 2.6.5
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): ACK

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.18.8
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): aliyun

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:
Admin and/or Standard User

Describe the bug

When deploying Deployment through the yaml file, the new version of rancher must specify workload.user.cattle.io/workloadselector to roll back on the UI interface, otherwise it will report an error that the tag cannot be found.
Deployment.apps "nginx-deployment" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{}: `selector` does not match template `labels`

To Reproduce

Unavailable yaml file
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: nginx
  name: nginx-deployment
spec:
  replicas: 2
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
        - image: 'nginx:1.14.0'
          name: nginx
          ports:
            - containerPort: 80

or Available yaml files
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: nginx
    workload.user.cattle.io/workloadselector: nginx
  name: nginx-deployment
spec:
  replicas: 2
  selector:
    matchLabels:
      workload.user.cattle.io/workloadselector: nginx
  template:
    metadata:
      labels:
        app: nginx
        workload.user.cattle.io/workloadselector: nginx
    spec:
      containers:
        - image: 'nginx:1.13.0'
          name: nginx
          ports:
            - containerPort: 80

Result
Expected Result

Unavailable yaml files can rollback versions
Screenshots

Additional context

We have the same issues on our cluster. By rollback rancher is adding a label "pod-template-hash" to selector.matchLabels which is forbidden since k8s v1.20 (selector labels are immutable)
As a workaround you can still use the old rancher ui or use kubectl commands
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-back-a-deployment
It would be nice if we could have a fix for the next release as we don't want to rely on the old UI anymore

I also encountered it. Why didn't anyone fix it

same problem here:
https://github.com/rancher/rancher/issues/39103

I had the same problem

Confirmed using rancher v2.6.3 kubernetes v1.20.14 rke v1.3.6
Switching to the old interface (./g) fixes the problem.


[Bug Report]: build tiny-vue error

Steps to reproduce
https://github.com/opentiny/tiny-vue/issues/1881
Reproduce link
No response
What is actually happening?
error
System Info
normal

fixed in<EMAIL_ADDRESS>


Creating a To-Do-List Using JavaScript

Creating a To-Do-List Using JavaScript, and the frontend in Bootstrap

Greetings Mam,
Please assign this issue to me.

Thanks.

Mam I have raised the PR, please review it ,
Thanks.

Please assign this issue to me


add support for ARM64 in build-tools Dockerfile

Signed-off-by: Xoán Mallón<EMAIL_ADDRESS>
Initial implementation of changes to add support for ARM64 in build-tools Dockerfile
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) (if applicable)
[x] Changelog has been updated and is aligned with our changelog requirements

Fixes #

Relates to #3092

Looks good in general. Do you have plans to update the already existing CI to use the new build-tools? Maybe in another PR after this to ensure it works?

Yes, once is published the new image with multiarch available I would like to change the github actions workflow for validation to use a matrix for check in both architectures. WDYT?

Due problems to install fossa-cli in build-tools image with ARM, it was moved the installation to the github action workflows defined in .github/workflows/fossa.yml, also it was deleted the container section because it was failing with the container section defined with build-tools image like in this execution. Without the container works fine like in this execution WDYT?

Thanks a lot for the ARM support!


Annotate all unsafe blocks with a safety comment and prevent regressions

As part of #61, we need to make sure that all unsafe code is proven to be sound. Currently, all unsafe code is either documented with a safety comment (// SAFETY: ...), or is marked with a TODO that references this issue. Our goal is to reach 100% safety comment coverage, and to not regress once we've reached 100%. To that end, we enforce the clippy::undocumented_unsafe_blocks lint to prevent regressions.
A note on linting: It'd be nice to be able to replace the top-level #![deny(clippy::undocumented_unsafe_blocks)] with a forbid once all TODOs are burned down, but unfortunately our safety_comment! macro relies on the ability to use #[allow(clippy::undocumented_unsafe_blocks)], so we have to settle for a deny.
In order to ensure that our soundness is forwards-compatible, safety comments must satisfy the following criteria:

Safety comments must constitute a (possibly informal) proof that all of Rust's soundness rules are upheld
Safety comments must not rely on any statements which do not appear in the stable versions of the Rust reference or standard library documentation (ie, the docs for core, alloc, and std); arguments which rely on text from the beta or nightly versions of these documents are not considered complete
All statements from the reference or standard library documentation which are relied upon for soundness must be quoted in the safety comment. This ensures that there is no ambiguity as to what aspect of the text is being cited. This is especially important in cases where the text of these documents changes in the future. Such changes are of course required to be backwards-compatible, but may change the manner in which a particular guarantee is explained.

Mentoring instructions

[ ] Easy tasks

[ ] Find any safety comment which links to a version of the Rust reference or stdlib docs that uses a beta or nightly link, and replace it with a link to the stable version of the same docs

[ ] Medium tasks

[ ] Find any safety comment which cites the reference or stdlib docs without quoting the text it is citing. Fix this by quoting any text on which the safety comment relies for soundness.

[ ] Hard tasks

[ ] See the list of suggested TODOs at the bottom of this issue, or find any instance of TODO(#429) in a comment; leave a GitHub comment on this issue to claim that instance to avoid duplicated work. Write a safety comment that abides by the requirements listed above.

Feel free to ask for help here if you're stuck or have questions!
List of suggested safety comments

List
This list contains safety comments which are good starter safety comments if you're not already familiar with writing them.

[ ] https://github.com/google/zerocopy/blob/f001cf24c0dba5c396c691236a5d347270ea6066/src/lib.rs#L757-L767
[ ] https://github.com/google/zerocopy/blob/f001cf24c0dba5c396c691236a5d347270ea6066/src/lib.rs#L757-L767

Yes! We have ~20 instances of #[allow(clippy::undocumented_unsafe_blocks)] in our codebase. If you're interested in driving that number down, I recommend you tackle them (at first) one-at-a-time. We have a high bar for safety comments, and it can take some practice to get the hang of. See the comments in ptr.rs for examples of the sort of safety comments we're looking for. Comments should, ideally:

enumerate the safety preconditions of the function, and explain why each one is satisfied
whenever possible, cite official Rust documentation regarding guarantees made by the language
when such guarantees are absent, document the absence of the guarantee and link to an issue in the zerocopy repo tracking getting that guarantee in writing somewhere official.

Yes, I am interested in this, thank you!

Can I work on this if this is still open?


duplicate instructions

section 6 (in the 2nd set of steps) in 'Configure Certificate Superseding for the Domain Controller Authentication (Kerberos) Certificate Template' is duplicating the instructions found immediately after in 'Unpublish Superseded Certificate Templates'

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

ID: 800b8090-65a9-da9f-a930-1f80dc9f2c2d
Version Independent ID: b4495b6a-4ca5-7aa1-7964-ef6e19275c4e
Content: Configure Hybrid Azure AD joined key trust Windows Hello for Business - Microsoft 365 Security
Content Source: windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md
Product: w10
GitHub Login: @mapalko
Microsoft Alias: mapalko

Possibly 4 years old information, depending on which individual parts of the text you refer to.
Original document, from commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/1ef5e46e08c1a1c1a727b31348eaebf17cf12835:

https://github.com/MicrosoftDocs/windows-itpro-docs/commit/1ef5e46e08c1a1c1a727b31348eaebf17cf12835#diff-83898d1110fb9584b454946a4426718dc93edd60c15173fabc6ae4c2c42dc733

Configure Hybrid Azure AD joined Windows Hello for Business: Public Key Infrastructure blame view (hello-hybrid-key-whfb-settings-pki.md):

https://github.com/MicrosoftDocs/windows-itpro-docs/blame/public/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md

I don't think the original author (Mike Stephens) is available, at least not easily as a GitHub user.
Maybe @mapalko could share some insight or views on this matter?

@bobert13581 I would say that section 6 (in the 2nd set of steps) in 'Configure Certificate Superseding for the Domain Controller Authentication (Kerberos) Certificate Template' is exposing directly how to unpublish the certificate templates you included in the superseded templates list, while the subsequent section is dedicated to unpublishing Superseded Certificate Templates and provides comprehensive details about how to do that (which include what was already stated).
I don't think it's needed to remove anything.


Monica errors after initial deploy

After successful deploy of a Monica stack from App Templates, the monica-app container displays this error:
INFO  Application key set successfully.
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36
Waiting for database to settle...
Waiting for database to settle...
Warning: mysqli::__construct(): php_network_getaddresses: getaddrinfo for db failed: Name or service not known in Standard input code on line 36

See: https://github.com/Lissy93/portainer-templates?tab=readme-ov-file#raising-issues
Issues relating to specific images need to be raised upstream.
This repo just collates templates listed in the Sources into a single manifest, so once a fix has been pushed out upstream, it will be available here.


Rest Trigger and Files

Currently the rest trigger does not handle requests containing files. Should we add that feature in the main Rest trigger?  Or should we have a different trigger to handle files ? @fm-tibco @mellistibco @abramvandergeest can you share your thoughts on this?
Currently, https://github.com/skothari-tibco/contrib/tree/rest_image/trigger/rest supports a single file. We can change it to handle multiple files.
Changes to the current trigger will include. Adding file setting in handler settings. And the type of the  content would be map[multipart.FileHeader]multipat.File. We can also discuss on the format of output.
file setting in the handler setting will be the key which contains the files in the Http request.The Http request should of type multipart/form-data
The reason there is multipart.FileHeader as a part of output because it contains the name, type and size of the file. Getting this information form the multipart.File only would not be possible.

I think it makes sense to add the ability to add multiple files to a REST request makes sense, and to have it in the main rest trigger.  I think that being able to send one file is a must with additional files being good but of lower priority (unless it makes sense to just do it that way from the beginning).


rtext: added functions for camel case and snake case

Adds functions for converting text to camel and snake case to match the addition of a pascal case function. Both have been tested against each other's conventions.

Hello,
Please, could this PR not be merged on its current state. It has 1126 changes on rtext.c and 2,685 on raylib.h. It breaks current code conventions and it's too taxing to review.
Best regards.

@asdqwe Agree with mentioned points.


Deleting a draft returns you to the dashboard

When I went into my drafts to delete some old ones, the delete was successful, but I was returned to the dashboard and had to navigate back to drafts.

Where would you prefer to end up instead? To stay in drafts? (double-checking I understand you)

For now, I think best would be to stay in drafts with no particular draft selected.


[Bug]: postInitApplicationSQLRefs configmap not executed as expected?

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
<EMAIL_ADDRESS>Version
1.21.0
What version of Kubernetes are you using?
1.28
What is your Kubernetes environment?
Self-managed: k3s
How did you install the operator?
Helm
What happened?
We are creating a postgres cluster via the following config:
            bootstrap:
              initdb:
                database: zitadel
                owner: zitadel
                postInitApplicationSQLRefs:
                  configMapRefs:
                    - name: zitadel-init-sql
                      key: zitadel-init.sql

            enableSuperuserAccess: true

The zitadel user and database is created and the superuser account is accessible - however our .sql script does not appear to be executing properly
apiVersion: v1
kind: ConfigMap
metadata:
  name: zitadel-init-sql
data:
  zitadel-init.sql: |
    CREATE SCHEMA IF NOT EXISTS eventstore;
    GRANT ALL ON ALL TABLES IN SCHEMA eventstore TO zitadel;
    CREATE SCHEMA IF NOT EXISTS projections;
    GRANT ALL ON ALL TABLES IN SCHEMA projections TO zitadel;
    CREATE SCHEMA IF NOT EXISTS system;
    GRANT ALL ON ALL TABLES IN SCHEMA system TO zitadel;
    CREATE TABLE IF NOT EXISTS system.encryption_keys ( id TEXT NOT NULL , key TEXT NOT NULL , PRIMARY KEY (id));
    CREATE TABLE IF NOT EXISTS eventstore.events2 ( instance_id TEXT NOT NULL , aggregate_type TEXT NOT NULL , aggregate_id TEXT NOT NULL , event_type TEXT NOT NULL , "sequence" BIGINT NOT NULL , revision SMALLINT NOT NULL , created_at TIMESTAMPTZ NOT NULL , payload JSONB , creator TEXT NOT NULL , "owner" TEXT NOT NULL , "position" DECIMAL NOT NULL , in_tx_order INTEGER NOT NULL , PRIMARY KEY (instance_id, aggregate_type, aggregate_id, "sequence"));
    CREATE INDEX IF NOT EXISTS es_active_instances ON eventstore.events2 (created_at DESC, instance_id);
    CREATE INDEX IF NOT EXISTS es_wm ON eventstore.events2 (aggregate_id, instance_id, aggregate_type, event_type);
    CREATE INDEX IF NOT EXISTS es_projection ON eventstore.events2 (instance_id, aggregate_type, event_type, "position");
    CREATE SEQUENCE IF NOT EXISTS eventstore.system_seq;
    CREATE TABLE IF NOT EXISTS eventstore.unique_constraints ( instance_id TEXT, unique_type TEXT, unique_field TEXT, PRIMARY KEY (instance_id, unique_type, unique_field));

The schemas and tables seem to be created, however the grants are not applied:
Schemas:
postgres=# \dn
         List of schemas
    Name     |       Owner
-------------+-------------------
 eventstore  | postgres
 projections | postgres
 public      | pg_database_owner
 system      | postgres

Grants:
postgres=# SELECT *
postgres-#   FROM information_schema.role_table_grants
postgres-#  WHERE grantee = 'zitadel';
 grantor | grantee | table_catalog | table_schema | table_name | privilege_type | is_grantable | with_hierarchy
---------+---------+---------------+--------------+------------+----------------+--------------+----------------
(0 rows)

postgres=# SELECT *
  FROM information_schema.role_table_grants
 WHERE table_schema = 'eventstore';
 grantor  | grantee  | table_catalog | table_schema |     table_name     | privilege_type | is_grantable | with_hierarchy
----------+----------+---------------+--------------+--------------------+----------------+--------------+----------------
 postgres | postgres | postgres      | eventstore   | events2            | INSERT         | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | SELECT         | YES          | YES
 postgres | postgres | postgres      | eventstore   | events2            | UPDATE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | DELETE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | TRUNCATE       | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | REFERENCES     | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | TRIGGER        | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | INSERT         | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | SELECT         | YES          | YES
 postgres | postgres | postgres      | eventstore   | unique_constraints | UPDATE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | DELETE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | TRUNCATE       | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | REFERENCES     | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | TRIGGER        | YES          | NO
(14 rows)

postgres=#

With the superuser account enabled, I can access the data base and create them though, so it's strange that they couldnt be created during the init process.
Example:
# Schema already exists
postgres=# CREATE SCHEMA IF NOT EXISTS eventstore;
NOTICE:  schema "eventstore" already exists, skipping
CREATE SCHEMA

postgres=# GRANT ALL ON ALL TABLES IN SCHEMA eventstore TO zitadel;
GRANT

postgres=# SELECT *
  FROM information_schema.role_table_grants
 WHERE table_schema = 'eventstore';
 grantor  | grantee  | table_catalog | table_schema |     table_name     | privilege_type | is_grantable | with_hierarchy
----------+----------+---------------+--------------+--------------------+----------------+--------------+----------------
 postgres | postgres | postgres      | eventstore   | events2            | INSERT         | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | SELECT         | YES          | YES
 postgres | postgres | postgres      | eventstore   | events2            | UPDATE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | DELETE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | TRUNCATE       | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | REFERENCES     | YES          | NO
 postgres | postgres | postgres      | eventstore   | events2            | TRIGGER        | YES          | NO
 postgres | zitadel  | postgres      | eventstore   | events2            | INSERT         | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | events2            | SELECT         | NO           | YES
 postgres | zitadel  | postgres      | eventstore   | events2            | UPDATE         | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | events2            | DELETE         | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | events2            | TRUNCATE       | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | events2            | REFERENCES     | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | events2            | TRIGGER        | NO           | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | INSERT         | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | SELECT         | YES          | YES
 postgres | postgres | postgres      | eventstore   | unique_constraints | UPDATE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | DELETE         | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | TRUNCATE       | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | REFERENCES     | YES          | NO
 postgres | postgres | postgres      | eventstore   | unique_constraints | TRIGGER        | YES          | NO
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | INSERT         | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | SELECT         | NO           | YES
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | UPDATE         | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | DELETE         | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | TRUNCATE       | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | REFERENCES     | NO           | NO
 postgres | zitadel  | postgres      | eventstore   | unique_constraints | TRIGGER        | NO           | NO
(28 rows)

is there any extra logging that can be referenced to see if there were issues in running the .sql script? Perhaps I'm missing something obvious, any help is appreciated. Cheers!
Cluster resource
Name:         zitadel-postgres
Namespace:    zitadel
Labels:       argocd.argoproj.io/instance=zitadel-postgres-cluster
Annotations:  <none>
API Version:  postgresql.cnpg.io/v1
Kind:         Cluster
Metadata:
  Creation Timestamp:  2023-11-13T12:05:58Z
  Generation:          1
  Resource Version:    1785063
  UID:                 1ae43315-52b5-4f94-9913-44b084965ee1
Spec:
  Affinity:
    Pod Anti Affinity Type:  preferred
  Backup:
    Barman Object Store:
      Destination Path:  s3://zitadel
      Endpoint URL:      https://zitadel-minio.buildstars.online
      s3Credentials:
        Access Key Id:
          Key:   ACCESS_KEY
          Name:  zitadel-db-credentials
        Secret Access Key:
          Key:         SECRET_KEY
          Name:        zitadel-db-credentials
    Retention Policy:  30d
    Target:            prefer-standby
  Bootstrap:
    Initdb:
      Database:        zitadel
      Encoding:        UTF8
      Locale C Type:   C
      Locale Collate:  C
      Owner:           zitadel
      Post Init Application SQL Refs:
        Secret Refs:
          Key:   init.sql
          Name:  zitadel-postgres-init-script
  Certificates:
    Client CA Secret:        zitadel-postgres-client-ca-key-pair
    Replication TLS Secret:  zitadel-postgres-client-cert
    Server CA Secret:        zitadel-postgres-server-ca-key-pair
    Server TLS Secret:       zitadel-postgres-server-cert
  Enable Superuser Access:   false
  Failover Delay:            0
  Image Name:                ghcr.io/cloudnative-pg/postgresql:16.0
  Instances:                 1
  Log Level:                 info
  Max Sync Replicas:         0
  Min Sync Replicas:         0
  Monitoring:
    Custom Queries Config Map:
      Key:                    queries
      Name:                   cnpg-default-monitoring
    Disable Default Queries:  false
    Enable Pod Monitor:       false
  Postgres GID:               26
  Postgres UID:               26
  Postgresql:
    Parameters:
      archive_mode:                on
      archive_timeout:             5min
      dynamic_shared_memory_type:  posix
      log_destination:             csvlog
      log_directory:               /controller/log
      log_filename:                postgres
      log_rotation_age:            0
      log_rotation_size:           0
      log_truncate_on_rotation:    false
      logging_collector:           on
      max_parallel_workers:        32
      max_replication_slots:       32
      max_worker_processes:        32
      shared_memory_type:          mmap
      shared_preload_libraries:
      wal_keep_size:               512MB
      wal_receiver_timeout:        5s
      wal_sender_timeout:          5s
    pg_hba:
      hostnossl all all <IP_ADDRESS>/0 reject
      hostssl all all <IP_ADDRESS>/0 cert clientcert=verify-full
    Sync Replica Election Constraint:
      Enabled:              false
  Primary Update Method:    restart
  Primary Update Strategy:  unsupervised
  Replication Slots:
    High Availability:
      Enabled:        true
      Slot Prefix:    _cnpg_
    Update Interval:  30
  Resources:
  Smart Shutdown Timeout:  180
  Start Delay:             3600
  Stop Delay:              1800
  Storage:
    Resize In Use Volumes:  true
    Size:                   1Gi
  Switchover Delay:         3600
Status:
  Certificates:
    Client CA Secret:  zitadel-postgres-client-ca-key-pair
    Expirations:
      Zitadel - Postgres - Client - Ca - Key - Pair:  2024-02-11 08:42:35 +0000 UTC
      Zitadel - Postgres - Client - Cert:             2024-02-11 12:05:58 +0000 UTC
      Zitadel - Postgres - Server - Ca - Key - Pair:  2024-02-11 08:42:36 +0000 UTC
      Zitadel - Postgres - Server - Cert:             2024-02-11 08:42:40 +0000 UTC
    Replication TLS Secret:                           zitadel-postgres-client-cert
    Server Alt DNS Names:
      zitadel-postgres-rw
      zitadel-postgres-rw.zitadel
      zitadel-postgres-rw.zitadel.svc
      zitadel-postgres-r
      zitadel-postgres-r.zitadel
      zitadel-postgres-r.zitadel.svc
      zitadel-postgres-ro
      zitadel-postgres-ro.zitadel
      zitadel-postgres-ro.zitadel.svc
    Server CA Secret:             zitadel-postgres-server-ca-key-pair
    Server TLS Secret:            zitadel-postgres-server-cert
  Cloud Native PG Commit Hash:    27f62cac
  Cloud Native PG Operator Hash:  4912e5eb808aca3bf134923625f2346d404a3c860cf24aca4266493846f8fc3b
  Conditions:
    Last Transition Time:  2023-11-13T12:06:16Z
    Message:               Cluster is Ready
    Reason:                ClusterIsReady
    Status:                True
    Type:                  Ready
    Last Transition Time:  2023-11-13T12:06:12Z
    Message:               Continuous archiving is working
    Reason:                ContinuousArchivingSuccess
    Status:                True
    Type:                  ContinuousArchiving
  Config Map Resource Version:
    Metrics:
      Cnpg - Default - Monitoring:  1784888
  Current Primary:                  zitadel-postgres-1
  Current Primary Timestamp:        2023-11-13T12:06:07.138580Z
  Healthy PVC:
    zitadel-postgres-1
  Instance Names:
    zitadel-postgres-1
  Instances:  1
  Instances Reported State:
    zitadel-postgres-1:
      Is Primary:    true
      Time Line ID:  1
  Instances Status:
    Healthy:
      zitadel-postgres-1
  Latest Generated Node:  1
  Managed Roles Status:
  Phase:  Cluster in healthy state
  Pooler Integrations:
    Pg Bouncer Integration:
  Pvc Count:        1
  Read Service:     zitadel-postgres-r
  Ready Instances:  1
  Secrets Resource Version:
    Application Secret Version:  1784864
    Client Ca Secret Version:    1743752
    Replication Secret Version:  1784861
    Server Ca Secret Version:    1743796
    Server Secret Version:       1743864
  Target Primary:                zitadel-postgres-1
  Target Primary Timestamp:      2023-11-13T12:05:59.202824Z
  Timeline ID:                   1
  Topology:
    Instances:
      zitadel-postgres-1:
    Nodes Used:              1
    Successfully Extracted:  true
  Write Service:             zitadel-postgres-rw
Events:
  Type    Reason                       Age   From            Message
  ----    ------                       ----  ----            -------
  Normal  CreatingPodDisruptionBudget  61s   cloudnative-pg  Creating PodDisruptionBudget zitadel-postgres-primary
  Normal  CreatingServiceAccount       61s   cloudnative-pg  Creating ServiceAccount
  Normal  CreatingRole                 61s   cloudnative-pg  Creating Cluster Role
  Normal  CreatingInstance             61s   cloudnative-pg  Primary instance (initdb)

Relevant log output
No response
Code of Conduct

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

Hi @cloudymax , @jessebot
the GRANT ALL ON ALL TABLES command in PostgreSQL does not automatically extend permissions to tables created after the command is executed. This command grants permissions only to the tables that exist in the schema at the time the command is run.
You should relocate the GRANT statement to a position where the CREATE command has already been executed

Hi @cloudymax , @jessebot the GRANT ALL ON ALL TABLES command in PostgreSQL does not automatically extend permissions to tables created after the command is executed. This command grants permissions only to the tables that exist in the schema at the time the command is run. You should relocate the GRANT statement to a position where the CREATE command has already been executed

Thanks so much for the sanity-check, the issue ended up being with Zitadel having co-mingled their SQL code with some undocumented magic strings in another part of the codebase.
We've create a ticket with them to address the root issue, so we can close this thread.
Thanks again!


fixed an issue that cause the overview chart to be slow to display

I think the issue is related to the $digest cycle, so it seems that the chart waits for the next cycle to be displayed..
So I'm not sure if this is the best solution, but it does make the chart display faster

Codecov Report

Merging #495 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #495      +/-   ##
==========================================
- Coverage   31.29%   31.28%   -0.02%
==========================================
  Files          20       20
  Lines        1981     1982       +1
  Branches      235      235
==========================================
  Hits          620      620
- Misses       1313     1314       +1
  Partials       48       48

Impacted Files
Coverage Δ

app/scripts/controllers/overview.js
0.96% <0%> (-0.01%)
:arrow_down:

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 e0d28ed...5625cf9. Read the comment docs.


wasm: fix network leak (#13836)

Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>Signed-off-by: Kuat<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

https://github.com/istio/istio/issues/24720

https://github.com/istio/istio/issues/24720

/lgtm
/approve

/lgtm
/approve

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
df6f749fd6847ad8e5fe03318802f54b89911186
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
df6f749fd6847ad8e5fe03318802f54b89911186
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
df6f749fd6847ad8e5fe03318802f54b89911186
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
df6f749fd6847ad8e5fe03318802f54b89911186
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
df6f749fd6847ad8e5fe03318802f54b89911186
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
df6f749fd6847ad8e5fe03318802f54b89911186
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

/retest

/retest

I probably will just disable the test for now. There is no meaning to keep retrying a 100% failing flaky test.

I probably will just disable the test for now. There is no meaning to keep retrying a 100% failing flaky test.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
3731665a0544f594dfe373e313ec7a3658df2959
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
3731665a0544f594dfe373e313ec7a3658df2959
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Ok great.. now it fails because of a different reason:
ERROR: Analysis of target '//:envoy_binary_test' failed; build aborted: Analysis of target '@envoy//bazel/foreign_cc:zlib' failed
INFO: Elapsed time: 15.665s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (376 packages loaded, 2575 targets configured)
ERROR: Couldn't start the build.  Will retry it one more time, if it still fails, we should make tsan non-required and debug it afterwards.

Ok great.. now it fails because of a different reason:
ERROR: Analysis of target '//:envoy_binary_test' failed; build aborted: Analysis of target '@envoy//bazel/foreign_cc:zlib' failed
INFO: Elapsed time: 15.665s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (376 packages loaded, 2575 targets configured)
ERROR: Couldn't start the build.  Will retry it one more time, if it still fails, we should make tsan non-required and debug it afterwards.

/retest

/retest

You could add flaky_test_attempts if it's really bad. Some tests are flakey even without Tsan.

You could add flaky_test_attempts if it's really bad. Some tests are flakey even without Tsan.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
3731665a0544f594dfe373e313ec7a3658df2959
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.7
3731665a0544f594dfe373e313ec7a3658df2959
link
/test test-tsan_envoy_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

https://github.com/istio/test-infra/pull/3160

https://github.com/istio/test-infra/pull/3160

/retest

/retest


Edge does not support matchAll

tested with
const regexp = RegExp('foo[a-z]*','g');
const str = 'table football, foosball';
const matches = str.matchAll(regexp);

According to this, it does since v79 (which was released in January, according to wikipedia and seems to be the first chromium based version of edge)
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/matchAll
I've been lookging at polyfill for matchAll in order to try and include it somehow but it seems overly complicated to support an old version of a browser that most people don't use (and shouldn't use).
There's two alternative possibilities of doing a 'g' regexp match with capturing groups, and they are explained in the proposal for matchAll : https://github.com/tc39/proposal-string-matchall
Note however that Foundry itself uses the same matchAll to find all the entity links in the journal entry, so that would still crash I think.

Closing since I have no intentions of using an alternative to matchAll considering that Foundry itself uses it already, so links in journals are already broken in Edge, and a new version of Edge supports it.


Another codecov test

Current coverage is 70.74%

Merging #2 into master will change coverage by +70.74% by 72d9582

Powered by Codecov

Current coverage is 70.74%

Merging #2 into master will change coverage by +70.74% by 72d9582

Powered by Codecov

Current coverage is 70.74%

Merging #2 into master will change coverage by +70.74% by 72d9582

Powered by Codecov

Current coverage is 70.74%

Merging #2 into master will change coverage by +70.74% by 72d9582

Powered by Codecov

Current coverage is 70.74%

Merging #2 into master will change coverage by +70.74% by 72d9582

Powered by Codecov


Unfolds request headers that are using obs continuations

This also removes a duplicated test file, that's not used / necessary. This reopens the old PR #1078.

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/158/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/173/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1854/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/155/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/284/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1744/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/417/

@bryancall Do we want this back ported to 7.1.x ?

@zwoop Yes, I think it should be backported.


tests: kernel: timer: timer_behavior: Tweak expected std deviation

If frequency of the system clock is lower then deviation may exceed default value (10us). Instead of adjusting the default value, test is rounding up expected standard deviation to a single clock cycle.
Fixes #71863.

I like the change, agree with @golowanow the calculation should be done once before the TC_PRINT and zaasert usage

@andyross @peter-mitsis please review


bug: transcribing with medium model

OS: Mac Ventura
Seems like with the tiny model, transcription works, but when using the medium you get a buffer size error. Perhaps we could do chunking
     Running `target/release/whisper audio.wav medium`
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_bind_group
    Buffer binding 0 range 212439040 exceeds `max_*_buffer_binding_size` limit 134217728

', /Users/botch/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.17.0/src/backend/direct.rs:3056:5
stack backtrace:
   0: rust_begin_unwind
             at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/panicking.rs:578:5
   1: core::panicking::panic_fmt
             at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/panicking.rs:67:14
   2: core::ops::function::Fn::call
   3: <wgpu::backend::direct::Context as wgpu::context::Context>::device_create_bind_group
   4: <T as wgpu::context::DynContext>::device_create_bind_group
   5: wgpu::Device::create_bind_group
   6: burn_wgpu::context::base::Context::execute
   7: burn_wgpu::kernel::index::select::select
   8: burn_tensor::tensor::ops::modules::base::ModuleOps::embedding
   9: whisper::model::Whisper<B>::forward_decoder
  10: whisper::main

Update
Using a six-minute audio file with the tiny model produces the same issue.

Chunking is the next planned feature. Right now it clips audio to around the first 30 seconds for the encoder, but the decoder sequence length isn't limited so it will overflow if it doesn't detect the end by the 30 second mark.

Rudimentary chunking is now implemented. Your long audio files should now work, although there is some minor transcription inaccuracy around the chunk edges. I tried incorporating the last few tokens from the previous chunk into whisper to remedy the chunk edge issues but then whisper severely repeats itself and stops predicting the end of chunks so I had to revoke that change. Any ideas why whisper is so finicky when exposed to tokens from the previous chunk?

Mint

whisper is so finicky when exposed to tokens from the previous chunk

sounds like Whisper hallucination it happens in other implementations as well. I would have to dig into this one...


Still in preview?

Hi, is this still in preview?  Any word on a official release date?

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

ID: c51a742c-4ddb-dd5e-7f67-3242a158378a
Version Independent ID: b5d96164-bec6-7732-79ad-8c6beef7e0c4
Content: Create a Node.js Office Add-in that uses single sign-on - Office Add-ins
Content Source: docs/develop/create-sso-office-add-ins-nodejs.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@Joel-Intact Thanks for your patience. We are actively working to GA SSO API. May I know how do you plan to use the SSO API? Do you need it to access Graph? Also, how do your users expect to get your add-in - via store or centralized deployment?

Hi @niteshgolchha85, thanks for responding to my inquiry.  It's good to hear that this is being actively worked on!  We're planning on using the SSO API to get an access token for the logged on user, and call our web services to send/receive data.  For Graph, I would just call the "me" endpoint passing the token to get data.  For deployment, both, mostly store and centralized deployment for clients with restrictions.

Thanks @Joel-Intact for the info. As I've mentioned earlier, I do not have a specific date yet but we'll make a public announcement once we plan to go GA


SQL Support

We are trying to  use the tool with SQL Server as data source, with numeric field, latitute and longitude, and with the below json. The json is copied from the example. However we could not display any points on the map. Is there a walkthrough or a sample case for SQL Server?
https://raw.githubusercontent.com/dogugun/fastq/master/geojsonbulut

Did you find a way to use SQL?

Nope, we had to switch to grafana's default map add-on.

Hi! is there any posibility to make it work with MSSQL or MySQL databases? I have an issue in the measurement assigment. The hole map is black. Also I see there is an issue on the png of the color selection. I can't find a column name that GeoLoop would take as measurement.

Hi! Has anybody managed to get it working? We're trying to set it up with clickhouse db with no luck...


Example: cce_planar fails

Traceback (most recent call last):
  File "E:\intership\Scarce-master\scarce\examples\cce_planar.py", line 226, in <module>
    myfile.append('Fluence\tBias\tN_eff_0\tN_eff\tt_e\tt_h\n')
AttributeError: 'file' object has no attribute 'append'

'''
Traceback (most recent call last):
File "E:\intership\Scarce\scarce\examples\cce_planar.py", line 242, in
t_h_trappings=t_h_trappings)
File "E:\intership\Scarce\scarce\examples\cce_planar.py", line 102, in cc_efficiency
pot_w_descr=pot_w_descr, mesh=mesh, smoothing=smoothing, pot_descr=pot_descr)
ValueError: need more than 2 values to unpack
'''


upload file not work when file input field contains multiple

for element

          iframe.file_field(:name, 'fileUploadInput').set photo
          ap iframe.file_field(:name, 'fileUploadInput').value
          ap iframe.file_field(:name, 'fileUploadInput').files

the message outpus is
"C:\\fakepath\\95668267-8c1f-4015-a471-460940b207ef.JPG@534w_340h_1e_1c_2o"
""

the problem is that the element's files is empty, so the callback which handle event.target.files not work.
For single file element, it works
<input style="display: none" type="file" name="imageLoad" id="carloadimage" onchange="return ajaxFileUpload();">

Can you create a test script which I could run to reproduce the problem? It is probably a selenium-webdriver issue, but let's check first.

Closing this due to inactivity.
Please, reopen if still an issue.


Handle possible conflict in updating test labels on cluster

What this PR does / why we need it:
The test on master after the last PR push seems to be failing because of a test flake. This PR fixes that
Ref: https://github.com/kubernetes-sigs/kubefed/runs/5593998914?check_suite_focus=true
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Test fix
Special notes for your reviewer:

@hectorj2f there was an update needed. Need LGTM label again. Thanks.

/approve

/lgtm


Add output related to configureSshConfig while creating a VM

I'd like to see stuff in the output that we're creating an ssh key and modifying their ssh config file. We're doing some magic here to make things simpler for users, but I think that makes logs more important.

What do you think about this?

I tried displaying the output of ssh-keygen but it looks real nasty.
The appending new entry line looks pretty bad with the floating quote and I'll fix that.  But I'm more curious if you think I should print off the whole entry or not.  Also would it be useful if we could hyperlink their config file to just let the user open it?

But I'm more curious if you think I should print off the whole entry or not

Seems excessive

Also would it be useful if we could hyperlink their config file to just let the user open it?

Sure


fix(postgres): ignore non-select queries

closes https://github.com/roapi/roapi/issues/180

enabled auto-merge (squash)

lol, that's why so instant


Incorrect texelFetch emitted for sampler2DMS

I compiled this shader with glslang:
#version 420  uniform sampler2DMS colorBuffer;  layout(location = 0) out vec4 outColor;  void main(void)  {     outColor = texelFetch(colorBuffer, ivec2(gl_FragCoord.xy), 0);  }
This compiles successfully but when compiled back to GLSL with SPIRV-cross it produces this:
outColor = texelFetch(colorBuffer, ivec2(gl_FragCoord.xy));
which will fail with "'texelFetch' : no matching overloaded function found".

Fixed on master.

It works now, thanks.


ImportError: No module named numpy.distutils.core

Traceback (most recent call last):
File "setup.py", line 5, in
from numpy.distutils.core import setup
ImportError: No module named numpy.distutils.core
When I follow your step, but why I have the Error?

Traceback (most recent call last):
File "setup.py", line 5, in
from numpy.distutils.core import setup
ImportError: No module named numpy.distutils.core
When I follow your step, but why I have the Error?

I fail in same issue, do you remember how to solve this?


"compose" is not optimal as name for the executable

This is not a real bug, but I do not like the name "compose" for the executable as there is already a Unix command "compose".
I would prefer something like "sbom-compose".
man compose

RUN-MAILCAP(1)                                         Run Mailcap Programs                                         RUN-MAILCAP(1)

NAME
       run-mailcap, view, see, edit, compose, print - execute programs via entries in the mailcap file

SYNOPSIS
       run-mailcap --action=ACTION [--option[=value]] [MIME-TYPE:[ENCODING:]]FILE [...]

       The  see, edit, compose and print versions are just aliases that default to the view, edit, compose, and print actions (re‐
       spectively).

Thank you for pointing out @vargenau !
What makes most sense in this case is scompose. Do you have any objections or another proposal?

I would prefer "sbom-compose" or "sbomcompose" that is more explicit.
Or "spdx-compose", "spdxcompose".

Addressed in Change compose command


revert bad @trusted

Range.opSlice might be unsafe. _input[a .. b] can't be @trusted.
Partially reverts #6866. CC @WalterBright @wilzbach

The auto-tester doesn't like this. Full revert then: https://github.com/dlang/phobos/pull/6870


Not Loading / slow

Hi Folks, workbench seems super slow today. I'm getting application timeouts and unresponsive soql queries

I'm having similar but maybe unrelated issues today, October 4th. I've been regularly (but inconsistently getting this error logging in and after getting in, with any query request:

I am having some issues with workbench today too, just tried to pull Id from Account in a dev org I have that has relatively small number of accounts and even that is timing out.
I am glad to see it isn't just me, I was originally getting the error while trying to set up a job and thought I did something wrong. It appears workbench is just having some issues today...

Update on this... it appears the jobs I opened via workbench are in my org, so the request is going through, I am just not getting the response in workbench.

I just bounced the servers and it seems to be ok now.


Multi-piece shipment support?

Does activeshipping gem supports creating of multi-piece shipment?
Example:
Our customer orders 2 pieces of item X. When we ask UPS/Fedex to ship the order of the customer, we need UPS/Fedex to give us 2 shipping labels instead of just 1 shipping label. Is there a way to do this using ActiveShipping gem?

If you perform a rate request with 2 packages, it will rate them as being on a single label (sometimes called master label). So you just need to do 2 separate find_rates calls with your separate packages.
Then the per label surcharges will be applied to each and sum the results by the service code to see the overall shipping price.
So yes, the gem supports this,  the api's by the carriers don't make it a single api call.

@developingchris Thanks for the response.
So for example our customer orders 2 pieces of item X, this is what we need to do:
response1 = ups.find_rates(origin, destination, package_x)
response2 = ups.find_rates(origin, destination, package_x)

# sum the rates of response1 & response2 by service code (Example: UPS Standard)

Is that correct?
Before you responded to my question, this is what we're doing btw:
packages = [package_x, package_x]
response = ups.find_rates(origin, destination, packages)

Since the customer orders 2 pieces of item x, instead of passing packages = [package_x] with quantity of 2, we're passing `packages = [package_x, package_x] with package_x having quantity of 1.
Wouldn't it give the same result with your suggestion above?

so if you pass both packages to a single call. Then the shipping company will put both boxes on a single label.   The carriers in my experience have a base fee per label.   So it depends on how you want to pay for the labels. If the customer needs to pay the base fee on both boxes, then you need to do the merge way.  If you want to provide the cheapest options available they can be a single label with "box 1 of 2" "box 2 of 2" labels on them as a set. In that case you would use what you are doing, passing 1 packages into the rate quote.
@jonathankwok  has been looking into the idea of a Shipment concept which would make this more clear.


tests/core/audit_test.py is flaky on py35

See this travis job for more details.
Looks like this test is non-deterministic, and we should fix it -- but the simple fix now is just to kick off that test again.

v1 deprecates the use of py35. Closing as "Won't Fix".


Expectation of timeline for Azure PubSub service GA release

Looking to determine if there is any expected timeline for the GA release of this service.
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5510a25f-3329-56aa-6f6d-f6068090413a
Version Independent ID: 31650e01-1730-710d-c7e4-7852b80fd01d
Content: What is Azure Web PubSub service?
Content Source: articles/azure-web-pubsub/overview.md
Service: azure-web-pubsub
GitHub Login: @yjin81
Microsoft Alias: yajin1

@01 Thanks for the feedback! We are currently investigating and will update you shortly.

@01 We have completed our research and wanted to share the below update with you.
As of right now, GA dates are only shared with the public via the Azure Roadmap site, which can be found here. As of right now, there is not a publicly shared GA date.
With that being said, the team is working hard on launching the service and reaching the GA milestone.
Most Azure products seem to go GA around our two major events. //Build, which is normally around May of each year. The second event is normally Ignite, which is happening in early November this year. I would keep an eye out for any GA announcements at Ignite this year. More information on Ignite can be found here. (Please note this is not suggesting a GA date for Azure Web PubSub. This message is merely observing when previous products went GA.)
Please let us know if you have any further questions or concerns.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update logic for how button is rendered

Jira ticket
Summary
This ensure that only one button is shown for users that have multi roles.
Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the office app as a TIO to find a move that has a status of payment requested and make note of the move locator code.
Using that code login as TIO and you should see the button enabled (you may have to review the weights)
Login as the TOO and find the same move using the move code. You should see that the button is disabled.
Login as a multi user and find the same move using the move code. You should only see one instance of the button and it should appear in the same state as the TIO.

Screenshots

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 624334780b4e3139c166e823e5c6ebfe87c6725a


Adding Hessians to Component

I notice that components only include values, bounds, and jacobians. Is there any reason Hessians are not stored in them as well, other than you just didn't need it?
We are considering using this library for a project, and a lot of the solvers we'd like to interface to accept hessians. I'm not entirely sure how this would look. I suppose it could actually go in CostTerm?

Yes, I just didn't use them, mostly because it was quite difficult to determine their analytical values for the problem I was solving. But they could be included in ifopt as well.
From the structure I would add a function "GetHessian()", that's callable on a cost-term, as well as on a constraint-set. That would be the 2nd derivative (3 dimensional matrix, right?), just as the function "GetJacobian()" supplies the first derivative (2d). The image here at the bottom might help: http://docs.ros.org/api/ifopt/html/group__ProblemFormulation.html

Ok that makes sense. I was not sure about the 3D matrix. I suppose for constraints it would have to be. I'm not an optimization guy. It seems like many of them only really care about the hessian of the objective function which could then just be 2D. But I could be completely wrong about that.

Hi, any progress here?
My understanding of non-linear interior-point optimization is that you only reason on 2d order derivatives for the objective, which is a simple matrix. The jacobian of the objective would actually be just the transpose of the gradient, so a vector. The same should apply for SQP:  "SQP methods solve a sequence of optimization subproblems, each of which optimizes a quadratic model of the objective subject to a linearization of the constraints" (cf. wikipedia).
To have exact Hessians passed in, what would one need to change to ifopt?
Thanks in advance.

While I am still interested, I have not looked into implementing this any more.

I went looking for this capability today since the problem I'm working on can efficiently compute an analytical Hessian matrix and I'm enjoying the ease of use ifopt provides. It seems like the current status is still open so I started to take a stab at it, naively searching for the word "Jacobian" and extending the code as needed. It will take some further investigation to make sure there aren't any nuances I skipped over.
This link indicates that the Hessian of the whole Lagrangian is need, that is the Hessian of the objective function and the constraints so both Components will need to be extended. From what I understand they should all be simple matrices (rank-2 tensors) as well.

Hi all,
Any update on this? Did somebody implement this and wants to provide the code extensions needed?


A quick question everyone concerns.

Is the IntermLM 7B the only one open to the community, larger models are commercially licensed?

We are developing models at different scales, and have a multi-stage release plan. InternLM-7B can serve as a solid starting point for both research and practical applications. We appreciate any community feedback.


Move Issuer / ClusterIssuer and Certificate resource content to a sub-folder of configuration/

Preview: https://deploy-preview-1075--cert-manager-website.netlify.app/
Part of the https://github.com/cert-manager/website/pull/1048 where we presented an improved overall navigation structure for the site.

Moved configuration/* > configuration/issuer-and-clusterissuer-resources/*
Moved usage/certificate > configuration/certificate-resources
Updated all the affected links within the site.
Added redirects for the benefit of people linking to our site
Improved the page descriptions and opening paragraphs of each of the Issuer type pages and the certificate resource page
Added a list of all the issuer types to the configuration/issuer-and-clusterissuer-resources/ homepage, because the side menu is not always expanded when you visit that page.

/cc @maelvls @mehak151 (and @jsoref ...if you have time)

This has been solved in an alternative way.
TODO: recover the changes made in the following files & apply them to the new website structure (if possible)

content/docs/configuration/README.md
content/docs/configuration/certificate-resources.md
content/docs/configuration/issuer-and-clusterissuer-resources/README.md


Upload coverage data to Codecov

LGTM,   CI failed because youtube change the cipher function again... I will fix later
Thanks for contribution!


Add option to build manifest into build folder

Could you please add an option to be able to build the manifest.json into the build folder rather than having it in the root folder?

No plans to add this feature as an option at this time