STX Address Derivation Should Match BTC Wallets

Currently, every STX address can derive a BTC address.
The problem is, the BTC address we derive does not use the same algorithm as BTC wallets. While every BTC wallet may use a different derivation algo, we should be able to match them based on what people use.
Essentially, current Bitcoiners can't get the same BTC address with the same seed phrase on their Hiro/Xverse wallet.
Every Bitcoiner's BTC address should be able to be used as a STX address, without even having Hiro wallet
e.g. I could use the BTC wallet of Pomp, Nic Carter, etc and send them dope NFTs that they can use later with the same seed phrase and Hiro. Easy onboarding!

I certainly agree with this principle, and we expect to build Bitcoin support into Hiro Wallet in a way that ensures that the user can take their seed phrase / Secret Key to other (Bitcoin) wallets and see their addresses seamlessly.
Though since we haven't built this support yet, "the BTC address we derive does not use the same algorithm as BTC wallets" is not an outstanding problem with the Hiro Wallet per se? Is that perhaps unique to Xverse?

Essentially, current Bitcoiners can't get the same BTC address with the same seed phrase on their Hiro/Xverse wallet.

The BTC address in Xverse is a P2SH-P2WPKH segwit address using the standard m/49’/0’/0’/0/0 path. Meaning you can get the same BTC address using the same key in other BTC wallets as long as you choose P2SH segwit.
And we are looking into allowing users to send/receive NFTs using that Bitcoin address, as Bitcoin NFTs should be.

How do we implement it on Gamma so that I can send an NFT to someone's BTC address or send BTC to someone's STX address?

Or I could send an NFT to Bitcoiner address without them having Xverse yet and then they just sign up for Xverse?

I certainly agree with this principle, and we expect to build Bitcoin support into Hiro Wallet in a way that ensures that the user can take their seed phrase / Secret Key to other (Bitcoin) wallets and see their addresses seamlessly.
Though since we haven't built this support yet, "the BTC address we derive does not use the same algorithm as BTC wallets" is not an outstanding problem with the Hiro Wallet per se? Is that perhaps unique to Xverse?

should we move this issue over to Stacks.js then?

Gamma has already implemented the translation.
You can type in the BTC address and the site will do the C32 translation(Stacks) but the displayed address at signing shown will be the C32 translation

You can do the conversion yourself easily from the CLI with: stx convert_address I sent Adam Back a boombox awhile ago

No they couldn't just sign up to Xverse and access these assets. Problem is that neither the Hiro wallets or Xverse allow derivation paths outside of the SLIP-44 standard. In Xverse case, it doesn't allow deriving more addresses beyond the 0 address_index

Hiro wallet you can easily modify and build the wallet without the 5757 coin_type, but defeats the point.
You also need to rely on the "Bitcoiner" supplying the address is aware of the derivation path to the address they gave you.
A powerful feature here for both wallets the ability to import an xPub/zPub and scan for assets.
The Hiro Wallet should also have a toggle setting to switch between /5757'/ & /0'/ coin_type

In Xverse case, it doesn't allow deriving more addresses beyond the 0 address_index

That is not true anymore. You can generate BTC/STX addresses in Xverse beyond the first index.

A powerful feature here for both wallets the ability to import an xPub/zPub and scan for assets.

I feel like 90% of the people using NFTs will have no idea what an xPub/zPub is.
Wallets using different derivation paths is for sure an issue. I don't think there's an easy solution here. But perhaps a web-based NFT viewer that takes BTC addresses would be sufficient to trigger the aha moment. And then if they want to access the asset they can install Xverse wallet.

This should be an issue on the SIP repo!


Session Driver Cookie Middleware Ordering Issue

I had an issue that Session Driver cookie was not working due to the re-ordering of the middleware as defined in Kernel.php as $middlewarePriority.
The cookie driver requires the AddQueuedCookiesToResponse middleware. It is also required that this middleware is before the StartSession middleware, as the AddQueuedCookiesToResponse writes the cookies that are queued up by StartSession to the response as post processing.
Now in my case mutiple middleware groups were merged together and the priority ordering re-ordered the middlewares to have first the StartSession and afterwards the AddQueuedCookiesToResponse, causing the session data not be sent back as a cookie.
Can \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class, be added to Illuminate\Foundation\Http\Kernel.php to ensure the ordering is always correct?

Is this a feature request? Because the issue template is missing. If so, feel free to attempt a PR.


Frontend with vitepress

A part of #2
Local development for a vitepress app.

Initialize a vitepress project.
mkdir document
cd document
yarn init
mkdir docs && echo '# Hello VitePress' > docs/index.md
Add some scripts to `package.json`
{
  "scripts": {
    "docs:dev": "vitepress dev docs",
    "docs:build": "vitepress build docs",
    "docs:serve": "vitepress serve docs"
  }
}


fix:support for setting SNI in zuul

Introduce property <ribbon_client>.ribbon.SNI
Needed for Supporting Origins that need SNI

@carl-mastrangelo can you please check this? It appears like the builds don't work any more

cc: @artgon


paper and code implementation are different

Thank your for nice job!
I notice that you use dot-product to measure simlarity between prediction in paper while use KL_div in code.
paper:

code:
https://github.com/Albert0147/NRC_SFDA/blob/1c2616039635710fa704d24a5cf7cfc9b47172bc/office-home/train_tar.py#L315-L317
I wonder why do you do this?
Thanks!

Hi, if you check pytorch document of kl_div, you will find they are indentical, without log here is just dot product.

...thanks 🤣

I have checked pytorch document,  https://pytorch.org/docs/stable/generated/torch.nn.KLDivLoss.html#torch.nn.KLDivLoss and I do not find them identical. As clearly stated in the document loss_pointwise = target * (target.log() - input), there is a log term. The difference can be seen easily as follows.
A = torch.randn((1, 1, 3))
A = torch.nn.functional.softmax(A, dim=-1)  # B, KM, C
# tensor([[[0.3066, 0.1715, 0.5219]]])
B = torch.randn((1, 1, 3))
B = torch.nn.functional.softmax(B, dim=-1)  # B, KM, C
# tensor([[[0.3418, 0.3557, 0.3025]]])

C1 = torch.nn.functional.kl_div(A, B, reduction='none').sum(-1)
C2 = (A * B).sum(-1)

(C1 - C2).norm()
# tensor(1.7436)

The author comments that "# kl_div here equals to dot product since we do not use log for score_near_kk". I have no idea what that means.

target here is just a scalar without gradient. Optimizing this obviously equals to optim - target * input

OK. that makes sense.


[BUG] Cannot use azure-ai-openai with Android

Describe the bug
java.lang.ExceptionInInitializerError in Android studio
I wanna run azure openai sdk at Android, but when I created OpenAIClient, app broke down bacause of ReflectionUtils.
Exception or Stack Trace
java.lang.ExceptionInInitializerError
at com.azure.core.implementation.ReflectionUtils.getLookupToUse(ReflectionUtils.java:119)
at com.azure.core.util.ExpandableStringEnum.getDefaultConstructor(ExpandableStringEnum.java:88)
at com.azure.core.util.ExpandableStringEnum.$r8$lambda$SMtq8BJfA6t_qJk1WfhslLPTCwc(ExpandableStringEnum.java:0)
at com.azure.core.util.ExpandableStringEnum$$ExternalSyntheticLambda1.apply(R8$$SyntheticClass:0)
at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1716)
at com.azure.core.util.ExpandableStringEnum.fromString(ExpandableStringEnum.java:68)
at com.azure.core.http.HttpHeaderName.fromString(HttpHeaderName.java:60)
at com.azure.core.http.HttpHeaderName.(HttpHeaderName.java:88)
at com.azure.core.http.HttpHeaderName.fromString(HttpHeaderName.java:56)
at com.azure.core.http.policy.RequestIdPolicy.(RequestIdPolicy.java:33)
at com.azure.ai.openai.OpenAIClientBuilder.createHttpPipeline(OpenAIClientBuilder.java:279)
at com.azure.ai.openai.OpenAIClientBuilder.buildInnerClient(OpenAIClientBuilder.java:259)
at com.azure.ai.openai.OpenAIClientBuilder.buildClient(OpenAIClientBuilder.java:382)
at com.lee.openai.azure.AzureOpenAIClientKt$azureOpenAIClient$2.invoke(AzureOpenAIClient.kt:27)
at com.lee.openai.azure.AzureOpenAIClientKt$azureOpenAIClient$2.invoke(AzureOpenAIClient.kt:23)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at com.lee.openai.azure.AzureOpenAIClientKt.getAzureOpenAIClient(AzureOpenAIClient.kt:23)
at com.lee.openai.azure.AzureOpenAIClientKt.flowText(AzureOpenAIClient.kt:31)
at com.lee.ailanguage.MainActivity$testAzureOpenAI$1.invokeSuspend(MainActivity.kt:25)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at androidx.lifecycle.DispatchQueue.drainQueue(DispatchQueue.kt:74)
at androidx.lifecycle.DispatchQueue.enqueue(DispatchQueue.kt:111)
at androidx.lifecycle.DispatchQueue.dispatchAndEnqueue$lambda$2$lambda$1(DispatchQueue.kt:99)
at androidx.lifecycle.DispatchQueue.$r8$lambda$1ME-FmJywCV2uxhp8ajM5a9C_oI(DispatchQueue.kt:0)
at androidx.lifecycle.DispatchQueue$$ExternalSyntheticLambda0.run(R8$$SyntheticClass:0)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:8073)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:620)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1011)
Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@ce6128c, Dispatchers.Main.immediate]
Caused by: java.lang.RuntimeException: Unable to use package-private MethodHandles.Lookup constructor.
at com.azure.core.implementation.ReflectionUtils.(ReflectionUtils.java:84)
... 33 more
Caused by: java.lang.NoSuchMethodException: java.lang.invoke.MethodHandles$Lookup. [class java.lang.Class]
at java.lang.Class.getConstructor0(Class.java:2332)
at java.lang.Class.getDeclaredConstructor(Class.java:2170)
at com.azure.core.implementation.ReflectionUtils.(ReflectionUtils.java:76)
To Reproduce
env:
Android studio version: Android Studio Electric Eel | 2022.1.1 Patch
jvm: Runtime version: 11.0.16+8-b2043.64 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
implemente azure openai : com.azure:azure-ai-openai:1.0.0-beta.2
create any OpenAIClient and test, then break.
Code Snippet
OpenAIClientBuilder()
.credential(AzureKeyCredential(AZURE_OPEN_AI_KEY))
.endpoint(AZURE_OPEN_AI_ENDPOINT)
.buildClient()
The killer is AzureKeyCredential.
Expected behavior
No break at least.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: Android
IDE: Android studio Electric Eel | 2022.1.1 Patch
Library/Libraries:  com.azure:azure-ai-openai:1.0.0-beta.2；com.azure:azure-core:1.40.0
Java version: Android studio need Java11 ,but at Gradle I set both sourceCompatibility and targetCompatibility to java8
App Server/Environment: Nothing
Frameworks: Android

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.
I followed https://github.com/Azure/azure-sdk-for-java/wiki/Android-Support to config Android projects
Android studio need at least java11, but I can tell ReflectionUtils.java is for java8.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

