[Test UI] Request: Options overload for CreateTestItem

Issue Type: Feature Request
@connor4312
Since the controller createTestItem method is used a lot, there should be an options-style overload for easier usage and intellisense. Here's my implementation in my code today, if it were part of the interface the controller as the first parameter would not be necessary.
/**
 * Options for creating a managed test item
 *
 */
export interface CreateTestOptions {
    /** Uniquely identifies the test. Can be anything but must be unique to the controller */
    id: string
    /** A label for the testItem. This is how it will appear in the test explorer pane */
    label: string
    /** Which test item is the parent of this item. You can specify the test controller root here */
    parent: TestItem<any>
    /** A resource URI that matches the physical location of this test */
    uri?: Uri
    /** Custom data that never leaves this test */
    data?: any
}

/** Overload of {@link TestController.createTestItem} that accepts options */
export function createTestItem<TChild>(testController: TestController, options: CreateTestOptions) {
    testController.createTestItem<TChild>(
        options.id,
        options.label,
        options.parent,
        options.uri,
        options.data
    )
}

VS Code version: Code - Insiders 1.58.0-insider (9744231fc12f1aed21089180b3f0394d694bd2a2, 2021-06-23T05:13:08.071Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Ryzen 7 4700U with Radeon Graphics          (8 x 1996)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.36GB (4.68GB free)

Process Argv
--crash-reporter-id 4453efaa-0821-4555-88e2-3de8bad9109e

Screen Reader
no

VM
0%

Extensions (31)

Extension
Author (truncated)
Version

emojisense
bie
0.8.0

markdown-checkbox
bie
0.1.3

vscode-opennewinstance
chr
0.0.7

bracket-pair-colorizer-2
Coe
0.2.1

esbuild-problem-matchers
con
0.0.2

gitlens
eam
11.5.1

filter-lines
ear
1.0.0

remotehub
Git
0.10.1

vscode-pull-request-github
Git
0.27.1

todo-tree
Gru
0.0.213

vscode-test-explorer
hbe
2.20.4

vscode-drawio
hed
1.5.0

change-case
hjd
1.0.2

git-graph
mhu
1.30.0

remote-containers
ms-
0.184.0

remote-ssh-nightly
ms-
2021.5.29700

powershell-preview
ms-
2021.6.1

test-adapter-converter
ms-
0.0.11

vscode-paste-image
mus
1.0.4

indent-rainbow
ode
7.5.0

docthis
oou
0.8.2

quicktype
qui
12.0.46

vscode-yaml
red
0.20.0

vscode-sort-json
ric
1.20.0

vscode-inline-values-powershell
Tyl
0.0.5

errorlens
use
3.2.7

vscode-icons
vsc
11.5.0

codetour
vsl
0.0.56

gistfs
vsl
0.2.9

gitmoji-vscode
Vtr
1.0.7

better-align
wwm
1.1.6

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
vspre833:30321513
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158:30321503
pythonvsuse255:30319630
vscorehov:30301224
vscod805:30301674
pythonvspyt200:30323110
vscextlang:30310088
vsccppwtct:30312693

What the API usually does is to use dedicated arguments for mandatory field and an options bag for the rest, so it could be
createTestItem(id, label, parent, options?: { uri?, data? }): TestItem

The idea behind is to make mandatory properties more important and to give them more weight

@jrieken the other point of the options bag in this case is that since it is an interface, it is easy to bring in JSON from an external tool with the same properties and cast it to the interface rather than having to unroll those properties for the constructor. I am a TypeScript novice so perhaps there is a better way if I have an external tool generating "test items" and outputting them to JSON?

It sounds like a very specific case that you have. The options bag might be working best for you but we have to look at this from the API consistency point of view and ask yourself if this createXYZ-function is a good fit wrt to similar cases.

With https://github.com/microsoft/vscode/commit/6a76c62232208f54bc85f22572013b382e39cf9e we're down to only one optional property, so I don't think it's worth making a bag of them at this point.


lisa.tests.hotplug: Add number of missing online CPUs metric

This metric is redundant with the list of CPUs that are online, but can be
easily plotted, unlike the list of CPUs.

@valschneider updated with the metrics you suggested


Add missing tags for ClearChat and UserNotice

Type: Improvement
Fixes: #308
While rewriting my chat logger from tmi.js to Twurple, I noticed that some documented and undocumented tags were missing.
PS: This is my first GitHub contribution and PR and I hope I respected your dev style (some code I did not understand so I am leaving it as is)

Thank you for the feedback I will rewrite it tomorrow 😃


Automate deleting old charts and updating dependencies

Summary

When trying to manually deploy a new 2i2c hub, I ran into a bug caused by our rename from base-hub to basehub from some time ago and the presence of an outdated chart with the old name.
To prevent this from repeating, when manually deploying a hub, we should automatically:

if there's a version mismatch

delete the charts/ dir

run helm dep up
continue deploying the hub/s

OK, this one has bitten me again I am looking at it a little bit more closely...
The first item is proposing:

if there's a version mismatch
delete the charts/ dir

When I look into the helm dep list in my local repo for the basehub and daskhub charts:
helm dep list
NAME      	VERSION	REPOSITORY                              	STATUS
jupyterhub	1.1.3  	https://jupyterhub.github.io/helm-chart/	wrong version

helm dep list
NAME        	VERSION	REPOSITORY                              	STATUS
basehub     	0.1.0  	file://../basehub                       	wrong version
dask-gateway	0.9.0  	https://dask.org/dask-gateway-helm-repo/	ok

This is great because we see there is a wrong version!
But if I try to get the output as json
helm dep list --output json
Error: unknown flag: --output

Buuu...
And a big PR for that seems to be stale: https://github.com/helm/helm/pull/8077
Since we are unconditionally updating the support chart here: https://github.com/2i2c-org/pilot-hubs/blob/master/deployer/hub.py#L109
What do you all think about just fetching the basehub and daskhub charts just before performing the helm upgrade without checking any status/version? That is what we are essentially doing on the CI: https://github.com/2i2c-org/pilot-hubs/blob/master/.github/actions/deploy/action.yml#L14 (although we start from a clean state there).

What do you all think about just fetching the basehub and daskhub charts just before performing the helm upgrade without checking any status/version?

I think it's an improvement over status quo. Unfortunately it just adds a lot of time to each deploy, slowing down testing...

I think it's an improvement over status quo. Unfortunately it just adds a lot of time to each deploy, slowing down testing...

The alternative would be to parse that output somehow to prevent unneeded updates... maybe ugly but a good enough compromise?

Just a quick note that the face we have a few "I've wasted a few hours being bitten by this" responses here makes me feel like this one is worth prioritizing. Is this one of those situations like "we collectively discuss and spend 4 hours now in order to save ourselves 30 hours later"?

this one is worth prioritizing.

I agree. It is something to should pick up sooner than later, IMHO.

Is this something that we could automate at all with a GitHub Action that runs on a CRON job or something? Is there config in this repo that could tell us if a hub's chart is out-dated? Or is this something that we'd need to build in as a check in the deploy script itself?

Or is this something that we'd need to build in as a check in the deploy script itself?

I think that is the case...

I think it's an improvement over status quo. Unfortunately it just adds a lot of time to each deploy, slowing down testing...

The alternative would be to parse that output somehow to prevent unneeded updates... maybe ugly but a good enough compromise?

I'm personally +1 on just adding helm dep up straight into the deployer and eating the extra time. It's not like we're talking about a 10s second script increasing to minutes long, more like a minutes long script is gonna take a few more minutes. I'm already in the habit of brewing some tea during deploys anyway ☕ 😁

Sorry I wasn't clear earlier - +1 to adding helm dep up, but hopefully we can keep this open until we do it conditionally too :)

I do want to investigate why deploys take minutes though - it has always bugged me. The process should be definitely much faster, given the actual work helm is doing.

OK I've updated the top comment with what I think are the next steps here 👍

I opened https://github.com/2i2c-org/pilot-hubs/pull/705 to address the first action point

#705 is already merged but keeping this one open for the conditional check.

Should we re prioritize this issue to be lower now? The underlying problem is now resolved, though the conditional would help us save time, so i guess the question is: how annoying is it to have to wait the extra time for each deploy?

I'm +1 as reprioritising as low impact. I personally do not find the extra time annoying.


Better named colour check - Fixes #24

Fixes #24
'black' was coming back falsey and being read as invalid.
Now this checks for the property rather than the value being truthy.
I'm not familiar with Mocha but maybe we could loop through the colour list and check they all work in the tests?

Thanks for the PR. Seems like a reasonable check, merging.


Widgets for default values

The input nodes should have widgets which sets/edits the default value of that node.
When collapsing, we should use type information of collapsed node inputs and set the types in its definition in the code (the one-line version, like collapsed1 arg1:Number = .... Then, this type should be used to match proper widget for input's value.
If there's no value set in the code, we should match a widget the same way as for the arg placeholder.

Refinement notes:

Special widget input for argument + special widget displaying arg, type and placeholder for default value
the default arg widget may accept only single line code.

Refinement notes, vol. 2:

The selection of require/default is very unusual, unless we remove “default” from the UI - then it’s just a selection with additional “required” option (and default at least if there is no other option)


Lost regions in the TYR DB

For example, Japan has a subdivision in the original GADM DB.
https://gadm.org/maps/JPN_1.html
And we have only World > Oceania > Japan > Japan > Japan > Tokyo

Argh, it's not lost; it's the only region in Oceania for some reason...


note the new api version

mainly the update will affect the permission system and also add error types (yay finally!!!!)

blocked until it'll be on production

alright.


Problem about installing freqencoder and gridencoder

我在生成core/lib/freqencoder(gridencoder)的时候发生了错误，两个encoder的报错信息相似，报错来自于C/C++头文件，最终导致ninja运行时的某一个步骤无法运行。我已经将两个报错信息导出到了本Issue的附件中。使用的系统是Ubuntu 22.04。
An error occurred when I am buildfing TeCH/core/lib/freqencoder(gridencoder). The error of them are similiar. It seems that the error is in a header file of C or C++. Finally it causes ninja stop with failure in subcommand. In the attachments of this issue is their error. My OS is Ubuntu 22.04. Your prompt reply would be greatly appreciated. Thank you!

Errors:
freqencoder-install-error.log
gridencoder-install-error.log

It seems to be a problem caused by the incompability between CUDA and my compiler, having nothing to do with TeCH. I'll check it and close this issue if I solved this problem.

I reversed my gcc and g++ version to 9 and now the problem was solved.


[C++] util_avx2.cc has been moved to compute but still #include acero headers

Describe the bug, including details regarding any error messages, version, and platform.
It looks like https://github.com/apache/arrow/issues/35115 moved util_avx2.cc from acero/ to compute/ but forgot to update #include lines. This was discovered while building Apache Arrow with a sandboxed build system where the entire acero/ is not visible if ARROW_ACERO=OFF.
Component(s)
C++

This should be included in 13.0.0?


Static link with ios_application in the rules_apple

@sergeykhliustin Have you tested integrating with ios_application in the rules_apple? I am getting an ObjcLink issue when trying to integrate an Objective-C apple_framework with a Swift application using rules_apple

I got the reason Swift doesn't support static link library here https://stackoverflow.com/questions/41210249/why-do-we-use-use-frameworks-in-cocoapods. So we must use the dynamic link (similar to use_framework! in the Cocoapods.

The reason seems more complex since I am deep into this blog. The modern Swift supports static links if we have the modular headers  https://blog.cocoapods.org/CocoaPods-1.5.0/
I will re-open this issue and also continue to investigate this. If anyone is more savvy about please discuss it.

I downgrade Bazel 7 to the bazel 6.
Use ios_application from rules_ios instead of rule_apple

It seems everything works well now 🙏


needs to be called twice to execute the undo correctly. So does the "redo"

I found out when I used demo，It's probably a bug.

Hi. Yes I'm aware of the problem. I'm currently working on fixing a few issues and improve the library.


Update the terms and conditions form page

Some links were broken and an error message was missing.
https://ukgovernmentdfe.slack.com/archives/C016H89QSCA/p1614698205002800

Review app deployed to https://teaching-vacancies-review-pr-2996.london.cloudapps.digital


Support dir-name for scala testSets

@tkrullmann do I need to sign a CLA or anything?

I ran the tests.  I confirmed with the current PR that they run cleanly.
I also confirmed that they fail if:

I remove the apply plugin in the scala test.
I remove the scala plugin check from the main file (the MissingPropertyException you expected).


Question: Usage across multiple processes?

Does this library support sharing a sqlite database across multiple node processes?

please explain what you would like from me
On Feb 3, 2017 10:33 PM, "Amila Welihinda"<EMAIL_ADDRESS>wrote:

Does this library support sharing a sqlite database across multiple node
processes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tgriesser/bookshelf/issues/1512, or mute the thread
https://github.com/notifications/unsubscribe-auth/AYUM0LpbgK3fmm5geYcM5Ev2O4eHwjOaks5rZBvAgaJpZM4L3D7_
.

I think it should, since it doesn't lock the file in any way.


Updated preview video

'nuff said

Thanks Paul. Seems a bit too fast - can you try 2.5 seconds...that's what I've used before (should have mentioned this).
Also, Chrome won't play the current one on lbry.com for me at time...I have to refresh a bunch. Any ideas?

Chrome probably has the original video cached. I'll update when I get to my desktop again.

Updated the video

Thanks, looks good! Let's see how it looks on lbry.com now.


Python wrapper: undo change package accumulators

because we would otherwise end up with broken wrappers because PATH and
PTYHONPATH weren't set.
Partially reverts 8d76effc178747f0c8f456fe619c1b014736a6af.
cc @Ericson2314

I've pushed this to staging.

Oh wow, I meant to do [ -z ] or &&. Sorry for the breakage / I hope this is the last of it.


Kim edit: acm-lightning-components.adoc

Kim edit: acm-lightning-components.adoc

PR to address these changes: https://github.com/mulesoft/docs-api-community-manager/pull/95

Resolved in https://github.com/mulesoft/docs-api-community-manager/pull/95 .


RFE: Move Contour and Envoy image configuration options to Contour.Spec from command line

Please describe the problem you have
I would like to request that --contour-image and --envoy-image command options:
https://github.com/projectcontour/contour-operator/blob/7e5ae24ae7234ea9d539ff6468c7c4623c045b9c/cmd/contour-operator.go#L34-L37
should be moved in ContourSpec. https://github.com/projectcontour/contour-operator/blob/7e5ae24ae7234ea9d539ff6468c7c4623c045b9c/api/v1alpha1/contour_types.go#L61

use case 1)
The configuration should be centralized.

use case 2)
When we deployed multiple Contour CR, we have to use same images among all Contour CRs. It is not possible to test a new Contour or Envoy image by one of Contour CRs.

