Support http2 calls

Reminder to add https://www.python-httpx.org/ support

my own cameras do not have this problem, so I won't be able to test this, update here if you are volunteer to share your camera.

Shared

assuming camera named tuin is yours, you need to give admin permission.

Better now?
I couldnt shareo nly "tuin"?

thanks, better now. but that URL does not make sense at all. Your latest captured picture is from 24th April 2021. I do not think that Eufy is storing these pictures more than couple of days in AWS.
your picture URL: https://zhixin-security-eu.s3.eu-central-1.amazonaws.com/thumb/2021/04/24/station/T8010XXX
my picture URL:  https://zhixin-security-eu.s3.eu-central-1.amazonaws.com/thumb/2022/01/16/station/T8010XXX
@bropat , any idea why this might happen?

moreover, I tried to access with http2 and it generated the same error.
import httpx
client = httpx.Client(http2=True)
r = client.get('https://zhixin-security-eu.s3.eu-central-1.amazonaws.com/thumb/2021/04/24/station/T8010XXX')
print(r)

it generated <Response [404 Not Found]>

resolving this as this is not related to http2 support, you can remove sharing your cameras and share my findings with @bropat while creating an issue on his repository. I am not sure if this is related anything software.

Huh whats the problem then?
I told you i havent got a picture anymore and you guys said it was related to this.
So i dunno whats wrong
You and bropat pointed to this...

Do not forget this is an open source project and everyone here is working on volunteering based, so there is no place to hold responsible anyone. We think it might be reason and we were wrong.
I am not comfortable at all working with you with your overall attitude.

To clarify: The solution with http2 was related to the error 204 No Content and not to 404 Not Found.
In this case, the problem is with Eufy. We cannot pick up what is no longer there.

By any chance, you (@bropat) might know why @skank01 is having very old pictureUrl?

Thx both you guys @bropat and @futakgun for keeping an eye on investigating this !
 ;)

Yeah its like the pictureUrl isnt updating anymore or smth, maybe thats why i dont see it anymore?

Exactly. It is now so old that it has already been deleted from the Eufy Cloud and so you get the 404 Not Found error.
Only Eufy knows why it is no longer updated.

@skank01 in your mobile app, do you get notifications including picture?

@skank01 in your mobile app, do you get notifications including picture?

Good one, it seems not.
Strange
Movementdetection is on though (all motions)
I just tested the movement stuff, but it doesnt detect my movement anymore...
i then looked to my modus, which says im home, maybe thats the reason


implicit type conversion of different index types

Reference Issues/PRs
Fixes #882
What does this implement/fix? Explain your changes.
added the provision of typecasting different types of series indexes such as Int64, Float64, UInt64 and RangeIndex into each other
Does your contribution introduce a new dependency? If yes, which one?
No

Great @Dbhasin1, the doc tests are passing now, just a few more minor comments and we're good to go after that I think!

That's awesome, I'll incorporate your suggested changes asap

hey, @mloning I don't know why the build (macOS-latest, 3.6) check got canceled. Could you give any pointers on how I could resolve this?

Hi @Dbhasin1, I've added the unit test and am happy to merge this now. Let me know if you have any final comments before merging?

Hi @mloning, sorry I couldn't add the unit test in time, got a little engaged elsewhere. yeah it looks good to me, may I know what you did to check whether the time index made sense?

Hi @Dbhasin1 take a look at the file changes here: https://github.com/alan-turing-institute/sktime/pull/892/files

Thanks again @Dbhasin1 for the PR, great work! As said, please reach out again if you want to join the mentoring scheme or have any questions.

Thanks again @Dbhasin1 for the PR, great work! As said, please reach out again if you want to join the mentoring scheme or have any questions.

Thank you @mloning! Yep, will definitely do so!


Support for encrypted payload

User can set an (externally) encrypted payload as described in #22 to be used with Chrome.

Here it is an example on how to use it:
$sender = new PHP_GCM\Sender($api_key);
$payload = Minishlink\WebPush\Encryption::padPayload(json_encode($payload_data), false);

$encrypted = Minishlink\WebPush\Encryption::encrypt(
	$payload,
	$localPublicKey,
	$salt,
	version_compare(phpversion(), '7.1', '>=')
);

$message = new PHP_GCM\Message('push');
$message->publicKey($encrypted['localPublicKey']);
$message->salt($encrypted['salt']);
$message->rawData(base64_encode($encrypted['cipherText']));

$sender->sendNoRetryMulti($message, array($token));


Update Console to match ext standards

We'd like to check all extensions to try to update dependencies, node versions, etc. to ensure that our support is consistent across PF and our extensions.

React 18 support, node 18
Webpack 5 (and general dependencies update)
A11y (at least testing on each PR)
Linting - bump to version 8

@jessiehuff to me it's not clear the exact missing standards. Maybe create some description? If someone else is going to work on it and is aware feel free to ignore.

It seems like as of #35 we are:

Already on React 18 and supporting node 18
Already using Webpack 5
Already running a11y tests on each PR
Already on version 8 of Eslint


linux_zen: 5.9.14 -> 5.10.1

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

/marvin opt-in
/status needs_reviewer
cc @andresilva

Result of nixpkgs-review pr 107003 run on x86_64-linux 1

8 packages marked as broken and skipped:

linuxPackages_zen.ixgbevf
linuxPackages_zen.lttng-modules
linuxPackages_zen.ndiswrapper
linuxPackages_zen.nvidia_x11_legacy304
linuxPackages_zen.phc-intel
linuxPackages_zen.rtl8723bs
linuxPackages_zen.sch_cake
linuxPackages_zen.tbs

25 packages failed to build:

linuxPackages_zen.akvcam
linuxPackages_zen.amdgpu-pro
linuxPackages_zen.anbox
linuxPackages_zen.broadcom_sta
linuxPackages_zen.chipsec
linuxPackages_zen.cryptodev
linuxPackages_zen.dpdk
linuxPackages_zen.ena
linuxPackages_zen.evdi
linuxPackages_zen.mwprocapture
linuxPackages_zen.mxu11x0
linuxPackages_zen.nvidia_x11_legacy340
linuxPackages_zen.nvidia_x11_legacy390
linuxPackages_zen.oci-seccomp-bpf-hook
linuxPackages_zen.rtl8192eu
linuxPackages_zen.rtl8812au
linuxPackages_zen.rtl8814au
linuxPackages_zen.rtl8821au
linuxPackages_zen.rtl8821ce
linuxPackages_zen.rtl8821cu
linuxPackages_zen.rtl88x2bu
linuxPackages_zen.rtl88xxau-aircrack
linuxPackages_zen.rtlwifi_new
linuxPackages_zen.virtualbox
linuxPackages_zen.virtualboxGuestAdditions

47 packages built:

linuxPackages_zen.acpi_call
linuxPackages_zen.asus-wmi-sensors
linuxPackages_zen.batman_adv
linuxPackages_zen.bbswitch
linuxPackages_zen.bcc
linuxPackages_zen.bpftrace
linuxPackages_zen.can-isotp
linuxPackages_zen.cpupower
linuxPackages_zen.ddcci-driver
linuxPackages_zen.digimend
linuxPackages_zen.facetimehd
linuxPackages_zen.fwts-efi-runtime
linuxPackages_zen.gcadapter-oc-kmod
linuxPackages_zen.hyperv-daemons
linuxPackages_zen.intel-speed-select
linuxPackages_zen.it87
linuxPackages_zen.jool
linux_zen (linuxPackages_zen.kernel)
linuxPackages_zen.mba6x_bl
linuxPackages_zen.netatop
linuxPackages_zen.nvidia_x11 (linuxPackages_zen.nvidia_x11_beta)
linuxPackages_zen.nvidia_x11_vulkan_beta
linuxPackages_zen.nvidiabl
linuxPackages_zen.openafs (linuxPackages_zen.openafs_1_8)
linuxPackages_zen.openafs_1_9
linuxPackages_zen.openrazer
linuxPackages_zen.perf
linuxPackages_zen.ply
linuxPackages_zen.r8125
linuxPackages_zen.r8168
linuxPackages_zen.sysdig
linuxPackages_zen.system76
linuxPackages_zen.system76-acpi
linuxPackages_zen.system76-io
linuxPackages_zen.systemtap
linuxPackages_zen.tmon
linuxPackages_zen.tp_smapi
linuxPackages_zen.turbostat
linuxPackages_zen.tuxedo-keyboard
linuxPackages_zen.usbip
linuxPackages_zen.v4l2loopback
linuxPackages_zen.v86d
linuxPackages_zen.vhba
linuxPackages_zen.x86_energy_perf_policy
linuxPackages_zen.xpadneo
linuxPackages_zen.zenpower
linuxPackages_zen.zfs (linuxPackages_zen.zfsStable ,linuxPackages_zen.zfsUnstable)

I guess some new kernel modules need changes to support 5.10.

evdi is fixed in a PR that hopefully will be merged soon.
Also coordination with this?  #106916

linux_latest has been updeted to 5.10 already in master, I'm not so sure whether that bump is important.

It is important for using new kernel features.

Just ran into an error with dex2oatd while building an image with robotnix which I am not able to reproduce on 5.9-zen:
dex2oatd E 12-17 11:47:11  3370  3370 dex2oat.cc:2200] Failed to copy oat file to file: out/soong/cheeseburger/dex_apexjars_unstripped/system/framework/arm/apex.oat: Invalid argument
dex2oatd E 12-17 11:47:11  3370  3370 fd_file.cc:175] File out/soong/cheeseburger/dex_apexjars_unstripped/system/framework/arm/apex.oat wasn't explicitly flushed before destruction.
dex2oatd E 12-17 11:47:11  3370  3370 fd_file.cc:178] File out/soong/cheeseburger/dex_apexjars_unstripped/system/framework/arm/apex.oat wasn't explicitly closed before destruction.
dex2oatd F 12-17 11:47:11  3370  3370 fd_file.cc:180] Check failed: guard_state_ >= GuardState::kClosed (guard_state_=Base, GuardState::kClosed=Closed)

(at the end of the 2h build process of course...)

Currently rebuilding with vanilla 5.10.

@Atemu No, I haven't seen that error message in any robotnix builds before.