Hi @leejay001, this issue is similar to #35756 where I mention that the Azure SDKs for Java aren't guaranteed to work with Android, nor do we offer support for them working with Android.

I was hitting this until I updated the API version to >= 26.  In my build.gradle my minSDK is 26 with targetSdk of 33. I had already enabled Java 8 desugaring with the JavaVersion.VERSION_1_8 for sourceCompatibility and targetCompatability.

Thanks for the update @georgeps22.
Updating to API version 26 and above makes sense as it appears Android added support for MethodHandle, and other java.lang.invoke APIs, in API version 26.
https://developer.android.com/reference/java/lang/invoke/MethodHandle

Thanks for the help, @georgeps22 and @alzimmermsft. However, I had already set the min SDK to 26, as indicated by Android Studio before this bug occurred. Additionally, I have enabled Java 8 desugaring using JavaVersion.VERSION_1_8 for sourceCompatibility and targetCompatibility. I suspect that the issue may be related to the Gradle build tools I used, which are:
gradle-7.5-bin.zip
id 'com.android.application' version '7.4.2' apply false
id 'com.android.library' version '7.4.2' apply false
id 'org.jetbrains.kotlin.android' version '1.8.0' apply false
id 'org.jetbrains.kotlin.jvm' version '1.8.0' apply false
These require Java 11 or above, but ReflectionUtils is only compatible with Java 8. I found this issue on GitHub: [https://github.com/Azure/azure-sdk-for-java/issues/29046 ] ,where @alzimmermsft mentioned that there was a Java 9+ version of ReflectionUtils, but it cannot be found currently.

@JonathanGiles could you please assist here since you're working on Android right now and Alan is away

@JonathanGiles -- I am facing the same issue - I am using java version 11, is there no hope of this to work azure-ai-openai SDK to work with Java 11?

@JonathanGiles -- I am facing the same issue - I am using java version 11, is there no hope of this to work azure-ai-openai SDK to work with Java 11?

This issue relates to usage on Android, whereas your comment appears unrelated to Android. Can you please file a new issue if you're specifically running into issues when running this library on Java 11 (without Android), as this library absolutely should work under Java 11. If you are asking about Android support, then your question should probably be asked in the context of Android API levels. Our target is to have some degree of baseline support from Android API level 26.

Hey, just hit the same error and unfortunately the solution provided by @georgeps22 didn't help, can we expect any changes regarding this issue in the coming weeks? 🙏

Android is not the primary target of the libraries in this repository. Whilst effort has been made to test against Android 26+ occasionally, this is not something we prioritize and cannot guarantee will work at all times. Closing this issue as won't fix.


Admin UI Update

Implement rest api & shell script for directly managing system configuration.
Implement basic bootstrap single page app for interacting with rest api
Add basicauth security for admin context

I haven't yet reviewed the BBoxManage.sh script, but wanted to leave these comments as I may not have a chance to review that for another 24h.

Thanks for the great review. I'll start on these items and look for your review of the shell script. Be kind, as shell scripting is not something I do a whole lot of :)

Looks great. Thanks!


Using the posterior distribution?

Hi, I'm interested in using bayespy to infer a posterior, and then use it to evaluate the predictive distribution, or else a MAP estimate if that isn't possible. Can this be done?

Hi! Yep, BayesPy infers an approximate posterior distribution. See docs for details:

https://www.bayespy.org/user_guide/quickstart.html
https://www.bayespy.org/user_guide/plot.html#posterior-parameters-and-moments

In order to make predictions, you can create a model which contains both the things you observer and the things you want to predict. Then, you'll get the posterior distribution of the things you want to predict too. Alternatively, you can first fit a model for the observations and fit it. After that, re-use the parameter nodes you want in a new predictive model.


Windows build errors

/imgui/src/extension_imgui.cpp
Line 89: use of undeclared identifier ‘GL_CLAMP_TO_EDGE’
Line 90: use of undeclared identifier ‘GL_CLAMP_TO_EDGE’
Line 1663: use of undeclared identifier ‘gl3wInit’; did you mean ‘glfwInit’?
Line 1664: use of undeclared identifier ‘GL3W_OK’

Works: https://github.com/britzl/extension-imgui/actions/runs/5875584726/job/15932110295


getting started guild fails

I followed the steps at https://github.com/grafana/tanka and it fails with the following error :
tk show environments/loki
Evaluating jsonnet: RUNTIME ERROR: couldn't open import "ksonnet-util/kausal.libsonnet": no match locally or in the Jsonnet library paths
	/Users/cameronbraid/loki-config/vendor/promtail/promtail.libsonnet:1:11-49	thunk <k> from <$>
	/Users/cameronbraid/loki-config/vendor/promtail/promtail.libsonnet:5:1-2	$
	main.jsonnet:1:18-54	thunk <promtail> from <$>
	main.jsonnet:3:1-9	$
	During evaluation

I can see that ksonnet-util is a dependency in vendor/promtail/jsonnetfile.json but it doesn't seem to be installed

Hi! You are right, it should be installed automatically. However, Tanka does not handle dependencies itself yet, we are using jsonnet bundler for this. Can you check your jb first and if it is okay file an issue with them?

https://github.com/jsonnet-bundler/jsonnet-bundler/issues/43

According to https://github.com/jsonnet-bundler/jsonnet-bundler/issues/43#issuecomment-541569015 you can't jb install a file

jb was able to do that before, added a comment to your issue. For now, the changes in #96 should resolve that

This issue is bigger than expected previously. As it will probably need collaboration of both projects, Tanka and jsonnet-bundler, we will need to think thoroughly about the final solution to avoid breaking changes for most users. Discussion is open in #100, closing this in favor of the former one


<EMAIL_ADDRESS>Fix dependency URLs

Obviously, both the URLs and the files' corresponding hashes.

[x] I have read the Contributing Guide.

/verify


Protocol version 32 is not supported yet by this client.

Getting Protocol version 32 is not supported yet by this client. and I'm running 2.1.5.
Any ETA support for newer protocols?

I just started trying to poke around with OrientDB and I am also getting this when running 2.1.8. Specifically, pyorient.exceptions.PyOrientWrongProtocolVersionException: Protocol version 32 is not supported yet by this client.

Hi guys, protocol 32 is already supported by pyorient.
The issue is in the pypi repository.
I apologize for this. Please, for now clone the github repository untill pypi will be fixed.
It works.


symlink of file to itself succeeds as NOP, should fail with OSError Errno 2

import pyfakefs.fake_filesystem
import os
fs = pyfakefs.fake_filesystem.FakeFilesystem()
fs.CreateDirectory('/Volumes')
fs.CreateDirectory('/Volumes/ramdisk')
fs.CreateDirectory('/Volumes/ramdisk/test')
os0 = pyfakefs.fake_filesystem.FakeOsModule(fs)
component0 = "alpha"
path0 = "/Volumes/ramdisk/test"
path1 = path0 + "/" + component0
path0 = path1 + "/" + component0
os0.symlink(path0,path0)
os fails the symlink with OSError and Errno 2, pyfakefs succeeds.

If you change it to not be a self-symlink, there's also an issue:
component0 = "alpha"
path0 = "/Volumes/ramdisk/test"
path1 = path0 + "/" + component0
path0 = path1 + "/" + component0
os0.symlink(path1,path0)
Basically, symlink is not checking existence of the path early enough and exiting if it doesn't exist.
Not an exciting error, but holding up aggressive symlink testing.  Exception types look to be matching for all tested operations other than symlink, under the "1 open file descriptor" constraint.

Yes, hopefully the symlink issues are soon over... Will check this over the weekend. I'm currently working on  another issue (tempfile removal) and hit a road block there, so I want to get this done first (before I start dreaming about symlinks...).

Sounds good, I'll hold off a bit.  It turns out that this one also stops checking for symlink problems without checking failure equivalence, since it allows some symlinks that should fail to do something, as in this case:
import pyfakefs.fake_filesystem
import os
fs = pyfakefs.fake_filesystem.FakeFilesystem()
fs.CreateDirectory('/Volumes')
fs.CreateDirectory('/Volumes/ramdisk')
fs.CreateDirectory('/Volumes/ramdisk/test')
os0 = pyfakefs.fake_filesystem.FakeOsModule(fs)
component0 = "alpha"
path0 = "/Volumes/ramdisk/test"
path1 = "/Volumes/ramdisk/test"
path2 = path0 + "/" + component0
component1 = "alpha"
path3 = path2 + "/" + component1
try:
os0.symlink(path1,path3)
except Exception as e:
print "FAILED WITH",e
result = ([p for p in os0.walk(path2,topdown=True,followlinks=False)])
print result


fix(router) regex path matching not considered with exact path match

Summary
This is a sister-PR for #4152, and makes similar adjustments to path matching.
The added test case shows the problem.

Replaced by https://github.com/Kong/kong/pull/4775


fix: DEV-1852: Fix missing labels on video regions

Hi @Gondragos!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/1005

/git merge develop


Interpretation of type Any & T [continuation]

As github sucks for long thread this is merly the continuation of https://github.com/CarliJoy/intersection_examples/issues/31.
Please consider opening new issues if you start discussion on new topics, so issues don't get too long.

Thanks @CarliJoy, it's a good idea.
I feel like we're getting somewhere - the proposal currently on the table seems to have few disadvantages. I'll prepare something in the repo that summarises the advantages, and the two potential issues pointed out by @erictraut. Perhaps it's worth opening separate threads for each of these.


Notes filtered based on file type and topics

Shift all fetching to the backend as much as you can


PE-35372 add --remove-expired option to prune command

Add --remove-expired option to prune command which will check for expired certificates in inventory.txt and/or in the signed directory and remove them from CRL.

Validated manually by adding expired certs to inventory.txt and signed directory.

@nmburgan Can you review the changes?


[RFC] New blog post: It's programs all the way down

DO NOT MERGE! Pretty complete draft I think, but a draft nonetheless. Please give feedback :-)

