Ignore backup files (ones with .n.old suffix) in download_missing

This is rather a hack to resolve immediate issue:
https://github.com/neondatabase/neon/issues/3024
Properly cleaning this file from index part requires changes to initialization of remote queue. Because we need to clean it up earlier than we start warking around files.
With on-demand there will be no walk around layer files becase download_missing is no longer needed, so I believe it will be natural to unify this with load_layer_map
@problame wdyt? Should I clean this up now or it will only introduce unnecessary conflicts with on-demand patch?

Plan to merge this tomorrow morning and then check affected project on staging


review and refactor IAndroidUtils methods

let's test all methods we provide in IAndroidUtils using latest 7.1.6 carina (some of them seems unsupported now)
review MobileDriver (iOS and Android independent) changes and move as much as possible commands into iMobileUtils

[#1399] is just a hotfix. @DimaGrinevich, please review all methods and if it ispossible to move them into the IMobileUtils

merge is planned for 7.2.x only


bugfix:2.6.0修改触发器有权限无法删除错误

Codecov Report

Merging #163 (f423742) into V2.6.0.x (a199fc9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           V2.6.0.x     #163   +/-   ##
=========================================
  Coverage     51.29%   51.29%
=========================================
  Files           692      692
  Lines         36585    36585
=========================================
  Hits          18765    18765
  Misses        17820    17820

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 a199fc9...f423742. Read the comment docs.


clarify gas metering

Summary
Clarify how to meter for gas for messages and state-relevant Txs too.
Context
Dropping some raw notes from discussions we had:
Transaction cost metering should only be based on bytes .
potenial workarounds: implicitly set gas limit to infinity (maybe not infinity, maybe use gas used purely for byte cost). This means no need for gas limit field in tx.
Some context:
In the SDK applications can define gas metering as they please.
Here is an example of metering based on bytes: https://github.com/cosmos/cosmos-sdk/blob/eb8aaf939513d3bf6e82bd13691cfbe9ef4ad28c/x/auth/ante/basic.go#L88-L95
more docs:
https://docs.cosmos.network/master/basics/gas-fees.html#block-gas-meter
and the AnteHandler: https://docs.cosmos.network/master/basics/gas-fees.html#antehandler
Timeline / Action Items
Note the implementation can happen for the incentivized testnet but we should definitely "de-risk" this earlier, i.e. we should start looking into what exact changes will be necessary certainly before the test-net milsetone.

Extra info: If you set the gas per all ops to 0 and the gas per byte to 1 gas per byte, then you exactly have metering per byte.
In terms on gas limit, the implicit gas limit should be the deterministic gas cost of a tx, not infinity. If it's infinity, accounts won't have sufficient balance to pay fees and the txs will be invalid. Of course, this point depends on where the implicit gas limit is injected; if after the validity checks then there's less of an issue.

The example mentioned is the default that we're using, gas is strictly per byte basic. Unless we add some additional operational gas cost, that will be zero too. What the default mechanism doesn't account for, is that we process messages before calling the function that deducts gas during DeliverTx. We only have to add another anteHandler to account for the message's size.

I think we can close with after #397

we also have our resource pricing specs https://github.com/celestiaorg/celestia-app/blob/main/specs/src/specs/resource_pricing.md so this feels safe to close


use with unplugin-icon and vue3 and vite, but throw iconify.mjs not found.

[vite] error while updating dependencies:
Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>    at Object.openSync (node:fs:585:3)
    at Object.readFileSync (node:fs:453:35)
    at runOptimizeDeps (D:\code\frontend-demo\node_modules\vite\dist\node\chunks\dep-59dc6e00.js:39538:46)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at processTimers (node:internal/timers:497:9)
    at async runOptimizer (D:\code\frontend-demo\node_modules\vite\dist\node\chunks\dep-59dc6e00.js:59545:38)
Vite Error, /node_modules/.vite/deps/theme-change.js?v=1febecd5 optimized info should be defined

unplugin-icon and @iconify/vue are two completely different packages.

thanks。 In my project i install @iconify/vue before and maybe i dont remove it totally. I clean the node_modules and reinstall the project works good.


chore(eslint-plugin): bump @typescript-eslint deps

Description
Bumping @typescript-eslint dependencies.
I'm not sure if it should be major/minor/patch, cause it should not break anyone. Just to be on the safe side, we can make it a major release, but I've marked it as patch in changeset, hope it's okay

I have signed the CLA!

Closing, as I've done typescript-eslint bumps as part of #420


fix: Fix for Credential records created before adding protocol v2

Credential records created before adding protocol v2 don't have protocol version set, so credentialRecord.protocolVersion returns undefined, and getService also returned undefined. Old credentials couldn't be deleted due to this issue.

@Przytua There's been quite some breaking changes to storage in 0.2.0. We resolve those using a migration script that can be run once updated to 0.2.0.
See https://github.com/hyperledger/aries-framework-javascript/blob/main/docs/migration/updating.md and https://github.com/hyperledger/aries-framework-javascript/blob/main/docs/migration/0.1-to-0.2.md for more information

@Przytua There's been quite some breaking changes to storage in 0.2.0. We resolve those using a migration script that can be run once updated to 0.2.0.
See https://github.com/hyperledger/aries-framework-javascript/blob/main/docs/migration/updating.md and https://github.com/hyperledger/aries-framework-javascript/blob/main/docs/migration/0.1-to-0.2.md for more information

Thanks for letting me know! Didn't notice that earlier.


[Bug] Window always opening on left-most monitor in Linux with KDE

Hi,
I recently got a dual monitor setup and noticed an annoying bug on Linux with KDE, the window always appear on the left-most monitor (which is my 2nd screen for me)
I actually identified the cause: before loading the window settings, the program clamps the position value, but it doesn't take into account that the origin point shift to the left-most point in a multi-monitor setup on Linux (at least on X11, I didn't test Windows or Wayland)
If the intent was to prevent the window from spawning out-of-bounds, it is unnecessary because this is done automatically (either by GLFW or X11, I don't know). It also does it for the size
Thank you again for the program!

Hi Frousties,
So this one is a little tricky... with the additional snag that I don't have a dual monitor setup -- although I do run KDE / X11 (Kubuntu)
Notes:
a) In windows 11, if I don't clamp, the window can end up off screen with no way to restore (set screen resolution large, drag window off to bottom right, close, change reolution to something small, open).
b) This is not an issue with Linux. As you mentioned, it automatically fixes it up.
At the very least I could remove the clamps for Linux.. which woud presumably solve your problem. Another, maybe better, solution is to enumerate all the attached monitors and add up all the widths (but not heights) to get a total desktop width.
The benefit of the second approach is dual monitors would work on windows too. The downside is

If monitors have different reolutions, there will be rectanguar 'holes'.
To do it properly I'd need to know the arrangment of monitors (are the horizontal or vertical?). eg. If horizonal, you'd add widths and probably take the max height, if vertical vice-versa. I'm sure this info is available, but hard to get right without actually being able to test it.

Still, if it's supported in Linux it would be nice to support windows too. If I did the second approach I'd just assume the monitors where horizontally arranged  For I'll probably do the Linux-only ifdef quickly and give you a commit hash when it's in.

Huh, weird behavior, would've expected Windows to clamp windows automatically
I think it would be fine to remove the clamp for now on Linux only, I'll make some tests on Windows to check how it behaves there

Cool. Assuming you are able to buid the project, give d020aa415efb86d85fdcd04b09868053ee536823
a go. I still clamp minimum size, but that's all. I'm out for a bit.. but I think it will work.

Sorry for the very late reply (life got crazy), but it seems to be working perfectly, on Windows and on Linux

NP. Thanks for testing. I'm renaming this issue to just refer to improving multi-monitor in general (esp in Windows). Want to keep the comments.


created FI.xml

Finnish holidays

Thank you very much for your first time contribution to this holiday-list! 🎉
Absolutely awesome!!!


CI: try XL runners

https://github.blog/2023-03-01-github-actions-introducing-faster-github-hosted-x64-macos-runners/

No significant benefit

Master: https://github.com/lima-vm/lima/actions/runs/5781237337/job/15666060253

