add decode_method for jsonrpc request

Fixes #169

The failing test has been fixed on development

rebased, will merge upon review @brandonpille


Spell checking doesn't work on iOS

Description
Spell checking doesn't work (red underline) when typing on iOS. It worked fine on Android.
Further testing:

Spell checking only works if there is multiline prop
Or no value prop provided

React Native version:
Expo SDK 40. RN 0.63.4
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Open App
Input text

Expected Results
Spell checking should work
Snack, code example, screenshot, or link to a repository:
https://snack.expo.io/sbVOzooBV

Same issue any update?

Do you still experience this issue?
I have four years of experience maintaining facebook/react-native and I specialize in the Text and TextInput components. I currently have 58 facebook/react-native PRs.
If you still experience this issue, I will prepare a patched release with the fix.
Thanks a lot


Support type 2 transactions

Closes: #1657

General question: Have you had a look at https://github.com/ethereum/web3.py/blob/3c00810e9a3563c69901549a6a54d4fe19c9d6a9/web3/_utils/transactions.py#L68 ?
It seems that web3.py's default is effectively doing what we are currently writing in the middleware. Of course, the middleware would give the power into our hands, but we could also save the effort and use the defaults.
Another option which would bring an actual benefit is that we fetch the latest block headers in the event fetcher anyway. There we can read the latest base fee so we could actually save us an RPC request. However, this is a bit tricky because it's stored in our logic and we would have to actively pass it to web3.
A third option could be to leverage the cache getBlockByNumber and always set the latest Base fee whenever we get a new block. If those caches were somehow able to communicate or cache the fee history call somehow then we could map it onto our cache system.


Fails to compile with clang11

README claims that clang11 is supported, but when I try the basic example with clang11 on Linux, compilation fails:
In file included from /home/conan/w/prod/BuildSingleReference/conan-center-index/recipes/reactiveplusplus/all/test_package/test_package.cpp:1:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/rpp.hpp:13:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/observables.hpp:19:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/observables/specific_observable.hpp:14:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/observables/fwd.hpp:13:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/subscribers/fwd.hpp:13:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/observers/constraints.hpp:13:
In file included from /home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/observers/fwd.hpp:13:
/home/conan/w/prod/BuildSingleReference/.conan/data/reactiveplusplus/0.1.2/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/rpp/utils/constraints.hpp:13:10: fatal error: 'concepts' file not found
#include <concepts>

Could you provide exact minimum supported versions of major compilers please (gcc, clang, msvc, apple-clang, though I guess apple-clang is not supported at all since it fails to compile even with latest version apple-clang 14 due to lack of std::ranges support)?

I will double check it later and update readme with specific versions of compilers, but CI works fine with clang-11
https://github.com/victimsnino/ReactivePlusPlus/actions/runs/3284620515/jobs/5410805522
-- The CXX compiler identification is Clang 11.0.0

Double-checked: clang-11 is possible to build RPP without any issues

Do you link to libstdc++ or libc++?

manually - not. Just do
export CC=clang
export CXX=clang++
cmake -B build -DRPP_BUILD_TESTS=1
cmake --build build --parallel 12

Closing due to inactivity and no way to reproduce it


Added documentation for Kiali

Looks good (assuming you resolve the conflicts). I quite like the style for listings (if it's new, but it's the first time I see it).

Fixes Maistra-33


Broadcasting over Arrays and CuArrays instead of calling kernels.

@ali-ramadhan why not broadcast over CuArrays? Is there a Performance hit?
Originally posted by @glwagner in https://github.com/climate-machine/Oceananigans.jl/issues/104#issuecomment-469749450

Based on some previous benchmarks I think so
https://github.com/climate-machine/Oceananigans.jl/blob/3cd4ae32cb4d716bc6470a6e7ba484ed98d60de7/benchmark/gpu.jl#L164-L198
Basically I wrote an x-difference operator that used @. @views which allowed it to act on Arrays and CuArrays, and when acting on a CuArray it was only ~10x faster compared to single-core CPU performance. While the entire time-stepping loop we have using GPUifyLoops.jl is ~90x faster.
However I don't think I did the benchmarking there properly (have to use @benchmark CuArrays.@sync I believe) and maybe I didn't use @. @views properly.
I think using broadcasts would make the code much more readable, but I can think of a few drawbacks (mainly related to performance):

I don't know how to fuse kernels when doing broadcasts. E.g. we might be able to do something like

@. Gu = calc_RHS_u(u, v, w, ...)
@. Gv = calc_RHS_v(u, v, w, ...)
...

which would look cleaner but then update_source_terms! would end essentially end up in several kernels. From talking with you I believe this shouldn't matter as kernel launches are cheap and the broadcast operator should essentially do exactly what update_source_terms! does, but I'm not 100% sure of this and we may lose out on performance.

We may want to fine tune our kernel launches, e.g. by using the thread-block layout we want which is probably possible, I'm just not very familiar with the CuArrays.jl package.

Some kernels, e.g. ones that do permutations like calculate_source_term_divergence_gpu! and idct_permute! can't be broadcasted over I think, but these are the exception rather than the rule.

To really find out whether we take a performance hit we might have to refactor the time-stepping to use broadcasting then benchmark the two approaches on CPU, GPU, and multi-GPU architectures (not sure if CuArrays.jl will do multi-GPU arrays yet). This will become much easier once #67 is resolved.

I'm not suggesting we should always use broadcasting. I'm just wondering if it's ok to use it for simple operations. It's a nice abstraction that works on CPUs and GPUs for simple calculations / global array updates (for example).

Ah sorry I must have misunderstood your question. Yeah I think broadcasts
tend to perform really well on scalar operations so I don't see why not.
On Tue, Mar 5, 2019, 12:13 PM Gregory L. Wagner<EMAIL_ADDRESS>wrote:

I'm not suggesting we should always use broadcasting. I'm just wondering
if it's ok to use it for simple operations. It's a nice abstraction that
works on CPUs and GPUs for simple calculations / global array updates (for
example
https://github.com/glwagner/StaggeredPoisson.jl/blob/d104825ba33f184af3b90ca0d958247d0011c7ad/src/solvers.jl#L148
).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/climate-machine/Oceananigans.jl/issues/108#issuecomment-469768233,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKyBSiIR6hlh-r4hjpSmahUJhp3x7Gzks5vTqXEgaJpZM4bfFUj
.

Ah sorry I must have misunderstood your question. Yeah I think broadcasts
tend to perform really well on scalar operations so I don't see why not.

there is sadly a performance difference between map, since broadcast need to check dimensions


Fix cache support for some versions

Scope & Purpose
Now we will take into account the fact, that primaryKeyCache and primarySortCache have bugs: https://arangodb.atlassian.net/browse/SEARCH-466

[x] :hankey: Bugfix
[x] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[x] sidelining PRs

[ ] ArangoDB Pullrequest
[x] RTA Pullrequest

Fix for https://arangodb.atlassian.net/browse/BTS-1352 will be introduced later

great, tnx!


Parse URI

fix #9

Cool, and it made Travis pass: https://travis-ci.com/justinwoo/format-nix/builds/106975489
Thanks


Calling line comment above comment , with out indentation ,causes error

https://user-images.githubusercontent.com/61395246/132909464-63cb0a14-5d57-4605-8808-a0ad4089de21.mp4
E5108: Error executing lua ...start/nvim-comment-frame/lua/nvim-comment-frame/util.lua:105: [nvim-comment-frame]: configuration not found for language: comment

This is due to an issue in language_for_range() API in treesitter. It considers the empty line as a comment line. Now comment frame refer the language trees and their ranges to figure out the language instead.


fix ignored session save_path

fixes symfony/symfony#16898
do not use php.ini session handler but native file to actually use save_path config
When handler_id is null it uses the Native one, but that does not set the save_path. So we need to use https://github.com/symfony/symfony/blob/master/src/Symfony/Component/HttpFoundation/Session/Storage/Handler/NativeFileSessionHandler.php instead (which is the default configuration).

@Tobion remind me, was this something that changed in Symfony 3? I always have a hard time wrapping me head around this, because I know (at least previously), that setting this setting to null and not setting it meant two different things.

Not defining handler_id is the same as handler_id:  session.handler.native_file (as now) because its the default value in the config. But IMO specifiying it explicitly is better DX because save_path and handler_id depend on each other.
handler_id: ~ means use handler from php.ini.

What about merging this in 2.3 then ?

@Tobion I agree with your point on DX. So, we used to default to ~, meaning "use php.ini" default. NOW this would default people to file storage. I'm just pointing out that we'll be changing the recommended default setting for projects, agree?
But I think I like it: though what about keeping the comment that setting this to null will cause the php.ini default to be used?
And yes, save_path was added in SE 3.0 only, but it always existed. So if we're going to keep it in 3.0, perhaps we should backport it to 2.3: it is nice to explicitly see why sessions are being stored in a specific location.

@ogizanagi the bug is ony in 3.0
Ok to sum up: In #606 the session handler was changed to use php.ini values. If you use the php.ini session handler, then the framework.session.save_path is irrelevant because it's not used at all.

So since symfony-standard 2.4 sessions are saved in php.ini save_path (sys_get_temp_dir by default) using the php.ini handler (files by default).
In symfony-standard 2.3 session are saved in app/cache/dev/sessions using session.handler.native_file as the default config of https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/Configuration.php#L252-L263 is used.
Since symfony-standard 3.0 @fabpot wanted to save sessions in var/sessions/dev via https://github.com/symfony/symfony-standard/commit/dcf4eadc767246546729813d88a3d1592e954363
But that does not work because the framework.session.save_path is not used at all and sessions are still saved in php.ini save_path. This is want is symfony/issues#16898 is about.