Am I right in assuming that this is basically an "announcement" for more posts to come? If so, yay!
Travis failure is because of wrong date in the post file name.
Pending review :+1:

@adelbertc What's the status on this? Would be happy to merge with feedback addressed :smile:

Comments addressed, date updated, should be OK now. @S11001001 I amended the series name to "Monadic EDSLs" - what do you think of that?

Let's do this on Wednesday the 21st to give folks time to yell at me/look over #116 :)

@adelbertc Just merge it yourself when you're ready :wink:

@larsrh Merged!


Feature/sdxconsole2 heartbeat to healthcheck

What? and Why?

What does this pull request change/fix? Why was it nessessary?
Changed SDX console 2.0 heartbeat feature to health check end point

Checklist

[ ] CHANGELOG.md updated? (if required)

Think you have the wrong merge target - this should be targeting the branch 2.0 rather than master

 Create Health Checkpoint for SDX Console 2.0


added support for Matrix Combinations Plugin

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


Not working

Not working on MacOS
package.json
{
    "scripts": {
        "start": "node ./index.js"
    },
    "dependencies": {
        "bumblebee-hotword-node": "0.2.1"
    }
}

index.js:
const Bumblebee = require('bumblebee-hotword-node');
const bumblebee = new Bumblebee();

bumblebee.addHotword('bumblebee');

bumblebee.on('hotword', function (hotword) {
	console.log('Hotword Detected:', hotword);
});

bumblebee.start();

Node.js v18.8.0:
npm start

> start
> node ./index.js

(node:65329) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
TypeError: Failed to parse URL from /Users/xxx/Desktop/test/node_modules/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.wasm
TypeError: Failed to parse URL from /Users/xxx/Desktop/test/node_modules/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.wasm
/Users/xxx/Desktop/test/node_modules/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.js:65
						throw ex
						^

RuntimeError: abort(TypeError: Failed to parse URL from /Users/xxx/Desktop/test/node_modules/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.wasm). Build with -s ASSERTIONS=1 for more info.
    at process.abort (/Users/xxx/Desktop/test/node_modules/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.js:486:11)
    at process.emit (node:events:513:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

Node.js v18.8.0

Node.js v16.18.0, v14.20.1
npm start

> start
> node ./index.js

/Users/xxx/Desktop/test/node_modules/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.js:65
						throw ex
						^

Error: spawn rec ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn rec',
  path: 'rec',
  spawnargs: [
    '-q',             '-c',
    '1',              '-r',
    '16000',          '-t',
    'wav',            '-V0',
    '-L',             '-b',
    '16',             '-e',
    'signed-integer', '-'
  ]
}

I can confirm the same error message exists on Linux + node 18.
However, after downgrading to node 14, the exception is gone. By the way I'm using the prebuilt version provided by microsoft mcr.microsoft.com/devcontainers/javascript-node:14

Adding to this, confirmed not working on WSL Ubuntu + node 18.
untimeError: abort(TypeError: Failed to parse URL from [REDACTED]/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.wasm). Build with -s ASSERTIONS=1 for more info.
    at process.abort ([REDACTED]/bumblebee-hotword-node/lib/porcupine-v1.9/pv_porcupine.js:486:11)

Was this ever solved? Also having this issue on my end on my Macbook after setting node to 14.15.5.


Investigate Exemplars

Grafana has a feature with the prometheus datasource called "exemplars" which allows users to link from metrics to traces in tempo. It would be interesting to explore how we might be able to support something similar with Opensearch.
Some questions to explore in a design doc:

If a user had opensearch metrics and opensearch traces set up, is there a way to link from one to another?
Is there a way to link between different datasource types (ex prometheus metrics to opensearch traces)
Is this functionality already possible with datasource plugins or does work have to happen on a grafana plugin sdk level to support this?

This was awaiting https://github.com/grafana/opensearch-datasource/issues/192 which is almost there!

The above issue is now complete so this is unblocked.


Bug: I can't go from "basic equalizer" to advanced.

hello, good day.
I can't go from "basic equalizer" to advanced. I can't change the audio output either. And the menu looks like the screenshot I'm taking.
I have MacOs Sierra 10.12.6
Thank you very much.

It's a common issue with older version of macOS.
Is the UI still broken if you open https://ui-v1.eqmac.app/ with Safari browser?

It's a common issue with older version of macOS.
Is the UI still broken if you open https://ui-v1.eqmac.app/ with Safari browser?

Hello! No, it doesn't work.

@Damiortiz can you please try opening eqMac again to see if it works now?

@Damiortiz can you please try opening eqMac again to see if it works now?

Now it works, it even looks like it should. When I switch to advanced equalizer it closes only after 2 seconds. (Sorry my bad English)

So issue closed then

thank you very much!


Using Bridge Link component with React Router Dom Link component

I'd like to use the functionality of the Link component from react-router-dom with the styling of the Link component from bridge. Any way to do that? I'm currently doing this:
import { Link as RRLink } from 'react-router-dom'
import { Link } from '@hack4impact-uiuc/bridge'

const MyLink = ({ id }) => (
  <RRLink to={`/workspace/${id}`}>
    <Link as="p">View Workspace</Link>
  </RRLink>
)

This does have the desired functionality, BUT I get errors printing to the console about nesting a tags, since this generates something along the lines of:

Is there a better fix for this? BTW, really enjoying working with this design system, great job to the team!

Each component has an as prop that allows you to set the components html tag https://styled-components.com/docs/api#as-polymorphic-prop. So you could do
<RRLink>
    <Link as="span">Some Link text here</Link>
</RRLink>

ah perfect, thanks!


fix: Don't expose existing emails via reset password and account creation forms

Fixes #5156

Yep, that is next. Wanted to make sure the basic logic is OK now though.

I messed up the rebase and had to do a clean PR. See #5288.


chore(release): Generate changelog

Integrate commitizen
to automatically generate the changelog and create a tag for release.
Signed-off-by: Charith Ellawala<EMAIL_ADDRESS>

I didn't know that was an issue. I'll look into it.


Fixed - Installing Requirements Error: squeeze_and_excite

Just to let other users know, when running the requirements.txt installation in a venv, our team encountered an error:

raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://pypi.org/simple/git/

We found that the fix for this issue was to manually run the command bellow. When testing the pip install requirements.txt again, the issue appeared to be solved.

pip install https://github.com/abhi4ssj/squeeze_and_excitation/releases/download/v1.0/squeeze_and_excitation-1.0-py2.py3-none-any.whl