Test default.yaml took 5m30s (Command completed after 1 attempt(s).

This PR: https://github.com/lima-vm/lima/actions/runs/5781425887/job/15666498981?pr=1720

Test default.yaml took 5m19s (Command completed after 1 attempt(s).)


Add flipper/test_help to automatically configure Flipper in tests/specs.

This adds flipper/test_help to automatically configure Rails/RSpec the way we recommend in our testing docs.
Open questions:

Should Flipper::Engine automatically require this if RAILS_ENV=test? I think yes, but maybe we wait until 2.0 to do that?
As brought up in #807, what should the default value for strict be in test? Currently with strict = :warn, you also have to call Flipper.add for each feature. In theory, I like the explicitness of this. It will guard against typos in flag names, but also seems like busywork.  One option is to establish a pattern for defining features in an initializer, like this:

# config/initializers/flipper.rb
module Feature
  Hubspot = Flipper.add(:hubspot)
  Seo = Flipper.add(:seo)
end

# app/jobs/hubspot_sync_job.rb
def perform(resource)
  return unless Feature::Hubspot.enabled?(resource)
end

Went down a nice little rabbit hole while investigating our Flipper-test-setup, guess I am waiting for the next release!
Well done 🚀


Add mamba ssm

Adding some of the newer SSM based mechanisms would be of interest, and the following dérivation would facilitate implementation.
https://srush.github.io/annotated-mamba/hard.html

"based" is an apparently simpler approach with similar performance one could use https://www.together.ai/blog/based combining

sliding window
linear (Taylor) attention

Bitnet and handful of other tech mentioned in https://www.answer.ai/posts/2024-03-06-fsdp-qlora.html could be useful for the larger deep models.


"Fields are euclidean rings" and the lawless % operator

I realized that the inclusion "every field is an Euclidean domain" means that all methods on EuclideanRing should have default implementations to satisfy the yet-to-be-tested algebraic laws on these structures.
I'm not an expert in ring structures and the introductory (e.g. Wikipedia) leave me somewhat unsatisfied.
I'm opening this issue to do a bit of brainstorming and clean-up. After discussion, I'll propose a PR incorporating the definition and tests.
Every field is an Euclidean domain, and as x/y can be computed for any y!=0, mod is always equal to 0. See discussion here, mathematical definition here, also discussion here.
Thus the implementations of mod, quot and quotmod become trivial.
Now, I could not find resources on how to define gcd and lcm. What I know:

there is a universal construction for all fields, as the inclusion shows. This inclusion can use all properties of fields, including the existence of a unit for multiplication, and the fact that all non-zero elements have a multiplicative inverse.
we cannot assume the existence of an order, because the same construction should apply to non-ordered fields such as the complex numbers.

I would be tempted to define gcd(x,y) = 1  and lcm(x,y) = x * y to satisfy the axioms of GCD domains.
Problem: this clashes with the usual definition of the % for doubles, which is inspired by a generalization of the property "how many times this quantity fits in that quantity" on floating point numbers.
I'm not sure what's the best way to proceed here. If we come to the conclusion that def mod(x: Double, y: Double) = 0.0 is the only construction that obey the GCD domain laws, then the result is going to be quite confusing for users.
On the other hand, EuclideanRing does not have any laws yet, which should be corrected.

Oh, and as a bonus: the value of the program below:
EuclideanRing.mod(2.0, 4.0) should ===(0.0)
EuclideanRing.mod(2, 4) should ===(2)

OK, in a field, we can define gcd(x, y) to be whatever we want. In general, the GCD is not unique. Actually, it's a convention that gcd(x, y) is positive for positive integers x, y.

Right -- the way I've heard this described is that there is more than one valid euclidean for a field, so you can have several different valid mod/gcd/lcm implementations. I think the important thing is that we are consistent.
I'm fine with having fields default to the simple gcd/lcm/mod definitions you proposed, but letting instances (e.g. Field[Double]) override them as necessary.

Agree with you, for gcd it's fine to have Field[Double] override it. But mod(x: Double, y: Double) has to be equal to zero, otherwise laws will fail. For example "mod(x, y) = 0 if y divides x`, which is always true in a field.

Actually, there is motivation for two modulo operators, with a % operator that would respect the JVM semantics for the common types (BigInt, primitives...), and a mod that would obey the ring laws (to be defined).
See the following:
scala> BigInt(-2) % 3
res7: scala.math.BigInt = -2

scala> EuclideanRing[BigInt].mod(-2, 3)
res8: BigInt = -2

Indeed, there is motivation for two modulo operators. One named remainder with a % syntax, obeying the currently wide-spread % behavior, the other being mod obeying the rules of the EuclideanRing under consideration.
In essence, we would follow the BigInt semantics, with appropriate generalizations for other primitives.
I'm writing a summary of the situation and will update this issue once done.

See work in progress here

See #693

This is solved now with the EuclideanRing and TruncatedDivision types.
The operator % (and /~) are no longer part of spire. Instead, we recommend emod, tmod, fmod and friends.


⚠ Bofrost.fr has degraded performance

In 3c4e22b, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1864 ms

Resolved: Bofrost.fr performance has improved in 3d48035 after 19 minutes.


problems making landing pages

Describe the bug
It's not really a bug, it's just that I got really excited paying my $20 to use your website, and whenever I want to make a landing page of my affiliate marketing stuff, it keeps giving me a message of "unethical type websites" and that's not the actual message,I was wondering if there is like a god mode version of this of ChatGPT, but I can go past that and just make a simple landing page. The Landing page of mine leads to an affiliate marketing offer for people who are looking for a.  I was wondering if there is like a god mode version of this of ChatGPT, but I can go past that and just make a simple winding page. Landing page of mine leads to an affiliate marketing offer for people who are looking for quick loans. I also have other offers for making money online as well. Seems to be I might have wasted my $20 for nothing.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-icom5o
Steps to reproduce
Can you build me a landing page Wordpress website about loans that are easy to get in case you need cash for an emergency. The website needs to be a wordpress based website that solves the problem of people getting loans to help pay for bills
Expected behavior
create a landing page with wordpress
Screen Recording / Screenshot

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

Appreciate the feedback! Bolt is powered by WebContainers and as such only supports languages that are supported by WebContainers. If you need to develop a WordPress project, another platform may be best for your needs at this time.

So can I get a refund cause obviously this is something that I need. I just
bought it today already canceled it.
On Thu, Nov 14, 2024 at 11:40 AM Brian @.***> wrote:

Appreciate the feedback! Bolt is powered by WebContainers
https://webcontainers.io/ and as such only supports languages that are
supported by WebContainers. If you need to develop a WordPress project,
another platform may be best for your needs at this time.
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/bolt.new/issues/2332#issuecomment-2477037825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASZMMXWKGRC5UAHPO76YZ3D2ATOAHAVCNFSM6AAAAABRZIWXOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXGAZTOOBSGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Refund requests are handled through<EMAIL_ADDRESS>


CB-12780 - Audit API and new event API should be authorized

Have you tried this out without PowerUser role with mow-dev ums?

@gregito can you pls check and answer @foldik's question? we would like to make sure it is tested recently with real (mow-dev) ums (since this PR is quite old)

@foldik @horadla23 it was tested by hand a while (2-3 months) ago

Can you do a fresh round of testing, since there was new commits since 2-3 month ago testing, then we'll merge.

Marked as DO_NOT_MERGE until the behavior gets verified as @lnardai suggested.

retest this please

Closing the PR, please re-open if it's still relevant.

I'm rerequesting reviews as this has been reviewed more than 6 months ago


Close H2Stream readBuffer on data.endStream

Fixes https://github.com/http4s/http4s/issues/7146. The Channel introduced in https://github.com/http4s/http4s/pull/7096 was not being closed in the right place.

Hello all! I just discovered this PR and took a look at its changes. I found that whenA may be used instead of if then ... else Applicative[F].unit:
- _ <-
-    if (data.endStream) s.readBuffer.close *> s.trailWith(List.empty).void
-    else Applicative[F].unit

+ _ <- data.endStream.whenA(s.readBuffer.close *> s.trailWith(List.empty).void)

I am not that experienced at scala, so can I ask you, is whenA version more readable than if then else or it is not?

Yes, you are right, this would be a good place to use whenA: it is correct and probably more readable :)
It would look like this:
_ <- (s.readBuffer.close *> s.trailWith(List.empty)).void.whenA(data.endStream)

There is a (very small) performance penalty to use it instead of an if, which is once reason why I didn't consider changing it here.

There is a (very small) performance penalty to use it instead of an if

This performance penalty caused because of method calling rather then directly using if then else? Because the whenA's body is just if (cond) void(f) else unit. Correct me if I am wrong, I am just trying to learn more about Scala :)

The signature for whenA looks like this:
def whenA[A](cond: Boolean)(f: => F[A]): F[Unit]

