text:
Overhaul fetch implementation and host API

This PR contains a substantial overhaul of the fetch implementation, along with meaningful changes to how the host API works
On the latter, the most important change is that the representation of handles is now completely opaque to consumers: instead of using a typedef visible to users of the host_api.h header, the header just forward-declares a class, which hence can't be created or interacted with from outside the host API implementation.

@guybedford while this isn't completely done, and in dire need of cleanup, it is most of the way there, I think. I'm sharing it now because the host API changes are bound to impact you quite a bit. I hope they're for the better, and I at least found them to be necessary to get back to a point where I'm able to reason through the management and lifecycles of resource handles.

@guybedford I think this is now ready for review. The resource handling is much cleaned up, and I addressed all the regressions of WPT tests that make sense to do here, relative to the state of the JS Compute Runtime I started with.
(The only things missing that that passes are around some convenience constructors such as Response.redirect(), which I'm not tackling here.)

Thank you for letting me know, @nicoburniske! Fascinating, given that I ran a whole bunch of WPT tests around fetch that seemed to say it works. I'll investigate.

@nicoburniske thank you again for the report! Turns out I had read some of the WPT outputs wrong, and there indeed was a bunch more stuff to fix 😃

One issue I did hit with this example:
const res = await fetch('https://www.google.com');
const text = await res.text();
console.log(text);

is that it throws (new TypeError("malformed UTF-8 character sequence at offset 1", ""))
Is decompression properly supported?

@guybedford ah, interesting. The fetch implementation indeed doesn't do transparent decompression. But usually that shouldn't matter either, because we're not setting the Accept-Encoding header. Are you setting that, by any chance?

@tschneidereit because we virtualize on top of Node.js's fetch implementation it might be overriding that I expect, posted https://github.com/bytecodealliance/jco/issues/447 to investigate further.

Actually I spoke too soon. Running against a test server I'm getting mangled response body data. Headers are just {"host":"localhost:8080","connection":"keep-alive"}. But the body the test server is sending back doesn't seem to reflect at all. Again, this could be ComponentizeJS / Jco toolchain specific, but I'd have to dig into it more. We did pass all the WASI HTTP tests though, so I haven't seen any mangled response issues before, unless there are gaps in the test suite.

@guybedford I fixed a whole bunch of additional issues now. Would be great if you could take a look at the additional commits I pushed since your review. Then we should land this, and move everything else into additional PRs. (Of which I'll open a few in a moment, stacked on top of this one 😄)

Thank you for the review! I pushed a commit addressing your comments. While there's a bunch of code motion in that commit, it's all trivial, so I'll go ahead and land this.

authors: guybedford tschneidereit

repo: bytecodealliance/StarlingMonkey


text:
Update deps to latest.

This includes a cargo patch for the wasm-tools crates to fix a build issue now that wit-bindgen no longer depends on the removed wit-parser ABI support.

Sigh, looks like we'll have to insert the patch into every generated test project. Let's see if we can do a release of wit-bindgen/wasm-tools instead.

@elliottt can I trouble you for a quick :+1: to unblock the other PRs? Thanks!

source: gharchive/pull-request

repo: bytecodealliance/cargo-component

license_type: permissive

license_source: github-api


text:
Support creating a set of imports with once piece of shared state easily

One thing the current wasmtime::Func API isn't great at is sometimes (for example with WASI) you want to create a set of functions that all share the same piece of state. Sort of like a trait that has a bunch of functions on it. This is possible today but it involves manually creating a lot of Func instances and explicitly using Rc to share state between each import.
It'd be nicer if we could explore possibly alternative ways of doing this. For example if we had like a FuncBuilder<T> where you passed it Fn(&T, Args...) -> R and it handed back a Func. That might make it easier to have shared state amongst a set of functions without having to manually deal with all the clunky Rc allocations.
To be clear I think this is basically about expressiveness, I believe everything should already be possible that needs to get done today. This may be more optimizable by the API as well, but we'd have to measure!

Ideally, I would suggest that we introduce an API for a HostModule object, which can have multiple named functions handed to it, and which can in the future participate in linking symbols by name. That object could provide various function builders.

This was fixed in the recently redesigned API

source: gharchive/issue

authors: alexcrichton joshtriplett

repo: bytecodealliance/wasmtime


text:
wasmtime -g panic

#include <stdio.h>
int main(void)
{
puts("Hello");
return 0;
}
built with wasi sdk v16.5: /opt/wasi-sdk/dist/wasi-sdk-16.5ga0a342ac182c/bin/clang --target=wasm32-unknown-wasi --sysroot /opt/wasi-sdk/dist/wasi-sysroot -g -O0 -v -o hello.wasm hello.c
wasmtime version: wasmtime-cli 0.40.0
lldb version: lldb version 10.0.0
linux wsl2: 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
run: wasmtime -g hello.wasm
exception thrown:
0: rust_begin_unwind
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/panicking.rs:142:14
2: core::result::unwrap_failed
at /rustc/4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/result.rs:1805:5
3: wasmtime_jit::debug::create_gdbjit_image
4: wasmtime_jit::instantiate::CompiledModule::from_artifacts
5: wasmtime::module::Module::from_parts
6: wasmtime::module::Module::from_binary
7: wasmtime::module::Module::from_file
8: wasmtime_cli::commands::run::RunCommand::load_module
9: wasmtime_cli::commands::run::RunCommand::execute
10: wasmtime::main

Please see https://github.com/bytecodealliance/wasmtime/issues/4669#issuecomment-1210997950 In any case can you upload the wasm file itself. That will help with reproducing it in the future if someone wants to work on fixing this bug.

hello.wasm.txt
Please rename the .txt file to original hello.wasm.

I drew inspiration from wasi example of wasmtime project itself. although lldb -- wasmtime run -g xyz.wasm throws nasty panic, the programmatical approach seemed to work fine e.g. set debug info to true. basically, adopted the wasi example and added config to set debug info = true. lldb ./wasi, set breakpoint for method name main (c wrapper) and _start (default wasi export). while in lldb debug session, run , gui, source code view is available.


text:
Support for SpiderMonkey's "Wasm ABI 2020" in general and on AArch64.

As part of a Wasm JIT update, SpiderMonkey is changing its internal
WebAssembly function ABI. The new ABI's frame format includes "caller
TLS" and "callee TLS" slots. The details of where these come from are
not important; from Cranelift's point of view, the only relevant
requirement is that we have two on-stack args that are always present
(offsetting other on-stack args), and that we define special argument
purposes so that we can supply values for these slots.
Note that this adds a new ABI (a variant of the Baldrdash ABI) because
we do not want to tightly couple the landing of this PR to the landing
of the changes in SpiderMonkey; it's better if both the old and new
behavior remain available in Cranelift, so SpiderMonkey can continue to
vendor Cranelift even if it does not land (or backs out) the ABI change.
Furthermore, note that this needs to be a Cranelift-level change (i.e.
cannot be done purely from the translator environment implementation)
because the special TLS arguments must always go on the stack, which
would not otherwise happen with the usual argument-placement logic; and
there is no primitive to push a value directly in CLIF code (the notion
of a stack frame is a lower-level concept).
Corresponds to patch on SpiderMonkey bug 1657802.

Updated for x64, thanks! I see a few failures on SpiderMonkey-x64 with e.g. jit-test/tests/wasm/bigint/bigint.js (and I have to test with --no-wasm-simd to get Cranelift now on x64); I'm not sure if this is pre-existing, since we don't run the new x64 backend on CI there; but all of the basic functionality seems to work, so the basic stack-slot setup in this PR should be correct, I think.

Updated -- that was a fun one to track down! (Ten points to Gryffindor rr...).
The problem is that we weren't restoring the TLS register in the epilogue -- unlike IonMonkey, we do not treat the TLS register as an unallocatable fixed register, but rather we just copy its value to an ordinary SSA value on function entry. Apparently we were free to clobber it previously, but now we are not. Easy enough to handle in the clobber-restore sequences.
When vendored in, this passes SpiderMonkey's jit-tests on both x64 (--wasm-compiler=cranelift --no-wasm-simd) and aarch64 (--wasm-compiler=cranelift).


text:
Replace nix dependency with in-house yanix crate

This commit replaces nix dependency with an in-house solution,
which borrows heavily from the nix crate, called yanix.
yanix stands for Yet Another Nix crate and is exactly what the name
suggests: an adaptation of the nix crate featuring certain
adjusments and additions tailored specfically to its main application
area which are implementation of WASI syscalls.
Since this commit belongs to the category of relatively big refactoring
efforts, here's a summary breakdown of major changes:

all uses of nix crate were replaced with yanix, and where
possible, uses of raw libc calls was wrapped in a safe Rust fn and
moved to the yanix crate
a couple of emscripten cfgs was added here and there, with the
ultimate goal being able to cross-compile wasi-common to the
emscripten target
fast-forwards snapshot_0 to the latest host-specific implementation
so that this commit can be fully testable

Now, onto what this commit doesn't:

perform full-fledged refactoring of the *nix implementation - on the
contrary, it barely scratches the surface; I welcome subsequent PRs
which brings us closer to this goal though! :-)
make it possible to cross-compile wasi-common to emscripten target
yet, but hopefully, brings us one step closer

From more detailed shortcomings of this commit, the implementation of
Dir (i.e., wrapper around readdir) is still left inside the
wasi-common proper for now, but if the time permits, I'll take a look
at moving it into the yanix crate where it seems to belong.
This PR relates to #520

cc @marmistrz

The change is so large that it's basically unreviewable. For the future, please try to split such changes into commits that could be reviewed separately. In particular, it would be good to have a separate commit for the functions that were just kanged from nix and a separate one for our wrappers.

Excellent point, and my apologies for the size of this PR, however, given the non-trivial nature of this task (replacing one core dependency with another), I've tried my best to keep the changes to minimum. Anyhow, this PR seems so large mainly due to the presence of changes in both the upstream and snapshot_0 which are essentially exactly the same bits of code, so you can safely ignore reviewing the changes in snapshot_0.

Shouldn't you attribute the nix developers as the crate authors? I guess that most code was taken from nix.

Absolutely! I haven't adjusted the authors bits in Cargo.toml just yet.

Actually, if it makes sense, I believe I can still chop this PR into a couple smaller ones if it aids the reviewing process. Now that I've got everything in place, I should be able to submit a series of PR instead of one large change. My main thinking behind one large change was that we'll have a setup tested from end to end. Lemme know what everyone thinks!

I'm gonna close this for now, as @sunfishcode and I have decided it would be better to avoid copying big chunks of code from nix. Instead, we believe we can easily rewrite those bits ourselves which will save us from having to deal with multi-licensing, etc. After I make the necessary adjustments to yanix, I will open a new PR for review.


text:
Remove CLI flags ordering from release notes

That commit was backed out.

Dupe of #6834.


text:
Patch size 8

Hello,
DINO reports excellent results using a patch size of 8 (+2.7 top1 accuracy on i1k for ViT-S and +1.9 for ViT-B, better segmentation results). Have you considered this setting ?
Overall do you consider doing additional experiments using iBOT ?
Best,
Simon

Hi @SimJeg,
Sorry for the late reply. No, we do not plan to scale iBOT for a larger sequence length. I think the performance gain should be valid with ViT-S/8 or ViT-B/8. You could try to run the experiment yourself with a few arguments changed for models with a patch size of 8 following DINO's args. Results are welcomed!

authors: SimJeg shallowtoil

repo: bytedance/ibot


text:
🛑 shlink is down

In 2375aca, shlink (https://l.byzocker.de) was down:

HTTP code: 502
Response time: 1125 ms

Resolved: shlink is back up in 552aa5c.

license: MIT


text:
app(styling): update color scheme and header (#5)

app(styling): update color scheme

feat(welcomeMsg): add stroke to h1

Looks good to me :rocket:

repo: c-grigsby/computer-vision


text:
Create Dataset

Create our dataset. Use our camera. Buy fruits. And prepare whole structure of folder with images

I created dataset of ~12tys images.
Firstly do images of 10 different classes of fruits. 80 images each.
Then augment data : original, mirror vertical, mirror horizontal, rotate different angels,
mirror rotated, diffrent brightness, noise.
At the end there are 12662 images.


text:
issue: 173 Mobile footer be less bad

Completes issue #173 Mobile footer be less bad .
Changes in this pull request:

Footer sections go full width on phones
Also made landing image stretch on phone to not have weird horizontal scrolling

:fire:

authors: firoze gotoplanb

license: mit

license_source: bigquery


text:
button rename

Now that the bSDD xslx is here (Yes!!) it may be a good idea to rename the 'Load Excel File' to something like 'xlsx to IDS xml'?

good idea! fix!


text:
chore: prepare new release

Motivation
To prepare the new release, the chart's appVersion needs to be bumped and the docs need to be adjusted.
Changes
I've bumped the appVersion and adjusted the docs.
I've also adjusted some of the default values in the chart to be aligned with the configuration options of the docs. The values before were rather confusing to new users.

chore: bump chart app version
fix: sparrow config values for chart
docs: adjust docs to new release

For additional information look at the commits.
Tests done
The sparrow deploys successfully with the newest image of the main branch.
$ helm upgrade sparrow ./chart/ -i --set image.tag=commit-ae8c61e -n sparrow --create-namespace
Release "sparrow" does not exist. Installing it now.
NAME: sparrow
LAST DEPLOYED: Wed Feb 21 12:11:14 2024
NAMESPACE: sparrow
STATUS: deployed
REVISION: 1
TEST SUITE: None

TODO

[x] I've assigned this PR to myself
[x] I've labeled this PR correctly

Please look at the docs again, maybe I've forgot to adjust something.

repo: caas-team/sparrow


text:
Request : Cheat : Weapon Switching as a Free Action

No hurry :)

if you are on turnbased can't the unlimited actions options work, could just turn it on, do your switch weapon then turn it off, you don't often switch weapons in combat anyway so it's not super inconvenient.

Unlimited Actions doesn't want to work anymore, I found, and additionally, it should be a free action as soon as you get a BAB of +1, so long as you do a move action!

Unlimited actions also dont work for me

authors: Amariithynar LukeRibbons Rudm0909 fazliamri

repo: cabarius/ToyBox


text:
Question: DNS-01 Challenge results in multiple DNS requests?

What is your question?
When using the DNS-01 Challenge, is it normal that the DNS Server receives multiple (up to 4) requests for _acme-challenge?
What have you already tried?
I tried skimming through the RFC, couldn't really find any mention of it.
I also read the documentation from Let's Encrypt but couldn't find any mention of this either.
So I am wondering if this is normal ACME-Challenge behaviour, or If there is something strange going on.
Bonus: What do you use this package for, and does it help you?
For context, I am trying to develop a CoreDNS Plugin that can automate tls certificates when CoreDNS itself is the autoritative DNS Server for the Domain. Currently testing this out with my own domain. While it seems to work (most of the time), I sometimes only receiv 1 or 2 of these requests and then the Challenge fails - and I am currently trying to figure out why.
[INFO] plugin/tls: Obtaining TLS Certificate, may take a moment
[INFO] plugin/tls: Answering ACME DNS request:_acme-challenge.ns1.subdomain.mariuskimmina.com.
[INFO] plugin/tls: Answering ACME DNS request:_acme-challenge.ns1.subdomain.mariuskimmina.com.
[INFO] plugin/tls: Answering ACME DNS request:_acme-challenge.ns1.subdomain.mariuskimmina.com.

In cases where I only receiv 1 or 2 of these requests, the log looks like this:
[INFO] plugin/tls: Answering ACME DNS request:_acme-challenge.ns1.subdomain.mariuskimmina.com.
[INFO] plugin/tls: Answering ACME DNS request:_acme-challenge.ns1.subdomain.mariuskimmina.com.
[ERROR] plugin/tls: Failed to setup TLS automatically: [ns1.subdomain.mariuskimmina.com] Obtain: [ns1.subdomain.mariuskimmina.com] solving challenge: ns1.subdomain.mariuskimmina.com: [ns1.subdomain.mariuskimmina.com] authorization failed: HTTP 400 urn:ietf:params:acme:error:dns - During secondary validation: DNS problem: SERVFAIL looking up TXT for _acme-challenge.ns1.subdomain.mariuskimmina.com - the domain's nameservers may be malfunctioning (ca=https://acme-v02.api.letsencrypt.org/directory)

Yes, some CAs like Let's Encrypt use multi-perspective validation to mitigate BGP attacks, etc: https://letsencrypt.org/2020/02/19/multi-perspective-validation.html

That perfectly explains what's going on here, thanks a lot!
I'm still not sure why some of those requests don't reach me sometimes but still you really helped me out here

Good luck!

authors: mariuskimmina mholt

repo: caddyserver/certmagic


text:
provider.oauth2 seems not to appear when added from pip on settings.py

Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/Library/Python/2.7/site-packages/django/core/management/init.py", line 350, in execute_from_command_line
utility.execute()
File "/Library/Python/2.7/site-packages/django/core/management/init.py", line 324, in execute
django.setup()
File "/Library/Python/2.7/site-packages/django/init.py", line 18, in setup
apps.populate(settings.INSTALLED_APPS)
File "/Library/Python/2.7/site-packages/django/apps/registry.py", line 85, in populate
app_config = AppConfig.create(entry)
File "/Library/Python/2.7/site-packages/django/apps/config.py", line 90, in create
module = import_module(entry)
File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/Library/Python/2.7/site-packages/provider/oauth2/init.py", line 1, in
import backends
File "/Library/Python/2.7/site-packages/provider/oauth2/backends.py", line 2, in
from .forms import ClientAuthForm, PublicPasswordGrantForm
File "/Library/Python/2.7/site-packages/provider/oauth2/forms.py", line 10, in
from .models import Client, Grant, RefreshToken
File "/Library/Python/2.7/site-packages/provider/oauth2/models.py", line 23, in
class Client(models.Model):
File "/Library/Python/2.7/site-packages/django/db/models/base.py", line 94, in new
app_config = apps.get_containing_app_config(module)
File "/Library/Python/2.7/site-packages/django/apps/registry.py", line 239, in get_containing_app_config
self.check_apps_ready()
File "/Library/Python/2.7/site-packages/django/apps/registry.py", line 124, in check_apps_ready
raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

Same symptom here.

same here

Same

getting same error .....plz help...

authors: RahulDwiwedi eddwinpaz horriblyUnpythonic josharchibal sanderroosendaal


text:
Fix GH Action names

This simple PR fixes a couple GitHub Action names for uniqueness.
Also, this is a good test of the per-PR site preview function, now that it's live.

Yep, builds again when reopened. I like it.


text:
Allow Taskbar Quick Launch Icons to be Organized

Hello, I have a feature request. Can we please gain the ability to organize taskbar quick launch icons manually(non-alphabetic), via app grabber?
Cheers!

Great idea, I will look into adding this.

This is now available in the latest release.

authors: Carbongrip dremin

repo: cairoshell/cairoshell


text:
Create static.yml

Allows you to publish your static html to a custom page for your repo. I haven't configured this file at all.

:shipit:

repo: cajunluke/dial-a-bart


text:
🛑 XMR Asia Servers is down

In 44885f1, XMR Asia Servers ($XMR_ASIA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR Asia Servers is back up in 593a88c after 14 minutes.

repo: cake-tech/upptime-cakewallet


text:
🛑 buy.cakepay.com is down

In 188e1dc, buy.cakepay.com (https://buy.cakepay.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: buy.cakepay.com is back up in 6d1b2b7 after 6 minutes.


text:
🛑 XMR EU Servers is down

In 2d8da15, XMR EU Servers ($XMR_EU) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR EU Servers is back up in c248f11 after 9 minutes.


text:
🛑 XMR Asia Servers is down

In ff4097b, XMR Asia Servers ($XMR_ASIA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR Asia Servers is back up in 7122e96 after 9 minutes.


text:
🛑 XMR EU Servers is down

In a863858, XMR EU Servers ($XMR_EU) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR EU Servers is back up in 1902575 after 8 minutes.


text:
🛑 xmr-node.cakewallet.com:18081 is down

In 2890809, xmr-node.cakewallet.com:18081 (xmr-node.cakewallet.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: xmr-node.cakewallet.com:18081 is back up in b5494c5 after 5 minutes.

repo: cake-tech/upptime-monerocom


text:
🛑 node.moneroworld.com:18089 is down

In 311aec4, node.moneroworld.com:18089 (node.moneroworld.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: node.moneroworld.com:18089 is back up in c1c65ef.


text:
🛑 node.moneroworld.com:18089 is down

In 9bf8b60, node.moneroworld.com:18089 (node.moneroworld.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: node.moneroworld.com:18089 is back up in 5c885db.


text:
Can I override addTimestamps?

Can I override addTimestamps() method? I don't like some of the default settings it using like the timestamp type for both created_at and updated_at and that only the created_at gets the current timestamp.
I'd like to set both  created_at and updated_at as datetime type and default value on both to be NOW(), is that possible some how?

Does someone want to address this, or make a PR?

repo: cakephp/phinx


text:
chore(*): update dependencies

I spent a bit of time a few weeks ago submitting some PRs to express-graphql. All of them got merged (except one) so I figured it was time to update the express-graphql dependency and all the others while I was at it.

Looks good to me.

authors: calebmer ferdinandsalis

repo: calebmer/postgraphql


text:
Fix label display with Chrome autocomplete

This fixes the issue with the floating label being hidden when the field is selected by Chrome to be autocompleted as it was rendered under Chrome's yellow background highlight of the field
Before:

After:

@EnzoMartin Thanks. The travis fails but that's more likely linked to babel@6 release

authors: EnzoMartin oliviertassinari

repo: callemall/material-ui


text:
feat(bundle): better minification

I've found that on iOS my bundle was about 15 MB because of all of the source-maps. With this fix, it dropped to 2.3 MB.

@zamotany Hey. Now it should be OK. The problem was, that we added a plugin for source maps twice, one was due to devtool and the other one because of implicit adding of the plugin. But still, could you please confirm that I don't introduce any malfunction? Thanks in advance!
cc @satya164

repo: callstack/haul


text:
How to config repack to run index.js code when run ScriptManager.loadScript in native side

Ask your Question
Hi Team. I try to run miniapp chunk:

With repack v2: Call ChunkManager.loadChunk (Run in Native Side) -> The code in index.js of miniapp will evaluate
With repack v3 . ScriptManager.loadScript (Run in Native Side) -> The code in index.js of miniapp not evaluate (Run in Super app showcase)
Resource link:
V3 webpack config: https://github.com/callstack/super-app-showcase/blob/main/packages/dashboard/webpack.config.mjs
How to config repack to run index.js code of the miniapp when running ScriptManager.loadScript in native side from v3  (Webpack config, Bootstrap script, Plugin)?

Thanks team.

Thanks for your response.
I want to load code in index.js file of miniapp project when using ScriptManager.loadScript to execute miniapp.bundle from native without run Federated.importModule('MiniAppChunkID', './index.js'),

webpack config miniapp

    new Repack.plugins.ModuleFederationPlugin({
    /**
     * The name of the module is used to identify the module in URLs resolver and imports.
     */
    name: 'MiniAppChunkID',
    exposes: {

      'MiniAppChunkID': './index.js',
    },
    }

Repack patch

async function repackScriptStartup() {
repackRuntime.shared.loadScriptCallback.push([$chunkId$]);
let chunkId = $chunkId$;
if (chunkId != 'main') {
let scope = 'default';
if (
repackRuntime.shared.scopes &&
(!repackRuntime.shared.scopes[scope] ||
!repackRuntime.shared.scopes[scope].__isInitialized)
) {
// Initializes the share scope.
// This fills it with known provided modules from this build and all remotes.
await repackRuntime.shared.initSharing(scope);
repackRuntime.shared.scopes[scope].__isInitialized = true;
}
    const container = (self as any)[chunkId];

    if (!container.__isInitialized) {
      container.__isInitialized = true;
      // Initialize the container, it may provide shared modules
      await container.init(repackRuntime.shared.scopes[scope]);
    }

    const factory = await container.get(chunkId);
    const exports = factory();
    return exports;
  }
}

After that. It work

Thanks for your response.
I want to load code in index.js file of miniapp project when using ScriptManager.loadScript to execute miniapp.bundle from native
without run Federated.importModule('MiniAppChunkID', './index.js'),
webpack config miniapp
    new Repack.plugins.ModuleFederationPlugin({
    /**
     * The name of the module is used to identify the module in URLs resolver and imports.
     */
    name: 'MiniAppChunkID',
    exposes: {

      'MiniAppChunkID': './index.js',
    },
    }

Im try
```
async function repackScriptStartup() {
repackRuntime.shared.loadScriptCallback.push([$chunkId$]);
let chunkId = $chunkId$;
if (chunkId != 'main') {
let scope = 'default';
if (
repackRuntime.shared.scopes &&
(!repackRuntime.shared.scopes[scope] ||
!repackRuntime.shared.scopes[scope].__isInitialized)
) {
// Initializes the share scope.
// This fills it with known provided modules from this build and all remotes.
await repackRuntime.shared.initSharing(scope);
repackRuntime.shared.scopes[scope].__isInitialized = true;
}
    const container = (self as any)[chunkId];

    if (!container.__isInitialized) {
      container.__isInitialized = true;
      // Initialize the container, it may provide shared modules
      await container.init(repackRuntime.shared.scopes[scope]);
    }

    const factory = await container.get(chunkId);
    const exports = factory();
    return exports;
  }
}

After that. It work

Thanks for your response.
I want to load code in index.js file of miniapp project when using ScriptManager.loadScript to execute miniapp.bundle from native
without run Federated.importModule('MiniAppChunkID', './index.js'),
webpack config miniapp
    new Repack.plugins.ModuleFederationPlugin({
    name: 'MiniAppChunkID',
    exposes: {

      'MiniAppChunkID': './index.js',
    },
    }

Im try
async function repackScriptStartup() {
      repackRuntime.shared.loadScriptCallback.push([$chunkId$]);
      let chunkId = $chunkId$;
      if (chunkId != 'main') {
        let scope = 'default';
        if (
          repackRuntime.shared.scopes &&
          (!repackRuntime.shared.scopes[scope] ||
            !repackRuntime.shared.scopes[scope].__isInitialized)
        ) {
          await repackRuntime.shared.initSharing(scope);
          repackRuntime.shared.scopes[scope].__isInitialized = true;
        }
        const container = (self as any)[chunkId];
        if (!container.__isInitialized) {
          container.__isInitialized = true;
          // Initialize the container, it may provide shared modules
          await container.init(repackRuntime.shared.scopes[scope]);
        }
        const factory = await container.get(chunkId);
        const exports = factory();
        return exports;
      }
    }

After that. It work

repo: callstack/repack


text:
Aun no mezclar hasta que....

Quitar el útlimo commit, el q dice experimentando con el butestrap limpio

ya se puede mezclar seguramente

repo: calonso-conabio/buscador


text:
Public Release for Fall24 meta-release

According to the discussion in: V0.2.0 M4 by FabrizioMoggio · Pull Request #95 · camaraproject/CallForwardingSignal (github.com)
M4 version for Fall24:

OAS file renamed according to: https://github.com/camaraproject/CallForwardingSignal/issues/93
Remove “-rc.n” from the version and server path: https://github.com/camaraproject/CallForwardingSignal/discussions/92
Remove "-rc.02" from "x-camara-commonalities": https://github.com/camaraproject/CallForwardingSignal/issues/94
updated changelog.md
updated readme.md
updated .feature files according to: https://github.com/camaraproject/CallForwardingSignal/issues/96
updated Readiness CL according to: https://github.com/camaraproject/CallForwardingSignal/issues/97
updated changelog.md according to: https://github.com/camaraproject/CallForwardingSignal/issues/98
updated readme.md according to: https://github.com/camaraproject/CallForwardingSignal/issues/100

What type of PR is this?
Add one of the following kinds:

subproject management
cleanup
documentation

What this PR does / why we need it:
final release for Fall24
Which issue(s) this PR fixes:

https://github.com/camaraproject/CallForwardingSignal/issues/94
https://github.com/camaraproject/CallForwardingSignal/issues/93
https://github.com/camaraproject/CallForwardingSignal/issues/96
https://github.com/camaraproject/CallForwardingSignal/issues/97
https://github.com/camaraproject/CallForwardingSignal/issues/98
https://github.com/camaraproject/CallForwardingSignal/issues/100
Special notes for reviewers:
PR done on behalf of @FabrizioMoggio
Changelog input
 release-note

Additional documentation
This section can be blank.
docs

@tanjadegroot For context: @FabrizioMoggio has issue with easyCLA so I copied his PR.
I fixed your review comments.
Regarding your 2 questions from the yaml:
on line 229: does unconditional forwarding overwrite conditional forwarding if both are active ?
Ludo: I tend to think that unconditional has predominance and override all other but happy to listen from @FabrizioMoggio
on line 230: with "This endpoint exceeds the main scope of the CFS API, for this reason an error code 501 can be returned" do you mean that this second endpoint is optional and may not be provided and that 501 is returned in that case ?
Ludo: Yes

@tanjadegroot For context: @FabrizioMoggio has issue with easyCLA so I copied his PR. I fixed your review comments. Regarding your 2 questions from the yaml:
on line 229: does unconditional forwarding overwrite conditional forwarding if both are active ? Ludo: I tend to think that unconditional has predominance and override all other but happy to listen from @FabrizioMoggio
on line 230: with "This endpoint exceeds the main scope of the CFS API, for this reason an error code 501 can be returned" do you mean that this second endpoint is optional and may not be provided and that 501 is returned in that case ? Ludo: Yes

_on line 229: my sentence was actually intended to just say that more than one kind of call forwarding service can be active at the same time and that the API will provide back every kind of service that is configured. The main kind are unconditional and conditional than we can have different flavors of conditional. The logic of what can be configured in the Network and the priorities of the call fwd services have no effect on the API. Anyway I agree,  if the they are both active in the same timeslot, unconditional  takes the precedence.
-on line 230: some additional information here: https://github.com/camaraproject/CallForwardingSignal/issues/37#issuecomment-2210346948

repo: camaraproject/CallForwardingSignal


text:
New API for location subscriptions

What type of PR is this?
enhancement/feature
What this PR does / why we need it:
Create a new API for creating subscriptions for location based events
Which issue(s) this PR fixes:
This PR is related to issue #18  Subscription for Location Area

Fixes #
Special notes for reviewers:
Changelog input
 release-note

Additional documentation
This section can be blank.
docs

@chia2017 you still have to define the details in the specific events being notified, that is the device and area.
        eventDetail:
          type: object -> here instead of object

Rename api to geofencing

Hi, I renamed the api two weeks ago before I went to vacation. So I did not recieve any new comment about review, If you think everything is fine you can merge this PR, but first it need two approvers. Anyway I am available if you have any comment.
Best,
Sadeghi

Rename api to geofencing

Hi, I renamed the api two weeks ago before I went to vacation. So I did not recieve any new comment about review, If you think everything is fine you can merge this PR, but first it need two approvers. Anyway I am available if you have any comment. Best, Sadeghi

Hi Sadeghi. I made another review. I think it is almost ready. Once @bigludo7 is back and make a further check we can merge. Thanks!

@chia2017 @jlurien Thanks for the effort - It looks good for me and thanks to have fixed my previous comments. Once José comments resolved we should be good for merging

I updated the API and applied all last comments that you wrote. If you have no more comment you can merge it and we can close the task. If you have further request you can contact my colleague Maximilian Laue, since I am not working with this project and I switched to the new project.
Best,
Sadeghi

I updated the API and applied all last comments that you wrote. If you have no more comment you can merge it and we can close the task. If you have further request you can contact my colleague Maximilian Laue, since I am not working with this project and I switched to the new project. Best, Sadeghi

@bigludo7 & @jlurien:
Could you please review again.
When anything needs to be adapted then I will fix it asap.
Thanks! 🚀

Thanks @chia2017 for the effort and good luck for your new project
@maxl2287 As of now we cannot approve because following DT suggestion (and CAMARA team approval) the event notification should be aligned with the CloudEvents.
This update is describe here: https://github.com/camaraproject/Commonalities/pull/56  and right now is in team review.
My recommendation is to wait for approval before to adjust your code.
Thanks

Now that https://github.com/camaraproject/Commonalities/pull/56 has been merged, we should update this PR accordingly @maxl2287, @akoshunyadi. Thanks

I created PR #98 to align on CloudEvents based on these commits here.
In the fact that @chia2017 is not part of the CAMARA project anymore and I am not allowed to add commits to his repository.

This feature is now followed here: https://github.com/camaraproject/DeviceLocation/pull/98

repo: camaraproject/DeviceLocation


text:
admin/user/index.blade

add message with icon on member index

J'ai encore fait des corrections au niveau HTML et aussi au niveau du controller

authors: Noksit cbouvat


text:
Fix TypeScript build in 1.0.0 branch

Don't know why, but the tsconfig.json composite build has stopped working in the 1.0.0 branch.

This is fixed. The issue was the command needed to build it is npm run build.


text:
Fix vulnerable deps

This replaces warnings-triggering canvg-browser with canvg, and upgrades some deps via npm audit fix.
Note that this touches PNG/JPG export facility. It works on my Mac though.

I see that canvg is more actively supported nowaday, which is great to see.

Follow up: https://github.com/bpmn-io/canvg-browser/pull/3.

authors: barmac nikku

repo: camunda/camunda-modeler


text:
[ENHANCEMENT] Add variable for camunda.operate.elasticsearch.indexPrefix

Describe the use case:
To use single common Elasticsearch for 2 different zeebe clusters and corresponding 2 Operate instances, I have to specify prefixes for indices:

camunda.operate.zeebeElasticsearch.prefix
camunda.operate.elasticsearch.indexPrefix

Helm chart contains variable global.elasticsearch.prefix that specifies the camunda.operate.zeebeElasticsearch.prefix property, but none I've found for camunda.operate.elasticsearch.indexPrefix
Describe the enhancement/feature:
Add variable for camunda.operate.elasticsearch.indexPrefix
Desired outcome and acceptance tests:
Variable added

@galingerv Thanks for opening this issue :raised_hands:
AFAIK the prefix isn't supported in all apps of 8.6 and below (namely Optimize)
We will support that in 8.7 as shown in PR no. https://github.com/camunda/camunda-platform-helm/pull/2643/
So I'd close this task as no action is needed for it because consistency is not possible for all apps (if you want to do that for some apps like Operate and Tasklist, you can use operate.configuration and tasklist.configuration for Camunda 8.6 and below).

authors: aabouzaid galingerv

repo: camunda/camunda-platform-helm


text:
Adjust the how to apply footer

Adjusted text and added a link to the supplier guide

Hey @smellems could you have a look at this PR if you have a sec?  I can't get the link to the supplier guide in the footer to work. I'm getting a liquid exception/Jekyll error message.

repo: canada-ca/micro-acquisition


text:
Instrument Otel

Description
This PR introduces otel tracing logs.
We collect traces on (get/count/create/update/delete/list/update/compact/dbsize)
When you run make jaeger, the traces are collected in a local jaeger instance at http://localhost:16686.

The metric counters (get/count/create/update/delete/list/update) are written to stdout every 30 seconds.
(Limitation: Jaeger can't accept these metrics)
{
      "Name": "k8s-dqlite.get",
      "Description": "Number of get requests",
      "Unit": "",
      "Data": {
        "DataPoints": [
          {
            "Attributes": [],
            "StartTime": "2024-07-10T09:52:13.907275271+02:00",
            "Time": "2024-07-10T10:24:13.907264437+02:00",
            "Value": 1685
          }
        ],
        "Temporality": "CumulativeTemporality",
        "IsMonotonic": true

@bschimke95

Nice work

Fly-by comment: I've like to see some docs about where the parent span comes from, env? header field? etc. Additionally, given the distributed nature of dqlite, how spans in dlite peers may be linked to each other.

Fly-by comment: I've like to see some docs about where the parent span comes from, env? header field? etc. Additionally, given the distributed nature of dqlite, how spans in dlite peers may be linked to each other.

@dimaqq Great question!
To answer your first question, we retrieve information about the parent span from the context header fields. See otel's spanContext, they follow the W3C TraceContext Specification.
In summary, a traceparent header has the values span-id trace-id and trace-flags (sampled flag). Additionally, the tracestate header is used which allows for multiple tracing systems in a trace.

Here are some screenshots from traces I found interesting/have questions about:
Does revision 0 mean a deleted entry? Why is there a count 9 on it?

Backend updates run very frequently in an idle cluster. Interestingly, lease is always zero for these. A create query returns a lease > 0.

Idle cluster runs constant update queries:

This shows the revision range that we run two consecutive compactions on:

While I had my cluster running idle I found this outlier:
Our compaction ran for 5m40s instead of our normal 6seconds.

Consequences for the cluster:

The next compaction spike should show which sql query is our culprit or if we have a bug in the kine layer. If it's in the sql query we will get more insight from Marco's work on metrics in dqlite.

Side-note: Our kine layer already tracks some metrics here: http://127.0.0.1:9042/metrics:
See an example output here

In the idle cluster compaction runs at ~6s, every now and then we have a few that take longer, there seems to be a slowdown in these sql queries. Maybe this is due to admissions?

authors: dimaqq eaudetcobello louiseschmidtgen


text:
Error getting active endpoint: revision.serving.knative.dev "" not found when doing Serverless InferenceServing

Bug Description
I have created a Serverless Kserve InferenceService and tried performing inference, but instead of getting a prediction, I get:
Error getting active endpoint: revision.serving.knative.dev "" not found
* Connection #0 to host 10.152.183.40 left intact

To Reproduce

juju deploy kubeflow 1.8/stable --trust
Apply the following InferenceService in a Profile namespace or on default (the result is the same)

apiVersion: "serving.kserve.io/v1beta1"
kind: "InferenceService"
metadata:
  name: "sklearn-iris-ckf-1-8"
spec:
  predictor:
    model:
      modelFormat:
        name: sklearn
      storageUri: "gs://kfserving-examples/models/sklearn/1.0/model"

Wait for the isvc to be ready `

$ kubectl get isvc -ndaniela
NAME                   URL                                                       READY   PREV   LATEST   PREVROLLEDOUTREVISION   LATESTREADYREVISION                    AGE
sklearn-iris-ckf-1-8   http://sklearn-iris-ckf-1-8.daniela.10.64.140.43.nip.io   True           100                              sklearn-iris-ckf-1-8-predictor-00001   21m

Perform inference on the ClusterIP and on the isvc URL

The `iris-output.json comes from here

# Using the ClusterIP
ubuntu@charm-dev-jammy:~$ kubectl get svc -ndaniela | grep sklearn
sklearn-iris-ckf-1-8-predictor-00001           ClusterIP      10.152.183.40    <none>
ubuntu@charm-dev-jammy:~$ curl -v -H "Content-Type: application/json" 10.152.183.40/v1/models/sklearn-iris:predict -d @./iris-input.json
*   Trying 10.152.183.40:80...
* Connected to 10.152.183.40 (10.152.183.40) port 80 (#0)
> POST /v1/models/sklearn-iris:predict HTTP/1.1
> Host: 10.152.183.40
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 76
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Thu, 30 Nov 2023 13:04:59 GMT
< Content-Length: 73
<
Error getting active endpoint: revision.serving.knative.dev "" not found
* Connection #0 to host 10.152.183.40 left intact

# Using the isvc URL
ubuntu@charm-dev-jammy:~$ kubectl get isvc -ndaniela
NAME                   URL                                                       READY   PREV   LATEST   PREVROLLEDOUTREVISION   LATESTREADYREVISION                    AGE
sklearn-iris-ckf-1-8   http://sklearn-iris-ckf-1-8.daniela.10.64.140.43.nip.io   True           100                              sklearn-iris-ckf-1-8-predictor-00001   24m

ubuntu@charm-dev-jammy:~$ curl -v -H "Content-Type: application/json" http://sklearn-iris-ckf-1-8.daniela.10.64.140.43.nip.io/v1/models/sklearn-iris:predict -d @./iris-input.json
*   Trying 10.64.140.43:80...
* Connected to sklearn-iris-ckf-1-8.daniela.10.64.140.43.nip.io (10.64.140.43) port 80 (#0)
> POST /v1/models/sklearn-iris:predict HTTP/1.1
> Host: sklearn-iris-ckf-1-8.daniela.10.64.140.43.nip.io
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 76
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< location: http://10.64.140.43.nip.io/dex/auth?client_id=authservice-oidc&redirect_uri=%2Fauthservice%2Foidc%2Fcallback&response_type=code&scope=openid+profile+email+groups&state=MTcwMTM0OTU4NnxOd3dBTkZkVVdrWk9UVnBIV1VGRVExSk1Uak5ZV1RjeVRsazBOMVZHVjAxUU4wOUJUVm95UmtSTlJUTkdRVGRVV2taTlZVUklOVUU9fMEGXL81whT_EM5vSRMamOezFLz9hr5HMxsb-7Az2PlD
< set-cookie: oidc_state_csrf=MTcwMTM0OTU4NnxOd3dBTkZkVVdrWk9UVnBIV1VGRVExSk1Uak5ZV1RjeVRsazBOMVZHVjAxUU4wOUJUVm95UmtSTlJUTkdRVGRVV2taTlZVUklOVUU9fMEGXL81whT_EM5vSRMamOezFLz9hr5HMxsb-7Az2PlD; Path=/; Expires=Thu, 21 May 2054 13:59:55 GMT; Max-Age=1200000000000
< date: Thu, 30 Nov 2023 13:06:26 GMT
< x-envoy-upstream-service-time: 4
< server: istio-envoy
< content-length: 0
<
* Connection #0 to host sklearn-iris-ckf-1-8.daniela.10.64.140.43.nip.io left intact

Environment

Microk8s 1.25-strict/stable
juju 3.1
Charmed Kubeflow 1.8/stable

Relevant Log Output
Checking the knative-serving activator pod logs:

{"severity":"ERROR","timestamp":"2023-11-30T13:09:55.657583568Z","logger":"activator","caller":"handler/context_handler.go:74","message":"Error while getting revision","commit":"500756c","knative.dev/controller":"activator","knative.dev/pod":"activator-6dd4b8cc79-zb6lv","knative.dev/key":"/","error":"revision.serving.knative.dev \"\" not found","stacktrace":"knative.dev/serving/pkg/activator/handler.(*contextHandler).ServeHTTP\n\tknative.dev/serving/pkg/activator/handler/context_handler.go:74\nknative.dev/serving/pkg/activator/handler.(*ProbeHandler).ServeHTTP\n\tknative.dev/serving/pkg/activator/handler/probe_handler.go:46\nknative.dev/networking/pkg/http/probe.(*handler).ServeHTTP\n\tknative.dev/networking@v0.0.0-20230419144338-e5d04e805e50/pkg/http/probe/handler.go:39\nknative.dev/serving/pkg/activator/handler.(*HealthHandler).ServeHTTP\n\tknative.dev/serving/pkg/activator/handler/healthz_handler.go:44\ngolang.org/x/net/http2/h2c.h2cHandler.ServeHTTP\n\tgolang.org/x/net@v0.7.0/http2/h2c/h2c.go:125\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:2936\nnet/http.(*conn).serve\n\tnet/http/server.go:1995"}

Additional Context

The isvc's readiness is True
The ksvc's readiness is True
I can see the isvc Pod present in the namespace, but no ksvc one

The issue describes about hitting the SVC directly of the ISVC, but this should not be the way to reach the ISVC. We should always use the high level SVC, which is an ExternalName one, that handles the redirections via VirtualServices and the IGWs.
@DnPlas I propose that we close this issue, since it doesn't follow the standard way for reaching KServe ISVCs. Let's ensure we document the process users should hit KServe in https://github.com/canonical/kserve-operators/issues/205 and in a new one for explaining internal traffic.
Then if in the future we see the same message, but from hitting the ExternalName Service then we can re-open

@kimwnasptd totally agree, I was going to add a comment similar to what you posted. Closing because of this.

authors: DnPlas kimwnasptd

repo: canonical/knative-operators


text:
Added a badge for the publish workflow

Issue
This repo's status is not displayed in the Charm Engineering Releases overview.
Solution
Added a badge for the "publish" workflow.
@ reviewers, does this make sense?

@ reviewers, does this make sense?

@a-velasco what's the meaning of the publish badge? If it's the state of publish of the last merge on the branch, then imo it makes sense

Closing to archive the repo...

authors: a-velasco paulomach taurus-forever

repo: canonical/mysql-router-snap


text:
ubuntu-image: Consolidate docs for contributors to ubuntu-image

The meta docs in the ubuntu-image repo need some restructuring to better serve their purpose:

Rename HACKING.md to CONTRIBUTING.md (to conform to the custom of the hour on GitHub).
Review the content of CONTRIBUTING.md for language, formatting, etc.
Add/move relevant stuff from the root README.md, so that there's a clear distinction between the README (repo info & project introduction), and ther CONTRIBUTING file has all the info for developers.

I would like to adopt this task please.

I'm interested in working on this issue!

Hey @rkratky ! I forked the ubuntu-image repo and created a branch with these fixes on it: https://github.com/nielsenjared/ubuntu-image/tree/oda-issue20-contributing
Do you want me to open a pull request against ubuntu-image? Or review changes on my fork?

Nice, thank you! I can't have a look before tomorrow, but feel free to open a PR against the main repo directly. Of you'd rather have me look before doing that, that's fine, too - but no need to. I'll review one way or the other 🙂

@nielsenjared, just to make sure it doesn't fall through the cracks: thank you for the PR! Ui left a review with suggestions.

authors: GrouchyM nielsenjared rkratky

repo: canonical/open-documentation-academy


text:
test-branch/execute-job/wrong-comment-on-pr/df0e635e-292c-401b-8d23-5ac8c01b8e32

PR for testing cadfabdf703be5d88f1a6f1a8eaa4effb813fe3c

comment 1

repo: canonical/repo-policy-compliance-tests


text:
Charm shows as active/idle even when raft configuration is incorrect

Describe the bug
As a follow-up to #88 -- when this happens there isn't an immediately obvious way to detect that something is wrong.
The charm will remain in active/idle even when raft has reported that it is unhealthy. There should probably be some sort of warning in this case.
Furthermore, it's not obvious what triggers raft to become unhealthy. Even without the bugfix in #88, when I tested manually after the new pod rejoined raft, everything appeared to be healthy. Raft only reached an unhealthy state once I removed the leader unit.
To Reproduce
Deploy an old version of the charm, before the bugfix in 88.
juju add-model raft-cluster-bug
juju deploy vault-k8s --channel edge -n 5 --trust --revision 53

Wait for everything to be up and running. Then, configure vault to connect to your vault cluster directly.
Install vault and yq if not already installed
sudo apt install vault yq

# Set vault token
vault_initialization_secret=$(juju secrets --format=yaml | yq '. | with_entries(select(.*.label == "vault-initialization")) | keys | .[]')
export VAULT_TOKEN=$(juju show-secret ${vault_initialization_secret} --reveal | yq '.[].content.roottoken')

# Extract the vault CA cert and set the path
vault_ca_certificate_secret=$(juju secrets --format=yaml | yq '. | with_entries(select(.*.label == "vault-ca-certificate")) | keys | .[]')
juju show-secret ${vault_ca_certificate_secret} --reveal | yq '.[].content.certificate' > vault_ca.pem
export VAULT_CAPATH=$PWD/vault_ca.pem

# Set the address of vault
export VAULT_ADDR="https://$(juju status vault-k8s --format=yaml | yq '.applications.vault-k8s.address'):8200"

Check the raft health
vault operator raft autopilot state

$ vault operator raft autopilot state
Healthy:                      true
Failure Tolerance:            2
Leader:                       raft-cluster-bug-vault-k8s/0
Voters:
   raft-cluster-bug-vault-k8s/0
   raft-cluster-bug-vault-k8s/1
   raft-cluster-bug-vault-k8s/2
   raft-cluster-bug-vault-k8s/4
   raft-cluster-bug-vault-k8s/3
Servers:
   raft-cluster-bug-vault-k8s/0
      Name:            raft-cluster-bug-vault-k8s/0
      Address:         10.1.166.210:8201
      Status:          leader
      Node Status:     alive
      Healthy:         true
      Last Contact:    0s
      Last Term:       3
      Last Index:      72
   raft-cluster-bug-vault-k8s/1
      Name:            raft-cluster-bug-vault-k8s/1
      Address:         10.1.166.193:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    494.230733ms
      Last Term:       3
      Last Index:      72
   raft-cluster-bug-vault-k8s/2
      Name:            raft-cluster-bug-vault-k8s/2
      Address:         10.1.166.224:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    99.573454ms
      Last Term:       3
      Last Index:      72
   raft-cluster-bug-vault-k8s/3
      Name:            raft-cluster-bug-vault-k8s/3
      Address:         10.1.166.255:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    4.714894438s
      Last Term:       3
      Last Index:      72
   raft-cluster-bug-vault-k8s/4
      Name:            raft-cluster-bug-vault-k8s/4
      Address:         10.1.166.220:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    2.488287328s
      Last Term:       3
      Last Index:      72

Delete a pod
kubectl delete pod vault-k8s-1 -n raft-cluster-bug

Wait for everything to settle back to active/idle. Observe everything still reports as healthy, even though the IP address is incorrect.
$ vault operator raft autopilot state
Healthy:                      true
Failure Tolerance:            2
Leader:                       raft-cluster-bug-vault-k8s/0
Voters:
   raft-cluster-bug-vault-k8s/0
   raft-cluster-bug-vault-k8s/1
   raft-cluster-bug-vault-k8s/2
   raft-cluster-bug-vault-k8s/4
   raft-cluster-bug-vault-k8s/3
Servers:
   raft-cluster-bug-vault-k8s/0
      Name:            raft-cluster-bug-vault-k8s/0
      Address:         10.1.166.210:8201
      Status:          leader
      Node Status:     alive
      Healthy:         true
      Last Contact:    0s
      Last Term:       3
      Last Index:      74
   raft-cluster-bug-vault-k8s/1
      Name:            raft-cluster-bug-vault-k8s/1
      Address:         10.1.166.193:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    1.811061128s
      Last Term:       3
      Last Index:      73
   raft-cluster-bug-vault-k8s/2
      Name:            raft-cluster-bug-vault-k8s/2
      Address:         10.1.166.224:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    4.100232431s
      Last Term:       3
      Last Index:      74
   raft-cluster-bug-vault-k8s/3
      Name:            raft-cluster-bug-vault-k8s/3
      Address:         10.1.166.255:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    3.714476475s
      Last Term:       3
      Last Index:      74
   raft-cluster-bug-vault-k8s/4
      Name:            raft-cluster-bug-vault-k8s/4
      Address:         10.1.166.220:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    1.488745791s
      Last Term:       3
      Last Index:      74

Remove the leader
kubectl delete pod vault-k8s-0 -n raft-cluster-bug

Wait for things to settle. Now, things are reporting as unhealthy.
$ vault operator raft autopilot state                                                                            2 ↵
Healthy:                      false
Failure Tolerance:            0
Leader:                       raft-cluster-bug-vault-k8s/2
Voters:
   raft-cluster-bug-vault-k8s/2
   raft-cluster-bug-vault-k8s/3
   raft-cluster-bug-vault-k8s/4
   raft-cluster-bug-vault-k8s/0
   raft-cluster-bug-vault-k8s/1
Servers:
   raft-cluster-bug-vault-k8s/0
      Name:            raft-cluster-bug-vault-k8s/0
      Address:         10.1.166.210:8201
      Status:          voter
      Node Status:     alive
      Healthy:         false
      Last Contact:    1m3.983504343s
      Last Term:       0
      Last Index:      0
   raft-cluster-bug-vault-k8s/1
      Name:            raft-cluster-bug-vault-k8s/1
      Address:         10.1.166.193:8201
      Status:          voter
      Node Status:     alive
      Healthy:         false
      Last Contact:    1m3.983503994s
      Last Term:       0
      Last Index:      0
   raft-cluster-bug-vault-k8s/2
      Name:            raft-cluster-bug-vault-k8s/2
      Address:         10.1.166.224:8201
      Status:          leader
      Node Status:     alive
      Healthy:         true
      Last Contact:    0s
      Last Term:       4
      Last Index:      101
   raft-cluster-bug-vault-k8s/3
      Name:            raft-cluster-bug-vault-k8s/3
      Address:         10.1.166.255:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    1.917555641s
      Last Term:       4
      Last Index:      101
   raft-cluster-bug-vault-k8s/4
      Name:            raft-cluster-bug-vault-k8s/4
      Address:         10.1.166.220:8201
      Status:          voter
      Node Status:     alive
      Healthy:         true
      Last Contact:    2.188396134s
      Last Term:       4
      Last Index:      101

Expected behavior

The charms should display some error, if in fact the raft cluster is broken.

But, raft itself seems to report everything as healthy at first. It's not obvious how we can detect the health of the raft cluster.

Environment

Charm / library version (if relevant): 53 for reproducing, but the general issue applies beyond that.
Juju version (output from juju --version): 3.1.6
Cloud Environment: microk8s
Kubernetes version (output from kubectl version --short):

Client Version: v1.27.7
Kustomize Version: v5.0.1
Server Version: v1.27.7

Additional context

As already mentioned in the ticket, it isn't possible to reproduce the issue with the same steps after the fix in #89 .
The charm after the fix uses hostnames instead of IP addresses so there will be no need to update IP addresses or Raft nodes. And based on a few tickets reported we see that there is a known issue with Raft nodes updating the IP addresses if the pod crashes and comes up again with a new IP.
Example issues:

https://github.com/hashicorp/vault/issues/10702#issuecomment-769076069
https://discuss.hashicorp.com/t/understanding-node-ip-changes-for-a-raft-cluster/56854
https://discuss.hashicorp.com/t/change-vault-cluster-node-ip/14923/1
https://github.com/hashicorp/vault/issues/17014

Based on fix #89 Raft cluster should not report unhealthy because of an IP change, however we still need to get a feedback if the cluster reports unhealthy for any other reason.
In general the cluster will report unhealthy if at least one of its nodes is reporting unhealthy and a node will report unhealthy it it can't heartbeat the leader unit or it can't keep up with the data replication from leader node (reference here)
PR #117 adds logging to report any node going unhealthy.

PR #117 has been merged.

authors: DanielArndt saltiyazan


text:
Provide optional parameters by Spring config

Some modules like the distributed event busprovides some additional properties that can be configured in the dolphin.properties file. Since the basic properties of the Dolphin Platform can be directly defined in the application.properties if Spring Boot is used this is currently not possible for the optional properties.

Already done

repo: canoo/dolphin-platform


text:
Dynamic 'from' address for mail agent

Hi,
I am working with mailAgent , I need to set different from address and subject based on my recipient.And it worked with subject by using liquid option ,but it had not worked for 'from' attribute ,Always I am getting from address as the attribute set in .env file.

Hi @bhagyalakshmikk,
I think that is a limitation of your email provider. Huginn will set the value you configure in the from field but some providers do not allow to "fake" the sender and always set it to your email address. A service like http://www.mailgun.com/ will allow you to configure the from address.

I'm going to close this.  Please reopen if you have more questions!

authors: bhagyalakshmikk cantino dsander

repo: cantino/huginn


text:
Move ActionMailer configuration to initializer

Prevents encoding issues in the generated YAML file when using especial characters like !
#1584

Moving the database config to an initializes does not seem to be possible, we could use the DATABASE_URL environment variable, but I don't know if that would work with unix sockets.

Nice @dsander. This looks right to me.

I'll point out that some (albeit outdated) deploy systems like Capistrano depend on creating database.yml as a symlink or a file that's generated at deploy time. Our old deploy system used to do the same for smtp.yml. We now use environment variables but some people with older Huginn deploys might have trouble with this.
Might want to make a more prominent changelog note or something

Good point.  I still use Capistrano and it may try to manage database.yml.  Maybe best to leave it as-is for now?

Oh yes, that is very true. I think our current capistrano deployment recipe would not be affected, but I agree that it is a very common thing to do.
It looks like that we do not mention modifying the directly smtp.yml anywhere, so I don't think it needs a prominent place. I might find some time over the weekend to update the changelog with the recent changes and add a note there.

Sounds good.  This looks good to me.

Thanks! I updated the changelog in #1602

authors: albertsun cantino dsander


text:
[Android] Error "Device is not connected" on Write o Read any characteristic

Detailed Description of the Issue
Issue Summary:
After successfully connecting to a BLE device using the @capacitor-community/bluetooth-le plugin in an Ionic 7 Angular application, attempting to read or write characteristics returns an error stating "device is not connected." This issue occurs even though the initial connection appears to be successful.
Steps to Reproduce:

Initialize the BLE client with BleClient.initialize().
Request the BLE device using BleClient.requestDevice() with appropriate service UUIDs.
Disconnect to the device using BleClient.disconnect(device.deviceId).
Connect to the device using BleClient.connect(device.deviceId).
Attempt to read or write a characteristic using BleClient.read(device.deviceId, serviceUUID, characteristicUUID) or BleClient.write(device.deviceId, serviceUUID, characteristicUUID, value).

Observed Behavior:
The device connects successfully, as confirmed by the connection logs.
Upon attempting to read or write a characteristic, an error is thrown indicating that the device is not connected.
Expected Behavior:
After a successful connection, reading from or writing to a characteristic should succeed without errors.
Additional Context:
The issue seems to be intermittent, as the connection is initially established but subsequent read/write operations fail.
Adding delays and retry logic does not resolve the issue.
This issue occurs on multiple Android devices and versions.
Environment:
Ionic Version: 7
Capacitor Version: 6.0.0
BLE Plugin Version:    "@capacitor-community/bluetooth-le": "^6.0.0"
Pls Help

A disconnect can also be triggered by the peripheral. When connecting you can pass an optional onDisconnect callback, see https://github.com/capacitor-community/bluetooth-le?tab=readme-ov-file#connect. Is this callback called between the successful connection and your read or write attempt?

I noticed that the disconnection event only triggers after a write or read attempt. However, by changing the autoconnect parameter to true, the connection works consistently.

repo: capacitor-community/bluetooth-le


text:
Add pattern or callback for deciding which files should trigger a reload

I'm using angular as components, and each component is contained in one directory with component.js (angular module), component-controller.js and component.html. I'm running a watch on all my component.html files, and creating a compiled component.html.js (using gulp-angular-templatecache).
Naturally the hot reloader will handle reloading these scripts and re-bootstrapping the angular page, so I'd like to ignore changes to html files, which, at the moment, cause an unnecessary reload.
A simple matching callback passed into the HotReloader ctor would do the trick. Takes the filename and checks the result for truthiness to decide whether to do the reload.
e.g.
_reloader = new HotReloader('http://localhost:5776', {     match: path => path.endsWith('.js') };
Let me know if I'm on the wrong track here. But as far as I could tell there was nothing (in the listener itself, rather than the emitter) that handled this.
Edit: this is my workaround in the meantime: http://pastebin.com/Jr0e1bqz

`
class MatchableHotReloader extends HotReloader {
constructor(backendUrl, transform, match) {
super(backendUrl, transform);
this.match = match;
}
onFileChanged(ev) {
    if (this.match(ev.path)) {
        super.onFileChanged(ev);
    }
}

}
`

Coundn't you also handle this by adding ignores to your watcher (for example chokidator-socket-emitter)?

@peteruithoven Yeah, you could but is that the best option? The emitter does it's job by notifying of file change events, is it up to the listener to check whether these events are relevant? I guess it's semantics, but is there a use-case where you might attach different listeners to the same emitter to handle different events?

I disagree I think, mainly because watches have costs, you can't watch unlimited files. That's why your probably also ignoring the git ignores and node_modules. So ignoring those html's "right from the gate" also saves you resources.

@nth-commit If you're still wanting this, a PR would be much appreciated.
Best implementation that I can think of would be having the user pass systemjs-hot-reloader a function that accepts the string module name and returns true or false for inclusion. This is more general then a regex or something like that.
For now I'm closing the issue, feel free to reopen if this is still important to you.

authors: HydrateEfficiently alexisvincent nth-commit peteruithoven

repo: capaj/systemjs-hot-reloader


text:
test: actually assert that release was created

Summary
Follow up to https://github.com/capistrano/capistrano/pull/2155#issuecomment-2172283634 and https://github.com/capistrano/capistrano/pull/2155#issuecomment-2174466232
I've gone with expecting the year, month, day as for that to fail there'd need to be a 24 hour delay between steps which'd be a whole problem of its own - it might be possible that if you run the suite at midnight in a particular timezone it could also fail, but if so that should only be a ~30 second window of possibility...
Short checklist

[x] Did you run bundle exec rubocop -a to fix linter issues?
[x] If relevant, did you create a test?
[x] Did you confirm that the RSpec tests pass?

Other Information
This is branched off #2159

@G-Rath looks good, thanks! 🙇  It would be great to avoid the flakiness around midnight, but I can't think of a way to do that without adding a significant amount of complexity. As it stands, the flake scenario should very rarely happen.

@G-Rath wow, you're quick! Thanks for the rebase

authors: G-Rath mattbrictson

repo: capistrano/capistrano


text:
Jenkins-cucumber error: No Enabled Jobs found with artifacts pattern: cucumber.json

Hi,
i'm running cucumber job and then i've got an error;
can you please assist?
2018-03-18 18:45:00,001 INFO  c.c.d.collector.CollectorTask - Running Collector: JenkinsCucumberTest
2018-03-18 18:45:00,208 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2018-03-18 18:45:00,208 INFO  c.c.d.collector.CollectorTask - http://illin4227:18080
2018-03-18 18:45:00,208 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2018-03-18 18:45:00,704 INFO  c.c.d.collector.CollectorTask - Fetched jobs                     0s
2018-03-18 18:45:20,675 INFO  c.c.d.collector.CollectorTask - New jobs                0       19s
2018-03-18 18:45:20,690 INFO  c.c.d.collector.CollectorTask - WARNING: No Enabled Jobs found with artifacts pattern: cucumber.json
2018-03-18 18:45:20,690 INFO  c.c.d.collector.CollectorTask - Finished                        20s
application properties:
#Database Name
dbname=dashboarddb
#Database HostName - default is localhost
dbhost=localhost

#Database Port - default is 27017
dbport=27017

#Database Username - default is blank
dbusername=dashboarduser

#Database Password - default is blank
dbpassword=dbpassword

jenkins.pageSize=1000

    #Collector schedule (required)
    jenkins-cucumber.cron=0 * * * * *

    #Jenkins server (required) - Can provide multiple
    jenkins-cucumber.servers[0]=http://illin4227:18080

    #Pattern to find cucumber reports
    jenkins-cucumber.cucumberJsonRegex=cucumber.json

    #Another option: If using same username/password Jenkins auth - set username/apiKey to use HTTP Basic Auth (blank=no auth)
    jenkins-cucumber.username=***
    jenkins-cucumber.apiKey=*****

@magma7  make sure Jenkins server has cucumber json in jenkisn workspace

@nireeshT ; Can you please help me solve this problem ?
I have the cucmber json in my jenkins workspace but still having "No Enabled Jobs found with artifacts pattern: cucumber.json"

closing due to inactivity, please reopen is this is still happening.

repo: capitalone/Hygieia


text:
Support for Sonar 6+ and UI changes

Fix for https://github.com/capitalone/Hygieia/issues/1311.
Changes:

Took changes suggested from the discussion thread.
Added tests
UI changes - since sonar 5, rules compliance was deprecated. Instead a "quality gate" was introduced. Made UI change to display quality gate when available

Screen shot:

This is working , thanks

We are using sonarqube 7.1 version.  We installed hygieia and tries to get the metrics on hygieia dashboard. But code metrics is just fetching the lines of code (code coverage info) . There is no other information available. Please suggest me what could be the reason for this issue? Is hygieia support for sonarqube version 7.1?


text:
key error on deleting ebs snapshots

This error can occur when deleting ebs snapshots
ERROR - custodian.output - Error while executing policy Traceback (most recent call last):
File "/usr/local/custodian/lib/python2.7/site-packages/c7n/policy.py", line 207, in poll results = a.process(resources)
File "/usr/local/custodian/lib/python2.7/site-packages/c7n/resources/ebs.py", line 70, in process snaps.add(dev['Ebs']['SnapshotId'])
KeyError: 'SnapshotId'`

I believe this is happening when there are non-EBS backed AMIs and a check needs to be made for the presence of the SnapshotId key

I can take a look at this.

Here's an example of an Image that causes the problem:
{
    "Architecture": "x86_64",
    "BlockDeviceMappings": [
        {
            "DeviceName": "/dev/sda1",
            "Ebs": {
                "DeleteOnTermination": true,
                "Encrypted": false,
                "SnapshotId": "snap-12345678",
                "VolumeSize": 20,
                "VolumeType": "gp2"
            }
        },
        {
            "DeviceName": "/dev/sdb",
            "Ebs": {
                "DeleteOnTermination": true,
                "Encrypted": true,
                "VolumeSize": 20,
                "VolumeType": "gp2"
            }
        },
        {
            "DeviceName": "/dev/sdc",
            "Ebs": {
                "DeleteOnTermination": true,
                "Encrypted": true,
                "VolumeSize": 200,
                "VolumeType": "gp2"
            }
        }
    ],
    "CreationDate": "2016-05-04T15:38:50.000Z",
    "Description": "Blah blah blah",
    "Hypervisor": "xen",
    "ImageId": "ami-12345678",
    "ImageType": "machine",
    "Public": false,
    "RootDeviceName": "/dev/sda1",
    "RootDeviceType": "ebs",
    "SriovNetSupport": "simple",
    "State": "available",
    "VirtualizationType": "hvm"
}

doh, yeah the ami was setup to create a new block dev, we handled this in the other ami block devs scans, probably something to consolidate handling on, thanks again.

authors: ewbankkit jeffastorey kapilt

repo: capitalone/cloud-custodian


text:
Related resources cannot find security-group for every resource except ec2.

I have begun to use the related resource functionality that was just merged on 10/17, and I have noticed some issues with the usage. I am not sure if it is because of my lack of understanding of the syntax, or if the functionality is broken. I didn't see any testing uploaded with the merge so it is possible these issues were missed.
For EC2, I want to get rid of instances that are using certain security groups. I do not know if this syntax is the most efficient, but I have gotten it to work using the following template (security group ids have been taken out):
  - name: ec2-default-security-group
    description: |
      If EC2 is using default security group, terminate the instance.
    resource: ec2
    filters:
      - or:
        - type: security-group
          match_resource: true
          key: "GroupId"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "GroupId"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "GroupId"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "GroupId"
          value: "sg-xxxxxxxx"
    actions:
      - terminate

Now, I am trying to replicate this functionality among every applicable resource. Let's take redshift for example:
  - name: redshift-cluster-default-security-group
    description: |
      If Redshift Cluster is using default security group, terminate the instance.
    resource: redshift
    filters:
      - or:
        - type: security-group
          match_resource: true
          key: "VpcSecurityGroupId"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "VpcSecurityGroupId"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "VpcSecurityGroupId"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "VpcSecurityGroupId"
          value: "sg-xxxxxxxx"
    actions:
      - type: delete
        skip-snapshot: true

That policy breaks with the following errors:
2016-10-20 19:06:33,541: custodian.policy:INFO Running policy redshift-cluster-default-security-group resource: redshift region:us-east-1 c7n:0.8.19.6
2016-10-20 19:06:33,932: custodian.resources.securitygroup:WARNING event ids not resolved: ['sg-7ab5dd02'] error:An error occurred (InvalidGroup.NotFound) when calling the DescribeSecurityGroups operation: The security group 'sg-7ab5dd02' does not exist in default VPC 'vpc-701e2515'
2016-10-20 19:06:33,933: custodian.filters:WARNING Resource cluster:dbr-redshift-redshiftcluster-o5tiqoqftuv3 references non existant SecurityGroup: sg-7ab5dd02
2016-10-20 19:06:33,988: custodian.resources.securitygroup:WARNING event ids not resolved: ['sg-7ab5dd02'] error:An error occurred (InvalidGroup.NotFound) when calling the DescribeSecurityGroups operation: The security group 'sg-7ab5dd02' does not exist in default VPC 'vpc-701e2515'
2016-10-20 19:06:33,988: custodian.filters:WARNING Resource cluster:dbr-redshift-redshiftcluster-o5tiqoqftuv3 references non existant SecurityGroup: sg-7ab5dd02
2016-10-20 19:06:34,038: custodian.resources.securitygroup:WARNING event ids not resolved: ['sg-7ab5dd02'] error:An error occurred (InvalidGroup.NotFound) when calling the DescribeSecurityGroups operation: The security group 'sg-7ab5dd02' does not exist in default VPC 'vpc-701e2515'
2016-10-20 19:06:34,038: custodian.filters:WARNING Resource cluster:dbr-redshift-redshiftcluster-o5tiqoqftuv3 references non existant SecurityGroup: sg-7ab5dd02
2016-10-20 19:06:34,089: custodian.resources.securitygroup:WARNING event ids not resolved: ['sg-7ab5dd02'] error:An error occurred (InvalidGroup.NotFound) when calling the DescribeSecurityGroups operation: The security group 'sg-7ab5dd02' does not exist in default VPC 'vpc-701e2515'
2016-10-20 19:06:34,090: custodian.filters:WARNING Resource cluster:dbr-redshift-redshiftcluster-o5tiqoqftuv3 references non existant SecurityGroup: sg-7ab5dd02
2016-10-20 19:06:34,090: custodian.resources.redshift:INFO Filtered from 1 to 0 redshift
2016-10-20 19:06:34,090: custodian.policy:INFO policy: redshift-cluster-default-security-group resource:redshift has count:0 time:0.55

I'm not sure if my syntax is incorrect or if this is broken, but these are my results.
There is also the concern of what to do when the security groups come in as an array, like so:
  - name: elb-default-security-group
    description: |
      If elastic load balancer is using default security group, terminate the instance.
    resource: elb
    filters:
      - or:
        - type: security-group
          match_resource: true
          key: "SecurityGroups[]"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "SecurityGroups[]"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "SecurityGroups[]"
          value: "sg-xxxxxxxx"
        - type: security-group
          match_resource: true
          key: "SecurityGroups[]"
          value: "sg-xxxxxxxx"
    actions:
      - delete

How would the filters look in this case?

sounds like a gap and we need some more unit tests on this for other resource types.

It ends up doing a query for GroupNames=['sg-xxxxxxxx']. Still trying to track down why.
If you change the query to GroupIds=['sg-xxxxxxxx'] or GroupNames=['default'], it works.

I think there may be an upstream bug in skew. In their SecurityGroup the ID and filter don’t seem to match. (One refers to the group’s ID and one to its name.) This doesn’t look consistent with the other resources described in that file.
See https://github.com/scopely-devops/skew/blob/develop/skew/resources/aws/ec2.py#L44
I’ll open an issue there to confirm.
FYI, I was able to get the resources to show up by changing the code in skew, and by continuing to use GroupId as the key instead of VpcSecurityGroupId.

definitely good to address upstream, but at this point i'd like to just get the fix in, its a one liner, reassigning, and addressed. we primarily use the skew models as defaults with extensions and mods as nesc, and use our own query engine as well.
wrt to the upstream, this is a delta i think from trying to support the classic mode networking, which has been deprecated for several years.

addressed in #564

Hi @kapilt  @skurfer can you please share link for security group policies.
I Want to allow port 80 nad 443 to have cidr value 0.0.0.0/0. No other port should have 0.0.0.0/0.
Please Provide the policy reference for that.

authors: aiell0 kapilt nitinitare skurfer


text:
opensource s3 bucket eater

scale out object scanner, code name salactus or unicron tbd.

done in #574


text:
Authentication failed not handling nested challenges

Utilizing the develop branch commit a53cb082b6a07f32ddc5c9cacff6f5dfe926f170
Using this code which seems to be entirely correct doesn't seem to authenticate correctly
    config = ce.get_config('Cognito', args.configfile)
    u = Cognito(config['pool_id'],config['client_id'], username=args.username)
    response = u.authenticate(args.password)

2017-04-11 12:24:16 DEBUG parsers.parse Response body:
{"ChallengeName":"NEW_PASSWORD_REQUIRED","ChallengeParameters":{"requiredAttributes":"[]","userAttributes":"{\"email_verified\":\"true\",\"email\":\"<ommitted email>\"}"},"Session":"<sessiong string ommitted>"}
2017-04-11 12:24:16 DEBUG hooks._emit Event needs-retry.cognito-idp.RespondToAuthChallenge: calling handler <botocore.retryhandler.RetryHandler object at 0x7fc01d531d90>
2017-04-11 12:24:16 DEBUG retryhandler.__call__ No retry needed.
Traceback (most recent call last):
  File "bin/auth-cognito", line 37, in <module>
    main()
  File "bin/auth-cognito", line 33, in main
    response = u.authenticate(args.password)
  File "~/.local/lib/python2.7/site-packages/warrant/__init__.py", line 213, in authenticate
    self.id_token = tokens['AuthenticationResult']['IdToken']
KeyError: 'AuthenticationResult'

It doesn't look like there is support for Challenges of NEW_PASSWORD_REQUIRED and it failed to raise like it should https://github.com/capless/warrant/blob/develop/warrant/aws_srp.py#L187

Looks like it assumes there will only be one response challenge.
We'll need to add the ability to complete the challenge with an additional input (the new password).

Yeah I also just realized my initial diagnosis in where I thought the problem was was wrong. And you've hit the nail on the head for the conclusion I just came to.

The handling in #15 isn't perfect for NEW_PASSWORD_REQUIRED I'd like there to be a module global which is a callable and returns back the password. Allows users to specify a system to get the password rather than using a TTY is present.

I like the way #25 handles the authentication, it raises by default and then lets the user come up with their own way of getting the password which keeps in line with a web usage model.

Based on your suggested workflow @bjinwright I'm working on this aspect. Not sure if any one else is.
However admin_get_user looks like it requires developer credentials, credentials which we won't have. How would we get the user status without being able to login. I'm assuming a web framework which and the user provides credentials which calls warrant which calls cognito. Those are the only credentials in the framework. Can you expound on how your proposed workflow executes that?

Thanks for the feedback that makes sense

So with that in mind we may need to implement the remaining work flows based on challenge types rather than user status. What do you think?

For historical purpose I'm still going to put my work for user statuses:
UNCONFIRMED - User has been created but not confirmed.
ConfirmSignUp
CONFIRMED - User has been confirmed.
Normal workflow
ARCHIVED - User is no longer active.
Not sure there is a workflow here.
COMPROMISED - User is disabled due to a potential security threat.
Not sure there is a workflow here.
UNKNOWN - User status is not known.
Not sure there is a workflow here.
RESET_REQUIRED - User has issued a reset password request but not reset it.
ConfirmForgotPassword, possibly RespondToAuthChallenge
FORCE_CHANGE_PASSWORD - User has not authenticated for the first time and must change password
RespondToAuthChallenge

The current state:

Warrant raises ForceChangePasswordException for users which are required to change their passwords after successful first login (NEW_PASSWORD_REQUIRED challenge).

new_password_challenge method is not documented

Warrant raises NotImplementedError when a challenge is not supported.

Warrant doesn't support  SMS_MFA, CUSTOM_CHALLENGE, DEVICE_SRP_AUTH DEVICE_PASSWORD_VERIFIER.

The first post says about the problem with the NEW_PASSWORD_REQUIRED challenge and this issue is fixed. The title has more broad meaning, it implies that warrant should support all challenges.
@bjinwright The decision of closing the issue depends on what to take into account: the title or the first post.

authors: armicron bjinwright blade2005 ebpetway

repo: capless/warrant


text:
Add text to the element

Hello!
How can I add text as a child of element with using docSpec?

Try this:
const modifyXml = (xml, id, modifier) => {
    if (id.length > 1) {
        const idClone = id.slice(0);
        const first = idClone.splice(0, 1);
        xml[first[0]] = modifyXml(xml[first[0]], idClone, modifier);
        return xml;
    }
    xml[id[0]] = modifier(xml[id[0]]);
    return xml;
};

const newTextChild = (parameter) => async (xml, id) => {
    return modifyXml(xml, id, (parent) => {
        if (!parent.$$) {
            parent.$$ = [];
        }
        parent.$$.push({
            '#name': '__text__',
            _: parameter,
        });
        return parent;
    });
};

const docSpec = {
    elements: {
        item: {
            menu: [{
                action: newTextChild('abc'),
                caption: 'Append text abc',
            }],
        },
    },
};

I will add newTextChild() soon to make it easier for you.

Thanks a lot. It works!

authors: captain-igloo hadwrf

repo: captain-igloo/react-xml-editor


text:
🛑 PhotoReal API is down

In 0ea0ff8, PhotoReal API (https://api.photoreal.cf/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PhotoReal API is back up in cdb8515 after 5 minutes.

repo: captainqdev/funkyducks-status


text:
[ImageCard] add upload capabilities

Closes #1754
Part of #1817
Summary
Add ability to upload images from local files or from url. Part of the Dashboard editor effort.
Change List (commits, features, bugs, etc)

created a new ImageUploader component
create a new check in ImageCard for existence of isNew prop and serve up uploader
created _image-uploader.scss
-added new utility function to handle fetch and conversion of images from url in cardUtilityFunctions.js

Acceptance Test (how to verify the PR)

Look at new story created for image uploader

:tada: This PR is included in version 2.141.0-next.25 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
fix(build): keep lint-staged and husky definition on the top level to avoid pre-commit problems

Closes #2037
Summary
The current setup kept erroring/failing on pre-commit hooks, complaining that it couldn't find a file at an invalid path. According to lint-staged docs, the setup for monorepos should only be on the root level, and we've got specifications in package.json at the root as well as in packages/react
Change List (commits, features, bugs, etc)
Remove duplicate setup for inner package file.
Acceptance Test (how to verify the PR)

Modify a file in the source tree, adding a line that will fail lint, e.g. let foo = 'bar'
git add that file to stage it
git commit -m "fix(build): test that this works", letting the pre-commit hooks
Commit should fail from bad lint.
Comment out the line we added in step 1 : // let foo = 'bar'
git commit -m "fix(build): test that this works", letting the pre-commit hooks
Commit should succeed

I did a fresh clone of my repo and this problem disappeared. If that sounds weird, I agree, and I would love to dedicate a month to figuring out why that happened. Alas, no.


text:
[Universal banner]: Image stretching

Description
At the desktop breakpoints, the image in the Universal banner is being too condensed as the screen is resized. We should figure out a solution to keep the image clear as the window is resized.

@RichKummer and @oliviaflory to check the CTA alignment to the grid: https://ibm.ent.box.com/folder/142303458357?s=fas5qv5zrscudr63y85g28v0k657p83u
Component(s) impacted
Universal banner
Browser
Chrome
Carbon for IBM.com version
v1.16.0-rc.1
Severity
Severity 3 = The problem is visible or noticeable to users but does not impede the usability or functionality. Affects minor functionality, has a workaround.
Application/website
C4IBM.com
Package
@carbon/ibmdotcom-web-components
CodeSandbox example
https://codesandbox.io/s/github/carbon-design-system/carbon-for-ibm-dotcom/tree/main/packages/web-components/examples/codesandbox/components/universal-banner
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

Design to do additional testing and update functional specs. Consider keeping fixed width until next breakpoint where image will become hidden. See example.

Feedback:

simplify type

Semi bold
Semi bold + regular ?
Try 14px

left align type
Try primary and tertiary buttons. Don't think secondary is the right choice
Should we allow for colors other than the default themes
option for video or image ?
Review in context (masthead) @ each breakpoint

Asset needs more space around it so it doesn't get cropped
Or adaptively change space around it so it doesn't get cropped.
Need detailed guidance on how to position and crop image. Has enough room to scale without being cropped.

authors: RichKummer kennylam oliviaflory


text:
[Sandbox]: New CTA Section/Next Step component from the Brand Expression project

Engineering info:

Innovation Team engineer: @proeung
Innovation Team JIRA Ticket: https://jsw.ibm.com/browse/HC-2434
DPO consulting engineer: N/A

User story

As a [user role below]:

I need to:

so that I can:

Additional information

Add new brand CTA Section/Next Step component to storybook
Light documentation
How to showcase this on a page (web components test template)

Acceptance criteria

[ ] Lead space added to storybook
[ ] published on CDN

PR: https://github.ibm.com/webstandards/carbon-for-ibm-dotcom-innovation-sandbox/pull/25


text:
feat(tutorial): complete step 5

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

URL: http://carbon-tutorial-dhebert-dev.mybluemix.net/#/

URL: http://carbon-tutorial-dhebert-dev.mybluemix.net/#/

repo: carbon-design-system/carbon-tutorial


text:
complete tutorial step 2-Dublin

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

@ciaramoynagh It looks like you need this PR to be coming from react-step-2 of your fork, not master

authors: SimonFinney ciaramoynagh


text:
React step 3 - Rochester

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Looks good.  I've marked your step 3 as complete.

authors: Jody-Mueller dstanich


text:
Comparative component usage guidance audits

conduct comparative audit of design system component content organization
create a template for component guidance
map current content against template to find shortcomings

Content can be found here: https://ibm.ent.box.com/folder/81789297308

repo: carbon-design-system/carbon-website


text:
fix: update Carbon versions to latest

This PR was automatically generated to update Carbon versions on a regular basis. This is not intended to create any breaking changes, and will be reflected as a minor version bump for affected packages. NB we'll run all tests and do visual verifications, but there is always the opportunity for unexpected regressions. If you're using one of the packages in a stable or production context you may want to check this before taking the next minor version, and do let us know ASAP if you see anything problematic.
The goal is to update to the latest Carbon versions each Friday, to ensure we remain up-to-date with the latest changes (often published on Thursdays) and to ensure interoperability with other packages that also depend on Carbon. We will normally update all other dependencies at the same time to their latest versions, except for specific cases where we have found the updates to be problematic or require further work before they can be used. By using the latest stable version of each dependency we ensure we get fixes and improvements in a timely fashion and reduce the impact of updating the versions that can arise if versions are allowed to become stale for an extended period.
What did you change?
This action ran yarn upgrade:carbon to upgrade all carbon-related packages to the latest versions.
This PR includes the various package.json that pull our dependencies forward to the latest versions, and updates the offline mirror.
How did you test and verify your work?
This PR should not be merged until the following checks have been made:

[ ] A reminder message has been posted onto the ccs-pal-dev Slack channel that a version update PR is going through.
[ ] yarn ci-check runs cleanly and all tests pass (done automatically as part of the PR checks).
[ ] the Netlify deploy-preview has been used to ensure that storybook runs and the main published components render correctly.

Generated as part of testing


text:
Masthead:  Work with Carbon to define strategic solution for the mobile menu

User Story

As a [user role below]:
consumer of the Carbon design system

I need to:
have a Carbon mobile Masthead L0 that can be included in the ibm.com Masthead

so that I can:
provide this component to the DDS adopters in the most efficient way

Additional information

A tactical solution has been defined and included in Issue #782
A strategic solution is needed.

Acceptance criteria

[ ] Agreed design is defined, agreed and documented with Carbon

After speaking with @larahanlon2 and @wonilsuhibm, we decided to keep the current positioning of the Carbon hamburger menu, i.e. it will stay in the same place whether the side nav is open or closed:

The ibmdotcom design will not be used for the time being (hamburger close button moves to right when visible):

Agreed!

authors: RobertaJHahn kennylam larahanlon2

repo: carbon-design-system/ibm-dotcom-library


text:
Remove Project Lombok dependency

This issue will track the progress in the individual repositories.

Makes sense only after migration to JDK 17 (see #17).

authors: grevend-bosch strieflin

repo: carbynestack/carbynestack


text:
🛑 mainnet - API is down

In d097f75, mainnet - API (https://api.beta.explorer.cardano.org/api/v1/epochs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mainnet - API is back up in 294d683 after 6 minutes.

repo: cardano-foundation/cf-explorer-status


text:
PRD template improvements

Some updates to PRD document templates.
If we decide to indeed display the code on this document, we can use monaco editor for preview with syntax highlighting. I haven't implemented that here because I realized that all the monaco-related code is currently in the host app.

Nice

authors: IanCal burieberry

repo: cardstack/boxel


text:
Move a few things out of runtime-common that were only consumed by host

I think @habdelra expected I would find more than this that could be extracted, but I didn't. The main consumption pattern is via the Realm class, which is used in both host and realm-server packages.

@habdelra shimExternals is used by both host and realm-server currently. I don't see how we can move it unless I am missing something.

Hmmm, it probably shouldn’t be used by host, since we have actual shims for that (as opposed to the no-op ones)

I'll create a separate task for shimExternals

authors: habdelra lukemelia


text:
Running Human or other actions

Is there any open source work out there to control the skeleton of humans so they are doing other tasks, like running etc.

yes, look into the documentation. However, there are no many examples code snippets.

authors: kbarbora soulslicer

repo: carla-simulator/carla