Update client dependency to fix a race condition

Ran dep ensure -update k8s.io/client-go in the ext-apiserver directory.
What this PR does / why we need it: Pulls in a fix for a race condition that is making tests flake.
@kubernetes/kube-deploy-reviewers

/assign @rsdcastro @jessicaochen @medinatiger

/lgtm

/lgtm


Log silent pass failure

https://github.com/HackIllinois/iOS/blob/f15f9660d21ecc6d2add802136abae3786f2180c/HackIllinois/Controllers/ViewControllers/HIUserDetailViewController.swift#L110
Replace try? with explicit do/try/catch block and properly log the error.

Resolved by #131


updated header X-Message-Id to be case sensitive

Description of the change:
updated header X-Message-Id param in description to show that X-Message-Id is actually with Id and not ID, as it was originally written in this page.
Reason for the change:
the param returned is X-Message-Id AND NOT X-Message-ID
Link to original source:
https://github.com/sendgrid/docs/blob/rc-develop/content/docs/glossary/x-message-id.md

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @Gonent,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

Great! Happy to help out :)
Thanks :)
On Fri, Sep 14, 2018 at 8:28 PM Elmer Thomas<EMAIL_ADDRESS>wrote:

Hello @Gonent https://github.com/Gonent,
Thanks again for the PR!
We want to show our appreciation by sending you some swag. Could you
please fill out this form https://dx.sendgrid.com/swag so we can send
it to you? Thanks!
Team SendGrid DX
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sendgrid/docs/pull/3921#issuecomment-421428892, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA9RYNg9vFRcVULPLu0YGyRke-PTEMS_ks5ua-crgaJpZM4WXwGX
.


fix(config): correct max. value of SKU parameters for Kwikset locks

Without this, when using ZWave-JS-UI, openHAB is complaining that the value my locks are reporting is not in range 0 to 0.

You're correct, they're read only. I just tried to update it in ZWave JS UI, and it reverted back after a second.


Leaderboard / Activity Tracker do not add points for / track voice chat activity or going live.

I don't know if I can do this, but I should look into it as it makes sense to make this a measure of activity.

Not possible. Video interaction is pretty much prohibited by Discord, and I can't keep track of multiple voice channels at once. The bot must hold a voice connection to detect when users start / stop speaking.


If you're using VRTK then Vive (and eventually Windows MR et al) should be fairly simple to support

Seems a shame not to make use of the cross-platform capabilities if they are there. Happy to take a look if you're accepting PRs.

We are accepting PRs.
We already have  code for the vive:
https://github.com/IBM/vr-speech-sandbox-vive

We could target other platforms, but I would want to test on them, and currently don't have the hardware for Windows MR.
If you can test on other platforms, and can give them some basic testing, that'd be great. Any PR would be welcome.

OK. So I suppose my next question is "considering you're using VRTK - why have separate Vive and Rift codebases?"

That's a good question. We may actually merge the two, and just document the differences in build targets. It turned out that there were less differences than I thought there would be, so in retrospect the answer is different than during planning.

@thestonefox will confirm but I was under the impression that (unless you're targeting a feature unique to a platform) then any code differences needed between VR platforms should be filed as a VRTK bug.
However - I haven't looked at your codebase and I'm far from being a VRTK expert myself. :)


[Update Request]: MPC-HC v2.3.2

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
clsid2.mpc-hc
Package Version
2.3.2
Please describe the changes you would like to see
MPC-HC x64 64-bit installer for version 2.3.2 should point to:
https://github.com/clsid2/mpc-hc/releases/download/2.3.2/MPC-HC.<IP_ADDRESS>.x64.exe
It currently points to:
https://github.com/clsid2/mpc-hc/releases/download/2.3.2/MPC-HC.2.3.2.x64.exe
x86 URL should remain the same.

Dup of:
https://github.com/microsoft/winget-pkgs/issues/161087
https://github.com/microsoft/winget-pkgs/pull/161111

Close with reason: Duplicate;


CircleCI: Twemproxy, Sentinels and TLS

I counted up to 34 different scenarios we are going to officially support in the next release. Those are the all the possible combinations of: Twemproxy, ACL, TLS, Client TLS verification, Sentinels, Single Instance, Sync and Async.
For instance, these are some examples of possible scenarios:

Twemproxy in sync mode
Sentinels in async mode
Single instance with TLS but not ACL in async mode.
Sentinels with TLS and ACL, enforcing client certificate verification, in sync mode
... Many more.

I think those can be reduced to 10 critical scenarios:

Single instance, Sync and Async
Single with TLS and ACL, Sync and Async
Sentinels, Sync and Async
Sentinels with TLS and ACL, Sync and Async
Twempproxy, Sync and Async

Testing these 10 scenarios doesn't test all possible combinations, but tests all the code (except TLS client verification), I think it should be enough.
Since our tests suite always runs once for Sync and once for Async, what we need is to set up 5 CircleCI workspaces to run our tests on. This PR implements all of them.

Jira Issue
https://issues.redhat.com/browse/THREESCALE-10870
Note for reviewers
For further explanation, please read commits descriptions.

Closing this after giving up. Circle CI doesn't provide a way to mount files on the containers using the docker executor. And if we use the machine executor we would need to mount the entire ruby 3 framework from a raw ubuntu image, and invent a way to properly cache it to not have to do it in every pipeline run, it's not worth IMO. Also, using machine executor I couldn't manage to connect to redis.

Let's try again...

Ideally we would run the tests in a proper container instead of the host. That can be achieved by attaching a volume to the container.

I tried that, but CircleCI doesn't allow attaching a volume to a container when launching containers from the docker executor.
https://circleci.com/docs/using-docker/#docker-benefits-and-limitations

I tried that, but CircleCI doesn't allow attaching a volume to a container when launching containers from the docker executor.

If you can run random commands, it can be achieved like this. But as I said, that can be explored in the future.


How to insert nullable values?

I am using Option<String> to represent a nullable String but my code bellow complains that it expected a String instead of Option. How should nullable values be written with sqlx?
My code that doesn't work:
let name = Some("D1plo1d");
sqlx::query!(
    "INSERT INTO users (name) VALUES ($1)",
    name
);

Also seeing this with other types e.g. Option<i32> in similar scenarios.

#94 looks like it's gonna fix this problem more or less for good but it's a breaking change because we can no longer support unsized expressions (string[..] without a leading &) but that brings us more in line with println!() and was necessary to make the compiler errors really nice.

@abonander amazing! Let me know if I can help at all!

Give the branch a try if you don't mind. I've got some testing on it but if it fixes your use-case that would really increase my confidence on it.

Just tested it out tonight, working perfectly so far with no code change on our end. Will let you know if I see anything funky, but looking good so far! Awesome job

@kilpatty that edit is interesting. I tried to finagle the code so it didn't require ownership but I'm guessing those structs were behind & references and you got errors about trying to move out of those?
That's suboptimal. I'm pretty sure println!() doesn't have that problem; we're trying to match its behavior to simplify teaching of query!().

Yes exactly they were being & references. Looks like it's mimicking the behavior of dbg!() vs println!() in that scenario.

@abonander wow, awesome! #94 even fixed some additional Option issues I was running into.
I'm not sure if this is a bug but while on #94 running a query! selecting Nullable types gives me Error: unexpected null for non-null column. Changing that to a queryAs! with Options resolves my issue.
Is this expected behavior, bug or a regression?
Error: unexpected null for non-null column
sqlx::query!(
            "SELECT * FROM invites WHERE public_key=$1",
            identity_public_key
        )

Patched Version
pub struct Invite {
    pub id: i32,
    pub public_key: String,
    pub created_at: DateTime<Utc>,
    pub is_admin: bool,

    pub slug: Option<String>,
    pub private_key: Option<String>,
}

sqlx::query_as!(
            Invite,
            "SELECT * FROM invites WHERE public_key=$1",
            identity_public_key
        )

@D1plo1d nullability in output columns is actually an orthogonal issue. I have most of the groundwork in #108, I just have to update the wording on the errors after we did some internal bikeshedding. We're still open to opinions on those though.

@abonander That's awesome. Appreciate the work y'all are putting into these robustness issues!

Hello, if you want to use UNNEST, sqlx still requires T instead of Option<T> - so you can't really insert multiple nullable values


Update dependencies and fix compatibility with python3

WARNING: THIS IS NOT TO BE MERGED YET. I'm opening a PR to see whether I'm on the right track.
The purpose of this PR is to fix compatibility with python3 (the target is python 3.7) and update requirements and the setup script to the more up-to-date versions. During this change, many tests fail, which I'm trying to fix.

dumpsmach_test now runs with python 3.7, provided that a minor fix to the omega package is made.

FYI: @slivingston @murrayrm

Oh I didn't know about draft. Thanks for pointing out.
I just haven't tested on python3.8. There is no change that is specific to 3.7 though.

@tichakorn832 let me know if I can be useful here. We are not using it in Tulip yet, but a good tool for testing against a variety of Python versions is tox (on PyPI).

@slivingston Thanks. it would be nice if you could help take a look at the change in tulip/interfaces/omega.py to make sure that I formulate it correctly with respect to the new interface in omega. There seems to be interface change in the latest version of omega, making the previous code in tulip not working anymore. All the tests run fine except test_spec_realizable_bool  in gridworld_test.py that keeps running out of memory.