The => F[A] is a "by-name" parameter. This is used to preserve laziness in the case when the condition is false.
https://docs.scala-lang.org/tour/by-name-parameters.html
What this means is that instead of directly passing F[A] to whenA, it allocates a by-name wrapper for F[A], and passes that instead. Creating this wrapper incurs a very small penalty.

Thanks for the explanation, @armanbilge!


energy consumption ???

it is possible to retrieve energy consumption information already present on the Daikin application ?

Here’s your corrected and polished version of the message, keeping a casual tone:
Hi @mduran80,
Thanks for your work! I agree with Oulasri—HA now allows us to track individual device energy consumption, and implementing this could really help us create more eco-friendly and cost-effective automations. This is especially useful when managing multiple energy sources like solar panels.
In my case, my solar setup already gives me real-time data on my home’s energy consumption and solar production. What I’d like to do is automate the operation of certain devices, like my washing machine, dryer, or heating system.
For the washing machine and dryer, I use smart plugs that provide the consumption data, but that’s not the case for my Daikin system. Having this info would make it possible to automate devices more intelligently by:
Starting devices when there’s enough free energy available (solar production minus the consumption of individual devices I’m tracking).
Responding dynamically to changes in solar production, like deciding which devices to pause, start, or adjust.
I don’t want (and don’t plan) to use smart plugs for every single device—just for the bigger consumers I mentioned. That’s why having this capability would be a huge help.
Thanks again for considering this!
Dorian


Undocumented syntax / operation of AddMultiplicationEquality()

What version of OR-Tools and what language are you using?
Version: 9.7.2996
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
MacOS, 13.5.2
What did you do?
I executed this code:
from ortools.sat.python import cp_model
model = cp_model.CpModel()
x = model.NewIntVar(0, 100, "x")
y = model.NewIntVar(0, 100, "y")
xy = model.NewIntVar(0, 10000, "xy")
model.AddMultiplicationEquality(xy, x, y)
model.Add(xy==20)
solver = cp_model.CpSolver()
solver.Solve(model)
print("x =", solver.Value(x))
print("y =", solver.Value(y))
print("xy =", solver.Value(xy))

and it ran through and gave me this:
x = 1
y = 20
xy = 20

What did you expect to see
An error, since the documentation gives the signature of AddMultiplicationEquality() as:
def AddMultiplicationEquality(self, target, variables). But in the above I'm doing AddMultiplicationEquality(target, variable1, variable2).

What did you see instead?
It seems to work the way I'd intuitively expected it to work, but I can't be sure and it's not documented. If this is expected behavior, I think it should be documented. If it's not expected, I think it should raise an error.

Please prefer to use the up to date with the last release ref doc here: https://or-tools.github.io/docs
=> https://or-tools.github.io/docs/pdoc/ortools/sat/python/cp_model.html#CpModel.AddMultiplicationEquality

Thank you - so, the new signature is AddMultiplicationEquality(target, *expressions)? That seems like a problematic breaking change...? Or is the previous usage still supported? I tried, and indeed, as far as I can tell, both seem to work. Should the former be preferred then, going forward? And why aren't the docs updated in the link I used?

Thanks, @lperron - would it make sense to update the documentation to cover this usage as well?

Yes, but we need to support more than 2 terms before that.
Laurent Perron | Operations Research | @.*** | (33) 1 42 68 53
00
Le jeu. 28 sept. 2023 à 16:16, Gili Rosenberg @.***> a
écrit :

Thanks, @lperron https://github.com/lperron - would it make sense to
update the documentation to cover this usage as well?
—
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/3931#issuecomment-1739324355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3NRREPYTIEGHCCSB5LX4WBCFANCNFSM6AAAAAA5KLLRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Some code linting and GH actions plus Docker

Hi, I'd like to contribute to this project because I'd like to use it at work to inspect some Java app deployed on Kubernetes: I would use this app in a Docker container as side-car in a Kubernetes pod.
I introduced checkstyle, I formatted the code and I resolved some issues listed by Sonar. I also added two GitHub actions: one for the pushes and one for PRs. Also, I added a primitive build for Docker using the standalone version of the JAR.
For the Docker push step you need two repository secret, DOCKER_USERNAME and DOCKER_PASSWORD, with a username from Docker Hub and a token generated ad-hoc for this repo (using your actual Docker Hub password is deprecable) and a variable, DOCKER_NAMESPACE, indicating your namespace on Docker hub (for example, during my tests I deployed the image as kerny3d/jminix:1.3.5, where kerny3d is my username and my namespace).
I hope you like this contibution.

Many thanks for the contribution!
I could not review all reformat change in details, though. Merged anyway.


az role definition update - wrong example

I am trying to create and update custom roles. However I'm facing issues when running the update command using a role definition that worked perfectly when creating a custom role. It seems that the example to update a definition is a copy&paste error as it actually uses the create command. Wondering how the role definition needs to look to prevent the following error during an update operation
▶ az role definition update --role-definition roles/keyvault.json
Please provide the unique logic name of an existing role

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

ID: 40e649cf-40e3-1b9e-141a-c62d244eda61
Version Independent ID: 78ea89c1-7c56-e33b-d10a-dae05642aa34
Content: az role definition
Content Source: src/command_modules/azure-cli-role/azure/cli/command_modules/role/_help.py
Service: azure-resource-manager
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Update regarding the error I received:

created a role with 2 assignable subscriptions (A + B)
az account set was set to B
create role definition, assuming it would end up in scope B as it is default for other resources being created, turns out to be a resource in A (I guess since it was listed first in assignable scopes)
error occured when I tried to remove subscription A and add C

So I guess the error Please provide the unique logic name of an existing role actually means Can not remove subscription where Role is defined or something

It is a CLI bug that we are not resolving the role definitions from the assignable scopes correctly.
@anoff Sorry for the delay in response. For now the reliable workaround is to delete and recreate the definition before we release the fix

Is this bug resolved?  If I'm reading it correctly, the role definition update functionality does not work?

Does this seem similar to https://github.com/Azure/azure-cli/issues/2745 ?
I am unable to update an existing role definition when assigned across multiple subscriptions (even though, I am in owner role across all subscriptions). I end up with similar:
"Please provide the unique logic name of an existing role"
This happens if in my role def I use the friendly "name" or the guid value..

Just a follow up - this works perfectly fine in PowerShell - it seems only a fault of Azure CLI.

I have the fix submitted, the key is to use the output of "az role definition create/list" to construct the input for update. The difference is there is the id which tells CLI the right subscription to use.

I have the fix submitted, the key is to use the output of "az role definition create/list" to construct the input for update. The difference is there is the id which tells CLI the right subscription to use.

I have done it but it still does not work. The issue is when I try add other subscription in "assignableScopes"

@santy8a, did you get the same error?

@santy8a, did you get the same error?

Yes. Same error.
This is my custom role

I created this file using this command. It is right?
az role definition list --name "Uses Case Role" --query [0] > /tmp/uses_case.json
But. when I try to update
$ az role definition update --role-definition /tmp/uses_case.json
Please provide the unique logic name of an existing role

@santy8a, the id is not respected right now but my PR will do. So please use the upcoming release

Thanks a lot @yugangw-msft ,
Do you know when is upcoming release?

@santy8a, it will be around tomorrow

Great, thank you very much


Corrects a typo: sever -> server

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/edi-migration-utilities.md
:white_check_mark:Succeeded
View

biztalk/index.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.

@exchange12rocks Good catch. Thank you!


Allow question.in to take an array (and not only a Range)

It's all in the title.
I'd like to be able to do:
prompt.ask 'Which" do |question|
    question.in array
end

:)

OK, I can already do that with a :validate and a Proc. :)


Questions about hunter with and compared to other tools

Cool, I came across hunter and I'm interested in it but I'm not sure if it will work well with another tool I use cmake-basis, which I've contributed to.
Is python necessary to use hunter? I strongly prefer pure CMake build tools. The use of python also concerns me as a dependency since catkin has some similarities but many issues, and it can break the build up into pieces losing some of the integration that comes with CMake. I'm not familiar with your implementation however so you may have good reasons these issues don't come up.
Some people also like to use tools such as ones that allow grid compilation. Is that still possible with hunter or does the us of ExternalProject_Add get in the way?

Hunter is a slot-in solution that automatically fetches and compiles your project's dependencies during your project build process.  It allows you to use whatever combination of platform/ide/toolchain you want, without having to worry whether your dependecies will be ok with that.  Hunter makes them ok with that.
Just download one module, a little boilerplate specifiying which Hunter version you want, and insert one hunter_add_package call to match every find_package call in your project.  That's it.  Those pacakges you use via find_package will be compiled ready for CMake to find when configuring your project.