@nak3 PTAL at https://github.com/projectcontour/contour-operator/issues/55 for background on the current version management approach. I need to think through the different approaches for supporting the blue/green upgrades. I'll put together some ideas and update this issue. cc: @Miciah

Hey @nak3, can you explain a bit more about case 2 above? Are you wanting to smoke test the new version before rolling it out? Or do you want to stage the rollouts such that you don't upgrade all your instances at the same time?

@danehans Sure! Thank you.
@stevesloka I wanted it for a smoke test originally. When I fixed an operator bug, I wanted to verify the Contour image quickly but that needs upgrade of all Contour images.
With said, I believe that there are some users who want to stage the rollouts.

I understand. Thank you. I am closing this.


enhancement Sync stats across FE cluster after analyze

Proposed changes

Before this PR, if user connect to follower and analyze table, stats would not get cached in follower FE, since Analyze stmt would be forwarded to master, and in follower it's still lazy load to cache.After this PR, once analyze finished on master, master would sync stats to all followers and update follower's stats cache
Load partition stats to col stats

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


feat(html/minifier): improve the remove_redundant_attributes option

Description:
Due https://github.com/kangax/html-minifier/issues/1075
A lot of CSS frameworks use (and not only):
input[type=text] {
  /* styles */
}

So it is not safe to remove them by default, anyway I implemented the safe mode - it will remove:

deprecated attributes (they doesn't used in CSS almost always, expect very old frameworks, which already doesn't supported)
SVG attributes, it  is common ptractide don't use them in CSS
attributes from metadata elements, because they will not be rendered

BREAKING CHANGE:
Yes
Related issue (if exists):
No

@kdy1 Done, for another enum too :+1:

@kdy1 Fixed again :smile:


Text wraps for items in the list of filters

With some terrible languages (such as French :) the double line spacing combined with end-of-line wrapping is problematic, as some lines are fairly long and, when they wrap, it's hard to visually distinguish items from "previous items that were wrapped":

The dropdown menu has been improved (in master):


Cookie Repository Still Blocks Under High Contention

Updating a cookie over and over again on multiple threads blocks too often inside the NonBlockingCookieStore, which of course shouldn't happen given the name of the class. Need to figure out why this happens and fix it.
The real culprit is the fact that they default client configuration will always add "global" cookies to the store for each request. One solution is to have a tiered version of the cookie store which adds these globals to a temporary map and thus removes all contention. A second is to reconfigure the concurrent hash map and/or update more carefully during the NonBlockingCookieStore.add method.

This is fixed in 0.14.1


different results on mobile

Why the examples in the demo page give different results on desktop and mobile?
https://jariz.github.io/vibrant.js/
You can try it out also with the Chrome Dev Tools, just make the Viewport with width less than 1200.

VibrantJS is not node-vibrant. node-vibrant is a fork and continuation off of VibrantJS and as a result tests would need to be done with this library itself


Update of xunit.runner.visualstudio - fixes inability to run tests side VS Test Explorer.

For deatils check: https://github.com/dotnet/cli/pull/6918

Thanks for this, and sorry it took so very long to respond. I actually included this as part of #39. I normally use NCrunch, which doesn't require the runner package, which is why I missed this.


hide VNet implementation behind cargo feature

I have a problem with mDNS package on old armv5te platforms
Armv5te doesn't support AtomicU64 and AtomicI64 types
https://doc.rust-lang.org/std/sync/atomic/#portability
this types are using in "vnet" mod.. Can we hide it behind cargo feature or change it to AtomicU32 and AtomicI32 for support this platform?
mDNS package doesn't use vnet module but has this dependency

thanks for reporting this issue. Will fix this by using cargo feature for util crate.

@rainliu can we use this crate instead for getting network interfaces https://docs.rs/pnet/0.8.1/pnet/index.html

@chertov, I just upgrade  webrtc-util to v0.1.19  in crates.io.
You can update  mDNS crate's dependent util version to v0.1.19 in order to disable vnet feature.


Consider switching away from rouille

Crate
ibc-relayer-rest, ibc-telemetry
Summary
The rouille crate imposes an unnecessary restriction on its time dependency, holding back useful changes.
Problem Definition
The crates depend on rouille, which pins its dependency on time to =0.3.2: https://github.com/tomaka/rouille/issues/246
This will come into conflict with changes made in https://github.com/informalsystems/tendermint-rs/pull/1030 and has already caused a rollback in https://github.com/informalsystems/tendermint-rs/issues/1047.
Proposal
Switch to warp, or any other suitable web service framework without dependency issues.
Acceptance Criteria
The problem is resolved upstream, or this project removes the rouille dependency.

For Admin Use

[x] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

With #1665 in, rouille will be the last obstacle to fixing #1478.


TypeError: Cannot read property '_location' of null

Basic info:
NodeJS version: v6.10.3
jsdom version<EMAIL_ADDRESS>Minimal reproduction case
const jsdom = require("jsdom");
const { JSDOM } = jsdom;
const window = (new JSDOM(``, { runScripts: "outside-only" })).window;

window.setTimeout(function() {
        window.close();
        window.setTimeout(function () {
                window.location.href = "hello";
        }, 300);
}, 1000);

In browsers after window.close(); all pending timeouts are cleared and new ones are not set up.

Great repro code, thanks! I will investigate this as soon as I am able to.


Missing code of scheduling algorithms

Hi Authors,
Thanks for your great efforts on this impressive work. But I did not find the code of compared scheduling algorithms under alg/scheduler/ folder, which seems should be supported (in run/exp_cluster/batch_run.sh).
Can you please provide these baseline codes?
Thanks!

Thanks for your interest in this work. We are currently developing a benchmark for existing DL schedulers. This still requires half of year based my expectation. We will try our best to release this benchmark at the end of this year. This benchmark will contain a full suite of Chronus's baselines and other well-known DL schedulers.

Thanks for your reply. That sounds will be an amazing project, and I'm looking forward to your benchmark for DL schedulers.


Add rad CLI to homebrew

https://radapp.dev/getting-started/#install-rad-cli
Currently we only support installing via curl.
AB#4434

We're public now!

Adding a note to this issue that @lechnerc77 set this up for us in an "unofficial" capacity. This is helpful progress, and it might be something we want to take over officially and add automation.
https://github.com/lechnerc77/homebrew-rad
We could also document the tap that @lechnerc77 created for us as an intermediate step.
Removing triage tag so this get looked-at again.


How to make Repe support image as input if using llama3 as base model?

We see huge demand for text-to-image honesty check. Please help us provide such capability

@poa010101 have you made progress in this direction?


Promotion Prod Tasks

[ ] Add the Controller Helm chart to EKS-A release Bundle
[ ] Infra to push Packages to Prod
[ ] Infra to build Bundle in prod

Eric did first task.
2nd and 3rd are in https://github.com/aws/eks-anywhere-packages/pull/171


Compiling on Debian Buster, latest Buster gcc, shows warnings

1.41.0:

Linux juvat3 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux:

gcc (Debian 8.3.0-6) 8.3.0

Partial log showing warnings:
compiling 3rdparty/libuv/src/unix/core.o
3rdparty/libuv/src/unix/core.c: In function 'uv__accept':
3rdparty/libuv/src/unix/core.c:88:22: warning: implicit declaration of function 'accept4'; did you mean 'accept'? [-Wimplicit-function-declaration]
 # define uv__accept4 accept4
                      ^~~~~~~
3rdparty/libuv/src/unix/core.c:498:14: note: in expansion of macro 'uv__accept4'
     peerfd = uv__accept4(sockfd, NULL, NULL, SOCK_NONBLOCK|SOCK_CLOEXEC);
              ^~~~~~~~~~~
