[fix] fix etcd-backup-restore based flavors

What this PR does / why we need it:
CAPL clusterrs with etcd-backup-restore and related flavors fail to created. This is down to some recent OBJ changes for key names and namespaces within the secrets.

LGTM. Just a question @bcm820 for my understanding, the keys and bucket can be in different namespaces? From the PR I see, the secrets of type=addons.cluster.x-k8s.io/resource-set should always be created in namespace=kube-system. Was there any specific reason why it was removed in the first place?

LGTM. Just a question @bcm820 for my understanding, the keys and bucket can be in different namespaces? From the PR I see, the secrets of type=addons.cluster.x-k8s.io/resource-set should always be created in namespace=kube-system. Was there any specific reason why it was removed in the first place?

That is hard-coded because that secret is only meant for backup-restore and the backup-restore pod is hardcoded to be in the kube-system namespace


Actually remove old event listeners

eventListener creates a new reference (that's why it's in Effect), distinct from old ones, so we need to store the result of that instead of the callback we passed to it

Example to reproduce it with:
D.button
  ((D.OnClick := _) <<< (log :: String -> Effect Unit) <$>
    oneOfMap bang ["You should", "only see", "this last one"]
  )
  [ text_ "Useless machine" ]

Thanks @MonoidMusician !


Fix fee for GLMR

Source :
https://github.com/PureStake/moonbeam/blob/master/runtime/moonbeam/src/lib.rs#L303
pub const TRANSACTION_BYTE_FEE: Balance = 1 * GIGAWEI * SUPPLY_FACTOR;

pub const GIGAWEI: Balance = 1_000_000_000;

pub const SUPPLY_FACTOR: Balance = 100;

fn polynomial() -> WeightToFeeCoefficients<Self::Balance> {
		smallvec![
			WeightToFeeCoefficient {
				degree: 1,
				coeff_frac: Perbill::zero(),
				coeff_integer: currency::TRANSACTION_BYTE_FEE,
				negative: false,
			},
			WeightToFeeCoefficient {
				degree: 3,
				coeff_frac: Perbill::zero(),
				coeff_integer: 1 * currency::SUPPLY_FACTOR,
				negative: false,
			},
		]

1 * 100^3 = 1_000_000
1 * 1_000_000_000 * 100 = 100_000_000_000

final_coefficient =<PHONE_NUMBER>00000000

Can't use standard type of fee calculation as it still unresolve for iOS:
https://app.clickup.com/t/2vcckpx

Was decided to change on standard type


Support for using

/// These callbacks are used to return multiple types from functions while
/// transferring ownership to the caller. The first argument is the number of
/// consecutive elements pointed to by the second argument. The third argument
/// is an opaque pointer forwarded to the callback by the caller.
using MlirTypesCallback = void (*)(intptr_t, MlirType *, void *);

Lead to:
/home/vchuravy/.julia/artifacts/c90711842814121dacf839a59bca4c40f573cbff/include/mlir-c/Interfaces.h:51:1: error: unknown type name 'using'
/home/vchuravy/.julia/artifacts/c90711842814121dacf839a59bca4c40f573cbff/include/mlir-c/Interfaces.h:51:27: error: expected expression
/home/vchuravy/.julia/artifacts/c90711842814121dacf839a59bca4c40f573cbff/include/mlir-c/Interfaces.h:60:45: error: unknown type name 'MlirTypesCallback'

using MlirTypesCallback = void (*)(intptr_t, MlirType *, void *);
it looks like this is C++.

I see I will need to grumble at upstream for putting that into a C header

Is there a way to work around this in Clang.jl?

closed by #480, #432, #435


Extra: Add new PreparedSQLPlaceholders sniff

WordPress 4.8.2 introduced a security fix which removed an undocumented, but well used feature in the $wpdb->prepare() method.
Officially only the %s, %d and %f placeholders were supported.
In reality, most forms of sprintf() type placeholders formats were supported before WP 4.8.2.
See: https://core.trac.wordpress.org/changeset/41496
This already has caused havoc, breaking big plugins like Yoast SEO and WordFence.
This new sniff will check that $wpdb->prepare() is used correctly by checking for the following issues:

Are only the following placeholders used ? %d, %f (%F) and %s.
Are literal % signs properly escaped ?
Are placeholders left unquoted in the query string ? (as they should be)
Is the correct number of replacement variables passed ?

Includes unit tests.
The sniff has been added to the Extra ruleset, though it could be argued that it should be added to Core as most of the above points are already in the handbook.
Refs:

https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/
https://developer.wordpress.org/reference/classes/wpdb/prepare/
https://github.com/Yoast/wordpress-seo/issues/7886
https://wordpress.org/plugins/wordfence/#developers (see changelog for 6.3.19)
https://core.trac.wordpress.org/ticket/41925

Additional notes:
The is_wpdb_method_call() method has been moved from the PreparedSQL sniff to the WP base Sniff to enable this sniff to use it as well.
Additionally, the re-usability and stability of the is_wpdb_method_call() method has been improved:

Add recognition of static function calls using :: operator.
Pass the methods to check for via a property to allow for child classes to be more flexible.
Only set the properties if such a property exists in the child class.
Don't sniff the method during live coding, i.e. when no close parenthesis is found yet.

Includes unit tests.

Related: #641 :smile:

You know what ? Looking at that issue and at the handbook, let's just go ahead and add this sniff to Core instead of to Extra.

Just for the fun of it, ran this sniff over core: result:

2 false positives for wrong replacement number (rare cases, but may need a whitelist flag)
6 quoted placeholders: https://core.trac.wordpress.org/ticket/41983

Oh and found a bug... let me fix that...

I have reported some (non-security) issues this sniff identified to bbPress and Yoast SEO as well.
Would @Ipstenu, @Otto42or @grappler be interested in running it over the whole plugin/theme repo ?

I think it would be interesting to run on all of the themes but I don't expect many issues as there is no need to for most themes to run direkt MYSQL.

In relation to the issues I opened in Trac - it turns out the documentation of the wpdb::prepare() and the wpdb_esc_like() methods may need to be updated to improve the information on using a literal % in combination with LIKE in queries.
If that yields the need for changes in this sniff, I will address that ASAP, preferably before the 0.14.0 release.
Ref: https://core.trac.wordpress.org/ticket/41983#comment:3


Update New-AutoSensitivityLabelPolicy.md

filling in missing info

Docs Build status updates of commit b31ea1d:
:clock10: Full build: the average full build time is 17 min(s) 34 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b31ea1d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 66ba358:
:clock10: Full build: the average full build time is 17 min(s) 34 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 66ba358:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Question about FDT

Thanks for this amazing tool, FDT.
I wonder some points.

When I transfer a huge file (over 1T). In this case, Still FDT use a multi-thread? in my case, I cannot get any speed-up.
When re-transmit it, It is super-faster than rsync. even if I deleted legacy file that already transferred. Is it cached? or How is it possible?

Hello,
For question 1, it transfers all files by byte range so it does not matter what file size is (almost), you could try to increase threads count by setting parameter -P 20 (to have 20 threads)
For question 2, we do not cache data but could you describe more your scenario? If file is already present it could be jus skipped if meta data is same.


请问生成的量化onnx用netron打开，为什么不会显示视频中的量化算子

这跟您选择的导出平台有关，如果您选择了Onnxruntime作为导出平台，他会导出带QDQ节点的模型。
其余平台在推理时全部不使用OnnxQDQ节点传递量化信息，它们使用json。因此你会得到一个fp32的onnx文件，以及一份带有量化信息的json文件。
推理框架会读取这个json，并将fp32的onnx文件转换为int8的

[06/02/2023-17:05:20] [TRT] [W] Calibrator is not being used. Users must provide dynamic range for all tensors that are not Int32 or Bool.
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 458) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 459) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 461) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 462) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 465) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 466) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 468) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 469) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 916, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 472) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 474) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 918, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 477) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 478) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 924, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 931, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 543) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 544) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 546) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 547) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 550) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 551) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 553) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 554) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 975, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 557) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 559) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 977, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 562) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 563) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 983, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 990, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 628) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 629) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 631) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 632) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 635) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 636) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 638) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 639) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1034, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 642) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 644) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1036, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 647) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 648) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1042, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1049, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 700) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 701) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 703) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 704) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 706) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 707) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 709) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 710) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1093, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 712) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 714) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1095, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 716) [Constant]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor (Unnamed Layer* 717) [Shuffle]_output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1101, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor 1108, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
[06/02/2023-17:05:20] [TRT] [W] Missing scale and zero-point for tensor output, expect fall back to non-int8 implementation for any layer consuming or producing given tensor
generate /root/ppq/working/int8-trt.engine
请问上述的warning是啥意思？  最终生成的int8-trt.engine能够推理，且和trtexec生成fp16的engine速度差不多； 是已经转换成功了吗？

是的，你已经转换成功了，你的模型结构可能比较复杂，对于一个复杂的模型而言，并不是所有算子都是可以量化的。
在PPQ中，我们实现了一系列调度器，它们负责找出模型中那些算子可以被量化，其余的算子将保持fp32精度参与运算。
你可以运行这样的语句：
for op_name, op in graph.operations.items():
print(op_name, op.platform)
该语句将打印算子调度信息，您可以检查调度情况是否符合预期。
您也可以参考这个例子手动修改调度信息：
https://github.com/openppl-public/ppq/blob/master/ppq/samples/Yolo/yolo_5.py