Is python necessary to use hunter?

No.  AFAIK, the only package that depends on anything like that is OpenSSL which required Perl to be there.

Building on OSX requires Python 3 from what I remeber.. at least for Boost

Cool, I came across hunter and I'm interested in it but I'm not sure if it will work well with another tool I use

Let me know if you have any problems. I see no reason why Hunter can conflicts with other CMake modules. Hunter set some *_ROOT CMake/environment variables + CMAKE_PREFIX_PATH to find packages in custom location. Hunter modify CMAKE_MODULE_PATH so you can use hunter_add_package module + Hunter set some internal variables that all starts with HUNTER_*.

Is python necessary to use hunter?

No. README explicitly states:
no need for Git or Python or anything

but some packages require external tools for building

OpenSSL which required Perl to be there

exactly

Building on OSX requires Python 3 from what I remeber.. at least for Boost

You mean this script? It's just for OS X. Well I think I can handle it with CMake easily. I've opened https://github.com/ruslo/hunter/issues/130

Some people also like to use tools such as ones that allow grid compilation

I think Alex answer this question, let me know if you need more info.

Hope answers help you. Closing.

@ruslo thanks!


Add Cont monad

This adds the type Cont r a = ContT r Identity a synonym.

:+1: Looks good to me!

Thanks!


Alternative no_std Oddio implementation

Does the exact same thing as #65 , but use num-traits as a base instead of directly using libm

Thanks for the PR! Unfortunately I don't think the extra dep is justified for the trivial internal cosmetic benefit.

It wasn't just cosmetic benefit. It also fixed the miri issue we were having with directly using libm.

That can be mitigated much more simply by using the std impls under miri, as proposed in https://github.com/Ralith/oddio/pull/65#issuecomment-940358676.


CLAPACK_FOUND used before initialized?

I don't think there's anything setting CLAPACK_FOUND in the file below, so I don't believe it's setting-up the proper targets. I'm actually getting a build error when trying to use the lapack target after a successful call to find_package(LAPACK REQUIRED) on a Windows build.
Additionally, the targets are only correctly set-up the first time you call find_package(LAPACK). Subsequent calls will have all the oF2C_LIBRARY_RELEASE etc. variables not set and hence the targets will typically be -NOTFOUND.
https://github.com/microsoft/vcpkg/blob/bb002cdd1a2c9eacbe60d8383fb5d437752b1e4e/ports/clapack/FindLAPACK.cmake#L171

cc @cenit

@bucurb, could you provide us the repro code?
The package clapack:x64-windows provides CMake targets:

    find_package(clapack CONFIG REQUIRED)
    target_link_libraries(main PRIVATE f2c lapack)

    find_package(lapack CONFIG REQUIRED)
    target_link_libraries(main PRIVATE lapack clapack::clapack)

Adding find_package(clapack CONFIG REQUIRED) fixes the issue for sure, but that is not the 'proper' fix, as lapack is supposed to be the 'pure virtual' package that dispatches to either clapack or lapack-reference depending on the platform. As for the repro, you only need 2 dummy sibling cmake files, both calling only find_package(LAPACK REQUIRED). Initially none will succeed, but if you do indeed set CLAPACK_FOUND as the script claims it does, then the first call will succeed, but the second will not, as the variables used to set-up the lapack targets are not set and the target will end-up invalid.

@bucurb, It looks a port bug, I have submitted a PR https://github.com/microsoft/vcpkg/pull/18707 to fix it, could you help test it?

@PhoebeHui I just created a PR with what worked for me. I saw your PR just now, sorry about that.


Add Search, sort, share Features

Search, sort, share Features

@tamas6 Please check PR , test, merge if still relevant.

https://app.photo.dev.fairdatasociety.org/ currently down: server error 400


RefreshCPUList ThrowNoMatchException

Library version
<IP_ADDRESS>
OS & OS version
Debian GNU/Linux 11 (KVM)
Note
Command working fine on windows.
Describe the bug
hardwareInfo.RefreshCPUList(); throw ThrowNoMatchException:
"sequence contains no matching element"
at System.Linq.ThrowHelper.ThrowNoMatchException()\n
at Hardware.Info.Linux.HardwareInfoRetrieval.GetCpuUsage(CPU cpu)\n
at Hardware.Info.Linux.HardwareInfoRetrieval.GetCpuList(Boolean includePercentProcessorTime)\n
To Reproduce

publish as linux-x64, release, net-core 6.0
execute RefreshCPUList()

Thank you for reporting this. I will look into it.

Here is the new NuGet: https://github.com/Jinjinov/Hardware.Info/releases/tag/v<IP_ADDRESS>
Is this issue resolved now?

Here is the new NuGet: https://github.com/Jinjinov/Hardware.Info/releases/tag/v<IP_ADDRESS>
Is this issue resolved now?

sorry, i will try to test only on sunday and answer to you :)


The string for Board Column was ever, does not work in queries. How can I get that to work in ADO?

I've tried to use the query string for "Board Column was ever..." and it doesn't have was ever as an option. Am I doing something wrong?

[Enter feedback here]

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

ID: b8acd801-cb9c-fa87-b4a7-5a44094bbd00
Version Independent ID: e471c7e6-2ace-9029-ae22-62f1725168fa
Content: Query by account, user, workflow, or board changes in Azure Boards - Azure Boards
Content Source: docs/boards/queries/query-by-workflow-changes.md
Service: azure-devops-boards
GitHub Login: @chcomley
Microsoft Alias: chcomley

@rrobertsor -- thank you for your question.  "Was ever" is showing in my list of options for Board Column:

I'm not sure how your situation may be different.
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.

@rrobertsor -- thank you for your question. "Was ever" is showing in my list of options for Board Column:

I'm not sure how your situation may be different.
I am closing this issue now. You are welcome to @ mention me for any followup. We hope to hear from you again.

Hi William
I am seeing something different. Noticeably the different reference to type of query:
My screen says "My queries" yours says "Custom Queries"
Though the options appear the same in screen. Does that make a difference?
As you can see on the screenshot here, when I select board column and type was there is no operator for was it shows nothing. And if I just go through the list, it shows nothing.
What could be restricting this?

What I see are these options:

Hi @rrobertsor, I'm sorry for the delay here. I've reached out to our product group and will get back to you as soon as I hear from them. Thanks!

Hi @rrobertsor, this is a bug in the New Boards Hub, which is now on by default. We've created an internal bug for our team to get it fixed! Thank you. Closing the issue, since it doesn't require an update to the article.


[BUG] CSI components CrashLoopBackOff, failed to connect to unix://csi/csi.sock after cluster restart

Describe the bug (🐛 if you encounter this issue)
After cluster restart (reboot all k8s nodes including control plane node), all csi components got stuck in CrashLoopBackOff:
╰─$ kl get pods
NAME                                                     READY   STATUS             RESTARTS          AGE
longhorn-manager-pxlcx                                   1/1     Running            16 (10h ago)      15h
longhorn-manager-gr26g                                   1/1     Running            16 (10h ago)      15h
engine-image-ei-b907910b-m6gr4                           1/1     Running            16 (10h ago)      15h
instance-manager-bb7e4a2035b50ec3896800262c56800c        1/1     Running            0                 10h
engine-image-ei-b907910b-7vfnt                           1/1     Running            16 (10h ago)      15h
instance-manager-dca4e951d12ab6ab6f714f42f1a2416e        1/1     Running            0                 10h
csi-attacher-67f8c99bcd-9fqwj                            1/1     Running            20 (10h ago)      15h
csi-snapshotter-6f6bf9c757-t68d7                         1/1     Running            19 (10h ago)      15h
csi-resizer-545b7c64f5-7l2hv                             1/1     Running            19 (10h ago)      15h
csi-attacher-67f8c99bcd-2chq8                            1/1     Running            19 (10h ago)      15h
csi-provisioner-557c7f7c44-g2x77                         1/1     Running            20 (10h ago)      15h
longhorn-driver-deployer-7f94bb668f-s7zwg                1/1     Running            16 (10h ago)      15h
longhorn-csi-plugin-h5xqw                                3/3     Running            72 (10h ago)      15h
longhorn-ui-646f4bc8df-tbmtt                             1/1     Running            29 (10h ago)      15h
csi-resizer-545b7c64f5-gzm2z                             1/1     Running            19 (10h ago)      15h
csi-provisioner-557c7f7c44-2p6lc                         1/1     Running            19 (10h ago)      15h
engine-image-ei-b907910b-9ztgm                           1/1     Running            16 (10h ago)      15h
csi-snapshotter-6f6bf9c757-jqqp9                         1/1     Running            19 (10h ago)      15h
longhorn-csi-plugin-4sqkv                                3/3     Running            69 (10h ago)      15h
longhorn-manager-dfn6d                                   1/1     Running            16 (10h ago)      15h
instance-manager-0435193fed60526c87fd3a53fb03ba39        1/1     Running            0                 10h
share-manager-pvc-911b2b67-1e45-4f26-914f-23f2090af998   1/1     Running            0                 10h
share-manager-pvc-81c99bd1-b424-4be2-a075-80e8b17334ab   1/1     Running            0                 10h
longhorn-ui-646f4bc8df-c9tqj                             1/1     Running            35 (10h ago)      15h
csi-attacher-67f8c99bcd-jsj54                            0/1     CrashLoopBackOff   141 (2m49s ago)   15h
longhorn-csi-plugin-kxtqn                                0/3     CrashLoopBackOff   535 (2m18s ago)   15h
csi-snapshotter-6f6bf9c757-xwmmn                         0/1     CrashLoopBackOff   141 (2m14s ago)   15h
csi-provisioner-557c7f7c44-wd57k                         0/1     CrashLoopBackOff   141 (2m5s ago)    15h
csi-resizer-545b7c64f5-8jxk4                             0/1     CrashLoopBackOff   141 (61s ago)     15h