I am able to locally run test_spec_realizable_bool without error on GNU/Linux with Python 3.7.6.
@tichakorn832 Are you able to run the test locally? If so, perhaps the error arises from the configuration of Travis CI hosts. I will investigate.


MINOR: Capitalise topicPurgatory name

This is a minor change, to capitalise topicPurgatory name to have consistent logging. Please find attached snapshot

@junrao @granthenke @ijuma Please review the change.

Good catch. Unfortunately this change affects metric names, which has compatibility implications. A KIP is required for changes with compatibility implications: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals


Super-Linter Release: vX.Y.Z

Changelog
Tesring
Bugs

Testing t

Testing

Testing

testng

testing

testing

It's not stale

testing

testing

testing

testing

testing

testing

testing

testing

comment

test


New flaky crash of 'language_2/covariant_test/37'

This test is expected to produce a compile-time error, but has (flakily) crashed on dartk-optcounter-linux-release-ia32:
https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8901399150148309184/+/steps/test_results/0/logs/ignored_flaky_test_failure_logs/0
I didn't paste the logs here because the stacktrace is useless.

Since the code produces a compile-time error, it seems that the crash must involve execution of the CFE.

I could not reproduce after 800 runs.

Both language_2/covariant/covariant_test and language/covariant/covariant_test are currently passing on all configurations and not flaky.


Fix CI

👍

Is this simply an upgrade or does it also fix the build fail issue?

It should fix it. The problem is that we should use npm@next for building node_gyp, see https://github.com/nodejs/node-gyp/issues/972#issuecomment-229887765


⚠ Minecraft has degraded performance

In 38344d4, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1227 ms

Resolved: Minecraft performance has improved in 27fbee1.


objective C : not able to display

Added to like this -- but it's not working .. how am i supposed to add .. little stuck here...
UILongPressGestureRecognizer *lpgr = [[UILongPressGestureRecognizer alloc]
                                      init];
lpgr.minimumPressDuration = 1.0; //seconds
lpgr.delegate = self;
lpgr.allowableMovement = 80;
[self.feedsTableView addGestureRecognizer:lpgr];
NSArray *options = @[@{@"Option 1": @(PeekViewActionStyleDefault)},
                     @{@"Option 2": @(PeekViewActionStyleDestructive)}];

UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"Main" bundle:nil];
UIViewController *viewController = [storyboard instantiateViewControllerWithIdentifier:@"addpost"];

[PeekView viewForControllerWithParentViewController:[self currentTopViewController]
                              contentViewController:viewController
                           expectedContentViewFrame:CGRectMake(0, 0, 280, 400)
                                        fromGesture:lpgr
                                shouldHideStatusBar:YES
                                        withOptions:options
                                  completionHandler:nil];

Can you describe how it's not working? Which device / simulator / OS are you testing on?

Hey sorry, My bad.. its working fine.. I was not calling properly..


Update  grpc to 0.6 version

Grpc::ClientStub is required after protoc-rust-grpc generate

Thanks!


Openpilot Unavailable - Waiting for Controls to start forever - Reboot fixes it

Describe the bug
Hello, I get this error message saying Openpilot Unavailable - Waiting for Controls to start
Reboot fixes it but it comes back on next vehicle start.
The error occurred in code not modified by sunny or twilsonco.
Provide a route where the issue occurs
https://useradmin.comma.ai/?onebox=64e16c4237493597
openpilot version
<IP_ADDRESS>
Additional info

This should be reported to the fork maintainer instead. Feel free to open a new issue if you can reproduce this with stock openpilot.


Add query string support.

This pull request adds the capability to specify query string parameters
in the options hash.
Ex.:
iex> HTTPotion.get("www.example.com", query: %{page: 2}) # Yields a request with "www.example.com?page=2" as the url

Tests pass on my machine, did I broke something or is it a false positive?

Maybe it's just intermittent errors with httpbin.
Why did you move base into a separate file?? o_0

It's just seemed weird to have two modules in the same file. But I can put it back there if you want :)

Is there a reason to have them both there?

I don't like extra files and directories, there's no reason to split that file.
The thing is, you definitely shouldn't make changes like this in a pull request that adds a feature ;-)
If you could just remove that commit and force push your PR branch, that would be great.

Should be good now :)

Thanks!
(GitHub doesn't say it's merged, because I've cherry-picked your commits, because you've rebased #71 onto something else and it would be duplicating those commits...
This is actually going to clean quite a bit of code in a project of mine :)

Released 2.2.0 with this, redirects and finally, ibrowse from hex!


pod are runing but unhealthy

Looks like it is a stale message, that appeared during the cluster initialization, isn't it?

Cluster initialization will occur？ @tetianakravchenko

Looks like it is a stale message, that appeared during the cluster initialization, isn't it?

This is correct! @linqingping it looks like your cluster is healthy and running. Please re open this issue if you are having problems though.


lionwiki no longer works with Yunohost 4 / php 7.3  (PCRE issue)