Hi Andrei,
Thanks for pointing this out. I saw that I missed the `squeeze and excite' module from the requirements.txt file. I made the changes.
Best
Abhijit

Closed due to inactivity and issue resolved.


Update repositories.txt

Closing as duplicate of https://github.com/arduino/library-registry/pull/1803


Remaining repos under grpc org need to be switched to Apache 2.0

These repos are still on BSD, it would be good to switch everything to Apache2.0 for consistency.
https://github.com/grpc/grpc-contrib
https://github.com/grpc/homebrew-grpc
https://github.com/grpc/grpc-haskell  (this repo is contributed by third party)
https://github.com/grpc/grpc-proto

@mehrdada, can you take a look please?
CC @hsaliak @varuntalwar

These are the PRs. For some reason I can't assign or request reviews for some of them, so I just list them here and leave setting the assignee to someone else:
https://github.com/grpc/grpc-contrib/pull/3
https://github.com/grpc/homebrew-grpc/pull/107
https://github.com/grpc/grpc-haskell/pull/19
https://github.com/grpc/grpc-proto/pull/5

@mehrdada  thanks a lot!

Closing this issue as the final open PR can be tracked there anyway: https://github.com/grpc/grpc-contrib/pull/3


Update generated ssh authorized_principals to be consistent with base os.

This updates the generated authorized_principals files to expect the v3 SSH principals. This more generally makes the generated files to consistent with base os (which just have the one expected principal and the emergency access principal).
Note that config.Config.SSHAccountID could be dropped since we only care about the environment in the new principal, but for some reason the SSH account ID seems to be informing the VPC account ID and I didn't want to go poking around in those bits of code that I don't know about.

This will break ssh access to non-spinnaker tasks, right?
I think they were working before because of the more lax principal lines.

I believe this will still work for non-spinnaker tasks. As long as we can resolve the asg (or equivalently job stack/detail) when we do a sonar lookup the server-side should be inserting matching principals.

Well, you know how this goes :)
It will almost certainly break some things.

Can we know beforehand if this is going to break things that use titus_agent accounts?
Can we know beforehand if this will break things that use an IAM ARN from a different account?
Can we know if this will break non-spinnaker tasks (kinda covered, and I guess the answer is .. maybe? blanks with colons?)

Also I can deploy this to my dev stack if you want, give it a real test on something.

Can we know beforehand if this is going to break things that use titus_agent accounts?
Can we know beforehand if this will break things that use an IAM ARN from a different account?
Can we know if this will break non-spinnaker tasks (kinda covered, and I guess the answer is .. maybe? blanks with colons?)

To the extent that we're talking about bastion 2.0 flow none of these things should break. The ssh certificate service was only ever injecting the test/prod account IDs, regardless off the titus_agent accounts or IAM ARN account ID. Likewise the certificate service was already rejecting requests to mint certs for jobs with app/stack/detail values that had colons, so those already never worked.
More subtly, there may have been cases with some different behavior (such as colon values working) in the bastion 1.0 titus-ssh workflow. Since this effectively forcefully cuts us over to the 2.0 flow this would mean there's no (easy) going back to titus-ssh for corner cases where the new flow intentionally doesn't work. But I would have expected those sort of mentions to come up regardless of these changes. So I would estimate disruption to be unlikely.


extend form to describe different entities

(e.g. resources and their creators, corresponding to different sections of the form)

done in https://zenodo.org/record/6423933#.Yk_LXDdBwUo


Instance autocomplete._popover with new ch.Popover

Sadly I'll have to close this since it's not aligned with the project's current objectives. :pensive:
Thanks for opening the issue. :grinning:


[Identity] Allow integration test request retries

Some managed identity integration tests occasionally fail with gateway timeouts. This ensures that the requests to the app endpoints are retried in these cases by adding the RetryPolicy to the PipelineClient.

/azp run python - identity - tests-weekly

API change check
API changes are not detected in this pull request.

/azp run python - identity - tests-weekly


Picker auto scroll to bottom when selecting images #71

Roy,
Here is the fix for #71

Hey Dustin, thanks for reporting and fixing it! I tested the change and it seems to work ok.


Query which OS to use

I am using ubuntu 16.04 and having lots of issues while installing. Can any one tell me which verison of ubuntu will go good for this? I am comfortable to switch to centos also.

Ubuntu 16.04 should work fine. Can you describe your problems?

I am having problem when installing the webpack.
[https://github.com/npm/npm/issues/13880](issue 1) and while trying to solve this issue i counter this one [https://github.com/npm/npm/issues/13882](issue 2). Can you help me here?
@patrys

Which versions of Node.js and mom are you using?

You can close the issue. It's been resolved. upgrading the npm solved the problem thanks,mate


Link CHANGELOG version heading to the release

For faster access [and as a reminder] that the github releases page exists

Ok, makes sense. Thanks!


Implement basic e2e tests against a real API

Description
Ideally should involve bringing up a real kuma and setting that up ready for testing against.
Worth noting that these can (probably/possibly should) be minimal tests on API endpoints etc and ideally we can also run the same tests against our mocks. (very much my opinion this bit so very much open to discussion)
P.S. I'd always wondered about auto-generating our mocks from OpenApi specs but also all we need to really test is that our mock API is correct. I'd almost rather these tests concentrated on that 🤔
We also have to be careful here as ideally we don't want to test what we don't own.

Let's have a general discussion about whether or not we should do this or if the value added is too low.

Maybe one day


An argument question

If I want to defend against a backdoor model trained on the "CIFAR-10" dataset using tiny_imagenet should I set '--use_tiny_imagenet' to true in the arguments?

I have already fixed this problem,however,there is another error described as follows:
"size mismatch for fc.weight: copying a param with shape torch.Size([10, 512]) from checkpoint, the shape in current model is torch.Size([200, 512])."


New version: Microsoft.OneDrive.Internal.Slow version 23.056.0314.0001

Result: Installation Failed

Manifest
Add/Remove Programs

Name
Microsoft OneDrive Internal Slow

Version
23.056.0314.0001

Publisher
Microsoft Corporation

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 6689
Microsoft Reviewers: Open in CodeFlow

Hi @vedantmgoyal2009,
I'm not sure how, but this PR results in Mozilla.Firefox being installed, not Microsoft.OneDrive. Here are the files changed from the sandbox:
files.txt

Installing in a sandbox gives the error:

Manifest Error: The multi file manifest has inconsistent field values. [ManifestVersion] Value: 1.0.0 File: Microsoft.OneDrive.Internal.Slow.locale.en-US.yaml


[CT-2416] [Feature] finer grain of location selection in dbt init

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
When we run dbt init to setup a profile
There is only two option in Desired location option

While it is not clear to first-time user what the location value here take effect, user is APAC region feels biased about not able to select their home region.
And evenmore, since in my case I have select bigquery as the adapter, it is intuitive that dbt can let user to select GCP region code as location input here, such as [45] asia-east2-b.
I expect there should be a full list of gcp zone to select during dbt init profile setup wizard.
Describe alternatives you've considered
one way is to remove this location selection step during dbt init, if the location isn't critial in profile. Meanwhile, as an optional settings here, we provide guideline on how to mannually set it afterwards and where it will be used.
another way, if gcp zone is too detailed to list out, then region-grain is also acceptable like asia-east2
Who will this benefit?
dbt init user, especially help if they start with dbt core.
Are you interested in contributing this feature?
No
Anything else?
If there is any document already mentioning about usage of location setting here while it is just my knowledge issue of not aware of it, please let me know.

@davidkhala Thanks for opening - you're right, this does seem a bit limited!
Our documentation states:

The location of BigQuery datasets can be configured using the location configuration in a BigQuery profile.
location may be either a multi-regional location (e.g. EU, US), or a regional location (e.g. us-west2 ) as per the BigQuery documentation describes.

The options provided during dbt init are defined here, in profile_template.yml:
https://github.com/dbt-labs/dbt-bigquery/blob/4673e40f36079fb547ae2a75fb352e2d0eb209ff/dbt/include/bigquery/profile_template.yml#L23-L27
We should either:

Add more options
Make it a free-text field

It's actually possible to override/customize this behavior for new users in your own project, by creating a profile_template.yml file in your project's root directory: https://docs.getdbt.com/reference/commands/init#profile_templateyml

Hi @jtcohen6
I haven't contributed before however I'm really keen to try and get involved. Wondering if this is something I could work on.
You suggested two approaches above, here are some pros and cons I see:
Add more options
Cons:

Given that there are over 30 BigQuery locations, it might be difficult to scan through and find the desired one
If new locations are added, it requires a change to profile_template.yaml

Pros:

Easy to implement (would just need to add these options to profile_template.yaml

Make it free text
Cons:

Opens up the opportunity for spelling errors which might cause unexpected errors later down the line

Pros:

More user friendly than a long drop down
No changes required to profile_template.yaml if new regions are added
Also easy to implement

Possible 3rd approach
Extend the current functionality in dbt-core to allow for free text fields with limited valid responses, prompting the user to try again if the given response is invalid (possibly implemented here)
Let me know if you think this is something I could get involved with, thanks.

Another option I was thinking about was to have multiple levels, the user could first choose the region, then the location like so:

This can be implemented like so in profile_template.yml:
 _choose_region:
    Asia-Pacific:
      _choose_location:
        asia-south1:
          _fixed_location: asia-south1
        asia-south2:
          _fixed_location: asia-south2
    Americas:
      _choose_location:
        US (Multi Regional):
          _fixed_location: US
        us-west1:
          _fixed_location: us-west-1
        us-west2:
          _fixed_location: us-west-2
    Europe:
      _choose_location:
        EU (Multi Regional):
         _fixed_location: EU
        europe-west1:
          _fixed_location: europe-west1
        europe-west2:
          _fixed_location: europe-west2


Number of Servos

How many servos can / must we use?
The component list states five, the overview image shows six.
The latter is also stated by "To enhance its capabilities, you are tasked with creatively installing an additional 2 cameras and 2 actuators."

For sure 5 is fixed. But one is more like a backup. Depends on the situation and paricipents it can change to 6. But 5 is the official number of servos.

Ok, thank you,


Geofence Diagnostics

Description of Change
Log individual create-region exceptions, with region details.
Issues Resolved
Probably not resolved, but related to #37
API Changes
None
Platforms Affected

Android

Behavioral Changes
None
Testing Procedure
It compiles.
PR Checklist

[x] Rebased on top of the target branch at time of PR
[ ] Changes adhere to coding standard

I'm going to remove the params version of this call in any case.  I want the exceptions of this call coming out clean.  Thanks for the PR in any case.


How do I compile this on Linux?

Specifically Debian. If there are instructions somewhere I could not find them. There doesn't appear to be any support for building with cmake. If there is I can't figure out how to do it so I assume a combination of autogen/configure is required - but I don't know how to use these.
Can someone provide a brief explanation please?

./configure && make && sudo make install


Bug: When lombok.accessors.chain=true setters show void return value

in lombok.config
lombok.accessors.chain=true
in code
new AuthEvent().setIp( "dd" ).setIp( "some" );
compiles well, but without IDE help after Ctrl+Space

I think it could be already fixed by changes for #254
I will double check it!

wow, great. Didn't find #254 first.
Thank you. Will be waiting for v0.13

I verified it. It should be really fixed in the next build!

great, thank you!


Liberty config

Please review and merge.

No point in reviewing this as it is already online.

@rdebusscher On the contrary, it was pushed online from a temporary branch: https://github.com/eclipse/microprofile-starter/tree/v0.9.4+issue-211
Whether we want it in master in this shape and form is debatable and open for review.

@Emily-Jiang I am about to open a new PR that consolidates this (and makes it even simpler) and re-intoridces the artifact id division to service-a and b (correctly this time) and addresses similar issues for Helidon.
While testing it, I noticed that jwt does not work for Helidon and I am in touch with someone to help me nail it down.

You can merge my changes and work on top of it if you want.

This PR is included in #214


Release/v9.1.0

#983
#985
#1006
#988
#998 - propose to bump this to a future release (matt)
#1008
#1001
#991

@AronPetrauskas Are you aware/expecting these changes to breaking? @girishv-ipg just installed this in VIRTO and instantly got a bunch of type errors due to changes in component interfaces: https://github.com/IPG-Automotive-UK/virto/actions/runs/12427467462/job/34697344096?pr=1258


Barretenberg Error: Unknown variant index for enum

Aim
I tried to compile, prove and verify following simple program using nargo and Barretenberg (bb) :
main.nr
use dep::std;

pub fn main(x : Field) -> pub Field {
    let mut y : Field = 0;
    let bytes_0 = x.to_be_bytes(32);
    let bytes_1 = x.to_be_bytes(32);
    let mut bytes_2 : [u8; 32] = std::unsafe::zeroed();
    for index in 0..32 {
        bytes_2[index] = (bytes_0[index] & bytes_1[index]);
    }
    y = std::field::bytes32_to_field(bytes_2);
    println(f"y => {y}");
    y
}

Prover.toml
x = "5"

nargo version
> nargo --version
nargo version = 0.31.0
noirc version = 0.31.0+30cb65a12668d192f8da940c32961210a05a962f

bb version
> bb --version
0.41.0

Expected Behavior
Successful execution of bb prove after nargo execute.
Bug
Unknown variant index for enum
To Reproduce

creation of a proper noir project with the given source file
nargo execute witness
bb prove -b ./target/TestProject.json -w ./target/witness.gz -o ./proof

Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
If this is related to the Barretenberg Project I can also open an issue there, but I am unsure which github project is the correct one for this kind of problem.
Installation Method
Binary (noirup default)
Nargo Version
nargo version = 0.31.0 noirc version = 0.31.0+30cb65a12668d192f8da940c32961210a05a962f
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

Unknown variant index for enum

This output is most commonly a serialization mismatch. If you do noirup -v 0.30.0 and continue using bb version 0.41.0 everything will pass as expected.
With your program I ran the following:
nargo execute witness
bb prove -b ./target/generics.json -w ./target/witness.gz -o ./proof
bb write_vk -b ./target/generics.json -o ./target/vk
bb verify -p ./proof -k ./target/vk

And everything succeeded as expected.
If you are working off nightlies you run a greater risk of hitting one of these serialization mismatches. The most recent Noir version is 0.32.0 and works with bb 0.46.1. If you are ever unsure about versioning you can check here.

As this output is from barretenberg we also ask that these issues be placed on the bberg repo. I have made an issue to improve this error message here, and we have an issue up already to improve the devex surrounding which versions should be used https://github.com/AztecProtocol/aztec-packages/issues/7525.
Going to close this issue but feel free to comment further if you have more questions.


Align remote and conf override members

I'm sorry 🙇
This is an implementation omission in this PR from me.

https://github.com/Songmu/ecschedule/pull/62

Without this, resource diffs will be detected every time.

Thank you. Released as v0.10.2.


[v1.x] backport #17900 "[MKLDNN] support using any format in pooling backward"

Description
This PR is to backport [MKLDNN] support using any format in pooling backward (#17900) to v1.x
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [all]

cc @ciyongch , adding this PR to 1.7.0 roadmap #16864

@mxnet-bot run ci [all]

@mxnet-bot run ci [unix-cpu, unix-gpu]


How will we automate the conversion of hub data to parquet after syncing to S3?

Per #18, we will default to parquet format for making hub data available in the cloud.
So far, we have a GitHub action that syncs model-output data to S3 exactly as submitted by teams (we sync admin/config files as well, but I'm assuming those aren't relevant to this conversation).
I'd advocate for retaining the submitted data in its original form (perhaps under a "raw data" path) and then landing the parquet version to the client/user-facing location.

One relevant consideration might be that a hub might choose to have its files submitted as parquet (this is allowable in a hub schema). In this case, would we still need to duplicate the data in the cloud?

@nickreich Good note! I think there is value in making a distinction between "raw data" and "user/client-facing data" for all hubs, regardless of their submission format:

Using the same S3 structure for every hub simplifies our code (e.g., no need to perform different data sync operations for hubs that submit in parquet)
It gives us room for future data manipulations we might decide to do (re-partitioning, for example)

The data I've seen in hubs so far is very small by cloud standards, so I'm not worried about duplication.

At a high-level (without getting into implementation details), would like to brainstorm how we might trigger follow-up data operations after a hub receives a new model-output submission:

Lean into AWS: We could write a lambda function that converts data to parquet and use S3 triggers to run the function every time new data lands.
Lean into GitHub: Package a data conversion function and have it run as an additional step to the "S3 sync" GitHub action. Have the GitHub action send both versions of the data (raw and parquet) to S3.
Use both: Write a lambda that converts the data and use the GitHub action to trigger it after the raw data lands in S3.
?? What am I missing ??

Also noodling on some variables that would influence our choice:

What should happen if the data conversion step fails? Do we want our GitHub checks to fail and block the merge?
Size of the individual model-output submissions
Administrative burden: what is the Hubverse appetite for expanding our reliance on AWS infrastructure from simple cloud storage to "a place where we need to maintain and update data conversion functions while also managing the associated permissions model"?
Cost

I don't have much experience with S3 triggers/lambdas and plan to spend some time learning how it works.

r.e. "What should happen if the data conversion step fails? Do we want our GitHub checks to fail and block the merge?" -- I think in general we should minimize burden on participating teams.  So if data conversion fails but a team's contribution was valid, I'd like to say the submission was valid and the team is done with their work, and hub administrators have to follow up.

At a high-level (without getting into implementation details), would like to brainstorm how we might trigger follow-up data operations after a hub receives a new model-output submission:

Lean into AWS: We could write a lambda function that converts data to parquet and use S3 triggers to run the function every time new data lands.
Lean into GitHub: Package a data conversion function and have it run as an additional step to the "S3 sync" GitHub action. Have the GitHub action send both versions of the data (raw and parquet) to S3.
Use both: Write a lambda that converts the data and use the GitHub action to trigger it after the raw data lands in S3.
?? What am I missing ??

Revisiting the above options now that we've had some additional conversations and experiment learnings (provisioning AWS resources via code.
I believe we should use a cloud-based trigger to initiate conversions/transformations on model-output files submitted to a hub.

If our eventual goal is to allow submissions directly to cloud storage (i.e., without submitting a PR to the hub's repo), we don't want to rely on a github action to initiation a post-submission data conversion process
Now that we have additional clarity for using infrastructure-as-code to provision hub resources, I'm less concerned about administrative burden for a cloud-based trigger

Because we're already using AWS, I propose exploring the use of S3 triggers, which can invoke various actions when data is written or removed from an S3 bucket.
Will close this and follow-up with issues with more specific work re: experimentation with S3 triggers.


AvailabilityGroup backup history added

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[x] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[x] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[x] Pester test is included
[x] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Have Get-DbaDbBackupHistory play nice with AG backup history spread across nodes
Approach
Little bit of recursion
Added another property to the BackupHistory object: AvailabilityGroupName
Select-DbaBackupInformation will now default to using AvailabilityGroupName if it's populated
If the SqlInstance is an AG listener then fire off a gddbh query to each node. For last,
pipe the results through Select-DbaBackupInformation to filter down to the full chain
If an instance is specified and the requested dbs are in an AG, then it will query all nodes in the AG for that database, but only use the instance for the other dbs.
Removed ParameterSet as it doesn't appear to do anything anymore.
Commands to test

Screenshots

Learning

ohhh @wsmelton - i think you've been wanting this for a while!

Be good to get @wsmelton to give it a thorough test. I'm sure he's got some more 'interesting' AG configurations than I've got to hand. Logic says it'll be fine, but reality's a harsh master

Failure appears to be nthing to do with this. Everyone happy if I merge?

Ok. So you might be able to answer this scenario without me having to dig through code...or see what was changed.
I have 3 node AG setup, the 3rd async replica is located at a DR site and is a named instance, but also because of security requires a custom port (not using 1433). I know in SMO that SQL Server class for AvailabilityGroup knows nothing of this port and only has the server name. When I pass in the listener in order to pull that backup history how is your code going to connect to that 3rd instance?
Now mind you I completely understand if it will break because we have the same issue in the DSC module for SQL Server and AG builds. If you can lay out how it connects to the other replicas to pull backup history I'm good with merging....

can we merge? 🐶 👀

It is fine with me to merge, just as long as folks understand it will have bugs that we cannot fix/resolve due to limitations in SMO....which I think should be rare cases.

Thank you 💯


Add Cryptocurrency addresses as donation methods

Please add direct cryptocurrency addresses within the app. Easy tap and donate without leaving the app. All happens offline (no internet needed).
TRX, AVAX, LTC, BTC, XEC, BNB, SOL, BCH, ALGO, XTZ, HBAR, DASH, FTM, XRP, XDC, ADA, XLM, KAS, XMR, SEI, INJ, SUI addresses available for donations (addresses have to be copyable).
I don't want going around to websites. I don't want support FIAT economy.
I don't want leave the app environment in order to make a donation.
Here an integration example made by other developers.

Good idea. In the mean time I have a BTC address available for donations: bc1qd4enyt30w02vty8xt3fm5uesunzxpnz3w4agf4
Maybe I should add this to the github sponsoring file

If I add this as a feature I will most likely add BTC, ETH and other widely known currencies

The fastest reliable and legit hacker I can recommend for you is  d a r k w e b p r o g r a m m e r @ g m a i l . c o m   , my $15,000 hack transfer with them was successful, trust me


fix: gh actions plugins

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


upgrade host.app to .NET Core 1.0

Would be really cool to see it working with the new .net

Also a valid point @thinkrapido perhaps @gingters can take this, because I know that he already did some great work with core-1.0? Not sure how his schedule looks like for the upcoming weeks. But I'll put it on the schedule

We will most likely not move to .NET Core with this sample app. Sorry.


Fix hide-tips CSS feature

Test URLs

PR list
Gobal conversations list

Screenshot
Before

After

ขอบคุณครับ

There's also a tip on the dashboard:

However I'm not sure if we want to hide it since the links in it are useful (?)

There's also a tip on the dashboard (above the square, too lazy to make another screenshot):

https://github.com/refined-github/refined-github/pull/5196#discussion_r767328562


Improve config file updating

During setup it asks the following:
echo "Configuration file $CONFIG_FILE exists already. What do you want to do?"
    echo "[0] Keep and use current configuration file."
    echo "[1] Edit existing configuration file."
    echo "[2] Delete the configuration file and start with a fresh one."
    read -p "Which option do you prefer? [hit Enter for 0]: " config_action

It would be good that when you selection option 2 the default security parameters are pulled from the current file like option 1.
If it's a new file the defaults should be blank like normal.

Yes, that makes sense. For example when the user upgrades to a new version and doesn't want to manually update the config, at least the AVS settings are kept.

Yes, that makes sense. For example when the user upgrades to a new version and doesn't want to manually update the config, at least the AVS settings are kept.

I think that it is better to have this as another option: "Upgrade existing configuration file"

You will be give the option as normal. The current setting will be in the brackets (default) so you can hit enter or put your new value in.


WIP: ServiceType & NodePort work

Integrating all the PRs into a clean/mergeable history.  Mostly creating PR for testing purposes.

LGTM so far

LGTM

I am monitoring jenkin and will update the e2e status.

Thanks Dawn and Justin!  This is a huge improvement.

@justinsb and @thockin My Jenkin run with this pr failed. Actually run is not finished, but I observed several service tests failure already:
• Failure [422.282 seconds]
Services
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:824
should be able to create a functioning external load balancer [It]
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:313
Expected error:
<*url.Error | 0xc20859e0f0>: {
Op: "Get",
URL: "http://<IP_ADDRESS>:31852",
Err: {
Op: "dial",
Net: "tcp",
Addr: {
IP: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\x92\x94=\xdb",
Port: 31852,
Zone: "",
},
Err: 0x6e,
},
}
Get http://<IP_ADDRESS>:31852: dial tcp <IP_ADDRESS>:31852: connection timed out
not to have occurred
Services
should release the load balancer when Type goes from LoadBalancer -> NodePort
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:601
[BeforeEach] Services
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:59

testContext.KubeConfig: /var/lib/jenkins/jobs/kubernetes-e2e-gce/workspace/.kube/config
STEP: Building a namespace api objects
[It] should release the load balancer when Type goes from LoadBalancer -> NodePort
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:601
STEP: creating service service-release-lb with type LoadBalancer
STEP: creating pod to be part of service service-release-lb
INFO: Waiting up to 5m0s for pod service-release-lb-1 status to be running
INFO: Waiting for pod 'service-release-lb-1' in namespace 'e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e' status to be '"running"' (found phase: '"Pending"', readiness: false) (12.499163ms)
INFO: Waiting for pod 'service-release-lb-1' in namespace 'e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e' status to be '"running"' (found phase: '"Pending"', readiness: false) (5.019461744s)
STEP: waiting up to 4m0s for service service-release-lb in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e to have a LoadBalancer ingress point
INFO: Waiting for service service-release-lb in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e to have a LoadBalancer ingress point (3.13453ms)
INFO: Waiting for service service-release-lb in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e to have a LoadBalancer ingress point (5.007810069s)
INFO: Waiting for service service-release-lb in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e to have a LoadBalancer ingress point (10.012672288s)
INFO: Waiting for service service-release-lb in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e to have a LoadBalancer ingress point (15.017706187s)
STEP: hitting the pod through the service's NodePort
STEP: Checking reachability of http://<IP_ADDRESS>:30531
STEP: Got error waiting for reachability of http://<IP_ADDRESS>:30531: Get http://<IP_ADDRESS>:30531: dial tcp <IP_ADDRESS>:30531: connection timed out
STEP: Got error waiting for reachability of http://<IP_ADDRESS>:30531: Get http://<IP_ADDRESS>:30531: dial tcp <IP_ADDRESS>:30531: connection timed out
STEP: Got error waiting for reachability of http://<IP_ADDRESS>:30531: Get http://<IP_ADDRESS>:30531: dial tcp <IP_ADDRESS>:30531: connection timed out
STEP: deleting pod service-release-lb-1 in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e
STEP: deleting service service-release-lb in namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e
[AfterEach] Services
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:68
STEP: Destroying namespace e2e-tests-service-0-0c5601f0-ea63-47c3-a6e1-970c809f049e
STEP: Destroying namespace e2e-tests-service-1-5305926b-2861-4060-a7bd-69744938293a

• Failure [427.308 seconds]
Services
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:824
should release the load balancer when Type goes from LoadBalancer -> NodePort [It]
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:601
Expected error:
<*url.Error | 0xc20859e0f0>: {
Op: "Get",
URL: "http://<IP_ADDRESS>:30531",
Err: {
Op: "dial",
Net: "tcp",
Addr: {
IP: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\x92\x94=\xdb",
Port: 30531,
Zone: "",
},
Err: 0x6e,
},
}
Get http://<IP_ADDRESS>:30531: dial tcp <IP_ADDRESS>:30531: connection timed out
not to have occurred
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:1048

@dchen1107 this is on GCE right?  Looking right now...

e2e issues should be fixed by #8728 ; just running through a -up / -test / -down cycle.

@justinsb  Thanks for the fixing. I or @lavalamp or @quinton-hoole will update with you the jenkin result tomorrow morning. Sometimes I have trouble to access our Jenkin through VPN too.

@justinsb @thockin Still have one consistent failure:
Shell tests that services.sh passes

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/shell.go:39
Error running &{/jenkins-master-data/jobs/kubernetes-e2e-gce/workspace/kubernetes/hack/e2e-suite/services.sh [/jenkins-master-data/jobs/kubernetes-e2e-gce/workspace/kubernetes/hack/e2e-suite/services.sh] []  <nil> Project: kubernetes-jenkins
Zone: us-central1-f
MINION_NAMES=e2e-test-jenkins-minion-xkzc e2e-test-jenkins-minion-xq2i
Found e2e-test-jenkins-minion-xkzc at <IP_ADDRESS>
Found e2e-test-jenkins-minion-xq2i at <IP_ADDRESS>
Starting service 'service-14074' on port 80 with 3 replicas
replicationcontrollers/service-14074
services/service-14074
Starting service 'service-342' on port 80 with 3 replicas
replicationcontrollers/service-342
services/service-342
Querying pods in service-14074
service-14074-1oi4d
service-14074-qnhqv
service-14074-yfmck
Waiting for 3 pods to become 'running'
Waiting for 3 pods to become 'running'
Querying pods in service-342
service-342-20lyi
service-342-gmed5
service-342-lps30
Waiting for 3 pods to become 'running'
Waiting for 2 pods to become 'running'
Test 1: Prove that the service portal is alive.
Verifying the portals from the host
Checking if service-14074-1oi4d service-14074-qnhqv service-14074-yfmck  == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Endpoints did not propagate in time
Stopping service 'service-14074'
replicationcontrollers/service-14074
services/service-14074
Stopping service 'service-342'
replicationcontrollers/service-342
services/service-342
Project: kubernetes-jenkins
Zone: us-central1-f
MINION_NAMES=e2e-test-jenkins-minion-xkzc e2e-test-jenkins-minion-xq2i
Found e2e-test-jenkins-minion-xkzc at <IP_ADDRESS>
Found e2e-test-jenkins-minion-xq2i at <IP_ADDRESS>
Starting service 'service-14074' on port 80 with 3 replicas
replicationcontrollers/service-14074
services/service-14074
Starting service 'service-342' on port 80 with 3 replicas
replicationcontrollers/service-342
services/service-342
Querying pods in service-14074
service-14074-1oi4d
service-14074-qnhqv
service-14074-yfmck
Waiting for 3 pods to become 'running'
Waiting for 3 pods to become 'running'
Querying pods in service-342
service-342-20lyi
service-342-gmed5
service-342-lps30
Waiting for 3 pods to become 'running'
Waiting for 2 pods to become 'running'
Test 1: Prove that the service portal is alive.
Verifying the portals from the host
Checking if service-14074-1oi4d service-14074-qnhqv service-14074-yfmck  == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Endpoints did not propagate in time
Stopping service 'service-14074'
replicationcontrollers/service-14074
services/service-14074
Stopping service 'service-342'
replicationcontrollers/service-342
services/service-342
[] <nil> 0xc208f931c0 exit status 1 <nil> true [0xc208da5c88 0xc208da5ca8 0xc208da5ca8] [0xc208da5c88 0xc208da5ca8] [0xc208da5ca0] [0x58ae70] 0xc208475140}:
Command output:
Project: kubernetes-jenkins
Zone: us-central1-f
MINION_NAMES=e2e-test-jenkins-minion-xkzc e2e-test-jenkins-minion-xq2i
Found e2e-test-jenkins-minion-xkzc at <IP_ADDRESS>
Found e2e-test-jenkins-minion-xq2i at <IP_ADDRESS>
Starting service 'service-14074' on port 80 with 3 replicas
replicationcontrollers/service-14074
services/service-14074
Starting service 'service-342' on port 80 with 3 replicas
replicationcontrollers/service-342
services/service-342
Querying pods in service-14074
service-14074-1oi4d
service-14074-qnhqv
service-14074-yfmck
Waiting for 3 pods to become 'running'
Waiting for 3 pods to become 'running'
Querying pods in service-342
service-342-20lyi
service-342-gmed5
service-342-lps30
Waiting for 3 pods to become 'running'
Waiting for 2 pods to become 'running'
Test 1: Prove that the service portal is alive.
Verifying the portals from the host
Checking if service-14074-1oi4d service-14074-qnhqv service-14074-yfmck  == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Checking if   == service-14074-1oi4d service-14074-qnhqv service-14074-yfmck
Waiting for endpoints to propagate
Endpoints did not propagate in time
Stopping service 'service-14074'
replicationcontrollers/service-14074
services/service-14074
Stopping service 'service-342'
replicationcontrollers/service-342
services/service-342

These two tests have occasional flakes:

Services should release the load balancer when Type goes from LoadBalancer -> NodePort
Services should correctly serve identically named services in different namespaces on different external IP addresses

I think we can live with this, if @justinsb will fix the services.sh test. :)

Will definitely fix - sorry!
If you can provide me with an output from one of the flakes, I can have a look at those as well.

Hm there are actually a number of flakes in this most recent run:
Services should release the load balancer when Type goes from LoadBalancer -> NodePort

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:602
Expected error:
    <*errors.errorString | 0xc208c90750>: {
        s: "service service-release-lb in namespace e2e-tests-service-0-af873fc2-22d6-45fd-9e2c-493b24167e65 doesn't have a LoadBalancer ingress point after 240.00 seconds",
    }
    service service-release-lb in namespace e2e-tests-service-0-af873fc2-22d6-45fd-9e2c-493b24167e65 doesn't have a LoadBalancer ingress point after 240.00 seconds
not to have occurred

Services should correctly serve identically named services in different namespaces on different external IP addresses

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:824
Expected error:
    <*errors.errorString | 0xc209116060>: {
        s: "service s0 in namespace e2e-tests-service-0-8397355a-319a-4d3a-bff9-04bc786a7fbe doesn't have a LoadBalancer ingress point after 240.00 seconds",
    }
    service s0 in namespace e2e-tests-service-0-8397355a-319a-4d3a-bff9-04bc786a7fbe doesn't have a LoadBalancer ingress point after 240.00 seconds
not to have occurred

Services should be able to create a functioning external load balancer

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:313
Expected error:
    <*errors.errorString | 0xc2091160a0>: {
        s: "service external-lb-test in namespace e2e-tests-service-0-16ce706c-478a-4768-9bf7-e2ea5a169d08 doesn't have a LoadBalancer ingress point after 240.00 seconds",
    }
    service external-lb-test in namespace e2e-tests-service-0-16ce706c-478a-4768-9bf7-e2ea5a169d08 doesn't have a LoadBalancer ingress point after 240.00 seconds
not to have occurred

Services should be able to change the type and nodeport settings of a service

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:521
Expected error:
    <*errors.errorString | 0xc208e47ef0>: {
        s: "service mutability-service-test in namespace e2e-tests-service-0-7e7ff24f-4523-4099-aac8-603e874aa107 doesn't have a LoadBalancer ingress point after 240.00 seconds",
    }
    service mutability-service-test in namespace e2e-tests-service-0-7e7ff24f-4523-4099-aac8-603e874aa107 doesn't have a LoadBalancer ingress point after 240.00 seconds
not to have occurred

WIP patch (implemented, but running through the test cycle) to continue to support deprecatedPublicIPs is here:  https://github.com/GoogleCloudPlatform/kubernetes/pull/8739
@lavalamp I don't support we have hit the quota-limit on the number of load balancers allocated?  If so, I'll look for a leak here.

Status update: I now get a different error from services.sh; it looks like it isn't doing strict round-robin between the nodes.  It takes a while for endpoints to propogate, and then "verifying the portals from a container fails because it sees one of the pods twice:
  service-32506 portal failed from container, expected:

                service-32506-4wije
        service-32506-7ejip
        service-32506-m9efj

          got:

                service-32506-7ejip
        service-32506-7ejip
        service-32506-m9efj

I also have an idea on a potential cause for LB leakage - I made a late change to zero out the LoadBalancerStatus immediately, so I need to double-check the logic around service release here.
Investigating both issues!

Thanks for working on this, Justin!

It is possible there is a leak.

A new flake, possibly all because we've leaked load balancers and I don't know which it's safe to delete because they're all named with long hex values:
Services should release the load balancer when Type goes from LoadBalancer -> NodePort

/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:602
Expected error:
    <*errors.errorString | 0xc208fa1f50>: {
        s: "service service-release-lb in namespace e2e-tests-service-0-a3ef5b51-026a-48e1-986c-ba04095e5d41 doesn't have a LoadBalancer ingress point after 240.00 seconds",
    }
    service service-release-lb in namespace e2e-tests-service-0-a3ef5b51-026a-48e1-986c-ba04095e5d41 doesn't have a LoadBalancer ingress point after 240.00 seconds
not to have occurred

I just deleted all the forwarding rules... Let's see if this makes it green for a bit.

The default e2e setup does not configure any forwarding rules.  So if this project is only running e2e, it should be safe to delete all the forwarding-rules (but I don't really know your setup).  You could also check that they have no attached instances.
I've also yet to see a leak when running it myself (at the end of the test, gcloud compute forwarding-rules list is empty).
The hex string is the UUID of the k8s service, with a prefix of "a", I believe.

So deleting all that stuff got us a totally green run. :)

I think it's actually target pools that are leaking. The forwarding rules seem to get cleaned up.

So to follow up: it's target pools leaking, from GKE's e2e test run that's using an old version. They share test projects & quotas with our GCE e2e testing.

When I originally wrote the verifying code I seem to recal reading 2x as
many tries then running that through sort and uniq for this reason.
On Sat, May 23, 2015 at 4:35 PM, Justin Santa Barbara <
<EMAIL_ADDRESS>wrote:

Status update: I now get a different error from services.sh; it looks like
it isn't doing strict round-robin between the nodes. It takes a while for
endpoints to propogate, and then "verifying the portals from a container
fails because it sees one of the pods twice:
service-32506 portal failed from container, expected:
            service-32506-4wije
    service-32506-7ejip
    service-32506-m9efj

      got:

            service-32506-7ejip
    service-32506-7ejip
    service-32506-m9efj

I also have an idea on a potential cause for LB leakage - I made a late
change to zero out the LoadBalancerStatus immediately, so I need to
double-check the logic around service release here.
Investigating both issues!
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8707#issuecomment-104954988
.

@a-robinson in case nobody did
On Sun, May 24, 2015 at 2:14 PM, Daniel Smith<EMAIL_ADDRESS>wrote:

So to follow up: it's target pools leaking, from GKE's e2e test run that's
using an old version. They share test projects & quotas with our GCE e2e
testing.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8707#issuecomment-105062686
.

The GKE tests leaking stuff is discussed in https://github.com/GoogleCloudPlatform/kubernetes/issues/7753#issuecomment-102942215. Tomorrow I'll check into adding the sleep to jenkins that I mention in the last comment there.

I just saw this.  So PublicIPs were deprecated, what were they replaced with here?


Update githubroadmap.php

fixes growth#193
Description

Fixes

@jsigwart the file you located is dummy data only used for local development when you might not have a GitHub API credential.
The live roadmap items are pulled from these tickets: https://github.com/lbryio/internal-issues/issues?q=is%3Aissue+is%3Aopen+label%3A2019
If you edit one of those tickets, the change should be live within an hour (the website caches results from GitHub).


[8.12-stable] Prevent NVME devices used by EVE to be passed through to VMs

Back porting the patch that protects NVME drives to 8.12.0:

Add function that checks if a device is used by EVE
Set keepInHost to true for such devices

Signed-off-by: Ioannis Sfakianakis<EMAIL_ADDRESS>

Is this just a git cherry-pick of what is in the master branch? Or a manual port?


Heap Use After Free in ex_docmd.c

We found Heap Use After Free an issue in vim binary and vim is complied with clang enabling ASAN.
Machine Setup
Machine : Ubuntu 16.04.3 LTS
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 20 2019 11:04:35)
Included patches: 1-2191
version : 8.1.2191
Commit : 83e9a1c
Command : ./vim -u NONE -X -Z -e -s -S POC -c ':qa!'

Was this run with  optimized compilation?  Please don't use the optimizer so that the line numbers are meaningful.


Format AUTHORS.md with hallmark

What is the purpose of this pull request?
[x] Documentation update
What changes did you make?

Changed tools/update-authors.sh to wrap email addresses in angle brackets (<>) which ensures remark recognizes them as links (rather than literal URLs, which is a GFM feature) which in turn prevents the bug https://github.com/remarkjs/remark-github/issues/18.
Added hallmark (only on AUTHORS.md to start) to format email addresses as mailto: links.

Is there a reason that hallmark doesn't just leave the the emails formatted like<EMAIL_ADDRESS>It seems cleaner to leave them that way if they're recognized as emails by GitHub and other tooling.

The idea behind it is to render the markdown the same as GitHub would (in places that aren't GitHub).

@vweevers Understood.


[Service Bus] Update tests and infrastructure for management API feature

Some APIs and test scenarios such as empty list() operations require that the Service Bus namespace used for live tests on CI to be empty.
This issue is to track investigation and decisions around the approach to take for the implementation and subsequently adding in the list() tests.
Context on test scenarios and other work arounds that were considered - https://github.com/Azure/azure-sdk-for-js/pull/6112#discussion_r346496535

One approach to consider is to not have the empty list scenario be a live test.
If we know what the response looks like for the case when service bus has no entities, then we can use that and test that our api returns an empty array.

Closing as a similar issue exists and is in progress https://github.com/azure/azure-sdk-for-js/issues/5985


[WIP] Preadditive Categories

Description
This PR implements Preadditive categories, in the style of Borceux1. We also prove some properties, the most interesting of which surrounds biproducts. Traditional definitions of biproducts often require some sort of enrichment, or at the very least zero objects. However, recent developments by Karvonen2 have provided an excellent definition that works without any sort extra structure, and coincides perfectly with older definitions when the enrichment is present.
Notes
Instead of defining Preadditive Categories as Ab-Enriched, we do the enrichment "by hand". This is done mainly to keep Preadditve (and in the future, Additive and Abelian) as structures over a category, rather than over an enriched one. This will allow us to show that the Category instances for Abelian Groups and modules over a Ring are Preadditive, rather than having to build a parallel instance that is Ab-Enriched.
Todos

[ ] Show that the Ab-Enriched version is equivalent
[ ] Show that our definition of biproducts implies the more traditional one

1: Borceux, Handbook of Categorical Algebra, Volume 2, Definition 1.2.1
2: Karvonen, Biproducts without pointedness
https://arxiv.org/abs/1801.06488

Ugh, moved to a new computer and git config is messed up. Will fix

Nice work! I noticed the other day that we have CMon-enriched categories in the library: https://github.com/agda/agda-categories/blob/c96e085e14ba619722c402cc161941ad8caf245b/src/Categories/Category/CMonoidEnriched.agda#L17
They are formalised in a similar way (by hand rather than via enrichment). Clearly they are related, so maybe the definition of preadditive categories should include the one for CMon-enriched ones? Or at least we should define a forgetful functor from one to the other. Similarly for the proof that these are equivalent to enriched categories, maybe the corresponding notions of tensor products could share some definitions/code.
WDYT?

So I noticed the Communitive Monoid Enriched stuff when I was writing this, but there is one reason that I didn't include the definition in Preadditive. I've defined Preadditive as a property on an existing category, whereas CM-Category bundles up all of the fields from Category inside itself.
Now, this is part of a much larger design discussion, but my feelings these days is that most things like Preadditive should be defined as properties, rather than bundled structures. This is because of purely operational reasons: A lot of our existing definitions work over Category, so having things be properties when we can makes things more compositional and encourages re-use of definitions/theorems. Obviously some things should be bundled up (IE: Bicategory and friends), but I think these are largely exceptions from the norm.
With that in mind, perhaps a type that captures this sort of "enrichment by hand over some algebraic structure" could be useful. I'm not 100% what it would look like, but it's food for thought.

So I noticed the Communitive Monoid Enriched stuff when I was writing this, but there is one reason that I didn't include the definition in Preadditive. I've defined Preadditive as a property on an existing category, whereas CM-Category bundles up all of the fields from Category inside itself.

I think the current convention — which is also the one used by the stdlib — is to have both an unbundled/property version (Is...) and a bundled one that uses the unbundled one internally. Things are slowly being migrated to this style. So maybe it would make sense to do this with both CM-Categories (add the unbundled version, e.g. CM-Enriched) and Preadditive (add a bundled version, e.g. PreadditiveCategory). I'll let @JacquesCarette and @HuStmpHrrr weigh in on this.

Very cool stuff. I will do a careful review soon.  [The code is very clean, but we might as well optimize it even more while it's still under development.] Right now, I'll just comment on the various things that have already been discussed.
First: my attempt at CMon-enriched was partial. I'm trying to do tangent categories and the like, and was working incrementally and more or less directly from the sources. I'm not sure if 'my' way of doing it is good for scalability. We definitely should try to get these two to line up (i.e. use the same conventions), and I'm entirely willing to change mine if I made some sub-optimal choices.  So yeah, if we can come up with a decent way to encode "enriched by hand over some algebraic structure", that would be grand.
Second: yes, we're moving to provide both bundled and unbundled versions. They have pros and cons, and it feels like a false choice to have to choose.  It's just not that much work to provide both, and ends up way more useful in the end.
Third: I continue to prefer lots of small PRs over large ones. Even if the PRs have dependencies.  So the (great!) infrastructure work in this PR should have been (can still be?) split. That work can be merged in much more quickly. The stuff that needs more careful consideration can then wait a bit longer, without stopping all progress.

Sorry for dropping these big PRs, It is a bad habit! I'll spin of the biproduct + reasoning combinators into separate PRs.

No worries, I easily drift into that too. I then have to go back and do some git magic to fix my own bad habits.

I've spun out Biproducts and the reasoning combinators into #250 and #251, respectively.

Global

@TOTBWF I know this is rather an old, partial PR, and that you're working more on 1lab right now, but it would be nice to get some closure on this one (and I mean that in let's get it pulled in, not let's just close it!). Anything I can do to prod that along?

To be honest I had totally forgotten about this! I'll try and get this over the finish line next week!

I guess "next week" didn't really happen... is there a chance this will get completed?


[CONTP-286] Revert new DD_ENTITY_ID

What does this PR do?
CONTP-286

Revert new DD_ENTITY_ID
Remove admission_controller.inject_config.inject_container_name from config

Motivation

Solution chosen in the New Origin Detection Spec RFC has been implemented (DD_EXTERNAL_ENV: it-INIT_CONTAINER,cn-CONTAINER_NAME,pu-POD_UID).
Therefore, the DD_ENTITY_ID as  en-(init.)$(DD_INTERNAL_POD_UID)/$(DD_INTERNAL_CONTAINER_NAME) from PRs:

https://github.com/DataDog/datadog-agent/pull/23447
https://github.com/DataDog/datadog-agent/pull/24482
are no longer needed.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
unit test updated
e2e test updated
QA same as
https://github.com/DataDog/datadog-agent/pull/27313 and
https://github.com/DataDog/datadog-agent/pull/27449
to make sure the new implementation is not broken

/merge


configMotion() of SensorQMI8658 doesn't work properly.

The following "Motion Detection Parameters" do not seem to be set correctly.

AnyMotion?hr  (? = X, Y, Z)
NoMotion?Thr  (? = X, Y, Z)

These parameters set gravitational acceleration uints,  in 1-byte format unsigned, 5-bits fraction.

I haven't been able to solve this problem yet. I will check it out later. Mark it first.


Dependencies updated to latest versions

All dependencies updated to the latest versions - except for OpenLayers (ol) and ol-contextmenu.
ol-contextmenu requires an update to work with any versions of ol over v8.. - these dependencies will be updated in the future.

Thanks @RobQuincey-DC - one day I'll actually remember the CDN links! I've updated these and once this is approved, I'll push to staging for testing before we publish.


Small refactor of transpose code

First step towards https://github.com/quantumlib/Stim/issues/169. Factoring out the maj/min index -> data index computations

very interesting. I think I see where we are misunderstanding each other. Let me try and explain by generalizing a bit.
In my mind, a tensor with d axes consists of an array of atomic types, and a coordinate function which tells us how to map index d-tuples to data. As a warm up, here is one way to implement a tensor data structure:
template <size_t d, typename A>
struct tensor {
    std::array<size_t, d> bounds;
    A *data;

    size_t size() {
        size_t result = 1;
        for ( size_t n : bounds ) {
            result *= n;
        }
        return result;
    }

    A *get_data(std::array<size_t, d> coordinates) {
        size_t data_index = 0;
        size_t stride = 1;
        for (size_t i = 0; i < d; i++) {
            data_index += coordinates[i] * stride;
            stride *= bounds[i];
        }
        return data + data_index;
    }
};

Here, incrementing the first index corresponds to incrementing data by 1, so the first axis is stored contiguously in memory. If we loop over the coordinates array backwards in get_data, that would correspond to the last axis being stored contiguously in memory. The situation for Stim is a little more complex, since our atomic type isn't directly addressable, so it made sense to me to use a bitword<W> as the atomic type. Subconsciously, I was thinking about simd_bit_table as a 3-tensor with coordinates (i,j,r) where (i,j) specifies a W bit x W bit block and r specifies a row in that block. That is what the poorly named function data_index does: It maps those coordinates into the corresponding offset in simd_bits. In my mind, operations like tensor contraction and transposition live on the coordinate side, because they refer to specific indices, i.e swap the first and 3rd index.

Okay, that's also how I think about it (as tensor indices), except I view each of the bits of the address as one of the indices. For example the test methods are written in terms of permuting the bits of the address. Some of the avx possibilities correspond to somewhat unusual but permutations which can be useful building blocks.
The table is a bit table so the preferred indices for the API are (major, minor) with the caveat that the bottom bits of minor are within a word.

OK, mulling on that for a day, I now have a much better understanding of how you are thinking about the indexing. Updated the PR. Hopefully it is now more consistent with the surrounding code!


Add support for reading 7zip archives

Add support for reading 7zipped wordlists.
7za e -so wordlis.txt.7za wordlist.txt

Implemented in 3b71060.


⚠ Secret Website 3 has degraded performance

In ccbb169, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3019 ms

Resolved: Secret Website 3 performance has improved in 6fd1646.