They are all unable to connect to unix://csi/csi.sock:
╰─$ kl logs csi-attacher-67f8c99bcd-jsj54
I1116 01:28:03.328201       1 main.go:97] Version: v4.4.0
W1116 01:28:13.329951       1 connection.go:183] Still connecting to unix:///csi/csi.sock
W1116 01:28:23.329624       1 connection.go:183] Still connecting to unix:///csi/csi.sock
W1116 01:28:33.330048       1 connection.go:183] Still connecting to unix:///csi/csi.sock
E1116 01:28:33.330124       1 main.go:136] context deadline exceeded

To Reproduce
Run negative test case Restart Cluster While Workload Heavy Writing repeatedly.
Expected behavior

Support bundle for troubleshooting
supportbundle_ae1d1892-8da7-4733-97d7-16326976bb0e_2023-11-16T03-17-09Z.zip
worker nodes logs:
worker_nodes_log.txt
Environment

Longhorn version: v1.5.x-head
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.27.1+k3s1

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
Kernel version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:
Impacted Longhorn resources:

Volume names:

Additional context
https://suse.slack.com/archives/C02DR3N5T24/p1700095454722879?thread_ts=1699951700.806219&cid=C02DR3N5T24

I cannot find any clue in the support bundle. Since the longhorn-csi-plugin is being repeatedly restarted, even if it fails to listen on csi.sock one time, it should succeed the next time, and the system should stabilize.
My immediate guess was SELinux. However, SELinux should have been set to permissive given the Jenkins parameters (I am not able to confirm or deny this from any of the logs we have). Additionally, it should have affected all nodes similarly.
I kicked off https://ci.longhorn.io/job/private/job/longhorn-e2e-test/129/ to try to reproduce it for live debugging. If that doesn't work, we will likely need to wait for another occurence.

I hit this one when restarting a one-node cluster. I was planning to create a ticket but looks like one already exist here.
The issue in my case is that longhorn-csi-plugin stays in crashing loop for about 4-5 mins then it recovers. Not sure if this is just slowing issue

I kicked off https://ci.longhorn.io/job/private/job/longhorn-e2e-test/129/ to try to reproduce it for live debugging. If that doesn't work, we will likely need to wait for another occurrence.

This didn't help to reproduce the issue.

I hit this one when restarting a one-node cluster. I was planning to create a ticket but looks like one already exist here.
The issue in my case is that longhorn-csi-plugin stays in crashing loop for about 4-5 mins then it recovers. Not sure if this is just slowing issue

I'll look into this a bit when I have time to see if there is an improvement we can make. It seems different from the original event, since, in that case, the CSI components never recovered.

I'm having this same issue, what kind of troubleshooting can we actually perform to identify the cause? This is on a five node cluster and it was working fine until a power issue took it out, now one node's looping on this error:
Still connecting to unix:///csi/csi.sock

Hello @yaleman. Could we have a support bundle please to confirm the identical symptoms and look for additional clues?
Please upload a it (or a paste a link) here, or send it to<EMAIL_ADDRESS>

A 30 second timeout was introduced to github.com/kubernetes-csi/csi-lib-utils/connection.Connect in this commit. The commit is included in github.com/kubernetes-csi/csi-lib-utils >= v1.14.0.
The latest version (v.2.11.0) of github.com/kubernetes-csi/livenessprobe picked up that change in this commit.
In the support bundle provided by @longhorn/qa, we were running longhornio/livenessprobe:v2.11.0. I'm not sure yet why this was the case, since we deploy longhornio/livenessprobe:v2.9.0 by default still. Maybe we were actively testing an improvement?

Here are the latest longhorn-csi-plugin logs from the support bundle:
2023-11-16T03:13:13.665926468Z time="2023-11-16T03:13:13Z" level=info msg="CSI Driver: driver.longhorn.io version: v1.6.0-dev, manager URL http://longhorn-backend:9500/v1" func="csi.(*Manager).Run" file="manager.go:23"
2023-11-16T03:13:13.687607928Z time="2023-11-16T03:13:13Z" level=info msg="Enabling node service capability: GET_VOLUME_STATS" func=csi.getNodeServiceCapabilities file="node_server.go:756"
2023-11-16T03:13:13.687626652Z time="2023-11-16T03:13:13Z" level=info msg="Enabling node service capability: STAGE_UNSTAGE_VOLUME" func=csi.getNodeServiceCapabilities file="node_server.go:756"
2023-11-16T03:13:13.687648727Z time="2023-11-16T03:13:13Z" level=info msg="Enabling node service capability: EXPAND_VOLUME" func=csi.getNodeServiceCapabilities file="node_server.go:756"
2023-11-16T03:13:13.687698615Z time="2023-11-16T03:13:13Z" level=info msg="Enabling controller service capability: CREATE_DELETE_VOLUME" func=csi.getControllerServiceCapabilities file="controller_server.go:1264"
2023-11-16T03:13:13.687704255Z time="2023-11-16T03:13:13Z" level=info msg="Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME" func=csi.getControllerServiceCapabilities file="controller_server.go:1264"
2023-11-16T03:13:13.687707962Z time="2023-11-16T03:13:13Z" level=info msg="Enabling controller service capability: EXPAND_VOLUME" func=csi.getControllerServiceCapabilities file="controller_server.go:1264"
2023-11-16T03:13:13.687711070Z time="2023-11-16T03:13:13Z" level=info msg="Enabling controller service capability: CREATE_DELETE_SNAPSHOT" func=csi.getControllerServiceCapabilities file="controller_server.go:1264"
2023-11-16T03:13:13.687713239Z time="2023-11-16T03:13:13Z" level=info msg="Enabling controller service capability: CLONE_VOLUME" func=csi.getControllerServiceCapabilities file="controller_server.go:1264"
2023-11-16T03:13:13.687792201Z time="2023-11-16T03:13:13Z" level=info msg="Enabling volume access mode: SINGLE_NODE_WRITER" func=csi.getVolumeCapabilityAccessModes file="controller_server.go:1280"
2023-11-16T03:13:13.687797371Z time="2023-11-16T03:13:13Z" level=info msg="Enabling volume access mode: MULTI_NODE_MULTI_WRITER" func=csi.getVolumeCapabilityAccessModes file="controller_server.go:1280"
2023-11-16T03:13:13.688131494Z time="2023-11-16T03:13:13Z" level=info msg="Listening for connections on address: &net.UnixAddr{Name:\"//csi/csi.sock\", Net:\"unix\"}" func="csi.(*NonBlockingGRPCServer).serve" file="server.go:100"

There is no evidence of anything wrong with longhorn-csi-plugin in this latest run.
Here are the latest livenessprobe logs from the support bundle:
2023-11-16T03:15:31.406665514Z W1116 03:15:31.406497   17969 connection.go:183] Still connecting to unix:///csi/csi.sock
2023-11-16T03:15:41.406718665Z W1116 03:15:41.406526   17969 connection.go:183] Still connecting to unix:///csi/csi.sock
2023-11-16T03:15:51.406020666Z W1116 03:15:51.405855   17969 connection.go:183] Still connecting to unix:///csi/csi.sock
2023-11-16T03:15:51.406094710Z F1116 03:15:51.405889   17969 main.go:146] failed to establish connection to CSI driver: context deadline exceeded