3rdparty/libuv/src/unix/core.c: In function 'uv__dup2_cloexec':
3rdparty/libuv/src/unix/core.c:1034:7: warning: implicit declaration of function 'dup3'; did you mean 'dup2'? [-Wimplicit-function-declaration]
   r = dup3(oldfd, newfd, O_CLOEXEC);
       ^~~~
       dup2

compiling 3rdparty/libuv/src/unix/pipe.o
3rdparty/libuv/src/unix/pipe.c: In function 'uv_pipe':
3rdparty/libuv/src/unix/pipe.c:393:7: warning: implicit declaration of function 'pipe2'; did you mean 'pipe'? [-Wimplicit-function-declaration]
   if (pipe2(temp, flags))
       ^~~~~
       pipe

On Sun, May 9, 2021 at 03:44 Ben Noordhuis @.***> wrote:

@tbrowder https://github.com/tbrowder Libuv's build scripts build with
-D_GNU_SOURCE. Looking at the output you posted, I suspect the project
you're trying to compile is using its own build script. Try getting in
touch with them.

Thanks. I’m keeping the using project (https://github.com/MoarVM/MoarVM)
updated on the issue. I'll pass the info on.


HTTP proxy support

Would you like to work on this feature?
yes
What problem are you trying to solve?
kube-client crate currently supports only SOCKS5 proxies in the kubeconfig (config.proxy_url, HTTP[S]_PROXY/http[s]_proxy env variables). Relevant code starts here. However, proxy can also use the regular HTTP protocol.
Describe the solution you'd like
Inspect scheme of the proxy URI and optionally wrap the base connector with hyper_proxy. Hide it behind a new feature http_proxy (name suggestions welcome).
Found some past discussions on this:
https://github.com/kube-rs/kube/discussions/1010
https://github.com/kube-rs/kube/pull/837
Describe alternatives you've considered
None so far
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-client

I like the proposal of this in theory because I would also like to support it, but it has one problem practically; the proposed crate has not had a release in over 2 years.
If we were to do this, I would personally prefer to do it after the hyper 1.0 upgrade in #1351 (since we are already having to deal with infrequently updated connector libraries there and this feature would compound that). Waiting for 1.0 would mean getting a 1.0 upgrade pushed up into hyper-proxy first though.

We have implemented it in our fork, and now that the hyper 1.0 upgrade is done we shall send a PR :)


Field with discriminator on generic causes AssertionError. (1.9.0a1)

Bug
When defining a Generic, with a Field that has descriminator, filling in the type variable of the generic class fails with an AssertionError.
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.9.0a1
            pydantic compiled: True
                 install path: /home/jonathan/.pyenv/versions/3.9.5/envs/lazy-maestro/lib/python3.9/site-packages/pydantic
               python version: 3.9.5 (default, Jun  3 2021, 16:26:08)  [GCC 9.3.0]
                     platform: Linux-5.4.0-91-generic-x86_64-with-glibc2.31
     optional deps. installed: ['dotenv', 'typing-extensions']

from typing import Generic, TypeVar, Union

from pydantic import Field
from pydantic.generics import BaseModel, GenericModel
from typing_extensions import Literal

_T = TypeVar("_T")

class Success(GenericModel, Generic[_T]):
    type: Literal["Success"] = "Success"

    data: _T

class Failure(BaseModel):
    type: Literal["Failure"] = "Failure"
    error_message: str

class Container(GenericModel, Generic[_T]):
    result: Union[Success[_T], Failure] = Field(discriminator="type")

# It's the following expresison that raises the traceback below:
Container[str]

