Implementation is incorrect for analytical Jacobian

Hi!
I'm working on bounded least-squares algorithms for scipy in GSoC this year. I was surprised by completely inadequate performance of leastsqbound in bounded problems, see my benchmarks.
I determined the reason after running benchmarks with numerical Jacobian approximation, when leastsqbound started to work rather well. If we do variables transformation we need to compute the Jacobian with respect to the new variables, J' = J T, where T is the Jacobian of transformation T_ij = dx_i / dx'_j. This isn't done in the code, so the Jacobian used is irrelevant to the new variables, thus the performance is poor.
Update for clarification:
These lines are the source of error. We need to pass modified Jacobian to leastsq. I know that you consider transformation in the end (line 347), but it isn't enough.

@nmayorov   I have a hard time following your table.  "g_norm" isn't defined, you say that "value" is "for convenience" but otherwise undefined, and you identify "nfev" as an important column.   I'd suggest that the number of evaluations is of secondary importance in comparison to getting a good estimate of the parameter values.  As far as I can tell, that information is missing from your comparison.    Perhaps it is what "g_norm" means?  Anyway, please define all your terms.
If I understand correctly, you're saying that the Jacobians are not calculated correctly when the bounds transformation is used.   It is correct when done internally (ie, with lmdif instead of 'lmder'), as the minimization is done fully on the "internal" variables.   You didn't actually mention whether you are even supplying Jacobian functions for any of your tests.  If you are supplying Jacobians, it sort of depends what you expect them to do.
I do believe your basic point that the results with user-supplied Jacobians is confusing, and it would be better to transform the result of the user-supplied Jacobian (expected to work solely on "external variables") back to "internal" variables.   Is that a correct interpretation?  Can you provide PRs for leastsqbound and lmfit (which is slightly diverged from leastsqbound)?

I'm can't add much to this discussion besides saying that I would be happy to accept any changes to leastsqbound which would address this issue.  My use of leastsqbound does not require a Jacobian so that portion of the code is not well tested.

@newville
Yes, this benchmark report should be better, sorry. I define g_norm in my notes at the beginning. It is the standard infinity-norm of the gradient in unconstrained case. In a constrained case it is the infinity-norm of properly scaled gradient to account for the presence of bounds, I use this concept in one of the algorithms I'm working on in GSoC. At the optimal point it is exactly zero, please read my post if you are interested in details.
value is the objective value we are minimizing, the sum of squares. If you don't trust my mysterious g_norm you can roughly judge the performance by looking at it.

If I understand correctly, you're saying that the Jacobians are not calculated correctly when the bounds transformation is used. It is correct when done internally (ie, with lmdif instead of 'lmder'), as the minimization is done fully on the "internal" variables.

It is the main point!

You didn't actually mention whether you are even supplying Jacobian functions for any of your tests. If you are supplying Jacobians, it sort of depends what you expect them to do.

Yes, all problems use analytical (user supplied) Jacobian. Again, sorry for not saying that.

I do believe your basic point that the results with user-supplied Jacobians is confusing,

They are not confusing, they just not satisfactory, the algorithm doesn't converge to optimal point.

and it would be better to transform the result of the user-supplied Jacobian (expected to work solely on "external variables") back to "internal" variables. Is that a correct interpretation?

It's not just better, it is the only correct way.

Can you provide PRs for leastsqbound and lmfit (which is slightly diverged from leastsqbound)?

I think I will, but it's not the top priority now (I hope you understand).
Please feel free to ask any questions, as my explanations tend to be not very clear.

I improved the benchmark report, hopefully it will make more sense to you now.

@nmayorov Any change you could create a small self contained example which shows the issue?  This would help me to fix this issue faster than trying to pull out an example from your benchmarks myself.

Yes, give me a 15 minute. I will prepare gist.

I think it's illustrative enough https://gist.github.com/nmayorov/99edcab1f701893755f1

Thanks for the example, very helpful.  I now understand the cause of the issue, I'll try to devise a fix so that the Jacobian is properly adjusted for the variable transform.  This might take a bit (a number of days) as leastsqbound is a hobby project for me. If you find a solution before then please submit a PR.

@newville https://github.com/newville
Yes, this benchmark report should be better, sorry. I define g_norm in my
notes at the beginning. It is the standard infinity-norm of the gradient in
unconstrained case. In a constrained case it is the infinity-norm of
properly scaled gradient to account for the presence of bounds, I use this
concept in one of the algorithms I'm working on in GSoC. At the optimal
point it is exactly zero, please read my post
https://nmayorov.wordpress.com/2015/06/19/trust-region-reflective-algorithm/
if you are interested in details.
value is the objective value we are minimizing, the sum of squares. If
you don't trust my mysterious g_norm you can roughly judge the
performance by looking at it.
If I understand correctly, you're saying that the Jacobians are not
calculated correctly when the bounds transformation is used. It is correct
when done internally (ie, with lmdif instead of 'lmder'), as the
minimization is done fully on the "internal" variables.
It is the main point!

OK, good to know.  Thanks for clarifying.
You didn't actually mention whether you are even supplying Jacobian

functions for any of your tests. If you are supplying Jacobians, it sort of
depends what you expect them to do.
Yes, all problems use analytical (user supplied) Jacobian. Again, sorry
for not saying that.
I do believe your basic point that the results with user-supplied
Jacobians is confusing,
They are not confusing, they just not satisfactory, the algorithm doesn't
converge to optimal point.

Well, that's because you assumed that the Jacobians should work a certain
way (specifically, without knowledge of how the bounds are implemented). I
completely agree that this is a reasonable assumption.

and it would be better to transform the result of the user-supplied
Jacobian (expected to work solely on "external variables") back to
"internal" variables. Is that a correct interpretation?
It's not just better, it is the only correct way.

Well, one could imagine taking the bounds mechanism into account in the
Jacobian function.  I am not at all suggesting that this should be expected
of the user of leastsqbound or lmfit.   So, I would agree that is the best
way, but not that it is the only way.
It looks to me like it is necessary to have  something like
_external2internal_grad, that applies the chain rule for bounded
variables and change the wrapped Dfun (wDfun) to use this.  Do you all
agree?

Can you provide PRs for leastsqbound and lmfit (which is slightly
diverged from leastsqbound)?
I think I will, but it's not the top priority now (I hope you understand).

Yes, I do understand.   Thanks for identifying the problem!  Of course, we
want to fix it soon, but probably have less time to look into this than
you've already spent looking at the problem.

It looks to me like it is necessary to have  something like
_external2internal_grad, that applies the chain rule for bounded
variables and change the wrapped Dfun (wDfun) to use this.  Do you all
agree?

That was my thought on what need to be done.

It looks to me like it is necessary to have  something like
_external2internal_grad, that applies the chain rule for bounded
variables and change the wrapped Dfun (wDfun) to use this.  Do you all
agree?

That's exactly what is required :)

@nmayorov Awesome!   Thanks!


[tr] devops.md localization to Turkish

Describe your changes
Add Turkish I10n for DevOps
Google Doc: https://docs.google.com/document/d/1kX_JAtZo9FnEeJtTV-zZQt4Wu0PxS0skxCBp1v_nF4k/edit#heading=h.mo94ylk0tzfj
Preview: https://deploy-preview-2698--cncfglossary.netlify.app/tr/devops/
Related issue number or link (ex: resolves #issue-number)
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@symys - Can you please fix the commit signings and PR description checklist to make sure everything is in place?

@symys
Now that dev-tr branch is merged to main, can you rebase your commit onto main and create this PR against main? Or start from scratch ;)

@symys
Sorry, I was wrong earlier. I thought we can now work against the main branch, but the Glossary development workflow requires us to still work against the dev-tr branch.
See https://cloud-native.slack.com/archives/C02N2RGFXDF/p1709745926614219

@symys however, you still need to fix the DCO issue (commit sign off).

@symys We're good to go here, except the DCO issue


Add 'Move Up One' and 'Move Down One' functions for audio object in Course Reserve List

[ ] Works as expected.


Tag renaming does not work in Firefox

Describe the bug
Firefox does not show the 3-dot context menu when hovering over a tag in the right sidebar
Steps to reproduce

Create en entry having a tag
Goto home or explore
Hover over the tag
'#' should turn into 3 dots

The version of Memos you're using
v0.22.5
Screenshots or additional context
No response

Are you in tree view? Currently the ⋮ only displays in default tag view and not in tree view

Yes, that is correct.


Memory leak in Docker image

What version of Music Assistant has the issue?
2.2.5
What version of the Home Assistant Integration have you got installed?
2024.9.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
I added the Monitor Docker integration and noticed that the Music Assistant Docker instance leak memory, about 15 MB per minute.

I'm currently not using Music Assistant much, I have Squeezebox radio added as a player and a misconfigured Spotify music provider.
When left alone the container used over 2 Gb in just a few hours.
How to reproduce
Unsure. Install music assistant as a Docker container and monitor memory usage, for example using the HA addon "Monitor Docker".
Music Providers
Spotify, not sure if this one is trigging the leak.
Player Providers
Squeezebox
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.9.2
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

music-assistant.log
Log file

You are the only one reporting this. Also I cant reproduce. I wonder if its because of the misconfigured spotify provider.
Can you either try to remove that provider from the settings or set it up correctly ?

I've configured Spotify and played some music. Still leaks memory.

Container started with docker compose:
services:
  musicassistant:
    image: ghcr.io/music-assistant/server
    domainname: docker.example.com
    hostname: ma
    restart: unless-stopped
    container_name: musicassistant
    volumes:
      - /home/user/ma:/data
    networks:
      ha:
        ipv6_address: 2001:db8::8
        ipv4_address: <IP_ADDRESS>
    privileged: true
    mem_limit: 250mb # set to avoid the cointainer growing and allocation all memory

networks:
  ha:
    name: my-macvlan-net
    external: true

Is it possible to use tracemalloc or some other python tools to find the leak?

I HIGHLY doubt there is a leak. You are really the only one reporting this and none of my 3 test instances show this behavior.
Also 250 mb is on the low side. We need at least 500mb memory for optimal performance.
Remember we have to move around a large amount of audio chunks and to prevent doing I/O we cache in memory.
Next to that lots of other stuff gets cached in memory.
Can't you just let it run and see if it stabilizes around 500mb ?

I've changed the limit til 750MB and the container runs stable now. I think the issue I had started when Spotify for some reason forced me to change the account password. To reproduce one might add and setup Spotify, change Spotify password and wait for the autentication token Music Assistant uses times out.

As Marcel suggested this doesn’t seem to be an issue so closing.

I've changed the limit til 750MB and the container runs stable now. I think the issue I had started when Spotify for some reason forced me to change the account password. To reproduce one might add and setup Spotify, change Spotify password and wait for the autentication token Music Assistant uses times out.

Great, thanks for testing and confirming. Just let us know if you do feel that the memory keeps expanding.


Minor Fix for Junit Python Script

Handles error if DBMS is not ready for junit

Experiencing a timeout in jenkins now