30 seconds after livenessprobe starts, it fails. From the code livenessprobe is expected to loop here indefinitely instead of failing. Due to the changes mentioned above, that does not happen.
The following sequence of events seems possible (though I have not managed to reproduce it):

longhorn-csi-plugin fails early and often. This is speculation, but maybe the longhorn-backend service is not up yet, so it cannot connect as it initializes.
Instead of waiting forever to connect to longhorn-csi-plugin via csi.sock, livenessprobe fails every 30 seconds.
Both longhorn-csi-plugin and livenessprobe fall into exponential restart backoff. As the backoff grows, it becomes possible for livenessprobe to start, fail to connect for 30 seconds, and die while longhorn-csi-plugin is waiting to start.
Eventually, longhorn-csi-plugin is able to consistently start successfully (as seen in the logs above). However, it always manages to do so at a time when livenessprobe is down.
Without livenessprobe, the liveness probe configured on longhorn-csi-plugin is guaranteed to fail. Kubernetes kills it.
Without longhorn-csi-plugin, livenessprobe cannot start. It fails (as seen in the logs above), and Kubernetes restarts it.

Additional evidence:

From the support bundle, longhorn-csi-plugin is in 5m0s exponential backoff. It last finished at 2023-11-16T03:15:51Z after having been up for 15s. Its exit code is 143, which is associated with graceful termination at the request of Kubernetes.
From the support bundle, livenessprobe is in 5m0s exponential backoff. It last finished at 2023-11-16T03:15:51Z.
If we continue this pattern, longhorn-csi-plugin and livenessprobe may eventually run successfully at the same time, but clearly the next many iterations will result in failure.

In the support bundle provided by @longhorn/qa, we were running longhornio/livenessprobe:v2.11.0. I'm not sure yet why this was the case, since we deploy longhornio/livenessprobe:v2.9.0 by default still. Maybe we were actively testing an improvement?

One mystery solved. https://github.com/longhorn/longhorn/pull/6920 bumped the version of livenessprobe (and other CSI components) in deployment manifests. This change hasn't made it to any released versions yet, though. It is expected to see it in v1.5.x and master test builds, but not out in the wild.

Reproduce steps:

kubectl edit -n longhorn-system service longhorn-backend and change the port from 9500 to 9501. This effectively breaks the longhorn-backend service temporarily.
kubectl delete -n longhorn-system pod longhorn-csi-plugin-<xxxxxx>.
Wait some length of time. All three containers go into CrashLoopBackoff.
kubectl edit -n longhorn-system service longhorn-backend and restore the correct port.
Monitor longhorn-csi-plugin. It can never recover (or at least not for a long time) and exhibits the behavior described above.

In the example below, I kept the longhorn-backend service broken for 6m30s. The situation was not improved 7m30s after that.
longhorn-csi-plugin-6zxtn                           0/3     CrashLoopBackOff   16 (1s ago)     6m36s
longhorn-csi-plugin-6zxtn                           2/3     CrashLoopBackOff   18 (2m11s ago)   8m46s
longhorn-csi-plugin-6zxtn                           0/3     CrashLoopBackOff   18 (2m41s ago)   9m16s
longhorn-csi-plugin-6zxtn                           0/3     CrashLoopBackOff   18 (1s ago)      9m17s
longhorn-csi-plugin-6zxtn                           1/3     CrashLoopBackOff   19 (2m27s ago)   11m
longhorn-csi-plugin-6zxtn                           1/3     CrashLoopBackOff   20 (2s ago)      11m
longhorn-csi-plugin-6zxtn                           0/3     CrashLoopBackOff   20 (1s ago)      12m
longhorn-csi-plugin-6zxtn                           2/3     CrashLoopBackOff   22 (2m16s ago)   14m
longhorn-csi-plugin-6zxtn                           0/3     CrashLoopBackOff   22 (2m46s ago)   14m
longhorn-csi-plugin-6zxtn                           0/3     CrashLoopBackOff   22 (2s ago)      14m

Deleting longhorn-csi-plugin-6zxtn immediately resolved the issue.

I replaced livenessprobe v2.11.0 with v2.10.0. While the other two containers went into a crash loop (as expected) when the longhorn-backend service was broken, the livenessprobe container did not.
W1218 22:53:48.550210  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:53:58.549453  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:54:08.549543  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:54:18.550311  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:54:28.550369  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:54:38.550120  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:54:48.549873  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:54:58.549510  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:55:08.549488  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:55:18.550327  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:55:28.549449  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:55:38.552287  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:55:48.549367  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:55:58.549464  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:56:08.549487  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:56:18.549671  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:56:28.549355  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:56:38.549645  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:56:48.549588  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:56:58.549452  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:57:08.549906  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:57:18.549325  114434 connection.go:173] Still connecting to unix:///csi/csi.sock
W1218 22:57:28.549934  114434 connection.go:173] Still connecting to unix:///csi/csi.sock

Since the containers were deep into backoff when I restored the service, it took still took a while to recover (had to wait for the longhorn-csi-plugin container to be allowed to restart). However, full recovery eventually occured.
longhorn-csi-plugin-dgrgh                           2/3     CrashLoopBackOff   10 (92s ago)    5m36s
longhorn-csi-plugin-dgrgh                           1/3     CrashLoopBackOff   10 (2m2s ago)   6m6s
longhorn-csi-plugin-dgrgh                           1/3     CrashLoopBackOff   10 (15s ago)    6m20s
longhorn-csi-plugin-dgrgh                           2/3     CrashLoopBackOff   11 (30s ago)    6m35s
longhorn-csi-plugin-dgrgh                           3/3     Running            12 (2m53s ago)   8m58s

Ideas to fix (in order of preference?):

Patch upstream livenessprobe to restore previous behavior. Revert to v2.10.0 (or v2.9.0, since we already have a Longhorn version of it) in the meantime.
Add a startup probe to the longhorn-csi-plugin container with a 5m window or configure its livenessProbe.initialDelaySeconds to 5m. Kubernetes will not kill this container for the first five minutes it is alive. This will keep it alive long enough for livenessprobe to connect with it whenever it comes back, but maintain the existing probe behavior after startup.
~Rework longhorn-csi-plugin startup so that it does not crash if it cannot connect to the longhorn-backend service. This may prevent the offset CrashLoopBackoffs from occurring in the first place.~ Kubernetes liveness probes will still fail, since the container is not ready. This only works as a potential addendum to 2.

Mine seems to have been sorted by restarting the node, it's a transient weirdness unfortunately.. will send a support bundle once I get one.

Mine seems to have been sorted by restarting the node, it's a transient weirdness unfortunately.. will send a support bundle once I get one.

Yes, I think that fits with the analysis I've done. Even without the bundle, can you confirm which version of the livenessprobe image you are running in your cluster? For example:
eweber@laptop:~/bundles/z1-00978262> kl get pod -l app=longhorn-csi-plugin -oyaml | grep livenessprobe
      image: longhornio/livenessprobe:v2.9.0
      image: docker.io/longhornio/livenessprobe:v2.9.0
      imageID: docker.io/longhornio/livenessprobe@sha256:555e27888f3692ab4130616ce4de62f950bdac16da3af4c432e13a71604e0261
      image: longhornio/livenessprobe:v2.9.0
      image: docker.io/longhornio/livenessprobe:v2.9.0
      imageID: docker.io/longhornio/livenessprobe@sha256:555e27888f3692ab4130616ce4de62f950bdac16da3af4c432e13a71604e0261
      image: longhornio/livenessprobe:v2.9.0
      image: docker.io/longhornio/livenessprobe:v2.9.0
      imageID: docker.io/longhornio/livenessprobe@sha256:555e27888f3692ab4130616ce4de62f950bdac16da3af4c432e13a71604e0261

I reviewed https://github.com/longhorn/longhorn/issues/6916 and it looks like we really do need to go to livenessprobe v2.11.0 if we want to mitigate the CVEs it mentions.
The upstream bug has some traction, but it's unlikely we'll see a version we can grab and test before v1.6.0 releases. I'll move forward with my mitigation PR.

I reviewed #6916 and it looks like we really do need to go to livenessprobe v2.11.0 if we want to mitigate the CVEs it mentions.
The upstream bug has some traction, but it's unlikely we'll see a version we can grab and test before v1.6.0 releases. I'll move forward with my mitigation PR.
* [x]  Create an issue to revert the mitigation when we upgrade livenessprobe if the mitigation changes are approved and merged.