Thanks!
The same happens on vanilla 5.10, so not a linux_zen-specific issue. (https://github.com/danielfullmer/robotnix/issues/74)

Oh yeah, should probably also mention over here that the issue above was most likely caused by ZFS and also happens on the vanilla 5.10 kernel.
I didn't test 5.10-zen very much because of this but the kernel itself was working fine when I did use it.

Back in the old days headers were the oldest kernel version available, not the latest, and it still was generally fine.


error while adding multiple proguard directory in release type

FileCollection proGuardFileCollection = files { file('./cproguardfiles').listFiles() }
proguardFiles(proGuardFileCollection)
Folder name is:  cproguardfiles(in project structure )
Error:(23, 0) Cannot convert the provided notation to a File or URI: file collection.
The following types/formats are supported:

A String or CharSequence path, for example 'src/main/java' or '/usr/include'.
A String or CharSequence URI, for example 'file:/usr/include'.
A File instance.
A URI or URL instance.

This is

switch it to
proguardFiles fileTree(dir: "cproguardfiles", include: ["*.pro"]).asList().toArray()

thanks it worked.

although the error is removed but it didn't accept the proguard files added, here is the screenshot of the error
here is the error along with screenshot,
Warning:com.fasterxml.jackson.databind.ext.PathDeserializer: can't find referenced class java.nio.file.Path
Warning:com.fasterxml.jackson.databind.ext.DOMSerializer: can't find referenced class org.w3c.dom.bootstrap.DOMImplementationRegistry
Warning:com.fasterxml.jackson.databind.ext.PathDeserializer: can't find referenced class java.nio.file.Paths
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.Transient
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.Transient
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.ConstructorProperties
Warning:com.fasterxml.jackson.databind.ext.PathDeserializer: can't find referenced class java.nio.file.Path
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.ConstructorProperties
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.Transient
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.ConstructorProperties
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.Transient
Warning:com.fasterxml.jackson.databind.introspect.JacksonAnnotationIntrospector$Java7Support: can't find referenced class java.beans.ConstructorProperties
Warning:okio.DeflaterSink: can't find referenced class org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
Warning:okio.Okio: can't find referenced class java.nio.file.Files
Warning:okio.Okio: can't find referenced class java.nio.file.Path
Warning:okio.Okio: can't find referenced class java.nio.file.OpenOption
Warning:okio.Okio: can't find referenced class java.nio.file.Path
Warning:okio.Okio: can't find referenced class java.nio.file.OpenOption
Warning:okio.Okio: can't find referenced class org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
Warning:okio.Okio: can't find referenced class java.nio.file.Path
Warning:okio.Okio: can't find referenced class java.nio.file.OpenOption
Warning:okio.Okio: can't find referenced class java.nio.file.Path
Warning:okio.Okio: can't find referenced class java.nio.file.OpenOption
Warning:okio.Okio: can't find referenced class org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
Warning:retrofit2.Platform$Java8: can't find referenced method 'boolean isDefault()' in library class java.lang.reflect.Method
Warning:retrofit2.Platform$Java8: can't find referenced class java.lang.invoke.MethodHandles$Lookup
Warning:retrofit2.Platform$Java8: can't find referenced class java.lang.invoke.MethodHandle
Warning:retrofit2.Platform$Java8: can't find referenced class java.lang.invoke.MethodHandles
Warning:retrofit2.Platform$Java8: can't find referenced class java.lang.invoke.MethodHandle
Warning:retrofit2.Platform$Java8: can't find referenced class java.lang.invoke.MethodHandles$Lookup
Warning:retrofit2.Platform$Java8: can't find referenced class org.codehaus.mojo.animal_sniffer.IgnoreJRERequirement
Warning:there were 41 unresolved references to classes or interfaces.
Warning:there were 1 unresolved references to library class members.
Warning:Exception while processing task java.io.IOException: Please correct the above warnings first.
Error:Execution failed for task ':app:transformClassesAndResourcesWithProguardForClientDebug'.

java.io.IOException: Please correct the above warnings first.

Include these in your proguard-rules.pro
-dontwarn com.fasterxml.**
-dontwarn okio.**
-dontwarn retrofit2.**

if i add these lines in proguard-rules.pro, then "{ file('./cproguardfiles').listFiles() }" will be useless, your as well as mine efforts will go in vein.

I don't understand. Can you provide any reference?
What I read about -dontwarn is they are only used to ignore warnings while building. So if you know that some unreferenced class won't create a mess in your project then its totally okay to use these.
http://proguard.sourceforge.net/manual/usage.html

I had the same problem as well.
android {
    ....
    buildTypes {
        release {
            minifyEnabled true
            shrinkResources true
            FileCollection proguardFileCollection = files { file('./proguard').listFiles() }
            proguardFiles(proguardFileCollection)
        }
    }
}

It seem

please add this "proguardFiles fileTree(dir: "proguard", include: ["*.pro"]).asList().toArray()"
and remove these lines,
FileCollection proguardFileCollection = files { file('./proguard').listFiles() }
proguardFiles(proguardFileCollection)

@sauravexodus , means i include these then, what will be the advantage of adding your file as i have to write the code in my own proguard files.

https://code.google.com/p/android/issues/detail?id=212882

@TheGreat0004 line of code solved it for me


mavlink parameter issues to review

param index changing during sync

it appears that some parameters are only marked active lazily and possibly during the first param sync

behaviour with network broadcast resulting in parallel parameter sync

@DonLakeFlyer @dogmaphobic @hamishwillee looking over the mavlink spec I would guess the parameter index is expected to be maintained.
https://mavlink.io/en/messages/common.html#PARAM_VALUE

Unfortunately this index changes in PX4 as new parameters are marked active. This doesn't need to happen after boot is complete, but at the moment it's possible.

The majority of this seems to be the commander preflight checks, which often don't run the first time until after the initial parameter sync.
INFO  [mavlink] send_one: CAL_ACC_PRIME (32 of 560),
INFO  [mavlink] send_one: CAL_BARO_PRIME (36 of 560),
INFO  [mavlink] send_one: CAL_GYRO_PRIME (45 of 560),
INFO  [mavlink] send_one: CAL_MAG_PRIME (62 of 560),
INFO  [mavlink] send_one: COM_ARM_EKF_AB (73 of 560),
INFO  [mavlink] send_one: COM_ARM_EKF_GB (74 of 560),
INFO  [mavlink] send_one: COM_ARM_EKF_HGT (75 of 560),
INFO  [mavlink] send_one: COM_ARM_EKF_POS (76 of 560),
INFO  [mavlink] send_one: COM_ARM_EKF_VEL (77 of 560),
INFO  [mavlink] send_one: COM_ARM_EKF_YAW (78 of 560),
INFO  [mavlink] send_one: COM_ARM_IMU_ACC (79 of 560),
INFO  [mavlink] send_one: COM_ARM_IMU_GYR (80 of 560),
INFO  [mavlink] send_one: COM_ARM_MAG (81 of 560),
INFO  [mavlink] send_one: SYS_HAS_BARO (548 of 560),
INFO  [mavlink] send_one: SYS_HAS_MAG (549 of 560),

As a quick improvement (not the right permanent fix) I'll see if we can have these parameters marked active immediately.

Is QGC checking or monitoring the param count at any point?

param index changing during sync

Parameter index cannot change during sync. Once sync is complete QGC doesn't care about indices.

Is QGC checking or monitoring the param count at any point?

QGC knows if it doesn't get all the parameters from the initial sync. Not really by checking the count, but by checking for indices for which it didn't get a param. It will then re-request this missed params by index.

This really isn't okay then. It's not happening intentionally, but at the moment there's actually no mechanism in place that prevents new params from being marked active (resulting in an index change) during the param sync. In retrospect I bet this explains some of the cases where very slow connections are getting stuck on param sync.
If it's relatively easy I'd consider monitoring the param_count in PARAM_VALUE (https://mavlink.io/en/messages/common.html#PARAM_VALUE), and aborting/retrying the entire sync if there's a change. I'll look for a more fundamental fix within PX4 itself.

The


Certificates import from a source have incorrect/incomplete data when initially created

Version: HEAD
While importing certs from a source, we noticed that upon initial import, the certificates had incorrect/limited set of data.  Specifically,

The Issuer is set to the ORGANIZATION_NAME instead of the name of the issuer
external_id, though included in cert data, is missing
authority_id, though detected and returned in the cert data coming from ourplugin.get_certificates was missing

We traced this back through the code and determined that the data for each certificate changes here:
https://github.com/Netflix/lemur/blob/f3d9513df2468f5c33a6f784e980f01b8a42f29e/lemur/sources/service.py#L27
Looking at CertificateUploadInputSchema, it appears to strip the certificate information down to a different set of keys (owner, notifications, roles, etc.) and the certificate 'body'.
The result is that upon import, as mentioned above, the certs are basically wrong/incomplete
until
When the recurring sync job runs, the certs are all updated, and e.g. issuer is fixed, authority_id is filled in and so on.  We presume this is either as the update is parsed or as the model parses its own cert body, but we haven't tracked that part yet.
The problem with this is that for N minutes (interval of sync cronjob), any initially imported certs are effectively wrong, which can wreak havoc with API integrations.
The expected behavior is that upon import, a certificate looks the same as it does after update, presuming the data has not changed
We might suggest that either:

CertificateUploadInputSchema should not strip out additional valid fields if they exist
Immediately upon import, the certificate model instance should update itself in the same way as when the CLI sync job is run (not sure if this is possible)

Hi, I was able to replicate the issues you've experienced. I've pushed this PR to resolve. Please take a look and feel free to submit another issue or PR if anything is missed or not functioning as intended: https://github.com/Netflix/lemur/pull/1691


Clarification of Connected Collectives

Right now we are using too many confusing terms in reference to connected Collectives, aka member Collectives, and we're not communicating how they work to users.
This is how they appear:

Are they called "Connected Collectives" or "Member Collectives"? I prefer "Connected Collectives" because it's more generic and people will be using this in different ways where 'member' might not fit.
Is the relationship hierarchical or reciprocal? i.e. are the two Collectives in the image above 'child' Collectives of the main one, or are they all connected as peers? I thought we were going to make them peers but we're displaying them in a hierarchy. If they are peers, they should show up on each other's pages, not only the child ones showing on the parent.
The "View Collective" button should have a capital 'C' on Collective.
This whole feature needs to be added to the docs.
I don't think "other ways to contribute" is a good section title. It should be called "Connected Collectives" or whatever term we decide to consistently use.

The decision was to rename everything to Connected collectives (see https://github.com/opencollective/opencollective/issues/3040). There should not be any occurrence of "Member Collective" anymore, I'm going to open a PR to fix that.

Is the relationship hierarchical or reciprocal?

It's hierarchical indeed. They however do show up on both pages, see https://github.com/opencollective/opencollective/issues/2485

This whole feature needs to be added to the docs.

It's already in the docs: https://docs.opencollective.com/help/collectives/connectedcollectives

I don't think "other ways to contribute" is a good section title. It should be called "Connected Collectives" or whatever term we decide to consistently use.

This section also displays events, which is why it's called "other ways to contribute"

Thanks @Betree for some reason it wasn't coming up when I searched docs!

@alanna I've removed all occurrences left for Member Collective, feel free to close if you think everything has been addressed will be addressed in another issue.

Thanks @Betree
My personal opinion is that sections should be modular and not combined, i.e. both Connected Collectives and Events should be their own section so admins can turn them on and off and reorder them as they see fit - we had another recent issue where a user wanted Events to show in the top nav bar, for example.
But I think that's a seperate issue so I'll close this.


Workspace multi-homing with Log Analytics Extension

Hello,
Is it possible to configure Workspace multi-homing with the Log Analytics VM Extension? The JSON schema doesn't show whether that is possible.
When MMA multi-homing was announced in 2016, it was mentioned in the below blog post by @satyavel that "The Azure virtual machine (VM) extensions will be updated with this new capability in June."
https://blogs.technet.microsoft.com/msoms/2016/05/26/oms-log-analytics-agent-multi-homing-support/

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

ID: cefed4e0-440d-18d5-8b8d-4a345f396e9b
Version Independent ID: 2882136f-7fde-685d-c24f-037ee7626667
Content: Azure Log Analytics virtual machine extension for Windows
Content Source: articles/virtual-machines/extensions/oms-windows.md
Service: virtual-machines-windows
GitHub Login: @roiyz-msft
Microsoft Alias: roiyz

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

@satyavel Can you please share your insights on this customer's question? Thanks.

@roiyz-msft @satyavel @MGoedtel Can you please take a look and share if you have any insights on the roadmap for this one?

@Karishma-Tiwari-MSFT @tFable - I'm investigating this now with the PM for the agent and will get back to you shortly.  Thanks.

@MGoedtel Thank you for helping out. Did you hear back from the product team?

@Karishma-Tiwari-MSFT @tFable - I've talked with the PM and needed to confirm something.  I've pinged him again and am waiting for a response.

Hello @MGoedtel
Is there an update on this?
Thanks,
t

I would also very much like to know how to accomplish this within a JSON template. As a CSP we are in desperate need of this functionality.
Thanks in advance.

@alexcastrus I received confirmation through a support ticket that the OMS IaaS extension does not support multi-homing. It is not currently possible to configure the IaaS OMS Extension with two workspaces. The support rep said that there is no indication that this feature is on the roadmap.

@tFable, @alexcastrus, @Karishma-Tiwari-MSFT - I just came back from vacation, so apologies for not getting back sooner.  I can also confirm that ARM does not support configuring the Log Analytics VM Extension for Windows with more than one workspace.  #please-close since this isn't a doc issue.

We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


service-object.d.ts: export declare type Metadata = any;

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
Metadata has no type information. This is slightly unsettling, because if I want to get the generation number after creating a file, I have to type-coerce an any.
For example:
//<EMAIL_ADDRESS>(L16):  export declare type Metadata = any;
//<EMAIL_ADDRESS>(L17):  export declare type MetadataResponse = [Metadata, r.Response];
//<EMAIL_ADDRESS>(L168): File.getMetadata(options?: GetMetadataOptions): Promise<MetadataResponse>;
const [metadata] = await my_file.getMetadata();
// metadata is typed as `any`

Describe the solution you'd like
Better type information on metadata

Hi @iiian thank you for opening this issue. We have plans to work on this in the future and it is currently being tracked by #1817. I am going to close this issue as a duplicate.


Lima uses DNS and proxy settings from en0 instead of the interface of the default route

I thought we had already changed this, but maybe I'm confusing this with the logic in Rancher Desktop that selects the interface to create a bridged network.

This was fixed by #570 afaict.


Support periodic background updates to ensure the app is up to date when brought into the foreground

PR #172.

Fixed in 3ce30772e80ec59be6bcf73c3c3f96b4c5a2d43a.


Added MONO_TLS_PROVIDER env variable to .travis.yml

Prerequisites

[X] I have written a descriptive pull-request title
[X] I have verified that there are no overlapping pull-requests open
[X] I have verified that I am following the Nancy code style guidelines
[X] I have provided test coverage for my change (where applicable)

Description
Our Travis builds recently started failing when we went from 4.8.0 (Stable <IP_ADDRESS>5/df81fe4 Tue Jan 3 15:47:11 UTC 2017) to Mono JIT compiler version 4.8.0 (Stable <IP_ADDRESS>5/038ff4a Mon Jan 9 14:42:31 UTC 2017) (we're grabbing latest published). I was recommended by @akoeplinger to try to add MONO_TLS_PROVIDER=legacy to our env variables to see if that resolves it. If this PR builds on Travis then it should be good to merge.

Looks like it worked 😄 Thanks for reporting this, I'll make sure we're tracking and fixing that exception in the new TLS provider 👍


Improve channel_bind code coverage

change ChannelBind's ID to turn.ChannelNumber.
move channelBindTimeout to StartArguments.

Fantastic improvement! Nice work :)
Also if we make sure we are properly tearing down channels I think we can close out https://github.com/pion/turn/issues/27

Codecov Report

Merging #51 into master will increase coverage by 5.74%.
The diff coverage is 46.66%.

@@            Coverage Diff             @@
##           master      #51      +/-   ##
==========================================
+ Coverage   11.79%   17.53%   +5.74%
==========================================
  Files          16       16
  Lines         670      673       +3
==========================================
+ Hits           79      118      +39
+ Misses        574      531      -43
- Partials       17       24       +7

Impacted Files
Coverage Δ

internal/server/server.go
0% <0%> (ø)
:arrow_up:

internal/server/turn.go
0% <0%> (ø)
:arrow_up:

internal/allocation/allocation.go
35.45% <66.66%> (+31.81%)
:arrow_up:

internal/allocation/channel_bind.go
42.85% <75%> (+42.85%)
:arrow_up:

internal/allocation/permission.go
14.28% <0%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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

Hi @Sean-Der , review again please.
I just add a attribute named permissionLifetime   to server. I think ChannelBind should have the same lifetime as CreatePermission lifetime, so it's 5 minutes for default.

LGTM


Deleting mux project fails

MacOS Sierra 10.12.6
Ruby 2.4.2p198
Tmuxinator 0.9.0
$ mux delete test_project
Are you sure you want to delete test_project?(y/n) y
/usr/local/lib/ruby/gems/2.4.0/gems/tmuxinator-0.9.0/lib/tmuxinator/cli.rb:220:in `block in delete': uninitialized constant Tmuxinator::Cli::FileUtils (NameError)
Did you mean?  FileTest
	from /usr/local/lib/ruby/gems/2.4.0/gems/tmuxinator-0.9.0/lib/tmuxinator/cli.rb:215:in `each'
	from /usr/local/lib/ruby/gems/2.4.0/gems/tmuxinator-0.9.0/lib/tmuxinator/cli.rb:215:in `delete'
	from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
	from /usr/local/lib/ruby/gems/2.4.0/gems/tmuxinator-0.9.0/bin/tmuxinator:15:in `<top (required)>'
	from /usr/local/bin/tmuxinator:23:in `load'
	from /usr/local/bin/tmuxinator:23:in `<main>'

@brandoncordell Did you figure out a fix for this? I'm getting the same error.

@nwshane I just deleted the project file itself (~/.tmuxinator/<project_name> IIRC). I don't remember if the delete command did anything else besides that, but that will work.

@brandoncordell That worked - thanks!

Closing this for now. Please re-open if anyone is still seeing this behavior.


make protocols a mutable list (a concrete ArrayList)

What is the purpose of the change
fix bug
issue: https://github.com/apache/incubator-dubbo/issues/3841
Brief changelog
make protocols a mutable list (a concrete ArrayList)
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #3869 into master will decrease coverage by 0.05%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #3869      +/-   ##
============================================
- Coverage     63.67%   63.62%   -0.06%
  Complexity       71       71
============================================
  Files           709      709
  Lines         31378    31378
  Branches       5071     5071
============================================
- Hits          19981    19965      -16
- Misses         9105     9122      +17
+ Partials       2292     2291       -1

Impacted Files
Coverage Δ
Complexity Δ

...org/apache/dubbo/config/AbstractServiceConfig.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...in/java/org/apache/dubbo/config/ServiceConfig.java
56.58% <100%> (ø)
0 <0> (ø)
:arrow_down:

...n/java/org/apache/dubbo/config/ProviderConfig.java
97.84% <100%> (ø)
0 <0> (ø)
:arrow_down:

.../apache/dubbo/qos/protocol/QosProtocolWrapper.java
64.1% <0%> (-17.95%)
0% <0%> (ø)

...onfig/spring/extension/SpringExtensionFactory.java
80.48% <0%> (-4.88%)
0% <0%> (ø)

.../apache/dubbo/remoting/transport/AbstractPeer.java
65.21% <0%> (-2.18%)
0% <0%> (ø)

...dubbo/remoting/exchange/support/DefaultFuture.java
74.14% <0%> (-2.05%)
0% <0%> (ø)

...he/dubbo/registry/multicast/MulticastRegistry.java
67.87% <0%> (-1.81%)
0% <0%> (ø)

...pache/dubbo/remoting/transport/AbstractServer.java
47.91% <0%> (+1.04%)
0% <0%> (ø)
: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 1706807...585f5e4. Read the comment docs.

@satansk could you help me check this?

@Moriadry one more thing, the type parameters need to be removed, otherwise LGTM

@satansk  yes, I thought we should support jdk 6 and below, I changed as you request. :)

fix whitespace when git push

@satansk What is you opinion on this pull request?

@ralf0131 LGTM, and thank you @Moriadry

my pleasure! and thank you for your help:)


flow-upgrade does nothing

i'm trying to upgrade to the latest flow from 0.48.0
I manually upgraded to 0.52.1 without any issues (no new issues, flow check passes)
Upgrading to 0.53.0 triggers thousands of errors, due to the extensive react changes, so I figured I should use the flow-upgrade tool
I have a large project, with several hundred files. Mostly react code. I am using .js as my extension, and I globalize some of my imports (like React, for instance)
Running flow-upgrade inside my project dir produces this output:
Processing 300 files...
Spawning 3 workers...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
All done.
Results:
0 errors
300 unmodified
0 skipped
0 ok
Time elapsed: 6.780seconds

No files were modified. Still thousands of flow errors. Am I missing something?

I'm getting this too. I have a lot of files, but if I cd into smaller directories and just run a few at a time, it does actually work.
Definitely issue with the package somewhere, but that might help you get around it for now.


pagination fails in cloudflare pages

I'll be using the prevPost and nextPost of https://astro-micro.vercel.app/blog/01-getting-started as reference point.
running this locally,
npm run build
npm run preview

the syntax of the resulting hrefs when viewed in a browser:
prevPost: http://localhost:4321/blog/00-micro-changelog
nextPost: http://localhost:4321/blog/02-blog-collection

Which is working as intended.
But if I open the html file itself seperately ( ./dist/blog/01-getting-started/index.html ):
prevPost: ./dist/blog/01-getting-started/00-micro-changelog
nextPost: ./dist/blog/01-getting-started/02-blog-collection

It somehow appends the target URL to the current URL, resulting in a 404 every time.
This behavior is imitated when building through cloudflare pages (which serves ./dist folder after building).
Are the hrefs being dynamically modified? or have I accidentally made some changes somewhere?

Hi, thanks for opening this issue. I can confirm the PostNavigation.astro component is broken when deployed on Cloudflare Pages. Deployments on Vercel or Netlify are not affected by this issue.
Astro Micro on Cloudflare Pages
When inspected the hrefs appear to be correct and link to the post's relative URL but Cloudflare seems to be appending it to the end of the current URL.
I also tried updating the site in astro.config.mjs but didn't notice a change.
I'll have to investigate further or get in contact with Cloudflare support.

Should be fixed now... lol


UI fix: improve position of add media / add item button in Schema tab

This issue is transferred from a comment in #5050, so it's easier to track separately.
The UI fix in question is to move the "add item" / "add media" button to the left of the schema building window and thus make it more prominent. See screenshots below (context-specific to Wikibase chosen):

Complete wireframes (including development parameters are here): https://xd.adobe.com/view/3ae13acb-7afb-4ea5-8252-351a1622abba-6fb2/
Originally posted by @lozanaross in https://github.com/OpenRefine/OpenRefine/issues/5050#issuecomment-1193187217

Hi @lozanaross @wetneb, as per the new guidelines https://forum.openrefine.org/t/welcome-and-guidelines-to-the-outreachy-ux-design-internship-applicants/567 in OpenRefine Discourse Forum. I would like to be assigned this.

I am not sure there is much design work to do here - are you looking into implementing it instead? The forum post you linked is about design tasks.

I am looking to work on the design. But, if you think there is not much work to do on this issue. Then, I would be happy if you can assign me some issues for design.

I cannot assign you to issues on my own - I do not know what areas of the tool you already master, what your interests and skills are, and so on. See Lozana's post:
https://forum.openrefine.org/t/welcome-and-guidelines-to-the-outreachy-ux-design-internship-applicants/567

Okay, Thank you.

I have made a few changes to the UI. The buttons have been moved according to the XD image. Please confirm if it looks okay.

I am facing slight alignment issues with the remove button. I could use some suggestions on how to improve it.

Could you guide me on how to recreate the website to add both media and items buttons?
Also, I was having issues while aligning the remove button. I could use some help to figure that out.
UI Changes Implemented

Left-aligned 'Add Item' button
Right-aligned 'Saved Schema' and 'Delete Changes' buttons
Added side border to the 'type file name or drag reconciled column' [Let me know if that needs to be reversed]
Increased the width of the div box to cover the whole width (as in the screenshots)
Remove, add term and other buttons aligned
Added border above the Add item button

Please let me know if the current changes look okay. I have attached the link for the UI changes.
https://imgur.com/a/444Cu5f

For me it's easier to review your work if you can open a pull request (even in a draft state if you do not feel confident).

Could you guide me on how to recreate the website to add both media and items buttons as in the XD image?

That would require configuring a wikibase with both mediainfo and item support. You could take an existing Wikibase manifest and tweak it to pretend it has both. I am not aware of a public Wikibase instance which currently uses both those entity types (at least we haven't got any in https://github.com/OpenRefine/wikibase-manifests).


adding automatic language detection

Julia, please review my changes and proof where needed.  Thanks!!!

@mizrachiran : Thanks for your contribution! The author, @juliako, has been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author, @juliako, has been notified to review your proposed change.


[POC] : subdivision by bloc size

Context
The CNES QI team is interested in the possibility of performing block-based coregistration, which is why studies are currently being conducted to test this functionality, referred to as blockwise. At the moment, users must specify the number of subdivisions they wish to apply. However, the QI team would prefer to specify block sizes instead. The goal of this ticket is to propose an implementation of this capability.
We will start the process of managing the size of an overlap between tiles. In this ticket, it will have a default value, and another ticket will be opened later to better manage this overlap.
Proposed Code
Currently, subdivision is handled by the subdivide_array function, so we propose managing block sizes at this level.

Extend Subdivision:
Currently, users input a number, but instead, we could allow them to input a dictionary or list containing two integers for rows and columns, and then calculate the number of subdivisions based on these values.
For example, for an image of size 985x1332:

Scenario 1: Subdivision 64, 8 rows/8 columns, block size of 123 rows by 166 columns.
Scenario 2: Block size of 100x100, 10 row blocks, 14 column blocks, 10*14 = 140 blocks.

Update the Following:

[ ] Update https://github.com/GlacioHack/xdem/blob/main/xdem/coreg/base.py#L3197 so that, based on row and column information, the function calculates the number of subdivisions when the user provides a list [row, col]:  there is an exemple

def subdivide_array(self, shape: tuple[int, ...]) -> NDArrayf:
    """
    Return the grid subdivision for a given DEM shape.
    :param shape: The shape of the input DEM.
    :returns: An array of shape 'shape' with 'self.subdivision' unique indices.
    """
    if len(shape) == 3 and shape[0] == 1:  # Account for (1, row, col) shapes
        shape = (shape[1], shape[2])

    if isinstance(self.subdivision, list):
        nb_bloc_row = np.ceil(shape[0] / self.subdivision[0])
        nb_bloc_col = np.ceil(shape[1] / self.subdivision[1])

        self.subdivision = int(nb_bloc_row * nb_bloc_col)

    return subdivide_array(shape, count=self.subdivision)

[ ] Update the associated docstring.

[ ] Copy a function that allow blocks to overlap

def patchify(arr, nblocks, overlap):
           # manually split with overlap a datacube for parallel computing

           overlap = int(np.floor(overlap))
           patches = []
           nx, ny = np.shape(arr)

           nx_sub = nx // nblocks[0]
           ny_sub = ny // nblocks[1]

           split = [[nx_sub * i, min(nx_sub * (i + 1), nx), ny_sub * j, min(ny_sub * (j + 1), ny)] for i in
                    range(nblocks[0] + 1) for j in range(nblocks[1] + 1)]
           over = [[max(0, l[0] - overlap), min(nx, l[1] + overlap), max(0, l[2] - overlap), min(l[3] + overlap, ny)] for l in
                   split]
           inv = []
           for k in range(len(split)):
               x0, x1, y0, y1 = split[k]
               i0, i1, j0, j1 = over[k]
               patches.append(arr[i0:i1, j0:j1])
               inv.append([x0 - i0, x1 - i0, y0 - j0, y1 - j0])

   return patches, inv, split

Replace the groups variable here by calling function patchify

Tests

[ ] A test should be added to this test with a parameter containing a list (or a dict) of tile sizes for rows and columns.
[ ] Unit tests should be implemented for patchify function

Documentation

[ ] It would be helpful to add a comment in the plot_blockwise_coreg file to inform users that an alternative solution is available.

/ estimate 5d

@adehecq, @rhugonnet
Currently, internal work is being done to test the blockwise method (and its current bug), but we would like to add this specific functionality. What do you think?
@duboise-cnes :)

This is a great idea! Being only able to specify a "number of blocks" is definitely a limitation. Having the option of specifying a "number of blocks" could be retained just for the specific use case (immediately translating it into a size).
For the subdivision of the array: To avoid edge effects during transformations of the chunks, it is usually necessary to use an overlap. I have some old code that does this here (which does not have proper tests written, but was used a lot and checked qualitatively), if can be useful: https://github.com/iamdonovan/pyddem/blob/main/pyddem/fit_tools.py#L1390 (the splitter/stitcher are for subdividing without overlap, and patchify/unpatchify with overlap; all work for a 3D data cube, but should also be applicable to 2D).
The problem is slightly different as a classic split/stitch here, as we don't know in advance the horizontal shift that the coregistration will find for each chunk. So we'd need some kind of splitter (for the fit()) followed by a patchify/unpatchify (for the apply()) that adjusts the size of the overlap based on the transformation to avoid introducing voids.
@erikmannerfelt could have more ideas/insights as he implemented the original functionality :slightly_smiling_face:.

def patchify(arr, nblocks, overlap):
    # manually split with overlap a datacube for parallel computing

    overlap = int(np.floor(overlap))
    patches = []
    nx, ny = np.shape(arr)
    nx_sub = nx // nblocks[0]
    ny_sub = ny // nblocks[1]
    split = [[nx_sub * i, min(nx_sub * (i + 1), nx), ny_sub * j, min(ny_sub * (j + 1), ny)] for i in
             range(nblocks[0] + 1) for j in range(nblocks[1] + 1)]
    over = [[max(0, l[0] - overlap), min(nx, l[1] + overlap), max(0, l[2] - overlap), min(l[3] + overlap, ny)] for l in
            split]
    inv = []
    for k in range(len(split)):
        x0, x1, y0, y1 = split[k]
        i0, i1, j0, j1 = over[k]
        patches.append(arr[i0:i1, j0:j1])
        inv.append([x0 - i0, x1 - i0, y0 - j0, y1 - j0])

    return patches, inv, split

def unpatchify(arr_shape, subarr, inv, split):
    # manually stitch account for split overlap a datacube for parallel computing

    out = np.zeros(arr_shape)

    for k, arr in enumerate(subarr):
        s = split[k]
        i = inv[k]
        out[s[0]:s[1], s[2]:s[3]] = arr[i[0]:i[1], i[2]:i[3]]

    return out

After more thinking, I'm wondering if directly using https://docs.dask.org/en/latest/generated/dask.array.overlap.map_overlap.html would make more sense, even if for now our input arrays are not chunked in-memory.
It would:

Make the functionality natively work out-of-memory on Dask arrays (probably with some small tweaks) the moment we have a dem Xarray accessor,
Work the same on the loaded NumPy arrays that we currently have,
Remove the requirement of having to write unit tests for our custom functions patchify/unpatchify (as map_overlap is already extensively tested in Dask),
(Potentially) Allow us to re-use similar code for other co-registration steps that require Dask mapping with overlap (#525).

The only downside is that Dask is more complex. For instance, we likely won't be able to use directly map_overlap because the fit() function is quite a specific operation, and spits out metadata instead of another array. We'll probably have to map the chunks with overlap in a custom delayed function. But we should be able to re-use existing code for that, for instance we managed a delayed chunking with overlap and atypical output in interp_points here (which is fully tested): https://github.com/GlacioHack/geoutils/blob/e7538d1cd9bec79508fe1452991cbef8c5078bb9/geoutils/raster/delayed.py#L250. And several of us have accumulated enough experience with it to help!
Could be worth it, what do you think? :smile:

After quick reading, I am not sure to understand completely all. Maybe in two phases:

first resolving bug and subdivision by bloc size simply
secondly discuss further on dask integration. maybe in another issue ?

I have discussed with @guillaumeeb from CNES who have more knowledge on dask usage than me. Do you have some insights on this dask impact proposed by @rhugonnet ?  A good way to be compatible with dask would benefit the project, i agree.

An additional point I just thought of: If resolving the bug involves removing the warp_dem function, that's for the best. It is likely responsible for artefacts seen in #584, and it would allow to remove scikit-image as a dependency altogether (I opened #654).
Agree on the two phases.
My main point was that we maybe shouldn't lose too much time implementing and testing a custom patchify function examplified in the PR description above, when we can use the one existing in Dask (independently of actually having Dask support in terms of memory usage/parallelization for now).
So in that sense, Dask would also be slightly part of the first phase but simply as a replacement of the patchify function  (which also runs on normal arrays).
Then, in a second phase, we could refine and test out-of-memory behaviour, parallelization, and other Dask parameters (for which we would already have the right code structure).

Hi everyone, sorry for the delay in response.
I totally concur with @rhugonnet analysis!! When I first read the original post of this issue, I directly thought of Dask and map_overlap as a solution! Complying with Dask interfaces would enable you to do blockwize operations for bigger than memory inputs, as well as distributed and parallel processing. And as said, Dask already implements part of your needs!
The important point, even if doing this in two phases, would be to already think of Dask as a design goal. For example, subdivisions as expressed as chunk shapes (nbrows, nbcols) in Dask, but I think this is what you are aiming at.
One last warning about map_overlap, this can complexify a Dask graph in big cases, there might be optimizations to look for on Dask side, but let's see that afterwards.


Ray should be deactivated if testing

Describe the bug
If you running phpunit/pestphp eg via Github Actions ray might not be installed which will cause the issue that tests will run endless. (happend to me and costs me 2 hours of github action time)

Versions
Ray version (you can see this in "About Ray"): 1.0.0

spatie/laravel-ray package version: ^1.1

PHP version:
Laravel version (if applicable): 8
To Reproduce
Steps to reproduce the behavior:

Add ray to a laravel project
Add ray.php to project with flag active is true
Add github action where you run the tests
=> Test didn't fail but run endless. (if phpunit isn't setup to fail early)

Expected behavior
Should not run in testing mode or should not block github actions.

This has been fixed in the latest release of spatie/ray (that exception won't be thrown anymore).

This has been fixed in the latest release of spatie/ray (that exception won't be thrown anymore).


Rails 5

http://guides.rubyonrails.org/5_0_release_notes.html
Things pending

Check if it works in production env
Fix forbidden(403) in test_runs_controller_test.rb
Fix feature tests
Tests appear to be slow

Is there something forcing us to upgrade? e.g. unsupported gems for 4.2
Do we gain any significant benefits from the upgrade at this point? e.g. faster ActiveRecord, smaller memory footprint, less objects in memory, etc.

Bare in mind that we don't have a staging environment. We need to test this in staging, with staging workers, webhooks, database etc. It seems like an opportunity to set this up.

We gain access to the ActionController::API, so that our API has no unecessary middleware(e.g. SessionMiddleware). This might make the API faster
We gain access to the ActionCable which might be a solution for live updates - We have to figure out if it is worth it.
We now have better syntax for controller tests(E.g. instead of post :create, {id: 2} we have the more explicit post :create, params: {id: 3}.
We gain access to the redirect_back helper that has a fallback location when the referrer doesn't exist


Documentation - SEE ALSO links are broken for all section of Command Reference

Bug reports
All of the SEE ALSO links inside the Command Reference section are dead. It is not just for cilium prefilter SEE ALSO section. See #2733.
Title
Broken SEE ALSO links for all sections of cmdref in documentation.
How to reproduce the issue
Some example links are mentioned below:

http://cilium.readthedocs.io/en/latest/cmdref/cilium/#see-also
http://cilium.readthedocs.io/en/latest/cmdref/cilium-health/#see-also

Likewise, all SEE ALSO links from http://cilium.readthedocs.io/en/latest/cmdref are non-functional.

Looks like the links are nesting within the current path, eg the link on prefilter page:
http://cilium.readthedocs.io/en/latest/cmdref/cilium_prefilter/cilium.html
This should actually be:
http://cilium.readthedocs.io/en/latest/cmdref/cilium.html

Looking at the latest docs, this problem seems to still be present. Reopening.

@joestringer I tried this locally using docker container and the issue seemed to be fixed.

@iamShantanu101 yep, but for some reason the same fix doesn't work on the readthedocs, so if you go to the online site, eg:
http://docs.cilium.io/en/latest/cmdref/cilium_bpf_proxy/
The links are still broken.
Further investigation required.

@iamShantanu101 yep, but for some reason the same fix doesn't work on the readthedocs, so if you go to the online site, eg:
http://docs.cilium.io/en/latest/cmdref/cilium_bpf_proxy/
The links are still broken.
Further investigation required.

I see that they (and all the other see also links I saw) are working again now, so I'm closing this issue.


Better format for listing days "service not provided on"

Currently, there is a list of dates like:
Service not provided on:
Mon, Jul 4, 2016
Mon, Sep 5, 2016
Thu, Nov 24, 2016
Fri, Nov 25, 2016
Sat, Dec 24, 2016
Sun, Dec 25, 2016
Sat, Dec 31, 2016
These could be grouped to make them more concise and take up less space:
Service not provided on:
Jul 4, Sep 5, Nov 24-25, Dec 24-25, Dec 31, 2016
@antrim What do you think? Do you have a better suggested format?

That's terrific!
Also, it wouldn't be hard for us to add a GTFS field in calendar_dates.txt,
holiday_name, if that could support further utility for this feature (now
or later).

I really like the holiday_name feature idea.
On Wed, Sep 21, 2016 at 1:08 PM, trilliumtransit<EMAIL_ADDRESS>wrote:

That's terrific!
Also, it wouldn't be hard for us to add a GTFS field in calendar_dates.txt,
holiday_name, if that could support further utility for this feature (now
or later).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/brendannee/gtfs-to-html/issues/19#issuecomment-248727815,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHPstERhYVPFA9cs6q3Hh4QAXGRsMlNbks5qsY68gaJpZM4KDOId
.

holiday_name could work and wouldn't be too hard to implement, but I'd need to add it as an optional field to the node-gtfs library for it to get imported. Since we'd still need to list the actual dates (no one really knows exactly when easter or thanksgiving falls) is it worth having a custom field for this?

I'm not sure I agree. Well, I agree that no one knows when easter or thanksgiving falls ahead of time. But I think that some one is considerably more likely to remember on Thanksgiving that there's no service if they're told there's no service on thanksgiving as opposed to on november 24.

Good point - if you think it would be valuable to be able to name holidays, lets implement it. Would the output then look like:
Service not provided on:
Independence Day (Jul 4), Labor Day (Sep 5), Thanksgiving (Nov 24-25), Christmas (Dec 24-25), New Years (Dec 31)
What is the best way to indicate the year?  Put it after each date?
Let me know if you have a better idea for the exact formatting.

My thought:
if holiday_name exists: then just Independence Day, Labor Day, Thanksgiving, Day after Thanksgiving, Christmas Eve, Christmas, New Years Eve
if holiday_name doesn't exist, then as you suggested above: Jul 4, Sep 5, Nov 24-25, Dec 24-25, Dec 31, 2016

I pushed an update to support holiday_name in node-gtfs and an update to use it in gtfs-to-html.
Here is a modifed calendar_dates.txt for Sonoma County that you can use to see this new feature in action. calendar_dates.txt
The output for Route 22 is
Service not provided on: Fourth of July, Sep 5, 2016, Thanksgiving, Christmas, Christmas Eve, Christmas, New Years Eve
Let me know what you think.

calendar_dates.holiday_name will start showing up in new Trillium GTFS feeds now.


bug in head.html

Hi there. I'm having trouble building the site (Ubuntu 20.04, Hugo extended v0.68.3) due to a bug in head.html
Is this a BUG REPORT or FEATURE REQUEST?:
bug
What happened:
Building sites … ERROR 2020/09/13 22:31:43 render of "home" failed: execute of template failed: template: _default/list.html:6:6: executing "_default/list.html" at <partial "head.html" .>: error calling partial: "/home/momar/Documents/websites/syna-start/themes/syna/layouts/partials/head.html:55:124": execute of template failed: template: partials/head.html:55:124: executing "partials/head.html" at <resources>: can't evaluate field PostProcess in type interface {}

How to reproduce it (as minimally and precisely as possible):
git clone --recurse-submodules https://git.okkur.org/syna-start
npm install -g postcss-cli
hugo

Environment:

Hugo version:  v0.68.3/extended linux/amd64 BuildDate: 2020-03-25T06:15:45Z

PostProcess from Hugo is only supported in Hugo with versions v0.69+. This should work with any version above v0.69+ and postcss-cli installed (as you already seem to have).
Let us know, if that resolves the issue.

Postcss-cli should not be mandatory with v0.17.4


insert missing set_xcode_and_swift_versions

The two failures look unrelated (test failures), so I think this one can go in.


[1.21] [bug] When Using Accessories Trinkets Compatibility Layer Items Disappear on world save

When loading a world items placed in trinkets slot disappear when loading a world, loading a world that was saved without the compatibility layer keeps items.

Oh, I see the problem. There was a issue within how I port the reading code that led to issues and will push a simple fix.

Uploaded a fix for such.


Do not shape and render null terminator

What does the pull request do?

This PR ensures we do not try to shape and render null terminators. This matches what WPF is doing.
This PR reverts changes from here #17004
What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[x] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

This seems to work only if the null char is the first character in a line?
(e.g. "\0Foo\0Bar" still has the second null rendered)


update to freedesktop runtime 18.08

The freedesktop platform is 18.08. Is there something else that needs to be updated or can we close this now?

fixed in: https://github.com/flathub/io.lbry.lbry-app/commit/8f35ca5dc4149ab28803e56d520bc03a4dbd1651


Fix compile warnings

Thank you! This is awesome. I'm going to take a closer look as soon as I can. I'm not that familiar with why some of the changes were made so I'll need to do some research.

I mostly added pin operator.
If you assigned a variable and then immediately used it in a match, I just assumed you wanted it to be matched on, otherwise you assigned it for no reason.

Looks great! Thanks!

@jesseshieh Could we get a new version pushed to hex with this fix? Thanks!

Oh sure. Sorry about that. I'll do that as soon as I can.

Okay, published as v0.1.1
https://hex.pm/packages/master_proxy


file/annotation specific cwd

Implementation is about what you'd expect, though there is an ambiguity around absolute paths. One option is to resolve absolute paths relative to the project, and the other is to resolve them as absolute paths.
I decided to resolve absolute paths as system-absolute paths, because the "project" directory is currently not really stable.
Resolution order goes as follows:

Current cwd
Markdown file folder
Frontmatter cwd
Annotation cwd

@christian-bromann

I decided to resolve absolute paths as system-absolute paths, because the "project" directory is currently not really stable.

How do you feel about this? Do you think using primarily relative files will be sufficient for now

🤔 that's interesting, I sort of assumed that the markdown file base dir is top of the priority stack?
The absolute path seems like a rare edge case that almost should be discouraged.

@sourishkrout

🤔 that's interesting, I sort of assumed that the markdown file base dir is top of the priority stack?

The way I described it is somewhat confusing. The resolution process goes down the list top to bottom; if it finds an absolute path, it uses that, and otherwise it resolves relative to the previous path. If the thing in the list doesn't exist, we skip to the next one.
It is internally possible in the code-base for a code-block to run "detatched" from a file which is why I included the cwd in the list. In all runnable files, however, resolution effectively starts from the markdown file base dir, since that is an absolute path, so it will overwrite the cwd in the resolution path.
Does that make sense?

The absolute path seems like a rare edge case that almost should be discouraged.

Until runme has a clear notion of what is a "runme project" at a file-system level (like a .runmerc configuration file) I'm personally wary of trying to resolve absolute paths relative to project root. Since then the ability to run the markdown file depends not just on the markdown file, but also how and from where it is run (in this case where the user selects for --project). More broadly, module resolution is a tough problem - TypeScript is a good case study.
Let me know if you think it is worth coming up with a solution for project-relative addressing in the short-term. Otherwise, in the meantime, I think treating absolute paths as system absolute paths is at least consistent with intuition.
I agree that this is probably not desired by many (though it would have use for the "local run-book" scenario?) For shared projects, I agree users should be encouraged to use relative paths for now.

Roger that on both 👍, @mxsdev.


[Suggestions] New PronounDB Features

Just a few quick ideas I thought of completely randomly. Felt like a waste to not share them.
Happy to cook up some concepts to show you guys if you wish. :)
Thanks!
Custom Pronoun Support:
Allow users to input their own custom pronouns, ensuring inclusivity for all gender identities.
Educational Resources:
Incorporate educational materials about gender identity and pronouns to help users understand the importance of using correct pronouns and fostering inclusivity.
`Pronoun Usage Statistics:
Offer users insights into their pronoun usage over time, highlighting trends and promoting awareness of language habits.
Pronoun Pronunciation Guide:
Provide audio recordings or phonetic spellings for pronouns to assist users in pronouncing them correctly. This could be especially helpful in conjunction with the Custom Pronoun Support.

This is already mentioned in the readme as to why this will not be a thing
This one kind of exists with the Pronouns 101 page, and I think pronouns.page does a very great job of having tons of resources I think linking to them is the best thing to do here
I thought about it, but I currently don't keep track of historical data and one thing I'm afraid of is the user count being too small and stats being able to be usable to infer data about people in particular which is something I'd rather like to avoid if possible
Why not, though once again pronouns.page does a very good job already so I'm not sure

Makes sense, happy to have a go at them via a pull request if that's something you want to see,
Also just realised that PronounDB uses black text for websites, even when they are on dark mode so might fix that in the pull.

@TobezDev I just made a pull request to fix this on Twitter (haven't noticed it on other websites though): https://github.com/cyyynthia/pronoundb.org/pull/115

Also just realised that PronounDB uses black text for websites, even when they are on dark mode so might fix that in the pull.

Version 0.14.2 is being rolled out with Twitter injection fixed (finally...)
As for the other points, I'm unsure what to do with this issue (see my previous remarks) 🤷🏻♀

Well as this issue is overly broad in scope I'll just close it. For the reference:

Custom pronouns support will not be added, as mentioned in the README
I'm not against having some educational resources. There's the "Pronouns 101" page which I wrote a while ago to help people who just got introduced to the concept of pronouns but nothing more. I'm not against extending the /wiki/ section of the website, but I personally don't have the time to maintain such thing. I will take the time to review PR adding such things if they come up. Feel free to open a new issue for this point specifically.
While I am myself a fan of graphs, I am dealing with sensitive data and have a responsibility to be careful with what I do with it. Some sets (like it/its, or neos whenever they finally get added to the site) are very low usage which is a problem, as it makes it possible to infer data about individuals specifically as the aggregation doesn't mix enough data together.
Unsure. It may have some uses, but considering there will not be custom pronouns I'm unsure how useful that would be. Maybe with neos, but then again I think handing this type of things off to pronouns.page is a better alternative as they have a much more mature dataset.


Mapping pending to in-progress

I've found sometimes Github actions sends a pending deployment that never resolves to a successful deployment, causing the deployments view to show an in-progress spinner forever.
I think the cause of this was simply committing two commits to master in quick succession, causing the first deployment to remain in pending.

Hey @mattcolman,
I've tried to reproduce this error and have experienced a different behaviour. When running two GitHub workflows in quick succession, the JIRA card shows X incomplete builds and the deployments view shows the workflow as pending. When the workflow has run successfully and you refresh the page, all builds look normal. Could you give me the steps to reproduce this issue and a screenshot of what you are experiencing?
At times, we are finding some builds are not appearing and the incomplete builds number is incorrect. We are looking into this as a separate issue.
Thanks for your time raising and discussing this issue with us.
Yvonne

Hey @mattcolman,
As we haven't heard from you in a while, I'll be closing this issue. If you'd like us to look into this further, please feel free to reopen this issue.


Not able to load module correctly if path contains single quote.

As you can see in the image below, I have created a path which contains single quote in it(C:\Users\manojkumar\Documents\PowerShellTesting\team's size\4.3.1-preview\MicrosoftTeams). Users are facing issues during time of importing cmdlets which are AutoRest generated. Parsing error as you can see in the image below -

It looks like it needs to be handle in PsHelper.cs file, as mentioned in the given image.

Fixed in<EMAIL_ADDRESS>


C4 explosions arent rendered for other players

C4 will only make a noise and explosion on the client that detonated it. The C4 can still kill players however which can lead to some confusion.

Fixed in 65463dc


remove component "is" parameter

This prop affects overrides, and can cause problems. E.g:
component A {
  render span {
    span el
  }
}
component B {
  render A {
    span el {

    }
  }
}
component C {
  render B {

    // Target B.el, or A.el??
    override el {
      style {
        color: red;
      }
    }
  }
}

☝ this is an issue with the DSL, not the syntax here. The DSL needs to be shaped such that components encapsulate elements, and are not elements themselves

Wontfix since the DSL will be removed in favor of the AST


0.4.1

Maximum Lines property in StateChartDebugger is not working.
Very minor problem but wanted to let you know :D
I also rly like new Settings tab.

Ahh the joys of late night coding. Yep I forgot to feed the parameter into the ringbuffer. Thanks for letting me know.


Always decode error messages before persisting them into the FJR

Fixes #8403
Added the same fix to the stringification of the exception as well, very likely redundant, but I'm happy provided it fixes this issue.
Honestly speaking, I do not see how it happened. Every error persisted in the FJR goes through the def addError method, which was properly fixed in the past (making sure ANY error messages are sanitized before persisted in the FJR):
https://github.com/dmwm/WMCore/pull/8524
This fix only apply if we get an error message which is not a string, but another object type (I don't think it ever happens, but I'm out of ideas).
For the record, this was the report/job that caused this issue:
2019-03-20 08:58:47,478:140143375185664:INFO:AccountantWorker:Handling /data/srv/wmagent/v1.1.20.patch3/install/wmagent/JobCreator/JobCache/pdmvserv_task_TOP-RunIIFall18wmLHEGS-00207__v1_T_190124_121044_6304/TOP-RunIIFall18wmLHEGS-00207_0/JobCollection_314448_0/job_2287826/Report.0.pkl
and in order to reproduce this failure, one can:
badErr = {'details': "<@========== WMException Start ==========@>\nException Class: CmsRunFailure\nMessage: Error running cmsRun\n{'arguments': ['/bin/bash', '/srv/job/WMTaskSpace/cmsRun1/cmsRun1-main.sh', '', 'slc6_amd64_gcc700', 'scramv1', 'CMSSW', 'CMSSW_10_2_7', 'FrameworkJobReport.xml', 'cmsRun', 'PSet.py', '', '', '']}\nCMSSW Return code: 8001\n\n\tModuleName : WMCore.W\xffMSpec.Steps.WMExecutionFailure\n\tMethodName : __init__\n\tClassInstance : None\n\tFileName : /srv/job/WMCore.zip/WMCore/WMSpec/Steps/WMExecutionFailure.py\n\tClassName : None\n\tLineNumber : 18\n\tErrorNr : 8001\n\nTraceback: \n\n<@---------- WMException End ----------@>", 'type': 'WMAgentStepExecutionError', 'exitCode': 8001}

from json import JSONEncoder
from WMCore.Wrappers.JsonWrapper.JSONThunker import JSONThunker
encoder = JSONEncoder()
thunker = JSONThunker()
thunked = thunker.thunk(badErr)
encoder.encode(thunked)

or load it from the original job report:
from WMCore.FwkJobReport.Report import Report

jobReport = Report()
jobReport.load('Report.0.pkl')
jsonFWJR = jobReport.__to_json__(None)
badStr = jsonFWJR["steps"]["cmsRun1"]["errors"]

Report was saved in
cmst1@vocms0282:/data/srv/wmagent/current/alan
I'm removing it now and restarting the component.

This is going to be tricky to test, basic tests are Ok, but to make sure it works, only time can answer.


overload mul! for gpu arryays

Codecov Report

Merging #167 (40c5c4e) into master (d96f434) will decrease coverage by 5.99%.
The diff coverage is 24.24%.

@@            Coverage Diff             @@
##           master     #167      +/-   ##
==========================================
- Coverage   76.50%   70.51%   -6.00%
==========================================
  Files          20       20
  Lines         613      675      +62
==========================================
+ Hits          469      476       +7
- Misses        144      199      +55

Impacted Files
Coverage Δ

src/compat/gpuarrays.jl
39.42% <24.24%> (-26.37%)
:arrow_down:

src/utils.jl
93.93% <0.00%> (-3.04%)
:arrow_down:

src/componentarray.jl
79.20% <0.00%> (-2.69%)
:arrow_down:

src/similar_convert_copy.jl
82.50% <0.00%> (-2.50%)
:arrow_down:

src/array_interface.jl
81.91% <0.00%> (-1.25%)
:arrow_down:

src/show.jl
3.92% <0.00%> (+0.07%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


node-gyp is unable to find msbuild if VS2019 is installed.

Node Version: node 10.15.1 npm 6.4.1
Platform: Windows Server 2019
Compiler: msbuild 15.9.21+g9802d43bc3

Verbose output (from npm or node-gyp):
Exit code: 1
Command: node-gyp rebuild
Arguments:
Directory: D:\a\1\jest\node_modules\weak
Output:
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp http GET https://nodejs.org/download/release/v10.15.1/node-v10.15.1-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.15.1/node-v10.15.1-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v10.15.1/SHASUMS256.txt
gyp http GET https://nodejs.org/download/release/v10.15.1/win-x86/node.lib
gyp http GET https://nodejs.org/download/release/v10.15.1/win-x64/node.lib
gyp http 200 https://nodejs.org/download/release/v10.15.1/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v10.15.1/win-x86/node.lib
gyp http 200 https://nodejs.org/download/release/v10.15.1/win-x64/node.lib
gyp info spawn C:\ProgramData\Chocolatey\bin\python2.EXE
gyp info spawn args [ 'D:\\a\\1\\jest\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=2015',
gyp info spawn args   '-I',
gyp info spawn args   'D:\\a\\1\\jest\\node_modules\\weak\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'D:\\a\\1\\jest\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\VssAdministrator\\.node-gyp\\10.15.1\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\VssAdministrator\\.node-gyp\\10.15.1',
gyp info spawn args   '-Dnode_gyp_dir=D:\\a\\1\\jest\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=C:\\Users\\VssAdministrator\\.node-gyp\\10.15.1\\<(target_arch)\\node.lib',
gyp info spawn args   '-Dmodule_root_dir=D:\\a\\1\\jest\\node_modules\\weak',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'D:\\a\\1\\jest\\node_modules\\weak\\build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args   '/clp:Verbosity=minimal',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=x64' ]

I have also tried to install VS2017 build tools on the machine in addition to VS 2019 and node-gyp still tries to find msbuild under the VS2019 install.  The issue is due to VS2019 having a different location for msbuild form VS2017.  It puts it under C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin instead of C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\15.0\Bin

I've just hit this, too. For those who want a temporary workaround, hand-editing the file configure.js in node-gyp appears to work. I changed line 161 from this:
variables['msbuild_path'] = path.join(vsSetup.path, 'MSBuild', '15.0',
to this:
variables['msbuild_path'] = path.join(vsSetup.path, 'MSBuild', 'Current',
then reran:
node-gyp configure

@zhulika could you maybe submit a PR for this?

I'm a C/C++ programmer. I'm not confident enough with Javascript or node-gyp to be able to implement something that detects the version of VS that is installed and adjust the output accordingly.

@zhulika @chrisrpatterson I wasn't comfortable touching configure.js plus I needed something that I can use to fix it in out build system now, so I created this temporary workaround in PowerShell. All it does is create a shim: MSBuild\15.0\Bin\MSBuild.exe -> MSBuild\Current\Bin\MSBuild.exe. Works for me so far.

I have sent PR #1715.

As a side note, if we open "Visual Studio cmd for vs2019" and run node-gyp from it, it will detect MSBUILD.exe correctly, but most of the created projects will require v14.1 toolset and default one shipped with vs 2019 is v14.2

error MSB8020: The build tools for Visual Studio 2017 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install Visual Studio 2017 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution"

With MSBuild being on the PATH (after running vcvars before compiling), my setup was able to find MSBuild correctly, however, I get the error as above. I ended up having to edit configure.js to use the platform toolset v142 in order to get mine to work.

set path=%path%;C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin

as a workaround yes.
but I've never had MSbuild in my path before.

I've edited the configure.js file on line 161 to 'Current' rather than '15.0' and I still get the error with a path pointing to '15.0'.

This still appears to be a problem, and the older Visual Studio versions aren't available anymore as far as i can tell:(

Older versions of VS are still available. Scroll down to Older Versions on this page (https://visualstudio.microsoft.com/downloads/), it leads to: https://visualstudio.microsoft.com/vs/older-downloads/
Or use Chocolatey, a package manager for Windows based on Nuget. Cheers, and hope this bug is resolved soon

Being addressed in https://github.com/nodejs/node-gyp/pull/1762.

node-gyp v5.0.0 is out with Visual Studio 2019 support. It's not yet integrated into npm so it has to be installed manually. This should do it:
npm install --global node-gyp@latest
for /f "delims=" %P in ('npm prefix -g') do npm config set node_gyp "%P\node_modules\node-gyp\bin\node-gyp.js"

That is, install node-gyp globally and make the npm config variable node_gyp point to node-gyp.js.

How to undo this after node-gyp is integrated into npm
npm uninstall --global node-gyp
npm config delete node_gyp

Apologies if I'm being stupid but I don't think that this works, either. I ran the script:
D:\work\gml>npm install --global node-gyp@latest
D:\Program Files\nodejs\node-gyp -> D:\Program Files\nodejs\node_modules\node-gyp\bin\node-gyp.js                          06b5.lock for D:\Program Files\nodejs\node_modules\.staging
+<EMAIL_ADDRESS>updated 1 package in 6.637s

D:\work\gml>

then tried to build a native addin on a machine that has VS2019:
D:\work\gml\serenity\0.2\src\serenityNode>node-gyp build
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp info spawn D:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe
gyp info spawn args [
gyp info spawn args   'build/binding.sln',
gyp info spawn args   '/clp:Verbosity=minimal',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=x64'
gyp info spawn args ]
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: spawn D:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe ENOENT
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
gyp ERR! stack     at onErrorNT (internal/child_process.js:456:16)
gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:84:9)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_modules\\node-gyp\\bin\\node-gyp.js" "build"
gyp ERR! cwd D:\work\gml\serenity\0.2\src\serenityNode
gyp ERR! node -v v12.4.0
gyp ERR! node-gyp -v v5.0.0
gyp ERR! This is a bug in `node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR!     <https://github.com/nodejs/node-gyp/issues>

Why is it trying to find MSBuild here:
D:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\15.0\Bin\MSBuild.exe

when it should be looking here:
D:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe

?
Is there something else that I should have done (obvious to most but I'm new to this so probably not obvious to me)?

I think that the problem was down to my PC. I had so many node-gyp installations plastered all over this PC and it seems that it was using a copy that it shouldn't have. I have eliminated all of the obsolete versions and it is now building OK with your script applied.
Apologies for the false alawm.

node-gyp v5.0.0 is out with Visual Studio 2019 support. It's not yet integrated into npm so it has to be installed manually. This should do it:
npm install --global node-gyp@latest
for /f "delims=" %P in ('npm prefix -g') do npm config set node_gyp "%P\node_modules\node-gyp\bin\node-gyp.js"

That is, install node-gyp globally and make the npm config variable node_gyp point to node-gyp.js.
How to undo this after node-gyp is integrated into npm
npm uninstall --global node-gyp
npm config delete node_gyp

Hi,
I'm a bit new here and having the same issue ...
I ran the command "npm install --global node-gyp@latest", which installed v5.0.2, as recommanded
But when I run "npm install --verbose", I get "gyp info using<EMAIL_ADDRESS>So i guess I need to run
for /f "delims=" %P in ('npm prefix -g') do npm config set node_gyp "%P\node_modules\node-gyp\bin\node-gyp.js"
but where/how do I run such a command?
I'm developing with VsCode, and if I run this command in the console, I get an error ...

@jeromesubs that command is for a cmd shell, but you're probably getting a PowerShell terminal inside VSCode. Try this one:
npm prefix -g | % {npm config set node_gyp "$_\node_modules\node-gyp\bin\node-gyp.js"}

this seems like a really weird solution but i was able to fix it by doing the following in an administrator powershell:
cd "C:\Program Files\nodejs\node_modules\npm\node_modules"
npm i -g node-gyp@latest
npm i node-gyp@latest

had this problem on fresh installs of VS 2019 on two different laptops and this has fixed them both.

@PaulGG that will cause you issues when uninstalling or updating Node.js, expect node-gyp to stop working in the future. Changing the installation under C:\Program Files\nodejs\ is always a bad idea.
The correct solution for PowerShell is:
npm install --global node-gyp@latest
npm prefix -g | % {npm config set node_gyp "$_\node_modules\node-gyp\bin\node-gyp.js"}

Having finally upgraded to node-gyp 5.0.3 on Windows 10, I started getting the infamous Error: Cannot find module %AppData%\npm\node_modules\node-gyp\bin\node-gyp.js, caused by node_modules\npm-lifecycle\node-gyp-bin being pushed on top of my PATH by npm, exactly as described here.
None of the existing remedies I've found and tried could solve this issue for me, including installing the latest windows-build-tools. Here's exactly what I tried, in the following order:

manually clean up mess and duplicates in System PATH and User PATH environment vars
npm uninstall -g node-gyp
npm uninstall -g npm
choco unistall nodejs
reboot
remove %AppData%\npm folder
remove %AppData%\npm-cache folder
choco install nodejs
npm install -g npm@latest
npm install -g node-gyp@latest
npm install -g windows-build-tools

I was still getting the missing node-gyp.js error. What did help was to properly set npm config set node_gyp to point to the correct node-gyp.js, as suggested above by @joaocgreis. Yet somehow his script didn't work properly for me (as well some other PowerShell/Batch scripts I tried).
Eventually, I've come up with the following PowerShell 6 one-liner that did the trick for me:
pwsh -Command npm config set node_gyp "`u{22}$(Join-Path $(npm root -g) -ChildPath 'node-gyp\bin\node-gyp.js')`u{22}"

Hope this helps others. I'd still recommend going through the above bullet list for clean troubleshooting.

My solution was running this command before npm install:
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe"

Using yarn instead of npm fixed this for me shrug

2019-11-30T10_41_01_335Z-debug.log
Pls how to fix this

@zeeterv, try this.

Not sure if this has been suggested before, if so apologies. It's not a fix, but will do the job
Simply use the Visual C++ toolset for the command-line shipped with VS2017.
From the terminal you can launch vcvars64.bat (or vcvars32.bat )file and then keep using the terminal to build:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat"

Install python and set env var PYTHON to C:\Python27\python.exe
npm install --g node-gyp@latest
In VS'19 make sure you've checked "MSVC v141 - VS 2017 C++ x64/x86 build tools" under "Desktop dev with C++" and installed
npm config msbuild_path C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exe
Add "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MSBuild.exe" as system env variable.
Now run "npm install"

Fourth point might be redundant. This worked for me, hope it works for you as well.
Thanks.

Worst issue I've run into in a good while.
None of the above solved it for me. I had to simply use Visual Studio Installer , to modify installation to include "Desktop Development with C++" option.
Simple.
Then it explained an error, though it found the precise path of 2019, it was still using a blank msvs_version.
npm config set msvs_version "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise"
Worked instantly.

My solution was running this command before npm install:
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe"

for others who do not use VSC Enterprise (I have community) - the my path is
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exe"

Still a problem in 2021. I wish there was a way to backport compatibility shims, so the ancient version of node-gyp in my dependencies would just work without futzing with the path vars.

@ariccio if I remember correctly, I think that I ended unsetting anything in the NPM config and used Visual studio installer to add MS build tools v2017 to my system next to the exidting v2019...

Guys this is fixed 2 years ago, you just need to install latest node-gyp globally and set npm to use that, detailed in a cm above:

node-gyp v5.0.0 is out with Visual Studio 2019 support. It's not yet integrated into npm so it has to be installed manually. This should do it (only need to be run once):

Windows Command Prompt

npm install --global node-gyp@latest

for /f "delims=" %P in ('npm prefix -g') do npm config set node_gyp "%P\node_modules\node-gyp\bin\node-gyp.js"

Powershell

npm install --global node-gyp@latest

npm prefix -g | % {npm config set node_gyp "$_\node_modules\node-gyp\bin\node-gyp.js"}

That is, install node-gyp globally and make the npm config variable node_gyp point to node-gyp.js.

How to undo this after node-gyp is integrated into npm

npm uninstall --global node-gyp

npm config delete node_gyp


✔ questions 1 - 4 passing

that'll do Aloysious, that'll do

         🚧 What we do this time? 🚧   Q1
----------------------------------------------------
[x]  Wrote a function named raisedToTheThird
that took in an array of numbers and returned a
new arrayof each of those numbers raised to the
3rd power

         🚧 What ELSE did we do ? 🚧  Q2
----------------------------------------------------
[x] Wrote a function named addOne that,
given an array of numbers, used map to return
a new array with each value simply
incremented by 1.

             🚧 And thennnnnn? 🚧  Q3
----------------------------------------------------
[x] Wrote a function named addQuestion that,
given an array of strings, used map to return a new
array containing each string followed by a
question mark character.

                 🚧 Finally. 🚧  Q4
----------------------------------------------------
[x] Wrote a function named forLoopTwoToThe that,
given an array of integers as input, iterates over
the array and returns a new array.
[x] The returned array contains the result of raising
2 to the power of the original
input element.
💻 Github
💼 Linkedin


resolves import error

@JWittmeyer this has some strange merge conflicts, which i believe come from different commit stages in the submodule


Stale content

This page seems to be old content. May want to redirect to: https://docs.microsoft.com/en-us/azure/data-lake-analytics/data-lake-analytics-data-lake-tools-get-started

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

ID: 4ebe1955-18ed-4113-91ff-49bdad69d049
Version Independent ID: beeadd08-2457-18b8-218d-8e7d373b2ec4
Content: Develop a U-SQL database project - Azure Data Lake
Content Source: articles/data-lake-analytics/data-lake-analytics-data-lake-tools-develop-usql-database.md
Service: data-lake-analytics
GitHub Login: @yanancai
Microsoft Alias: yanacai

@omarv74 which page are you talking about? Are you referring to the entire article Develop a U-SQL database project - Azure Data Lake? The page has not been updated for a while as we did not add new features to it. However, the content is still valid, and I believe there are still customers referring to this doc for U-SQL database project development. I don't think we should redirect this doc to the get started doc.

@himanshusinha-msft  can I ask why the issue is assigned to me? I don't have any context of this. And I think the doc content is up-to-date and doesn't need any change.

@yanancai  My apologizes  I  misunderstood the comments from you on this , going ahead and closing the issue now .


http: remove envoy.reloadable_features.http_default_alpn runtime flag

Signed-off-by: Snow Pettersen<EMAIL_ADDRESS>Risk Level: Low
Testing: n/a
Docs Changes: n/a
Release Notes: Deprecation note
Fixes #14646

Didn't find any test coverage for this flag (oops?) but we'll see how CI goes


Add support for split tests with random distributions

@kmendes FYI This PR needs to be rebased

@kmendes Did you ever see the message by @thedrow?
You need to handle the merge-conflict, so currently the PR is just stuck.

Was this resolved or simply rejected?

@thedrow Agree, 3 years and no words seems odd

@thedrow @nj I'm sorry for not being clear. Rejected for now. PR was never rebased and others didn't show enough support for this feature.
But if you feel confident that this feature would add a lot of value and any of you rebases these changes and creates a new PR for them, I'd be happy to merge it.


perf(postgres): optimize the expired rows cleanup routine in postgres connector

Summary
This PR tries to optimize the expired rows cleanup routine in the Postgres strategy connector.
Currently, the cleanup logic is managed by a timer.every, which will run multiple DELETE sub-queries in one big query and delete those rows that got expired. Concerns have been raised about such queries may lead to high load on database if the number of expired rows is large. The idea originates from FTI-4746 and KAG-516, but the code that got changed in this PR may not be directly relevant to the root cause of the production issue. The logic itself is definitely worth some optimizing after all.
This PR brings the following changes to the cleanup logic:

Makes the cleanup interval configurable. A new config parameter pg_expired_rows_cleanup_interval is introduced to control the interval of triggering the timer.
A cluster mutex is added to ensure that in a "traditional" deployment cluster, only one cleanup will be running at the same time.
The big query which contains multiple DELETE sub-queries has been split into multiple queries, with more obvious logging, so that if any errors are encountered, the table which caused such an error can be located easily. And each query will use its own connection so that if any of them got timed out on Kong's side(for example, waiting for locks in the Pg but the connection itself is timed out), the following cleanup will not be affected.
Debug logging which shows the total time usage of each table is added.
Batch delete is implemented in every DELETE query to avoid letting extremely slow query consuming database resources.

Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

Optimize the expired rows cleanup routine in Postgres connector.
Add a new config parameter pg_expired_rows_cleanup_interval to control the interval of expired rows cleanup routine.

Issue reference

FTI-4746
KAG-516

Question: what if we drop the Postgres cleanup routine altogether, and instead create Postgres triggers on entities that have ttl=true? We could run the trigger AFTER INSERT. I think that would be a better solution. This issue only affects traditional deployments. Very little the Control Plane and none the Data Planes or DBless.

Hmm I'm a bit concerned about the AFTER INSERT trigger(if we're going to add a DELETE * instead of a batch deleting), it could also lead to more concurrent queries and high resource usage, right? Say there is a user's scenario that oauth2_tokens are created frequently, since hybrid mode cannot be used under the oauth2 case, there will still be some users having large traditional clusters deployed.
But yes, dropping the background timer and adding a trigger(and batch deleting in the function perhaps?) is more straightforward, we could re-consider this option after the CP-DP refactor thing happens. What do you think about it? @bungle

The ttl fields on all tables (where schema says ttl=true) need proper indexes as they are also used with SELECTs.

@bungle Could you please show me where can I change to make this guarantee? I can confirm that all these ttl enabled tables have a proper index on ttl fields in our migration files, but I don't know if there is any DAO mechanics that can guarantee the schema field is indexed.

@bungle Could you please show me where can I change to make this guarantee?

Yes, just by looking our Postgres schemas that ttl=true tables have the index. If they don't we need to add index for ttl.  We have added them during the years, but there might still be some entities that are missing Postgres index.

Hmm I'm a bit concerned about the AFTER INSERT trigger(if we're going to add a DELETE * instead of a batch deleting)

The batch deleting as you added here is basically Postgres feature. Thus it is easy to add it in trigger delete too.

it could also lead to more concurrent queries and high resource usage, right? Say there is a user's scenario that oauth2_tokens are created frequently, since hybrid mode cannot be used under the oauth2 case, there will still be some users having large traditional clusters deployed.

We can tune this inside trigger. E.g. delete only sometimes etc.
What I mean that the current logic is very complicated as in this PR. I think in most cases what we already had is better than what we have here. So then we have probably a single pain point that is oauth2 tokens. Perhaps oauth2 tokens ttling should be implemented differently while the rest are fine with current or triggers. Perhaps triggers can be made to work with oauth2 tokens problem too.

superseded by #10389