make default browser value as NULL

make browser=NULL or remove it completely from carina-demo

done: https://github.com/qaprosoft/carina-demo/commit/8552f8920ddb9d7744243667af5e1186e39f5494


reconcile cloudstack datacenter

Issue #, if available:
datacenter reconciler#1267
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I left a few comments before looking at the PR holistically and realizing this seems like boilerplate, is that right?

Is this PR boilerplate only?

Added setdefault for now, will add datacenter validator and validations in later prs

/lgtm

/lgtm


Add PointerEvent polyfill

Hello.
Is it possible to add polyfill for PointerEvent ?

Yes, we could add https://github.com/wessberg/pointer-events but I can't see which browser versions it supports

It would be nice, thanks. We have already used that polyfill in our project and it's quite uncomfortable to load polyfills from two different sources.
I think it supports all browsers which don't support PointerEvent, but I'm not quite sure about that


SciBertClassifier does not work with spacy-transformers 0.5.2

One easy to reproduce this is by adding a parameter pretrained="scibert" to the test for bert_classifier. This throws ValueError: Unsupported transformers config name: 'models/scibert_scivo...
One way of resolving this for now is to pin the version to 0.5.1.

This is a nightmare.

I think this is resolved by #190

I think this is resolved by #190


Make Grafana load event frame graph with date range = event frame date range

See #58.

Actually - maybe not a duplicate. @jmbeisner - are you saying set the grafana x-axis based on the event frame timestamp(s)?

@bfaivre - Yep exactly. Is that what you need grafana 4.7 for from #58?

No - this is a bit different. In 4.7 you can filter your template (parameters) based on the grafana time range the user selects. We'll have to research if you can set the dashboard time range by a query (or some other method).

@c49nelson, @jmbeisner - did you guys see that you can click and drag into a desired time range?

@jmbeisner, @kkotaich placing this one on the back burner and removing from the targeted v0.4.0 release.

@kkotaich going to close this issue for now since we can set the time range with the URLs we are building for the app buttons.


[CI]Support build on windows

I'm not familiar with windows, and I don't have a corresponding environment, if anyone wants to continue this, it can be done on my basis.


Size

Which connector were you using?
Kaggle
What's going wrong with this connector?
There was an error caused by the community connector. Please report the issue to the provider of this community connector if this issue persists.
Connector details
Please use smaller than 20MB csv files.
Error ID: 2313771d

This is expected behavior. This connector can only support data sets that are smaller than 20MB.


out of memory when training imagenet with .rec file.

Environment info
Operating System: ubuntu 16.04
Compiler: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Package used (Python/R/Scala/Julia): Python
MXNet commit hash: 8ad3c8a7a98dfa6bd6f5065cf9c3688f2414c3d4
Python version and distribution: Python2.7.12
Error Message:
The usage of memory, at the beginning of training is 5.7%-7.9% , after a while (3~4h) it takes 27% and finally it run out of my memory (waked up by the alarm message).
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

cd examples/image-classification && python train_imagenet.py --network my_net --gpus 0,1,2,3 --num-epochs 100 --lr 0.01 --lr-step-epochs 30,60,80,110 --batch-size 256 --top-k 5 --data-train /data_shared/datasets/ILSVRC2015/rec/train_480_q100.rec --data-val /data_shared/datasets/ILSVRC2015/rec/val_480_q100.rec --rgb-mean 123.68,116.779,103.939 --data-nthreads 4 --model-prefix ./my_net

What have you tried to solve it?

set the prefetch_buffer = 1 but the accuracy of my model drop to 20% and set prefetch_buffer back to 2,4,8, the accuracy is right!
cpu memory increase continually when set the prefetch_buffer = 1

also find some similar issues:
https://github.com/apache/incubator-mxnet/issues/1411
https://github.com/apache/incubator-mxnet/issues/3183
https://github.com/apache/incubator-mxnet/issues/2969
https://github.com/apache/incubator-mxnet/issues/2111
https://github.com/apache/incubator-mxnet/issues/2099

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


tf.losses.mean_squared_error does not support name parameter

Some times MSE is not the only loss in the model, and there maybe multiple MSE losses and adds up to the total loss, a custom name of mse loss layer without using name_scope can be helpful.

@Hong-Xiang I believe the reason a name_scope is used, rather than a single name parameter, is because mean_squared_error expands to multiple underlying operations.  Is there a reason why name_scope isn't sufficient for your use case?

@tatatodd Thank you for your explanation, name_scope is sufficient, the only problem is that it may lead a little mess to code than using name directly :-).

@Hong-Xiang OK cool.  And note that although it's a little more code to write, using name_scope has the additional benefit that your ops will be nicely grouped in visualization tools like TensorBoard.
I'm closing this out; feel free to file new issues if you run into them!  :)


Fix capitalisation of references in Readme .

The html generated for the 'Properties' section uses and a #properties link.
The local references to '#Properties' were not resolving to anything.

@IzakMarais Thank you 👍
Merged 🎉


NOISSUE - Refactor InfluxDB Reader: explicit check event + add safe conversion

What does this do?
This PR is a simple refactoring of influxdb measurement data.
Which issue(s) does this PR fix/relate to?
No issue related to this PR.
List any changes that modify/break current functionality
Have you included tests for your changes?
Still working
Did you document any new/modified functionality?
No
Notes

@tzzed thanks for the PR. Please sync your branch to the master.
@arvindh123 please review this PR

Codecov Report

Merging #1460 (6180558) into master (f4312ae) will decrease coverage by 0.03%.
The diff coverage is 66.66%.

:exclamation: Current head 6180558 differs from pull request most recent head 04e569e. Consider uploading reports for the commit 04e569e to get more accurate results

@@            Coverage Diff             @@
##           master    #1460      +/-   ##
==========================================
- Coverage   70.92%   70.88%   -0.04%
==========================================
  Files         123      123
  Lines        9564     9567       +3
==========================================
- Hits         6783     6782       -1
- Misses       2254     2257       +3
- Partials      527      528       +1

Impacted Files
Coverage Δ

readers/influxdb/messages.go
80.48% <66.66%> (-0.88%)
:arrow_down:

things/service.go
72.02% <0.00%> (-1.20%)
: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 f4312ae...04e569e. Read the comment docs.

the len's comparison to zero is more clear because we want to check the 0 value an empty array. len(v)  < 1 includes negatives values.
About the safe cast is just to avoid panic.
I just let myself to do this PR as a "good first issue" but you are free to close it.

@nmarcetic and @dusanb94 need to review and approve this one.

@tzzed if there is no action from your side to correct mentioned comment, this PR will be closed due to the inactivity.


Make sure library is 64 bit compatible

Coming up pretty soon, Android will require apps to be 64bit.

Hey Any idea when we'll be able to get the 64 bit compatible lib?

I think the author added x64 support:
it was on that branch - https://github.com/Beyka/Android-TiffBitmapFactory/tree/x64-support/src/main/jni/libs which merged into master.
i need it too, but didnt check it yet.

I think the author added x64 support:
it was on that branch - https://github.com/Beyka/Android-TiffBitmapFactory/tree/x64-support/src/main/jni/libs which merged into master.
i need it too, but didnt check it yet.

Library support x64 from first release.  Full list of available architecture support:
ARM v7
ARM v8-64
X86
X86-64
MIPS
MIPS-64


Include link to other troubleshooting page

There is another support page with extensive application troubleshooting that should be included with this https://support.microsoft.com/en-us/help/4509382/troubleshooting-application-deployment-in-configuration-manager

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

ID: d6783f42-7ea1-bbb5-9fd0-8eed2daf8c17
Version Independent ID: 9fc83fef-d55a-9f18-6a6a-8316ecaae740
Content: Troubleshoot app deployments - Configuration Manager
Content Source: sccm/apps/deploy-use/troubleshoot-application-deployment.md
Product: configuration-manager
Technology: configmgr-app
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @jandreacola for the suggestion! We've been working with folks in support to move some specific troubleshooting content from KBs (internal and external) over to core docs.
@mestew FYI

This is done. Vinay migrated that KB to docs: https://docs.microsoft.com/en-us/mem/configmgr/apps/understand/app-deployment-technical-reference (and it's linked from this article)


Question: panic: error creating server listener: No such file or directory

I'm trying to run cargo web start, but as I can see it is hyper error. Any thoughts on what could be wrong? The port is not in use.
thread 'main' panicked at 'error binding to <IP_ADDRESS>:8000: error creating server listener: No such file or directory (os error 2)', /home/darksome/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.12.35/src/server/mod.rs:116:17

The only thing hyper is doing there is trying to bind to the address, and the OS said "nope". Typical causes are that something else is indeed listening on that port.


Pylance showing "operator not supported for different types" error twice

 Environment data

Language Server version: 2023.4.31
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda): venv, 3.11.3
python.analysis.indexing: true
python.analysis.typeCheckingMode: basic

 Code Snippet

y = 10
z = y + "hello"

 Repro Steps

Open and save a new Python file
Add the code snippet above
Notice the error being added to the problems window twice:

 Expected behavior
Second line not to show up
 Logs

  Logs

2023-04-24 11:30:04.445 [info] [Info  - 11:30:04 AM] (18804) Pylance language server 2023.4.31 (pyright 5b6a1d3b) starting
2023-04-24 11:30:04.445 [info] [Info  - 11:30:04 AM] (18804) Server root directory: REDACTED\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.4.31\dist
2023-04-24 11:30:04.450 [info] [Info  - 11:30:04 AM] (18804) Starting service instance "titanic"
2023-04-24 11:30:04.502 [info] [Info  - 11:30:04 AM] (18804) Setting pythonPath for service "titanic": "REDACTED\Apps\titanic\.venv\Scripts\python.exe"
2023-04-24 11:30:04.509 [info] [Warn  - 11:30:04 AM] (18804) stubPath REDACTED\Apps\titanic\typings is not a valid directory.
2023-04-24 11:30:04.715 [info] [Info  - 11:30:04 AM] (18804) Assuming Python version 3.11
2023-04-24 11:30:04.984 [info] [Info  - 11:30:04 AM] (18804) Found 2 source files
2023-04-24 11:30:05.285 [info] [Info  - 11:30:05 AM] (18804) Background analysis(1) root directory: REDACTED\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.4.31\dist
2023-04-24 11:30:05.285 [info] [Info  - 11:30:05 AM] (18804) Background analysis(1) started
2023-04-24 11:30:05.612 [info] [Info  - 11:30:05 AM] (18804) Indexer background runner(2) root directory: REDACTED\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.4.31\dist (index)
2023-04-24 11:30:05.612 [info] [Info  - 11:30:05 AM] (18804) Indexing(2) started
2023-04-24 11:30:06.420 [info] [Info  - 11:30:06 AM] (18804) scanned(2) 43 files over 1 exec env
2023-04-24 11:30:07.371 [info] [Info  - 11:30:07 AM] (18804) indexed(2) 28 files over 1 exec env
2023-04-24 11:30:07.381 [info] [Info  - 11:30:07 AM] (18804) Indexing finished(2).