ref: https://github.com/longhorn/longhorn/issues/7428

Verified passed on master-head (longhorn-manager 859d438) following test steps https://github.com/longhorn/longhorn/issues/7116#issuecomment-1861814093 and https://github.com/longhorn/longhorn-manager/pull/2388#issuecomment-1868012280. longhorn-csi-plugin pods can run stable after backend service restored.
Also ran negative test case Restart Cluster While Workload Heavy Writing for 60 times, didn't observe this issue. Test results:
https://ci.longhorn.io/job/private/job/longhorn-e2e-test/133/
https://ci.longhorn.io/job/private/job/longhorn-e2e-test/134/
https://ci.longhorn.io/job/private/job/longhorn-e2e-test/135/


Update linux env file for SPLUNK_MEMORY_TOTAL_MIB

Is this file documented?  I see the parent directory path is printed post-installation but not immediately seeing any mentions of its purpose.

Is this file documented? I see the parent directory path is printed post-installation but not immediately seeing any mentions of its purpose.

It's mainly for users who install the deb/rpm packages manually instead of via the installer script, which will configure this file according to the command-line options.
I'll add instructions to the readme in a separate PR for installing the packages without the installer script, and how to use this file to set the env vars for the default config.


lightbox package fails to build with yarn install

After unzipping the source, building with yarn install fails with following error:

lerna ERR! yarn run prepare exited 1 in '@maker-ui/lightbox'
lerna ERR! yarn run prepare stdout:
yarn run v1.22.4
$ microbundle --no-compress --jsx React.createElement
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run prepare stderr:
node-resolve: setting options.module is deprecated, please override options.mainFields instead
node-resolve: setting options.jsnext is deprecated, please override options.mainFields instead
node-resolve: setting options.module is deprecated, please override options.mainFields instead
node-resolve: setting options.jsnext is deprecated, please override options.mainFields instead
node-resolve: setting options.module is deprecated, please override options.mainFields instead
node-resolve: setting options.jsnext is deprecated, please override options.mainFields instead
Error: 'default' is not exported by src\play.svg
at xxxxxxxxxx\maker-ui\packages\lightbox\src\Preview.js:4:7
2: import { Box } from 'theme-ui'
3:
4: import playIcon from './play.svg'
^
5:
6: const Preview = ({ index, set, urls, show }) => {
error Command failed with exit code 1.
lerna ERR! yarn run prepare exited 1 in '@maker-ui/lightbox'

Hey! Thank you very much for your interest in the project.
I'm currently rebuilding everything in Typescript and implementing my own Box component that should resolve this bug and a few others in @maker-ui/components (see the typescript branch for progress updates).
Closing this for now as the API will be a little different in the next 2 weeks.


Is there a way to create an instance of vscode.TextDocument?

Is there a way to create an instance of vscode.TextDocument?

Do you mean a new Untitled file?
https://stackoverflow.com/questions/41068197/vscode-create-unsaved-file-and-add-content

i have a TextDocument, and can i get the parent dir of the file? so i want to create a TextDocument

const parentDirPath = path.join(document.uri.fsPath, '..');// where `document` is `vscode.TextDocument`

i hava a file path of parent dir 。 and i want to get a TextDocument represent that file

TextDocument is  ... a text document. You can't make a text document out of a directory.
Do you perhaps want to create a file inside that directory?

You must use openTextDocument to open or create one (see docs). However, there is no API to ready/write arbitrary file objects.

@jrieken thanks~


Ditch RBFormatter in place of RBConfigurableFormatter

The default formatter in a Dolphin image is RBFormatter. We should replace this with the better, configurable, RBConfigurableFormatter, as has been done in Pharo (for example).

Not pressing. The formatter is available to use if desired.


Testing, please ignore. (hhoypv)

This is a bug bounty test. Please ignore.. Please DO NOT APPROVE THIS! (hhoypv)

你好，邮件已收到。


Issue while trying to compile: "sorry, unimplemented: non-trivial designated initializers not supported"

Hi,
I get this message when I try compiling using this library.
My code is the example at https://github.com/stm32duino/X-NUCLEO-53L5A1/blob/main/examples/X_NUCLEO_53L5A1_HelloWorld/X_NUCLEO_53L5A1_HelloWorld.ino
I get these messages while trying to compile:
`
Arduino: 1.8.15 (Linux), Board: "Arduino Uno"
WARNING: library STM32duino_VL53L5CX claims to run on stm32 architecture(s) and may be incompatible with your current board which runs on avr architecture(s).
In file included from /home/angelo/Arduino/libraries/STM32duino_VL53L5CX/src/vl53l5cx_api.cpp:41:0:
/home/angelo/Arduino/libraries/STM32duino_VL53L5CX/src/vl53l5cx_buffers.h:21564:1: error: too many initializers for 'const uint8_t [0] {aka const unsigned char [0]}'
};
^
/home/angelo/Arduino/libraries/STM32duino_VL53L5CX/src/vl53l5cx_buffers.h:21564:1: sorry, unimplemented: non-trivial designated initializers not supported
/home/angelo/Arduino/libraries/STM32duino_VL53L5CX/src/vl53l5cx_buffers.h:21564:1: sorry, unimplemented: non-trivial designated initializers not supported
/home/angelo/Arduino/libraries/STM32duino_VL53L5CX/src/vl53l5cx_buffers.h:21564:1: sorry, unimplemented: non-trivial designated initializers not supported
/home/angelo/Arduino/libraries/STM32duino_VL53L5CX/src/vl53l5cx_buffers.h:21564:1: sorry, unimplemented: non-trivial designated initializers not supported
exit status 1
Error compiling for board Arduino Uno.
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
`
Any ideas? Thanks in advance.

Hi @angeloov
Unfortunately, as stated by the log, this library is not compatible with avr architecture as avr gcc is too old.
See https://github.com/stm32duino/VL53L5CX/issues/8#issuecomment-1127388699
Duplicated of #8


Rhode Island - Onboard to UP

Problem statement
Rhode Island has expressed interest in receiving more conditions than just COVID. As such, we want to learn what they want to receive and get them successfully added to the Universal Pipeline.
What you need to know

Rhode Island is already connected to ReportStream through the COVID pipeline
TBD

Closing, work completed.


TestCNIReachability test flakes

https://prow.istio.io/view/gcs/istio-prow/logs/integ-pilot-k8s-tests_istio_postsubmit/1220
https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/20458/integ-pilot-k8s-tests_istio/6910
https://prow.istio.io/view/gcs/istio-prow/logs/integ-pilot-k8s-tests_istio_postsubmit/1220

Still flaking now with the wait, presumably still the race. https://prow.istio.io/view/gcs/istio-prow/logs/integ-k8s-116_istio_postsubmit/1262. Are we turnign on the pod fixer by default in master?

Fixed, the issue was a mismatch in the container name on validator


Multiple path template support?

ResourceDescriptor#pattern now returns a list of patterns strings. How do we handle these values when there is more than one?

The annotations have been updated and this has been answered. Closing.


Need help?

I just cloned the repo as I'm very curious about this project. But there seems to be some work to be done to make it easy to use. Currently it seems to have a dependency on a few global variables and there's a quite dirty hack to check if a callback has been called by using Thread.sleep.
Just wondering if there's anything I could do to help to push this forward?

Hi @andersekdahl,
Yes the usability is not all that great...well actually it is but its simply not documented! Its on my todo list of this week.
Its mainly uses a global var called SuperChargedReact = {} which we store some variables, settings and callback output in. The main reason for this is to allow for ReactRouter to be used. We need to be able to pass in the url requested and then the router uses a callback which we can't control in order to render out the correct component. What we have to do is get this to render out its results as a string and store them back into a var in the SuperChargedReact object.
We don't know when that callback will finish processing as its async within the JS engine hence the "dirty hack" of putting a timer in to poll when the variable has been populated or not. This is not ideal but is there for a reason.
The obvious way to do this would be to get the JS engine to call back out to the host environment (aka .net) and let it know its finished (ie pass the callback to .net) but this has a few draw backs. We would still need to await the callback firing into .net so some waiting around would be required. Additionally when creating a new context their is a performance penalty if you want to link the host to the JS engine, how bad this is we've not bench tested but on the ClearScript site they say there are some big savings to be made (and curse me for not book marking the forum posts I'm referencing to back this up, again I'll have to return with the links in another post). Hence us trying the Thread.sleep idea.
I don't think the length of the sleep is correct (its massive really) but it should work for most peoples computers for now, again in the docs we'd discus tweaking this value to see what you can get away with. I've got an idea to have a way to train it to find the minimum amount of time it needs to perform the task in one interation and set it to that, that should give the fastest response time it can most of the time. Alternatively we could maybe play around with using await somewhere. But before I did that I would like to see the speed penalty if any of linking the host to the js engine and seeing if we can't get that working. So yes it is a "dirty hack" but one that is in there due to some thought. Its a pragmatic hack ;)
If you want to push this area forward let me know your thoughts/ideas on the above and if you want to have a play around with a possible tweak please do so. For my side of the bargain I'll write up some info on how to get up and running with this code better, I'm well aware we have some gaps!
Thanks for the interest.
Cheers
Pete