The error:
Traceback (most recent call last):
  File "/tmp/test.py", line 25, in <module>
    Container[str]
  File "/home/jonathan/.pyenv/versions/lazy-maestro/lib/python3.9/site-packages/pydantic/generics.py", line 95, in __class_getitem__
    create_model(
  File "pydantic/main.py", line 959, in pydantic.main.create_model
  File "pydantic/main.py", line 291, in pydantic.main.ModelMetaclass.__new__
  File "pydantic/main.py", line 762, in pydantic.main.BaseModel.__try_update_forward_refs__
  File "pydantic/typing.py", line 477, in pydantic.typing.update_model_forward_refs
    literal (or one of several literals):
  File "pydantic/typing.py", line 456, in pydantic.typing.update_field_forward_refs
    parameters = tuple(_type_check(p, msg) for p in parameters)
  File "pydantic/fields.py", line 735, in pydantic.fields.ModelField.prepare_discriminated_union_sub_fields
AssertionError

Thank you so much for trying out the alpha release and reporting @jonathanslenders 🙏
I opened a patch

Thanks a lot @PrettyWood for looking into this! Really appreciate your work!


Azure Key vault (AKV) integration - PART 2

Currently BAF only supports Hashicorp Vault.
Part 2 of this feature enables BAF to support Azure Key vault for ansible playbooks so that it gets loosely coupled with the playbooks.

Modify the role platforms/hyperledger-fabric/configuration/roles/setup/vault_kubernetes to add this secret (this secret will be used in helm chart to charts for the give access control of akv using a servicePrinciple)
(in shell)    KUBECONFIG={{ kubernetes.config_file }} kubectl create secret generic kvcreds --from-literal clientid={{ vault.clientid }} --from-literal clientsecret={{ vault.clientsecret }} --type=azure/kv  -n {{ component_name }}
(add when condition also for this task)
Edit task to change the path to with the cert is stored (as akv doesnt support folder structure)
Change the path like org/peer/cert/ca.crt to org-peer-cert-ca.crt
Change the roles where certs are fetched from vault as
az keyvault secret show org-peer-cert-ca.crt

For more information
https://docs.microsoft.com/en-us/cli/azure/keyvault/secret?view=azure-cli-latest#az-keyvault-secret-show

Marked as "wontfix" because we are using Vault as an abstraction for Cloud KMS and we do not want to implement the same code for different Cloud KMS. Cloud KMS can be integrated with Vault to store the unseal keys and auto-unseal of Vault similar to what we did for AWS KMS in #354 .


Update Now moves all VS Code windows to the same macOS Desktop

Does this issue occur when all extensions are disabled?:
I was reminded of this bug by updating, so it was then too late to test without extensions. Since I can't control when updates are available, it is impossible for me to experimentally verify this, but I'm almost certain that this behavior is not related to extensions.

VS Code Version: 1.59.1
OS Version: 11.4 (20F71)

Full output of "About Visual Studio Code":
Version: 1.59.1
Commit: 3866c3553be8b268c8a7f8c0482c0c0177aa8bfa
Date: 2021-08-19T11:53:52.479Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Darwin x64 20.5.0
Steps to Reproduce:

Distribute your windows across macOS Desktops according to whatever pattern you find most productive (by project, for example).
Press the "Update Now" button to update VS Code
Discover that your window arrangement has been utterly disregarded.

cc @bpasero @deepak1556

Upstream: https://github.com/electron/electron/issues/10124

Closing as per electron/electron#10124


[requirements] Update dependencies

For this task:

We need to update all the dependencies
Update django to django3.

Drop support of python2 ?

As this is a reusable app, we shouldn't drop support of Python 2 now.

Oh, Got It Now ! Thank You :smiley:

The last release of django-x509 which supports python 2 will be 0.5.0, which I released a few days ago: https://github.com/openwisp/django-x509/releases/tag/0.5.0
We can prepare the next release to be python 3 only in order to support the newer versions of django.

PS: let's leave this for the Google Code-In.

Hello can I work on it ?

It's not in GCI system for now! :smile:

Python3.5 doesn't support Django3 right ? So, I have to exclude it ?

And the requires.io shows all dependencies are up-to-date except Django

Here's Kind of summary

Some modules like six, @python_2_unicode_compatible has been removed in django3 or only supported for it's older vesrions (Older versions of Django)

Python3.5 Dosen't support Django3.0 as I mentioned in my previous comment. Please tell me If I'm not right ! I will research more on it :smile:

All dependenices are up-to-date Requires.iohttps://requires.io/github/openwisp/django-x509/requirements/?branch=master

Is anything left please tell me :smile:

@IAmAMissingColon

For six, there are 2 possible solutions mentioned here, if it's a library and you need alternatives for that library, please comment the name of the library here as well so that we can look for an alternative library.

No, we are not dropping support for all other versions of Django, only adding support.

That's great! :smile:

Regarding jsonfield, I just read : https://github.com/dmkoch/django-jsonfield/
Which makes this task a hard one I suppose! :smile:
@nemesisdesign What do you think? :smile:

For Python, we should test python 3.6 and 3.7.

For the jsonfield we can use this one: https://github.com/rpkilby/jsonfield2
Looks like a fork of the one we're using, with the difference that is actually maintained.

I have taken this up so do I have remove support for python 2?

@Weirdo914 no, we'll do that in a separate issue

let's support only django 2.2.x and django 3.0.x, on python 3.6 and 3.7.
The last python 2.7 compatible release with support for old django versions is 0.5.0.


Coveralls badge

Added a coveralls badge showcasing the amount of code in the project that has tests written for it.

This branches seems to be a bit weird because there are lots of commit history in the branch.
Could you please rebase it or create a new PR for it?

Pull Request Test Coverage Report for Build 851

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.156%

Totals

Change from base Build 849:
0.0%

Covered Lines:
967

Relevant Lines:
1304

💛  - Coveralls


Add backwards compatibility setting for token claims

Add the environment variable and then add the attributes a separate key/value pairs to the claim object outside of the vc_presented_attributes object.
Set the ver_config with optional include_v1_attributes field to default False. Then when getting the claims it decides to add the attributes individually based of this ver_config setting.
This is the claim object pulled from logs when running demo.

{
'pres_req_conf_id': 'verified-email',
'acr': 'vc_authn',
'nonce': 'Y-JG5tXSWN1nplex-k653A',
'sub'<EMAIL_ADDRESS>'vc_presented_attributes': '{"email"<EMAIL_ADDRESS>'email'<EMAIL_ADDRESS>}

Resolves #347

@jamshale before merging, just confirming you tested having an "older" release with stored configs and upgrading and it works as expected?

@esune I haven't ran any testing where I started a v1.0 and upgraded to v2.0. I can do that.

@esune Ok I tested this now and it works as expected.
The ver_config after upgrade doesn't have the include_v1_attributes field because it is optional, and it works as before. But then you can PATCH the field either as true or false and get the expected values in the attribute payload.


[DH-559] Add get event and list events endpoints

Codecov Report

Merging #445 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #445      +/-   ##
===========================================
+ Coverage    96.12%   96.12%   +<.01%
===========================================
  Files          102      102
  Lines         3197     3198       +1
  Branches       280      280
===========================================
+ Hits          3073     3074       +1
  Misses          85       85
  Partials        39       39

Impacted Files
Coverage Δ

datahub/event/views.py
100% <ø> (ø)
:arrow_up:

datahub/event/urls.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Invoking deployment process: FAILED

I'm using Ubuntu Server 14.04 LTS (HVM), SSD Volume Type - ami-3d50120d
When I do a mup deploy I get the following error:
Started TaskList: Deploy app 'formspoint-clients' (linux)
[domain-name.com] - Uploading bundle
[domain-name.com] ✔ Uploading bundle: SUCCESS
[domain-name.com] - Setting up Environment Variables
[domain-name.com] ✔ Setting up Environment Variables: SUCCESS
[domain-name.com] - Invoking deployment process
[domain-name.com] ✘ Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
//registry.npmjs.org/fibers/-/fibers-1.0.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/source-map-support/-/source-map-support-0.2.8.tgz
npm ERR! network connect ETIMEDOUT
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! System Linux 3.13.0-36-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /opt/formspoint-clients/tmp/bundle/programs/server
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! syscall connect
npm ERR! code ETIMEDOUT
npm ERR! errno ETIMEDOUT
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /opt/formspoint-clients/tmp/bundle/programs/server/npm-debug.log
npm ERR! not ok code 0
-----------------------------------STDOUT-----------------------------------
=> re-installing binary npm module 'bcrypt' of package 'npm-bcrypt'
make: Entering directory `/opt/formspoint-clients/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
  SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
  SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node: Finished
  COPY Release/bcrypt_lib.node
make: Leaving directory `/opt/formspoint-clients/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
----------------------------------------------------------------------------

Have you done mup setup?
On 2015 ජන 19, සඳුදා at පෙ.ව. 4.52 Aaron Adams<EMAIL_ADDRESS>wrote:

When I do a mup deploy I get the following error:
[ec2-....us-west-2.compute.amazonaws.com] ✘ Invoking deployment process:
FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'ec2-....us-west-2.compute.amazonaws.com,54...' (RSA) to the list of known hosts.
sudo: node-gyp: command not found
-----------------------------------STDOUT-----------------------------------
=> re-installing binary npm module 'bcrypt' of package 'npm-bcrypt'
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/226.

yes

hmm. not sure why node-gyp didn't get installed at the first.

I just created a new instance, and didn't manually install node-gyp.  Did a mup setup -- it was successful.  then did a mup deploy:
tarted TaskList: Deploy app 'application-name' (linux)
[formspoint.com] - Uploading bundle
[formspoint.com] ✔ Uploading bundle: SUCCESS
[formspoint.com] - Setting up Environment Variables
[formspoint.com] ✔ Setting up Environment Variables: SUCCESS
[formspoint.com] - Invoking deployment process
[formspoint.com] ✘ Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'domain-name.com,ip-address' (RSA) to the list of known hosts.
sudo: node-gyp: command not found
-----------------------------------STDOUT-----------------------------------
=> re-installing binary npm module 'bcrypt' of package 'npm-bcrypt'
----------------------------------------------------------------------------

Completed TaskList: Deploy app 'application-name' (linux)

very interesting. What's the ami you've used.
On Mon Jan 19 2015 at 12:05:11 PM Aaron Adams<EMAIL_ADDRESS>wrote:

I just created a new instance, and didn't manually install node-gyp. Did a
mup setup -- it was successful. then did a mup deploy:
tarted TaskList: Deploy app 'application-name' (linux)
[formspoint.com] - Uploading bundle
[formspoint.com] ✔ Uploading bundle: SUCCESS
[formspoint.com] - Setting up Environment Variables
[formspoint.com] ✔ Setting up Environment Variables: SUCCESS
[formspoint.com] - Invoking deployment process
[formspoint.com] ✘ Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'domain-name.com,ip-address' (RSA) to the list of known hosts.
sudo: node-gyp: command not found
-----------------------------------STDOUT-----------------------------------
=> re-installing binary npm module 'bcrypt' of package 'npm-bcrypt'
Completed TaskList: Deploy app 'application-name' (linux)
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/226#issuecomment-70451567.

I'll give it a try.
On Mon Jan 19 2015 at 12:27:47 PM Arunoda Susiripala <
<EMAIL_ADDRESS>wrote:

very interesting. What's the ami you've used.
On Mon Jan 19 2015 at 12:05:11 PM Aaron Adams<EMAIL_ADDRESS>wrote:

I just created a new instance, and didn't manually install node-gyp. Did
a mup setup -- it was successful. then did a mup deploy:
tarted TaskList: Deploy app 'application-name' (linux)
[formspoint.com] - Uploading bundle
[formspoint.com] ✔ Uploading bundle: SUCCESS
[formspoint.com] - Setting up Environment Variables
[formspoint.com] ✔ Setting up Environment Variables: SUCCESS
[formspoint.com] - Invoking deployment process
[formspoint.com] ✘ Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'domain-name.com,ip-address' (RSA) to the list of known hosts.
sudo: node-gyp: command not found
-----------------------------------STDOUT-----------------------------------
=> re-installing binary npm module 'bcrypt' of package 'npm-bcrypt'
Completed TaskList: Deploy app 'application-name' (linux)
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/226#issuecomment-70451567.

AMI type:
Red Hat Enterprise Linux 7.0 (HVM), SSD Volume Type - ami-99bef1a9
Red Hat Enterprise Linux version 7.0 (HVM), EBS General Purpose (SSD) Volume Type
Instance type: t2.small

Ah ah. This might be the issue. We only support Ubuntu at this moment.
On 2015 ජන 19, සඳුදා at ප.ව. 8.04 Aaron Adams<EMAIL_ADDRESS>wrote:

AMI type:
Red Hat Enterprise Linux 7.0 (HVM), SSD Volume Type - ami-99bef1a9
Red Hat Enterprise Linux version 7.0 (HVM), EBS General Purpose (SSD)
Volume Type
Instance type: t2.small
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/226#issuecomment-70501467.

But I should give it a try.
On 2015 ජන 19, සඳුදා at ප.ව. 8.07 Arunoda Susiripala <
<EMAIL_ADDRESS>wrote:

Ah ah. This might be the issue. We only support Ubuntu at this moment.
On 2015 ජන 19, සඳුදා at ප.ව. 8.04 Aaron Adams<EMAIL_ADDRESS>wrote:

AMI type:
Red Hat Enterprise Linux 7.0 (HVM), SSD Volume Type - ami-99bef1a9
Red Hat Enterprise Linux version 7.0 (HVM), EBS General Purpose (SSD)
Volume Type
Instance type: t2.small
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/226#issuecomment-70501467.

Sorry, I did an edit, I'm using Ubuntu

Okay. Got it.
On 2015 ජන 19, සඳුදා at ප.ව. 8.08 Aaron Adams<EMAIL_ADDRESS>wrote:

Sorry, I did an edit, I'm using Ubuntu
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/226#issuecomment-70502204.

Thanks!  I'm kinda stuck without this working... MUP seems to be the defacto deployment option in my situation, is there an alternative way to deploying a Meteor app to a ubuntu-trusty-14.04-amd64-server-20140927 (ami-3d50120d) instance I can use until this gets sorted out?

mup setup installs node version 0.10.33.  my local system (OSX) has node version 0.10.32 (just did a node -v on the command line).  I'm on Meteor <IP_ADDRESS>.  Does this version of Meteor use it's own copy of node?  I thought <IP_ADDRESS> used node version 0.10.33?

if you have you own Node version remove it, like:
// WARNING: If nodeVersion omitted will setup 0.10.31 by default. Do not use v, only version number.
  "nodeVersion": "0.10.32",

I had the same problem, i removed that line then run setup and deploy

@cristiandley thanks for the help,
You mean remove the reference of it from my mup.json file?  The comment above my "nodeVersion" attribute states:   // WARNING: If nodeVersion omitted will setup 0.10.33 by default. Do not use v, only version number.
So comment out my "nodeVersion": "0.10.33", attribute then?

@aadamsx  yes, also try using
"setupNode": true,

Ok,
(1) created a new Ubuntu instance
(2) assigned the Elastic IP that's linked to my domain
(3) removed "nodeVersion": "0.10.33" attribute from my mup.json file -> made sure "setupMongo": true, "setupNode": true
(4) did a mup setup -> everything installed successfuly
(5) ssh'd into my instanced and did a node -v -> v0.10.33
(6) back on my OSX box -> did a node -v -> v0.10.32
(6) did a mup deploy -> got this error again:
[domain-name.com] - Uploading bundle
[domain-name.com] ✔ Uploading bundle: SUCCESS
[domain-name.com] - Setting up Environment Variables
[domain-name.com] ✔ Setting up Environment Variables: SUCCESS
[domain-name.com] - Invoking deployment process
✘ Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'domain-name.com,55.555.5.555' (RSA) to the list of known hosts.
sudo: node-gyp: command not found
-----------------------------------STDOUT-----------------------------------
=> re-installing binary npm module 'bcrypt' of package 'npm-bcrypt'
----------------------------------------------------------------------------

So, I guess I have node v0.10.32 installed on my OSX box (and node v0.10.33 installed on my amazon instance), but this shouldn't affect my node version for Meteor version 1.2.1, am I right?

Opened a SO question on this: http://stackoverflow.com/questions/28034984/deploying-meteor-application-with-mup-to-ubuntu-ec2-instance

Why dont you give a try to DigitalOcean ?... i have 10 vm's with meteor with different Ubuntu versions and no problem at all (production level).
Take a look at my configuration file (im using mongohq):
{
  "servers": [
    {
      "host": "<IP_ADDRESS>",
      "username": "root",
      "password": "passroot"
    }
  ],
  "setupMongo": false,
  "setupNode": true,
  "setupPhantom": false,
  "appName": "test",
  "app": "/path/for/app",
  "env": {
    "PORT": 80,
    "ROOT_URL": "http://url.com",
    "MONGO_URL": "mongodb://db:dbpass@oceanic.mongohq.com:888/something"
  },
  "deployCheckWaitTime": 15
}

@cristiandley, with Digital Ocean, as far as I know, one cannot install tools on your instance -- please correct me if this is wrong. For example, I need to install PDFtk server (just a command line tool) on my instance.

I have same issue, asked question here http://stackoverflow.com/questions/28038602/meteor-up-bcrypt-error-on-invoking-deployment-process

@cristiandley, I contact DigitalOcean support... I will be abel to install PDFtk, so I might give them a try now.
Did you set up a Nginx server too, if so, do you have a reference I can follow on that?

I solved this issue.

Fix for me was to set "setupNode": true, despite Node already being set up on the server. Also commented out "nodeVersion".

@aadamsx Would you be so kind as to share how you solved this? I'm trying each of these solutions with DigitalOcean right now and nothing is working - it's always tripping on the compile of bcrypt. This usually happens when you don't have access to the compile tools but since I'm running as root... that wouldn't make any sense.
I have tried running with no nodeVersion specified, then I tried with the default. Then I tried building another server with Node preinstalled (0.12.3)... nothing. I then tried to npm install node-gyp and bcrypt - it installed but the deploy still fails.
I've run into this before - where gyp causes issues and it almost always has to do with a version clash between Node and the module that's trying to be built.
I'll keep investigating...

BTW here's my config:
{
  "servers": [
    {
      "host": "mymachine.myurl.com",
      "username": "root",
      "pem": "~/.ssh/id_rsa"
    }
  ],
  "setupMongo": true,
  "setupNode": true,
  "nodeVersion" : "0.12.4",
  "setupPhantom": false,
  "enableUploadProgressBar": true,
  "appName": "myapp",
  "app": "/Users/rob/sites/myapp",
  "env": {
    "PORT":"80",
    "ROOT_URL": "http://[my url]"
  },
  "deployCheckWaitTime": 60
}

I've tried the above with the node version specified as the default (36), no version specified, installNode : false, etc.
Here's the error I'm getting on Ubuntu 14.04 running on DigitalOcean:
-----------------------------------STDERR-----------------------------------
	R! cwd /opt/myapp/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt
	gyp ERR! node -v v0.12.3
	gyp ERR! node-gyp -v v1.0.3
	gyp ERR! not ok
	npm WARN package.json<EMAIL_ADDRESS>No description
	npm WARN package.json<EMAIL_ADDRESS>No repository field.
	npm WARN package.json<EMAIL_ADDRESS>No README data
	child_process: customFds option is deprecated, use stdio instead.
	../src/coroutine.cc: In function ‘void* find_thread_id_key(void*)’:
	../src/coroutine.cc:90:3: warning: ‘thread_id’ may be used uninitialized in this function [-Wmaybe-uninitialized]
	   if (tls == thread_id) {
	   ^
	stop: Unknown instance:
	  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
	App did not pick up! Please check app logs.
	-----------------------------------STDOUT-----------------------------------
	src/libcoro/coro.o
	  SOLINK_MODULE(target) Release/obj.target/fibers.node
	  SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished
	  COPY Release/fibers.node
	make: Leaving directory `/opt/myapp/tmp/bundle/programs/server/node_modules/fibers/build'
	Installed in `/opt/myapp/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.28/fibers.node`
<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/eachline
	└──<EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/chalk
	├──<EMAIL_ADDRESS>	├──<EMAIL_ADDRESS>	├──<EMAIL_ADDRESS>	├──<EMAIL_ADDRESS><EMAIL_ADDRESS>	└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/source-map-support
	└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/fibers
	Waiting for MongoDB to initialize. (5 minutes)
	connected
	rocket-shop start/running, process 5053
	Waiting for 60 seconds while app is booting up
	Checking is app booted or not?
	----------------------------------------------------------------------------

This is quite confusing :/ - I was running a 1G CPU (the $10/mo machine) and everything failed. I then decided to bump the machine to 2G - I've seen things go south with Node and Rails when resorting to swap files (Discourse comes to mind).
And it worked.
I don't think this is an issue with mup - it was just trying to compile bcrypt and some other things and (I guess?) ran out of memory or something.
So that's it: use a bigger image (at least 2G).

No need to install anything on the box extra for mup deployment.
Change your nodeVersion setting to this: "nodeVersion": "0.10.36" and do a mup setup/mup deploy again.

@aadamsx As mentioned I tried a bunch of different versions of Node - including 36 twice. The solution was a bigger box, for some reason.

I had the same issues and like @robconery - I also tried it on a larger instance and it works like a charm via port 3000, though I've yet to try switching it to the main IP but I am sure that will work fine.

@hwrod your solution worked for me as well

@hwrod  it works for me.  Thanks~
I've change several node version 0.12.7/0.12.5/0.10.9, they all don't work.
I found the default node version is 0.10.36

I have this issue too, failing deploy with messages about bcrypt. Same as RobConery.
However, I have been deploying successfully (10x maybe) in the last 2 days.
Running free micro instance on AWS, Ubuntu.
Could it be that with every deployment ,temp files are building up and I am running out of diskspace??
I had a demo today...and final deployment ...and then it crashed.
I had to quickly setup new AWS to have demo....sweat was dripping from my spine :) :)

Try to update mup.json with Node v0.10.40
then
mup setup  and  mup deploy

Thank you change of Node V0.10.40 worked was struggling with this issue over a day.

Thank you. Change to Node v 0.10.10 worked for me as well! You saved me a day of struggling.

Node v 0.10.10 worked here as well, thanks alot!

I'm using Digital Ocean, Ubuntu 14.04.4 x64.
! I got it working by resizing the Droplet from 512MB to 1GB !
I also updated node and npm to the latest version (1.4.28 npm and v4.4.0 node)

Woot! Here it also worked. I didn't need to resize. All I had to do was change the node version to Node v0.10.40.
Thnk for sharing guys!


When to open your code?

I am looking forward for your implementation!

I have attempted to reproduce your paper's results, but the performance is unstable and the training speed is very slow. I suspect there might be issues with my implementation. I would like to refer to your official implementation for guidance. Thank you!

Thanks for your attention!
I am sorry to have kept you waiting for so long. We are going to release the code it before ECCV camera is ready.


Gradle CI pipeline in Travis

As SRM Team
We want an automated build pipeline such that commits to master (or otherwise agreed) branch will build the deployables, run the tests, and produce reports on code/test quality
So that we can measure and maintain quality on this codebase.
Assumptions
Done Criteria:

[ ] confirm & agree appropriate build chain

This presents an interesting challenge due to the unique structure of the project

@ornearius you beat me too it (raising the issue that is) - thanks. I've updated the goals - so can you check them please?
I'm assuming that we'll do this in the same Travis account/environment that  Chris VH is using for python project(s)?


Implement translation of web site content.

From @aroubin on August 23, 2018 4:31
Implement automated translation of web site content.
Copied from original issue: Microsoft/Access2Justice#405

@breeglej @grawdon Is this language translation?  This is a task.  If this is for language translation for content, we can add a bug to fix the stakeholder reported issues.

@breeglej and @grawdon Is this required for pilot?

@KellyeDC and @breeglej No, I don't see this as needed for pilot. We might not want automatic translation for content as it could change the meaning and that is dangerous for legal information.


Add support for tuple concatenation to array analysis.

Resolves #5383
Adds support for tuple concatenation to array analysis.  Fixed a couple of places where equiv_set get_shape could fail and in those cases we do not create a parfor.  There are other spots and there probably needs to be a comprehensive review of those cases.

Please could you resolve the conflicts by merging master into this branch. Thanks!

retest this please

/AzurePipelines run

@DrTodd13 for future, command for retest is this comment https://github.com/numba/numba/pull/5396#issuecomment-658037379 or, if you click the "checks" tab at the top, the left side bar has clickable "rerun" buttons. I'm not sure if the authentication is working for it though.

Closing. To clear up the git history https://github.com/numba/numba/pull/6224 pulls the patch series doing the work into a new PR rebased on mainline. @DrTodd13 please could you take a look? Thanks.


Spectrum live TV support and research

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.08.23. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.08.23

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[x] Other

Anyone else interested in helping with this please contact me.
I have done a bit of research understanding how watching live TV at https://watch.spectrum.net/livetv works and on iOS as well which uses the Adobe SDK. I have not yet completed this research but these are my discoveries:

Authentication does use cookies but not always
Authentication on the API uses OAuth v1
Streams are encrypted, the metadata is embedded in the m3u8 and it is base64 encoded (PKCS#7 DER encoded inside)
Your OAuth consumer key and secret (which never change) are found in on the main page in the JavaScript:

GET https://watch.spectrum.net/livetv with no cookies
find line with window.onload = function () {
find next line with var environments = ...
parse this base64-encoded string. sample data:
[{"name":"prod","label":"production","splunk":{"domain":" https://splunk.ngclogging.cloud.twc.net/"},"analytics":{"endpoint":"https://v-collector.dp.aws.charter.com/api/collector"},"vpns":{"baseUri":"https://vpns-gen.timewarnercable.com"},"oAuth":{"consumerKey":"joeigjioegj","s":"jaoiegjoejg"},"displayRawRentError":false,"default":true}]"
Use this OAuth data to get token
Getting the temporary token:
GET https://services.timewarnercable.com/auth/oauth/request
OAuth data required from previous
Returns URL-encoded string with xoauth data
example: oauth_token=xxxx&oauth_token_secret=xxx&xoauth_token_expiration=1503113510937&oauth_callback_confirmed=true
'Authorise' your device:
POST https://services.timewarnercable.com/auth/oauth/device/authorize
OAuth data required from last step
POST data:
xoauth_device_id: xxx
xoauth_device_type: ONEAPP-OVP
oauth_token: xxx
username: your spectrum account username (could be an email)
password: ...
To get a session ID, etc:
Oauth GET https://services.timewarnercable.com/ipvs/api/smarttv/adobe/session
In the JSON: ticketId, sessionId, expiration (UNIX timestamp)
Then get stream information, JSON which will have the URI to an m3u8 file:
OAuth GET:
https://services.timewarnercable.com/ipvs/api/smarttv/stream/live/v1/172?adID=<adId>&csid=stva_ovp_pc_live&dai-supported=true&drm-supported=true&encoding=hls&sessionId=<your session ID>&vast-supported=true
I have no idea what adID is in the above URL.
In the JSON, you will see the key stream_url which is the full m3u8 URL. This is downloadable without cookies or anything (authorisation is in the query string). It is timed and will eventually expire.
In the M3U8, you can find the following:
EXT-X-FAXS-CM key -> base64 decode -> pkcs7 decode
base64 -d file-with-content > faxs.der
openssl pkcs7 -inform der -in faxs.der -print_certs
POST URL is in the metadata
strings -n 10 faxs.der
The POST URL for the license server found in the metadata requires query parameters:
CrmId=twc&AccountId=twc&ContentId=6_ae&SubContentType=Primetime&OriginalUri=/flashaccess/getServerVersion/v3&Ticket=<ticket ID>&SessionId=<SessionId>
ContentId is the channel ID (in this case A&E).
You must POST a certificate as is (possibly URL encoded which seems strange yes)  in the body of the request. What you get back is a 'individualization certificate', as in the decryption key?
There are two such requests. I do not know why. They differ in size so they are different.
Once the key is grabbed, I assume any TS file can be decrypted. The algorithm is not really known, but I seem to see references to AES-128-CBC in the Adobe Player SDK on iOS. There is a method named: -[DRMManager initDecryptionSession:playbackSession:error:complete:].
Python code to demonstrate (set global variables USERNAME and PASSWORD):
from base64 import b64decode
from datetime import datetime
from math import trunc
from random import SystemRandom
import json
import logging
import re
import sys

from requests_oauthlib import OAuth1Session
import requests

USER_AGENT = ('Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 '
              '(KHTML, like Gecko) Chrome/61.0.3163.49 Safari/537.36')

URL_LIVE_TV = 'https://watch.spectrum.net/livetv'

# TODO Get URLs dynamically like the site
URL_AUTO_AUTHORIZATION = 'https://services.timewarnercable.com/auth/oauth/auto/authorize'
URL_DEVICE_AUTHORIZATION = 'https://services.timewarnercable.com/auth/oauth/device/authorize'
URL_STATUS = 'https://services.timewarnercable.com/auth/oauth/token/status'
URL_TEMPORARY_REQUEST = 'https://services.timewarnercable.com/auth/oauth/request'
URL_TOKEN_EXCHANGE = 'https://services.timewarnercable.com/auth/oauth/ssotoken/exchange'
URL_TOKEN = 'https://services.timewarnercable.com/auth/oauth/token'
URL_WAYFARER = 'https://services.timewarnercable.com/auth/oauth/wayfarer'
URL_ADOBE_SESSION = 'https://services.timewarnercable.com/ipvs/api/smarttv/adobe/session'
URL_VPNS_CONNECT = 'https://vpns-gen.timewarnercable.com/vpnspush/v1_5/connect'
URL_VPNS_REGISTRATION = 'https://vpns-gen.timewarnercable.com/vpnsservice/v1_5/registration'

# Device ID original JavaScript:
# "xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx".replace(
#   /[xy]/g,
#  (e) => {
#    var t = (16 * Math.random()) | 0;
#    if (e === 'x') {
#        n = t;
#    } else {
#        n = 3 & t | 8;
#    }
#    return n.toString(16);
# })
def generate_device_id():
    rand = SystemRandom()
    s = [x for x in 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx']
    for i, c in enumerate(s):
        if c == 'x' or c == 'y':
            t = trunc(16 * rand.random()) | 0
            if c == 'x':
                n = t
            else:
                n = 3 & t | 8
            s[i] = hex(n)[2:]
    return ''.join(s)

if __name__ == '__main__':
    log = logging.getLogger('oauthlib')
    log.addHandler(logging.StreamHandler(sys.stdout))
    log.setLevel(logging.DEBUG)

    sess = requests.Session()
    sess.headers.update({'User-Agent': USER_AGENT})

    # GET https://watch.spectrum.net/livetv with no cookies
    r = sess.get(URL_LIVE_TV)
    r.raise_for_status()

    data = None
    for line in r.content.decode('utf-8').split('\n'):
        if 'var environments' not in line:
            continue
        m = re.match(r'(?:\s+)?var(?:\s+)environments(?:\s+)=(?:\s+)[\'"]([^\'"]+)[\'"]', line)
        if not m:
            raise Exception()
        data = json.loads(b64decode(m.group(1)).decode('utf-8'))
    if not data:
        raise Exception()

    oauth_consumer_key = data[0]['oAuth']['consumerKey']
    oauth_secret = b64decode(b64decode(data[0]['oAuth']['s']))

    oauth = OAuth1Session(oauth_consumer_key,
                          client_secret=oauth_secret)
    oauth.headers.update({
        'User-Agent': USER_AGENT,
        'Referer': URL_LIVE_TV,
        'Origin': 'https://watch.spectrum.net',
        'Accept': 'application/json, text/plain, */*',
    })
    token_data = oauth.fetch_request_token(URL_TEMPORARY_REQUEST)

    device_id = generate_device_id()

    r = oauth.post(URL_DEVICE_AUTHORIZATION, data=dict(
        xoauth_device_id=device_id,
        xoauth_device_type='ONEAPP-OVP',
        oauth_token=token_data['oauth_token'],
        username=USERNAME,
        password=PASSWORD,
    ))
    r.raise_for_status()
    dev_auth = 'https://f?oauth_token={}&{}'.format(token_data['oauth_token'], r.content.decode('utf-8'))
    dev_auth = oauth.parse_authorization_response(dev_auth)

    r = oauth.post(URL_TOKEN)
    r.raise_for_status()
    oauth_token = 'https://f?{}'.format(r.content.decode('utf-8'))
    oauth_token = oauth.parse_authorization_response(oauth_token)

    oauth = OAuth1Session(oauth_consumer_key,
                          client_secret=oauth_secret,
                          resource_owner_key=oauth_token['oauth_token'],
                          resource_owner_secret=oauth_token['oauth_token_secret'],
                          verifier=dev_auth['oauth_verifier'])
    oauth.headers.update({
        'User-Agent': USER_AGENT,
        'Referer': URL_LIVE_TV,
        'Origin': 'https://watch.spectrum.net',
        'Accept': 'application/json',
    })

    # VPNS - what is VPNS? :(
    #r = oauth.post(URL_VPNS_REGISTRATION, json={
        #'Registration': {
            #'Device': {
                #'id': device_id,
            #},
            #'id': device_id,
            #'operation': 'create',
        #}
    #})
    #r.raise_for_status()
    #registration_data = r.json()
    #vpns_client_id = registration_data['Registration']['Client']['id']
    #vpns_session_id = r.headers['X-VPNS-NOTIFY-SESSIONID']

    r = oauth.get(URL_ADOBE_SESSION)
    r.raise_for_status()
    session = r.json()
    ticketId = session['ticketId']
    sessionId = session['sessionId']
    expiration = datetime.fromtimestamp(session['expirationTimeSeconds'])

Any progress recently?
You used to be able to download on demand shows via streamlink / livestreamer by simply replacing "HLS_DRM" in the M3U8's URL with "HLS" but that no longer works.

Haven't had a chance to look at this.
If anything the work is in debugging Adobe Flash DRM in multiple ways:

Decompile the SWF that Spectrum/others use and analyse (I found key mentionings, API endpoints, etc), but this does not really contain decryption code because that's Adobe's code
Debug/Disassemble the iOS app and Flash DRM iOS framework with Hopper or IDA Pro (only latest Hopper can make psuedo-code from arm64 code)
Debug/Disassemble the DLL/dylib of the Flash browser plugin with Hopper or IDA Pro

Once one is cracked arguably the rest are done too until a Flash update comes. An exploit is definitely another potential and it could be found by disassembling the Flash plugin.
I don't think this DRM scheme has been cracked publicly nor have I seen any content on the web spreading that was from a source that used Adobe's DRM as far as I know. Netflix/Amazon/etc all use their own systems (EME/M3U8+AES key in a browser, their own apps on iOS/Android/etc).

The word "FAXS" reminds me of SAMPLE-AES (#9786), which is a different decryption flow than AES-128. There's a Javascript implementation at https://github.com/video-dev/hls.js/pull/997


Feature/aws accounts

I added a panel in Setup section to list and add AWS Accounts.
~What may changes soon, since the API isn't finished :~
~- Support for External ( It will be send by the API before user can add its informations )~
~- Support for pretty name for AWS Accounts~
@alexis-ld If you're okay, we can merge this PR when everything will be implemented.
Update (15/11/18) :

Panel Component is now available (It has a title and a body that can be collapsed)
AWS.FormComponent let you add an AWS Accounts
( External will be given by API, roleARN and pretty will be requested but only roleARN is mandatory )
AWS.ListComponent will list accounts and let you edit or delete an account.
AWS.Bills.FormComponent let you add a S3 Bucket to get bills
( S3 Bucket and path are requested and both are mandatory )
AWS.Bills.ListComponent will list bills and let you edit or delete a bucket.

N.B. : Since some features are still not available in API, I had to mock some data (Bills).
PropTypes are already set to handle bills in accounts.

Ok ! We'll wait until the API have this implemented before merging this.

TODO
WIP
Sagas

[ ] Check response for API.AWS.Accounts.newAccountBill in AccountsSaga.newAccountBillSaga
[ ] Check response for API.AWS.Accounts.editAccount in AccountsSaga.editAccountSaga
[ ] Check response for API.AWS.Accounts.editAccountBill in AccountsSaga.editAccountBillSaga
[ ] Check response for API.AWS.Accounts.deleteAccount in AccountsSaga.deleteAccountSaga
[ ] Check response for API.AWS.Accounts.deleteAccountBill in AccountsSaga.deleteAccountBillSaga

User login call has been updated to match API routes.
N.B. : Account edition/deletion is not ready in API now. Account bills too. I'll make another PR when API will have implemented these features.


[TF-TRT] DEFAULT_TRT_MAX_WORKSPACE_SIZE_BYTES fixed to LLONG_MAX - 512

This PR fixes a minor bug where default max_workspace_size was set to 2GB instead of LLONG_MAX as recommended by TensorRT.
This PR fixes this problem

@bixia1 for review


DBZ-3467 'group' keyword to be used as ID

https://issues.redhat.com/browse/DBZ-3467
Upstream PR - https://github.com/antlr/grammars-v4/pull/2170

Thx!


Correction for raw affiliation Laboratoire ICAR UMR 5191 / LabEx ASLAN

Correction needed for raw affiliation Laboratoire ICAR UMR 5191 / LabEx ASLAN
raw_affiliation_name: Laboratoire ICAR UMR 5191 / LabEx ASLAN
new_rors: 04mn0nr69
previous_rors: 050f22e89
works_examples: W4297432826
contact: 2306387a5cdf995ef5bb37c0a1a8ded2:3ab90db5d88fc30593630f9cb250 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


504 Gateway Time-out

Describe the bug
For some reason, after a few months of perfect operation and use, the backend responds very slowly. This is giving a 504 error on the frontend. Sometimes it will work fine, but most of the time it will respond very slowly. For example, time curl -L localhost:8080/server/api/core/communities is 1m or more, rendering the page unusable.
The database (postgres) and solr work fine. There are no health warnings of any kind. Also, there don't seem to be any errors in the dspace logs.
Do you know how I can debug this?
I am running DSpace 7.3.

@santilococo : I'd recommend following our Troubleshooting Guide to look for other errors being reported in DSpace, Tomcat, Postgres, Solr, etc. https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
As this sounds like an issue with your setup and not a specific bug in DSpace, I'd also recommend using one of our Support options listed at https://wiki.lyrasis.org/display/DSPACE/Support  It's possible others on our dspace-tech (Tech Support) list may have more specific advice, if you provide more details about your setup, etc.
Flagging as "cannot reproduce"

Thanks Tim.
I resolved the issue by running the database locally, as the connection to the cloud-based database (for some reason) was unreliable.


adding Depth Anything v2

This deals with #450 .
Only adding most basic functionality from depth anything v2. Also not tested with boost, tiling, or any extra features (although they should work).
Notes
Maybe we should make a guide for how to add new models because they are coming out so fast right now.
This only uses vitl model (maybe others should be included too). vitg is suppose to come out soon and presumable be better.
Depth anything has it's own functions for pointcloud conversions (right now using zoedepth functions)
Depth anything v2 also does have metric information that's thrown out that maybe could be included somewhere (the information is normalised away).
I'm also starting to think maybe we should invert the UI list so newer models are near the top.

@semjon00 @thygate have a quick moment to review this?

@graemeniedermayer Hello and thank you for this MR! Could you please update it so that all the available depth anything models are listed? Also, do you think there is a change this new code could cause exceptions for users who won't even use Depth Anything v2? Currently, the code uses modular approach: if one feature fails to load (e.g. impainting), other features won't be harmed.

@thygate These models look good, do you think we should set one of them as a default once this lands?

It is compartmentalised so I don't expect it to cause any issues for other users. People appear to be using the pull request directly so I would prefer it be merged before it causes too much confusion. Adding models should be straightforward, but because people are using this branch maybe I could make a separate pull request for that?
This is also one of the faster models so I think it would be a good default.

I was getting an error when trying to naively implement half. It runs at about 3.5 vram GB for me which is really surprising. But I'll look into this more.

I am making some changes based on this MR, lands soon (tm*)
*Ok soon for real actually.

The half bug is "RuntimeError: Input type (float) and bias type (struct c10::Half) should be the same"
Means we should check that all the objects we pass around (image input for instance) are all half.

Thanks one more time for the MR ❤ , took the code and inspiration from there. I also added half mode and other models. I would appreciate if you could verify that I did not miss anything. And of course, this model (standing on the shoulders of giants, of course) is awesome and just destroys the res101 IMHO. The authors even provide the video mode and point clouds and metric values, I start feeling silly for my video implementation.
If you can find an idea for improving, I'm all ears!

While I do appreciate your comments about technical debt in the depth_api file, perhaps the comment should be shorter.
any chance you could add me as coauthor on the depthanything v2 commit?

About technical debt, sorry, I meant to put it to another place - we have unexplainable numbers like this all over the project. You could not have prevented this mess, we had these magic numbers long before the API was even a thing. And the core reason actually is how gradio treats options in the drop-down - as numbers. We needed an entire class just to aggregate the UI elements and their settings together (gradio_args_transport.py). I moved it to get_default_net_size (the function with the cryptic set of numbers). I hoped the comment to be funny. Didn't mean it to be a dig at your code 😅😢
Adding you as co-author, forgot to do that...
I am really sorry, how I handled this looked quite bad not gonna lie.


Is qvis support GQUIC?

Hi, my problem is that GQUIC is supported?
It is still use gquic popularily, expecially q046 which is used mostly in latest chrome browser.

Hello there,
Currently, GQUIC is indeed not supported and I don't have plans to ever support it here. It is evolving towards IETF QUIC anyway and will soon be outdated/obsolete.
I also don't really want to encourage behavioral analysis on outdated versions of the protocol. In my opinion, research on gQUIC is no longer useful.
That being said, I would be open to others adding support for it. For more information, see this issue: https://github.com/quiclog/pcap2qlog/issues/1
With best regards,
Robin


Design the look of the Website.

This so far what we discussed about the websites design.
@deevad manage to found backups of it's current theme back in 2011 in mypaint/mypaint#496.

I found in my backup/archives the themes + community screenshot from the 2011 campaign + the visual I made for the page. I put all in a zip here; http://www.davidrevoy.com/XYZ/2015-11-15_mypaint-web.zip

He also suggest we could use this theme and build upon that.

I just browsed a bit the themes. I like the design of the place-holder website you made on http://mypaint.org/ : something white, simple, classic. Maybe http://jekyllthemes.org/themes/fengzhichu-theme/

It looks good so far to me,but when I switch to its mobile navigation menu, it looks really ugly so we'll need to work on that. Like I replied, We'll use a lot of the old assets that @deevad had backups of, and We'll use some screenshots from mypaint/mypaint#149 to give it an updated look.
Here's what @achadwick had to say bout design of mypaint's website on mypaint/website#2

For the look: well, something a bit more modern than the old design would be nice! I'm not a huge follower of site trends, but "modern" seems to mean infinitely scrollable (not paginated), not column-based (normally one), and good for mobile right now.
Maybe use the (easily mocked, but serviceable) "page-sized dark image-background hero section with 2 or 3 white-outline CTA buttons" pattern. Yeah, I know, so generic. Perhaps just trim it down to a page-wide banner with especially awesome artwork (close-up photo of on-screen artwork being painted?) or a slideshow of similar in the index.html template, above the start of the blog posts? Anything to look a bit less corporate :grinning:
There are probably tons of readymades on http://jekyllthemes.org/ that can be adapted. One with strong support for multimedia posts would be best: particularly galleries, but consider that we might do tutorial videos too. It would need to be deployable without plugins, for hosting on github
Content: the default Jekyll theme's split between "pages" and "posts" is good.
Pages should be points of engagement that fire users off into development land, or towards the downloads or online communities relating to MyPaint, as well as basic info. We definitely need a who-we-are page listing out the devs, and probably a glossy what-this-program-is brochure page. IIRC, Krita have an especially good "how can I get involved (with development, site coding, artwork, resources, community building, you name it...)" page.
Posts of course should be development news, links to Things of Interest (e.g. tutorials, new brush packs) and release announcements, and I'll try to keep the blog updated.

And I replied:

Plus with design I'll probably build from one of the themes from the Jekyll site. I'll expand more upon in another issue once we have a set list of what the site needs, but I'll definitely don't want it to feel corporate.
With images if we name them correctly, we could avoid using folders. That's something I could expand upon in the website's wiki for contributors.

From all the information you guys gave, you are looking for a end to end web page, that point's to everything that we have in the community. Basically a portfolio for MyPaint with the front page highlighting the key features. I'll keep in mind both GIMP and Krita webpages as references. If you guys have any ideas for the design for the site, let me know down below.
Also if any artist wishes to have their artwork featured on the website, leave a comment down below with link to the artwork. The artwork also needs to be on at least a CC BY-NC to be compatible to the website.

Hey, I saw the link to my old Mypaint webdesign was broken when I reread this thread bumped this morning.
So, I uploaded a new link (hopefully more stable for the coming next years):
https://www.peppercarrot.com/extras/forum/2011-webdesign_mypaint-web.tar.gz

Hi David, nice to see you around -- it was hard not to see your name while making the new website. Thanks for updating the link


Egress Broken in VPC Tiers

ISSUE TYPE

Bug Report

COMPONENT NAME

VPC

CLOUDSTACK VERSION

4.14

CONFIGURATION

OS / ENVIRONMENT

Ubuntu 18.04, KVM, Advanced Networking, Local Storage
SUMMARY

According to the documentation: "By default, all incoming traffic to the guest networks is blocked and all outgoing traffic from guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing traffic specified in this ACL rule is allowed, the rest is blocked."
ACLs on VPC tiers do not block the rest of the traffic even if an Egress rule is added.
STEPS TO REPRODUCE

- create a VPC with 2 tiers, Management and Service
- create a custom ACL for each tier with the same name as the tier
- Create an ACL Egress rule on Management that allows accessing Service Tier (for example on port 22)
- Create a VM on Management Tier
- Test accessing the Service tier from the VM
- Test accessing the Internet from the VM

EXPECTED RESULTS

The VM should have access to the Service tier as specified.
However, Since there is already an Egress rule specified the the rest of outgoing traffic should be blocked.
The VM should not be able to access the Interenet.

ACTUAL RESULTS

The VM can access the internet:
ping www.google.com works
wget http://www.google.com works.

Further testing: Traffic is going out from the VPC tiers despite the 9999 deny all rule.
Something here seems fundamentally broken.

I am also experiencing issues with ACLs Egress which use multiple CIDRs, although I still could not asses if the issue is with Ansible Modules or ACS. see https://github.com/ngine-io/ansible-collection-cloudstack/issues/41

after discussing the multiple CIDRs issue with @resmo we think that it is related to this issue. Rules are also not working when they take multiple CIDRs as parameters.

rules can't take multiple CIDRs as parameter value - please see the UI/API - at least - afaik
The original issue described here should be confirmed by someone else as well - it's a serious one IMO, even would consider it a blocked issue myself if true.
cc @Spaceman1984 @rhtyd

@andrijapanicsb I check the API spec and they take a list.
Also, Ansible modules have been built matching the API, taking lists is been tested too.

Tested the original issue -
I created a VPC with 3 tiers - Management, Service and NoACL - The third one had no ACL list specified.
I was able to ping google.com from VMs running on all 3 tiers. ( This is the bug )
Adding a deny rule on <IP_ADDRESS>/0 blocked outgoing traffic.

Thanks @Spaceman1984.

Please see docs before confirming an issue @Spaceman1984
http://docs.cloudstack.apache.org/en/latest/adminguide/networking/virtual_private_cloud_config.html?highlight=acl#about-network-acl-lists
Specifically:
The default Network ACL is used when no ACL is associated. Default behavior is all the incoming traffic is blocked and outgoing traffic is allowed from the tiers...:
With this in mind ^^^, conduct the testing... - it is expected that your noACL tier was able to ping anything outside
But the other "blocked by default..." egress issue:
I think the documentaion is not correct - i.e. for VPC networks, I don't recall that there was ever an implementation that will by default block outgoing traffic (egress) on ACLS where some Egress rules allow some access - i.e. you would always want to add <IP_ADDRESS>/0 deny rule - it's an EMPTY ALC that you want to populate your way - just like on any other router - you will explicitely add deny to <IP_ADDRESS>:0 as the last rule in the ACL.
I would prefer that we update the documentation on VPC ALC, instead of chaning the behaviour, unless some of you can confirm that this worked differently in previous ACS versions @rvalle ?

@Spaceman1984 yes, @andrijapanicsb is right.
You can add a single egress rule to your setup, which should imply that the allow all out by default stops. then you can validate.
@andrijapanicsb I cannot comment on previous ACS versions, I joined the party late !
I agree with you in which I do not like the original specification: i.e. after adding one rule the default policy changes. I don't like it.
But I guess it would be good to know if this issue is also in pre 4.14 just in case it turns out that it works as specified in previous releases.

@rvalle closing this one. can you work on the description and title if you want to re-open? thanks


Rework homegrown ModAPI DLLs support

Current implementation misses the point, since projects would have to be modified to build against the homegrown DLLs. This is unacceptable and must be fixed.

Feature dropped, no fix needed.


Crash: Simultaneous accesses to 0x12d2205e0, but modification requires exclusive access

Xcode 13.0
iOS 15.0.2
The crash happens with me when setting the isAnimating to .constant(false). It happens when setting the currentFrame to nil which I think publishes an update. Solved the issue by checking if the currentFrame is not nil before nullifying it. Actually I don't have an idea why we should set it to nil in the deinit.

Thread #1, queue = 'com.apple.main-thread', stop reason = Simultaneous accesses to 0x12d2205e0, but modification requires exclusive access
    frame #0: 0x000000018634ccf4 libswiftCore.dylib`_swift_runtime_on_report
    frame #1: 0x000000018634d3ac libswiftCore.dylib`swift_beginAccess + 648
    frame #2: 0x0000000189c588c8 SwiftUI`SwiftUI.GraphHost.isValid.getter : Swift.Bool + 28
    frame #3: 0x0000000189017744 SwiftUI`generic specialization <SwiftUI.InvalidatingGraphMutation> of SwiftUI.GraphHost.asyncTransaction<τ_0_0 where τ_0_0: SwiftUI.GraphMutation>(_: SwiftUI.Transaction, mutation: τ_0_0, style: SwiftUI._GraphMutation_Style, mayDeferUpdate: Swift.Bool) -> () + 28
    frame #4: 0x000000018901e35c SwiftUI`SwiftUI.AttributeInvalidatingSubscriber.invalidateAttribute() -> () + 268
    frame #5: 0x0000000188fe9124 SwiftUI`SwiftUI.AttributeInvalidatingSubscriber.receive(τ_0_0.Output) -> Combine.Subscribers.Demand + 104
    frame #6: 0x00000001891870c4 SwiftUI`protocol witness for Combine.Subscriber.receive(τ_0_0.Input) -> Combine.Subscribers.Demand in conformance SwiftUI.AttributeInvalidatingSubscriber<τ_0_0> : Combine.Subscriber in SwiftUI + 24
    frame #7: 0x0000000188fe9f8c SwiftUI`SwiftUI.SubscriptionLifetime.Connection.receive(τ_0_0.Output) -> Combine.Subscribers.Demand + 244
    frame #8: 0x0000000198f10854 Combine`Combine.ObservableObjectPublisher.Inner.send() -> () + 204
    frame #9: 0x0000000198f28eb4 Combine`Combine.ObservableObjectPublisher.send() -> () + 552
    frame #10: 0x0000000198f1bb10 Combine`Combine.PublishedSubject.send(τ_0_0) -> () + 160
    frame #11: 0x0000000198f05390 Combine`function signature specialization <Arg[1] = Owned To Guaranteed, Arg[2] = Dead, Arg[3] = Owned To Guaranteed, Arg[4] = Dead> of static Combine.Published.subscript.setter : <τ_0_0 where τ_1_0: AnyObject>(_enclosingInstance: τ_1_0, wrapped: Swift.ReferenceWritableKeyPath<τ_1_0, τ_0_0>, storage: Swift.ReferenceWritableKeyPath<τ_1_0, Combine.Published<τ_0_0>>) -> τ_0_0 + 620
    frame #12: 0x0000000198f0688c Combine`static Combine.Published.subscript.setter : <τ_0_0 where τ_1_0: AnyObject>(_enclosingInstance: τ_1_0, wrapped: Swift.ReferenceWritableKeyPath<τ_1_0, τ_0_0>, storage: Swift.ReferenceWritableKeyPath<τ_1_0, Combine.Published<τ_0_0>>) -> τ_0_0 + 40
    frame #13: 0x00000001092b270c SDWebImageSwiftUI`ImagePlayer.currentFrame.setter(value=nil, self=0x00000002803c5f80) at ImagePlayer.swift:0
  * frame #14: 0x00000001092b25d4 SDWebImageSwiftUI`ImagePlayer.deinit(self=0x00000002803c5f80) at ImagePlayer.swift:34:22
    frame #15: 0x00000001092b2788 SDWebImageSwiftUI`ImagePlayer.__deallocating_deinit(self=0x00000002803c5f80) at ImagePlayer.swift:0
    frame #16: 0x000000018634fde0 libswiftCore.dylib`_swift_release_dealloc + 56
    frame #17: 0x00000001092c8fbc SDWebImageSwiftUI`destroy for WebImage at <compiler-generated>:0
    frame #18: 0x0000000188ffd5b0 SwiftUI`destroy value witness for SwiftUI.ModifiedContent + 72
    frame #19: 0x0000000188ffd5b0 SwiftUI`destroy value witness for SwiftUI.ModifiedContent + 72
    frame #20: 0x00000001b29c6aa8 AttributeGraph`AG::Node::destroy(AG::Graph&) + 152
    frame #21: 0x00000001b29c65d4 AttributeGraph`AG::Subgraph::invalidate_now(AG::Graph&, unsigned long) + 1272
    frame #22: 0x00000001b29c2728 AttributeGraph`AG::Graph::invalidate_subgraphs() + 184
    frame #23: 0x00000001b29cc138 AttributeGraph`AG::Graph::Context::~Context() + 276
    frame #24: 0x00000001b29cac20 AttributeGraph`AGGraphInvalidate + 36
    frame #25: 0x00000001890e5f9c SwiftUI`SwiftUI.GraphHost.invalidate() -> () + 168
    frame #26: 0x000000018902f7d4 SwiftUI`closure #1 () -> () in SwiftUI._UIHostingView.deinit + 84
    frame #27: 0x0000000189029df8 SwiftUI`SwiftUI._UIHostingView.__deallocating_deinit + 228
    frame #28: 0x0000000189034de4 SwiftUI`@objc SwiftUI._UIHostingView.__deallocating_deinit + 28
    frame #29: 0x00000001815a8960 CoreFoundation`__RELEASE_OBJECTS_IN_THE_ARRAY__ + 116
    frame #30: 0x00000001815bc64c CoreFoundation`-[__NSArrayM dealloc] + 276
    frame #31: 0x0000000199b3f55c libobjc.A.dylib`AutoreleasePoolPage::releaseUntil(objc_object**) + 200
    frame #32: 0x0000000199b3b928 libobjc.A.dylib`objc_autoreleasePoolPop + 208
    frame #33: 0x0000000185332128 QuartzCore`CA::Context::commit_transaction(CA::Transaction*, double, double*) + 620
    frame #34: 0x000000018533b174 QuartzCore`CA::Transaction::commit() + 680
    frame #35: 0x000000018531d210 QuartzCore`CA::Transaction::flush_as_runloop_observer(bool) + 88
    frame #36: 0x00000001815db570 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
    frame #37: 0x00000001815aa854 CoreFoundation`__CFRunLoopDoObservers + 572
    frame #38: 0x00000001815a58ec CoreFoundation`__CFRunLoopRun + 1052
    frame #39: 0x00000001815b93c8 CoreFoundation`CFRunLoopRunSpecific + 600
    frame #40: 0x000000019cdca38c GraphicsServices`GSEventRunModal + 164
    frame #41: 0x0000000183f5f060 UIKitCore`-[UIApplication _run] + 1100
    frame #42: 0x0000000183cdcb8c UIKitCore`UIApplicationMain + 2124
    frame #43: 0x0000000104de2500 Haraj`main(argc=1, argv=0x000000016b023918) at main.m:15:17
    frame #44: 0x0000000106f41a24 dyld`start + 520

I have exactly the same problem besides the crash still happen occasionally even if I don't set the isAnimating parameter.

I am still having this issue, randomly crashes the app.

I have exactly the same problem besides the crash still happen occasionally even if I don't set the isAnimating parameter.

Seems TSAN issue.
@angelmic  Can you have a test with v3.0.0-beta is this still reproducable ?

I am facing same issue any solution ?

This code no longer exists ? There are no deinit
Try with 3.0.0-beta2 with reproducable demo ?

how to try or install   3.0.0-beta2 on my project @dreampiggy

I have installed 2.2.5 and still no crash has produced yet
only code exist in imagePlayer file
deinit {
player?.stopPlaying()
}

how to try or install 3.0.0-beta2 on my project @dreampiggy
Just use the fixed version ? As a App developer, you have final control for each package's version.

https://developer.apple.com/documentation/xcode/adding-package-dependencies-to-your-app

Try with v2.2.6 and see whether this been fixed or not.
If you don't have time to try v3.0.0
In v3.0.0, this repo may move to SDWebImage Core repo...So which need some migration (not pain, but still need changing the Podfile or Package.swift)

v2.2.6 updated  and crashed has been fixed. Thank you @dreampiggy


[BUG]Edit ConfigMap With RancherUI

When the characters of each line exceed a certain length, after saving through the UI, all non-blank lines will eventually have extra line breaks. It appears every time you save.

rancher v2.7.9 Same problem ㅜㅜ

If the long lines are comments in things like nginx config files, this results in an unusable, corrupted config.

@alves08

same issue
#42288

@LaoZhang-best thanks for raising this issue. There was another on rancher/rancher with more detail. I've transferred that over to this repo and will close this as a duplicate


Add shortcuts for named and outputwrapping elementwise operation vert…

…ices

Codecov Report

Merging #26 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
+ Coverage   96.84%   96.85%   +0.01%
==========================================
  Files           9        9
  Lines         792      796       +4
==========================================
+ Hits          767      771       +4
  Misses         25       25

Impacted Files
Coverage Δ

src/mutation/sugar.jl
96.42% <100%> (+0.27%)
:arrow_up:

src/mutation/op.jl
95.65% <100%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Reduce disk utilization

I notice that the SFrame folder comes in at a sizable 5.5Gb after compiling libunity. I'm interested in extracting the minimum runtime dependencies of libunity plus the header files, something like what make install would do for many packages.
Is that (or is there a plan to) make that functionality available? Or it's not too much trouble, would you mind offering me some guidance on how to do it manually?
Thanks!

Ah. It is huge mainly because of symbol tables. stripping it brings it substantially smaller. (Also, we static link most things).
We do collect an "SDK" during the build process which is just the minimal set of header files required.

Make in [build]/oss_src/unity
[build]/oss_src/unity/sdk will now contain a complete subdirectory of headers, a sample Makefile, etc.
And you want the core library in [build]oss_src/unity/libunity_shared.so/dylib/dll

@ylow Do we plan to take any action in the SFrame repo to reduce the size of built artifacts?


update pakage

Using the sound controller class, I created an example with vertical and horizontal features, and also added the ability to hide and show it by double clicking.
Everything can be customized in the created class.

add drag volume

I want this pack for pure volume control. Therefore, I reject this request.


FireTV Media Player not showing up in HASS

I got my FireTV setup using this guide: https://home-assistant.io/components/media_player.firetv/
However when I run the firetv-server it works fine when going to localhost and shows the proper state of my firetv, but I can't get Home Assistant to connect to it. I'm assuming this is due to the firetv server not starting at boot and rather me starting it up after boot?
Here is the error in homeassistant:
16-10-30 03:55:05 homeassistant.components.media_player.firetv: Could not connect to firetv-server at <IP_ADDRESS>:5555

So I got this solved, however the device is now showing improper states.
Whenever my firetv is in the main menu or paused video it shows "playing"

Do you have a Fire TV stick or other device? What version of FireOS is it running? There is some variation out there.

I'm running on a FireTV stick on OS: <IP_ADDRESS>

How did you solve it? I have currently the same problem.

@tringler What problem are you referring to?
@happyleavesaoc Have you been able to find possible fixes for this issue? It's not too big of a deal, but it kinda sucks since if I want to pause it and get out of bed it's kinda hard to see.

@Nitee I was able to solve it.

@tringler Did you solve the issue with improper states or some other issue?

The original issue of integration with HA has been solved. Discussion of state detection should go in this issue: https://github.com/happyleavesaoc/python-firetv/issues/7.


Replace the wait flag in the helm operations by a configurable polling interval

Closes #1661
This PR adds a configuration flag for the time interval to check the status of the resources deployed by the manager.
It is used by the blueprint-controller and in helm uninstall operation.

As a general comment, I don't think that the same number can be used for both. Checking every two seconds for a resource status makes sense, whereas install timeout is much longer. Not sure what happens if the install timeout is not sufficient - will the operation fail?

I think it will fail but I'll check. I will add an additional env var for operation timeout.

Also, please look at https://github.com/fybrik/fybrik/issues/1622 - another polling interval, the same configuration can be used for  polling blueprints and blueprint resources. Helm timeouts are different, I would not mix them all.


fix(meta): when txUnlink inode, try return the inode after update lin…

…k cnt.

fix the bug that when delete file by tx, will evict fail in some case.

LGTM


Dereference was required for named reference args

This patch adds dereference of named reference args such as Namedarg("blahblah", Pyref r).
I am not Python expert.  If the patch looks ugly, please change it as you like.

Well spotted, thanks a lot for the MR !


Adds Next Export command

This drops in next export so Fleek can pick it up for creating pure static site.

bump @Oktalize

@wpmonty I was looking through the code again and I forgot about this API. Wouldn't this cause issues since next export disables API routes?

@wpmonty I was looking through the code again and I forgot about this API. Wouldn't this cause issues since next export disables API routes?

Good call; I wonder how Fleek recommends handling APIs - maybe ship them off to AWS lambda lol

@wpmonty I was looking through the code again and I forgot about this API. Wouldn't this cause issues since next export disables API routes?

Good call; I wonder how Fleek recommends handling APIs - maybe ship them off to AWS lambda lol

AWS lambda, or maybe even Akash? This is definitely one the areas that needs improvement for Web3. I am thinking that most of the reasons Fleek doesn't do it because they need maximum compatibility with IPFS.

Until we resolve the fundamental issue of APIs with Fleek, there is no reason to merge in next export