非常感谢大佬认真回答！

非常感谢大佬认真回答！


code source location incompatibilites with quilt-loader 0.18.1-beta+

    public static URI getURI(final Class<?> clazz) throws URISyntaxException {
        return clazz.getProtectionDomain().getCodeSource().getLocation().toURI();
    }

    public static Path getPath(final Class<?> clazz) throws URISyntaxException {
        final URI uri = getURI(clazz);
        System.out.println("URI: " + uri);
        return Paths.get(getURI(clazz));
    }

final byte[] bytes = Files.newInputStream(getPath(Example.class)).readAllBytes();
System.out.println("length: " + bytes.length);

URI: quilt.mfs://example.jar.i0:0/
java.nio.file.FileSystemException: Cannot open an InputStream on a directory!
	at org.quiltmc.loader.impl.filesystem.QuiltMemoryFileSystemProvider.newInputStream(QuiltMemoryFileSystemProvider.java:169)
	at java.base/java.nio.file.Files.newInputStream(Files.java:160)

This isn't the only usage of code source URIs that no longer works with the latest quilt loader betas but I don't have any stack traces for the other incompatibilities yet.
If you know a better way to find the location of a jar file containing a class file that works on quilt, fabric, forge (legacylauncher and modlauncher), paper, and sponge that would be just as good as a solution inside of the quilt itself.

Are you needing access to your mod jar or something else? For mod jars, you can get their root paths from the ModContainer


FloatField use NumberInput by default

FloatField should use NumberInput #677

Hi @Demetriex , this looks good! A couple things to add perhaps is:
Add some tests verifying the behavior:

When the "step" property is not defined as "any" or a specific float, then the field doesn't pass validation for that specific float. The HTML input itself when calling input.checkValidity() wont report true unless its "any" or a specific float up to the defined precision, i.e - step="0.01" validates for "1.10" but not for "1.234"

I also left some comments on the changes for you to take a look at.


Generating out 'latest' and 'preview' profiles

Still to come is the snapshot profile which is supported in Stack
edit: Stack Profile 2017-03-09 has been added.