feat repo API support

#43
WIP

I have completed the requirements  in #43 , v0.2.0 maybe able to be released on time.

Modified the code and submitted a new PR #59 .


Update iacmData.ts

Update IaCM Roadmap
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664b96947c57ca02ccac9a03--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664bacc6d8a3d019e56cbede--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664baccb3800ea1c952b775d--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664bacd356a6511c4a08f681--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66abecd3a7f4c749b21e1fea--harness-developer.netlify.app

@richardblack-Harness do you still need this one?

@richardblack-Harness do you still need this one?

@ravilach Our roadmap items are in place for Q3 and beyond, I will close this.


Throwing error immediately after installation

Getting the following error in the Terminal immediately after installing the extension:
$ node -e 'require(\"fs\").writeFileSync(\"C:\\Users\\<USERNAME>\\AppData\\Local\\vscode-sqltools\\Data\\.node-runtime\", process.exec
Path)' && exit 0
[eval]:1
require(\"fs\").writeFileSync(\"C:\\Users\\<USERNAME>\\AppData\\Local\\vscode-sqltools\\Data\\.node-runtime\", process.execPath)
        ^

SyntaxError: Invalid or unexpected token
←[90m    at new Script (node:vm:100:7)←[39m
←[90m    at createScript (node:vm:257:10)←[39m
←[90m    at Object.runInThisContext (node:vm:305:10)←[39m
←[90m    at node:internal/process/execution:75:19←[39m
    at [eval]-wrapper:6:22
←[90m    at evalScript (node:internal/process/execution:74:60)←[39m
←[90m    at node:internal/main/eval_string:27:3←[39m

Desktop (please complete the following information):

SQLTools Version: 0.4.1
VS Code Version: 1.73.1
OS: Windows 11
Driver:

[ ] MySQL/MariaDB

Additional context
Reinstalling the extension and/or restarting VSCode doesn't help. Creating/removing the .node-runtime folder doesn't help either. Shows this message when VSCode starts:

On the dropdown on the Terminal tab of the Panel, which shell is marked as your default?

Git Bash

The algorithm for detecting the path of a node runtime isn't handling the case where a Windows instance of VS Code is using Git Bash as the default shell.
@Shujee a workaround for you is to edit your user-lever settings.json file and look for sqltools.useNodeRuntime. If you find it, delete the line. If you still get the problem, check the file .vscode/settings.json in the workspace you opened in VS Code, and remove that setting from it.
Knowledge of where your node runtime is located is only required if you are using the SQLite driver.

Thanks @gjsjohnmurray . Fixed it for me.

Resolved by #1059


Update IC Candid Files

Motivation
The Internet Computer APIs have updated.
Changes

Updated the interface description files for the Internet Computer.
Updated the javascript bindings for the latest IC interface.

Tests

[ ] Please check the API updates for any breaking changes that affect our code.

The title and description of this automated PR is misleading. It isn't the IC description but the definition of various canisters.
Can you update this automation?

The title and description of this automated PR is misleading. It isn't the IC description but the definition of various canisters. Can you update this automation?

How about this? https://github.com/dfinity/ic-js/pull/533


Large images only partially load

Another developer and I independently discovered a problem. We each made applications that load a large image. When displaying the large image however, the Elm app would only display most of it; most of the bottom portion of the image would just be gray. We thought it was our code, but I discovered that if I use Elm-Reactor just to serve up the image, the problem is still there. I made a simple html file that just loads our large images and there was no problem. The problem persisted with multiple large images and multiple file types.
Elm Version
0.18
Browser
I experienced the problem in Chrome and Firefox.
Reproducing
Put a large image (>1mb) in a directory, and run Elm-Reactor in that directory. Open up localhost:8000/.

Reproduced the same issue


Update to v1.20

Description
Updates Mockbukkit to v1.20
Checklist
The following items should be checked before the pull request can be merged.

[x] Code follows existing style.
[x] Unit tests added (if applicable).

This is blocked by #790


Evaluation using LMM data.

Waiting on more samples from LMM.  Current results with 8 samples are uninformative.

With 38 samples, 8 of which have truth data we find 6 out of 8 confirmed CNVs.  When applying a simple post-calling filter of rejecting segments on which both duplications and deletions are called (evidence of tangent normalization failing) there is only 1 false positive.  I strongly suspect that issue #375 (testing in progress) or issue #378 will eliminate false positives in a more principled way.

Done with original germline model; issue #541 is for new model.


Request event listener running too early?

Hi,
I just wondered why the request event listener needs to run so early in the priority? I've had an issue with it loading before other high priority event listeners, which are required to process the message. Would you consider setting the priority to the default (0), or maybe allow this to be configured? Happy to submit a pull request if you think this is a good idea 🙂
Many thanks,
Dan

PR if you think this is a good idea: https://github.com/uecode/qpush-bundle/pull/129


crashes at _cgo_topofstack

Go version
go1.21.1
Output of go env in your module/workspace:
android

What did you do?
"I'm running a cgo application in an Android environment, and it crashes at _cgo_topofstack. How can I troubleshoot this issue?"
What did you see happen?
crash report
signal 11 (SIGSEGV), code -6 (SI_TKILL), fault addr --------
    r0  00000000  r1  000028f3  r2  0000000b  r3  00000008
    r4  00002829  r5  92589500  r6  92589548  r7  0000010c
    r8  00000007  r9  f2dda124  r10 92589400  r11 bc3218ca
    ip  bf21e9cc  sp  eeb7fc00  lr  bb39d2f8  pc  bb3c07d8

backtrace:
      #00 pc 0049a7d8  /data/app/~~RaMB3k_xm7v41sDHB5G52Q==/com.tencent.supercar-Qe2_Smo7BnMcTvBrMSmgRA==/lib/arm/libtskm.so

addr2line result
./arm-linux-androideabi-addr2line -e /Users/jackieluo/Downloads/houzhuang/armeabi-v7a-r20b/libtskm.so -f -C 0049aab0
_cgo_topofstack
??:?

What did you expect to see?
no crash

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions

I have the same problem on iOS


NFT_STORAGE_TOKEN = ""

Could you tell me what kind of data I should put into the NFT_STORAGE_TOKEN ?
It is located in config/config-token.ts
export const NFT_STORAGE_TOKEN = "";

Nft storage isn't working anymore, use PINATA SDK


port createNewLayer from L.esri.featureLayer for renderer plugin

just a small tweak to make Cluster.featureLayer look more like esri.featureLayer for the sake of https://github.com/Esri/esri-leaflet-renderers/pull/158
to be honest, i have no clue how this was working in<EMAIL_ADDRESS>

this branch has been rebased.
for this PR or any other i ever open, feel free to pile on additional commits, --force push, rebase, close or anything else you'd like at will.

@jgravois I was in the process but a meeting popped up and you beat me to it. thanks much though!

released in https://github.com/Esri/esri-leaflet-cluster/releases/tag/v2.1.0


activate extension tab in a split view by mouse click

in case you have the extension tab in a split view, because the view is read-only it means u cant activate it with a mouse click like any other tab,
which means if u tried to close it you will close a different tab "the previously focused one" and your only solution would clicking on the extension tab it self to make it active.

I think #71774 has fixed this in 1.34 Insiders

just tested it out and u r correct


Unable to view the containers in storage explorer under storage account which I created

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.24.3
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
Windows 10
Bug Description
Storage explorer not opening the containers
Steps to Reproduce

Launch Storage explorer
Expand the containers

Actual Experience
Create storage account and blob container in azure and installed storage explorer to access it from tool.
Added the SA as local in explorer and while opening the containers, getting error
Expected Experience
NA
Additional Context
NA

@venu564 How did you connect to the storage account in Storage Explorer? Did you connect to it as a local attachment or from your signed-in azure account? What error did you get when trying to access it?

Closing due to lack of response. If you still have issue, please open a new issue with the additional information.