This occurs because pyright needs to do union expansion for the LHS and RHS types when analyzing a binary operator like +. For example, if the LHS is type str | bytes and the RHS is type int | str, it needs to check all four combinations of types (str + int, str + str, bytes + int, and bytes + str). Some of these may be valid (e.g. str + str) whereas some are not. The top-level error will say Operator "+" not support for types "str | bytes" and "int | str", whereas the second-level errors will list all of the combinations that don't work.
That said, I agree this looks incorrect when there are no unions involved as in your code sample above. I'll look at how we can handle the no-union case better.

This will be addressed in the next release of pyright.

It's now smart enough to determine when the secondary message is redundant.


[DO NOT MERGE] Backport the thread reuse and some bug fixes from master to ozone-1.4

What changes were proposed in this pull request?
Backport the following fixes from master to ozone-1.4 for 1.4.1:
HDDS-10387. Fix parameter number warning in KeyOutputStream and related classes (#6225)
HDDS-10383. Introduce a Provider for client-side thread resources passing (#6222)
HDDS-10384. RPC client reusing thread resources. (#6326)
HDDS-10564. Make Outputstream writeExecutor daemon threads. (#6418)
HDDS-9976. Memory leak for DeleteBlocksCommand when queue is full (#5845)
How was this patch tested?
https://github.com/xichen01/ozone/actions/runs/8644461640

@szetszwo @jojochuang please check that your commits are correctly cherry-picked.

@xichen01 , thanks for working on the backports!  The cherry-pick for HDDS-10387 looks good.

Since I don't have access to rebase merge, I'll push the commit for this PR directly to the ozone-1.4 branch so that cherry-pick doesn't get compressed.

Since I don't have access to rebase merge, I'll push the commit for this PR directly to the ozone-1.4 branch so that cherry-pick doesn't get compressed.

Done.
https://github.com/apache/ozone/commits/ozone-1.4/

These PR has been pushed to ozone-1.4 .


should gist:isCharacterizedAs be a subprop of gist:isCategorizedBy?

I think gist:isCharacterizedAs is a specialization of  gist:isCategorizedBy where the domain and range are fixed.
Whereas gist:isCategorizedBy doesn't fix the domain and range.

I think gist:isCharacterizedAs is a specialization of gist:isCategorizedBy

If anything, it is the reverse. One way to characterize something is to say what category it is in. There are possibly many other ways. However, we might not need gist:isCharacterizedAs - I've never found a use case for it.
Ironically, gist:isCharacterizedAs  is uncharacteristic of most gist properties, by having a very narrow domain and range. That goes against our guidelines.  If we keep  gist:isCharacterizedAs I hitnk it shoujld have no domain  or range and should be a supeproperty of gist:isCategorizedBy.

I think it should have no domain or range and should be a supeproperty of gist:isCategorizedBy.

I'd be happy with that as well, @uscholdm .
I think they likely belong in the same prop hierarchy (not top level siblings).
I was just using the presence of domain and range to be a cue that this is a specialization. Also isCharacterizedAs has "categorize" in its skos:defintion.
Also the skos:definition on gist:isCharacterizedAs seems to be backwards:
"A way to categorize a behavior."
While the domain is gist:Event and the range is gist:Behavior.
So I'f say that the Event is categorized by the Behavior -- the Behavior isn't being categorized.

I agree, the current definition seems a complete anomaly. I'd be in favor of dropping it, as you initially suggest, @uscholdm. What is the use case when isCategorizedBy is not appropriate?

Also the skos:definition on gist:isCharacterizedAs seems to be backwards:
"A way to categorize a behavior."

That's true. This is an ancient definition, needs to be updated if we keep the property.

PROPOSAL: delete the property isCharacterizedAs because it is historical and was never used, to my knowledge. The narrow domain and range are also historical, we don't do that these days. The main purpose it serves is to enable Event to have some axioms.  That is not a super-compelling reason.
gist:Event
	a owl:Class ;
	owl:equivalentClass [
		a owl:Restriction ;
		owl:onProperty gist:isCharacterizedAs ;
		owl:someValuesFrom gist:Behavior ;
	] ;

gist:isCharacterizedAs
	a owl:ObjectProperty ;
	rdfs:domain gist:Event ;
	rdfs:range gist:Behavior ;
	owl:deprecated "true"^^xsd:boolean ;
	skos:definition "A way to categorize a behavior."^^xsd:string ;
	skos:prefLabel "is characterized as"^^xsd:string ;
	.

We have deprecated the property in PR #951, so the issue is irrelevant.


⚠ Jenkins Plugins Artifactory has degraded performance

In f819850, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1191 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 26380d6 after 12 minutes.


Implement missing shims for Windows

Here we track shims that Miri currently only implements for Linux and macOS targets, but not for Windows.
If you run into this, try cargo miri test --target x86_64-unknown-linux-gnu. This works even on a Windows host (without installing anything extra) and interprets programs on a well-supported Linux target.

[ ] File system access (https://github.com/rust-lang/miri/issues/3482)
[x] Threading
[x] std::thread::sleep
[x] std::sync
[ ] Console functions (https://github.com/rust-lang/miri/issues/2652)

Also add RNG to the list (rand's default initial seed comes from the OS via BCryptGenRandom).

We do test that getrandom works on Windows, why isn't rand using that? For this to work we implement SystemFunction036 which is the actual name of RtlGenRandom. I thought supporting getrandom would be enough to cover RNG initialization.

In fact we even test this through rand:
https://github.com/rust-lang/miri/blob/2cdd1744b896e8129322229f253f95fd7ad491f1/test-cargo-miri/tests/test.rs#L28
@jmerdich  SmallRng::from_entropy() and rand::thread_rng() both work on Windows, so I cannot reproduce the problem you are describing.

Ah, looks like newer versions of getrandom changed which function they are using.

@jmerdich thanks for the notification, https://github.com/rust-lang/miri/pull/1755 should fix this. :)

@RalfJung thanks for the amazingly prompt fix! I got set up to contribute something for this and was surprised to find it already done! :D

Ah, sorry for that.^^
Fixing std::thread::sleep should be rather easy, if you are looking for something small to get started with. :)

Miri is great project, thanks!
I am trying to use miri on a regression test on windows, which uses fs::read_to_string. When doing so, I get an error
can't call foreign function `CreateFileW` on OS `windows`

To my understanding from this issue is that file system access is still not implemented for windows (it was added for Unix platforms 2019 in #923.
Is there a workaround for reading a regression reference in windows, such that miri does not complain (unfortunately I cannot use include_str! as it takes a string literal as argument)?

@mbyt you can run Miri with --target x86_64-unknown-linux-gnu. This works on Windows without WSL and without installing anything extra. Miri can then use its Linux support for file system access to emulate what the program does, and it should largely work for accessing Windows file systems as well. Please report an issue (a new issue) if it does not.

Since most of the small things are done now, I'll close this issue in favor of one that is specifically about file system access: https://github.com/rust-lang/miri/issues/3482.


chore(switch): move styles.scss to switch.scss

Deploy preview for pf-next ready!
Built with commit 24aa925eee60237af1e9d7fbc63825a217a9a1ad
https://deploy-preview-806--pf-next.netlify.com

:tada: This PR is included in version 1.0.59 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Macro cooldown

A configurable cooldown between macro invokes in the same channel
An example if cooldown is set to 5 seconds
user sends macro
2 seconds pass
user sends same macro in the same channel
bot doesn't respond but instead adds some kind of clock/alarm clock emote to the invoke

closed by #3


adding optional hostname parameter for micro app in tests

Codecov Report

Merging #229 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #229      +/-   ##
==========================================
- Coverage   62.75%   62.68%   -0.07%
==========================================
  Files          40       40
  Lines        3058     3058
  Branches      364      364
==========================================
- Hits         1919     1917       -2
- Misses       1047     1049       +2
  Partials       92       92

Impacted Files
Coverage Δ

core/utils/network_utils.py
55.78% <0%> (-2.11%)
: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 e6dc17d...1d28434. Read the comment docs.

!test


Show (incoming) call hierarchy does not show call inside lambda

Reproducible on the following code:
struct C {
  int func() const;
};

void f(C &c) {
  [&c]() -> void { auto a = c.func(); };
}

When doing find references on C::func(), it nicely shows the caller in the lambda.
When doing a show call hierarchy, it does not show that caller.
If you remove the auto a =  from the code, it does show in the call hierarchy.
Logs
I[15:41:19.652] clangd version 18.1.3 (https://github.com/llvm/llvm-project c13b7485b87909fcf739f62cfa382b55407433c0)
I[15:41:19.653] Features: windows+grpc
I[15:41:19.653] PID: 22392
I[15:41:19.653] Working directory: e:\checkout
I[15:41:19.653] argv[0]: e:\clangd.exe
I[15:41:19.653] argv[1]: --log=verbose
I[15:41:19.653] argv[2]: --enable-config
I[15:41:19.653] argv[3]: --header-insertion=iwyu
I[15:41:19.653] argv[4]: --header-insertion-decorators
I[15:41:19.653] argv[5]: --rename-file-limit=0
I[15:41:19.653] argv[6]: --limit-results=1000
I[15:41:19.653] argv[7]: --pch-storage=disk
I[15:41:19.653] argv[8]: --crash-diagnostics-dir=E:\temp
I[15:41:19.661] Starting LSP over stdin/stdout
V[15:41:19.661] <<< {"id":0,"jsonrpc":"2.0","method":"initialize","params":{"capabilities":{"general":{"markdown":{"parser":"marked","version":"1.1.0"},"positionEncodings":["utf-16"],"regularExpressions":{"engine":"ECMAScript","version":"ES2020"},"staleRequestSupport":{"cancel":true,"retryOnContentModified":["textDocument/semanticTokens/full","textDocument/semanticTokens/range","textDocument/semanticTokens/full/delta"]}},"notebookDocument":{"synchronization":{"dynamicRegistration":true,"executionSummarySupport":true}},"textDocument":{"callHierarchy":{"dynamicRegistration":true},"codeAction":{"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["","quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}},"dataSupport":true,"disabledSupport":true,"dynamicRegistration":true,"honorsChangeAnnotations":false,"isPreferredSupport":true,"resolveSupport":{"properties":["edit"]}},"codeLens":{"dynamicRegistration":true},"colorProvider":{"dynamicRegistration":true},"completion":{"completionItem":{"commitCharactersSupport":true,"deprecatedSupport":true,"documentationFormat":["markdown","plaintext"],"insertReplaceSupport":true,"insertTextModeSupport":{"valueSet":[1,2]},"labelDetailsSupport":true,"preselectSupport":true,"resolveSupport":{"properties":["documentation","detail","additionalTextEdits"]},"snippetSupport":true,"tagSupport":{"valueSet":[1]}},"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25]},"completionList":{"itemDefaults":["commitCharacters","editRange","insertTextFormat","insertTextMode"]},"contextSupport":true,"dynamicRegistration":true,"editsNearCursor":true,"insertTextMode":2},"declaration":{"dynamicRegistration":true,"linkSupport":true},"definition":{"dynamicRegistration":true,"linkSupport":true},"diagnostic":{"dynamicRegistration":true,"relatedDocumentSupport":false},"documentHighlight":{"dynamicRegistration":true},"documentLink":{"dynamicRegistration":true,"tooltipSupport":true},"documentSymbol":{"dynamicRegistration":true,"hierarchicalDocumentSymbolSupport":true,"labelSupport":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]},"tagSupport":{"valueSet":[1]}},"foldingRange":{"dynamicRegistration":true,"foldingRange":{"collapsedText":false},"foldingRangeKind":{"valueSet":["comment","imports","region"]},"lineFoldingOnly":true,"rangeLimit":5000},"formatting":{"dynamicRegistration":true},"hover":{"contentFormat":["markdown","plaintext"],"dynamicRegistration":true},"implementation":{"dynamicRegistration":true,"linkSupport":true},"inactiveRegionsCapabilities":{"inactiveRegions":true},"inlayHint":{"dynamicRegistration":true,"resolveSupport":{"properties":["tooltip","textEdits","label.tooltip","label.location","label.command"]}},"inlineValue":{"dynamicRegistration":true},"linkedEditingRange":{"dynamicRegistration":true},"onTypeFormatting":{"dynamicRegistration":true},"publishDiagnostics":{"codeDescriptionSupport":true,"dataSupport":true,"relatedInformation":true,"tagSupport":{"valueSet":[1,2]},"versionSupport":false},"rangeFormatting":{"dynamicRegistration":true},"references":{"dynamicRegistration":true},"rename":{"dynamicRegistration":true,"honorsChangeAnnotations":true,"prepareSupport":true,"prepareSupportDefaultBehavior":1},"selectionRange":{"dynamicRegistration":true},"semanticTokens":{"augmentsSyntaxTokens":true,"dynamicRegistration":true,"formats":["relative"],"multilineTokenSupport":false,"overlappingTokenSupport":false,"requests":{"full":{"delta":true},"range":true},"serverCancelSupport":true,"tokenModifiers":["declaration","definition","readonly","static","deprecated","abstract","async","modification","documentation","defaultLibrary"],"tokenTypes":["namespace","type","class","enum","interface","struct","typeParameter","parameter","variable","property","enumMember","event","function","method","macro","keyword","modifier","comment","string","number","regexp","operator","decorator"]},"signatureHelp":{"contextSupport":true,"dynamicRegistration":true,"signatureInformation":{"activeParameterSupport":true,"documentationFormat":["markdown","plaintext"],"parameterInformation":{"labelOffsetSupport":true}}},"synchronization":{"didSave":true,"dynamicRegistration":true,"willSave":true,"willSaveWaitUntil":true},"typeDefinition":{"dynamicRegistration":true,"linkSupport":true},"typeHierarchy":{"dynamicRegistration":true}},"window":{"showDocument":{"support":true},"showMessage":{"messageActionItem":{"additionalPropertiesSupport":true}},"workDoneProgress":true},"workspace":{"applyEdit":true,"codeLens":{"refreshSupport":true},"configuration":true,"diagnostics":{"refreshSupport":true},"didChangeConfiguration":{"dynamicRegistration":true},"didChangeWatchedFiles":{"dynamicRegistration":true,"relativePatternSupport":true},"executeCommand":{"dynamicRegistration":true},"fileOperations":{"didCreate":true,"didDelete":true,"didRename":true,"dynamicRegistration":true,"willCreate":true,"willDelete":true,"willRename":true},"inlayHint":{"refreshSupport":true},"inlineValue":{"refreshSupport":true},"semanticTokens":{"refreshSupport":true},"symbol":{"dynamicRegistration":true,"resolveSupport":{"properties":["location.range"]},"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]},"tagSupport":{"valueSet":[1]}},"workspaceEdit":{"changeAnnotationSupport":{"groupsOnLabel":true},"documentChanges":true,"failureHandling":"textOnlyTransactional","normalizesLineEndings":true,"resourceOperations":["create","rename","delete"]},"workspaceFolders":true}},"clientInfo":{"name":"Visual Studio Code","version":"1.96.0"},"initializationOptions":{"clangdFileStatus":true,"fallbackFlags":[]},"locale":"en-us","processId":20064,"rootPath":"e:\\checkout","rootUri":"file:///e%3A/checkout","trace":"off","workspaceFolders":[{"name":"checkout","uri":"file:///e%3A/checkout"}]}}

I[15:41:19.661] <-- initialize(0)
I[15:41:19.782] --> reply:initialize(0) 120 ms
V[15:41:19.782] >>> {"id":0,"jsonrpc":"2.0","result":{"capabilities":{"astProvider":true,"callHierarchyProvider":true,"clangdInlayHintsProvider":true,"codeActionProvider":{"codeActionKinds":["quickfix","refactor","info"]},"compilationDatabase":{"automaticReload":true},"completionProvider":{"resolveProvider":false,"triggerCharacters":[".","<",">",":","\"","/","*"]},"declarationProvider":true,"definitionProvider":true,"documentFormattingProvider":true,"documentHighlightProvider":true,"documentLinkProvider":{"resolveProvider":false},"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"\n","moreTriggerCharacter":[]},"documentRangeFormattingProvider":true,"documentSymbolProvider":true,"executeCommandProvider":{"commands":["clangd.applyFix","clangd.applyTweak"]},"foldingRangeProvider":true,"hoverProvider":true,"implementationProvider":true,"inactiveRegionsProvider":true,"inlayHintProvider":true,"memoryUsageProvider":true,"referencesProvider":true,"renameProvider":{"prepareProvider":true},"selectionRangeProvider":true,"semanticTokensProvider":{"full":{"delta":true},"legend":{"tokenModifiers":["declaration","definition","deprecated","deduced","readonly","static","abstract","virtual","dependentName","defaultLibrary","usedAsMutableReference","usedAsMutablePointer","constructorOrDestructor","userDefined","functionScope","classScope","fileScope","globalScope"],"tokenTypes":["variable","variable","parameter","function","method","function","property","variable","class","interface","enum","enumMember","type","type","unknown","namespace","typeParameter","concept","type","macro","modifier","operator","bracket","label","comment"]},"range":false},"signatureHelpProvider":{"triggerCharacters":["(",")","{","}","<",">",","]},"standardTypeHierarchyProvider":true,"textDocumentSync":{"change":2,"openClose":true,"save":true},"typeDefinitionProvider":true,"typeHierarchyProvider":true,"workspaceSymbolProvider":true},"serverInfo":{"name":"clangd","version":"clangd version 18.1.3 (https://github.com/llvm/llvm-project c13b7485b87909fcf739f62cfa382b55407433c0) windows+grpc x86_64-pc-windows-msvc"}}}

V[15:41:19.785] <<< {"jsonrpc":"2.0","method":"initialized","params":{}}

I[15:41:19.785] <-- initialized
V[15:41:19.797] <<< {"jsonrpc":"2.0","method":"textDocument/didOpen","params":{"textDocument":{"languageId":"cpp","text":"struct C {\n  int func() const;\n};\n\nvoid f(C &c) {\n  [&c]() -> void { auto a = c.func(); };\n}\n","uri":"file:///e%3A/checkout/test.cpp","version":1}}}

I[15:41:19.797] <-- textDocument/didOpen
I[15:41:19.800] Failed to find compilation database for e:\checkout\test.cpp
I[15:41:19.800] ASTWorker building file e:\checkout\test.cpp version 1 with command clangd fallback
[e:\checkout]
"C:\\Program Files\\LLVM\\clang" "-resource-dir=E:\\lib\\clang\\18" -- "e:\\checkout\\test.cpp"
V[15:41:19.822] <<< {"id":1,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":27,"line":5},"start":{"character":19,"line":5}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:19.823] <-- textDocument/codeAction(1)
V[15:41:19.824] Driver produced command: cc1 -cc1 -triple x86_64-pc-windows-msvc19.38.33134 -fsyntax-only ... -x c++ "e:\\checkout\\test.cpp"
I[15:41:19.825] --> textDocument/clangd.fileStatus
V[15:41:19.825] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"parsing includes, running Update","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:19.825] Building first preamble for e:\checkout\test.cpp version 1
V[15:41:19.845] <<< {"jsonrpc":"2.0","method":"$/setTrace","params":{"value":"off"}}

I[15:41:19.845] <-- $/setTrace
I[15:41:19.845] unhandled notification $/setTrace
V[15:41:19.846] <<< {"id":2,"jsonrpc":"2.0","method":"textDocument/documentLink","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:19.846] <-- textDocument/documentLink(2)
I[15:41:19.846] Built preamble of size 235100 for file e:\checkout\test.cpp version 1 in 0.02 seconds
V[15:41:19.847] <<< {"id":3,"jsonrpc":"2.0","method":"textDocument/inlayHint","params":{"range":{"end":{"character":0,"line":7},"start":{"character":0,"line":0}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:19.847] <-- textDocument/inlayHint(3)
I[15:41:19.847] --> workspace/semanticTokens/refresh(0)
V[15:41:19.847] >>> {"id":0,"jsonrpc":"2.0","method":"workspace/semanticTokens/refresh","params":null}

V[15:41:19.848] indexed preamble AST for e:\checkout\test.cpp version 1:
  symbol slab: 0 symbols, 128 bytes
  ref slab: 0 symbols, 0 refs, 136 bytes
  relations slab: 0 relations, 24 bytes
V[15:41:19.850] <<< {"id":0,"jsonrpc":"2.0","result":null}

I[15:41:19.850] <-- reply(0)
V[15:41:19.851] <<< {"id":4,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:19.851] <-- textDocument/semanticTokens/full(4)
I[15:41:19.855] Indexing c++14 standard library in the context of e:\checkout\test.cpp
V[15:41:19.883] <<< {"jsonrpc":"2.0","method":"$/cancelRequest","params":{"id":1}}

I[15:41:19.883] <-- $/cancelRequest
V[15:41:19.883] <<< {"id":5,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":27,"line":5},"start":{"character":19,"line":5}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:19.883] <-- textDocument/codeAction(5)
V[15:41:19.884] <<< {"jsonrpc":"2.0","method":"$/cancelRequest","params":{"id":5}}

I[15:41:19.884] <-- $/cancelRequest
V[15:41:19.885] <<< {"id":6,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":27,"line":5},"start":{"character":19,"line":5}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:19.885] <-- textDocument/codeAction(6)
V[15:41:19.909] indexed file AST for e:\checkout\test.cpp version 1:
  symbol slab: 3 symbols, 4920 bytes
  ref slab: 3 symbols, 5 refs, 4304 bytes
  relations slab: 0 relations, 24 bytes
V[15:41:19.909] Build dynamic index for main-file symbols with estimated memory usage of 12640 bytes
I[15:41:19.909] --> textDocument/publishDiagnostics
V[15:41:19.909] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[{"code":"-Wunused-value","message":"Expression result unused","range":{"end":{"character":39,"line":5},"start":{"character":2,"line":5}},"relatedInformation":[],"severity":2,"source":"clang"}],"uri":"file:///e:/checkout/test.cpp","version":1}}

I[15:41:19.909] --> textDocument/inactiveRegions
V[15:41:19.909] >>> {"jsonrpc":"2.0","method":"textDocument/inactiveRegions","params":{"regions":[],"textDocument":{"uri":"file:///e:/checkout/test.cpp"}}}

I[15:41:19.910] --> reply:textDocument/codeAction(1) 87 ms, error: Task was cancelled.
V[15:41:19.910] >>> {"error":{"code":-32800,"message":"Request cancelled"},"id":1,"jsonrpc":"2.0"}

V[15:41:19.910] ASTWorker running DocumentLinks on version 1 of e:\checkout\test.cpp
I[15:41:19.910] --> reply:textDocument/documentLink(2) 64 ms
V[15:41:19.910] >>> {"id":2,"jsonrpc":"2.0","result":[]}

V[15:41:19.910] ASTWorker running InlayHints on version 1 of e:\checkout\test.cpp
I[15:41:19.910] --> reply:textDocument/inlayHint(3) 63 ms
V[15:41:19.910] >>> {"id":3,"jsonrpc":"2.0","result":[{"kind":1,"label":": int","paddingLeft":false,"paddingRight":false,"position":{"character":25,"line":5}}]}

V[15:41:19.910] ASTWorker running SemanticHighlights on version 1 of e:\checkout\test.cpp
I[15:41:19.910] --> reply:textDocument/semanticTokens/full(4) 58 ms
V[15:41:19.910] >>> {"id":4,"jsonrpc":"2.0","result":{"data":[0,7,1,8,131075,1,6,4,4,32785,3,5,1,3,131075,0,2,1,8,131072,0,3,1,2,16387,1,4,1,2,16384,0,15,4,18,131592,0,5,1,1,16387,0,4,1,2,16384,0,2,4,4,32784],"resultId":"1"}}

I[15:41:19.910] --> reply:textDocument/codeAction(5) 26 ms, error: Task was cancelled.
V[15:41:19.910] >>> {"error":{"code":-32800,"message":"Request cancelled"},"id":5,"jsonrpc":"2.0"}

V[15:41:19.910] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:19.910] --> reply:textDocument/codeAction(6) 25 ms
V[15:41:19.910] >>> {"id":6,"jsonrpc":"2.0","result":[]}

I[15:41:19.910] --> textDocument/clangd.fileStatus
V[15:41:19.910] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

[Error - 3:41:20 PM] Request textDocument/codeAction failed.
[object Object]
V[15:41:20.121] <<< {"id":7,"jsonrpc":"2.0","method":"textDocument/foldingRange","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:20.121] <-- textDocument/foldingRange(7)
[Error - 3:41:20 PM] Request textDocument/codeAction failed.
[object Object]
I[15:41:20.131] --> reply:textDocument/foldingRange(7) 9 ms
V[15:41:20.131] >>> {"id":7,"jsonrpc":"2.0","result":[{"endLine":1,"kind":"region","startCharacter":10,"startLine":0},{"endLine":5,"kind":"region","startCharacter":14,"startLine":4}]}

V[15:41:20.622] <<< {"id":8,"jsonrpc":"2.0","method":"textDocument/documentHighlight","params":{"position":{"character":8,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:20.622] <-- textDocument/documentHighlight(8)
V[15:41:20.623] ASTWorker running Highlights on version 1 of e:\checkout\test.cpp
I[15:41:20.623] --> reply:textDocument/documentHighlight(8) 1 ms
V[15:41:20.623] >>> {"id":8,"jsonrpc":"2.0","result":[{"kind":1,"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}},{"kind":1,"range":{"end":{"character":34,"line":5},"start":{"character":30,"line":5}}}]}

I[15:41:20.623] --> textDocument/clangd.fileStatus
V[15:41:20.623] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:20.624] <<< {"id":9,"jsonrpc":"2.0","method":"textDocument/documentSymbol","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:20.624] <-- textDocument/documentSymbol(9)
V[15:41:20.625] ASTWorker running DocumentSymbols on version 1 of e:\checkout\test.cpp
I[15:41:20.625] --> reply:textDocument/documentSymbol(9) 0 ms
V[15:41:20.625] >>> {"id":9,"jsonrpc":"2.0","result":[{"children":[{"detail":"int () const","kind":6,"name":"func","range":{"end":{"character":18,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}}],"detail":"struct","kind":23,"name":"C","range":{"end":{"character":1,"line":2},"start":{"character":0,"line":0}},"selectionRange":{"end":{"character":8,"line":0},"start":{"character":7,"line":0}}},{"detail":"void (C &)","kind":12,"name":"f","range":{"end":{"character":1,"line":6},"start":{"character":0,"line":4}},"selectionRange":{"end":{"character":6,"line":4},"start":{"character":5,"line":4}}}]}

I[15:41:20.625] --> textDocument/clangd.fileStatus
V[15:41:20.625] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:20.626] <<< {"jsonrpc":"2.0","method":"$/setTrace","params":{"value":"off"}}

I[15:41:20.626] <-- $/setTrace
I[15:41:20.626] unhandled notification $/setTrace
V[15:41:20.628] <<< {"id":10,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":8,"line":1},"start":{"character":8,"line":1}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:20.628] <-- textDocument/codeAction(10)
V[15:41:20.628] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:20.628] --> reply:textDocument/codeAction(10) 0 ms
V[15:41:20.628] >>> {"id":10,"jsonrpc":"2.0","result":[]}

I[15:41:20.628] --> textDocument/clangd.fileStatus
V[15:41:20.628] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:20.629] <<< {"jsonrpc":"2.0","method":"$/setTrace","params":{"value":"off"}}

I[15:41:20.629] <-- $/setTrace
I[15:41:20.629] unhandled notification $/setTrace
V[15:41:20.906] <<< {"jsonrpc":"2.0","method":"$/setTrace","params":{"value":"off"}}

I[15:41:20.906] <-- $/setTrace
I[15:41:20.906] unhandled notification $/setTrace
V[15:41:21.045] <<< {"id":11,"jsonrpc":"2.0","method":"textDocument/documentSymbol","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:21.045] <-- textDocument/documentSymbol(11)
V[15:41:21.045] ASTWorker running DocumentSymbols on version 1 of e:\checkout\test.cpp
I[15:41:21.045] --> reply:textDocument/documentSymbol(11) 0 ms
V[15:41:21.045] >>> {"id":11,"jsonrpc":"2.0","result":[{"children":[{"detail":"int () const","kind":6,"name":"func","range":{"end":{"character":18,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}}],"detail":"struct","kind":23,"name":"C","range":{"end":{"character":1,"line":2},"start":{"character":0,"line":0}},"selectionRange":{"end":{"character":8,"line":0},"start":{"character":7,"line":0}}},{"detail":"void (C &)","kind":12,"name":"f","range":{"end":{"character":1,"line":6},"start":{"character":0,"line":4}},"selectionRange":{"end":{"character":6,"line":4},"start":{"character":5,"line":4}}}]}

I[15:41:21.045] --> textDocument/clangd.fileStatus
V[15:41:21.045] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:21.149] <<< {"id":12,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":8,"line":1},"start":{"character":8,"line":1}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:21.150] <-- textDocument/codeAction(12)
V[15:41:21.150] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:21.150] --> reply:textDocument/codeAction(12) 0 ms
V[15:41:21.150] >>> {"id":12,"jsonrpc":"2.0","result":[]}

I[15:41:21.150] --> textDocument/clangd.fileStatus
V[15:41:21.150] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:21.608] <<< {"id":13,"jsonrpc":"2.0","method":"textDocument/documentLink","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:21.608] <-- textDocument/documentLink(13)
V[15:41:21.608] ASTWorker running DocumentLinks on version 1 of e:\checkout\test.cpp
I[15:41:21.608] --> reply:textDocument/documentLink(13) 0 ms
V[15:41:21.608] >>> {"id":13,"jsonrpc":"2.0","result":[]}

I[15:41:21.608] --> textDocument/clangd.fileStatus
V[15:41:21.608] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.054] <<< {"id":14,"jsonrpc":"2.0","method":"textDocument/documentLink","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.054] <-- textDocument/documentLink(14)
V[15:41:22.054] ASTWorker running DocumentLinks on version 1 of e:\checkout\test.cpp
I[15:41:22.054] --> reply:textDocument/documentLink(14) 0 ms
V[15:41:22.054] >>> {"id":14,"jsonrpc":"2.0","result":[]}

I[15:41:22.054] --> textDocument/clangd.fileStatus
V[15:41:22.054] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.200] <<< {"id":15,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":8,"line":1},"start":{"character":8,"line":1}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.200] <-- textDocument/codeAction(15)
V[15:41:22.200] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:22.200] --> reply:textDocument/codeAction(15) 0 ms
V[15:41:22.200] >>> {"id":15,"jsonrpc":"2.0","result":[]}

I[15:41:22.201] --> textDocument/clangd.fileStatus
V[15:41:22.201] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.209] <<< {"jsonrpc":"2.0","method":"$/cancelRequest","params":{"id":15}}

I[15:41:22.209] <-- $/cancelRequest
V[15:41:22.249] <<< {"id":16,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":8,"line":1},"start":{"character":8,"line":1}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.249] <-- textDocument/codeAction(16)
V[15:41:22.249] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:22.249] --> reply:textDocument/codeAction(16) 0 ms
V[15:41:22.249] >>> {"id":16,"jsonrpc":"2.0","result":[]}

I[15:41:22.249] --> textDocument/clangd.fileStatus
V[15:41:22.249] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.302] <<< {"id":17,"jsonrpc":"2.0","method":"textDocument/documentSymbol","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.302] <-- textDocument/documentSymbol(17)
V[15:41:22.302] ASTWorker running DocumentSymbols on version 1 of e:\checkout\test.cpp
I[15:41:22.302] --> reply:textDocument/documentSymbol(17) 0 ms
V[15:41:22.302] >>> {"id":17,"jsonrpc":"2.0","result":[{"children":[{"detail":"int () const","kind":6,"name":"func","range":{"end":{"character":18,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}}],"detail":"struct","kind":23,"name":"C","range":{"end":{"character":1,"line":2},"start":{"character":0,"line":0}},"selectionRange":{"end":{"character":8,"line":0},"start":{"character":7,"line":0}}},{"detail":"void (C &)","kind":12,"name":"f","range":{"end":{"character":1,"line":6},"start":{"character":0,"line":4}},"selectionRange":{"end":{"character":6,"line":4},"start":{"character":5,"line":4}}}]}

I[15:41:22.302] --> textDocument/clangd.fileStatus
V[15:41:22.302] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.422] <<< {"id":18,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":8,"line":1},"start":{"character":8,"line":1}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.422] <-- textDocument/codeAction(18)
V[15:41:22.422] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:22.422] --> reply:textDocument/codeAction(18) 0 ms
V[15:41:22.422] >>> {"id":18,"jsonrpc":"2.0","result":[]}

I[15:41:22.422] --> textDocument/clangd.fileStatus
V[15:41:22.422] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.425] <<< {"id":19,"jsonrpc":"2.0","method":"textDocument/documentLink","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.425] <-- textDocument/documentLink(19)
V[15:41:22.425] ASTWorker running DocumentLinks on version 1 of e:\checkout\test.cpp
I[15:41:22.425] --> reply:textDocument/documentLink(19) 0 ms
V[15:41:22.425] >>> {"id":19,"jsonrpc":"2.0","result":[]}

I[15:41:22.425] --> textDocument/clangd.fileStatus
V[15:41:22.425] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

I[15:41:22.612] Indexed c++14 standard library (incomplete due to errors): 19266 symbols, 503 filtered
V[15:41:22.621] <<< {"id":20,"jsonrpc":"2.0","method":"textDocument/foldingRange","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.621] <-- textDocument/foldingRange(20)
I[15:41:22.622] --> reply:textDocument/foldingRange(20) 1 ms
V[15:41:22.622] >>> {"id":20,"jsonrpc":"2.0","result":[{"endLine":1,"kind":"region","startCharacter":10,"startLine":0},{"endLine":5,"kind":"region","startCharacter":14,"startLine":4}]}

V[15:41:22.707] <<< {"id":21,"jsonrpc":"2.0","method":"textDocument/documentSymbol","params":{"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:22.707] <-- textDocument/documentSymbol(21)
V[15:41:22.707] ASTWorker running DocumentSymbols on version 1 of e:\checkout\test.cpp
I[15:41:22.707] --> reply:textDocument/documentSymbol(21) 0 ms
V[15:41:22.707] >>> {"id":21,"jsonrpc":"2.0","result":[{"children":[{"detail":"int () const","kind":6,"name":"func","range":{"end":{"character":18,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}}],"detail":"struct","kind":23,"name":"C","range":{"end":{"character":1,"line":2},"start":{"character":0,"line":0}},"selectionRange":{"end":{"character":8,"line":0},"start":{"character":7,"line":0}}},{"detail":"void (C &)","kind":12,"name":"f","range":{"end":{"character":1,"line":6},"start":{"character":0,"line":4}},"selectionRange":{"end":{"character":6,"line":4},"start":{"character":5,"line":4}}}]}

I[15:41:22.707] --> textDocument/clangd.fileStatus
V[15:41:22.707] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:22.751] Build dynamic index for header symbols with estimated memory usage of 11650960 bytes
V[15:41:24.527] <<< {"id":22,"jsonrpc":"2.0","method":"textDocument/documentHighlight","params":{"position":{"character":8,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:24.527] <-- textDocument/documentHighlight(22)
V[15:41:24.527] ASTWorker running Highlights on version 1 of e:\checkout\test.cpp
I[15:41:24.527] --> reply:textDocument/documentHighlight(22) 0 ms
V[15:41:24.527] >>> {"id":22,"jsonrpc":"2.0","result":[{"kind":1,"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}},{"kind":1,"range":{"end":{"character":34,"line":5},"start":{"character":30,"line":5}}}]}

I[15:41:24.527] --> textDocument/clangd.fileStatus
V[15:41:24.527] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:28.958] <<< {"id":23,"jsonrpc":"2.0","method":"textDocument/references","params":{"context":{"includeDeclaration":true},"position":{"character":8,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:28.958] <-- textDocument/references(23)
V[15:41:28.959] <<< {"id":24,"jsonrpc":"2.0","method":"textDocument/documentHighlight","params":{"position":{"character":8,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:28.959] <-- textDocument/documentHighlight(24)
V[15:41:28.959] ASTWorker running References on version 1 of e:\checkout\test.cpp
I[15:41:28.959] --> reply:textDocument/references(23) 1 ms
V[15:41:28.959] >>> {"id":23,"jsonrpc":"2.0","result":[{"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}},"uri":"file:///e:/checkout/test.cpp"},{"range":{"end":{"character":34,"line":5},"start":{"character":30,"line":5}},"uri":"file:///e:/checkout/test.cpp"}]}

V[15:41:28.959] ASTWorker running Highlights on version 1 of e:\checkout\test.cpp
I[15:41:28.959] --> reply:textDocument/documentHighlight(24) 0 ms
V[15:41:28.959] >>> {"id":24,"jsonrpc":"2.0","result":[{"kind":1,"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}},{"kind":1,"range":{"end":{"character":34,"line":5},"start":{"character":30,"line":5}}}]}

I[15:41:28.959] --> textDocument/clangd.fileStatus
V[15:41:28.959] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:30.698] <<< {"id":25,"jsonrpc":"2.0","method":"textDocument/hover","params":{"position":{"character":9,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:30.698] <-- textDocument/hover(25)
V[15:41:30.698] ASTWorker running Hover on version 1 of e:\checkout\test.cpp
I[15:41:30.700] --> reply:textDocument/hover(25) 1 ms
V[15:41:30.700] >>> {"id":25,"jsonrpc":"2.0","result":{"contents":{"kind":"markdown","value":"### instance-method `func`  \n\n---\n→ `int`  \n\n---\n```cpp\n// In C\npublic: int func() const\n```"},"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}}}

I[15:41:30.700] --> textDocument/clangd.fileStatus
V[15:41:30.700] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:31.494] <<< {"id":26,"jsonrpc":"2.0","method":"textDocument/hover","params":{"position":{"character":6,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:31.494] <-- textDocument/hover(26)
V[15:41:31.494] ASTWorker running Hover on version 1 of e:\checkout\test.cpp
I[15:41:31.496] --> reply:textDocument/hover(26) 1 ms
V[15:41:31.496] >>> {"id":26,"jsonrpc":"2.0","result":{"contents":{"kind":"markdown","value":"### instance-method `func`  \n\n---\n→ `int`  \n\n---\n```cpp\n// In C\npublic: int func() const\n```"},"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}}}

I[15:41:31.496] --> textDocument/clangd.fileStatus
V[15:41:31.496] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:32.929] <<< {"id":27,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[],"triggerKind":2},"range":{"end":{"character":7,"line":1},"start":{"character":7,"line":1}},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:32.929] <-- textDocument/codeAction(27)
V[15:41:32.929] ASTWorker running codeAction on version 1 of e:\checkout\test.cpp
I[15:41:32.929] --> reply:textDocument/codeAction(27) 0 ms
V[15:41:32.929] >>> {"id":27,"jsonrpc":"2.0","result":[]}

I[15:41:32.929] --> textDocument/clangd.fileStatus
V[15:41:32.929] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:34.637] <<< {"id":28,"jsonrpc":"2.0","method":"textDocument/prepareCallHierarchy","params":{"position":{"character":7,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:34.637] <-- textDocument/prepareCallHierarchy(28)
V[15:41:34.645] ASTWorker running CallHierarchy on version 1 of e:\checkout\test.cpp
I[15:41:34.645] --> reply:textDocument/prepareCallHierarchy(28) 8 ms
V[15:41:34.645] >>> {"id":28,"jsonrpc":"2.0","result":[{"data":"197EBC1474C766FA","kind":6,"name":"func","range":{"end":{"character":18,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}},"uri":"file:///e:/checkout/test.cpp"}]}

I[15:41:34.645] --> textDocument/clangd.fileStatus
V[15:41:34.645] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:34.656] <<< {"id":29,"jsonrpc":"2.0","method":"textDocument/documentHighlight","params":{"position":{"character":8,"line":1},"textDocument":{"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:34.656] <-- textDocument/documentHighlight(29)
V[15:41:34.665] ASTWorker running Highlights on version 1 of e:\checkout\test.cpp
I[15:41:34.665] --> reply:textDocument/documentHighlight(29) 8 ms
V[15:41:34.665] >>> {"id":29,"jsonrpc":"2.0","result":[{"kind":1,"range":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}}},{"kind":1,"range":{"end":{"character":34,"line":5},"start":{"character":30,"line":5}}}]}

I[15:41:34.665] --> textDocument/clangd.fileStatus
V[15:41:34.665] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///e:/checkout/test.cpp"}}

V[15:41:34.865] <<< {"id":30,"jsonrpc":"2.0","method":"callHierarchy/incomingCalls","params":{"item":{"data":"197EBC1474C766FA","kind":6,"name":"func","range":{"end":{"character":18,"line":1},"start":{"character":2,"line":1}},"selectionRange":{"end":{"character":10,"line":1},"start":{"character":6,"line":1}},"uri":"file:///e%3A/checkout/test.cpp"}}}

I[15:41:34.865] <-- callHierarchy/incomingCalls(30)
I[15:41:34.866] --> reply:callHierarchy/incomingCalls(30) 0 ms
V[15:41:34.866] >>> {"id":30,"jsonrpc":"2.0","result":[]}

System information
Output of clangd --version:
clangd version 18.1.3 (https://github.com/llvm/llvm-project c13b7485b87909fcf739f62cfa382b55407433c0)
Features: windows+grpc
Platform: x86_64-pc-windows-msvc

Editor/LSP plugin: 0.1.33
Operating system: Windows

From what I was able to debug myself, the issue seems to be linked to the symbols used in the Ref. It seems to create a ref to the function from the lambda, though that symbol is not added in Symbols. As such, the lookup of the symbol fails and the entry is ignored.


Get-DbaDatabaseGrowth

Is this a feature OR bug:
https://trello.com/c/pUAVChjK
Additional comments
Refs: http://www.sqlskills.com/blogs/erin/trending-database-growth-from-backups/
With a-Chart that does something like: https://blogs.technet.microsoft.com/richard_macdonald/2009/04/28/charting-with-powershell/
Notes column to warn if there's not enough info to determine long term growht. Support for -Since with either a timespan or like Week, Month, Year. By default use all data.
Add support for -Databases dynamic param to allow for one, many or all.

Done!


Error while compiling the source

I followed the steps mentioned in this link
https://github.com/grpc/grpc/blob/master/INSTALL.md
when i compile the  source using make i keep getting an error ,i have attached a screenshot
plz help me with this

Which OS and compiler are you using?
On Thu, Jun 30, 2016, 5:46 AM haripraveenrajt<EMAIL_ADDRESS>wrote:

[image: screenshot from 2016-06-30 13 40 38]
https://cloud.githubusercontent.com/assets/19606745/16488430/67ad59de-3ec8-11e6-9553-e5184798b2f1.png
I followed the steps mentioned in this link
https://github.com/grpc/grpc/blob/master/INSTALL.md
when i compile the source using make i keep getting an error ,i have
attached a screenshot
plz help me with this
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/issues/7168, or mute the thread
https://github.com/notifications/unsubscribe/AJpudTZS-Va4S-1rj-3gV71OMox-N8udks5qQ7qWgaJpZM4JCHsg
.

Im using Ubuntu 12.04 64 bit os and GCC

Which version of GCC?

gcc version - 4.6.3


Text fields are blurred on dialog resize

Here's a gif showing what happens: http://i.imgur.com/rlMkjzr.gifv
This is mostly an issue when opening dialogs on cell phones, and trying to type stuff into textfields.
If you do that the on screen keyboard pops up, resizing the window and blurring the textfield, which closes the keyboard immediately.

I'm having this exact same issue.

Thanks for reporting the issue. I'm going to take a look!

Hi, it's now fixed in the last version of LumX :-)


extra "[ ]" for server configuration in calico-kubeconfig

The calico-node failed to start and I found the server with extra [ ] in /etc/cni/net.d/calico-kubeconfig, tried to remove [ ] manually, but  the file /etc/cni/net.d/calico-kubeconfig was recreated when the calico-node pod was restarted. is this a bug or something to do with the environment?
cat /etc/cni/net.d/calico-kubeconfig
Kubeconfig file for Calico CNI plugin.
apiVersion: v1
kind: Config
clusters:

name: local
cluster:
server: https://[<IP_ADDRESS>]:443

Expected Behavior

calio-node pod up running
Current Behavior

The calico-node failed to start and I found the server with extra [ ] in /etc/cni/net.d/calico-kubeconfig, tried to remove [ ] manually, but  the file /etc/cni/net.d/calico-kubeconfig was recreated when the calico-node pod was restarted. is this a bug or something to do with the environment?
cat /etc/cni/net.d/calico-kubeconfig
Kubeconfig file for Calico CNI plugin.
apiVersion: v1
kind: Config
clusters:

name: local
cluster:
server: https://[<IP_ADDRESS>]:443

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Calico version v3.24.5

Orchestrator version (e.g. kubernetes, mesos, rkt): kubespray2.21.0

Operating System and version: ubuntu22.04
Link to your project (optional):

Hi @onap4105, can you please share how did you install Calico on your cluster? Have you enabled ipv6 in your cluster by any chance and using ipv4? Also If possible could you please try installing newer version of Calico, and see if the issue persist?

server: https://[<IP_ADDRESS>]:443

This is fine and expected.

The calico-node failed to start and I found the server with extra [ ] in /etc/cni/net.d/calico-kubeconfig

These are unrelated, most likely. calico/node doesn't ever look at /etc/cni/net.d/calico-kubeconfig.
What is the error you're seeing?

@onap4105 Can you please update the error?


libarchive: Upgrade to 3.7.7 to fix CVE-2024-48957, CVE-2024-48958, CVE-2024-20696

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[X] The toolchain has been rebuilt successfully (or no changes were made to it)
[X] The toolchain/worker package manifests are up-to-date
[X] Any updated packages successfully build (or no packages were changed)
[X] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[X] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[X] All package sources are available
[X] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[X] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[X] All source files have up-to-date hashes in the *.signatures.json files
[X] sudo make go-tidy-all and sudo make go-test-coverage pass
[X] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Upgrade to 3.7.7 to fix CVE-2024-48957, CVE-2024-48958, CVE-2024-20696
Change Log

Upgrade to 3.7.7 - Fix CVE-2024-48957, CVE-2024-48958, CVE-2024-20696
Remove unused patches

Does this affect the toolchain?

YES
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2024-48957
https://nvd.nist.gov/vuln/detail/CVE-2024-48958
https://nvd.nist.gov/vuln/detail/CVE-2024-20696

Test Methodology

Pipeline build id: 658792

Auto cherry-pick results:

3.0-dev :white_check_mark: -> https://github.com/microsoft/azurelinux/pull/10773

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=659338&view=results


View granted permissions

Pull Request Details
What issue does this PR address

View permissions granted from other PODs

Link to associated issue: https://github.com/anusii/solidpod/issues/199

Checklist
Complete the check-list below to ensure your branch is ready for PR.
Flutter Style Guide: https://survivor.togaware.com/gnulinux/flutter-style.html

[x] Screenshots included in linked issue
[x] Changes adhere to the team style and coding guideline
[x] No confidential information
[x] No duplicated content
[x] No lint check errors related to your changes (make prep or flutter analyze lib)
[x] Pre-exisiting lint errors noted: [HERE]
[x] Tested on at least one device

[ ] Android Phone
[ ] Android Emulator
[ ] Chrome on Android
[ ] Chrome
[ ] iOS
[ ] Linux
[ ] MacOS
[x] Windows

[ ] Added 2 reviewers (or 1 for private repositories then they add another)

Finalising
Once PR discussion is complete and 2 reviewers have approved:

[ ] Merge dev into the branch
[ ] Resolve any conflicts
[ ] Add one line summary into CHANGELOG.md
[ ] Bump appropriate version number in pubspec.yaml
[ ] Push to git repository and review
[ ] Merge PR into dev

Thanks Dawei. Fixed those now


Migrate ECS AWSX guide to multi-lang

Oustanding tasks:

[ ] Add Go
[ ] Remove props listings and just link to the registry (assuming this will exist)
[x] Make the service-less tasks section clearer and probably shorter
[ ] Docker ECR image integration rework
[ ] Maybe add a section on EC2?
[ ] Remove or rework the fire-and-forget example ... this relies heavily on callback magic that's not multi-lang. Perhaps just add a note about it being classic-only?

This was merged into another branch


Change link to tutorial in README

The tutorial that was previously linked to doesn't show up in the sidebar of typescriptlang.org/docs/ anymore.
The "TypeScript in 5 minutes" tutorial is essentially the same tutorial, but does show up in the sidebar and the docs overview.
By linking to this, the user that clicks through knows where they end up on the docs page, instead of being lost on the "Quick Tutorial" that they can't find again, except through this README.

Fixes #

Agree - thanks @mrnugget  <3


Don't run stale/danger/labeller on forks

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against b1739c94a8e0cb2c9176beefdad9b2d9cfc0c66b


m-article-card__timestamp changes needed

Hi,
Please kindly give a path where the m-article-card__timestamp class can be found?
Want to hide x hour to post and x min. read section
Please assist on this,
Many Thanks

Hi,
if you want to hide that element you can inject the following styles in your Ghost Admin (Code injection -> Site Header)
<style>
.m-article-card__timestamp {
  display: none;
}
</style>

Hi,
if you want to hide that element you can inject the following styles in your Ghost Admin (Code injection -> Site Header)
<style>
.m-article-card__timestamp {
  display: none;
}
</style>

I'm closing this issue now, please feel free to reopen it if needed.

I'm closing this issue now, please feel free to reopen it if needed.


Create azure pipelines windows x64 continuous code analysis

continuous code analysis build is slow, but enables a huge TODO list with evident opportunities for new contributors.

Hi Robert! Thanks for this PR - I just looked more closely and noticed it is using our old Cmake setup, which has recently been completely reworked. That's part of why it's failing.
A few other notes:

templates in share/ci/templates such as build.yml are meant to be common to all jobs across OS, with arguments added as needed to customize from the main azure-pipelines.yml
OS-specific install scripts are in share/ci/scripts and here we are trying to have one script per dependency, e.g. install_cmake, install_python, etc.
the Azure job in azure-pipelines.yml for Windows should be similar to the Linux and Mac jobs - I had intended to use the version that was commented out, just adding necessary install scripts for dependencies.
This structure is similar to other ASWF projects such as OpenColorIO.
Do you want to create a powershell script share/ci/windows/install_zlib.ps1 for installing zlib? Refer to install_cmake.ps1 in same directory. I was planning to use Invoke-Webrequest which uses wget, instead of NuGet. This way if we ever need to test gcc or clang on Windows, we wouldn't need a new script (NuGet is MSVC specific right?). But I'm fine with Nuget for now too.
OpenEXRViewers has moved to a separate repo so we don't need FLTK.
Boost Python is another dependency that needs an install script. I will be working on this in a week (I have no Windows access this weekend) but let me know if you want to write that script. Happy to have the contributions!

OpenEXR_Viewers hasn't moved to another repo, yet. We've talked about it,
as a way of simplifying the build instructions for OpenEXR by eliminating
all reference to Fltk. But for now, it's still there, buildable via a
separate option.
On Fri, Aug 9, 2019 at 2:24 PM Christina Tempelaar-Lietz <
<EMAIL_ADDRESS>wrote:

Hi Robert! Thanks for this PR - I just looked more closely and noticed it
is using our old Cmake setup, which has recently been completely reworked.
That's part of why it's failing.
A few other notes:

templates in share/ci/templates such as build.yml are meant to be
common to all jobs across OS, with arguments added as needed to customize
from the main azure-pipelines.yml
OS-specific install scripts are in share/ci/scripts and here we are
trying to have one script per dependency, e.g. install_cmake,
install_python, etc.
the Azure job in azure-pipelines.yml for Windows should be similar
to the Linux and Mac jobs - I had intended to use the version that was
commented out, just adding necessary install scripts for dependencies.
This structure is similar to other ASWF projects such as OpenColorIO.
Do you want to create a powershell script
share/ci/windows/install_zlib.ps1 for installing zlib? Refer to
install_cmake.ps1 in same directory. I was planning to use
Invoke-Webrequest which uses wget, instead of NuGet. This way if we ever
need to test gcc or clang on Windows, we wouldn't need a new script (NuGet
is MSVC specific right?). But I'm fine with Nuget for now too.
OpenEXRViewers has moved to a separate repo so we don't need FLTK.
Boost Python is another dependency that needs an install script. I
will be working on this in a week (I have no Windows access this weekend)
but let me know if you want to write that script. Happy to have the
contributions!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openexr/openexr/pull/513?email_source=notifications&email_token=AFC3DGORP3WHBV3VB3ZCCHTQDXOA3A5CNFSM4IHN7H62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD37Z2FI#issuecomment-520068373,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFC3DGN3HPXXNDYOO7WVZ7TQDXOA3ANCNFSM4IHN7H6Q
.

--
Cary Phillips | R&D Supervisor | ILM | San Francisco

Thanks for the correction, Cary. The Viewers are excluded from the default build so they aren't being tested by our Linux or Mac CI jobs or the SonarCloud job. So Fltk should not be installed, as you said.
I looked more closely and it appears that the new cmake setup still accepts all the same flags as the old cmake as well. I can no longer see the pipeline log for this PR to check why the job failed. And attempts to re-run it didn't work. I don't think it's critical to determine though since I still would want to restructure the Windows job to be similar to our Mac/Linux jobs and the other ASWF projects.

Cary, please advise if OpenEXR_Viewers should be added to the CI for now though. May have been an oversight on my part.

I don’t think we need to include OpenEXR_Viewers in the CI build. My
understanding of that code is that it’s primarily example code. It’s
binaries, not a library.
It would be good to update the code and replace Fltk with something like
Qt.
On Fri, Aug 9, 2019 at 6:10 PM Christina Tempelaar-Lietz <
<EMAIL_ADDRESS>wrote:

Cary, please advise if OpenEXR_Viewers should be added to the CI for now
though. May have been an oversight on my part.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openexr/openexr/pull/513?email_source=notifications&email_token=AFC3DGNLFSAHZNLISNMT3T3QDYIR5A5CNFSM4IHN7H62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4AC6EY#issuecomment-520105747,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFC3DGOV2FH6T4HIJDK2EILQDYIR5ANCNFSM4IHN7H6Q
.

--
Cary Phillips | R&D Supervisor | ILM | San Francisco

I use this OpenEXR viewer instead of the official one: https://github.com/tizian/tonemapper . It's very lightweight, cross platform, and easy to build without bringing in a dependency as large as Qt. Perhaps it would be a good starting point.
I've created a new issue in order not to hijack this comment thread. https://github.com/openexr/openexr/issues/521

Greetings @xlietz
I appreciate the notes and information here. Nuget reminds me of yum or apt. The binaries that get distributed can be of any toolchain and architecture, but they are public domain.  I have seen students pick up and run with nuget to start exploring the nouns and verbs of a new library without getting stuck at barriers.
Great point about Windows builds with other toolchains, (GCC, CLang). Do we want to consider Intel toolchain also? When time allows, I will start reworking this PR and add the zlib script. Do the other ASWF projects such as OpenColorIO have windows build yaml for examples?
Thanks,
coast

Hi @coast77777777777 - I have a working install-zlib.ps1 script now. So the only script still needed is an install-boost script that installs boost and boost-python, required by PyIlmBase. The scripts are all Windows powershell scripts, in share/ci/scripts/windows/*.ps1.
No need for a Windows-specific yml template. The Windows job is already in azure-pipelines.yml. The Windows job is based on OpenColorIO pipeline. The Windows jobs is commented out currently but will be uncommented once I submit a PR with install-zib. Probably later this week since I am still working out an issue with how the tests run.

Ok sounds great, thanks! I am busy with orientation stuff these two weeks, so I will take a closer look later in August.

On Aug 12, 2019, at 9:28 PM, Christina Tempelaar-Lietz<EMAIL_ADDRESS>wrote:
Hi @coast77777777777 - I have a working install-zlib.ps1 script now. So the only script still needed is an install-boost script that installs boost and boost-python, required by PyIlmBase. The scripts are all Windows powershell scripts, in share/ci/scripts/windows/*.ps1.
No need for a Windows-specific yml template. The Windows job is already in azure-pipelines.yml. The Windows job is based on OpenColorIO pipeline. The Windows jobs is commented out currently but will be uncommented once I submit a PR with install-zib. Probably later this week since I am still working out an issue with how the tests run.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Robert - just a heads up, I'm close to wrapping up a Windows install script for boost and boost-python as we want to get rest of tests running on the Azure pipeline soon. Thanks!

Closing this PR as Azure Windows job is now mostly up and running. Keeping a copy of your script however for future reference. Thanks!

Sounds great thanks! I also appreciate your fully worked example for sonar cloud that I can apply to other systems.

On Sep 5, 2019, at 1:54 PM, Christina Tempelaar-Lietz<EMAIL_ADDRESS>wrote:
Closed #513.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


join_contexts failing on vanderMoezel_1987 in v 4.2.0

the join_contexts function is failing at vanderMoezel_1987 (v4.2.0), because there are two entries for a context that map to the same context property value - and therefore break the function the second place pivot_wider is used:
dataset_id        link_id           link_vals `time to flowering type`
  <chr>             <chr>             <chr>     <chr>
1 vanderMoezel_1987 entity_context_id 01        from seed
2 vanderMoezel_1987 entity_context_id 03        from resprouting
3 vanderMoezel_1987 entity_context_id 04        unknown
4 vanderMoezel_1987 entity_context_id 02        unknown

I've fixed this in the current austraits.build repository, but in the meantime, vanderMoezel_1987 needs to be added flagged as a problem study within the join_contexts function. (Meanwhile Hall_1981 is no longer a problem study in v4.2.0.)
@yangsophieee and I decided today to add tests to traits.build that ensure the austraits functions work as each new dataset is added to ensure these problems stop surfacing after releases!

@yangsophieee just pointed out that recent edits to the traits.build workflow now automatically collapse identical context property values, so this is no longer a problem.

Not supporting 4.2.0 closing after discussion with @ehwenk


Collection of already tried publishers

A collection of publishers that have been tried but could not be added to Fundus due to various problems. To add a new publisher please note the date you tried to add it and the reason your progress was stopped.

Publisher
Date
Encountered Problem

Wall Street Journal
24.08.2023
Paywall

The New York Times
27.08.2023
Paywall

USA Today
28.08.2023
Redirect -> Empty robots.txt

NY Daily News
29.08.2023
Geoblocking

The Times UK
29.08.2023
Paywall

Financial Times
31.08.2023
Paywall

Al Arabiya
24.4.2024
Cloud-Flare

Date: 27.04.2024
https://www.express.de/
urllib.error.HTTPError: HTTP Error 403: Forbidden
publisher uses bot protection ?

Date: 28.04.2024
https://medium.com/
urllib.error.HTTPError: HTTP Error 403: Forbidden
publisher uses bot protection ?


DNF Sort Explanation added

Related Issue

#1173

Proposed Changes

Detail Explanation of DNF sort in readme added and code for DNF sort is already added by someone but the explanation is missing so I added that to enhance the experience.

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the README.
[x] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

In this I have added a detailed explanation of DNF sort starting from what it is and ending with the disadvantages, all document was written in a simple language to be understandable easily.

DNF Sort is the sorting method that is used to sort the array only having 0's 1's and 2's.

Change is required to enhance the understanding of the DNF sort.

#1173

[x] New feature (non-breaking change which adds functionality)

LGTM🌟


I want to add +5 HTML CSS vanilla projects

Goal
Goal is to add +5 HTML CSS vanilla Projects
Details
I would like to add construction-site, music, blog, college-site and many more

would like to add responsive html-css projects
Can you please assign it to me under Hacktoberfest 2021? @Ayush7614


Mocked functions not tracking calls properly when called in a recursive context

Describe the bug
Given a recursive function which works through a list of functions and executes each one with a different set of arguments, we would expect that when this recursive function is under test, the mocked functions being passed in should independently track calls to each of them, allowing us to assert that each one is called with the correct arguments.
What instead happens is that the tracking of calls to each mocked function seems to get overwritten by tracking calls to the others. I suspect something is being passed around by reference somewhere, but haven't been able to figure it out by digging into either the Vitest or tinyspy source code.
It's quite a fiddly one to explain, so hopefully the reproduction repo makes it a bit clearer. I also found that if I debugged through the calls, I could see that the correct calls were being tracked against each function in turn, but that the subsequent function call tracking seemed to be overwriting the previous function call tracking.
Please let me know if there's any other info I can provide to help understand the problem. Thanks in advance for your help!
Reproduction
See StackBlitz for in-place example.
import { expect, test, vi } from "vitest";

const recursiveFn = (
  [fn, ...rest]: ((args: string[]) => void)[],
  args: string[] = []
) => {
  args.push("wibble");
  fn(args);

  if (rest.length) recursiveFn(rest, args);
};

test("Functions passed to recursive fn should track calls separately", () => {
  // given
  const fn0 = vi.fn();
  const fn1 = vi.fn();
  const fn2 = vi.fn();

  // when
  recursiveFn([fn0, fn1, fn2]);

  // then
  expect(fn0).toHaveBeenCalledOnce();
  expect(fn0).toHaveBeenCalledWith("wibble");

  expect(fn1).toHaveBeenCalledOnce();
  expect(fn1).toHaveBeenCalledWith("wibble", "wibble");

  expect(fn2).toHaveBeenCalledOnce();
  expect(fn2).toHaveBeenCalledWith("wibble", "wibble", "wibble");
});

Result:
AssertionError: expected "fn0" to be called with arguments: [ 'wibble' ]

Received:
    1st fn0 call:

    Array [
  -   Array [
  -     "wibble",
  -     "wibble",
  -     "wibble",
  -   ],
  +   "wibble",
    ]

System Info
System:
    OS: Linux 5.4 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 6.61 GB / 12.21 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  npmPackages:
    @vitest/coverage-c8: ^0.28.3 => 0.28.3
    vitest: ^0.29.2 => 0.29.2

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hi @sheremet-va - thanks for the speedy response, and taking the time to point out my mistake! Really appreciated.


Query parameters table is displayed as a string

Query Parameters section looks like in this screenshot, but is supposed to be a table:

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

ID: c5833e8f-1e83-b275-d3fe-0d4f81a56cbf
Version Independent ID: e3fb6faa-305a-179b-13df-fdb08056cc03
Content: Executing the export by invoking $export command on Azure API for FHIR
Content Source: articles/healthcare-apis/export-data.md
Service: healthcare-apis
Sub-service: fhir
GitHub Login: @CaitlinV39
Microsoft Alias: cavoeg

Thank you for catching this! It is resolved.

Thank you for catching this! It is resolved.

@CaitlinV39 Thanks for the super quick response. :+1:

@CaitlinV39 Thanks for the super quick response. :+1:


Downloader interface to sentry outdated

Download_headers does not handshake properly with sentry and does not detect protocol
Possibly related https://github.com/ledgerwatch/interfaces/commit/6eceb08988f0b684322d4829d3905957fea1bd3e

Closed by https://github.com/torquem-ch/silkworm/pull/522

@mriccobene don't close issue before related PR is merged.
We have auto-closing feature on PRs (i.e. when you open a PR related to an issue simply put in the description Fixes #xxx where xxx is the id of the issue or use the proper link button on the PR page.

In such way when the PR is merged the related issue is automatically closed with the proper reference (instead of appearing as manually closed)


Deleting cell should have confirmation before removing cell

Having just accidentally deleted a cell that had been running for over 4 hours, I'd like to suggest that there be a confirmation popup for running Jupyter cells to be deleted. Ideally there should be an option to confirm for all cells, but should be a default for cells that are currently executing.

you can undo delete cell operations, but that wouldn't bring back an in-progress cell, so a confirmation on running cells sounds reasonable.


[fix] [broker] Incorrect service name selection logic

Fixes #17080
Motivation
PulsarServiceNameResolver is used to randomly select a service name from multiple service names, the logic is:

select a random index of the service name list
if the previous service name can not work, use {previous index} + 1

But when we call the method PulsarWebResource.getRedirectionUrl, it will always create a new PulsarServiceNameResolver instance, this reduces the above logic to only randomly select a service name.
You can reproduce by ReplicatorTest.activeBrokerParse (the more invalid service names in variable cluster2ServiceUrls, the greater the probability of a problem).
Modifications
But when we call the method PulsarWebResource.getRedirectionUrl, reuse the same PulsarServiceNameResolver instance.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

https://github.com/poorbarcode/pulsar/pull/66

/pulsarbot run-failure-checks


V12 Support

Not currently installable on Foundry V12. Will this be supported on the V12 release?

heres hoping ... this is a big help and would love to see it still working for Ver 12