So either we keep using php.ini settings by default (which means we do not know where sessions are saved and thus the var/session directory makes no sense). Or we want to use var/sessions but then we have to fix the session handler to a file based one as well (because it does not make sense to configure the save_path to var/sessions if you use a redis handler in your php.ini.

var/sessions seems to be the best to me, and it was intended by @fabpot to use this directory, so I don't see why we should propose php.ini default to be used.

In fact, the final solution added by Fabien in 3.0, was suggested by drak (ghost, unfortunately, on the PR) on the linked #606 PR: https://github.com/symfony/symfony-standard/pull/606#issuecomment-29839961... but that was never the right solution (for the exact reasons this issue was opened).
I think we should keep the native, php.ini handler, but with more comments than we have now:
session:
    # handler_id set to null will use the default session handler from php.ini
    handler_id: ~

    # or, you can specify some specific handler and options
    # http://symfony.com/doc/current/reference/configuration/framework.html#handler-id
    # handler_id: session.handler.native_file
    # save_path: "%kernel.root_dir%/../var/sessions/%kernel.environment%"

But then it does not make sense to preconfigure the directory https://github.com/symfony/symfony-standard/tree/master/var/sessions if it is not used.

@Tobion you're right, so I would vote to remove the var/session directory if we used my proposal.
If we do use my proposal and you think the code is a little to wordy (i.e. too many comments), then yea: we could just link to the docs for how to configure session handlers in general. We should link to the reference docs - the link you posted (unfortunately) only shows you how to do file storage: it doesn't help anyone looking to configure something else, like Redis.
So we're back to what you mentioned @Tobion: do we default to using the php.ini default (as was done in 2.4-3.0 in the SE) or do we default to /var/session file storage? Based on the decision in #606, we previously decided to use the php.ini default.

As I understand it, @fabpot proposal was only about avoiding to have the save_path inside the application cache (which is the default), in order to prevent flushing it on a cache:clear.
Not especially about promoting the use of session.handler.native_file (but if used, suggest to store sessions into /var/session)
But then, as @weaverryan expressed, it makes no sense to have the var/session directory in SE if it is not used by default, as well as having the session.save_path path option configured. It should rather be commented.
I would opt for @weaverryan suggestion. Or even remove back the save_path option. Then, simply link the cookbook entry, which already mention why you should use another save_path than the default %kernel.cache_dir%/sessions.

Imo having sessions stored in var/sessions is less confusing for users as the Symfony applications would not interfer with other PHP applications on the same server which could lead to hard to debug issues.

The more I think about this, the more I agree with @xabbuh: put things in /var/sessions by default (as this PR does). But, I think at least a link to the docs is useful: this would be a common setting to need to change (and the docs could use some work too....)
session:
    # http://symfony.com/doc/current/reference/configuration/framework.html#handler-id
    handler_id: session.handler.native_file
    save_path: "%kernel.root_dir%/../var/sessions/%kernel.environment%"

:+1: as-is, but even more with the docs link comment

I've got the same issue (https://github.com/symfony/symfony/issues/17157). Please merge this!

Thank you @Tobion.

@weaverryan added the doc mention in 44a1fd8


More user testing and/or examples

From the GoogleDoc:

Perhaps look at existing applications
Build a small library of examples e.g. https://github.com/hokein/electron-sample-apps
Port StockFlux?

More exercising of the API via either user testing, examples, or a combination of both.

Port StockFlux?

I'm attempting this.


Init perla.json

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
Most of these are the defaults we set in Types.fs but most (if not all of these) are optional so we should trim the initial perla.jsonc and only leaving really relevant options in the json file.

This is out in v0.16.0


Problems with .create()

I'm trying to use jsdomify like the quickstart says, but I have some problems.
undefined is not a function (evaluating '(0,r.jsdom)(o)')
I'm using node 6, Karma + Webpack :)
The configs are here: https://github.com/asteka/asteka

Hi @guidiego, can you point me to the bit of code that is causing the issue?


Select multiple values?

Is there any option to make possible to select multiple values from search?

You can use select2 (https://select2.github.io) for multiple selection. Because typeahead's purpose of use is autocomplete.

You can also use bootstrap-tokenfield - see the second example in the link above.


⚠ Shadow Does Streams has degraded performance

In 27df35e, Shadow Does Streams (https://stream.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 5659 ms

Resolved: Shadow Does Streams performance has improved in 43802bf after 12 minutes.


Simplify entrypoint

When getting started with the repo, the two primary entrypoints are "building the code" and "running examples".
While a skilled developer will have no problem building with cmake, running chmod +x tests/test.sh, and understanding what is needed to run the examples, these are an extra impedance for someone new to the repo.
I'd recommend using a Makefile as the entrypoint for building, running tests, etc. The READMEs will need to be updated as well.
cc https://github.com/openjournals/joss-reviews/issues/2533

@nnadeau I would like to kindly convey to you that the issue has been resolved by creating Makefiles and also updating the documentation accordingly. Kindly provide your further reviews so we could decide if the thread could be closed.

New related issues: https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/28 https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/24 https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/23 https://github.com/kaustubh-sadekar/OmniCV-Lib/pull/22 https://github.com/kaustubh-sadekar/OmniCV-Lib/pull/21 https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/20 https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/19 https://github.com/kaustubh-sadekar/OmniCV-Lib/issues/18


How to get “Display name” on the label of in Blazor's razor page?

I have following model:
class User
{
    [Display(Name = "Display Name")]
    public string Name { get; set; }
}

I have following model:
class User
{
[Display(Name = "Display Name")]
public string Name { get; set; }
}
In standard Razor I would do something like that to get "Display name"
<label asp-for="Model.Name"></label>

but that doesn't seem to work in Blazor. Dose anyone know how to get display name in Blazor page without using reflection?
Thanks in advance...

Thanks for contacting us, @enetstudio.
This is not a feature we currently have. We will put this issue in the Backlog to reevaluate in the future.

Got it, thanks...


gmake: Makefile: No such file or directory

When I run "python3 ./scripts/build_wheel.py --trt_root /usr/local/tensorrt", I meet error
gmake: Makefile: No such file or directory
gmake: *** No rule to make target 'Makefile'.  Stop.

Thank you! I solved this question with your help, but I meet another error ”RuntimeError: The NVIDIA driver on your system is too old (found version 11080). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver.“
My CUDA is 12.2 and my NVIDIA driver is 520.56.06, so update the CUDA driver version is the only solution?

There is a related issue you encounter https://github.com/NVIDIA/TensorRT-LLM/issues/83, it may be helpful.

Closing - reopen if needed

When I run "python3 ./scripts/build_wheel.py --trt_root /usr/local/tensorrt", I meet error

Hi there,
I found the solution about this. Just install git-lfs follow by this link


fix(cloudid): add en-US html templte

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[x] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.7

/area cloudid
/cc @zexi

Codecov Report

Merging #9958 (39025c2) into master (1ab8ce5) will increase coverage by 2.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9958       +/-   ##
==========================================
+ Coverage    5.97%   8.05%    +2.08%
==========================================
  Files         849     107      -742
  Lines      132215   12991   -119224
==========================================
- Hits         7898    1047     -6851
+ Misses     123616   11824   -111792
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.05% <ø> (+2.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/billing/billingcycle.go

pkg/compute/models/dns_zones.go

pkg/multicloud/ucloud/host.go

pkg/util/stringutils2/i18n.go

pkg/appsrv/fetch.go

pkg/compute/models/external_projects.go

pkg/compute/models/dnsrecords.go

pkg/compute/models/loadbalanceraclresource.go

pkg/multicloud/aws/host.go

pkg/compute/models/cloudregions.go

... and 732 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9958 (39025c2) into master (1ab8ce5) will increase coverage by 2.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9958       +/-   ##
==========================================
+ Coverage    5.97%   8.05%    +2.08%
==========================================
  Files         849     107      -742
  Lines      132215   12991   -119224
==========================================
- Hits         7898    1047     -6851
+ Misses     123616   11824   -111792
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.05% <ø> (+2.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/billing/billingcycle.go

pkg/compute/models/dns_zones.go

pkg/multicloud/ucloud/host.go

pkg/util/stringutils2/i18n.go

pkg/appsrv/fetch.go

pkg/compute/models/external_projects.go

pkg/compute/models/dnsrecords.go

pkg/compute/models/loadbalanceraclresource.go

pkg/multicloud/aws/host.go

pkg/compute/models/cloudregions.go

... and 732 more

Continue to review full report at Codecov.

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


Reproducing results

Hi thanks for sharing the great work!
I tried the code on Replica dataset (with TensoRF model), on scan1 to 7 it gives close PSNR values to the reported results, but for scan 8, I got 24.42 PSNR which is far from the reported 39.59 in the paper.
Is it normal? Does it also happen on your machine?
Thanks in advance!

Hi thanks for sharing the great work!
I tried the code on Replica dataset (with TensoRF model), on scan1 to 7 it gives close PSNR values to the reported results, but for scan 8, I got 24.42 PSNR which is far from the reported 39.59 in the paper.
Is it normal? Does it also happen on your machine?
Thanks in advance!

Sorry for the late reply. Try setting s3im_weight=5 in Replica scan8.

Thanks for your reply! I am also wondering if you can also share the TanksAndTemples dataset used in the paper? I tried to find it but it seems that your dataset is pre-processed. Thanks a lot!

@AoxiangFan sry for the late reply. You can modify the TanksAndTemples dataset according to the description in our paper. I will share the dataset lately.


[Security] Nonce reuse

Nonce reuse
I have a question in regard to nonceEnabled:
I assume that the csp-html-webpack-plugin is only invoked at build time and not for every http request. If this assumption is correct, how can one prevent attackers from just copying CSP nonces and by that bypassing the entire CSP?
Relevant section in the CSP spec is here: https://w3c.github.io/webappsec-csp/#security-nonces
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

It would be great if an nonce could be passed to the page at runtime somehow.

I came across this option but I'm not sure the CSP HTML Webpack Plugin makes use of it?
https://webpack.js.org/guides/csp/
I've tried setting __webpack_nonce__ but it doesn't seem to end up applied.

You're correct in your assumption - nonces are only useful if they are changing often, ideally on every page load. If your app will be deployed for long periods of time without its source code changing, you should either:

Use shas instead, which checks the contents of a script block matches in a more strict fashion
Generate your own nonces server side and put them into your html source on each page load, using the __webpack_nonce__ feature as suggested above. Here's a stackoverflow post with some more details

At Slack, we have opted to only use shas

@AnujRNair thanks for your reply! Are there any potential risks that nonce can address which hashes cannot?
We tried getting __webpack_nonce__ working without luck, so if hashes alone eliminate any need for an nonce, that would be great news.

Not to my knowledge. As far as I am aware, they're as good as each other. Someone can correct me if you find otherwise!

Hashes are useful for when you don't want to serve your HTML through a server request first. The hashes are precomputed and put directly into the HTML. Nothing more to do
Nonces are useful when you have dynamic JS being generated by the server, which is being added to the HTML. It's easier to create a nonce then parse the file and generate a hash

Thanks for confirming @AnujRNair!
I think that CSP can serve as strong defence-in-depth mechanism, if configured properly. Unfortunately, it's very easy to misconfigure a CSP and by that making it trivially bypassable which will not only take away any security benefits, but will also give a false sense of security.
I really like this module, but I think the way (esp. the defaults) are implemented right now could cause many applications to end up with a trivially bypassable CSP. I think it's crucial to provide a secure-by-default configuration as most users won't know all the intricate details about CSP:

nonce reuse: if nonces are not changing on every page reload (even cached responses are a problem!) they'll cause the entire CSP to become bypassable (this is similar to XSRF tokens). Nonces changing often (even if every 10 minutes) are still easy to bypass as the attacker could fetch the current nonce in less than a second.

This module enables nonces by default, so even if your hashing everything, the presence of a re-used nonce will make the entire CSP bypassable as the policy allows executing of scripts using a hash or a nonce.
It's not trivial to setup SPAs with regenerated nonces for every page load. Unless this module can provide this integration, it might be better to disable nonces by default and warn developers that if they enable noncing they'd need to make sure that they're regenerated on every page load themselves.

host allowlists: host entries in the CSP often lead to bypasses (JSONP, hosting of AngularJS, ..), esp. if there are CDNs in the allowlist (which is often necessary). More about how easy it is to bypass allowlists in CSP (even automatically) can be found here.

This module could add 'strict-dynamic' by default, which would cause the entire allowlist to be ignored and therefore would remove all potential allowlist based bypasses.

However, when using hashes alone (which likely is the recommendation of SPAs if they can't generated nonces on every page load) it's not possible to hash sourced scripts (actually it is, but only in Chrome right now..). Since alllowlists shouldn't be used either the only way to get a hash-only policy working is to rewrite sourced scripts that can't be inlined (for example if they're hosted somewhere else) into a hashable inline script block that dynamically loads these scripts.
E.g. these two sourced scripts need to be converted into a hashable inline script.:
<script src="https://example.org/foo.js"></script>
<script src="https://example.org/bar.js"></script>

<!-- 'sha256-XuHWTNmJH6UK7Qi9Te9PhtU5CRMuihd33ChamIrBDsI=' -->
<script>
var scripts = [ 'https://example.org/foo.js', 'https://example.org/bar.js'];
scripts.forEach(function(scriptUrl) {
  var s = document.createElement('script');
  s.src = scriptUrl;
  s.async = false; // to preserve execution order
  document.head.appendChild(s);
});
</script>

Regarding @Slapbox's question on nonces vs. hashes:

hashes are slightly more resilient as they don't suffer from nonce exfiltration issues. But in practice hashes are harder to use as it's not possible to hash sourced scripts (browser support and if fetched scripts are not static).

Great writeup @lweichselbaum.

I think it's crucial to provide a secure-by-default configuration as most users won't know all the intricate details about CSP

I think this part is a bit tough though. Any secure CSP will break most projects and will only be fixable by users who understand CSP in the first place. Providing a secure example isn't enough and so I feel like directing people to external resources might be best here.

Thank you!

Any secure CSP will break most projects and will only be fixable by users who understand CSP in the first place.

I think it's possible to have a secure CSP without breaking most projects.
The rewriting of sourced (external) scripts (which were previously allowed by host allowlists or nonces) into a hashable inline script as shown in the code snippet above can be automated. With that a CSP based only on hashes (without allowlists) can be used as a secure default.
Of course, if you can use nonces that change on every page load (nonce actually stands for number used once), it would be easier to deploy a strong CSP as you wouldn't have to rewrite script tags.

@AnujRNair I found that hashes aren't applied except to inlined scripts and styles - so I'm wondering if you have any advice for getting __webpack_nonce__ working, since otherwise we're back to the nonce reuse issue.

@AnujRNair how are you going about using SHAs at Slack? It seems like this is the route we'll have to go, but it's not really supported yet in the plugin. Any advice for how to move forward? It seems like we've just hit an unbreakable wall here.

Sorry for the delay in getting back to you here
@lweichselbaum thanks so much for the detailed writeup and presentation - it was extremely useful.
I would love to create a secure-out-of-the-box plugin here - it looks like we probably can't use nonces since webpack generates everything statically at compile time, so we might have to switch to using hashes only and deprecate nonces to ensure we don't provide a false sense of security. Unless you know of a way that we might be able to use nonces with webpack here?
@Slapbox that is correct - only inline styles and scripts are hashed at the moment. https://github.com/slackhq/csp-html-webpack-plugin/pull/87 is exploring whether we can hash external script and style tags as well
At Slack, we only use hashes, and we generate our script tags as @lweichselbaum recommended. We do this by defining a custom template, and passing it to the HtmlWebpackPlugin instance.
You can do the same with something similar:
webpack config:
function generateTemplateParams(compilation, assets) {
  return {
    assetsJs: assets.js,
    assetsCss: assets.css,
  }
}

new HtmlWebpackPlugin({
  templateParameters: generateTemplateParams,
  template: 'path/to/template.ejs',
  inject: false, // don't inject script and style tags - we'll do so manually

template.ejs:
<% _.each(assetsJs, function(js, idx) { %>
	<script>
		const s<%= idx %> = document.createElement('script');
		s<%= idx %>.src = '<%= js %>';
		document.getElementsByTagName('head')[0].appendChild(s<%= idx %>);
	</script>
<% }) %>

This is the basics, but there's lots more customization you can do there

Maybe there could be a way to have the nonce injection be a replaceable token, so that the nonce token could be replaced dynamically at runtime? I would like that ability, because I am attempting to do just that, until a hash can be generated for an external script/stylesheet.


fix: implementation of file size formatting

This PR removes src/utils/fmt.rs, since it only had the format_bytes function, which can also be used from another library.
The implementation of format_bytes is also incorrect. 1024 bytes is not equal to 1KB, as the test indicates. 1024 bytes is equal to 1KiB, and means Kibibyte, where bi stands for binary. Why not just use a library for that? That would eliminate such bugs.
The PR changes the file size type from String to u64 and adds a _bytes postfix to the property name.
- pub(crate) size: String,
+ pub(crate) size_bytes: u64,

I would love to store the file size as the Size struct provided by the size crate and remove the postfix, but Size doesn't implement the Serialize trait, and we'd have to wait for that before we can do that.

Hi @Antosser! The confusion between Kilobyte and Kibibyte is pretty common.
I recommend you read this article which can help you understand better the notation and how
the different units of work.
With regards to add another dependency just for this, I don't think is ideal as I try to keep
Http Server as dependency light as possible.

Usually computers doesnt render size using Base-2, the use of kilo, giga, and mega is
more of jargon than actually the value.
Please take a peek on these two pictures:
This is the current main:

This is this branch proposal:

My observations are:

macOS Get Info window uses Kilobytes instead of Kibibytes
Both size values (skip unit please) are the same value, but in neither of both the size matches OS specific size. (Float point precision is a well known issue).

Usually computers doesnt render size using Base-2, the use of kilo, giga, and mega is
more of jargon than actually the value.

Windows uses binary but incorrectly displays KiB as KB

The point is, the way it is right now is incorrect. The number is binary while the unit is decimal

but in neither of both the size matches OS specific size

That's because the number in http-server is in KiB, while the OS size is in bytes

Usually computers doesnt render size using Base-2, the use of kilo, giga, and mega is

more of jargon than actually the value.
Windows uses binary but incorrectly displays KiB as KB

Im struggling finding an OS that uses Base-2 notations in their data size notations.
Even though I consider you are technically right, I still have to consider the user base counter part, which not only involves the technical side of the problem, but the educational.
OS developers and the Software Industry have been using Base-10 notation for years.
This would introduce confusion, and also would affect current users perception on the data size values because HTTP Server would render a different unit than their systems.

The point is, the way it is right now is incorrect. The number is binary while the unit is decimal

Thing is, no popular system uses binary notation. Its a matter of usage and how the data industry popularized data units.
Using Base-2 would be against that, please take into consideration all kind of users.

but in neither of both the size matches OS specific size

That's because the number in http-server is in KiB, while the OS size is in bytes. It has almost nothing to do with floats

Please pay attention to the size value in macOS Get Info window and compare it to HTTP Server's size value.

This commit now uses the humansize crate, which allows choosing BINARY vs. DECIMAL. This is what if now looks like:

These are the possible options provided by the crate:


[ARO-7788] Don't overwrite default installer version in local dev

Which issue this PR addresses:
Fixes https://issues.redhat.com/browse/ARO-7788
What this PR does / why we need it:
Currently, the dev cluster creation tooling always makes sure that the default openshift version together with the default installer image is written to the cosmos db before creating the cluster. This however makes it impossible to use a custom installer image with the default openshift version, as any modifications to the installer image are overwritten.
This PR changes this behaviour so that the default version and installer image is only written when it is not already present.
Test plan for issue:

testing was performed according to instructions in jira ticket.

Is there any documentation that needs to be updated for this PR?

No

How do you know this will function as expected in production?

this doesn't affect production.

/azp run ci

/azp run e2e


⚠ Bofrost.be has degraded performance

In 144b0dd, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1354 ms

Resolved: Bofrost.be performance has improved in 1f57354 after 7 minutes.


VTGate batch API changes

This is the first part of the batch API changes. This change just introduces the new API. The actual functionality will be implemented in subsequent changes.
I debated about making the tablet type a query level parameter vs. the current request level parameter, but decided to keep it at request level. I think it will be too confusing to allow multiple queries to go to different tablet types.
Looks like grpc is not implemented for vtgate. So, there was no change required in that area.

LGTM.
gRPC is not implemented for vtgate yet, you're correct, I was waiting for you to change the API first, so we only do the work once...
However, you can already change the proto3 definitions for vtgate service to match this change if you want, so it's done. Ultimately, the proto3 will be the source of truth for all the APIs and their documentation... But I'll do it if you don't. :)

@alainjobart PTAL

LGTM


Text missing in aorsa2d.ps

It seems that the ps lost all text. When I ran AORSA back in May all the graphs in aorsa2d.ps had labels, but they are all gone in the file from my 128 MHz helicon computation (I repeated it today). The old aorsa2d.ps is also two times larger.
I checked the file with 3 viewers: Ghostviewer on windows, acrobat distiller on windows, and ghost viewer on windows subsystem Linux.
Maybe it is necessary to recompile pgplot?
I am not sure whether I want to submit my full-scale AORSA calculation now, since I only know how to diagnose my AORSA runs with these plots.
Any advice would be helpful.
I attached all the usual output and the PDF I got from acrobat distiller, since PS is not supported here. I also attached the first 11 pages from the AORSA run I did in May.
log_aorsa2d.txt
out15.txt
aorsa2d_in.txt
aorsa2d.PDF
aorsa2d_may_excerpt.PDF

This may be an issue with the grfont.dat file being missing? It is in the examples, but double check it is still present in your run directory.

That makes sense, thanks! Rerunning the debug case now!

Ok that fixed it. Thanks! I will keep in mind that I have to have that file in my working directory.


fix(exporter-zipkin): add main property - entry point to the module

Which problem is this PR solving?

Closes #287

Add missing main property - entry point to the Zipkin exporter module.

Codecov Report

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

@@            Coverage Diff             @@
##           master     #289      +/-   ##
==========================================
- Coverage   98.96%   98.89%   -0.07%
==========================================
  Files          78       78
  Lines        3077     3163      +86
  Branches      187      213      +26
==========================================
+ Hits         3045     3128      +83
- Misses         32       35       +3

Impacted Files
Coverage Δ

...ckages/opentelemetry-core/src/common/NoopLogger.ts
14.28% <0%> (-5.72%)
:arrow_down:

...ges/opentelemetry-core/src/common/ConsoleLogger.ts
91.66% <0%> (-3.08%)
:arrow_down:

.../opentelemetry-core/test/metrics/NoopMeter.test.ts
94.87% <0%> (-2.19%)
:arrow_down:

...s/opentelemetry-core/test/context/B3Format.test.ts
100% <0%> (ø)
:arrow_up:

.../opentelemetry-exporter-jaeger/test/jaeger.test.ts
100% <0%> (ø)
:arrow_up:

...s/opentelemetry-core/test/trace/tracestate.test.ts
100% <0%> (ø)
:arrow_up:

...entelemetry-exporter-jaeger/test/transform.test.ts
100% <0%> (ø)
:arrow_up:

...entelemetry-core/test/common/ConsoleLogger.test.ts
100% <0%> (ø)
:arrow_up:

.../opentelemetry-core/src/trace/spancontext-utils.ts
100% <0%> (ø)
:arrow_up:

...s/opentelemetry-core/test/trace/NoopTracer.test.ts
100% <0%> (ø)
:arrow_up:

... and 15 more


https://www.samsung.com/us/support/?chat=auto

https://www.samsung.com/us/support/?chat=auto

PLEASE EXPOSE ALL OF MY GIRLFRIENDS SECRET RELATIONSHIPS


ensureNotInGC: Use GC.inFinalizer instead of allocating

This requires a bump of the minimum version to v2.090, but I believe that's fine (we still support 6 versions, aka 1 year).


preparation for release 0.14.0

List of related issues or pull requests
Refs: #306
Describe the changes made in this pull request

bumped minor version to 0.14.0
updated CHANGELOG

Instructions to review the pull request

No one loves a good changelog more than you!


Update docs

Having to setup emsdk like that on readthedocs is not great. We should probably have the xeus-python addon do this automatically if needed.

Looks like the emsdk conda package is painful to use for end-users and on readthedocs. I'll try to make it easier to use https://github.com/conda-forge/emsdk-feedstock/pull/3. Ideally the end user would not even know about emsdk.


sofa-ark-maven-plugin support for running integration test

Your question
https://docs.spring.io/spring-boot/docs/current/maven-plugin/usage.html , springboot based ark plugin
now not support for running integration test while package, we now need for this function, wondering if
this could be done in future version

@lunasxk  we has support integration test in spring boot.  http://www.sofastack.tech/sofa-boot/docs/sofa-ark-ark-demo


"A cycle occurred while laying out the GUI." Exception occurred while adding the Inlines to the TextBlock in WINUI_Desktop

Describe the bug
"A cycle occurred while laying out the GUI." exception occurred while adding the Inlines to the TextBlock in WINUI
Steps to reproduce the bug

Run the attached Sample.
Note the "A cycle occurred while laying out the GUI." exception occurred.

You can find the sample in the bottom of the query.
Expected behavior
The "A cycle occurred while laying out the GUI." exception should not occur and TextBlock should update based on the Inlines.
Screenshots

NuGet package version
1.0.0
Packaging type
No response
Windows version
Windows 10 version 20H2 (19042, October 2020 Update)
IDE
Visual Studio 2022-preview
Additional context
We have a custom button that has the content as ContentPresenter. By using this custom button we have tried to change the TextBlcok foreground based on its content by using the Run and TextBlock.Inlines. Please refer to the below image which we have tried

And in the Custom Button ArrangeOverride method, I have changed the custom button contentpresenter ie. TextBlcok inline based on its content. While I am doing this, the button ArrangeOverride is called multiple times so that only this exception occurred. We need to know why the Button ArrangeOverried is called multiple times when we change textblock inlines.
Sample Location
WINUI Sample - TextBlock_Inline_WINUI.zip
And i have added the same codes in the UWP platform. In UWP also the same "Layout cycle detected." exception occurred.
UWP Sample - TextBlock_Inline_UWP.zip
But the same codes does not occur any issues in the WPF sample and ArrangeOverride is also called only one time:
WPF Sample - TextBlock_Inline_WPF.zip

I am using MAUI and I got this error with:

Label and multiBinding
FormattedString and multiple spans

I am using MAUI and I got this error with:
Label and multiBinding
FormattedString and multiple spans

@SathiyathanamSathish your ArrangeOverride method is calling ApplyInline which clears the text box and then adds new content, this is causing the layout to be dirtied which is causing a new layout to be run which repeats the process causing a cycle.

I have got the same error using MAUI with ListView.
When the control containing the ListView is made invisible then visible I got the crash.

I've also this error with collectionview and listview on .net MAUI while jumping back from one page to another.
@tripjump Did you ever find out the problem or a workaround ?

I am seeing this on MAUI targeting WinUI. It happens when clicking a button that executes a navigation command, from within a CollectionView that is bound to a lot of records.

I had this issue when page where navigation started from had next code with border (not commented out):
.Net7 in use and seem to occur only with WinUI. Not in android emulator at least (didn't test in real device). Didn't have any effect when took content or parameter from border out. Needed to leave content without border to get it work. In navigated to page I also have Listview with border but it didn't have any difference if I took border out from there (or anything else)
    <ListView x:Name="MainPanel" ItemsSource="{Binding SearchItems}" BackgroundColor="#232323" ItemTapped="MainPanel_ItemTapped" HasUnevenRows="True" SeparatorColor="Transparent">
        <ListView.ItemTemplate>
            <DataTemplate>
                <ViewCell>
                    <!--<Border Padding="4" MinimumHeightRequest="55" BackgroundColor="#191919" Margin="0,1,0,1" StrokeThickness="1">
                        <Border.StrokeShape>
                            <RoundRectangle CornerRadius="5" />
                        </Border.StrokeShape>-->
                        <Grid>
                            <Grid.ColumnDefinitions>
                                <ColumnDefinition Width="*" />
                                <ColumnDefinition Width="Auto" />
                            </Grid.ColumnDefinitions>
                            <Grid.RowDefinitions>
                                <RowDefinition Height="Auto"/>
                                <RowDefinition Height="Auto"/>
                            </Grid.RowDefinitions>
                            <Label Grid.Column="0" Text="{Binding CurrentName}" FontSize="14" TextColor="White" Margin="3,0,0,0" LineBreakMode="WordWrap"/>
                            <Image Grid.Column="1" HeightRequest="25" WidthRequest="25" Source="video.png" IsVisible="{Binding IsLocked}" Margin="0,3,5,3" Aspect="AspectFit"/>
                            <Image Grid.Column="1" Grid.Row="1" HeightRequest="25" WidthRequest="25" Source="star_border.png" Margin="0,0,5,3" Aspect="AspectFit"/>
                        </Grid>
                    <!--</Border>-->
                </ViewCell>
            </DataTemplate>
        </ListView.ItemTemplate>
    </ListView>


[FEATURE] Filters for display tables

Add filters within the various display screens so as to simplify the search.
Four very useful filters for example in the “Executions” screen would be:

“Status” filter
“Backup” filter
“Database” filter
Filter “Started at”

Yes, honestly would love to have some filters on these tables and even possibly a search as well bar as well.


regiontoshare: Add version 1.3.5651

Closes #10698

[x] I have read the Contributing Guide.

/verify


add polarionID for test verify hook annotation updates domainxml

What this PR does
Before this PR:
no polarion id for  update domain XML with SM BIOS properties
After this PR:
adding polarion id for  update domain XML with SM BIOS properties

Fixes #
Why we need it and why it was done in this way
polarion ID needed so test can be wxecutable in Tire1
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

/test all

/ok-to-test

/lgtm

@tiraboschi can you please review

@EdDev can you please review?

created different PR https://github.com/kubevirt/kubevirt/pull/12013


Remove TODO comment about merging events

What this PR does / why we need it:
Just removed a TODO comment.
We just settled that we don't have to merge events when committing, on this discussion: https://github.com/pipe-cd/pipe/pull/1429#discussion_r557089641
Which issue(s) this PR fixes:
Fixes https://github.com/pipe-cd/pipe/issues/1406
Does this PR introduce a user-facing change?:

NONE

🚀
/approve

🚀
/approve


Add xarray wrapper for WAA Lejinse

TODO:

[ ] add tests
[ ] check docstring
[ ] add info to whatsnew

Codecov Report

Merging #82 (4d4d5a6) into master (96ddefa) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
- Coverage   65.64%   65.60%   -0.05%
==========================================
  Files          22       22
  Lines         780      782       +2
==========================================
+ Hits          512      513       +1
- Misses        268      269       +1

Impacted Files
Coverage Δ

pycomlink/processing/xarray_wrapper.py
88.00% <ø> (-4.00%)
:arrow_down:

pycomlink/processing/wet_antenna.py
87.27% <100.00%> (+0.48%)
:arrow_up:

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 96ddefa...4d4d5a6. Read the comment docs.


Multiple errors trying out type_check

I'm just starting to try type_check, and my very first attempt is failing miserably.
I'm probably missing something, sorry if that's the case.
defmodule EmptyMix do
  defstruct [:name]
  use TypeCheck, enable_runtime_checks: Mix.env() != :prod
  @type! t :: %__MODULE__{name: String.t()}

  @spec! example(%{String.t() => any} | EmptyMix.t()) :: EmptyMix.t()
  def example(%__MODULE__{} = struct), do: struct
end

I'm getting:
** (UndefinedFunctionError) function String.t/0 is undefined or private

It seems to be due to the second usage.
If I change the second use to ...%{binary() => any} ..., I get:
** (UndefinedFunctionError) function EmptyMix.t/0 is undefined (function not available)

What am I missing?
If I then change these EmptyMix.t() to t(), then I get:
** (CompileError) lib/type_check/spec.ex: invalid quoted expression: #TypeCheck.Type< binary() >

Please make sure your quoted expressions are made of valid AST nodes. If you would like to introduce a value into the AST, such as a four-element tuple or a map, make sure to call Macro.escape/1 before

Hey there!
No worries, what goes wrong here is a usage error, but a very subtle one.
It may be a good indication that we need to improve the error messages for this particular problem.
The problem is the part %{String.t() => any()}. This is not actually a valid type. You have the choice between:

%{required(String.t()) => any()}
%{optional(String.t()) => any()}
3.%{"some_particular_constant_value" => any()}.
(switching String.t() for binary()

It seems that currently TypeCheck tries to interpret String.t() as a literal constant value and therefore compiles it as if it were a normal function call. (And later on the compiler then will complain that this function does not exist). Switching String.t() out for binary() similarly results in it trying to use the type 'binary()' as a literal value, which leads to the "invalid quoted expression" error.
Let me see whether we can do something to produce more readable error messages when this mistake is made. I'm not sure this is possible in the general sense, but at least for some common cases it might be possible to add a "did you mean" section to the raised exception message before reraising.

The other problem you get, about EmptyMix.t() not being found is something that I consider a real bug in the library. Substituting it for t() is the way to circumvent this problem for now, but this should be handled by the library itself in my opinion. I'll make a new issue for this bug.

Thanks for the reply :-)

The problem is the part %{String.t() => any()}. This is not actually a valid type.

Oh, it is not? I read the docs as it being equivalent to the require() form... I'll gladly make a PR to improve the official doc if needed. Or did you mean that it's not a valid type for type_check but valid in Elixir?

[...] I'll make a new issue for this bug.

Thanks.

Interesting!
Looking in the documentation, it seems like this was added in Elixir v1.11. Whether it was already allowed beforehand (and only missing in the docs) or not allowed at all I do not know.
But this change things: The library should definitely allow this syntax and transform it to the required(type) form automatically :+1: !

Ah, ok.
There seems to be some level of support already though.

There seems to be some level of support already though.

That is a references to a test file in which the creation of types based on 'real' Elixir typespecs is tested. This is a test case where this variant of the syntax is tested, but it is constructed as a normal Elixir typespec. It does not go through the normal parsing step that happens when you call @type!, @spec! or TypeCheck.conforms.

The fix is part of the now-published release v0.12.4.


Expand tutorial and current reference into Developer Guide

@friedger  suggested we build out a similar guide (simpler of course) https://developer.android.com/guide/
Currently, we have:

tutorial (hello world)
reference
three more sophisticated but undocumented examples

@moxiegirl I added some paragraphs in the README (See https://github.com/blockstack/blockstack-android/pull/123) Should this stay there or go somewhere else? Should we generate documentation from the example codes? So that we can maintain the code only in the source folder?

@friedger Well, when it comes to API reference it makes sense to generate it from the source code. Tutorials are a bit problematic, depends on the tool of course. Do you have one in mind?


[Bug]:CAYW failed

Debug log ID
FA4AFDUC-refs-apse
What happened?
A CAYW failed error occurred while exporting information

Can't do anything without a new log.

Can't do anything without a new log. 没有新日志什么也做不了。

Sorry, I almost forgot about it. This is the log ID running on 3983: EVGWV3VX-refs-apse

Can't do anything without a new log. 没有新日志什么也做不了。

Sorry, I almost forgot about it. This is the log ID running on 3983: EVGWV3VX-refs-apse

As before, CAYW failed is displayed when citing documents

These builds for now only add logging to find the cause of the problem, I don't know what the problem is yet (I cannot reproduce it locally). Can you get me a new log from build 4002?

These builds for now only add logging to find the cause of the problem, I don't know what the problem is yet (I cannot reproduce it locally). Can you get me a new log from build 4002?

This is the log ID of version 4002: NSFKDIC8-refs-apse

This just adds more logging -- I can see what call is being issued, but that call succeeds for me.

(assuming you picked Combined multi-objective optimization...)

(assuming you picked Combined multi-objective optimization...) （假设您选择了组合多目标优化...）

The main process is like this, using Obsidian's Zotero Integration plug-in to import document information, when importing, zotero's own document selection page will pop up, and after selecting confirmation, Bibtex reports an error, and the Obsidian plugin does not receive any information about the document.
I don't know if this will help you pinpoint the cause

(assuming you picked Combined multi-objective optimization...)

This problem exists on any literature entry

I will need a new debug log from build 4003.

I will need a new debug log from build 4003.

Debug log ID:UEXDP4YL-refs-euc

Can you try again on the new build, and send a log? It won't work, but I hope to get a more useful error message in the log with it.
Can you try disabling all extensions except bbt and trying again? I haven't been able to reproduce the error, I'd like to rule out or hone in on extension conflicts.

Can you try again on the new build, and send a log? It won't work, but I hope to get a more useful error message in the log with it.
Can you try disabling all extensions except bbt and trying again? I haven't been able to reproduce the error, I'd like to rule out or hone in on extension conflicts.

Following your thinking, I checked all the extensions. The Zotero Citation extension was found to be a source of conflict.

Can you try again on the new build, and send a log? It won't work, but I hope to get a more useful error message in the log with it.
Can you try disabling all extensions except bbt and trying again? I haven't been able to reproduce the error, I'd like to rule out or hone in on extension conflicts.

Following your thinking, I checked all the extensions. The Zotero Citation extension was found to be a source of conflict.

Keep only the bbt and Zotero Citation extensions,Debug log ID:B6FQ63NW-refs-apse

Where do I find this Zotero Citation extension?

Where do I find this Zotero Citation extension?

This is the url of the extension:https://github.com/MuiseDestiny/zotero-citation.
Conflict issues are currently being raised in the extension

I can't help there. Everything is in chinese.

Build 4028 should fix it.

I run without problems with build 4029, thanks for your help.👍


WIP: Create a Django backend adapter for CockroachDB

Start following the Django tutorial and try to get the resulting app running on CockroachDB. This doesn't work yet, but it's a start. Only the last commit in this branch is really interesting.
Progress is currently blocked on cockroachdb/cockroach#4357
This branch also deletes the old SQL driver now that we've switched to the postgresql protocol.

Some of the features that need to be supported by cockroachdb inorder to work with django-orm using postgresql_psycopg2 backend.

uuid, time, inet datatypes
Function pg_catalog.pg_table_is_visible()
Directly interpreting timestamp literals from strings.
extract() function in extract('day' FROM '2010-02-20 00:00:00') format, 'dow' for 'dayofweek'.
date_tunc() function
Deferrable constraint checks.
Savepoints
Tablespaces
Schema changes inside transactions
Sequences, setval() function
Cursors
ALTER COLUMN TYPE
Operator patterns for varchar and text indexes.

From a quick glance, it looks like CockroachDB now supports the UUID datatype.

is any update with that ? Is any way how we could help ?

We've made progress on some of the features that django needs, but some of the big ones are still open (including column type changes and deferrable constraints). If you want to help out the issues linked in https://github.com/cockroachdb/cockroachdb-python/pull/14#issuecomment-300455498 would be a good place to start.

Is anyone actively looking at this?  It would make CockroachDB immensely more usable and capable of powering thousands of Django dashboards.

Thanks for this amazing work , I would like know what is the current state or status about this driver to django ?.
Thanks

I spoke with someone at CockroachDB about Django support recently and it sounds like due to the sheer volume of work on their plate, they're focusing on paid customer feature requests first (which is understandable for a growing startup). If any of your companies really want Django support in CockroachDB, try to advocate to your managers to pay for the startup/enterprise versions to help speed things along!

I spoke with someone at CockroachDB about Django support recently and it sounds like due to the sheer volume of work on their plate, they're focusing on paid customer feature requests first (which is understandable for a growing startup). If any of your companies really want Django support in CockroachDB, try to advocate to your managers to pay for the startup/enterprise versions to help speed things along!

Thanks for your comments  .
Have a nice day.

Any updates for this?
I'm eager to make this work with django

@rkruze has been looking into this.

we expect support for most platforms to be driven by the community instead of built by Cockroach Labs.

Thank you for the great open source software and all the excellent work put into this.
I hope my comment doesn't come as rude or make any attack or a way to underestimate of the effort of every single individuals into this project.
However, when I read

PostgreSQL-compatible driver or ORM

I'd expect to anything from postgresql be working with the cockroachdb out of the box.
The first thing that got me watching cockroachdb development was the fact about being compatible with PostgreSQL drivers or ORM, but statments such as

we expect support for most platforms to be driven by the community instead of built by Cockroach Labs.

will make me to think such work is being put on the framework or app developers, the app/framework devs are simply using a PostgreSQL driver to build the ORM and if cockroachdb is compatible with PostgreSQL then they should not have anything else to work on.
I believe Django does uses very specific PostgreSQL features and has a great recommendation for such database, but things like https://github.com/cockroachdb/cockroachdb-python/pull/14#issuecomment-304429967 seems to be pretty standard PostgreSQL stuff that people would expect from a "PostgreSQL-compatible driver or ORM".
In any case, again I hope my comment doesn't come aggressive or showing any undermining the great effort on this project.
If Django gets supported, I'll be happy to do beta testing on some of my projects.
I hope to see more resources and support from cockroachlabs into such feature/problem.

@Alir3z4 I have an initial version of a Django backend that is doing some slight modifications on top of the Postgres backend. You can find that backend here: https://github.com/cockroachlabs/cockroach-django I was able to complete the initial tutorial with this backend. Let me know if you run into any issues. Thanks!

@rkruze Great job. I tried it on one small project and except one refactoring it works great and one issue. https://github.com/cockroachlabs/cockroach-django/issues/1
Since you cannot nest transaction.atomic and I like to use those as if they should go out of style I think I would encounter those many more times in something bigger.

This can be closed in favor of https://github.com/cockroachdb/cockroach-django.

@timgraham Yep, we can close this PR in favor of the other repo
We should also think about whether it makes sense to continue to have this cockroachdb-python package that has all-in-one cockroach support or if it should be renamed cockroach-sqlalchemy. The original idea was all-in-one but now that seems like it just makes dependencies messier (and it seems unlikely that there would be code sharing between cockroach-django and cockroach-sqlalchemy)

(+1 for renaming this repo to cockroach-sqlalchemy, imo it makes sense to keep them explicitly separate.)

Hey @bdarnell , I've been looking at your approach for achieving compatibility with django and I think it can be applied for another 'newsql' db. Would you be interested in checking this out?


Unable to deploy Databricks Asset Bundle from Azure DevOps pipeline via Workflow Identity Federation

Describe the issue
I want to deploy a Databricks Asset Bundle from an Azure Pipeline using databricks cli. While authentication for the cli itself seems to work, the actual deployment does not. It appears that the underlying Terraform provider is not able to authenticate.
The issue in particular appears to arise from our DevOps service connection. The service connection is configured for Workload Identity Federation. When I try an old service connection that authenticates using client credentials, the deployment succeeds.
I suspect the bug may be fixed by simply upgrading the version of Terraform that databricks cli uses under the hood. Currently it uses Terraform 1.5.5. Newer versions of Terraform seems to support the Workload Identity Federation flow. See https://developer.hashicorp.com/terraform/language/settings/backends/azurerm, but note how version 1.5.x of that same page makes no mention of Workload Identity Federation.
Relevant documentation:

https://devblogs.microsoft.com/devops/introduction-to-azure-devops-workload-identity-federation-oidc-with-terraform/
https://devblogs.microsoft.com/devops/public-preview-of-workload-identity-federation-for-azure-pipelines/
https://developer.hashicorp.com/terraform/language/v1.5.x/settings/backends/azurerm

Configuration
# azure-pipelines.yml
variables:
  databricksHost: "https://adb-XXX.azuredatabricks.net"

pool:
  vmImage: "ubuntu-latest"

jobs:
  - job: databricks_asset_bundle
    displayName: "Deploy Databricks Asset Bundle"
    steps:
      - bash: |
          # Install Databricks CLI - see https://learn.microsoft.com/en-us/azure/databricks/dev-tools/ci-cd/ci-cd-azure-devops
          curl -fsSL https://raw.githubusercontent.com/databricks/setup-cli/main/install.sh | sh

          # Verify installation
          databricks --version

          # Create databricks config file
          file="~/.databrickscfg"

          if [ -f "$file" ] ; then
              rm "$file"
          fi

          echo "[DEFAULT]" >> ~/.databrickscfg
          echo "host = $databricksHost" >> ~/.databrickscfg
        displayName: Setup Databricks CLI
      - task: AzureCLI@2
        displayName: Deploy Asset Bundle
        inputs:
          azureSubscription: "my-workload-identity-federation-service-connection"
          addSpnToEnvironment: true
          scriptType: "bash"
          scriptLocation: "inlineScript"
          inlineScript: |
            # As described in https://devblogs.microsoft.com/devops/public-preview-of-workload-identity-federation-for-azure-pipelines/
            export ARM_CLIENT_ID=$servicePrincipalId
            export ARM_OIDC_TOKEN=$idToken
            export ARM_TENANT_ID=$tenantId
            export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
            export ARM_USE_OIDC=true

            # Databricks authentication itself works fine
            echo ------------- List experiments -------------
            databricks experiments list-experiments

            # But bundle deployment does not
            echo ------------- Deploy bundle -------------
            databricks bundle deploy --log-level=debug --target dev

I have tried various combinations of the ARM_ environment variables above, but I couldn't find a working combination.
What did work was using a service principal service connection, in combination with:
          addSpnToEnvironment: true
          inlineScript: |
            export ARM_CLIENT_ID=$servicePrincipalId
            export ARM_TENANT_ID=$tenantId
            export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
            export ARM_CLIENT_SECRET=$servicePrincipalKey

# databricks.yml
bundle:
  name: my_project

variables:
  service_principle:
    description: Service principle used by the DevOps agent
    default: my-service-principle-id

run_as:
  service_principal_name: ${var.service_principle}

# Example resources to deploy
resources:
  experiments:
    my_experiment:
      name: "/Workspace/Users/${var.service_principle}/my_experiment"

targets:
  dev:
    mode: production
    default: true
    workspace:
      host: https://adb-XXX.azuredatabricks.net

Steps to reproduce the behavior

Create a DevOps service connection with Workflow Identity Federation
Create an Azure Pipeline with above yml (replace placeholders), using the service connection from 1)
Create Databricks Asset Bundle with above above yml (replace placeholders)
Trigger pipeline
Observe error

Expected Behavior
The deployment of the asset bundle should succeed.
Actual Behavior
The following error appears in the pipeline's log:
------------- Deploy bundle -------------
2024/08/27 08:40:59 [DEBUG] GET https://releases.hashicorp.com/terraform/1.5.5/index.json
2024/08/27 08:40:59 [DEBUG] GET https://releases.hashicorp.com/terraform/1.5.5/terraform_1.5.5_SHA256SUMS.72D7468F.sig
2024/08/27 08:40:59 [DEBUG] GET https://releases.hashicorp.com/terraform/1.5.5/terraform_1.5.5_SHA256SUMS
2024/08/27 08:40:59 [DEBUG] GET https://releases.hashicorp.com/terraform/1.5.5/terraform_1.5.5_linux_amd64.zip
Uploading bundle files to /Users/***/.bundle/my_project/dev/files...
Deploying resources...
Updating deployment state...
Deployment complete!
Error: terraform apply: exit status 1

Error: cannot create mlflow experiment: failed during request visitor: default auth: azure-cli: cannot get access token: ERROR: Please run 'az login' to setup account.
. Config: host=https://adb-XXX.azuredatabricks.net,/ azure_client_id=***, azure_tenant_id=XXX. Env: DATABRICKS_HOST, ARM_CLIENT_ID, ARM_TENANT_ID

  with databricks_mlflow_experiment.main,
  on bundle.tf.json line 17, in resource.databricks_mlflow_experiment.main:
  17:       }

Note that the listing of experiments works fine:
------------- List experiments -------------
[
   (expected list of experiments, redacted)
  {
      ...
  },
  ...
]

OS and CLI version
Output by the Azure pipeline:
azure-cli                         2.63.0

core                              2.63.0
telemetry                          1.1.0

Extensions:
azure-devops                       1.0.1

Dependencies:
msal                              1.30.0
azure-mgmt-resource               23.1.1

Databricks CLI: v0.227.0
OS: Ubuntu (Microsoft-hosted agent, latest version)
Is this a regression?
I don't know, I'm new to Databricks.
Debug Logs
See attachment.
debug_logs.txt

Also it seems to be related to this feature request https://github.com/databricks/databricks-sdk-go/issues/495

@Pim-Mostert what is surprising is that CLI commands work for you, could you try to run this command with --log-level TRACE flag and provide an output?
 databricks experiments list-experiments --log-level TRACE

@andrewnester Sure:
2024-08-27T11:01:55.1358321Z ------------- List experiments -------------
2024-08-27T11:01:55.1480761Z 11:01:55  INFO start pid=1874 version=0.227.0 args="databricks, experiments, list-experiments, --log-level, TRACE"
2024-08-27T11:01:55.1486300Z 11:01:55 DEBUG Found bundle root at /home/vsts/work/1/s (file /home/vsts/work/1/s/databricks.yml) pid=1874
2024-08-27T11:01:55.1489766Z 11:01:55 DEBUG Apply pid=1874 mutator=load
2024-08-27T11:01:55.1494173Z 11:01:55  INFO Phase: load pid=1874 mutator=load
2024-08-27T11:01:55.1497169Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq
2024-08-27T11:01:55.1501801Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=EntryPoint
2024-08-27T11:01:55.1508168Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=scripts.preinit
2024-08-27T11:01:55.1512861Z 11:01:55 DEBUG No script defined for preinit, skipping pid=1874 mutator=load mutator=seq mutator=scripts.preinit
2024-08-27T11:01:55.1516555Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=ProcessRootIncludes
2024-08-27T11:01:55.1520538Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=ProcessRootIncludes mutator=seq
2024-08-27T11:01:55.1524682Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=VerifyCliVersion
2024-08-27T11:01:55.1528227Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=EnvironmentsToTargets
2024-08-27T11:01:55.1531938Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=InitializeVariables
2024-08-27T11:01:55.1541062Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=DefineDefaultTarget(default)
2024-08-27T11:01:55.1544626Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=LoadGitDetails
2024-08-27T11:01:55.1550812Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=PythonMutator(load)
2024-08-27T11:01:55.1554405Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=validate:unique_resource_keys
2024-08-27T11:01:55.1558241Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=SelectDefaultTarget
2024-08-27T11:01:55.1561794Z 11:01:55 DEBUG Apply pid=1874 mutator=load mutator=seq mutator=SelectDefaultTarget mutator=SelectTarget(dev)
2024-08-27T11:01:55.1566466Z 11:01:55 TRACE Loading config via environment pid=1874 sdk=true
2024-08-27T11:01:55.1569451Z 11:01:55 TRACE Loading config via resolve-profile-from-host pid=1874 sdk=true
2024-08-27T11:01:55.1573469Z 11:01:55 TRACE Attempting to configure auth: pat pid=1874 sdk=true
2024-08-27T11:01:55.1575987Z 11:01:55 TRACE Attempting to configure auth: basic pid=1874 sdk=true
2024-08-27T11:01:55.1579964Z 11:01:55 TRACE Attempting to configure auth: oauth-m2m pid=1874 sdk=true
2024-08-27T11:01:55.1582931Z 11:01:55 TRACE Attempting to configure auth: databricks-cli pid=1874 sdk=true
2024-08-27T11:01:55.1586293Z 11:01:55 DEBUG Running command: /usr/local/bin/databricks auth token --host https://adb-XXX.azuredatabricks.net pid=1874 sdk=true
2024-08-27T11:01:55.1708113Z 11:01:55 TRACE Attempting to configure auth: metadata-service pid=1874 sdk=true
2024-08-27T11:01:55.1708871Z 11:01:55 TRACE Attempting to configure auth: github-oidc-azure pid=1874 sdk=true
2024-08-27T11:01:55.1709975Z 11:01:55 DEBUG Missing cfg.ActionsIDTokenRequestURL, likely not calling from a Github action pid=1874 sdk=true
2024-08-27T11:01:55.1710641Z 11:01:55 TRACE Attempting to configure auth: azure-msi pid=1874 sdk=true
2024-08-27T11:01:55.1711667Z 11:01:55 TRACE Attempting to configure auth: azure-client-secret pid=1874 sdk=true
2024-08-27T11:01:55.1712348Z 11:01:55 TRACE Attempting to configure auth: azure-cli pid=1874 sdk=true
2024-08-27T11:01:55.1713620Z 11:01:55 DEBUG Running command: az account get-access-token --resource 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d --output json --tenant XXX pid=1874 sdk=true
2024-08-27T11:01:55.8769849Z 11:01:55  INFO Refreshed OAuth token for 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d for tenant XXX from Azure CLI, which expires on 2024-08-27 12:01:54.000000 pid=1874 sdk=true
2024-08-27T11:01:55.8777969Z 11:01:55 DEBUG Running command: az account get-access-token --resource https://management.core.windows.net/ --output json --tenant XXX pid=1874 sdk=true
2024-08-27T11:01:56.3681975Z 11:01:56  INFO Refreshed OAuth token for https://management.core.windows.net/ for tenant XXX from Azure CLI, which expires on 2024-08-27 12:01:51.000000 pid=1874 sdk=true
2024-08-27T11:01:56.3688434Z 11:01:56  INFO Using Azure CLI authentication with AAD tokens pid=1874 sdk=true
2024-08-27T11:01:57.6325404Z 11:01:57 DEBUG GET /api/2.0/mlflow/experiments/list
2024-08-27T11:01:57.6326186Z < HTTP/2.0 200 OK
2024-08-27T11:01:57.6326679Z < {
2024-08-27T11:01:57.6326983Z <   "experiments": [
2024-08-27T11:01:57.6327560Z <     {
                                    REDACTED
2024-08-27T11:01:57.6433239Z <     "... (5 additional elements)"
2024-08-27T11:01:57.6433371Z <   ]
2024-08-27T11:01:57.6433481Z < } pid=1874 sdk=true
2024-08-27T11:01:57.6433605Z [
2024-08-27T11:01:57.6433699Z   {
2024-08-27T11:01:57.6433962Z     "artifact_location":XXX
2024-08-27T11:01:57.6434160Z     "creation_time": XXX
2024-08-27T11:01:57.6434310Z     "experiment_id": XXX
2024-08-27T11:01:57.6434477Z     "last_update_time": XXX
2024-08-27T11:01:57.6434691Z     "lifecycle_stage": XXX
2024-08-27T11:01:57.6435001Z     "name": XXX
2024-08-27T11:01:57.6435201Z     "tags": [
2024-08-27T11:01:57.6435303Z       {
2024-08-27T11:01:57.6435453Z         "key": "mlflow.experiment.sourceName",
2024-08-27T11:01:57.6435772Z         "value": XXX
2024-08-27T11:01:57.6435968Z       },
2024-08-27T11:01:57.6436080Z       {
2024-08-27T11:01:57.6436193Z         "key": "mlflow.ownerId",
2024-08-27T11:01:57.6436341Z         "value": "587479253565293"
2024-08-27T11:01:57.6436459Z       },
2024-08-27T11:01:57.6436639Z       {
2024-08-27T11:01:57.6436756Z         "key": "mlflow.ownerEmail",
2024-08-27T11:01:57.6436923Z         "value": "XXX"
2024-08-27T11:01:57.6437069Z       },
2024-08-27T11:01:57.6437166Z       {
2024-08-27T11:01:57.6437299Z         "key": "mlflow.experimentType",
2024-08-27T11:01:57.6437433Z         "value": "NOTEBOOK"
2024-08-27T11:01:57.6437559Z       }
2024-08-27T11:01:57.6437654Z     ]
2024-08-27T11:01:57.6437763Z   },
                                ... REDACTED
2024-08-27T11:01:57.6483974Z ]
2024-08-27T11:01:57.6484127Z 11:01:57  INFO completed execution pid=1874 exit_code=0

Ah, I see, CLI auth works because it eventually configures to use azure-cli auth type and not OIDC one so it might be not what you expect anyway.
So to summarise:

to be able to use OIDC in Azure Pipelines change in Go SDK needs to be made hence this ticket
The issue that CLI authenticates with azure-cli type but bundles failed to do so is separate one and might be related to some miss on bundles side where we don't pass all necessary env variables. If this is an issue for you, please feel free to open a separate ticket for this in Databricks CLI repo.

Thank you!

It's not an issue for me right now, but I expect it will be in the near future (when my company disables the old service connection). I've opened a new issue: https://github.com/databricks/cli/issues/1722
Please let me know if you need more information.
Thanks!


[aes, pre_sca] Enable formal masking verification of AES with Alma

This PR adds a couple of support files and a how to for formal verifying the masking employed inside AES using the Alma tool.

Thanks @rswarbrick for approving this. I've fixed the remaining issues and will merge this once CI passes.


Improve documentation and examples 😎

Implement Help command
Include license (MIT)
Include contributing guidelines
Include contributing code of conduct

Fixes #4 and #7.


Intellisense ranking issue

VSCode Version: Code - Insiders 1.12.0-insider (31a5fb236ddeed969a0021a2f94e7695ffbfb66b, 2017-04-28T06:13:22.707Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

path-intellisense
christian-kohler
1.2.0

gitignore
codezombiech
0.5.0

bracket-pair-colorizer
CoenraadS
0.10.3

tslint
eg2
0.12.0

vscode-postfix-ts
ipatalas
1.3.0

Steps to Reproduce:

Using the postfix extension, entries are added to intellisense such as log
But ranking doesn't seem to order them correctly

I would expect log to be topmost, so I can just press enter without having to navigate the menu.

Turns out its a setting
"editor.snippetSuggestions": "inline"


Improvements to the analytic topology architecture

This is the url:https://osm-edge-docs.flomesh.io/docs/overview/about/

Thanks to the community for allowing suggestions, the OSM topology is attached to this page.
But without parsing the architecture, I couldn't get a clear understanding of the architecture.

ok，I have no questons, thanks!


Consumes

Which consumes do we need to include in the sim? Which TBC consumes stay?

Potions: change to being only usable once in combat (can use one just prior to combat start and another during combat)
https://wotlk.evowow.com/?items=0.1
Elixirs: can benefit from the mixology perk for alchemists
https://wotlk.evowow.com/?items=0.2
Flasks: can benefit from the mixology perk for alchemists
https://wotlk.evowow.com/?items=0.3
Food:
https://www.mmorpg.com/guides/70-80-food-buffs-2000117040
Drums: there's 2 new drums in wotlk that provide lesser versions of blessing of kings and mark of the wild (not stacking with the buffs themselves)
https://wotlk.evowow.com/?item=49633
https://wotlk.evowow.com/?item=49634
Weapon Imbues: no new weapon oils and stones, old oils & stonesare are set to work only on items of ilvl <165
https://wotlkdb.com/?item=22522
https://wotlkdb.com/?item=28421
https://wotlkdb.com/?item=23529
https://wotlkdb.com/?item=18262
Engineering: new gadgets attached to equipment glove rockets and frag belt, along with new explosives
https://wotlk.evowow.com/?spell=54998
https://wotlk.evowow.com/?spell=54793
https://wotlkdb.com/?items=7.2

Pet food option: https://www.wowhead.com/wotlk/item=43005/spiced-mammoth-treats

I am not sure if this is the right section for it (didn't find any other category) - but in the gem selection "nightmare tear" (+10 all stats; https://www.wowhead.com/wotlk/item=49110/nightmare-tear) , "enchanted tear" (+6 all stats; https://www.wowhead.com/wotlk/item=42702/enchanted-tear) and "enchanted pearl" (+4 all stats; https://www.wowhead.com/wotlk/item=42701/enchanted-pearl) are missing. please include these ones.

I am not sure if this is the right section for it (didn't find any other category) - but in the gem selection "nightmare tear" (+10 all stats; https://www.wowhead.com/wotlk/item=49110/nightmare-tear) , "enchanted tear" (+6 all stats; https://www.wowhead.com/wotlk/item=42702/enchanted-tear) and "enchanted pearl" (+4 all stats; https://www.wowhead.com/wotlk/item=42701/enchanted-pearl) are missing. please include these ones.

Those are included now. Thanks for the note!

Just missing new explosives now.


include DevExpress (.config) to mapping

According to your DevExtreme documentation I have to call
DevExpress.config({ defaultCurrency: 'EUR' });
for setting another default currency than USD.
Is it possible to include this DevExpress object in your angular 2 mappings?
It would be great if I can import it like
import { DevExpress} from 'devextreme-angular2';
and use it as described.
If this is not possible, how can I use it instead (Angular 2 with TypeScript)?

Hi,
Once we fix the #16 issue, it will be possible to import the config as follows:
import config from 'devextreme/core/config'

As a temporary workaround, you can declare the DevExpress namespace:
declare var DevExpress: any;

and use it as follows:
DevExpress.config({ defaultCurrency: 'EUR' });

Hi! Issue #16 has been fixed in 16.2.1-alpha.1. You can import parts of DevExtreme functionality as mentioned above:
import config from 'devextreme/core/config'

The whole modules structure can be found here


Release Paketo Dotnet Core buildpack

Release in the week of May 17th if relevant changes or dependency updates are merged.
What steps did you take to close this issue? What resources did you use? How long did you spend on this task this week? Answer in a comment.

Check this dashboard to see whether there are un-released commits on any of the implementation buildpacks in this language family
Cut releases of implementation buildpacks that have feature additions or dependency updates
Trigger the Update buildpacks workflow in the language family buildpack to pull in the newly cut versions
Release language family buildpack

Released v0.3.0


How to eliminate false detection in “multi_hand_tracking_mobile_gpu”？

I made an app to recognize five gestures, such as "1", "2", "3", "4" and "5". In the video links are as follows, when there is no hand in the field of vision, there are landmarks detected constantly.
If coincidentally, the detected gesture (false detection) matches the gesture "Five", which will lead to wrong recognition. Regardless of real-time performance, can we detect three times and all three times are the same gesture? And then finally confirm, or what better way? The video links are as follows
https://youtu.be/cSLpG43Csoo

Hi, I'm not able to open your linked video. But you are right, there're definitely certain cases trigger false positive detections.
What you described makes sense, but more in a temporal way, e.g. if 3 or more consecutive frames returns the same gesture then it'll be output?


TPCC docs update with proper scsi reference

The Tpcc benchmark white paper https://www.cockroachlabs.com/guides/cockroachdb-performance/ and https://www.cockroachlabs.com/docs/stable/performance-benchmarking-with-tpc-c.html
specifying the scsi option for SSD use
https://cloud.google.com/compute/docs/disks/local-ssd#create_local_ssd
as a few customers had mistakingly picked incorrect NVM-e drivers and had poor results.
https://cloud.google.com/compute/docs/disks/performance#optimize_local_ssd
as not all customers will use roachprod.

@drewdeally, recreated this issue in the docs repo.


Failed to refresh token: 401

After running soft for 15 minutes getting this error:
Failed to refresh token: 401
How should I fix it?

same

check your session, it may be revoked or duplicated


Adopt/fork signalr-client dependency

The dependency singalr-client, which is vital to this project seems to be abandoned. It would be best to take over maintenance if possible of create a fork with necessary fixes (i.e. bug #8)

I am interested in doing this -- are you in contact with the project maintainer? Or do you suggest just forking and start maintaining the fork?

@themagicmountain I have sent him an email, but never heard back. I'll try to follow up on that and will update this issue.


Add --imports flag

Resolves issue #6
New flag --imports
Bumps goblin to v0.4.3
Uses [patch] to pull in the GitHub-hosted checksec for compatibility with goblin v0.4.3
Refactors handling of Multi-Arch Mach-O binaries

Thanks for the thorough feedback @tnballo!
Since we can't publish these changes until checksec is updated, I will work on the improvements you've suggested and any others that I that come up while I'm going back over the code.
Todos:

[ ] Use Rust Default trait in Import struct
[ ] Pass usize by value
[ ] Better use of goblin constants (replacing magic numbers / hex codes)
[ ] Improve output (alphabetical, consistent formatting, etc)

Sounds great @d3vco , thanks! Looking forward to merging whenever ready and pushing to crates.io ASAP.
Have opened a PR on the checksec repo to hopefully unblock us on that front.

@tnballo , I have completed all of my todos, so I will (try to) stop making new changes at this point. Happy to update / optimize anything you find in your review.

It's now pushed to crates.io :tada:
Thanks again, I think the --imports flag will be handy for many people!


Add support for ppc64le architecture

bootc-image-builder lacks support for ppc64le.
This two patch series adds such support.

Update manifestForDiskImage to include support for ppc64le architecture
Update partition table map with ppc64le specific data

Signed-off-by: Sachin Sant<EMAIL_ADDRESS>

Thank you for this PR! It seems we need to do a bit of work on our side first before this works. I tried the following to test it:
diff --git a/test/test_build.py b/test/test_build.py
index da27fbc..337b51f 100644
--- a/test/test_build.py
+++ b/test/test_build.py
@@ -285,6 +285,7 @@ def build_images(shared_tmpdir, build_container, request, force_aws_upload):
             *upload_args,
             *target_arch_args,
             "--local" if local else "--local=false",
+            "--rootfs", "ext4",
         ])

         # print the build command for easier tracing
diff --git a/test/testcases.py b/test/testcases.py
index e5b1f6a..81335f3 100644
--- a/test/testcases.py
+++ b/test/testcases.py
@@ -52,6 +52,8 @@ def gen_testcases(what):
             # todo: add fedora:eln
             test_cases.append(
                 f'{CONTAINERS_TO_TEST["centos"]},raw,arm64')
+            test_cases.append(
+                'quay.io/sacsant/fedora-bootc:latest,raw,ppc64le')
         elif platform.machine() == "arm64":
             # TODO: add arm64->x86_64 cross build test too
             pass
diff --git a/test/vm.py b/test/vm.py
index 1bb21f5..2297ed7 100644
--- a/test/vm.py
+++ b/test/vm.py
@@ -134,6 +134,11 @@ class QEMU(VM):
             ]
             if use_ovmf:
                 qemu_cmdline.extend(["-bios", find_ovmf()])
+        elif self._arch in ("ppc64le"):
+            qemu_cmdline = [
+                "qemu-system-ppc64le",
+                "-M", "pseries",
+            ]
         else:
             raise ValueError(f"unsupported architecture {self._arch}")

and when running the test with:
$ sudo pytest  -s -vv ./test/test_build.py::test_image_boots[quay.io/sacsant/fedora-bootc:latest,raw,ppc64le]
...
panic: required mounts for bootupd stage [/boot/efi] missing

goroutine 1 [running]:
github.com/osbuild/images/pkg/manifest.(*RawOSTreeImage).addBootupdStage(0xc00052a7e0, 0xc0007d0938)
	/root/go/pkg/mod/github.com/osbuild/images@v0.61.0/pkg/manifest/raw_ostree.go:127 +0x2a5
....

so our "images" code is not flexible enough right now to handle a scenario without a /boot/efi .

Wonderful, it seems like https://github.com/osbuild/images/pull/758 has landed so the panic() I saw in the previous run is fixed.

Wonderful, it seems like osbuild/images#758 has landed so the panic() I saw in the previous run is fixed.

Yes, yoheiueda mentioned about this PR. Some more changes related to bootupd is also required. Working on them.

Some more changes related to bootupd is also required. Working on them.

Currently we do have bootupd enabled on Fedora CoreOS derivatives for ppc64le as far as I know; there were bootupd specific interactions you were seeing with bib here?

Some more changes related to bootupd is also required. Working on them.

Currently we do have bootupd enabled on Fedora CoreOS derivatives for ppc64le as far as I know; there were bootupd specific interactions you were seeing with bib here?

The last missing piece from bootc perspective is bootupd related code for bootloader install.
From bootc/lib/src/install.rs:1210
crate::bootloader::install_via_bootupd(&rootfs.device, &rootfs.rootfs, &state.config_opts)?;
rootfs.device passed to install_via_bootupd points to base device/disk (e.g /dev/sdb ). For ppc64le grub2-install requires PReP boot partition which is typically the first partition on device (eg /dev/sdb1) so instead of base device pass the prep-boot partition value. Something similar to https://github.com/coreos/bootupd/blob/6a4fc6f8758ff18432d5a43995b8f53ad79d4419/src/bios.rs#L42

but why 😱 did someone pick dos format for aarch64? We need to follow that up separately.

:arrow_right: https://github.com/osbuild/bootc-image-builder/issues/551

Looks sane to me offhand.
Though I just now realized...you presumably copied the dos partition table layout from the aarch64 one...but why 😱 did someone pick dos format for aarch64? We need to follow that up separately.

I followed the code in images repository https://github.com/osbuild/images/blob/main/pkg/distro/fedora/partition_tables.go#L109

(Also, again not a new problem, but this code rather desperately needs some documented const for some of these values...but again, can be a followup)

Rebased the branch.
Let me know if there are any review comments on this PR.


adding healthcare extension with sdk

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/Azure/azure-cli-extensions.git@adding-heatlhcare#subdirectory=src/$EXT&egg=$EXT"

merging 1st release, more changes will come by the end of this week


bump audio version to v8 from v4

Bumps audio websocket protocol from v4 to v8. Required going forward from November 18th.
Code change checklist

[x] I have ensured that all methods and functions are fully documented using doxygen style comments.
[x] My code follows the coding style guide.
[x] I tested that my change works before raising the PR.
[x] I have ensured that I did not break any existing API calls.
[x] I have not built my pull request using AI, a static analysis tool or similar without any human oversight.

Unit tests pass, no further adjustment is required at this time beyond our already existing support for XChaCha20.


Make IsZero take the entire PageMeta into account

I can't see where set is filled out (for example), by DecodeBuildConfig, which makes me suspect that IsZero is returning true in pageMeta.applyDefaultValues when it shouldn't.
All tests still passed with this change, but I'm not entirely sure where the right place to add a test would be.

... nevermind, I figured it out -- defaultBuildConfig is further filled in by WeakDecode, not overwritten.
Closing.


Quickstart db create not creating all the tables

When running the db create command it responds saying the database is created and the version table is created (the base table), but the rest of the tables were not created. Am I missing something, because it just used the base generator which should set up the project for me correctly.
Any guidance would be appreciated.

db create does only that, and a separate command db migrate is for running all migration files.

I added hints to quickstart to make it clearer.


Fix tests with serde >= 1.0.196

In serde 1.0.196, the "invalid type" error message for floats started
adding a trailing ".0" if no decimal point was already part of the
formatted float, causing tests to fail like:
---- test_chrono_timestamp_seconds_with_frac stdout ----

error: expect test failed
   --> serde_with/tests/chrono_0_4.rs:551:9

Expect:
----
invalid type: floating point `0`, expected a string at line 1 column 3
----

Actual:
----
invalid type: floating point `0.0`, expected a string at line 1 column 3
----

Change the tests to use a test value of 0.1, so the test will work both
pre- and post-serde 1.0.196.

Thanks for the contribution.


HCW-98: Logging and API Gateway

HCW Deployment is showing as failing because the integration tests directory doesn't exist in this PR (added in https://github.com/NHSDigital/healthcare-worker-api/pull/16). I've run a manual test with postman pointing at https://internal-dev.api.service.nhs.uk/healthcare-worker/pr-8/Worker?identifier=1 and it's returning as expected. So I'm confident that this is working correctly.
Merging before review to get a solid base. Reviews can then continue from the closed PR or from develop itself.


[v.0.13] Release Tracker

We cut a release branch for the 0.13 release.
Our plan from this point from this point is roughly:

Phase 1 (until 06/13): work on finalizing the release branch
Phase 2 (after 06/13): perform extended integration/stability/performance testing based on Release Candidate builds.

This issue is for tracking cherry-picks to the release branch.
Cherry-Pick Criteria
Phase 1 (until 06/13/22):
Only low-risk changes may be cherry-picked from master:

Fixes to regressions against the most recent minor release (e.g. 0.12 for 0.13 release; see module: regression issue list)
Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
Fixes to new features introduced in the most recent minor release (e.g. 0.12 for 0.13 release)
Test/CI fixes
Documentation improvements
Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
Release branch specific changes (e.g. change version identifiers)

Any other change requires special dispensation from the release managers (currently @atalman, @seemethere ). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 06/13/22):
Note that changes here require us to rebuild a Release Candidate and restart extended testing (likely delaying the release). Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
Changes will likely require a discussion with the larger release team over VC or Slack.
Cherry-Pick Process

Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).

Create (but do not land) a PR against the release branch.

# Find the hash of the commit you want to cherry pick
# (for example, abcdef12345)
git log

git fetch origin release/0.13
git checkout release/0.13
git cherry-pick abcdef12345

# Submit a PR based against 'release/0.13' either:
# via the GitHub UI
git push my-fork

# via the GitHub CLI
gh pr create --base release/0.13

Make a request below with the following format:

Link to landed master PR (if applicable):
*

Link to release branch PR:
*

Criteria Category:
*

Someone from the release team will reply with approved / denied or ask for more information.
If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.

NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.
Please note HUD Link with branch CI status and link to the HUD to be provided here.
HUD
Versions
0.13

This is duplicate of #6081. Let's use the issue created originally by @NicolasHug.


not allow rtl language in dropdown

https://github.com/srtraj/dropdown_textfield/blob/1a24411cd04bd03c798bf355f5c7ee139c31185c/lib/dropdown_textfield.dart#LL1107C33-L1107C65
alignment: Alignment.centerLeft,

@MayHatuel Sorry for delayed reply, I was busy with other things and couldn't maintain this package. Added alignment based on rtl . Please check the latest release: dropdown_textfield version 1.1.0