visualstudio package is missing in the preview profile (I don't know if there are more missing packages). Is the profile like that?

@mcardosos says:
visualstudio package is missing in the preview profile (I don't know if there are more missing packages). Is the profile like that?

Hmm, when I look in my Dev branch I see Visual Studio in the preview profile: ://github.com/marstr/azure-sdk-for-go/tree/dev/profiles/preview/visualstudio/mgmt/visualstudio
Is that the package you mean? Was there another one that was missing?

Sorry, I meant latest

Ahhhh! yes, that is by design. If you go look, visualstudio only has preview packages, which are filtered out of the the latest profile.

Ok ok. Only comment is I would explain what this profiles are

I'll address documentation concerns in future PRs. For now, I'm going to merge this in :)


Restructure account commands to account subcommand

Also edit the history count trigger so it only runs on insert, and not on delete. This will make sure that deletes run super fast 🚀

While this works as it did before, I realise that we don't count actual history delete requests here. Should we add a trigger on update? I think users might be confused if the remote count doesn't decrease when they delete

I wish :( If we actually update the remote count when rows are soft deleted, sync won't work. It's append-only, afterall, and expects counts to always increase

We should perhaps offset the deleted items from the remote count before displaying it though


App Crashes when calling alert.show() with or without any arguments

I added this to my project but cannot get it to work.  Everything I try calling any of the alert types I get Warning: Attempt to present <UIAlertController: 0x7fb50503ee00> on <UINavigationController: 0x7fb504017600> whose view is not in the window hierarchy!.  I got the example project working but it does not work in my project.  What am I doing wrong?
UPDATE: I have narrowed it down to alert.show() whenever it is called with or without args it causes this crash and error.

Could you send me an example project with a reproducible error?

I tried creating a simple example project with the same error doing it exactly how I did in my actual project but cannot seem to get it to reproduce the error.  I did get it to work in my project by replacing the alert.show() with self.present(alert, animated: true, completion: nil) but cannot reproduce the error.  What would you like me to do since I could not seem to make a reproduction of the error?

Well, without a reproducible example I won't be able to look into it. In any case, you may want to look into which view controller presents the alert. In case SwiftEntryKit's entry is being displayed, just make sure the sender is a view controller embedded in the entry so that the alert will be displayed in the proper window.
I'm closing this for now, but if you manage to reproduce the problem, just sample it and send it over.
Cheers.


Upgrade NodeJS to support >= v16

Older versions of node-sass are incompatible with newer versions of NodeJS and newer node-sass is conflicting with other required versions of node-sass. sass is a recommended replacement for node-sass to address these issues. See:
https://www.npmjs.com/package/node-sass
https://stackoverflow.com/questions/64625050/error-node-sass-version-5-0-0-is-incompatible-with-4-0-0
Description
Between NodeJS v14 and 15, many packages received maintenance updates, however, node-sass v4 became incompatible. It is recommended to instead use the sass package as a replacement.
Steps taken to perform the package upgrade

Using NodeJS v14: npm remove node-sass
Using NodeJS v16: npm i sass

Does this PR introduce a breaking change?

[ ] Yes
[x] No
It shouldn't.

Does this PR fix an open issue?

[x] Yes
[ ] No
Partially fixes https://github.com/unchained-capital/caravan/issues/225 This issue might still be present when node version is greater than 16.

Hell yeah. Good catch. Any chance you could put this on a branch of your repo that's not master so it's easier to test/verify locally. There might be some git-fu I'm unaware of to get around it but I don't know how to checkout the master branch of another remote.

@bucko13 If your fork is setup like mine, this is what I did to check it out locally:
git fetch upstream pull/279/head:pr-279
git checkout pr-279


Using OpenCV with jetson-inference

Hi,
I'm trying to use opencv to do inference on a trained model. I'm trying to pass in an image to the Detect method (in detectNet.cpp) and draw the bounding boxes on my Mat image. However, the Detect method takes in a float* as the image and I'm not sure how to format my Mat image so that it is a viable input. According to TensorRT documentation the image inputs should be in NCHW format (which is new to me), but when I try converting the images I consistently get errors like "cudaPreImageNetMean failed" or "tensorRT context failed". Could anyone provide some insight as to what I'm doing wrong, or if there's a better way to use OpenCV images for inference?

I managed to make it work. Let say cvImage is a 1920x1080 RGB uchar8 image. You first need to allocate memory on the GPU like this:
uchar3* imgBufferRGB = NULL;
float4* imgBufferRGBAf = NULL;
cudaMalloc((void**)&imgBufferRGB, 1920 * sizeof(uchar3) * 1080);
cudaMalloc((void**)&imgBufferRGBAf, 1920 * sizeof(float4) * 1080);

Then, you transfer the image to the GPU and convert it to RGBAf (because it is what detectnet takes as an input, it could be more efficient to modify detectNet.cpp and convert directly from uchar8 to TensorRT format).
 cudaMemcpy2D((void*)imgBufferRGB, 1920*sizeof(uchar3), (void*)cvImage.data, cvImage.step,
              1920*sizeof(uchar3), 1080, cudaMemcpyHostToDevice);
 cudaRGBToRGBAf(imgBufferRGB, imgBufferRGBAf, 1920, 1080); // defined in cudaRGB.h
 int numBoundingBoxes = maxBoxes;
 if (net->detect((float*)imgBufferRGBAf, 1920, 1080, bbCPU, &numBoundingBoxes, confCPU)) {
   printf("%i bounding boxes detected\n", numBoundingBoxes);
 }

I am pretty new du CUDA and the code may be inefficient but I hope it helps

@gariepyalex Hi,
Do you share your code entirely?

@gariepyalex can you share your code for how to use opencv

Sorry I can't share the code

Thank you， @gariepyalex . I did what you said, but the boundingbox is different from the result of the detect-console sample，and it doesn't make much difference. I read Mat to GPU memory.Can you help me ? Thank you!

hello, @gariepyalex  that was helpful. but I still need to convert back from float4 to Mat.
I tried to use the same way but with cudaRGVAfToRGB but it gives me errors .can you help me on it.
the error is this:
`
[cuda]   cudaGetLastError()
[cuda]      invalid pitch argument (error 12) (hex 0x0C)
[cuda]      /home/nvidia/Desktop/mod/jetson-inference/utils/cuda/cudaRGB.cu:136
OpenCV Error: Assertion failed (size.width>0 && size.height>0) in imshow, file /home/nvidia/build_opencv/opencv/modules/highgui/src/window.cpp, line 331
terminate called after throwing an instance of 'cv::Exception'
what():  /home/nvidia/build_opencv/opencv/modules/highgui/src/window.cpp:331: error: (-215) size.width>0 && size.height>0 in function imshow
Aborted (core dumped)
`


Planning for next models implementation

I have more time those days to review and upgrade my codes (kgcnn) now has 23 models implemented. I would like to see if we can find time to implement not all of them but max 5 of the best ones. what do you think ?
for ESOL:

for Fresolv:

By the way you can now only contact me using my gmail.com email I am moving to another company.
Please let me know your point of view on that.
Especially DGIN looks encouraging compare to GIN version and close to DMPNN.
thanks
Guillaume

Hi @thegodone, thanks for the info! :)
If time allows, I could look into the most promising/interesting ones. Not sure though who those are. Given DMPNN, AttentiveFP, GATv2, etc. are already implemented with molgraph, I wonder whether there are any other models worth implementing?
Have you tried the DMPNN or AttentiveFP of molgraph? How are they performing in comparison? (They might need some hyper-parameter fine-tuning or tweaks to perform well.)
Based on the paper I read on DGIN (think it was the original DGIN paper, but not sure), it did not seem particularly interesting to me.

To piggyback on this, I find CMPNN useful.


[Feature][DataX] Support OceanBase datasource in DataX task

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Adding support for OceanBase in DataX type tasks by introducing DataX OceanBase plugins.

https://github.com/alibaba/DataX/tree/master/oceanbasev10reader
https://github.com/alibaba/DataX/tree/master/oceanbasev10writer

Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

OceanBase datasource  template with dolphinscheduler


Added configuration key for Disable HTTPs check

When deploy to a private network, it's not necessary to use https. This helps the users to know how to do this.

Hi @ups216, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Very nice! Merged as 6e653392b922c4d9a1a7c0ca375d2e3c91231c7b


Inferred shape and existing shape differ error

All I did was converted a standard vgg16 prototxt and standard vgg caffemodel from caffe and then converted it to onnx using mmdnn and then tried to convert it to caffe2, but got following error while converting generated onnx model to caffe2.
File "/usr/local/lib/python3.5/dist-packages/onnx-1.2.3-py3.5-linux-x86_64.egg/onnx/backend/base.py", line 75, in run_model
backend = cls.prepare(model, device, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/caffe2/python/onnx/backend.py", line 713, in prepare
model = onnx.shape_inference.infer_shapes(model)
File "/usr/local/lib/python3.5/dist-packages/onnx-1.2.3-py3.5-linux-x86_64.egg/onnx/shape_inference.py", line 36, in infer_shapes
inferred_model_str = C.infer_shapes(model_str)
RuntimeError: Inferred shape and existing shape differ in rank: (2) vs (3)

Hi @vijay73anand, thank you for reporting but please make sure whether it is an issue related to caffe2. You can check whether the IR of MMdnn is correct by converting to other frameworks that MMdnn supports.


[Feature] Using CustomDataset in Nuscenes style - How to support NuScenes style evaluation ?

Custom Dataset Evaluation with NuScenes when certain dataset related jsons are non-existent
One of the ways to adapt our custom dataset into NuScenes style is by generating the middle format nuscnes_infos_train/val.trainval.pkl as expected for NuScenes. I have been succesful in doing that.
However, Evaluation on this custom Dataset is tricky as it compares predictions with GT from v1.0-trainval/sample_annotations.json which stores GT as translation:[], size:[] and rotation:[] unlike the 7DOF gt_bboxes that is available in infos.pkl
What is the best way to adapt evaluation on Nuscenes style infos.pkl with predictions?
Highlight:
context
Our custom dataset will not contain NuScenes like schema.

Have the same problem!

Any body has the same problem to align custom dataset as NuScenes schema ?


(GH-2384) Subsequent changes after #3552 Update resource names

Describe the changes you have made to improve this project
This PR fixes some changes from #3552. Additionally it renames some keys from this PR.

Remove the Metro suffix
Rename ButtonBase into Button only, because most of us uses the Button and not the ButtonBase /cc @Evangelink (I hope this is ok)
Rename Standard.VisualStudio into VisualStudio only
Minor fixes

Closed Issues
Closes #2384

We reviewed the other PR quite a lot but there are still quite a lot of things we missed :s


[Bug] — createUser method and email confirmations

Bug report
Describe the bug
Using the auth.api.createUser when email confirmations are disabled does not automatically confirm emails.
For instance, if you disable email confirmations and create a users via auth.api.createUser, the auth.users table will show the email_confirmed_at column as null and the supabase ui will show Waiting for verification..:

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Disable email confirmations
Create a user via auth.api.createUser
View the auth.users table
Take a look at the email_confirmed_at column which will be null
Take a look at the supabase ui that shows users and you'll see the Last Sign In column show Waiting for verification..

Expected behavior
The expected behavior when creating a user while having email confirmations disabled is that the email_confirmed_at column on the auth.users table will be set to the time the user signed up and the supabase ui that shows users will have Last Sign In set to the time the user signed up.
This is how the behavior is when creating a user via auth.signUp

System information

OS: macOS
Version of supabase-js: [1.28.2]
Version of Node.js: [14.18.0]

Additional context
I also noticed that if you have email confirmations enabled and a user is created via  auth.api.createUser, no email confirmation is sent.

So i did a bit of investigating and here's what I was able to come up with. When using the auth.api.createUser, it calls the gotrue api, specifically the admin/users POST endpoint.
This in turn calls the [adminUserCreate(https://github.com/supabase/gotrue/blob/master/api/admin.go#L176) method which does a number of things. What's important in regards to this issue is that it:

grabs the params here
grabs the config here

Now after the new user is written to the table, there are a number of checks. One of which is:
if params.EmailConfirm {
	if terr := user.Confirm(tx); terr != nil {
		return terr
	}
}

I beleive this is where the issue exists. params.EmailConfirm will always be null. When we grab the params mentioned above, what's happening is that we decode the request body. But the request body only allows UserAttributes defined as such:
export interface UserAttributes {
  /**
   * The user's email.
   */
  email?: string
  /**
   * The user's password.
   */
  password?: string
  /**
   * An email change token.
   */
  email_change_token?: string

  /**
   * A custom data object. Can be any JSON.
   */
  data?: object
}

One solution is to add a check against the config we grab if AutoConfirm is enabled. This is reflective of the behavior of the auth.signUp API which ultimately calls the signup POST endpoint on the gotrue server.
After a user is created with the signup endpoint, there are checks against the config on to whether or not the user should be confirmed. This can be seen here:
if params.Provider == "email" && !user.IsConfirmed() {
	if config.Mailer.Autoconfirm {
		if terr = models.NewAuditLogEntry(tx, instanceID, user, models.UserSignedUpAction, nil); terr != nil {
			return terr
		}
		if terr = triggerEventHooks(ctx, tx, SignupEvent, user, instanceID, config); terr != nil {
			return terr
		}
		if terr = user.Confirm(tx); terr != nil {
			return internalServerError("Database error updating user").WithInternalError(terr)
		}
        ....
}

If this appears to be the right path, I'm happy to stab at creating a PR!

Want to also say that this is an issue for me too and I think a PR to fix this would be a great idea!

Hello, it seems to be  fixed ;) : https://github.com/supabase/supabase/issues/4268


Clustering geojson data using PruneCluster and Angular Leaflet Directive

I am trying to cluster geojson data using PruneCluster and the Angular leaflet directive. However, my code does not display the clusters and there are no errors in the console to help in troubleshooting. Below is the code for my controller:
angular.module('bizvizmap').controller('controller', [
	'$scope', '$http', '$filter', 'leafletData',
	function ($scope, $http, $filter, leafletData){
	$scope.center = {
        lat: 39.5500507,
		lng: -105.7820674,
		zoom: 4
            },
	$scope.defaults = {
		scrollWheelZoom: false
			},
	$scope.events = {
			map: {
			enable: ['zoomstart', 'drag', 'click', 'mousemove'],
			logic: 'emit'
			}
			},
    $scope.layers = {
            baselayers: {
            osm: {
            name: 'OpenStreetMap',
            url: 'http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png',
			type: 'xyz'
                    }
                },
			markers:{}
	},
	$scope.map = null;
	leafletData.getMap("bizvizmap").then(function(map){
		$scope.map = map;
	});
	function renderMarkers(data, map){
		var markerLayer = new PruneClusterForLeaflet();
		for (var i=0; i < data.length; i++){
			var marker = new PruneCluster.Marker(data[i].geometry.coordinates[1], data[i].geometry.coordinates[0]);
			markerLayer.RegisterMarker(marker);
		}
		map.addLayer(markerLayer);
		markerLayer.ProcessView();
	}
	$scope.geojson = {};
	$http.get('data/bizvizmap.geojson').success(function (data){
			$scope.data = data;
			// Render clustered markers
			renderMarkers(data, $scope.map);
		});
]);

Any help is highly appreciated.

Hi, can you share your geojson file? Your source code looks fine.

Here is part of the geojson file:
{"type":"FeatureCollection","features":[{"type":"Feature","properties":{"Name":"Drummond Co Inc","Address":"1000 Urban Center Dr Ste 300","City":"Birmingham","State":"AL","Phone":"(205) 945-6300","County":"Jefferson","Latitude":"33.48360731","Longitude":"-86.70488291","BusinessDescription":"Coal & Other Minerals & Ores - Wholesale","SIC":"5052001","SICDescription":"Coal & Other Minerals & Ores - Wholesale","NAICS":"423520","NAICSDescription":"Coal and Other Mineral and Ore Merchant Wholesalers","Website":"www.drummondco.com"},"geometry":{"type":"Point","coordinates":[-86.70488291,33.48360731]}}]}

Isn't just that you don't access to the features list in the GeoJson document?
Could you try to replace renderMarkers(data, $scope.map); by renderMarkers(data.features, $scope.map); ?

Thanks. Its working now.


Tabbing with highlighted code ignores tab preference

VSCode Version: 1.2.1
OS Version: OS X 10.11.5

Steps to Reproduce:

Settings:
{
  "editor.tabSize": 2,
  "editor.wrappingColumn": 0,
  "editor.renderWhitespace": true,
  "files.trimTrailingWhitespace": true
}

@blakeembrey When the selection is a single line selection the text will be replaced with a \t. Otherwise there would be absolutely no way to insert a Tab character anymore.
Related #8840 #4312 -- the latter one has the exact opposed view as #8840 and this issue

@alexandrudima Understood. However, I still disagree. I don't care to insert tabs, that's why I set my preferences as spaces. Having a surprising and hacky way just to insert a tab doesn't make a lot of sense to me. I can't recall any other editor that does this.
The exact behaviour I run into this was actually trying to fix my indentation. Say you have copied something and the indent is one space off. I'd go back and highlight the space and hit tab. Great, now I have a tab character instead of the two spaces I asked for.

@alexandrudima Actually https://github.com/Microsoft/vscode/issues/8840 is a duplicate of this issue. It says the expected behaviour is to insert spaces (not the opposite).

@blakeembrey -- I completely agree.  I opened #8840 not knowing this one already existed.  The current behavior seems clunky and non-intuitive and allows \t characters to be inserted into a file unintentionally.  Visual Studio and Notepad++ also both seem to function as I would expect.  VSCode's behavior seems like the outlier, and IMHO incorrect.

@blakeembrey I agree, hitting tab + indentation with spaces should not insert the tab character.


Roll engine 8849d3092d5a..f3482700474a (1 commits)

https://github.com/flutter/engine/compare/8849d3092d5a...f3482700474a
git log 8849d3092d5aa6866501663cd62397f1a1564e67..f3482700474a791dabe9c4783568ed0fe512b04d --no-merges --oneline
f34827004 Simplify buildtools (flutter/engine#9875)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (aaclarke@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


remove privileged: true from daemonset

Signed-off-by: Anurag<EMAIL_ADDRESS>
remove privileged: true from daemonset

Ref: #781

It's not working :\
ci-test-runtime uses one of the YAMLs you updated and is the only relevant test we have to test this out, And it's failing. Can you check it out?

https://github.com/kubearmor/KubeArmor/pull/900
Closing favour of https://github.com/kubearmor/KubeArmor/pull/900


WIP Fix flush token cron job for RHEL

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test

So I think the ternary operator is fine because we don't want to be adding not needed paths into a cron job that is run by root. I also moved the ternary operator into the template so the weirdly named variable cron_bin_path disappears. Please see other comments.

LGTM


[Type checker] Move for-each pattern checking logic into the solver.

Move checking of the for-each pattern deeper into the solver, and start
detangling the "type check" and "coerce" phases somewhat for pattern type
checking, as a precursor to making the former more functional.

@swift-ci please smoke test


fix: showing a warning on transactions detail/cosignature modal

fixes #1719
showing a warning on transactions detail/cosignature modal and getting ack when the tx is announced by 3rd party account
WIP:

texts need to be localized
all the transaction types need to be tested (restriction, metadata etc)

https://www.loom.com/share/57b7dcfb2dd14f12b7067eaa999a57e3

I think only case we should avoid is warning for cosigners when we creating multisig: https://share.getcloudapp.com/9ZuQZnWK


Timeout Error: Could not establish Postmate handshake

Unexpected Errors

Hi @asinger720, I'm not sure either, unfortunately. I recommend comparing what's enabled in your Production org with your Sandbox org where the app is working and hope something stands out.

I ran into this issue in a sandbox and it was related to browser cookie management - specifically whether 3rd party cookies are blocked or not. Salesforce has been changing domains around quite a bit presumably for performance reasons, and seems to be more aggressive in the dev/sandbox environments than production.

Thanks @datapharmer.
In the latest release, Release 2.2, I’ve swapped from Postmate to Penpal as the communication library. Hopefully that also may help resolve the issue for others too.

In further investigations, the resolution may require enabling Allow IFraming of Visualforce Pages with Clickjack Protection.


ARROW-15171: [C++][Java] Update ORC to 1.7.2

This PR aims to bump ORC to 1.7.2.
Apache ORC 1.7.2 is a maintenance release with the following bug fixes.

https://github.com/apache/orc/releases/tag/v1.7.2
https://orc.apache.org/news/2021/12/20/ORC-1.7.2/

Rebased.

@github-actions crossbow -g cpp

@github-actions crossbow submit -g cpp

Thank you, @williamhyun and @pitrou !


declarations only used inside subsequently defined closures problematic: error "printf.go:485:6: argType declared but not used"

Tried running godebug on my light fork of Ross' c2go. It errored out on un-used declaration. The declaration is used, but only inside a closure defined later in that function.
prep:
go get github.com/glycerine/c2go
jaten@mbp13:~/go/src/github.com/glycerine/c2go$ godebug run *.go
printf.go:485:6: argType declared but not used
couldn't load packages due to errors: main
jaten@mbp13:~/go/src/github.com/glycerine/c2go$

minimal test case small.go:
package main

func takeClosure(f func(i interface{})) {
}

func main() {
    var touchedInClosure string
    takeClosure(func(i interface{}) {
        switch i.(type) {
        case string:
            touchedInClosure = "I have been written to!"
        }
    })
}

results on minimal test case small.go
jaten@mbp13:~/go/src/github.com/glycerine/c2go$ godebug run small.go
small.go:7:6: touchedInClosure declared but not used
couldn't load packages due to errors: main
jaten@mbp13:~/go/src/github.com/glycerine/c2go$

c2go is probably a nice small-medium sized program to try godebug on; I would suggest confirming that godebug works on it in full.

Thanks for the report! Surprisingly, it looks like you found a bug in golang.org/x/tools/go/loader:
Minimal loader program loader.go:
package main

import (
    "fmt"

    "golang.org/x/tools/go/loader"
)

func main() {
    var conf loader.Config
    conf.CreateFromFilenames("main", "small.go")
    _, err := conf.Load()
    fmt.Println(err)
}

results on your minimal test case small.go
$ go run loader.go
small.go:7:6: touchedInClosure declared but not used
couldn't load packages due to errors: main

I'll see if I can find out what's going on and get this fixed upstream.

This isn't a bug. Using a variable isn't just writing to it but reading it and because the variable is never used inside it's scope, it complains about it.

@omeid is right. It's unfortunate that godebug does not accept a program that the go tool does, though.
I was curious what the spec had to say about this. I found this:

Implementation restriction: A compiler may make it illegal to declare a variable inside a function body if the variable is never used.

So the spec leaves this open, and both the go tool and the loader library are in compliance. The latter is just more strict.

Early versions of godebug used golang.org/x/tools/go/types for type checking. That library does not object to small.go:
package main

import (
    "fmt"
    "go/ast"
    "go/parser"
    "go/token"

    "golang.org/x/tools/go/types"
)

func main() {
    var fs token.FileSet
    f, err := parser.ParseFile(&fs, "small.go", nil, 0)
    if err != nil {
        fmt.Println("error in parsing: ", err)
        return
    }
    _, err = types.Check("main", &fs, []*ast.File{f})
    fmt.Println(err)
}

Running it:
$ go run parser.go
<nil>

The loader library provides a lot that the types library does not, so it might not be worth the effort to switch to it. But it would make godebug behave more like go for this case.

Please don't downgrade.
c2go has been written against an older version of Go and should be ported to the latest if they want to use godebug, not the other way around.

c2go isn't outdated. It runs on tip (or, at least, my copy of tip from last week):
~/src/github.com/glycerine/c2go$ go version
go version devel +180fbb1 Fri Mar 27 00:30:14 2015 +0000 linux/amd64
~/src/github.com/glycerine/c2go$ go run *.go
usage: c2go [options] *.c
  -I string
	    include directory
  -c string
	    config file
  -dst string
	    GOPATH root of destination (default "/tmp/c2go")
exit status 2

The surprising behavior is that godebug's type checker behaves differently from go's type checker, even though both are compliant with the language spec.

@glycerine I tried just deleting that variable from the code and godebug run worked fine:
$ godebug run *.go
usage: c2go [options] *.c
  -I="": include directory
  -c="": config file
  -dst="/tmp/c2go": GOPATH root of destination

Oops, I messed up my test with golang.org/x/tools/go/types. I had edited small.go before I ran the test.  Sorry, @glycerine! If you want to debug that library, just delete that variable.

Arg. Agree we can't fix this locally, but I am still inclined to think we
should upstream this as an issue so that "go run" and the types library are
consistent.
On Sun, Apr 5, 2015 at 9:58 PM, Jeremy Schlatter<EMAIL_ADDRESS>wrote:

Closed #14 https://github.com/mailgun/godebug/issues/14.
—
Reply to this email directly or view it on GitHub
https://github.com/mailgun/godebug/issues/14#event-273861199.

--
Best regards,
Jason
--
Jason E. Aten, Ph.D.
<EMAIL_ADDRESS>650-429-8602
linkedin: https://www.linkedin.com/pub/jason-e-aten-ph-d/18/313/45a

err, I misread -- It's the "golang.org/x/tools/go/loader" library that
differs in strictness, yes?
On Mon, Apr 6, 2015 at 7:55 AM, Jason E. Aten<EMAIL_ADDRESS>wrote:

Arg. Agree we can't fix this locally, but I am still inclined to think we
should upstream this as an issue so that "go run" and the types library are
consistent.
On Sun, Apr 5, 2015 at 9:58 PM, Jeremy Schlatter<EMAIL_ADDRESS>
wrote:

Closed #14 https://github.com/mailgun/godebug/issues/14.
—
Reply to this email directly or view it on GitHub
https://github.com/mailgun/godebug/issues/14#event-273861199.

--
Best regards,
Jason
--
Jason E. Aten, Ph.D.
<EMAIL_ADDRESS>650-429-8602
linkedin: https://www.linkedin.com/pub/jason-e-aten-ph-d/18/313/45a

--
Best regards,
Jason
--
Jason E. Aten, Ph.D.
<EMAIL_ADDRESS>650-429-8602
linkedin: https://www.linkedin.com/pub/jason-e-aten-ph-d/18/313/45a

opened https://github.com/golang/go/issues/10356 to track upstream

go/loader and go/types behave the same way, and both are different from gc. I thought differently earlier in the ticket, but I was mistaken.


Condition Icon Counters

While the recent update to Status Effects was excellent, it seems to break compatibility with the module "Status Icon Counters".
While this isn't the end of the world, it could be a useful feature to integrate or support in the future, especially with stackable conditions like Strife and Fatigue. This could potentially even allow for a direct link between the status effect and the counter in the character sheet.
Example image from the module mentioned:

This will be coming in the next few updates. The refactor of the conditions interface and the change in how it works was done to make it easier to support this feature along with some other improvements.

Will be part of the next release.


V25 review p1

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

We can now close this as this was merged in.


Loading message?

There is something from OSD to be used if I want to show a loading message do my users while the image is being loaded?

There is no built in message mechanism but you can use the tile-drawn event as described on #648 to detect when the first tile has been drawn.

This event is fired even if the image is loading yet. Can I get the images URL using this event to check with JS if image is fully loaded? I couldn't find which images were loaded when "tile-drawn" is fired

This event is fired even if the image is loading yet.

Do you want to detect when all the necessary tiles have been drawn? I think we are missing such event.
Maybe we could create a new event for that.

Can I get the images URL using this event to check with JS if image is fully loaded? I couldn't find which images were loaded when "tile-drawn" is fired

I am not sure whether you want the URL of the tile or of the tiled image but you can get both:
viewer.addHandler("tile-drawn", function(event) {
   var tileUrl = event.tile.url;

   // Supposing your tile source has an URL.
   // For example for DZI images, it would be the .dzi file
   var tileImageUrl = event.tiledImage.source.url;
});

Yes, that is what I need! Can you give me a tip about where can I start to develop such event? I'm not very familiar with OSD code yet, but I could try. I'm trying to identify the images loading progress manipulating the drawCanvas function. I'm not sure this is the best way to get such information

I am not sure whether you want the URL of the tile or of the tiled image but you can get both:

My idea was to get the image URL and check is JS if this image is already loaded. I'm not sure this is possible, but was my best shot! =)

Yes, that is what I need! Can you give me a tip about where can I start to develop such event? I'm not very familiar with OSD code yet, but I could try. I'm trying to identify the images loading progress manipulating the drawCanvas function. I'm not sure this is the best way to get such information

You probably need to raise the event when _needsDraw is set to false here https://github.com/openseadragon/openseadragon/blob/master/src/tiledimage.js#L132
But I am thinking we actually need 2 events:

when a tiled image is entirely drawn
when the world is entirely drawn
I would wait on @iangilman thought on that.

My idea was to get the image URL and check is JS if this image is already loaded. I'm not sure this is possible, but was my best shot! =)

Could you clarify what you mean by image? Tile (which has a specific URL) or entire image (TiledImage) which doesn't necessary have a URL depending on the tile source used?

Could you clarify what you mean by image? Tile (which has a specific URL) or entire image (TiledImage) which doesn't necessary have a URL depending on the tile source used?
I mean the tile

But I am thinking we actually need 2 events:

*when a tiled image is entirely drawn
*when the world is entirely drawn I would wait on @iangilman thought on that.

I will try to follow this way. I will kepp you updated. I'll be pleasured to make my first commit to this amazing project with such event.

Yes, we've definitely been wanting this event! I think even starting with the one for TiledImage would be a good start. @avandecreme is correct in pointing out the key flag (_needsDraw). I'm thinking if you checked to see if it was false right after the updateViewport call here:
https://github.com/openseadragon/openseadragon/blob/master/src/tiledimage.js#L240
...that would do it. You'd want to only fire it once, though (otherwise you'd get flooded with these events), so you need to keep track of whether you've fired it yet.
I'm a little up in the air as to whether the new event should be fired on behalf of TiledImage (like bounds-change) or on behalf of the Viewer (like tile-drawing). I think I'm leaning toward firing it on behalf of the Viewer. This would make it easy for people who just have a single tiled image (still the most common use case) but still make it possible for us to build a version for the whole World (i.e. all tiled images have finished loading the necessary tiles for the initial view) at some point.

Has this event been completed yet, or is it available for testing?  I'm more than happy to try it out.
Having an event fired when the current image with a drawer has fully completed loading would be excellent for my current task, in order to ensure that when I capture a snapshot of the canvas image, it's correct and complete.

@malDuffin no, this still needs to be done; looks like @humbertorodrigues has perhaps moved on to other things. Would you like to take your hand at writing the patch?

Hi Ian,
I can certainly give it a go.
What would you suggest is the best way to detect when this event should be raised?  I'm assuming there is a way to detect the total number of tiles to be loaded for that current drawer ( X ), and then when X tile-drawn events are detected, the loading is complete?

I think it may be as simple as adding an  else clause to:
https://github.com/openseadragon/openseadragon/blob/master/src/tiledimage.js#L800-L802
… and firing it then. You'd want to only fire it once, though (otherwise you'd get flooded with these events), so you need to keep track of whether you've fired it yet for that TiledImage.

+1
I could really do with this event!

Ok, I've made a start here:
https://github.com/openseadragon/openseadragon/pull/837
Feedback welcome!

#837 has landed, with support for this at the TiledImage level. In the future we might want to add one at the World or Viewer level that pays attention to all of the tiled images, or maybe this is good enough. At any rate, closing this issue.


Idea: Adding support for nip11 relay info

Firstly, thanks for nostr-tools, it makes building on nostr super easy in the browser. 🧡 🧡 🧡
My idea is to add nip11 support to nostr-tools. The back story is that I was pushing parameterised replaceable events to several relays, until I realised they don't support them (nip33). Then checking nostr.watch it seems that there's only a small subset of relays who support nip33.
My thought was that I'd like my nostr client to automatically reject messages I try to post to relays which don't support those features. Of course I'd also like to be able to override said protections.
Before I go too far down the rabbit hole and start writing PRs, I wanted to check in with the maintainers first. Is this something you think would make sense to add to nostr-tools?
Edit: I can think of lots of different ways nip11 support could be added. The scenario described above is just one of those. I wanted to open the discussion on the whole topic rather than just the idea of rejecting events to relays which won't support them.

As far as I know nop11 is not possible to implement in the browser, because
WebSocket client API doesn't support it.
I think it would be better to change the protocol actually to not contain
features that can't be implemented in the browser.
On Fri, Jan 13, 2023, 14:54 Callum Macdonald @.***>
wrote:

Firstly, thanks for nostr-tools, it makes building on nostr super easy in
the browser. 🧡 🧡 🧡
My idea is to add nip11
https://github.com/nostr-protocol/nips/blob/master/11.md support to
nostr-tools. The back story is that I was pushing parameterised replaceable
events to several relays, until I realised they don't support them (nip33).
Then checking nostr.watch it seems that there's only a small subset of
relays who support nip33.
My thought was that I'd like my nostr client to automatically reject
messages I try to post to relays which don't support those features. Of
course I'd also like to be able to override said protections.
Before I go too far down the rabbit hole and start writing PRs, I wanted
to check in with the maintainers first. Is this something you think would
make sense to add to nostr-tools?
—
Reply to this email directly, view it on GitHub
https://github.com/nbd-wtf/nostr-tools/issues/85, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN5SWAGHKRSE3NGELUZZI73WSFUA7ANCNFSM6AAAAAAT2P22NE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ah sorry, you're right, it works.
On Fri, Jan 13, 2023 at 3:03 PM Callum Macdonald @.***>
wrote:

@adamritter https://github.com/adamritter I have a different
understanding here. I believe nip11 requires that the server sets the
relevant CORS headers. I've just done a quick and dirty test in my browser
console and I was able to retrieve the relay info like so:
fetch('https://relay.nostr.nu', {headers: {'accept': 'application/nostr+json'}}).then(r => r.json().then(console.log))
—
Reply to this email directly, view it on GitHub
https://github.com/nbd-wtf/nostr-tools/issues/85#issuecomment-1381988672,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN5SWAAX46RCAFKNLJHSD5LWSFVFZANCNFSM6AAAAAAT2P22NE
.
You are receiving this because you were mentioned.Message ID:
@.***>

The implementation should be a standalone nip11.ts file exporting a function that just makes a request to a relay and returns the data, with the types and so on. Maybe with some helper methods.
To keep everything lean and agnostic we can't mix that into the relay.js implementation here, that must be done at higher levels.

@fiatjaf Gotcha. So a standalone nip11.ts file which handles getting the relay info, etc.
One idea I had was to check relays for nip support before opening the websocket connection. Then to add some filtering on which types of events get broadcast to which relays. Those filters would probably be nip specific. So a filter for nip33 would say something like kind>=30000&kind<40000.
Where would you see those filters going? Part of the nip11.ts file? Or as a separate export from each of the nip files? Or does this seem like it doesn't fit nostr-tools and would be better implemented as a separate package altogether?
Personally, I kinda like the idea that by default, nostr-tools won't send events to relays which don't support them. Especially with events that should be deleted (whether expired, replaced, whatever), it seems like an unfortunate scenario to accidentally send it to a relay that doesn't support the appropriate nip.

I saw this issue and as I am working on a relay implementation and this nip is about relays I did a nip11.ts with types and a function to get infos from a relay. I also did some tests, here a link to the file I did:
https://github.com/giacomogagliano/nip11/blob/nip11/nip11.ts
hope it can help!

Nice, @giacomogagliano, can you open a pull request adding that to this repo?

Yes =), sounds great =)!


Add inherit_visibility_layer to Parallax2D

After feedback from other maintainers, this is an alternative to #93512. The suggestion was, rather than exposing it for all canvas items, only expose it on Parallax2D nodes. The drawback is that it would create added complexity to renderer_canvas_cull.cpp over #93512, and wouldn't address https://github.com/godotengine/godot-proposals/issues/10014, but would mean Parallax2D would be supported in multiple viewports for things like split screen games. This added complexity could be simplified if/when the general canvas item feature is desired by the community as a whole.
When inherit_visibility_layer is set to true, the parent visibility_layer will be used the Parallax2D node and for all descendants. This allows a parallax node to appear in only one viewport without needing to manually update the visibility_layer of every node.
Shown below is two SubViewports sharing the same World2D. The first viewport shows layer 1 and 2. And the second shows 1 and 3. The parallax nodes are duplicated into both viewports, both with inherit_visibility_layer enabled, but the first is set to layer 2 and the second is set to layer 3, so they will only show in those layers.

https://github.com/user-attachments/assets/acb7c837-1706-40f7-b49f-526209bd4d81

How come the closure?

I did some more playing around, and it seems there's a quirk you can currently exploit with visibility layers only in 2D, where one acts as a key for another which allows you to hide layers in certain viewports by gating them behind a non-compatible visibility layer even if all the children are.

In the above, only the second set of sprites will be visible. But if they're shared on a viewport that culls 1 and 2, only the first set will be visible. This means you currently are able to set up parallax nodes and leave them at the arbitrary default of 1, and it will only show up on the desired viewport as long as you gate them properly.
There is still a lot of work to be done with visibility layers, as there are a lot of quirks and inconsistencies, however in the current system, you are able to achieve parallax in split screens with an easy trick, so this feature would be a bit redundant. There's also the idea that we could handle all parallax logic in the renderer itself, but that comes with tradeoffs too.


"player_leave" hook makes it red

Using API6 and version 5 of webapi. This hook throws a big error :
    "player_leave"=[
        {
            # This is the address of the endpoint.
            address="myurl"
            # Choose to either send the data as:
            # JSON = application/json
            # XML = application/xml
            dataType=JSON
            # Set to true to send detailed json data
            details=true
            # Set to true or omit to enable the endpoint.
            enabled=true
            # Choose to send the data wrapped as application/x-www-form-urlencoded
            form=true
            # This is a list of additional headers that is sent to the server. You can use this to e.g. specify a secret
            # key which ensures that the server knows the requests are coming from the Web-API.
            # Please note that the following headers will always be overridden by the Web-API:
            # X-WebAPI-Version, X-WebAPI-Event, X-WebAPI-Source, User-Agent, Content-Type, Content-Length, accept, charset
            headers=[]
            # This is the http method that is used (GET, PUT, POST or DELETE)
            method=POST
            # Permissions node same as the ones in the permissions.conf file,
            # use to configure which data is sent to this node
            permissions="*"
        }
    ]

But is fine with details=false. Hook 'player_join' has no problem, with or without details.
Report is here : https://pastebin.com/aCtargyu

Fixed in v5.0.6


403 PERMISSION_DENIED accessing BigQuery discovery endpoint

Update: oops, discovered I forgot to add BigQuery to the list of API restrictions for the key.

BigQuery discovery is returning 403 response when accessing the discovery endpoint.
I've tried multiple discovery URLs (both which I can access via my browser)

https://bigquery.googleapis.com/discovery/v1/apis/bigquery/v2/rest
https://www.googleapis.com/discovery/v1/apis/bigquery/v2/rest

II also get the error in both forms of the load method

gapi.client.load('bigquery', 'v2')
gapi.client.load(' https://bigquery.googleapis.com/discovery/v1/apis/bigquery/v2/rest')
gapi.client.init({discoveryDocs: [...], ...})

I'm calling it from the background page of a Chrome Extension. The goal is to have the user access their BigQuery using OAuth2.
Here's the response:
{
  "error": {
    "code": 403,
    "message": "Requests to this API bigquery method google.discovery.Discovery.GetDiscoveryRest are blocked.",
    "status": "PERMISSION_DENIED",
    "details": [
      {
        "@type": "type.googleapis.com/google.rpc.ErrorInfo",
        "reason": "API_KEY_SERVICE_BLOCKED",
        "domain": "googleapis.com",
        "metadata": {
          "consumer": "projects/<id>",
          "service": "bigquery.googleapis.com"
        }
      }
    ]
  }
}

The reason API_KEY_SERVICE_BLOCKED seems to suggest I'm missing a configuration option somewhere. However, the current setup is working with the Google Sheets API

Update: oops, discovered I forgot to add BigQuery to the list of API restrictions for the key.

Sounds like this issue was resolved. Feel free to reopen if i misunderstood.


Who can help me？not find treema-utils.js

module.js:341
throw err;
^
Error: Cannot find module '../../bower_components/treema/treema-utils.js'
at Function.Module._resolveFilename (module.js:339:15)
at Function.Module._load (module.js:290:25)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at Object. (/home/hnck/codecombat-master/server/models/Achievement.coffee:7:15)
at Object. (/home/hnck/codecombat-master/server/models/Achievement.coffee:1:1)
at Module._compile (module.js:413:34)
at Object.loadFile (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:16:19)
at Module.load (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at AchievablePlugin (/home/hnck/codecombat-master/server/plugins/achievements.coffee:13:17)
at Schema.plugin (/home/hnck/codecombat-master/node_modules/mongoose/lib/schema.js:1226:3)
at Object. (/home/hnck/codecombat-master/server/models/User.coffee:634:12)
at Object. (/home/hnck/codecombat-master/server/models/User.coffee:1:1)
at Module._compile (module.js:413:34)
at Object.loadFile (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:16:19)
at Module.load (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at Object. (/home/hnck/codecombat-master/server/commons/auth.coffee:3:8)
at Object. (/home/hnck/codecombat-master/server/commons/auth.coffee:1:1)
at Module._compile (module.js:413:34)
at Object.loadFile (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:16:19)
at Module.load (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at Object. (/home/hnck/codecombat-master/server_setup.coffee:17:8)
at Object. (/home/hnck/codecombat-master/server_setup.coffee:1:1)
at Module._compile (module.js:413:34)
at Object.loadFile (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:16:19)
at Module.load (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at Object. (/home/hnck/codecombat-master/server.coffee:11:15)
at Object. (/home/hnck/codecombat-master/server.coffee:1:1)
at Module._compile (module.js:413:34)
at Object.loadFile (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:16:19)
at Module.load (/home/hnck/codecombat-master/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:20:19)
at Object. (/home/hnck/codecombat-master/index.js:11:14)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)
at startup (node.js:148:18)
at node.js:405:3
npm ERR! Linux 3.10.0-693.el7.x86_64
npm ERR! argv "/root/.nvm/versions/node/v5.12.0/bin/node" "/root/.nvm/versions/node/v5.12.0/bin/npm" "start"
npm ERR! node v5.12.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! codecombat@ start: node ./index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the codecombat@ start script 'node ./index.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the codecombat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./index.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs codecombat
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls codecombat
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/hnck/codecombat-master/npm-debug.log

Can you try running under node 6? We're not on 5 any more.

Thank nwinter very much, but now when I install, there is no public folder.


Update nan to 1.5, make compatible with io.js

:)

Hello, @talrasha007.
nan has been updated in 399f22901dadecc8132aa86cc638c7a379bc61b2.
Although late, this issue is resolved.
Closing for now.


Getting lots of failedJobs

numOfJobsCompleted":23,"numOfJobsFailed":25
Query:
Shisha bars in London
Running basic command, is this because of google page layout?
Its exceeding 5000ms and timing out 50% of each request
{"level":"info","component":"scrapemate","numOfJobsCompleted":13,"numOfJobsFailed":7,"lastActivityAt":"2024-04-02T10:43:21.913079263Z","speed":"6.50 jobs/min","time":"2024-04-02T10:43:46.856171969Z","message":"scrapemate stats"} {"level":"info","component":"scrapemate","job":"Job{ID: fcf935d7-83ad-4c51-bdf8-0e6857f98cd1, Method: GET, URL: https://www.google.com/maps/place/Cavalli+lounge/data=!4m7!3m6!1s0x48760517c9548bab:0xa81bb11018bf2868!8m2!3d51.4978355!4d-0.1650291!16s%2Fg%2F11t7sfbsfj!19sChIJq4tUyRcFdkgRaCi_GBCxG6g?authuser=0&hl=en&rclk=1, UrlParams: map[hl:en]}","error":"Timeout 5000.00ms exceeded.","status":"failed","duration":36361.429128,"time":"2024-04-02T10:43:51.615019055Z","message":"job finished"} {"level":"error","component":"scrapemate","error":"Timeout 5000.00ms exceeded.","time":"2024-04-02T10:43:51.615039471Z","message":"error while processing job"} {"level":"info","component":"scrapemate","numOfJobsCompleted":13,"numOfJobsFailed":8,"lastActivityAt":"2024-04-02T10:43:51.615045471Z","speed":"4.33 jobs/min","time":"2024-04-02T10:44:46.913444177Z","message":"scrapemate stats"}

"numOfJobsCompleted":191,"numOfJobsFailed":181,
touch results.csv && docker run -v $PWD/example-queries.txt:/example-queries -v $PWD/results.csv:/results.csv gosom/google-maps-scraper -depth 20 -c 8 -input /example-queries -results /results.csv -lang en -exit-on-inactivity 3m
Shisha bars in Croydon
Shisha bars in Bromley
etc etc...

i am getting
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Could this be the problem?

I had the same issue on my 1 vCPU server.
I had to upgrade.
Where are you trying to run the program ? Which config ?

@liamsegura it looks like you use the provided docker image in ARM. I never tried that.
Better compile and run you own build.
additionally, you may want to use a more powerfull machine or reduce concurrency.
Also depth 20 is maybe a bit high, the more you scroll the more slow it is (maybe google throttles?) .
I recommend you reduce the depth to 10 and do more searches instead (in sub areas).


Lux / No rrule!! available for gemm foreigncall

This is a simplified example from the Bayesian neural net Turing.jl tutorial:
import Mooncake
using DifferentiationInterface: AutoMooncake, prepare_gradient
using Lux: Lux
using Random: Xoshiro

"""Generates a NamedTuple of parameters in the format that Lux expects"""
function reconstruct_nn_params(ps_new::AbstractVector)
    # Works
    # (layer_1 = (weight = reshape(ps_new[1:2], 1, 2), bias = ps_new[3:3]),)
    # Fails
    (layer_1 = (weight = reshape(view(ps_new, 1:2), 1, 2), bias = ps_new[3:3]),)
end

nn = Lux.Chain(Lux.Dense(2 => 1, Lux.σ))
_, st = Lux.setup(Xoshiro(468), nn)
xs = rand(Xoshiro(468), Float32, 2, 3) # training data
params = randn(Xoshiro(468), 3) # parameters

predict(params) = Lux.apply(nn, xs, Lux.f32(reconstruct_nn_params(params)), st)[1]
predict(params)

prep = prepare_gradient(predict, AutoMooncake(; config=nothing), params)

It's just the view that seems to be problematic, without that it doesn't error.
Bisects to 0.4.57, i.e. https://github.com/compintell/Mooncake.jl/pull/410

Thanks for finding + minimising this -- #424 will resolve. Your bisection makes total sense -- I changed the way that gemm!'s rrule is implemented in that PR, and the result was very slightly less generic than I had hoped for. It looks like I mustn't have had any test cases covering Base.ReshapedArrays being passed into BLAS calls. In any case, #424 permanently adds inputs containing Base.ReshapedArrays to the test suite of all BLAS / LAPACK functions, so there should be no risk of this bug reappearing for gemm! or for any other BLAS / LAPACK functionality.

0.6.32 is merged, should be available shortly, and should resolve. Please let me know if it doesn't!


HHH-4712 - Fix missing column failures when non-identifier properties named id.

https://hibernate.atlassian.net/browse/HHH-4712
In circumstances where an entity's identifier was an Embeddable but also contained a non-identifier property named id would result in failure to generate the proper column aliases for the query.
This fix makes sure the same logic is used in several places to avoid the incorrect SQL generated.

Applied


Cannot Remove Tags with 'x'

When 'first' tag is added to a cell clicking the 'x' does not remove the tag.

I get the following VsCode error.

VsCode Version: 1.71
OS: macOS Monterey Version 12.6

Same error here, the +Tag button is not working as well.
Gives the following error message:

Thanks I think it's probably that we didn't activate the extension on command execution. Will push a fix soon.

0.1.2 is published now. Please give it a try and let me know if you are still seeing the issue. If that happens, let's see how we can get more info from you to have it resolved. Thanks in advance!

@rebornix It's still giving the same error, checked with 0.1.2 and 0.1.3 both have this issue.

I can confirm with 0.1.3 - all I get is "actual command NOT FOUND", with no functionality (other than viewing tags) seemingly working.
The "Log (Extension Host)" output window shows:
[2022-09-27 17:15:29.967] [exthost] [error] actual command NOT FOUND _vscode_delegate_cmd_l8kcb9rm undefined


Rocket Chat Window doesn't start in the last known position

Description:
Rocket Chat window doesn't start in the last known position if the position was at the edge of the screen. No matter what edge (or corner) it is, RC always starts in random position. Problem occurs with multiple and single screen setups without changing the sreens setup.
If the last window position wasn't at the edge - RC starts in that position with unharmed window size.
Steps to reproduce:

Put the RC window at the edge of the screen.
Turn off RC
Turn on RC

Expected behavior:
RC should keep the last position of the window.
Actual behavior:
RC starts in the default position with default windows size.
Client Setup Information

Desktop App or Browser Version: 3.9.4 / 3.9.5
Operating System: Windows 10/11

Not sure if this is a Rocket.Chat issue to fix, but I'll send this issue to the Electron repository ...

FYI, this seems to be the same issue already reported here: https://github.com/RocketChat/Rocket.Chat.Electron/issues/2714


Author ADR 11 summarizing error handling changes

Closes: #XXX
Description

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests.
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Closing this PR and re-opening it against main instead of against the error-handling branch.

Just a note on the reason for closing this issue.
We can edit a base branch of a PR.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request


Support MQTT-5 publish related properties.

Master Issue: #369
Motivation
Support publish with Content type, Correlation data, Response topic properties.
Documentation

[x] no-need-doc

Codecov Report

Merging #663 (e19471c) into master (0d0af93) will increase coverage by 0.00%.
The diff coverage is 60.17%.

@@            Coverage Diff            @@
##             master     #663   +/-   ##
=========================================
  Coverage     77.97%   77.98%
- Complexity      910      925   +15
=========================================
  Files           108      109    +1
  Lines          3923     3974   +51
  Branches        276      297   +21
=========================================
+ Hits           3059     3099   +40
- Misses          702      711    +9
- Partials        162      164    +2

Impacted Files
Coverage Δ

...s/mqtt/proxy/MQTTProxyProtocolMethodProcessor.java
77.89% <0.00%> (-0.86%)
:arrow_down:

...lsar/handlers/mqtt/support/Qos1PublishHandler.java
64.81% <0.00%> (ø)

...qtt/support/MQTTBrokerProtocolMethodProcessor.java
78.84% <41.17%> (-0.99%)
:arrow_down:

...ar/handlers/mqtt/utils/PulsarMessageConverter.java
90.81% <97.61%> (+5.10%)
:arrow_up:

...o/streamnative/pulsar/handlers/mqtt/Constants.java
100.00% <100.00%> (ø)

...lsar/handlers/mqtt/messages/MqttPropertyUtils.java
89.47% <100.00%> (-0.78%)
:arrow_down:

.../pulsar/handlers/mqtt/messages/ack/MqttPubAck.java
87.80% <100.00%> (+0.30%)
:arrow_up:

...handlers/mqtt/restrictions/ClientRestrictions.java
68.00% <100.00%> (+1.33%)
:arrow_up:

...pulsar/handlers/mqtt/MQTTCommonInboundHandler.java
77.94% <0.00%> (-4.42%)
:arrow_down:

Continue to review full report at Codecov.

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


Assertion failed in test/test-tcp-write-queue-order.c (write_cancelled_callbacks)

on Debian jessie, fresh install
/tmp/libuv-1.4.2# uname -a
Linux webtop1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02) x86_64 GNU/Linux
during the make check
tcp_write_queue_order failed: exit code 6
Output from process tcp_write_queue_order:
Assertion failed in test/test-tcp-write-queue-order.c on line 129: write_cancelled_callbacks > 0
FAIL: test/run-tests
1 of 1 test failed
Please report to https://github.com/libuv/libuv/issues
Makefile:3835: recipe for target 'check-TESTS' failed
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory '/tmp/libuv-1.4.2'
Makefile:4091: recipe for target 'check-am' failed
make: *** [check-am] Error 2
le line 129 of the tsts is
ASSERT(write_cancelled_callbacks > 0);
same pb with last version from git
EDIT: I update for the typo

I'll try and take a look!

Next time, could you put the output log in between ```(three backticks), then the whole output would be formatted in the same manner.
The line that you are talking is here: https://github.com/libuv/libuv/blob/v1.x/test/test-tcp-write-queue-order.c#L129
In the test we are creating 1000 little writes to try to force queuing, however in your case it did not work.
I think the test would succeed in you case if you further increase the REQ_COUNT to lets say 100000.
Probably your write socket buffer size is higher than usual, could you post the output of the following command:
cat /proc/sys/net/ipv4/tcp_wmem

Hello,
you're right
cat /proc/sys/net/ipv4/tcp_wmem
30000000	30000000	30000000
this value is high as I am performing benchmark.
Actually my friend and collegue (blackbelt in system and C programming) found out the problem already.
You may  check this value instead of hardcoded one in your test ?
kr,
julien

You may check this value instead of hardcoded one in your test ?

I don't understand what you want to say...
On my simple machine I have:
4096    16384   903776

4kb minimum, 16kb maximum per socket and ~0.86MB total for all buffers.
Now your test machine has 28MB as minimum, maximum and total. I fear that the test will not succeed nevermind how much you increase the REQ_COUNT in the test. Maybe increasing the buffer size will help.
Either way, the test failure doesn't matter much. I have written the test and as far as I remember we just agreed to this value.
This can be closed unless we want to make this test pick something more dynamic according to uv_recv_buffer_size so it succeeds on machines with beefier socket size buffer settings as well.

Hello, I work with Julien.
We agree that our settings are a bit extreme. However, please imagine being in the end-user's seat in such a situation; by "end-user" I mean the average userland developer who may not be familiar with such global settings, or even not have root credentials. The error message, from his standpoint, is cryptic (knowing nothing of libuv, I spent 10 minutes to figure it out), and without understanding the  mechanism he cannot easily decide to ignore the negative test result...

Hello, I work with Julien.
We agree that our settings are a bit extreme. However, please imagine being in the end-user's seat in such a situation; by "end-user" I mean the average userland developer who may not be familiar with such global settings, or even not have root credentials. The error message, from his standpoint, is cryptic (knowing nothing of libuv, I spent 10 minutes to figure it out), and without understanding the  mechanism he cannot easily decide to ignore the negative test result...

-Alex

Hello, I work with Julien.
We agree that our settings are a bit extreme. However, please imagine being in the end-user's seat in such a situation; by "end-user" I mean the average userland developer who may not be familiar with such global settings, or even not have root credentials. The error message, from his standpoint, is cryptic (knowing nothing of libuv, I spent 10 minutes to figure it out), and without understanding the  mechanism he cannot easily decide to ignore the negative test result...

-Alex

Hello, I work with Julien.
We agree that our settings are a bit extreme. However, please imagine being in the end-user's seat in such a situation; by "end-user" I mean the average userland developer who may not be familiar with such global settings, or even not have root credentials. The error message, from his standpoint, is cryptic (knowing nothing of libuv, I spent 10 minutes to figure it out), and without understanding the  mechanism he cannot easily decide to ignore the negative test result...

-Alex

Hello, I work with Julien.
We agree that our settings are a bit extreme. However, please imagine being in the end-user's seat in such a situation; by "end-user" I mean the average userland developer who may not be familiar with such global settings, or even not have root credentials. The error message, from his standpoint, is cryptic (knowing nothing of libuv, I spent 10 minutes to figure it out), and without understanding the  mechanism he cannot easily decide to ignore the negative test result...

-Alex

Hello, I work with Julien.
We agree that our settings are a bit extreme. However, please imagine being in the end-user's seat in such a situation; by "end-user" I mean the average userland developer who may not be familiar with such global settings, or even not have root credentials. The error message, from his standpoint, is cryptic (knowing nothing of libuv, I spent 10 minutes to figure it out), and without understanding the  mechanism he cannot easily decide to ignore the negative test result...

-Alex

For info: increasing #define REQ_COUNT to 100000 was enough to successfully pass the test

Her's a constructive suggestion: instead of hard-coding REQ_COUNT, maybe it is possible to detect the writes that don't complete immediately (equivalent of an EWOULDBLOCK in synchronous nonblocking semantics) ?

Nice suggestion, I think we can check the uv_write_buffer_size until it is > 0 or the counter increases to MAX_INT.

I have created a pull request which ups the maximum req_count to 100k, I don't want to do more, because it already requires like a 10mb memory block just to fit the requests. Maybe it doesn't really require that much until really referenced.
Anyway, this should fix this test for 10 years or so until we all having 16TB ram is considered to be normal.

Hum not sure about the 10 years: as you suspected the memory is not committed until used, and in some workloads (like ours) only a few sockets in the system will exercise that big depths. So the 10MB value is everything but the max... I like your suggestion of checking write_queue_size btw; that sounds more robust than bumping a constant ;-)

I like your suggestion of checking write_queue_size btw

I'm doing that already here, but I can't create an infinite sized block of requests here.
I can technically do something with malloc, but that would make the code more verbose and difficult. Maybe the other guys can chip in with some ideas.
Also, the 10MB are for holding the requests, not the actual amount of data we write to the socket. The test shouldn't fail until someone runs the test with socketbuffers set to 90MB

OK. But instead of wasting resources, what about forcing the tested socket buffer size to a known value ? Something like  uv_send_buffer_size(handle,16384) ...

lol, probably the best idea.


[FEA] Add testing for stage level scheduling

Is your feature request related to a problem? Please describe.
Spark 3.1 includes stage level scheduling: https://issues.apache.org/jira/browse/SPARK-27495 .  Add tests cases to configure Spark running with stage level scheduling enabled.
Describe the solution you'd like
Run the spark-rapids plugin with stage level scheduling enabled for a subset of integration tests and validate the output.
Describe alternatives you've considered
We could run with all tests enabled and stage level scheduling enabled.  We can start with a subset.
Additional context
https://issues.apache.org/jira/browse/SPARK-27495

After discussion, the right thing to do is create an example where we can demonstrate running an ETL job with the plugin and then in a subsequent stage running still on the GPU but without the plugin.  For example, an ETL job followed by an XGBoost job reading from Parquet files.  In between stages the configuration of the executors will change.
This can then be turned into a test case.


CouchDB 3.0 fails to start on CentOS 8 after following installation instructions

Description
After a fresh install in a freshly installed CentOS 8, CouchDB fails to start.
Instead, CouchDB returns the following error:
[info] 2020-03-02T15:44:38.397655Z<EMAIL_ADDRESS><0.11.0> -------- Application couch_log started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.409035Z<EMAIL_ADDRESS><0.11.0> -------- Application folsom started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.459996Z<EMAIL_ADDRESS><0.11.0> -------- Application couch_stats started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.460161Z<EMAIL_ADDRESS><0.11.0> -------- Application khash started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.469610Z<EMAIL_ADDRESS><0.11.0> -------- Application couch_event started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.469779Z<EMAIL_ADDRESS><0.11.0> -------- Application hyper started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.477903Z<EMAIL_ADDRESS><0.11.0> -------- Application ibrowse started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.485659Z<EMAIL_ADDRESS><0.11.0> -------- Application ioq started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.485799Z<EMAIL_ADDRESS><0.11.0> -------- Application mochiweb started on node<EMAIL_ADDRESS>[info] 2020-03-02T15:44:38.491456Z<EMAIL_ADDRESS><0.232.0> -------- Preflight check: Asserting Admin Account

[info] 2020-03-02T15:44:38.491566Z<EMAIL_ADDRESS><0.232.0> --------
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
  No Admin Account Found, aborting startup.
  Please configure an admin account in your local.ini file.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Steps to Reproduce
Follow the steps for CentOS here: https://docs.couchdb.org/en/stable/install/unix.html
Expected Behaviour
The admin account should be configured at first Fauxton startup. In this case, CouchDB refuses to even start...
Your Environment

CouchDB version used:
Operating system and version: CentOS 8

Additional Context

@natcohen This is a breaking change in CouchDB 3.0 and expected:

http://docs.couchdb.org/en/stable/whatsnew/3.0.html
https://github.com/apache/couchdb/pull/2389

In the Debian installer, the debconf framework allows us to prompt the user at install time for the user, and place it in an ini file. Unfortunately, CentOS/RedHat have no such mechanism.
To work around this, add a section like the following to your /opt/couchdb/etc/local.ini file:
[admins]
admin = password

You can then run service start couchdb and CouchDB will startup with your admin user.

Ok but then the doc should reflect that... Following this: https://docs.couchdb.org/en/stable/install/unix.html doesn't give a clue to what needs to be done.

@natcohen Thanks - would you be willing to help us? We're always looking for support.
Fork https://github.com/apache/couchdb-documentation and make a pull request with the recommended change. We'll definitely take it!


nsd: 4.8.0 -> 4.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/nsd/versions.
meta.description for nsd is: Authoritative only, high performance, simple and open source name server
meta.homepage for nsd is: http://www.nlnetlabs.nl
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.9.1 with grep in /nix/store/jq8jfr4fkn2xvl5i5xd23c0aqg01hsna-nsd-4.9.1
found 4.9.1 in filename of file in /nix/store/jq8jfr4fkn2xvl5i5xd23c0aqg01hsna-nsd-4.9.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

nsd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jq8jfr4fkn2xvl5i5xd23c0aqg01hsna-nsd-4.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nsd https://github.com/r-ryantm/nixpkgs/archive/183ed98086f44465e2ad04548961a1162f4a02f7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/183ed98086f44465e2ad04548961a1162f4a02f7#nsd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jq8jfr4fkn2xvl5i5xd23c0aqg01hsna-nsd-4.9.1
ls -la /nix/store/jq8jfr4fkn2xvl5i5xd23c0aqg01hsna-nsd-4.9.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

nsd

Maintainer pings
cc @hrdinka for testing.

@Mic92 thanks for testing!


Read an account from the service

As a DevOps
I need Read an account from the service
So that [benefit]
Details and Assumptions
* [document what you know]

Acceptance Criteria
gherkin
Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

OK