because of a change in how php 7.3 handles regular expressions (they made a PCRE to PCRE2 migration which is much stricter, see https://php.watch/versions/7.3), lionwiki will have problems to render pages.
I'll try to fix this a.s.a.p.

It has been fixed upstream: https://sourceforge.net/p/lionwiki-t2t/code/ci/b13cd5b340ac0e6045c05a11515cf450b6430a8c/tree/txt2tags.class.php?diff=67e8ddc804b6ca09e2cb91dd734450e7857a4a60


branch proposal

How about add wrapper-component into the branch decorator?
branch(predicate,
    ...,
    renderNothing,
    ReactCSSTransitionGroup
)(WrappedComponent)

I had a similar idea, but it wouldn't be implemented in branch — it would be a new helper called wrapComponent (or similar):
wrapComponent(OuterComponent)(InnerComponent)

// renders
<OuterComponent>
  <InnerComponent />
</OuterComponent>

So your example would look like
compose(
  wrapComponent(ReactCSSTransitionGroup),
  branch(predicate,
    ...,
    renderNothing
  )
)(WrappedComponent)

As I understand it's the same as the nest decorator? The issue is that ReactCSSTransitionGroup triggers only when child component do mount or unmount. But branch component doesn't unmount itself only its left/right components.


[c++/python] Fixes for dense arrays and core 2.27/dev

Issue and/or context: As tracked on issue #2407 / [sc-51048].
Changes:
Some findings from https://github.com/TileDB-Inc/centralized-tiledb-nightlies/issues/25. There is more to do though.
Notes for Reviewer:
Python read-OOM repro
#!/usr/bin/env python

import tiledbsoma
import pyarrow as pa
import sys
import os, shutil

# Any dense 2D array with small current domain but huge (~ 2**63) core domain
uri = 'dense-dnda-227'

print("RD-DNDA URI", uri)

dnda = tiledbsoma.open(uri)
# This next line will slowly OOM -- watch htop
o = dnda.read()

Fixed as of this commit: https://github.com/single-cell-data/TileDB-SOMA/pull/3244/commits/0e6493a05ea64c58935c6216d579a671b3d95059
R write-fail repro
$ cat wr-lldb.r
#!/usr/bin/env Rscript

library(tiledbsoma)
library(arrow)

uri <- "data-dnda-r"
element_type = arrow::float32()
shape = c(10, 20)

cat("CR-DNDA URI     ", uri, "\n")
cat("CR-DNDA SHAPE   ", shape, "\n")

if (dir.exists(uri)) unlink(uri, recursive=TRUE)
dnda <- tiledbsoma::SOMADenseNDArrayCreate(uri, type=element_type, shape=shape)

cat("WR-DNDA URI", uri, "\n")
dnda$write(matrix(1:12, nrow=3,ncol=4))

dnda$close()

$ ./wr-lldb.r
CR-DNDA URI      data-dnda-r
CR-DNDA SHAPE    10 20
WR-DNDA URI data-dnda-r
Error: WriterBase: Buffer sizes check failed; Invalid number of cells given for attribute 'soma_data' (12 !=<PHONE_NUMBER>3709551615)
Execution halted

Fixed as of this commit: https://github.com/single-cell-data/TileDB-SOMA/pull/3244/commits/0e6493a05ea64c58935c6216d579a671b3d95059

Investigation so far shows that Python dense-array write calls C++ set_array_data as well as set_dim_points, while R dense-array write calls only the former and not the latter.
cc @mojaveazure and your observation the other day that the dense-array writer doesn't handle coords. Furthermore, as presently coded, it can only write the full core domain of the array. And now that with the new-shape feature flag enabled, the core domain (soma maxdomain) is huge and the core current domain (soma domain) is small.
Here is a repro that fails even with the new-shape feature flag disabled, proving that this bug is older than the new-shape mod:
#!/usr/bin/env Rscript

library(tiledbsoma)
library(arrow)

uri <- "data-dnda-r"
element_type = arrow::float32()
shape = c(10, 20)

cat("CR-DNDA URI     ", uri, "\n")
cat("CR-DNDA SHAPE   ", shape, "\n")

if (dir.exists(uri)) unlink(uri, recursive=TRUE)

dnda <- tiledbsoma::SOMADenseNDArrayCreate(uri, type=element_type, shape=shape)

cat("WR-DNDA URI", uri, "\n")

dnda$write(matrix(1:12, nrow=3,ncol=4))

dnda$close()

CR-DNDA URI      data-dnda-r
CR-DNDA SHAPE    10 20
WR-DNDA URI data-dnda-r
Error: WriterBase: Buffer sizes check failed; Invalid number of cells given for attribute 'soma_data' (12 != 200)
Execution halted

The typeguard-related failures are new and weird. I created #3245 to check.

CI run from commit 1 failed: https://github.com/single-cell-data/TileDB-SOMA/actions/runs/11542968229/job/32126790602?pr=3245

@nguyenv this is ready for review, and has green CI for this repo (i.e. with core 2.26).
There is still an issue or two remaining for core dev, which I have installed on one laptop to mimic @jdblischak 's nightlies. So, there will be at least one more PR. Meanwhile everything here on this PR is already a strict improvment.

Moving back to draft, likely to abandon later on.
On discussion with @nguyenv :

The main context of this PR is:

For dense arrays only
If any dim's subarray range isn't specified, core uses the core domain
With new-shape feature-flag enabled, and with core 2.27 where dense arrays can have current domain (they couldn't in 2.26), we are indeed using data-sized core current domain and huge core domain
Put those together and we get these problems
Note there are a few other issues on this PR, and a few not yet included in this PR, other than that -- and those should be split out into separate PRs

On this PR I've ben finding callsites, for write and for read, for Python and R, and touching up the ranges which end up being core subarrays on each dim slot

This is tedious and error-prone

What we should do instead is:

In one place -- in libtiledbsoma, in ManagedQuery, before submit_query
If any dim's range has not been set up to this point, and if the array has a current domain, simply set the ranges on that dim to be the current domain's (lo, hi)
We know (for a fact) that core will go ahead and use the too-big domain anyway so this is safe

Closing in favor of #3263 and #3268, and at least one more PR to come after those.


Add server and client feature gates to enable compiling server-only or client-only binaries

The motivation being, presumably, to keep binary sizes small. And maybe to be less of a lolbin? (We're pretty much gonna be a lolbin no matter what)

I wonder if separating out the knock listener might be handy; it could run on a proxy and open up forwards to internal boxes (see also #101)

Separating out the knock listener is also kinda desirable because: there's a way for nmap -sU to find the knock port using the user mode sockets we've got right now. For non-bound ports the kernel sends ICMP Port Unreachable responses, but it won't send an ICMP Port Unreachable for the socket where the knock listener is.
The best way around this I can figure is just to listen for the knock using a raw socket, which requires CAP_NET_ADMIN. Using a separate binary as a knock listener, that binary could be setuid or otherwise be privileged in a way where those privileges don't bleed into the rest of the program.


fix: update deps

This PR...
Changes

updated testkube and testkube-executor-init dependencies

Fixes

Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

This is not needed to get the updates through.


Handle duplicate Join Channel

Fixes #1235
Currently rps will call JoinChannel any time it receives a ChannelUpdated event. Right now it seems that we're sending out multiple ChannelUpdated events (possibly related to #1237)
The xstate-wallet ends up creating multiple workflows for each JoinChannel request, ending up with multiple Application workflows running, causing issues with the UI.
To safeguard this I've added deterministic workflowIds for some of the events so we can detect the duplicate call and avoid starting a workflow.
Longer term:
-RPS should probably be more careful about making duplicate calls

The xstate-wallet should not be sending out duplicate ChannelUpdated events (this might be resolved by #1237?)

RE: rps.  We make that API call in a saga every time a redux action is dispatched, as long as the channel status is 'proposed':
https://github.com/statechannels/monorepo/blob/855d07e75287daf15405a8dff78fdf2e55dd689c/packages/rps/src/redux/game/saga.ts#L86-L87
I suppose previous versions of the wallet, as well as the fake provider, may have changed the status of the channel more rapidly, preventing any more API calls being made? (And that might explain why things worked better then?)
From the saga's point of view, the API call is blocking. If the channel was guaranteed to be progressed out of 'proposed' when the joinChannel call resolves, then (I think) we wouldn't make multiple calls unnecessarily (except in case of error)?

RE: rps. We make that API call in a saga every time a redux action is dispatched, as long as the channel status is 'proposed':
https://github.com/statechannels/monorepo/blob/855d07e75287daf15405a8dff78fdf2e55dd689c/packages/rps/src/redux/game/saga.ts#L86-L87
I suppose previous versions of the wallet, as well as the fake provider, may have changed the status of the channel more rapidly, preventing any more API calls being made? (And that might explain why things worked better then?)
From the saga's point of view, the API call is blocking. If the channel was guaranteed to be progressed out of 'proposed' when the joinChannel call resolves, then (I think) we wouldn't make multiple calls unnecessarily (except in case of error)?

Hmm, that's a good point. Perhaps we should be sending a CreateChannel/JoinChannel response only once the channel is funded?  Also related to this is #1241 where RPS was missing a ChannelUpdated event since it was blocked on JoinChannel.
I think the two PRs can go in as is for now but I've created #1243 to consider when we should send out the responses/channel updated.


Add end user documentation for WASM extension.

For WASM Extensions https://github.com/envoyproxy/envoy/issues/4272
Add documentation including:
https://github.com/envoyproxy/envoy/pull/9259 - including stats, meaning, uses

Place docs here https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_features/scripting


bigtable: document connection pool

Hi,
I'm using bigtable from go. After about a week spent debugging and talking to support before I worked out what was going on, please document the connection pool setting in the bigtable client.
In particular this code in bigtable.go NewClient:
        // Default to a small connection pool that can be overridden.
        o = append(o,
                option.WithGRPCConnectionPool(4),

I was baffled by throughput issues before realising the client was limiting me to 4 connections internally.

Moved to https://github.com/GoogleCloudPlatform/google-cloud-go/wiki/Feature-Backlog.


Add labels in field areas

We should know what the fields are. labels should be added

Hi, there are already placeholders for input fields, adding labels is not very...mainstream, I can do it but it wouldn't look as good as a placeholder

@kb24x7 if you could just add an example and comment it

Added a template and commented it 👍


Accept a values file for spin new

Right now a user has to either work through the prompt or manually set KEY=VALUE strings through the CLI to satisfy the parameters defined in a template.
It'd be nice to pass a values.toml in the non interactive experience to avoid long CLI incantations

I would like to pick this up.

Thank you @mooori ! Let me know if you have any questions and feel free to @ me for a review when ready.

When a user has a parameter in values.toml and passes the same parameter via --value, would it make sense for the value passed as option to overwrite the value in the file?
For example with foo = 'a' in values.toml and --value foo=b as command option the final entry in the map would be ("foo", "b").

Yep. I agree. Explicit CLI definitions should take precedence.


Add cleanup command for expired tokens

Alternative to #10
This adds a command that can be run or scheduled to run periodically to remove expired tokens. The default behaviour is to remove tokens that have been expired longer than 3 hours, but this threshold can be adjusted by passing a DateTime constructor string as argument, for example:
php app/console keystone:token:cleanup yesterday
php app/console keystone:token:cleanup '3 days ago'

Een default van 3 uur vind ik wel erg kort, maar goed het is instelbaar... zou eerder aan een week of een maand denken.

@fieg The time is variable, but the main concern is that jobs that use the same token in parallel don't "suddenly" start getting 400 responses from the authenticator. 3 hours should be more then enough time for all processes to receive a 401, which should trigger a new token.

@oldskool I think there could be clients that don't request that often and without an expiration notice it would be harder for those clients to debug. But anyways, like we both said, it's configurable...

I don't think this is a proper solution. I would keep the tokens that are expired and throw away expired tokens of that user when he successfully re-authenticates (if that is possible). Then we get as many keys as we have users.
For server 2 server communication i would opt for bearer token like authentication. (for simplicity and speed, https is required though)

@mvanduijker That doesn't entirely work as well, see #10

This is what the spec says: http://developer.openstack.org/api-ref/identity/v2/?expanded=authenticate-detail

If the authentication token has expired, this call returns the HTTP 401 status code.
If the token has expired, this call returns the HTTP 404 status code.
The Identity API treats expired tokens as no longer valid tokens.
The deployment determines how long expired tokens are stored.

The deployment determines how long expired tokens are stored.

This is what we should look at IMO. A command that cleans up expired tokens solves all use cases mentioned here, and adheres to the spec, to the best of my knowledge. Per deployment you can choose to cleanup right after, a couple hours after, or never at all, depending on your preference.


KnowledgeBaseResponse.to_json() and .to_dict() crash with PydanticSerializationError

Example:
for knowledge_base_response in client.knowledge_base.list():
    backup_filename = f'./backups/knowledge_bases/{knowledge_base_response.knowledge_base_id}_{
        knowledge_base_response.knowledge_base_name}_{timestamp}.json'
    print(knowledge_base_response)
    with open(backup_filename, 'w') as backup_file:
        backup_file.write(knowledge_base_response.to_json())

Crashes with:
Traceback (most recent call last):
  File "/Users/username/Code/customername/projectname/retellai/./backup.py", line 36, in <module>
    backup_file.write(knowledge_base_response.to_json())
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Code/customername/projectname/.venv/lib/python3.12/site-packages/retell/_models.py", line 161, in to_json
    return self.model_dump_json(
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Code/customername/projectname/.venv/lib/python3.12/site-packages/pydantic/main.py", line 352, in model_dump_json
    return self.__pydantic_serializer__.to_json(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pydantic_core._pydantic_core.PydanticSerializationError: Error serializing to JSON: TypeError: 'MockValSer' object cannot be converted to 'SchemaSerializer'

Identical problem happens when using to_dict().
Note that it works with several other very similar implementations, but for other data:
for agent_response in client.agent.list():
    backup_filename = f'./backups/agents/{agent_response.agent_id}_{
        agent_response.agent_name}_{timestamp}.json'
    with open(backup_filename, 'w') as backup_file:
        backup_file.write(agent_response.to_json())

for llm_response in client.llm.list():
    backup_filename = f'./backups/llms/{llm_response.llm_id}_{timestamp}.json'
    with open(backup_filename, 'w') as backup_file:
        backup_file.write(agent_response.to_json())

for phone_number_response in client.phone_number.list():
    backup_filename = f'./backups/phone_numbers/{phone_number_response.phone_number}_{
        phone_number_response.nickname}_{timestamp}.json'
    with open(backup_filename, 'w') as backup_file:
        backup_file.write(phone_number_response.to_json())

It seems to be a known problem with Pydantic: https://github.com/pydantic/pydantic/issues/7713
Tried to downgrade Pydantic to 2.4.0. But still had the same error. Same with these versions: 2.10.2, 2.9.2, 2.8.2, 2.7.4, 2.6.4, and 2.4.2.
Using macOS 15.1.1 with zsh, asdf, etc. Python and venv as visible in paths of traceback.
Does this work and is tested on your end? Any idea how to solve this?

Same problem as well. How to fix this issue?

This is due to a mismatch between the returned value and the openapi definition. This has been fixed now.


Switch to targetSdk = 34

WHAT
WHY
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

cc @huewu


Print settings in log msg

Add to the printed log what settings were used because it can help catch some problems earlier.
E.g. somebody wanted aggregated output but it was set it individual and they haven't updated it.

Done in ebf7f37e8f1d3216d7a5000312d435a1a3a1bc9a


chore: add volunteer DominicFrei

@codewithvoid Thank you for the quick review. I've added another commit to address your comments. :)

Thank you, @codewithvoid !


Wiki's use of $XDG_CONFIG_HOME can be more clear

Describe the bug
The Customization and Configuration pages in the wiki mention:
$XDG_CONFIG_HOME/macchina/ on Linux and the BSDs.
This is technically correct, but can be confusing since most Linux distributions do not set $XDG_CONFIG_HOME.  This will lead many users unfamiliar with $XDG settings trying to echo that in a prompt will not get a response and not know where to put the configs without some Googling around.
I recommend changing both pages to:
~/.config/macchina/ on Linux and the BSDs. (or $XDG_CONFIG_HOME/macchina/ if set)
And another point of clarification on the Customization page is to mention themes must be placed in individual TOML files inside the themes/ directory.  The way it is currently stated makes it seem they are configs all in a themes file.

Hi, thank you for taking the time to write this issue out!
I totally agree with you, you may edit the wiki if you'd like.

Fixed :)
Please let me know if you notice any other areas where the wiki can be improved.
I appreciate you reaching out!


snowcrash: fix on aarch64-darwin

Picks up a patch that updates golang.org/x/sys so that it can be built on aarch64-darwin using Go 1.18.
This fixes this Hydra failure.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Looks good to me.


Different device

Hope I can use windows as option and option on my external keyboard.
and don't need to reset it while i just my MacBook pro build in keyboard.
XD

@JefferyVin I have made some enhancements to KBE to support per device configuration within the same profile. Please check if this helps: https://github.com/tekezo/Karabiner-Elements/issues/770 Any questions please let me know.


Ursa 0.2.0 dev 2

update ursa to new version
This might solve linking issues caused by different versions of openssl-sys being used by ursa and libindy
Also updated Cargo.lock

@AxelNennker could you work with @mikelodder7 and make sure that releases or tags exists in the Ursa repo and they are synced to crates.io releases. I think it would be helpful to have ability to check the differences between Ursa versions. As soon as it's not formal releases I don't think special changelog should exist, but at least tags should be useful from my point of view.

There are releases in ursa but libindy uses the dev version.
So think it is already as you suggest.
I think there is an issue with the dev-1 version that uses a version of openssl-sys that is different to the version libindy is using and because of it we have link problems on Ubuntu18.
I don't see the link currently in my PRs anymore...
Not sure how to proceed regarding openssl in ursa and libindy. Reexporting everything (openssl, libsodium, ...) from Ursa is not unproblematic in itself because libursa gets too fat and projects dependent on libursa might be able to follow all libursa decisions.
Currently libindy is using openssl for sha256 and libursa is using openssl for bignumber stuff.
https://github.com/hyperledger/ursa/pull/61

@AxelNennker @mikelodder7 taking into account few latest comments in https://github.com/hyperledger/ursa/pull/61 I'm in doubt about this PR...
Should ursa be republished without Cargo.lock to crates.io and then we can update this PR and merge it?

ursa dev-2 has the same openssl-sys as libindy and I assume that is good for libindy's Ubuntu18 builds where we saw some link errors
In general, I think, libindy should not use the ursa dev crates but the released versions.
And the ursa crate should not have Cargo.lock which led to the situation that they used different versions of openssl. Neither should libindy use a binary libursa.dylib/so/a but a ursa rust crate with some 0.1.* version number.
Regarding ursa's publishing dev versions to crates.io, I suggest not to do that. If a rust program or library wants to use a pre-release version it can use cargo's git feature and get the pre-release version from there.

Ursa-0.2.0-dev-6 is up. Its the same as dev-5 except it includes a CHANGELOG and LICENSE


Memory leak just including the module

node.js 10.10.0
npm 6.4.1
express: 4.17.1

Memory usage went from 60MB (normal) to 450MB over 9 hours by simply including the module:
const quillConverter = require('node-quill-converter');

Hi @jessewilliams1 Thanks for submitting this. I'll look into it.

This looks suspiciously like an infinite loop:
document.execCommand = function (command, showUI, value) {
  try {
      return document.execCommand(command, showUI, value);
  } catch(e) {}
  return false;
};

Hmmm. I'll test it out. Thanks for your patience.

Hey @joelcolucci, the leak is probably due to the JSDOM library and the fact that you are reading the quill file synchronously. That could have an impact when converting large files.
The reason why the leak occurs by just including the file is that the reading of the file is done at the top level. So whether you use the package or not, it will always read the files.
I'm using this package locally and how I solved it is by using fs.promises.readFile and instead of using require.resolve, I used path.join to get the full path to quill.min.js file.
The performance improved greatly.

Thanks @adesege. I'll try out those adjustments. I appreciate your time and feedback.

You are welcome man! The package gave me a good start though. Thanks.

@joelcolucci Is memory leak issue resolved now? I have to convert HTML to Delta on nodejs server side. So i need this package to implement on node side

Unfortunately, in my testing, there is still a memory leak. I updated to version 0.3.3 and let the node server run on the server. It took about 2 days, but the memory usage kept increasing until it ran out of memory.

@extremerotary Thanks for the feedback.
In my testing I noticed that a potential leak occurs when calling Quill.setContents. Quill might have a circular reference preventing the garbage collector from cleaning things up. I'm away this weekend but will dive back in next week.
Are you using this in a web application or an ETL pipeline?

@joelcolucci
Hey Joel,
We use it in a web application.

I experienced the same issue after including the module in a nodejs app. I use it to convert quill delta to HTML.
See memory usage in blue:

nodejs 14.9.0 npm 6.14.7 express 4.17.1 node-quill-converter 0.3.3
At the moment, I simply require the module like so: const { convertDeltaToHtml } = require("node-quill-converter"); and then use it when needed: convertDeltaToHtml(delta); Is there anything I should be doing differently?

Hey @Trunksome, thanks for letting me know. I'm backed up work up at the moment. I'll try and spin up a long running process and see if I can replicate, isolate this issue.

Hi @joelcolucci really nice work on this project!
Is there any update on this issue? I'm using the module the same way as @Trunksome, and the service is eating up lots of memory and dies frequently.

I ended up closing this library and wrapping everything in a class (thereby only creating a JSDOM when needed) and calling
close() {
    this.cache = null;
    this.DOM.window.close(); // found it here: https://stackoverflow.com/questions/13893163/jsdom-and-node-js-leaking-memory
}

once i'm finished with the converter.
Memory leaks are gone.


Feature/wrap syscall

add a separate tracer which wraps ioctl(KVM_RUN) to intercept all KVM_EXIT_MMIO. The programmer can then observe the mmio write requests and himself serve the mmio read requests.
It is mutually exclusive with the inject_syscall tracer, will probably join both later).

todo: fix clippies and remove dead code/commits


Make JSON properly write and parse dictionary keys

Fixes #33161.
Allows to successfully serialize dictionary instances (as keys) in #33137.
This is certainly a hack currently, need more work. Ideally any json-incompatible type should be converted with VariantWriter as JSON strings and read with VariantParsers, see https://github.com/godotengine/godot/issues/33161#issuecomment-548053758.

Closing for now because this needs more fundamental changes to how JSON writes and parses json-incompatible types against Variant, but this should give some direction, again see https://github.com/godotengine/godot/issues/33161#issuecomment-548053758.


Zeng Hou Project Portfolio Page

Updated project portfolio page

Coverage remained the same at 92.063% when pulling f29326d8fde259c2dbcb9f79f3d8952ef5f62773 on zenghou:zengHouProjectPortfolioPage into 0427d51c520799e179b08781c1abffee2bf9b025 on CS2103AUG2017-F11-B4:master.


Delete scrup.rb

Dead.

Merged as eb3641132284f3d75c10f0ae0cd42fde4c5ee63f.

There's a slippery slope to looking for alternate, valid links to a download, but if the link on the readme were changed to point to the GH releases page, this would still be valid, no?

if the link on the readme were changed to point to the GH releases page, this would still be valid, no?

Yes. I don’t think we’d even need to get that far. The homepage is the github repo, so outright using the releases download would be appropriate. I looked into it before removal, though, and in this case it doesn’t apply because the releases page only contains the source, not a usable binary we can get.
This has been discontinued, though, so it’s unlikely they’d want to add it anyway.


arduino ESP8266

Hello there
Would this work for an esp8266 /NodeMCU ?
I would like to try this to serialize an array of struct and back again.
I'd be happy to experiment and feedback.
Thank you
Den

Hi!

Would this work for an esp8266 /NodeMCU ?

We just don't know because we are far from embedded development, sorry.


Power measurements not working with Broadwell

Power measurements do not work properly for Broadwell family processors (and newer)

I checked on a couple of Broadwell machines and it seems to be working.


accessing parameters in ruby

Hi Guys,
Thanks for the Gem!
Is there a way I can access a parameter in ruby rather than use a parsed parameter in cfndsl.
For example I want to do something like
Description parameters['environment'] + 'ec2_cloudformation_stack'
Rather than an FnJoin with a Cloudformation parameter
Thanks for your help,
thebeefcake.

Short answer:
Not currently
Long answer:
You cannot dereference parameters before the template is compiled by CloudFormation. DSLs like cfndsl provide a wrapper, but ultimately just compile a JSON template that's submitted to the CloudFormation API. Since StackMaster uses CloudFormation parameters, the value of that parameter is not looked up at any level until it's submitted to the API. So your DSL (whether it be Sparkleformation or cfndsl) has no capability to know the parameter value at (it's) compile time.
It might be possible to submit the parameters to cfndsl or SparkleFormation as a variable or method for dereferencing, so that it can know about them, but this functionality does not exist today.

Thanks Patrick,
I'm not sure I was clear in what I was trying to do, Is there a way to use a parameter defined in yaml as a variable in ruby/cfndsl rather than bringing it in as a cloudformation parameter.

The parameters are available to stack master and Cloudformation but not the DSL (and hence no code written in the DSL) without calling out to StackMaster, and exposing a lot of implementation details to the DSL. This would be extremely fragile and likely to break with updates to StackMaster.
The only way I can see to do this would to change StackMaster to pass the parameters to the DSL library when we compile the template. This seems possible with Cfndsl.

I started on addressing this in #120 but it still needs a little more work.

@redterror see #144 its complete in there

Implemented in #120 and released in 1.10


How active is the development

Just wanna reach out and see what the status of the development. We are planning on using Kysely and in need of pagination capability.

Hey,
Broadly speaking I think it is largely "done" for the time being. I've been using it myself without issues but I'm not yet using it in production (though actually will be very soon). I built the library to solve my use cases and it now does, so I'm not in any rush to add any new features, though I'm happy to look over any issues or pull requests.
That said, it's overall a very simple library so as long as you don't run into any edge cases that I haven't, it shouldn't be too risky of a dependency.


raidboss: update actor control wipe for timelines

This is the timeline change for #4691.
To avoid having to redo this change in the future,
change the timelines to the desired future 6.2 code,
and use the same "back compat replacement" strategy
that we used before #4431 removed them.

Tested this manually by printing out the regex from timelines.  It looks good to go.


Reduce the frequency at which the Pulumi Operator hits the GitHub API

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
Posting on behalf of a customer. Mainly, this is to rate-limit API requests due to low API key limits.
This is partially addressed with ResyncFrequencySeconds; however, that does not impact (failures during deployment)[https://github.com/pulumi/pulumi-kubernetes-operator/blob/da76f15514ec9e7d99c885ddab019c3026e1d7dd/pkg/controller/stack/stack_controller.go#L872-L898], which result in requeue after a fixed interval of 5s or immediate requeue.
Affected area/feature

Thanks, @meagancojocar - we'll get this lined up as soon as we can.

Added to epic https://github.com/pulumi/pulumi-kubernetes-operator/issues/586

Good news everyone, we just released a preview of Pulumi Kubernetes Operator v2. This new release implements a back-off strategy when hitting upon stack errors, to avoid hitting the GH API too frequently:
https://github.com/pulumi/pulumi-kubernetes-operator/pull/709
Please read the announcement blog post for more information:
https://www.pulumi.com/blog/pulumi-kubernetes-operator-2-0/
Would love to hear your feedback!  Feel free to engage with us on the #kubernetes channel of the Pulumi Slack workspace.


[Feature Request] System Prompt Support

When I use Llama, it outputs PARAGRAPHS of text from a very simple question.
As such, for the HuggingChat web client, I have a custom system prompt to get it to be more concise. Yet, this doesn't carry over to the Mac client.
If support could be added for this, the app would be perfect.

Hi all, if nobody is working on it, I would like to take this up.
Thanks!

Hi all, if nobody is working on it, I would like to take this up. Thanks!

I will start working on this. Thanks!


Hashtag symbol (#) in function names breaks syntax highlighting

Hi, and thank you for developing this VS Code extension.
I've noticed that the following breaks the highlighting:
(set-info :category "industrial")
(declare-sort |T@U| 0)
(declare-sort |T@T| 0)
(declare-fun Ctor (T@T) Int)
(declare-fun intType () T@T)
(declare-fun int_2_U (Int) T@U)
(declare-fun U_2_int (T@U) Int)
(declare-fun type (T@U) T@T)
(declare-fun LitInt (Int) Int)
(declare-fun BoxType () T@T)
(declare-fun $Box (T@U) T@U)
(declare-fun MapType (T@T T@T) T@T)
(declare-fun MapTypeInv0 (T@T) T@T)
(declare-fun MapTypeInv1 (T@T) T@T)
(declare-fun |Set#Card| (T@U) Int) ; <-------------------- broken after this line
(declare-fun |Map#Card| (T@U) Int)
(declare-fun |Map#Values| (T@U) T@U)
(declare-fun |Map#Empty| (T@T T@T) T@U)
(declare-fun |Map#Build| (T@U T@U T@U) T@U)

Thanks @WirelessWizard for reporting this.  I will try and fix it once I page it all back in.

I bumped into this one today as well with the following:
(declare-fun |@foo_i8#i8!void#ub!9| () Bool)

Either of you guys are welcome to fix it, I had a quick look and didn't succeed.

This line here seems to be missing the # char: https://github.com/SRI-CSL/SMT.tmbundle/blob/master/Syntaxes/smt.tmLanguage#L116
I just have no clue how to test a grammar change in VS Code ☺

I did five years ago, it was a bit of an adventure, and I had time. But a lot has happened in 5 years and I fear it has
been permanently paged out.  I can add it and hold my breath. Though I think I would need to push it upstream to
the linguist repository. Alas I am very busy so ...

But if you feel the urge, I can certainly pass the buck to you. You could be chief maintainer of the  SMT.bundle.
There would be no turning back. Your life would be forever changed. Fame, fortune, celebrity status ...


[QUESTION] - Why don't use just isOnline?

In the with-online-status-props component, why don't use just isOnline property in state? If is offline soon will not true, in the isOnline property
this.state = mapStatusToProps({
        isOnline: global.navigator.onLine,
        isOffline: !global.navigator.onLine
      })

Hi.
That's the internal state and implementation. From outside:
const Demo = (props) => (

props: {JSON.stringify(props)}

);

export default withOnlineStatusProps(
  ({ isOnline, isOffline }) => ({ isOnline, isOffline })
)(Demo)

What you return there is what you get as props, zero or many.
Feel free to continue conversation here even if the issue is closed :)


[zh-cn]Reference files to sync task 13

Reference files to sync task 13
Related to task-13 of issue https://github.com/kubernetes/website/issues/39987.

Thanks.
/lgtm
/approve


Document in FAQ running KIC as DaemonSet

Description
Based on information gathered from

https://github.com/Kong/charts/pull/269
https://github.com/Kong/kubernetes-ingress-controller/issues/682
https://kubernetes.github.io/ingress-nginx/deploy/baremetal/#via-the-host-network

document when and how deploy KIC as DaemonSet, update of Helm chart docs is needed to, see and review https://github.com/Kong/charts/pull/918

Testing instructions
Preview link:
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

This is replaced with https://github.com/Kong/docs.konghq.com/pull/6403


Android Basics: Introduction to Room and Flow

Whenever you try to download the starter app in GitHub, the main branch is downloaded instead. All the changes are already done for the codelab. The only way I could get around it was to copy and change the URL to say "starter" rather than "main."

...I wonder if that's a Github issue, because usually when I'm on a specific branch it downloads that branch, and the URL in the codelab goes to the starter branch page. (And it downloaded the starter branch when I started-but-didn't-finish the codelab.)

I think Github fixed this a few weeks ago, FWIW.

I believe the issue is now fixed, but thanks for filing to increase awareness for other developers!


Get AbstractPlugin in AbstractPlugin

I use plugins like API for my components.
When I call method of plugin in controller — it works.
// Сontroller
class CatalogController extends AbstractActionController
{
    // Action
    public function indexAction()
    {
        // Getting plugin in my controller and call a function — OK
        $this->AlbrinPersonalSaleUser()->add();
    }
}

But if I try to call method of plugin in another plugin:
// My plugin
class AlbrinPersonalCart extends AbstractPlugin
{
    public function getBasketUserId()
    {
        // I receive an error
        $id = $this->AlbrinPersonalSaleUser()->add();
    }
}

Error message
Call to undefined method AlbrinPersonal\Controller\Plugin\AlbrinPersonalCart::AlbrinPersonalSaleUser()

Can I use plugin another plugin, without passing additional objects?
P.S.: Temporarily, I found the following solution
// My plugin
class AlbrinPersonalCart extends AbstractPlugin
{
    public function getBasketUserId()
    {
                $albrinPersonalSaleUserPlugin = $this->getController()->getPluginManager()->get('AlbrinPersonalSaleUser');
                $id = $albrinPersonalSaleUserPlugin->add();
    }
}

The better way is you inject the plugin:
class AlbrinPersonalCart extends AbstractPlugin
{
       private $albrinPersonalSaleUser;
       public function __construct(AlbrinPersonalSaleUser $albrinPersonalSaleUser)
       {
              $this->albrinPersonalSaleUser = $albrinPersonalSaleUser;
       }
}

and then, you can use factory for it:
'AlbrinPersonalCart' => function(\Zend\Mvc\PluginManager $manager) {
         $plugin  = new AlbrinPersonalCart($manager->get('AlbrinPersonalSaleUser'));
         return $plugin;
},

I think it is not an issue ;). close-able ;)

I am developing an engine for online store and other components for integration with multiple services on Zend Framework.
It is planned that the components can be any number. For example, forty components. Each component may have a different number of plugins — API.
Components must be loosely and able to communicate with each other through the API.
Therefore, each time to do such injections will be difficult:
'AlbrinPersonalCart' => function(\Zend\Mvc\PluginManager $manager) {
         $plugin  = new AlbrinPersonalCart($manager->get('AlbrinPersonalSaleUser'));
         return $plugin;
},

Plugins are not seeded with the plugin manager; only controllers are, which is why you cannot do method overloading to retrieve them.
You have three options:

inject your plugins with the plugins on which they depend, as @samsonasik suggested. This is the best option, as it ensures there are no hidden dependencies, encourages and facilitates testing, and allows for easy substitutions via alternate factories.
Create an alternate abstract plugin base that accepts the plugin manager; plugins can then pull other plugins from that. Use an initializer or delegator factory to inject the plugin manager automatically.
Plugins already compose the controller that calls them, so you can also pull plugins from that: $this->getController()->plugjnName().

Hi samsonasik,
Please let us know where (which file)  we inject the below code for calling plugin into another plugin as i am new to zend 3.
'AlbrinPersonalCart' => function(\Zend\Mvc\PluginManager $manager) {
$plugin  = new AlbrinPersonalCart($manager->get('AlbrinPersonalSaleUser'));
return $plugin;
},
Thanks


Toggle All returns empty array

Hello i just landed in a weird scenario, the problem i was facing with the toggleAll().
Situation
I've assigned variable name "selected" for `md-row-select` attribute and in the controller this `selected` array comes under the `$scope` variable.
Issue
Case 1: This works perfectly fine while selecting each list item separately, it fills the `selected` array with appropriate selected data. :+1:
Case 2: While selecting the toggleAll checkbox the list items in the UI got selected but on the other hand the array selected inside the controller is supposed to get filled by all the selected items, whereas it still reflects the length 0.
I've tried various methods to fix this problem even touched the  md-data-table.js but found no success, then i tried to find the bug in the [demo] (http://danielnagy.me/md-data-table/) page & realized that the demo page is also struggling with the same error as i am.
Ref 1

Ref 2

Please help

I'm a little confused as to whats going on. I've created this pen that will log the selected items to the console from within the controller and it appears to be working fine.
I'll investigate this more when I have time.

I haven't been able to duplicate this in your pen, and it certainly doesn't seem to be a problem in the demos, but I'm experiencing this problem as well in my implementation.
In my case, I can select individual rows, and they get added to the array.
If I select all rows with the top checkbox, the array is empty.
If I touch the top checkbox, the individual row selection never works -- after checking the top checkbox, the array stays empty no matter what I do next.
Same Angular version, same Angular Material version. No idea what might be causing it/interfering with that box.

I ran to same problem if add ng-if="true" to table element like:

has anyone found a work around for this?

+1
Adding the ng-if to a table element causes this error.

This may be a natural consequence of the ngIf directive.

Note that when an element is removed using ngIf its scope is destroyed and a new scope is created when the element is restored. The scope created within ngIf inherits from its parent scope using prototypal inheritance. An important implication of this is if ngModel is used within ngIf to bind to a javascript primitive defined in the parent scope. In this case any modifications made to the variable within the child scope will override (hide) the value in the parent scope.

What version of this module are you using? I just tested an ngIf directive on the mdTable element in version 0.9.4 and the toggleAll feature still work.
If you can't update to version 0.9.4, or it is still not working for you, try putting the ngIfdirective on a parent element or use ngShow

Thanks for the quick reply, Daniel. I'm using 0.8.14. Changing ng-if to ng-show fixed the problem :+1:


Add d2l-selection-action-dropdown.

This PR adds a new d2l-selection-action-dropdown component, that like other selection components supports the requires-selection attribute to control the enabled/disabled behaviour based on the selection state.  It further enhances the d2l-overflow-group to respect this opener and its children.
It can be used in conjunction with any dropdown content in the same fashion as the existing dropdown openers.

I noticed the d2l-selection-action and d2l-selection-action-dropdown components were not getting the expected spacing within the overflow group like other components - added that to the CSS.


Link to 'good first issues'

We encourage projects to use the 'good first issues' tag for identifying issues that are good for newcomers, could we incorporate that into the card somehow? Maybe even with a counter of the number of good first issues?

Hi again!
Are you familiar with CLOTributor? One option would be to add a link to CLOTributor filtering by the corresponding foundation and project.

There is also CLOMonitor, which we've already partially integrated in landscape2 by displaying a summary report in the item details view (when available).

It's easy to add more foundations to both sites, so if you are interested we could discuss it 🙂 Fore more details about how CLOTributor works, please take a look at the README file in the source repository.

I'm somewhat familar with that tool. It does seem interesting, buPt I'm unsure of the overall alignment with the recommended best practices and project measurement tooling for LF projects. Probably a much larger discussion ;-)
For this, could we just simply use the existing 'good first issues' badge, but better integrate it into the UI? https://github.com/badges/shields#contributing

Thanks! If we could also have the data for good first issues that we could pull out in a CSV/API, that would be great.
Is CLOTributor connected to landscape-listed projects? I like the idea and would love to make it something that could be used for my foundations.

If we could also have the data for good first issues that we could pull out in a CSV/API, that would be great.

You could use the same -undocumented yet 😇- API that powers the UI if you'd like 🙂 (output is json though).
Sample request to get good first issues for CNCF projects:
https://clotributor.dev/api/issues/search?limit=20&offset=0&good_first_issue=true&foundation[0]=cncf

Is CLOTributor connected to landscape-listed projects? I like the idea and would love to make it something that could be used for my foundations.

Not yet, but the plan is to eventually have it feed from the landscape data, yes. At the moment both CLOMonitor and CLOTributor feed from the same data files hosted on the CLOMonitor repo.

Done!
Closed by #582


fix(bootstrap): Fix indent and bump boostrap version

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Looks like the change already exists.


resque-pool fails to launch on macOS High Sierra

Launching resque-pool results in an error
Error message
objc[5921]: +[__NSPlaceholderDictionary initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

Apple made changes to forking processes in High Sierra to harden security of the OS it seems.
I found a workaround on Stackexchange in a question related to Unicorn.
 OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

https://stackoverflow.com/questions/46591470/unicorn-with-ruby-2-4-1-causing-weird-crash
Ruby
https://bugs.ruby-lang.org/issues/14009


Deploying front-end

On SE1, you can deploy your front-end to ipfs, s3 and surge:

I think it's super handy to have this functionality built-in, but, following the SE2 motto (keep it simple & minimal 🫡) I think we don't want to have all the options, at least for now.
From what I've seen, most of the people use surge (yarn build + yarn surge), since it's 0-config and it gives you an URL directly. I guess IPFS will also make sense at some point.
Also since we are using NextJS, we can only deploy to Surge (or any other "static sites" hosting) when using client side rendering (no ssr, api routes, etc). We can mention Vercel in the DOCS for people who needs server functionalities.
Thoughts? @technophile-04 @rin-st

I agree, surge is the simplest way and enough for now. We can consider Vercel or alternatives in the future if ssg/ssr will be needed.
What do you think about the possibility of deploying only the UI page with our header and footer(with SE icon/'Built with SE' message)? As a user, I don't need home/debug pages after deploying.

What do you think about the possibility of deploying only the UI page with our header and footer(with SE icon/'Built with SE' message)? As a user, I don't need home/debug pages after deploying.

Right now people would need to remove those pages (which is not a big deal) + deploy. I think making the "magic" (removing pages, or other stuff) on deploy could be tricky.
Also, we could consider removing the Homepage for good....and showing some text + the debug contract stuff.
But maybe, in the future, we could build some script to clean SE-2. e.g.:

a script to remove all the demo pages & debug
a script to remove all the TW classes (for people that want to use their own classes, or UI system)
...

Too many options!
But let's keep focusing on the core stuff and iterate. We'll have a bunch of feedback when people start using it.

Love the discussion and suggestions here.

I think this is the right time for drafting a PR for yarn surge (surge seems simple, minimal nd comfortable for se-1 devs too ) what do you guys think? Because having a build in functionality to deploy is really great / handy / core before we start sharing with others
having a way to deploy to ipfs is really great to have and have alot of discussion on Twitter recently that you should deploy your app to a decentralized service too. I saw fleek has some cli, checkout -> @fleekhq/fleek-cli maybe we can explore this or even the current se-1 approach is fine. Also its not important at the moment but really good to have before we start sharing.

Also, we could consider removing the Homepage for good....and showing some text + the debug contract stuff on init

Why? I like the homepage 😅, I see developers/myself taking inspiration from example-ui.tsx file and directly start editing index.tsx(Homepage). if we have debug contract on Homepage/index.tsx itself then I cannot tinker with contract simultaneously while building UI, I like to edit UI on localhost:3000 and tinker  on locahost:3000/debug and switch back and forth while developing(might be only my personal view). No hard feelings if we remove it though 🙂

I see developers/myself taking inspiration from example-ui.tsx file and directly start editing index.tsx(Homepage)

You can edit example-ui.tsx and not even touch index.tsx :). So you'll need the homepage only when developing an app

Great stuff!!

I think this is the right time for drafting a PR for yarn surge (surge seems simple, minimal nd comfortable for se-1 devs too ) what do you guys think? Because having a build in functionality to deploy is really great / handy / core before we start sharing with others

Agree, let's go for it! Any of you feel free to assign yourselves to the issue.

Why? I like the homepage sweat_smile, I see developers/myself taking inspiration from example-ui.tsx file and directly start editing index.tsx(Homepage).
You can edit example-ui.tsx and not even touch index.tsx :). So you'll need the homepage only when developing an app

Love having different opinions on this! haha. I think we shouldn't do anything for now. At some point in the future, after we (and other devs) use SE2 and we have more feedback, we can re-open the discussion again.


Race condition when creating a scheduled action from Sunstone

Description
When creating a periodic snapshot-create action for a VM from Sunstone, an infinite loop of create-snapshot action is executed, having messages like these ones in the OpenNebula log:
Wed Oct  6 12:20:41 2021 [Z0][ReM][E]: Req:9680 UID:0 one.vm.update result FAILURE [one.vm.update] Cannot update template. Error parsing END_VALUE, times has to be greater than 0
Wed Oct  6 12:20:41 2021 [Z0][ReM][D]: Req:1888 UID:0 IP:<IP_ADDRESS> one.vmpool.infoextended invoked , -2, -1, -1, -1
Wed Oct  6 12:20:41 2021 [Z0][ReM][D]: Req:1888 UID:0 one.vmpool.infoextended result SUCCESS, "<VM_POOL><VM><ID>129..."
Wed Oct  6 12:20:42 2021 [Z0][VMM][D]: Message received: SNAPSHOTCREATE SUCCESS 129 snap-3

To Reproduce
To reproduce the issue:

Go to "Action" tab
Specify the action (e.g snapshot-create) and time, and check the "Periodic" checkbox.
Specify "Repeat" as "Hourly" and "Each 1 hour".
Specify "End" as "After Each 2 times".
Add a action.

Expected behavior
Periodic actions must be executed just at the time they are scheduled.
Details

Affected Component: Sunstone & CLI
Hypervisor: KVM
Version: 5.12

Additional information
The same behavior occurs in the CLI.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

fixed in 6.2.0, closing


Reduce inline code block padding to prevent collision

Based on https://github.com/wagtail/wagtail/issues/6793
This should be avoided:

It would also be good to increase the font size.

Does this issue still persist?

Not sure. I am not sure if we still have background on inline code. You could create an example to check that.

I checked and I didn't find any background only red-colored text.
We can close this issue

1 down 23 remaining ✌


Position of tooltips with dynamic content incorrect

Tooltips that have dynamic content are not centered. If you also set a different position (e.g. position="LEFT"), then the tooltip will not even open

The dynamic content is added to the tooltip after the change detection cycle. As a result, the size of the tooltip is not quite correct after the first positioning. Therefore, we have to manually reposition the tooltip as soon as the size changes


Recommended practice to shuffle data with datapipes differently every epoch

📚 The doc issue
I was trying torchdata 0.4.0 and I found that shuffling with data pipes will always yield the same result across different epochs, unless I shuffle it again at the beginning of every epoch.
# same_result.py
import torch
import torchdata.datapipes as dp
X = torch.randn(200, 5)
dpX = dp.map.SequenceWrapper(X)
dpXS = dpX.shuffle()
for _ in range(5):
    for i in dpXS:
        print(i)   # always prints the same value
        break

# different_result.py
import torch
import torchdata.datapipes as dp
X = torch.randn(200, 5)
dpX = dp.map.SequenceWrapper(X)
for _ in range(5):
    dpXS = dpX.shuffle()
    for i in dpXS:
        print(i)   # prints different values
        break

I wonder what is the recommended practice to shuffle the data at the beginning of every epoch?  Neither the documentation nor the examples seem to answer this question.
Suggest a potential alternative/fix
No response

Technically speaking, you should use DataLoader to work with DataPipe to enable shuffling with different randomness of every epoch. But, there are a few bugs in DataLoader and map.SequenceWrapper, I will send a patch to fix it.
Besides, it seems the behavior of MapDataPipe is different from IterDataPipe:

IterDataPipe.shuffle would shuffle lazily during iteration: shuffle order is changed across epoch
MapDataPipe.shuffle would shuffle at the construction time: shuffle order is fixed
We need to find a way to align them together

Could you please try to use IterDataPipe via dp.iter.IterableWrapper as a temporary workaround?

This is what I have now:
X = torch.randn(200, 5)
dpX = dp.iter.IterableWrapper(X)
dpXS = dpX.shuffle(buffer_size=X.shape[0])
dl = torch.utils.data.DataLoader(dpXS)
for _ in range(5):
    for i in dl:
        print(i)
        break

It seems that to emulate the old DataLoader's shuffle=True behavior I'll need to pass in the size of the dataset explicitly into the shuffle() method.

The shuffle for IterDataPipe has to be a buffered shuffle as there isn't a concept of indices.


wasm-pack build --target web panics for hello_world from a checked out repository

Describe the Bug
wasm-pack build --target web on the hello_world example in a repository checkout gives a panic:
[INFO]: 🎯  Checking for the Wasm target...
[INFO]: 🌀  Compiling to Wasm...
    Finished release [optimized] target(s) in 0.21s
[INFO]: ⬇  Installing wasm-bindgen...
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', crates/cli-support/src/descriptor.rs:195:15
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::panicking::panic_bounds_check
   9: wasm_bindgen_cli_support::descriptor::Descriptor::_decode
  10: wasm_bindgen_cli_support::descriptor::Descriptor::_decode
  11: wasm_bindgen_cli_support::descriptor::Descriptor::_decode
  12: wasm_bindgen_cli_support::descriptor::Descriptor::_decode
  13: <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T,I>>::from_iter
  14: wasm_bindgen_cli_support::descriptor::Function::decode
  15: wasm_bindgen_cli_support::descriptor::Descriptor::_decode
  16: wasm_bindgen_cli_support::descriptors::execute
  17: wasm_bindgen_cli_support::Bindgen::_generate
  18: wasm_bindgen::main
  19: std::rt::lang_start::{{closure}}
  20: std::panicking::try::do_call
  21: __rust_maybe_catch_panic
  22: std::rt::lang_start_internal
  23: main
Error: Running the wasm-bindgen CLI
Caused by: failed to execute `wasm-bindgen`: exited with exit code: 101

Steps to Reproduce

checkout https://github.com/rustwasm/wasm-bindgen
got to examples/hello_world/
execute wasm-pack build --target web

Expected Behavior
wasm-pack build --target web should not panic.
Actual Behavior
wasm-pack build --target web panics.
Additional Context
There is no panic, if only the hello_world directory is downloaded, instead of checking out the repository.

Thanks for the report! This is an issue of mismatch between the git crate and the crates.io CLI. The bug here is in wasm-bindgen itself and is tracked at https://github.com/rustwasm/wasm-bindgen/issues/1227.
To build the examples out of the wasm-bindgen repository the best way to do it is to copy them out and then wasm-pack build should work.

Thank you.


Update question_of_month.yml

@MarkAckert :  when you have a chance, please review this change  TY!


Add translations for Windows GUI theme menu

Since the theme switching menu for dark mode was implemented by me, I thought I should try adding translations for it too. This PR implements translation for the newly added menu items and adds 2 languages as a start so that translators can contribute. Hope I am doing this correctly.

Corrected to match Microsoft Terminology.

I changed the identifiers in the translation files because "theme" is too much generic and may conflict with something else in the future.
I changed the English wording for "system" (using the one from VS).
I added the French translation.
Please double-check then pull then force push if you wish to have the "verified" tag on the patch.

Should be okay. I'm not good in Mandarin and Korean so someone can correct it in the future if it is not perfect.

@JeromeMartinez Tested the latest dev build and encountered a bug:

Steps to reproduce:

Open MediaInfo
Click Language on the menu bar
Select any language including English

Possibly caused by files in %APPDATA%\MediaInfo\Plugin\Language not updated automatically on MediaInfo update? Changing language via the Preferences window works though.

Confirm that deleting the entire %APPDATA%\MediaInfo directory fixes the above.

It happens sometimes but no clear indication about when, it is not due to your patches, it was the case sometimes in the past too.

It happens sometimes but no clear indication about when, it is not due to your patches, it was the case sometimes in the past too.

Very easy to reproduce. Just delete %APPDATA%\MediaInfo\Plugin\Language\en.csv. Now everytime select en in Preferences window or menu drop-down, everything will disappear. However, after close Preferences window it will be back to normal.
This is because there are two copies of translation files. One in C:\Program Files\MediaInfo\Plugin\Language and another in %APPDATA%\MediaInfo\Plugin\Language. The one in %APPDATA% is not updated when MediaInfo is updated so new translations that are updated after the user first install will not be there. It seems MediaInfo use the one in %APPDATA% when changing languages but use the other updated one in other cases.
So at the moment, for updated translations to work properly, user has to manually purge the entire %APPDATA%\MediaInfo after every MediaInfo update. It will then auto generate with latest changes.

The one in %APPDATA% is not updated when MediaInfo is updated so new translations that are updated after the user first install will not be there. It seems MediaInfo use the one in %APPDATA% when changing languages but use the other updated one in other cases.

If it is not too much to ask (I am aware that you already done a lot), it would be great if you take some time for fixing that. We are too much late on other things we promised that we can not focus on that now.
%APPDATA%\MediaInfo\Plugin\Language was not wanted, if I remember correctly the copy was more or less done due to access rights after WinXP for templates (the user can edit them in the UI, so it needs to be in a writable dir, but the languages are not) but if it can be avoided it is better.

The one in %APPDATA% is not updated

but a hot fix like updating this one after another install is fine too, and we would work on a better fix... Later.

but a hot fix like updating this one after another install is fine too, and we would work on a better fix... Later.

Cannot understand how/why MediaInfo creates copies of the language files and how it decides when to read/write to which folder. All looks very complicated after a quick look.
For a quick/easy workaround, I suggest checking for existence of %APPDATA%\MediaInfo\Plugin\Language on first start-up after version change and if exists, overwrite all the files with ones from install directory. Is this okay? If yes then I'll see if I can implement this.

Like this:
    //Load Configuration
    if (Prefs->Config_Load()==2) //Showing options if no config
    {
        #ifndef MEDIAINFOGUI_PREFS_NO
        TPreferencesF* PreferencesF=new TPreferencesF(this);
        PreferencesF->Cancel->Enabled=false;
        PreferencesF->ShowModal();
        delete PreferencesF;
        Prefs->Config_Load(); //Again...
        #endif //MEDIAINFOGUI_PREFS_NO

        //Quick temporary fix for translations after an update
        //----------------------------------------------------------------------------------------------
        //Copies updated language files from install folder to appdata folder if appdata folder exists,
        //overwriting existing files
        //----------------------------------------------------------------------------------------------
        namespace fs = std::filesystem;
        fs::path appdata_path = std::getenv("APPDATA");
        fs::path language_path = appdata_path / "MediaInfo\\Plugin\\Language";
        ZenLib::Ztring BaseFolder;
        BaseFolder=Application->ExeName.c_str();
        fs::path language_source_path = BaseFolder.substr(0, BaseFolder.rfind(__T("\\"))).c_str();
        language_source_path = language_source_path / "Plugin\\Language";
        if (fs::exists(language_path) && fs::is_directory(language_path)) {
            try {
                for (const auto& entry : fs::directory_iterator(language_source_path)) {
                    fs::path current = entry.path();
                    fs::path target = language_path / current.filename();
                    if (fs::is_regular_file(current)) {
                        fs::copy_file(current, target, fs::copy_options::overwrite_existing);
                    }
                }
                //ShowMessage("Success updating translations!");
            } catch (const fs::filesystem_error& e) {
                ShowMessage("Error updating translations in %APPDATA%!");
            }
        }
        //----------------------------------------------------------------------------------------------
    }

Cannot understand how/why MediaInfo creates copies of the language files and how it decides when to read/write to which folder.

The template directory in the same top level directory "Plugin" needs to be writable (edit by the program in preferences).
20 years ago, the program files directory was writable.
It is no more (for good reasons).
There was a quick hack (I don't remember who / when / how) for copying the to level directory "Plugin" from the now read only dir to the writable dir. Duplicate is not necessary, it was not wanted.

All looks very complicated after a quick look.

Reason we always postoned such dev to later, which is not good :(.

For a quick/easy workaround, I suggest checking for existence of %APPDATA%\MediaInfo\Plugin\Language on first start-up after version change and if exists, overwrite all the files with ones from install directory. Is this okay? If yes then I'll see if I can implement this.

Such hot fix is fine for me if it works for new installs (no dir) as well as old installs (existing dir).
A better fix could wait.


Ionic Deskop: Components that look good at scale

Feature Request
Describe the Feature Request
I had a conversation with Mike in Slack and we were chatting about the current state of the components at PWA scale.
In my opinion, the current implementation of Material doesn't scale well to desktop size and looks clunky. I'd respectfully submit the following UI libraries as inspiration for future desktop components:

Vaadin's Web Components: https://expensemanager.demo.vaadin.com/
Microsoft's Fabric: https://developer.microsoft.com/en-us/fabric
Atlassian's AtlasKit: https://atlassian.design/guidelines/product/overview.

Ionic's hybrid mobile components are very good. I'd like to see the desktop components be just as good and I think it would highly benefit all involved.

Alibaba's Ant design: https://ng.ant.design/
Specs are in Chinese, translate with Chrome.


github integration

As this project plans to track payments related to issues and pull requests, standard git is not enough. These are add on features by services like github and bitbucket.
Since github is the biggest, that's where we'll start with integrations. Similarly, this seems to be the most popular of the github python clients: https://github.com/sigmavirus24/github3.py

[ ] Issues checked against ledger for status i.e. unassigned, closed, not present in ledger
[ ] PRs checked against ledger for status i.e. closed
[ ] Able to listen for command words in issues and commits. Example to implement: 'closes' keyword
in commit also updates ledger entry.
[ ] Make actions on github when local activity happens like guild creation per https://github.com/deginner/gitguild/issues/3

I tried to add specific deliverables related to github in this task. In truth, the reason it has a big bounty is the vagueness. Aside from syncing #6 and storing the data #3, it just seems like there is a lot of possibility to integrate the functionality github adds in issues, PRs and more. Please be creative and use your judgement on what the most interesting functionality is for the size of the bounty.

Git Guild Bounty Program

Total
Dev
Sales
Reporter
Tester(s)
Maintainer
Documenter

N/A
assignee(s)
N/A
@isysd
@isysd, @d3brouille
@isysd
@d3brouille

$1,741.67
$1,100.00
$0.00
$91.67
$366.67
$91.67
$91.67

Closing this as the specifics described are no longer relevant to the workflow. PRs and issues on github are not a necessary part of this software.


KEP-4247: make QHint enabled by default

Description

https://github.com/kubernetes/enhancements/issues/4247 is going to be enabled by default at 1.32.
Issue

KEP: https://github.com/kubernetes/enhancements/issues/4247

/sig scheduling

Upstream change merged: https://github.com/kubernetes/kubernetes/pull/128472

/approve


feat(Banner): Migrate to Variance + ColorModes

Overview

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

🚀 Styleguide deploy preview ready!https://607f9bc4ceed0e61fed9f602--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-illustrations@0.10.3-alpha.00a4e8.0@codecademy/gamut-kit@0.3.39-alpha.00a4e8.0@codecademy/gamut-labs@14.0.1-alpha.00a4e8.0@codecademy/gamut-styles@9.5.4-alpha.00a4e8.0@codecademy/gamut-tests@2.3.15-alpha.00a4e8.0@codecademy/gamut@32.0.1-alpha.00a4e8.0@codecademy/konamimojisplosion@0.2.15-alpha.00a4e8.0@codecademy/markdown-overrides@0.5.27-alpha.00a4e8.0@codecademy/styleguide@36.0.1-alpha.00a4e8.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60804a65fbce2c1242b25a94--gamut-preview.netlify.appDeploy Logs


How to update hyperterm

Sorry, I'm a beginner. How can I update hyperterm? Thank you!

Hi there! What system are you on? OSX HyperTerm supports Automatic Updates and so you should see a notification from your HyperTerm window when there is an update available (so long as you're on a version that supports it. >4.x I believe.)
Also make sure that you aren't on the latest version of HyperTerm, otherwise there is no updates to update to.
If you're wondering how to take advantage of all the merges and updates to the repository, you can clone the repo and build the app yourself to have the latest features; but these aren't officially released yet and so may contain bugs.
If there's anything more you'd like to know, please feel free to ask! Alternatively, you can join the community channel at https://zeit.chat and ask the community there any questions you may have. 😄

@CodeTheory Your patient andswer makes me surprised, It helps me a lot.

I'm glad! I aim to assist. 😄

How can I disable automatic updates?

Why would you disable automatic updates?


add vectune link at AI section

Hi. I'm from the Kinic dev team and would like to add a link to Vectune, an open-source library, for use with KinicVectorDB.

@ClankPan you have to reply to the message in the CLA with the suggested text so I can merge this :) great work btw