[interop] cxx vector benchmark - reenable without SwiftPM support

@swift-ci please test

@swift-ci please test linux platform

@swift-ci please build macOS toolchain

@swift-ci please build toolchain

@swift-ci please test linux platform

@swift-ci please build toolchain

@swift-ci please test linux platform

@swift-ci please build toolchain

@swift-ci please test

@swift-ci please benchmark

@swift-ci please benchmark

@swift-ci please benchmark

@swift-ci please benchmark

@swift-ci please test

@swift-ci please build toolchain

Results:
Performance (x86_64): -O

Regression
OLD
NEW
DELTA
RATIO

FlattenListLoop
976
1615
+65.5%
0.60x (?)

LineSink.characters.alpha
67
84
+25.4%
0.80x (?)

Dictionary3
121
134
+10.7%
0.90x (?)

NSError
101
109
+7.9%
0.93x (?)

Added
MIN
MAX
MEAN
MAX_RSS

CxxVecU32.sum.Cxx.rangedForLoop
11
11
11
—

CxxVecU32.sum.Swift.forInLoop
24
24
24
—

CxxVecU32.sum.Swift.iteratorLoop
11
11
11
—

CxxVecU32.sum.Swift.reduce
24
24
24
—

CxxVecU32.sum.Swift.subscriptLoop
11
11
11
—

Code size: -O

Regression
OLD
NEW
DELTA
RATIO

CxxVectorSum.o
78
10256
+13048.6%
0.01x

Performance (x86_64): -Osize

Regression
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
2452
3879
+58.2%
0.63x (?)

Dictionary4
159
201
+26.4%
0.79x (?)

ArrayInClass
195
215
+10.3%
0.91x (?)

PrefixAnySeqCRangeIter
13
14
+7.7%
0.93x (?)

PrefixWhileAnySequence
185
199
+7.6%
0.93x (?)

Added
MIN
MAX
MEAN
MAX_RSS

CxxVecU32.sum.Cxx.rangedForLoop
81
81
81
—

CxxVecU32.sum.Swift.forInLoop
62
63
62
—

CxxVecU32.sum.Swift.iteratorLoop
81
81
81
—

CxxVecU32.sum.Swift.reduce
61
62
61
—

CxxVecU32.sum.Swift.subscriptLoop
81
81
81
—

Code size: -Osize

Regression
OLD
NEW
DELTA
RATIO

CxxVectorSum.o
70
8618
+12211.3%
0.01x

Performance (x86_64): -Onone

Regression
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStubNSDateRefAccess
3175
3555
+12.0%
0.89x (?)

Added
MIN
MAX
MEAN
MAX_RSS

CxxVecU32.sum.Cxx.rangedForLoop
1584
1614
1595
—

CxxVecU32.sum.Swift.forInLoop
7760
8695
8184
—

CxxVecU32.sum.Swift.iteratorLoop
1890
2163
2021
—

CxxVecU32.sum.Swift.reduce
9473
9708
9554
—

CxxVecU32.sum.Swift.subscriptLoop
1783
1894
1820
—

Code size: -swiftlibs

✅
Benchmark Check Report

⚠🔤
CxxVecU32.sum.Swift.forInLoop name is composed of 5 words.  Split CxxVecU32.sum.Swift.forInLoop name into dot-separated groups and variants. See http://bit.ly/BenchmarkNaming

⛔⏱
CxxVecU32.sum.Swift.forInLoop has setup overhead of 6 μs (23.1%).  Move initialization of benchmark data to the setUpFunction registered in BenchmarkInfo.

⚠🔤
CxxVecU32.sum.Cxx.rangedForLoop name is composed of 5 words.  Split CxxVecU32.sum.Cxx.rangedForLoop name into dot-separated groups and variants. See http://bit.ly/BenchmarkNaming

⚠⏱
CxxVecU32.sum.Cxx.rangedForLoop execution took 10 μs.  Increase the workload of CxxVecU32.sum.Cxx.rangedForLoop to be more than 20 μs.

⚠⏱
CxxVecU32.sum.Swift.iteratorLoop execution took 11 μs.  Increase the workload of CxxVecU32.sum.Swift.iteratorLoop to be more than 20 μs.

⚠⏱
CxxVecU32.sum.Swift.subscriptLoop execution took 11 μs.  Increase the workload of CxxVecU32.sum.Swift.subscriptLoop to be more than 20 μs.

⛔⏱
CxxVecU32.sum.Swift.reduce has setup overhead of 6 μs (23.1%).  Move initialization of benchmark data to the setUpFunction registered in BenchmarkInfo.

⚠Ⓜ
CxxVecU32.sum.Swift.reduce has very wide range of memory used between independent, repeated measurements.  CxxVecU32.sum.Swift.reduce mem_pages [i1, i2]: min=[55, 55] 𝚫=0 R=[0, 57]

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 32 GB

@swift-ci please test macOS platform

@swift-ci please test

@swift-ci please benchmark

@swift-ci please build toolchain

@swift-ci please build toolchain

Results:
Performance (x86_64): -O

Regression
OLD
NEW
DELTA
RATIO

LineSink.characters.alpha
67
85
+26.9%
0.79x

FlattenListLoop
1128
1222
+8.3%
0.92x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
4553
3931
-13.7%
1.16x (?)

Added
MIN
MAX
MEAN
MAX_RSS

CxxVecU32.sum.Cxx.rangedForLoop
9
9
9
—

CxxVecU32.sum.Swift.forInLoop
21
21
21
—

CxxVecU32.sum.Swift.iteratorLoop
12
13
13
—

CxxVecU32.sum.Swift.reduce
25
33
28
—

CxxVecU32.sum.Swift.subscriptLoop
10
13
12
—

Code size: -O

Regression
OLD
NEW
DELTA
RATIO

CxxVectorSum.o
78
10256
+13048.6%
0.01x

Performance (x86_64): -Osize

Regression
OLD
NEW
DELTA
RATIO

FlattenListLoop
975
1380
+41.5%
0.71x (?)

Dictionary4
157
203
+29.3%
0.77x (?)

StringWalk
1240
1360
+9.7%
0.91x (?)

PrefixWhileAnySequence
185
199
+7.6%
0.93x (?)

PrefixWhileSequence
185
199
+7.6%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

PrefixAnySeqCntRange
16
14
-12.5%
1.14x (?)

Added
MIN
MAX
MEAN
MAX_RSS

CxxVecU32.sum.Cxx.rangedForLoop
76
78
77
—

CxxVecU32.sum.Swift.forInLoop
58
59
58
—

CxxVecU32.sum.Swift.iteratorLoop
76
77
76
—

CxxVecU32.sum.Swift.reduce
60
61
60
—

CxxVecU32.sum.Swift.subscriptLoop
76
76
76
—

Code size: -Osize

Regression
OLD
NEW
DELTA
RATIO

CxxVectorSum.o
70
8618
+12211.3%
0.01x

Performance (x86_64): -Onone

Added
MIN
MAX
MEAN
MAX_RSS

CxxVecU32.sum.Cxx.rangedForLoop
1697
1702
1699
—

CxxVecU32.sum.Swift.forInLoop
7612
8061
7876
—

CxxVecU32.sum.Swift.iteratorLoop
1777
1832
1808
—

CxxVecU32.sum.Swift.reduce
9524
9753
9612
—

CxxVecU32.sum.Swift.subscriptLoop
1774
1813
1790
—

Code size: -swiftlibs

✅
Benchmark Check Report

⚠⏱
CxxVecU32.sum.Swift.subscriptLoop execution took 11 μs.  Increase the workload of CxxVecU32.sum.Swift.subscriptLoop to be more than 20 μs.

⚠🔤
CxxVecU32.sum.Swift.forInLoop name is composed of 5 words.  Split CxxVecU32.sum.Swift.forInLoop name into dot-separated groups and variants. See http://bit.ly/BenchmarkNaming

⛔⏱
CxxVecU32.sum.Swift.forInLoop has setup overhead of 2 μs (8.0%).  Move initialization of benchmark data to the setUpFunction registered in BenchmarkInfo.

⚠⏱
CxxVecU32.sum.Swift.iteratorLoop execution took 10 μs.  Increase the workload of CxxVecU32.sum.Swift.iteratorLoop to be more than 20 μs.

⚠🔤
CxxVecU32.sum.Cxx.rangedForLoop name is composed of 5 words.  Split CxxVecU32.sum.Cxx.rangedForLoop name into dot-separated groups and variants. See http://bit.ly/BenchmarkNaming

⚠⏱
CxxVecU32.sum.Cxx.rangedForLoop execution took 10 μs.  Increase the workload of CxxVecU32.sum.Cxx.rangedForLoop to be more than 20 μs.

⛔⏱
CxxVecU32.sum.Swift.reduce has setup overhead of 4 μs (15.4%).  Move initialization of benchmark data to the setUpFunction registered in BenchmarkInfo.

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 32 GB

@swift-ci please test windows platform


Wrong output with Ryzen

Hi.
Used the latest release of Avisynth+ with avsresize and HDRTools. avsresize compiled with the latest zimg.
FFVideoSource()
z_ConvertFormat(pixel_type="RGBPS", resample_filter_uv="spline36", colorspace_op="2020:st2084:2020:l=>rgb:linear:2020:l")
z_ConvertFormat(colorspace_op="rgb:linear:2020:l=>rgb:st2084:2020:l")
ConvertRGbtoXYZ(Color=0, Outputmode=2)
ConvertXYZ_Reinhard_HDRtoSDR(exposure_x=5,contrast_x=0.9)
RGBAdjust(rg=0.95,gg=0.95,bg=0.95)
ConvertXYZtoYUV(color=2)

Intel 7900x output vs Ryzen 2700x output
Source image
When avsresize is compiled from this tree, the output is identical from both Intel and AMD.
When avsresize is compiled from this tree, the AMD output is wrong.
avsresize by default is compiled with zimg approximate_gamma = 1. When it's compiled with the latest zimg and approximate_gamma = 0, the output is identical from both Intel and AMD.
Also with ZIMG_CPU_NONE and the latest zimg the output is identical.

Actually, this is not specific to Zen1 processor. What is happening is that the SSE code path for transfer-function lookup does not have enough precision for HDR, because it uses uniform quantization of the LUT. This can happen on pre-AVX2 Intel CPUs too. For Zen1, we can put the code path back to AVX2 (and you can do this manually), but the problem is still not really solved.

Thinking about this further, is this a problem on an HDR display, or is it only apparent when viewing the ST.2084 image on a non-HDR display? This banding artifact occurs primarily in very low light levels.

non-HDR display is used.

I mean that the artifact you discovered might not be visible when viewing the HDR as intended. It turns out not to matter though, since I found a solution.

I don't have HDR display, so can't test what the output would be.
Anyway, the solution is ok, no problems anymore.
It seems this is resolved.
Thanks.


Feature - new blocklisting capabilities based on the data_name for data sources

To accomodate with more use cases, provide a new blocklisting capability to blocklist entities based on the data_name value

Version 1.2.35 is now live.


Updates dev dependencies

OVERVIEW
Updates the dev dependencies to the latest available versions.
WHERE SHOULD THE REVIEWER START?
package.json
HOW CAN THIS BE MANUALLY TESTED?
Run yarn review and verify lint and tests pass
ANY NEW DEPENDENCIES ADDED?
No additions, but several updates.
CHECKLIST
Be sure all items are ✅ before submitting a PR for review.

[x] Verify the linter and tests pass: npm run review
[x] Verify this branch is rebased with the latest master

GIF

It should work fine with v1. I don't know that it is specifically necessary to list as a peer dep though. I think of peer deps as "this won't function with that". Technically, nothing in this lib is directly connected to styled-components functions. It's just designed to work with how SC calls things.


ReferenceError: ElementQueries is not defined.

When I upgrade to 1.2.5 or 1.2.6 (from 1.2.4), I start receiving this error:
ReferenceError: ElementQueries is not defined.
There is a commented out global ElementQueries: false in anguar-gantt-plugins.js within gantt.resizeSensor and several references to ElementQueries.update() in the resizeSensor plugin that the error stems from.
Adding https://github.com/marcj/css-element-queries removes the errors and appears to work.  Any reason this dependency should not be added to the bower.json?

Answer is in the question. We have choosen to not add plugins dependencies in bower.json.


[GDNative] even more API fixes

closes #12253
Also adds the godot_pluginscript_register_language method to the API struct, which @touilleMan forgot to do 😛

reaaaaally ??? :cry:


Trung Dan git part B

the tests are not run because there are conflicts, you need to fix them. Check the readme on how to do it.

:+1:


Workflow should not trigger on own comments

The backport-action bot added comments to PRs contain "/backport". This could result in the backport workflow being triggered again, causing an infinite loop of backport messages. By checking the user id of the comment we can prevent comments from backport-action triggering the workflow.

Let me know if you'd rather have the check be github.event.comment.user.login != "backport-action" instead.


Driver over WebSocket instead of VMService

Internal: b/140286752
It would be interesting to provide a way to run Flutter Driver tests over a WebSocket connection instead of the VM Service protocol. That would allow it to be used in release builds, for example.
This would not be a feature that is enabled by default, and enabling it would have to involve some sort of out-of-band key exchange (with the driver extension generating part of the key) to ensure that only code that we expect to connect can connect. Or alternatively maybe the connection would be outgoing (you provide the endpoint to the driver extension). Or maybe you have to implement the endpoint logic and just hand in a socket or stream/sink pair.

I'll take this for now to investigate plausibility and design the API.

Tracked at Google by b/140286752.

See also #38329 which is about not requiring a driver process at all.

Internal bug 140286752 has been closed.


rotate-api-tokens.sh: add new commands change-ft-account-passwords and sync-ft-account-passwords

https://trello.com/c/AOxxcCSy
This was far more involved than I expected it to be, but doing it manually is annoying and error prone, so I wouldn't be beat.
change-ft-account-passwords will "detect" email/password combinations in a set of FT variables by looking for matching pairs of settings ending in _email and _password. It will then generate a new password for each account, separate accounts being determined by unique email address. A
github PR will then be created to apply these changes.
sync-ft-account-passwords will use the API to set the account passwords for any accounts found in a set of FT variables (detected in the same way).
Doing it this way allows separate accounts to be used for the different test variants, new classes of accounts could be added, or some accounts could be omitted entirely for certain variants and the scripts should continue to operate robustly & agnostically.
Coming soon - a basic jenkins job for driving this.

I've now done a full run of this script via jenkins for preview and it worked.

I've run this for all 3 environments now and it works.

Yeah I guess so, we already have some limited wrappers for sops in -utils


Action: azureFunctions.deploy Error

The issue text was copied to the clipboard.  Please paste it into this window.
  Does this occur consistently?  Repro steps:   1. 2.  Action: azureFunctions.deploy Error type: AuthorizationFailed Error Message: The client<EMAIL_ADDRESS>with object id '006022c1-a7fb-43fd-b5a8-e1f3e57b9ef2' does not have authorization to perform action 'Microsoft.Web/sites/read' over scope '/subscriptions/8254cfcc-22cc-4e2f-867f-1235ba2ea380' or the scope is invalid. If access was recently granted, please refresh your credentials.   Any idea what? As a workaround, you can try the "Advanced" option when creating a function app
Could be related to https://github.com/microsoft/vscode-azureappservice/issues/1490


replace special chars in user names

so the username can be used as the name of the User resource as well as the label value

let me close this one - it should rather fail if the name is not compliant than doing some additional replacements

the correct fix is here: https://github.com/kubesaw/ksctl/pull/94


Fix: Handle volumes with no tags

Currently the script will fail if you have any available volumes without tags. This fixes the issue

Pushed another commit because the script will also currently create snapshots of every available volume, not just the ones that match the instance name.

Thanks for that @srichter :) Your changes make a lot of sense and improve the script! Very much appreciated and accepted.


PrestoDB docker image

Marathon tasks to setup cluster you can find here: https://github.com/pubnative/marathon-tasks/commit/38a2ec8fc603e18b6cbe969ff8cbee3afb0ca29e
Airpal already switched to the cluster on Mesos: https://github.com/pubnative/marathon-tasks/commit/0ff7ce30517d44f33c5b0e73a067afb9c524f060

👍


⚠ Mobitopup has degraded performance

In ec3f607, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 11485 ms

Resolved: Mobitopup performance has improved in 1368d7a.


License should be for datarockets

Create a new license that will keep gem's rights under DR company

I think MIT license is quite enough for us. But we need to correct it a little bit (e.g. change the owner)

Sounds good 👍


$ElementType<T, K> indexable signature not found for Class

$ElementType unable to run on classes.
declare class Lo { 	mapp<T, K : $Keys<T>>(array: T[], prop: K): $ElementType<T, K>[]; } class Device {     push_token: string } let devices: Device[] = [] let tokens = _.compact(_.mapp(devices, 'push_token'))
Errors with:
element type
Indexable signature not found in Device

Currently seeing this error on all my Class usage with $ElementType. Records are working fine.

Same issue, I am trying to create a simple ReadOnly type:
type ReadOnly<T> = {
  +[key: string]: $ElementType<T, key>
}

Additionally, I get identifier key (Could not resolve name) for the usage of key .

@jeffijoe that's not an issue with $ElementType, the only identifiers you can use must be declared in between the first set of angle brackets, like you've done with T. Something like:
type ReadOnly<T, K> = {
  +[K]: $ElementType<T, K>
}

Obviously that doesn't do what you want, but that's an unrelated issue.

@kidcosmic oddly enough, you can work around your issue by changing your Device class to extend Object:
Try flow
declare function mapp <T, K: $Keys<T>> (array: T[], prop: K): $ElementType<T, K>[];

class Device extends Object {
  push_token: string
}

let devices: Device[] = []
const a = mapp(devices, 'push_token');
(a: string[]);

@jcready oh lol there goes 40+ flow errors.
much appreciated sir.

@jcready Having the class extend from Object just to get index signature based types working seems a bit weird, is this classified as a bug?

@jeffijoe I would certainly classify it that way. Especially considering all classes in javascript extend Object already.

Some progress on this?

Workaround
class D {
  x: number
}

type S = $ElementType<$ReadOnly<D>, 'x'>

const m: S = ''

The issue seems to be fixed a long time ago


(maint) switched to macos-11

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

GitHub Release
NuGet Package
Your GitReleaseManager bot :package::rocket:


acos registry, gulimall-coupon register failed..

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
We recommend using English. If you are non-native English speaker, you can use the translation software.
Which Component
eg. Nacos Discovery, Sentinel
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
e.g.  MacOS  、Java8 、 Version 0.2.1.RELEASE

Please refer more information so that we can know why your service register failed


delete proposedApiFunction of createTerminalRenderer

delete proposedApiFunction of createTerminalRenderer

This is proposed API: https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts#L1127
Is there any discussion or history behind this?

You'll have to wait for the proposed API to be stabilized, before the extension can be published on the marketplace.
cc @Tyriar


fix: allow upgrading when history has nothing but failures

This is a Work In Progress. DO NOT MERGE IT.
It has long been possible for people to get their releases into a state where they could no longer successfully upgrade because they had failed enough times that no deployed releases are left in their history.
This can happen in the following ways:

They can install and fail (without --atomic), which leaves them with only one failed release
They can install successfully, but have supplied --wait, and failed when a pod did not come up (which will mark the deployment failed)
They can set their history to some low-ish number, and then perform enough failed releases in a row that no deployed ones exist

And there are probably others. All of these cases are exacerbated by CI/CD systems that naively install and then don't clean up after failures.
See #5595 for context
The Approach
The approach I took here was to attempt to leverage Helm 3's 3-way diff to recover from a broken release. (Note: This approach is not possible in Helm 2.)
In the usual prepareUpdate, Helm attempts to load the last deployed release from history. If none is found, the deployment fails. The proposed fix here extends that logic:

If the deployed release exists, use that release
If a deployed release does NOT exist, try to load the last release and use that, regardless of whether it failed
If both loads fail, the release fails

The wager here is that even if there is a failed release, the 3-way diff will be able to detect the changes in cluster and recover from the potentially inaccurate release manifest.
I am proposing this as a bug fix, as it fixes a case that cannot currently be accounted for at all (when history gets truncated, and only failed releases are left). It seems to me that if this route does not introduce any anomalous behavior, it is right to make it the default action taken. I think it would be a patently bad idea to add yet another flag to the already misleading jumble of flags hanging off of helm update.
We need to look very carefully at this approach.

Does it solve the problem of history + failed releases?
Does it break expected behavior?
Does it introduce new possible bugs by diffing against a failed manifest?

A few misc notes:

This should work fine paired with --atomic, since it will not trigger the atomic rollback condition unless there is a new failure.
This should work with --cleanup-on-fail, which will remove broken resources, since this continues to use the existing diff logic
This will work with any version of --history-max greater than or equal to 1.
When --reuse-values is set, this will use values that were set on the last failed update
How do we verify its behavior?

Example
I have a chart called alwaysfails, which is basically helm create alwaysfails with the values.yaml setting image to nosuchimage9999.
# Run this command as often as you like
$ helm3 upgrade --install alwaysfails ./alwaysfails --debug --wait --timeout=5s
# Then remove the `--wait --timeout=5s`
$ helm3 upgrade --install alwaysfails ./alwaysfails --debug

I ran three failed releases, and a successful 4th.
Since removing the wait will mark the deployment successful, you will see this in history:
$ helm3 history alwaysfails
REVISION	UPDATED                 	STATUS    	CHART            	APP VERSION	DESCRIPTION
1       	Mon Apr 13 19:33:24 2020	failed    	alwaysfails-0.1.0	1.16.0     	Release "alwaysfails" failed: timed out waiting for the condition
2       	Mon Apr 13 19:33:32 2020	failed    	alwaysfails-0.1.0	1.16.0     	Upgrade "alwaysfails" failed: timed out waiting for the condition
3       	Mon Apr 13 19:33:39 2020	superseded	alwaysfails-0.1.0	1.16.0     	Upgrade "alwaysfails" failed: timed out waiting for the condition
4       	Mon Apr 13 19:35:27 2020	deployed  	alwaysfails-0.1.0	1.16.0     	Upgrade complete

(Note that it does currently mark the recovered release as superseded instead of failed. We could change that. Not sure what the utility is either way.)
Signed-off-by: Matt Butcher<EMAIL_ADDRESS>

I just learned about Draft PRs today, if you're interested: https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft

similar PR #7767 about rollback, need to get reviewer

With Helm 2, @adamreese and I paired on this particular case. It's a doozy.
Together, we introduced https://github.com/helm/helm/pull/3097 to prevent cases where a failed deployment could not be reconciled simply because Helm 2 could not reconcile against the live state of the cluster.
This is likely the most controversial pull request we ever merged into Helm as seen with https://github.com/helm/helm/issues/3353#issuecomment-358367529. For posterity, those issues were #2257, #2341, #2346, #2437, and #3068, but there are likely others.
Now that we can reconcile against the live state of the cluster in Helm 3, I think it's fine to relax this constraint as we can at least perform some form of reconciliation with the last failed release.
If you wouldn't mind looking through those past issues and see if there may be any cases that might not be addressed by this proposal, that'd be wonderful. I'm all for this but perhaps there may be some case I'm forgetting back when Helm 2 used to diff against the last failed release that might be worth looking into.

This is solved by #7653 as well.

Yeah, it looks like this takes a pretty similar approach to #7653, but without introducing a new flag. When I looked at that PR, I got about as far as the help text, and the description made it sound  highly dangerous. The help text in that PR suggest that that version is not production-safe... and I am wondering why @yinzara.
I'm getting concerned that the sheer number of combinatorics on the helm upgrade command are making it so complicated that we are never going to be able to solve this problem. (And, let's be honest, a huge part of this problem is just the design of Kubernetes.)
For example, depending on which combination of --install --atomic, --wait, --force, --reuse-values, --recreate, --timeout, you can get the exact same chart + values to end up in any number of different states over time. We somehow have to get the default Helm behavior to be sane enough that this is not the responsibility of the user to untangle all of the flags.
Issue #5595 is a good example: People naively think that because they all got a similar error message, they are all hitting the same "bug." But if you read through the thread, you will see there there are dozens of minuscule differences in flags + history depth + expectations that are leading to a variety of actual runtime conditions that are "not desired". In the end, releases they believe should be running or recoverable are not -- but the causes are variegated, massively compounded by the complexity of all of the flags.
I don't particularly have strong feelings about whether it is better to go ahead with a slightly modified version of #7653 or with this. But I am going to spend some time analyzing how dangerous this approach actually is -- and whether the new diffing strategy in Helm 3 can actually do an adequate job. If it can't then perhaps we do use #7653 as-is and just let people live on the edge. (Which, no doubt, will just produce new acrimonious threads with people accusing us of neglect, ignorance, and malice like they are in #5595.) But if we can show this solution to be reasonably effective, I think we should fix it as part of the core.
Finally, I am still on the fence about --atomic. Maybe we have to start telling people, "look, there is no recovery story for failing a helm install unless you use --atomic." That actually sounds reasonable to me. But I have reservations that --atomic is all that reliable in all cases. Rollbacks are not time machines (as @bridgetkromhout likes to say). They come with their own set of difficulties. Are they acceptable difficulties? Perhaps. Might we be able to just skip this particular problem and rely on --atomic? I am not sure.

The solution in #7767 is to just treat the current release as the last release. That is an interesting proposal as well, though I think that in some cases it will orphan objects that were created by a previous release. Might be good to investigate that approach as well, though.

Okay @adamreese and I paired on this for a few hours today, and looked deeply into the patching code. We did find a few minor things that needed fixing. Specifically, the diffing logic was too likely to leave the release in an unstable state because it was too conservative in deletions. So we are looking into a fix for that, but will do that in a separate PR.
We also looked at the case where the new chart added an object that the old (possibly failed) release did not have, but that exists in the cluster. We decided to retain the current behavior, which is that this case should fail. Otherwise we could accidentally adopt a resource that Helm was not intended to manage. But this could present an edge case if we go ahead with this proposal.
@yinzara are you interested in updating your PR to remove the flag? And maybe to use a typed error? After pair-reviewing this with @adamreese, we think this approach will work well enough that we don't need a flag. And since your patch landed before mine, I'm good with continuing with yours. We left a couple of comments on your PR, but they were all easy to fix -- especially if the u.Replace flag is removed.
We think only the following release statuses are acceptable to recover from (so both of our proposed fixes are wrong as-is):

Failed
Superseded

But it is unclear whether you can actually ever get a Superseded without first finding a Deployed. So probably just Failed. (Deleted and all of the Pending* ones will introduce additional issues in the diff/merge logic.)

I'm happy to update the PR to whatever you'd like.  I'm confused what you mean by using a typed error instead of a flag?

Oh wait. I think you're saying to just make this the default behavior and to not introduce the flag but limit it only to the Failed and Superseded statuses.  No issues. I'll handle that.  And what you mean a typed error? I'm not 100% sure what you're referring to. Which error? You mean if there is only one in another status? or?

Closing in favor of #7653


Configure Awake to enabled during working hours only

Description of the new feature / enhancement
I'm using Awake to override my company's group policy and prevent it from turning off monitors and locking after (what feels like only) 7 seconds. I'd like Awake to be enabled when I'm working (9-5pm, M-F) and currently the only time-based automation I see is to set the expiry date. With this I have to start it every day and change the expiry date to today.
I'd prefer to be able to set and forget, in other words configure the Active period to be within certain hours of every weekday. It would then enable itself during those hours and I no longer need to launch the PowerToys settings window every morning for myself.
Scenario when this would be used?
I would use such a new feature 100% of the time to automate when Awake is active and inactive. I would set it once, then forget about it. That would be perfect for me.
Supporting information
My support for this idea is that I'm currently getting frustrated with having to reopen the settings every morning to change the expiry date. So much so that I could conceivably see myself learning Powershell to modify the configuration and relaunch Awake and maybe create a Windows Task to run it (and I'm no Windows powershell user, so I don't even know if this is a possibility, but I'm close to losing a day's effort in researching it).

This feature would be fantastic, I have the same use case. I do have a question though. Assume I've set recurring for M-F 8-5 but I leave on PTO for a week. Does Awake operate even when the computer is locked? I assume not but asking as I wouldn't want my screen on/PC unlocked while I'm out of office.

I have been looking for this option since the day I discovered "Awake". I implemented a workaround by creating a scheduled task that triggers a Powershell script when my PC resumes from sleep. The script kills any running instances of Awake, then starts it again via the CLI and pass an expiration time (e.g. the end of my work day):
Get-Process Powertoys.Awake | Stop-Process
Start-Process -WindowStyle Minimized -FilePath "C:\Program Files\PowerToys\PowerToys.Awake.exe" -ArgumentList "--expire-at=17:30:00 --display-on=false"

The scheduled task is a little tricky to setup, since I had to find out the exact event id to which it should trigger. I chose this:

The action that I configured is:
Program/script: "C:\Program Files\PowerShell\7\pwsh.exe"
Add arguments: -NoProfile -ExecutionPolicy Bypass -File "<path-to-powershel-script>\Restart-Awake.ps1"
I hope this helps anyone while waiting for this feature to be implemented in Awake ;)

This appears to be an oft requested feature. Is anyone actively working to add this feature in a future version?

You can add a 'In-Progress' label on this. Per the contributing docs, I'm estimating a review in 3-4 weeks.
My fork: https://github.com/zskelton/PowerToys/tree/main

If anyone on the Awake team can give me a PM, it'd help to navigate the code versus trial/error/recompile. Specifically, I'm looking at when I compile just Awake, I can see the changes as the console app. But I have to compile the whole runner to get to see it in the tray. I'm certain I'm missing a step here but someone's assist would be easier than trial and error.
Thanks.

Tracking this conversation here: #24846


in chapter 4 (https://near.academy/near101/chapter-4) text is scrambled

Description:
in chapter 4 the usage of markdown to html cause the method to be seen as get meme count instead of get_meme_count probably due to faulty markdown translator.

also the 2. part is not in a new lone.

There are other issues with this and converting snake case to italics:

Thanks @BenKurrek, as discussed also happens with getmemelist / get_meme_list, which will probably trouble people completing Chapter 6

Thanks everyone! I've bundled the fixes for both Chapter 4 and Chapter 6 in the same PR #48


Create Advertisement Video

We need to create a 3-minute advertisement for our project.
Our project thankfully doesn't need to be done to create the video. Instead, we can focus on the "how, what, why and why not" per the documentation.
One approach might be something like:

Contributing to open-source is difficult. There are 100's to choose from, but how do you know the project you are choosing to contribute to has made it easy to do so?
Maintaining an open-source project is just as difficult. How to help prospective developers know your project is not just worth contributing to, but also easy?
Constable aims to fix this problem. The goal of constable is to provide a simple letter grade score for a repository to let developers know how "contributable" the project is.
Initially being developed as a GitHub action - making it super simple to add to your project! - the goal is to make it easy for project maintainers to see the score for their project, check it with every change, and even create a badge to show off on their README.md
If you care about helping the open-source community continue to make it easier for everyone to contribute to projects, consider using (and contributing to) Constable!

More thoughts:

how this helps YOU!
what it does now
what we hope it does in the future


Develop

I created a pr to your dev branch. i dont' have merge privilege

I'll fix AppVeyour and deploy next package version soon

I'll fix AppVeyor and then I'll deploy the package to Nuget
Thx

1.1.0 is released on Nuget.org

Thanks!


⚠ Bofrost.lu has degraded performance

In 799811d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1511 ms

Resolved: Bofrost.lu performance has improved in 64258b2 after 6 minutes.


Ignore both swSrc and swDest when globbing for the manifest

R: @philipwalton
Fixes #2229
We previously had some code that ensured that swDest was omitted from the glob matches when generating the precache manifest.
This extends that to also ignore swSrc in injectManifest mode.
I also improved the that generates the globIgnores value so that instead of just matching anything that has the same basename as swSrc/swDest, it actually uses a full path to the file, relative to globDirectory. This should reduce the chance of a false positive.

Actually, let me extend this to ignore the workbox-*.js runtime files that are generated, too.

Coverage decreased (-0.3%) to 78.992% when pulling 477a48cff7ce07cd2933bec4b281a20b37ebafff on better-glob-ignores into 4486dfff1cb268472ddc15e3c7833c3b79ce6488 on master.


feat: add Lighthouse Reports

Depends on https://github.com/ohdearapp/ohdear-php-sdk/pull/31

Is this one ready to merge now too?

Now it is, here's how it looks:

Very nice!


feat(notify): 管理后台新建的联系人，手机号和邮箱无需进行校验

这个 PR 实现什么功能/修复什么问题:
管理后台新建的联系人，手机号和邮箱无需进行校验

[x] 功能、bugfix描述
[x] 冒烟测试

是否需要 backport 到之前的 release 分支:

release/3.7

/area notify
/cc @zexi @swordqiu

Codecov Report

Merging #10638 (623f1f1) into master (e4a47a1) will increase coverage by 1.91%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #10638       +/-   ##
===========================================
+ Coverage    5.90%    7.82%    +1.91%
===========================================
  Files         866      110      -756
  Lines      135100    13477   -121623
===========================================
- Hits         7974     1054     -6920
+ Misses     126421    12303   -114118
+ Partials      705      120      -585

Flag
Coverage Δ

aFlag
7.82% <ø> (+1.91%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/syncworkers.go

pkg/compute/models/elasticcacheresource.go

pkg/mcclient/options/k8s/service.go

pkg/util/samlutils/request.go

pkg/util/influxdb/influxdb.go

pkg/cloudcommon/db/fieldtags.go

pkg/hostman/guestfs/fsdriver/base.go

pkg/compute/models/skus.go

pkg/compute/models/loadbalanceraclresource.go

pkg/compute/models/loadbalancerhuaweicachedlbbg.go

... and 746 more

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 e4a47a1...623f1f1. Read the comment docs.


Remove dependency CAPM3RELEASE variable from metal3-dev-env

What steps did you take and what happened:
When doing minor releases it's impossible to test the following PRs:

https://github.com/metal3-io/metal3-dev-env/pull/1485/files
https://github.com/metal3-io/cluster-api-provider-metal3/pull/2164/files

We always have to merge one without running any tests. The reason is CAPM3RELEASE variable, we set this variable in metal3-dev-env but configs for this variable are in CAPM3.
What did you expect to happen:
These PRs should not be dependent on each other and we should be able to run the tests.
Possible fix:
Set the value of CAPM3RELEASE in CAPM3 ci-e2e.sh script and metal3-dev-env should set the value only when there no default value coming from CAPM3.
/kind improvement

/triage accepted
This was hit, once again, after 1.9 minor was cut.


Using maps part 2 (out of probably 3): converts address to latitude, longitude and sends to datastore

Otherwise, LGTM.

@meagancheese l got that json from https://mapstyle.withgoogle.com/ . l think it'd be in accordance with the style guides since it's from a Google Site, so l'll just leave it as is. Plus, it'd be a hassle to change ~200 lines


timeout error message when transaction went through

Location
transaction processing
Expected behavior
when the transaction is succesfull i get a message "transaction was sent"
Never show an error message when a transaction went through.
Actual behavior
I got an error message saying "there was a time out"
Steps to reproduce the problem
send SWT
The fact that i got an error message made me redo the action, in the end sending the SWT twice.
Operating system / hardware

tested this today, bug still there.

check


move image CRUD operations to AWS

Get images from s3 bucket now works properly, still need to implement error handling


Support labels for containers

This PR adds basic support (without interpolation) for labels at deployment time. These are useful in pretty much all modern Docker deployments.
cc @dselans

What's going to happen when you use labels but deploy to hosts that do not support labels?

Try it, I don't know and I don't have access to a 1.5 Docker daemon to try it. I think Docker will just ignore them.

Want to merge this, but don't want to break things for you @dselans

@actaeon I'd love to merge this but don't want to break things for you guys running Docker 1.5. I don't have 1.5 to test with. Can you or someone else there validate it? Much appreciated.

@relistan offsite this week :) , will look at it Monday.

Thanks @actaeon !

Ping @actaeon

@intjonathan @actaeon @spkane can one of you guys let me know if this is mergeable? Thanks!

Docker 1.5 is very much end of life, we're not running it internally any longer and at this point it seems nobody should. Concerns about compatibility with it have expired too.

@relistan Can you weigh in on whether this should be in a 1.9 or 1.8.10?

@intjonathan good, glad no one is running 1.5 :) . Since this is a minor feature addition I'd ship it as 1.8.10. 👍


GUI detection of motion is not sensitive enough

I think that the "motion" outline on the gui should:

Be binary, not brighter/darker depending on how much motion
Should be a lot more sensitive

I tend to find that its not sensitive enough, I have to really move the trackers when I do it.

I think it only checks for movement on one axis? Since when I was assembling my BNO085 carrier boards, i had to wave them long-wise to get it to light up. That, or that was just the only axis I was able to get it fast enough with. 🤔

Would using the accel work? So people can move their trackers without rotating them and it'd register movement...

Hmm, that could also work well. As long as you keep the gyro sensing as well since not everyone has accelerometers in their DIYs.

I think both should be used


ArgumentError: comparison of NilClass with 7 failed

Environment:
elasticsearch: v1.6.2
gem elasticsearch-rails: d6e534c7b3ae
rails: 4.2.1
Backtrace:
[GEM HOME]/bundler/gems/elasticsearch-rails-d6e534c7b3ae/elasticsearch-model/lib/elasticsearch/model/adapters/active_record.rb:28 in sort_by
[GEM HOME]/bundler/gems/elasticsearch-rails-d6e534c7b3ae/elasticsearch-model/lib/elasticsearch/model/adapters/active_record.rb:28 in block (2 levels) in records
/gems/activerecord-4.2.1/lib/active_record/relation/delegation.rb:46 in map
[APP TRACE]

Steps to reproduce:

Add sleep 10 in elasticsearch-model/lib/elasticsearch/model/adapters/active_record.rb:17 to make the following steps more stable
Perform search records = Model.search(criteria).records.records
Create new record matching the search criteria
Wait until sleep 10 is running
=>
from [GEM HOME]/bundler/gems/elasticsearch-rails-d6e534c7b3ae/elasticsearch-model/lib/elasticsearch/model/adapters/active_record.rb:29:in sort_by'  from [GEM HOME]/bundler/gems/elasticsearch-rails-d6e534c7b3ae/elasticsearch-model/lib/elasticsearch/model/adapters/active_record.rb:29:in block (2 levels) in records'
from [GEM HOME]/gems/activerecord-4.2.1/lib/active_record/relation.rb:629:in `inspect'

I think this happens because sql_records and response.response['hits']['hits'] have different IDs because we make two separate calls to the ES for the results:
sql_records = klass.where(klass.primary_key => ids) # <--- first call
sql_records.instance_exec(response.response['hits']['hits']) do ... # <--- second call
I paste the code for clarity below:
 # lib/elasticsearch/model/adapters/active_record.rb
module Records
  # Returns an `ActiveRecord::Relation` instance
  #
  def records
    sql_records = klass.where(klass.primary_key => ids)

    # Re-order records based on the order from Elasticsearch hits
    # by redefining `to_a`, unless the user has called `order()`
    #
sleep 10
    sql_records.instance_exec(response.response['hits']['hits']) do |hits|
      define_singleton_method :to_a do
        if defined?(::ActiveRecord) && ::ActiveRecord::VERSION::MAJOR >= 4
          self.load
        else
          self.__send__(:exec_queries)
        end
        @records.sort_by { |record| hits.index { |hit| hit['_id'].to_s == record.id.to_s } }
      end
    end

    sql_records
  end
end

Maybe we can cache search.response to make sql_records consistent with ES response IDs?

Closing this as it is out-of-date.


About MailSender

Sometimes I don't need to cc to others , but the code have to do that.
If I remove the cc tag, it will return the error.

also add a bcc option. make cc and bcc optional

If you add the cc tag and leave it empty, do you still have the error?

I've fixed the issue in the new version 2.5.


amazon polly - add neural support

This is my second attempt at this. I first created a dev environment and a branch within my fork and pushed the changes to it. Then I created a PR from the branch. Hopefully I did it right.
Please delete the old PR. I couldn't figure out how to fix the git issues with it: https://github.com/home-assistant/home-assistant/pull/26836
Breaking Change: None
Description:
Adds neural support.  Neural only work with the proper combinations of features such as voice and region. See the official docs. I'll probably put a note about this in the hass docs PR I submit.
https://docs.aws.amazon.com/en_pv/polly/latest/dg/NTTS-main.html
https://aws.amazon.com/blogs/aws/amazon-polly-introduces-neural-text-to-speech-and-newscaster-style/
Related issue (if applicable):  none
Pull request with documentation for home-assistant.io (if applicable): https://github.com/home-assistant/home-assistant.io/pull/10547
Can someone confirm this is correct before I spend a bunch of time trying to update the docs? I previously screwed that up too because of "rebasing".
Example entry for configuration.yaml (if applicable):

tts:
  - platform: amazon_polly
    aws_access_key_id: x
    aws_secret_access_key: x
    voice: Joanna
    sample_rate: 24000
    engine: neural

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[ ] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

added docs to initial comment. also https://github.com/home-assistant/home-assistant.io/pull/10547


Update index.md

I just added that maybe we should change the programmers oath  with the changing of technology

[x ] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


PR documentation builds

Currently, if the environment variable MOCK_DOCS is set, the setup.py file will skip the building of the wheels. This is required for ReadTheDocs, where C++ extensions cannot be built.
Unfortunately, ReadTheDocs environment variables are not passed to PRs and forks, so we cannot activate the option to build the docs for PRs. An alternative option would be to simply mock out the C++ extensions in the conf.py file, like we do for The Walrus.

@josh146, do we still need something in setup.py that allows us to install PennyLane-Lightning without having things like Eigen?

@trbromley, with the new device, is this issue now closed?

@josh146 we still have MOCK_DOCS in setup.py so I believe it would still be a blocker for PR docs builds.
Could we remove MOCK_DOCS? :thinking: I'm not sure, the main difference with the new device is removing the Eigen dependency, but we still do load the C++ extensions within the if-statement. Probably the best option would be to follow what is done in the Walrus.

I believe you can now share env variables with PR builds: https://github.com/readthedocs/readthedocs.org/issues/7182#issuecomment-839037501. Will have a go!

Docs now build in each PR. Closing.


Playing only if selected

Hi,
I'm having an issue playing music: sound stream does not start unless i log onto the Spotify account via browser and select the Rasperry Pi device from the Spotify Connect popup menu ( bottom right corner in Spotify web player window ) and press the Play button. It's happening both in daemon mode and if run manually.
Running librespot manually with verbose option, I can see it stops a few steps after the volume setup:
[2021-03-16T16:45:15Z INFO  librespot] librespot (raspotify v0.16.0) 0adb851 (2020-12-15). Built on 2020-12-30. Build ID: KLdkAvgt
[2021-03-16T16:45:15Z DEBUG librespot_connect::discovery] Zeroconf server listening on <IP_ADDRESS>:39013
[2021-03-16T16:45:15Z INFO  librespot_core::session] Connecting to AP "gew1-accesspoint-e-jczs.ap.spotify.com:4070"
[2021-03-16T16:45:16Z INFO  librespot_core::session] Authenticated as "XXXXXXXXXXXXXXXXXXX" !
[2021-03-16T16:45:16Z DEBUG librespot_core::session] new Session[0]
[2021-03-16T16:45:16Z DEBUG librespot_connect::spirc] new Spirc[0]
[2021-03-16T16:45:16Z DEBUG librespot_connect::spirc] canonical_username: XXXXXXXXXXXXXXXXXXX
[2021-03-16T16:45:16Z DEBUG librespot_core::mercury] new MercuryManager
[2021-03-16T16:45:16Z DEBUG librespot_playback::player] new Player[0]
[2021-03-16T16:45:16Z INFO  librespot_playback::audio_backend::alsa] Using alsa sink
[2021-03-16T16:45:16Z DEBUG librespot_playback::player] command=AddEventSender
[2021-03-16T16:45:16Z DEBUG librespot_playback::player] command=VolumeSet(65535)
[2021-03-16T16:45:16Z DEBUG librespot_core::session] Session[0] strong=3 weak=2
[2021-03-16T16:45:16Z INFO  librespot_core::session] Country: "US"
[2021-03-16T16:45:16Z DEBUG librespot_core::mercury] unknown subscription uri=hm://remote/user/XXXXXXXXXXXXXXXXXXX/
[2021-03-16T16:45:16Z DEBUG librespot_core::mercury] subscribed uri=hm://remote/user/XXXXXXXXXXXXXXXXXXX/ count=0
[2021-03-16T16:47:16Z DEBUG librespot_core::session] Session[0] strong=3 weak=2
[2021-03-16T16:49:16Z DEBUG librespot_core::session] Session[0] strong=3 weak=2
[2021-03-16T16:51:16Z DEBUG librespot_core::session] Session[0] strong=3 weak=2
After the selection in the web browser, as described above, it plays without any problem.
Any idea?
Thanks,
Mimmo

Raspotify is a Connect client. It's meant to be remote controlled by a Spotify app. It functions kinda like a chromecast except just for Spotify. I'm not sure what you expect? Ofc you have to open the web interface or an app to make it start playback. Did you expect it to start playback by itself when the service started?


Duplicate entries for Wikidata

There appear to be two different prefixes for Wikidata that are not merged together. From what I understand, the fact that both of these have the synonym type "canonical" means that they are considered fully independent.
https://github.com/linkml/prefixmaps/blob/b8a2bbdf56cca5dec9d12e7cc4a9cf408736abeb/src/prefixmaps/data/merged.csv#L4541
https://github.com/linkml/prefixmaps/blob/b8a2bbdf56cca5dec9d12e7cc4a9cf408736abeb/src/prefixmaps/data/merged.csv#L4574

I'm not sure how we go about resolving this. We have two different prefixes from different sources with different URL's. The optimal solution would be to push this upstream and get them to agree, at least on the canonical URL. Otherwise, I feel like we're stuck with making arbitrary decisions in prefixmaps.
Am I missing something?


yq command fails and plgd bund des not run

The plgd bundle fails to run starting from the latest commit 8fa49b1.
The issue was found in today's Comarch's nightly testing of CTT C2C test cases.
Command that we use to start the plgd bundle:
docker run -it --pull always --name plgd \
-e FQDN=test_plgd \
-e COAP_GATEWAY_HUB_ID=00000000-0000-0000-0000-000000000001 \
--network=host \
ghcr.io/plgd-dev/hub/bundle:vnext-8fa49b1

The output of the docker command shows that the run.sh script fails on each execution the yq command. After producing this output, the script exits, so the container does not run. Here is the output:
vnext-8fa49b1: Pulling from plgd-dev/hub/bundle
Digest: sha256:d5a6bab0fb0006b868862aec0406e8e165424f350c224dc09435a757c8ca47df
Status: Downloaded newer image for ghcr.io/plgd-dev/hub/bundle:vnext-8fa49b1
generating CA cert
generating GRPC internal cert
generating COAP-GW cert
generating NGINX cert
ROOT_CERT_PATH=/data/certs/root_ca.crt CA_POOL=/data/certs/ca.crt
/usr/local/bin/run.sh: line 136: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 142: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 148: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 155: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 161: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 167: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 175: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 181: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 187: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 195: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 201: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 207: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 215: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 221: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 227: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 235: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 241: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 247: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 255: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 261: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 267: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 275: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 281: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 287: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 295: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 301: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 307: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 315: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 321: /usr/bin/yq: Permission denied
/usr/local/bin/run.sh: line 327: /usr/bin/yq: Permission denied
Generating RSA private key, 4096 bit long modulus (2 primes)
...................................................................................................................................................................................................++++
....++++
e is 65537 (0x010001)
starting nats-server
Try to reconnect to nats(localhost:10001) 1
starting mongod
Try to reconnect to mongodb(localhost:10000) 1
starting nginx
starting oauth-server
/usr/local/bin/run.sh: line 451: /usr/bin/yq: Permission denied

The nightly testing is showing that recent commit 2f58016 has fixed the issue.

Pls reopen if the issue occurs again.


Update NanoVG

#228
This would update nanovg and side libs from upstream.
Updating Nanovg appeared, though, to introduce a very significant change in my rendering.
DPF current no patch

Before (update fontstash and stb_truetype only)

After (update all of nanovg)

I don't really see a difference in the rendering.
What am I missing?
It is impossible to review such big PRs. All fine to merge into develop if it just works as usual

The above, on newer NanoVG, draws the text larger by some amount like 10%.

The nanovg update would change the unit of font sizes.
The last edit resets it like before, which is pixel-based as opposed to em-based, so the update should be backward compatible.


Documentation

Uncomment this line and add some basic docs for everything.

Relevant discussion in #7

Some specific things I've noticed in the rendered docs:

There should be a platform-agnostic example on the docs landing page with a graphics example, probably exercising all bits of the embedded_graphics API (triangle, square, circle, text, image). This will get updated with a following char mode example when #27 is ready. A link to a runnable example demonstrating the same for each display mode would be good too.
To extend the previous point, there should be an explanation of the concept of display modes; this driver can't be used without choosing one!
There should be better links between types/other language constructs in the docs
Readme:

The image needs to go on a diet. It's huge at the moment.
graphics is on by default and no longer optional so should be de-listed

The re-exports list needs an audit. This is related to #5 so can probably be fixed over there
Should there be a description of how all the modules fit together?
builder needs a couple of examples. I suggest:

A default/basic one that just sets up a display in graphics mode with SPI
One that exercises as many of the builder options as possible that changes the display size, rotation and I2C address in I2C mode.

Each mode should have an explanation of what it does. Also worth mentioning that RawMode shouldn't be directly used and is only a helper for the builder.
borrow_iface_mut could use a short usage example.
Make sure each module has a more-than-one-line description of what it does, preferably with a code example.

borrow_iface_mut could use a short usage example.

Actually that should go away and the "DisplayProperties" (or whatever the name will end up to be in the end) should provide proper methods to change configuration and send data.

Cf. https://github.com/jamwaffles/ssd1306/pull/49


Activity

Looks like time to merge this in so @vladyslav-iosdev can work on his parts like #2056

@hboon i need to merge activity into train-leaves, and then rebase train-leaves to branche i working on, right?

Answered offline.

@hboon merged with the understanding that speed optimisation will be another PR

@James-Sangalli ok!


Disable VHost when host does not support vhost-net

#169
Disable VHost when host does not support vhost-net
Signed-off-by: zhangjie<EMAIL_ADDRESS>

@jiulongzaitian any progress on this ?

@jiulongzaitian Any updates on this?

Hi @jiulongzaitian - please could you update this PR with the feedback provided (and to resolve the merge conflict)?

Maybe @jiulongzaitian is not available right now - we'll give this another week, and then decide how we push forwards with it...

@jiulongzaitian Any updates?

Ping @jiulongzaitian.
Don't worry if you are not able to update this PR for whatever reason. But it would be useful if you could let us know if you do intend to update it, so we can decide what to do with this PR.

@jiulongzaitian If you are not available, we can assign another one take over this PR. That's all right

Hi @jiulongzaitian - no problem. Thanks for notifying us. In which case, I think we can use the Assisted PR Process here if anyone is willing to pick up this work?

https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md#assisted-pr-workflow

We're happy to support anyone who wants to have a go :-)

https://github.com/kata-containers/community#join-us

Thanks @caoruidong! I've assigned the PR (and the issue) to you too now.

@caoruidong I can see that you're working on this, please make sure you let us know when you're done reworking it, so that we can review it.


[ISSUE #2370] <Remove warning code in shenyu-plugin-global、shenyu-spi>

// Fixes #2370

optimize warning code
replace if with optional

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2397 (4a5ddfd) into master (eda5a06) will decrease coverage by 0.05%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##             master    #2397      +/-   ##
============================================
- Coverage     58.15%   58.09%   -0.06%
+ Complexity     3951     3948       -3
============================================
  Files           629      629
  Lines         18058    18062       +4
  Branches       1691     1690       -1
============================================
- Hits          10501    10493       -8
- Misses         6721     6733      +12
  Partials        836      836

Impacted Files
Coverage Δ

...nyu/plugin/cryptor/handler/CryptorRuleHandler.java
35.29% <ø> (ø)

...pache/shenyu/plugin/cryptor/utils/CryptorUtil.java
57.14% <0.00%> (-4.40%)
:arrow_down:

...ache/shenyu/plugin/global/cache/MetaDataCache.java
100.00% <100.00%> (ø)

...ava/org/apache/shenyu/spi/SpiExtensionFactory.java
100.00% <100.00%> (+60.00%)
:arrow_up:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
82.35% <0.00%> (-11.77%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
54.73% <0.00%> (-9.48%)
:arrow_down:

...he/shenyu/plugin/grpc/client/ShenyuGrpcClient.java
8.69% <0.00%> (-4.35%)
:arrow_down:

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
54.54% <0.00%> (-1.82%)
:arrow_down:

Continue to review full report at Codecov.

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


Concurrency: report errors on failures on Windows

The usage of libdispatch in Concurrency is dynamic - it does not
explicitly link against libdispatch and thus cannot directly invoke
dispatch_main.  While linking against dispatch would be ideal, this
should improve the current path.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test


Re: Toot

mastodon-ios-apps Template

GitHub Issue
App Store
Home Page

App ID:<PHONE_NUMBER>

Description

Mastoot is a beautiful, elegant, and performant Mastodon client app.

Developer Contact
Embed

Data
App Store Tools

Local

https://user-images.githubusercontent.com/43663476/211100570-21ea9f88-31af-4876-835f-d7cbf814b9d0.MOV


Creating Jupyter Docker image

Fixes issue SCE-1129.
Summary of changes:

added /jupyter/Dockerfile
modified readme.


Vsync no longer throttles rendering in v0.4.0

Bevy version
v0.4.0
Operating system & version
Arch Linux 5.9.11
What you did
use bevy::prelude::*;

fn main() {
    App::build()
        .add_plugins(DefaultPlugins)
        .add_plugin(bevy::diagnostic::FrameTimeDiagnosticsPlugin)
        .add_plugin(bevy::diagnostic::PrintDiagnosticsPlugin::default())
        .run();
}

What you expected to happen
Using Bevy v0.3.0:
❯ cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/bevy_vsync`
Diagnostics:
---------------------------------------------------------------------------------------------
frame_count                                                      : 64.000000   (avg 64.000000)

frame_time                                                       : 0.016700    (avg 0.016689)

fps                                                              : 59.950072   (avg 59.930779)

What actually happened
Using Bevy v0.4.0:
❯ cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.08s
     Running `target/debug/bevy_vsync`
Diagnostics:
---------------------------------------------------------------------------------------------
frame_count                                                      : 332.000000  (avg 332.000000)

frame_time                                                       : 0.002922    (avg 0.003053)

fps                                                              : 328.634749  (avg 328.075462)

Additional information
This was observed under X11.

I observed the same thing, on both X11 and Wayland.
I was wondering why a simple example was spinning my cpu at 100%, but then I saw that the app was running at ~1000fps

reverting this commit  seems to fix the problem

What gpus / drivers do you all have?

Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics (CML GT2) (0x9b41)

I use the standard i915 driver.
I don't know if it matters, but I am running the Sway Wayland compositor.

Interesting. Maybe mailbox vsync is broken on that setup? Normally if it was unsupported, wgpu would fall back to Fifo vsync (what we used before). Maybe the driver reports mailbox vsync as supported, but it's a broken impl?

mmh, with vulkaninfo I see these lines mentioning fifo and mailbox:
Present Modes: count = 4
		PRESENT_MODE_IMMEDIATE_KHR
		PRESENT_MODE_MAILBOX_KHR
		PRESENT_MODE_FIFO_KHR
		PRESENT_MODE_FIFO_RELAXED_KHR

So I guess that mailbox is at least advertised, but possibly broken?

I run vkcube with --present_mode set to 0 (immediate), 1 (mailbox) and 2 (fifo).
And for mailbox the cube is spinning ad fast as in immediate, as opposed to fifo.
So I think that the driver is really broken.

I won't have access to that computer until next year, but I have a similar setup on my laptop. I'll see if I can't reproduce the issue tonight.

I don't know much about Vulkan, but I was curious about this issue so I read some stuff about presentation modes.
As far as I understand, the mailbox mode does not guarantee a capped frame rate. Even in the wgpu definition of the enum the comments seem to imply so:
pub enum PresentMode {
    /// The presentation engine does **not** wait for a vertical blanking period and
    /// the request is presented immediately. This is a low-latency presentation mode,
    /// but visible tearing may be observed. Will fallback to `Fifo` if unavailable on the
    /// selected  platform and backend. Not optimal for mobile.
    Immediate = 0,
    /// The presentation engine waits for the next vertical blanking period to update
    /// the current image, but frames may be submitted without delay. This is a low-latency
    /// presentation mode and visible tearing will **not** be observed. Will fallback to `Fifo`
    /// if unavailable on the selected platform and backend. Not optimal for mobile.
    Mailbox = 1,
    /// The presentation engine waits for the next vertical blanking period to update
    /// the current image. The framerate will be capped at the display refresh rate,
    /// corresponding to the `VSync`. Tearing cannot be observed. Optimal for mobile.
    Fifo = 2,
}

I also read the following articles about it:

https://developer.samsung.com/sdp/blog/en-us/2019/07/26/vulkan-mobile-best-practice-how-to-configure-your-vulkan-swapchain
https://software.intel.com/content/www/us/en/develop/articles/api-without-secrets-introduction-to-vulkan-part-2.html?language=en#_Toc445674479

As far as I understand, with the mailbox presentation mode there is a capped 60fps frame rate only if the swap chain has  only two available images. Otherwise the application is free to present a new image in the mailbox without having to wait for vsync.
Is this correct? and if so, is it the case that there are only two images used by bevy? I am not sure where to look in the code to check.

Same behavior on my laptop which has Intel integrated graphics:
         apiVersion     = 4202641 (1.2.145)
         driverVersion  = 83898369 (0x5003001)
         vendorID       = 0x8086
         deviceID       = 0x5916
         deviceType     = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
         deviceName     = Intel(R) HD Graphics 620 (KBL GT2)

       Present Modes: count = 4
                PRESENT_MODE_IMMEDIATE_KHR
                PRESENT_MODE_MAILBOX_KHR
                PRESENT_MODE_FIFO_KHR
                PRESENT_MODE_FIFO_RELAXED_KHR

I was looking through the source of vkcube and found this:
https://github.com/KhronosGroup/Vulkan-Tools/blob/1f550ddec2f3519f3ee7fd9cb1941b5642796ae2/cube/cube.c#L1234-L1263
    // The FIFO present mode is guaranteed by the spec to be supported
    // and to have no tearing.  It's a great default present mode to use.
    VkPresentModeKHR swapchainPresentMode = VK_PRESENT_MODE_FIFO_KHR;

    //  There are times when you may wish to use another present mode.  The
    //  following code shows how to select them, and the comments provide some
    //  reasons you may wish to use them.
    //
    // It should be noted that Vulkan 1.0 doesn't provide a method for
    // synchronizing rendering with the presentation engine's display.  There
    // is a method provided for throttling rendering with the display, but
    // there are some presentation engines for which this method will not work.
    // If an application doesn't throttle its rendering, and if it renders much
    // faster than the refresh rate of the display, this can waste power on
    // mobile devices.  That is because power is being spent rendering images
    // that may never be seen.

    // VK_PRESENT_MODE_IMMEDIATE_KHR is for applications that don't care about
    // tearing, or have some way of synchronizing their rendering with the
    // display.
    // VK_PRESENT_MODE_MAILBOX_KHR may be useful for applications that
    // generally render a new presentable image every refresh cycle, but are
    // occasionally early.  In this case, the application wants the new image
    // to be displayed instead of the previously-queued-for-presentation image
    // that has not yet been displayed.
    // VK_PRESENT_MODE_FIFO_RELAXED_KHR is for applications that generally
    // render a new presentable image every refresh cycle, but are occasionally
    // late.  In this case (perhaps because of stuttering/latency concerns),
    // the application wants the late image to be immediately displayed, even
    // though that may mean some tearing.

So it sounds like the high framerate is to be expected and is in fact just mailbox working as intended, and if we wanted to cap rendering to 60 fps we need to either use FIFO, or wait manually. I'm curious, why did we switch to mailbox? @cart

I can confirm that mailbox vsync causes weird effects on my dell xps13 running fedora on X11. Maybe also relevant: I'm not running any kind of compositing (plain i3 window manager), so maybe Mailbox vsync is hitting some less-well supported codepath in the driver.
Symptom: reported fps is fluctuating between 60-100fps but motion is quite jerky (in my own project https://github.com/sim82/crystal_planes). It is hard to describe but it seems to skip frames frequently. Hardcoding vsync to fifo fixes the jerkyness and the fps is stable at 60. If it helps I can do some more analysis, e.g. run with compositing or get more timing information from the mainloop.
GPU0:
VkPhysicalDeviceProperties:
    apiVersion     = 4202627 (1.2.131)
    driverVersion  = 83890184 (0x5001008)
    vendorID       = 0x8086
    deviceID       = 0x5916
    deviceType     = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
    deviceName     = Intel(R) HD Graphics 620 (KBL GT2)

I changed the title, since vsync seems to actually still prevent tearing which is its main purpose.

I changed the title, since vsync seems to actually still prevent tearing which is its main purpose.

We switched to mailbox because it cut input latency, which in retrospect is probably just by nature of not blocking on vsync framerates.
wgpu examples use mailbox by default, and they do have built in frame limiting:
https://github.com/gfx-rs/wgpu-rs/blob/4c518912790ee011cebcd75e9879647554e3261c/examples/framework.rs#L235
We should probably do the same, but the "request redraw" approach they use will require some changes on our end (ex: breaking rendering out from the main schedule so it can be executed separately on-demand). There might be some nuance there because the current system was built under the assumption that rendering runs immediately after game logic. And the LAST stage runs after rendering. We'd need to decide how to handle that. These changes could either be very easy or very hard :smile:

We switched to mailbox because it cut input latency, which in retrospect is probably just by nature of not blocking on vsync framerates.
wgpu examples use mailbox by default, and they do have built in frame limiting:
https://github.com/gfx-rs/wgpu-rs/blob/4c518912790ee011cebcd75e9879647554e3261c/examples/framework.rs#L235
We should probably do the same, but the "request redraw" approach they use will require some changes on our end (ex: breaking rendering out from the main schedule so it can be executed separately on-demand). There might be some nuance there because the current system was built under the assumption that rendering runs immediately after game logic. And the LAST stage runs after rendering. We'd need to decide how to handle that. These changes could either be very easy or very hard :smile:

We switched to mailbox because it cut input latency, which in retrospect is probably just by nature of not blocking on vsync framerates.
wgpu examples use mailbox by default, and they do have built in frame limiting:
https://github.com/gfx-rs/wgpu-rs/blob/4c518912790ee011cebcd75e9879647554e3261c/examples/framework.rs#L235
We should probably do the same, but the "request redraw" approach they use will require some changes on our end (ex: breaking rendering out from the main schedule so it can be executed separately on-demand). There might be some nuance there because the current system was built under the assumption that rendering runs immediately after game logic. And the LAST stage runs after rendering. We'd need to decide how to handle that. These changes could either be very easy or very hard :smile:

We switched to mailbox because it cut input latency, which in retrospect is probably just by nature of not blocking on vsync framerates.
wgpu examples use mailbox by default, and they do have built in frame limiting:
https://github.com/gfx-rs/wgpu-rs/blob/4c518912790ee011cebcd75e9879647554e3261c/examples/framework.rs#L235
We should probably do the same, but the "request redraw" approach they use will require some changes on our end (ex: breaking rendering out from the main schedule so it can be executed separately on-demand). There might be some nuance there because the current system was built under the assumption that rendering runs immediately after game logic. And the LAST stage runs after rendering. We'd need to decide how to handle that. These changes could either be very easy or very hard :smile:

I am observing this issue on Windows 10 with nVidia GeForce card.

I am observing this issue on Windows 10 with nVidia GeForce card.

Same. Not sure I'm doing something wrong (I'm new to Bevy), but...

I have a NVidia GeForce RTX 2080. I guess it's a good card, and I use a 144Hz monitor, but but I can't see 1600fps so I'd like to have that fixed to vsync instead. :sweat_smile:

Same. Not sure I'm doing something wrong (I'm new to Bevy), but...

I have a NVidia GeForce RTX 2080. I guess it's a good card, and I use a 144Hz monitor, but but I can't see 1600fps so I'd like to have that fixed to vsync instead. :sweat_smile:

Short term I think the fix should be to revert to FIFO as the cost of no frame limiting is pretty high and the "fix" is easy. Medium term we should bake in some frame limiting (which will be slightly involved due to the issues mentioned above). Then we can flip back to "mailbox with fifo fallback".

Short term I think the fix should be to revert to FIFO as the cost of no frame limiting is pretty high and the "fix" is easy. Medium term we should bake in some frame limiting (which will be slightly involved due to the issues mentioned above). Then we can flip back to "mailbox with fifo fallback".

I'm also having this problem. Is there any kind of workaround or short term fix I can apply before the changes you mentioned have been made?

Considering that:

1/60 of a second is not a latency that impacts every game type (not at all for GUI applications);
Not every device can afford the extra power draw of mailbox;
Not every device is limited by 60Hz, and 1/144 second latency might be acceptable where 1/60 wasn't;
The nonscientific nature of the claims that <10 ms can be humanly perceived and affect your gameplay.

Considering all these factors, then I really think that this should be configurable parameter.

1/60 of a second is not a latency that impacts every game type (not at all for GUI applications);

If the GUI has draggable elements, you will notice the lag between the cursor moving and the draggable element moving. Even if it is just a single frame.

The nonscientific nature of the claims that <10 ms can be humanly perceived and affect your gameplay.

There is a reason VR headsets use framerates >60Hz. Even if it doesn't impact desktop gaming much, as far as I know it is noticable when you move your head in a VR headset. (Don't own one, so can't try to check for myself.)

There is a reason VR headsets use framerates >60Hz. Even if it doesn't impact desktop gaming much, as far as I know it is noticable when you move your head in a VR headset. (Don't own one, so can't try to check for myself.)

As I understand, it is not for latency, but for smoothness. Whether vsync is fifo or mailbox doesn't matter for VR.

@alice-i-cecile it seems like we can close this, no? Vsync is now configureable.


Reduce the requested CPU by half, move to 1.5*1024 for memory

Received a +1 on stg, merging ...

@joelddiaz, @ivanhorvath, approved #3066.


How can I remove cogs from being shown.

For example, let's say I have some cogs that I do not want to be on the help command, how would I go on removing the cog from the help command?

I would just add a cog check to not show it.
cog_check reference
    async def cog_check(self, ctx: commands.Context):
        if ctx.invoked_with != "help":
            return True

Gret! I will try this out.


Add ip6 tables

fixes #26

@agherzan @lorenzo-stoakes @michal-mazurek @telphan @petrosagg

superseded by https://github.com/resin-os/meta-resin/pull/290
Closing this one


Add support for isMapConatiner and isArrayContainer

according to swagger-codegen documentation and search in templates directory there should be isMapConatiner and isArrayContainer mustache variables. This PR sets the missing variables.

Thanks!


Enable multiple OpenID authentication providers

Is your feature request related to a problem? Please describe
Background: OpenID Connect (OIDC) is a standard protocol for authenticating users, and many common apps (Google, Facebook, ORCID, etc.) provide this service for other registered third-party apps to use. Users can confidently log in with their existing credentials to use the third-party, and the third-party app can be confident that an authenticated user is accessing its services.
Current State: H2O Wave supports OIDC authentication with optional command line arguments passed to the waved server at startup. This enables Single Sign On functionality for the wave apps.
Feature Upgrade: Apps often need to offer multiple OIDC sign-on options to users, because this increases the likelihood that the user has an account with one of the sign-on services. Enabling the developer to configure multiple OIDC options on the Wave server would provide this benefit to Wave apps, which is generally expected by web app users.
Describe the solution you'd like
Wave should provide a mechanism for deploying the server with multiple OIDC configurations.
Because there are so many optional command line arguments needed, it might make sense to provide these in a configuration file rather than at the command line. In a config file, each OIDC configuration could be grouped and named. Then the app developer could inspect the available OIDC configurations, and offer some or all of those options to the user for authentication.
The wave server might need some way of knowing which service to connect to for authentication, so perhaps then name of the OIDC configuration could be passed in the HTTP header or URL query?
Ideally the OIDC service selected by the user gets stored at the User level, rather than at the App or Deployment (waved) level.
Describe alternatives you've considered
The alternatives currently available seem to be:

Require all users to obtain an account with the single OIDC service selected by the Wave app developer. This limits the freedom of the user to use an existing account.
Start a separate waved server instance for each OIDC option, then redirect user to that URL based on the OIDC option they select. This requires repetition of app services and the waved server, and logic complexity that extends outside the current app framework of Wave.
Deploy an OIDC proxy that handles the logic of offering OIDC options and maintaining the state of authentication, thus providing only a single OIDC interface to Wave. This requires each developer to independently write an OIDC server and the logic for proxying to the underlying services.

Because there are so many optional command line arguments needed

I guess our docs need a minor update for this section - all the above params are also available as env variables allowing for making your own config files - scripts.
Thanks for a great write-up @pshafer-als! cc @lo5


New Horizons - NASA Science

https://science.nasa.gov/mission/new-horizons

And your point is?
Maybe you should have used some issue template? Or properly followed #30839?


Plugin for Discourse backups to Nextcloud?

Hey @kajatiger & @jen-v! I just stumbled upon your post about the Discourse plugin for backup to Google Drive on the RailsGirls blog, pretty cool! :)
I read that you made it modular so possibly any service could be used as backup location. It would be awesome if we can connect it to Nextcloud, which is basically an open source alternative to Dropbox and Google apps. Technically it simply uses the WebDAV standard for files and basic auth (or tokens) for authentication, and supporting that standard would also make it work for lots of other platforms. (cc @MorrisJobke and @ChristophWurst if there’s more technical stuff because I mainly do design ;)
I’m not sure if you’re super busy with the program or we could meet and chat about it as I’m in Berlin too. For example at one of the weekly OpenTechSchool Frontend Co-learning meetups at co.up. There’s also @gsambrotta there who coded on both Discourse and Nextcloud before. :)

hi @jancborchardt ! nice to meet you, and very glad to receive this surprise message with a challenging task :) we would really like to look into it and be in contact with you guys. We'll write soon, once we talk properly about the scope of our tasks for the summer and how to integrate this in our plan. Cheers!

Great stuff! Since you are in Berlin, you are also very welcome at our Nextcloud conference end of August at the TU. :)

If we already start to build a discourse-sync-to-nextcloud plugin, would you be interested in us giving a little lightning talk at the conference?

Oh wow, that's so cool! Of course, please do give a lightning talk about it at the conference! :) Let me know if there's any issues during the registration/submission process.
You're also very welcome in our IRC channel #nextcloud-dev :)

(And even if it's not 100% done for the conf, a talk about your process is useful! And there will be lots of other contributors there too, including our RGSoC team @jonatoni and @xh3n1 who work on the Contacts app. :)

hi @jancborchardt :)
A little update about this subject:
we've talked about how the Nextcloud plugin will be built and are very excited about it, specially since we couldn't find any nextcloud gem (api wrapper) that we could use for it. This means, we must build it!
Our idea is to first build the gem and use it afterwards in our discourse-sync-to-nextcloud.

@jen-v oh nice, that’s thorough! Let me know how it goes :)


show utf charater in page

I need to display characters on the page(home.client.view.html) and other page
but instead displays a question mark character,
How can I solve this problem?

@webnovin I assume you need to show UTF-8 characters?
If so, it seems like the content type for the page is indeed set as UTF-8. Can you please confirm if that's not the case for you? (and also check whats the current content-type meta tag is set on your HTML page?

Is this still an issue or can this be closed?

quite old and no update so let's close for now.


Not able to deploy

Hi all,
I am facing a problem deploying coolify on ec2.

help would be appreciated :)

@andrasbacsai can you please check this? I have tried with 3 different VMs, all running Ubuntu 20.03 LTS, in azure, aws, and my home (pi4)

Is it for everyone or just me?

Probably everyone. 😢

:(
when will things get fixed? I was excited to try coolify

Fixed in #51! You can give it a try now!

I'm closing this after we talked on Telegram. I will test t2.micro if it's capable of using it for Coolify.


ts_config extends from external package

I'm trying to extend a tsconfig from an external dependency like this:
ts_config(
    name = "tsconfig",
    src = "tsconfig.json",
    deps = ["//:node_modules/@tsconfig/node16-strictest-esm"],
)

{
  "extends"<EMAIL_ADDRESS>}

I have also tried adding /dir to the package, and still not working.
ERROR: /home/juan/Projects/hibot/rocka/proto-generator/BUILD:10:11: Compiling TypeScript project //proto-generator:ts [tsc -p proto-generator/tsconfig.json] failed: (Exit 1): tsc_worker.sh failed: error executing command bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm_typescript/tsc_worker.sh @bazel-out/k8-fastbuild/bin/proto-generator/src/index.js-0.params
Compilation failed:
 TypeError: Cannot use 'in' operator to search for 'tsconfig.json' in undefined
    at getNode (/home/juan/.cache/bazel/_bazel_juan/110af2bd36a97b83ddd5caaaec0d3270/execroot/rocka/bazel-out/k8-opt-exec-2B5CBBC6/bin/external/npm_typescript/tsc_worker.sh.runfiles/npm_typescript/ts_project_worker.js:57:24)

This indeed looks like a bug in the worker.  I'll take over.

@jbedard it works disabling the worker

PP: still relevant. Needed for 1.0 milestone.


REQUEST FEATURES: SPECIFIC-TOPICS DOWNLOADER

Thank you for you amazing work! I would love to request for a feature to download for a specific set of keywords on LibGen!

This wouldn't be super hard to implement:

Select the right md5 hashes from the metadata db based on keyword/topic
Lookup which chunks those hashes are in
Download only those chunks, and only the files you want

I don't have time to work on this, but welcome PRs if anyone is interested.


Building on M1 Mac leads to Incorrect Architecture Linking

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.2
Firebase SDK version: 7.3.0
Installation method: CocoaPods
Firebase Component: RemoteConfig, Analytics

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
On an M1 Mac (Apple Silicon), running my project for the iOS Simulator results in the following:
ld: in /Users/kevinchau/Documents/dev/radioapp-ios/Pods/FirebaseAnalytics/Frameworks/FIRAnalyticsConnector.framework/FIRAnalyticsConnector(FIRAnalyticsConnector_a8eeba373b74508311b8b22b8d3202a6.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/kevinchau/Documents/dev/radioapp-ios/Pods/FirebaseAnalytics/Frameworks/FIRAnalyticsConnector.framework/FIRAnalyticsConnector' for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

If I add arm64 into Excluded Architectures for the target, then I will get No Such Module: FirebaseRemoteConfig

Seems related to building for the simulator. Running on a debug device via USB works fine.

Hi @kevinchau, sorry for the trouble. I believe this is a CocoaPods 1.9 issue and it was resolved in 1.10. Can you check which version of CocoaPods you have installed?

Also make sure you're following the CocoaPods instructions for using an M1 Mac. See https://github.com/firebase/firebase-ios-sdk/blob/master/AppleSilicon.md

@ryanwilson I'm running 1.10.0
@paulb777 When I run pod install after adding the -M1 version tag, I'm getting this issue.
[!] CocoaPods could not find compatible versions for pod "GoogleAppMeasurement":
  In snapshot (Podfile.lock):
    GoogleAppMeasurement (= 7.3.0, ~> 7.0)

  In Podfile:
    Firebase/Analytics (= 7.3.0-M1) was resolved to 7.3.0-M1, which depends on
      Firebase/Core (= 7.3.0-M1) was resolved to 7.3.0-M1, which depends on
        FirebaseAnalytics (= 7.3.0-M1) was resolved to 7.3.0-M1, which depends on
          GoogleAppMeasurement (= 7.3.0-M1)

Specs satisfying the `GoogleAppMeasurement (= 7.3.0, ~> 7.0), GoogleAppMeasurement (= 7.3.0-M1)` dependency were found, but they required a higher minimum deployment target.

I have my podfile with this as the first line:
platform :ios, '10.0'
I've tried everything all the way up to 13.0 - I'm getting the same error message calling for a higher minimum deployment target.

@kevinchau  I'll reach out to the Ads team and find out what I can.

FYI: The excluded architecture approach doesn't seem to work in some cases. It's telling me that the simulator needs an ARM64 binary.

FYI: The excluded architecture approach doesn't seem to work in some cases. It's telling me that the simulator needs an ARM64 binary.

I'm going to close since the OP's question was resolved.
Please open another Issue if you have additional questions on any of the tangential topics in this issue thread.

I'm going to close since the OP's question was resolved.
Please open another Issue if you have additional questions on any of the tangential topics in this issue thread.


create leader171.txt

@prokhorind First stage of verification passed, official domain for Києво-Печерський ліцей №171 “Лідер” is leader171.kyiv.ua as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@prokhorind Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


inconsistent charges between parents and children

charge should be a functional inheritable property (see https://github.com/oborel/obo-relations/pull/723), but this is in conflict
charges-inconsistencies.tsv.txt
Example
cyanidin 3-O-(6-O-acetyl-beta-D-glucoside)
(https://www.ebi.ac.uk/ols4/ontologies/chebi/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_131449)
charge +1
subclass
acetate ester
https://www.ebi.ac.uk/ols4/ontologies/chebi/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_47622?lang=en
charge 0

Here is how to regenerate using semsql:
create view charge as select * from statements where predicate='obo:chebi/charge';
create view inconsistent_charge as select c1.subject, c2.subject from charge as c1, rdfs_subclass_of_statement as s, charge as c2 where c1.subject=s.subject and c2.subject=s.object and c1.value != c2.value;

Consider
putreanine(1+) (CHEBI:180912) is a carboxylic acid anion (CHEBI:29067)
That a cation(1+) is an anion(1−) seems to be absurd, right? But  carboxylic acid anion is defined as R-COO−, where R could bear any charge, including positive. The "net charge" of a carboxylic acid anion does make as much sense as its average mass, that is, none.
In case of entities such as monoatomic boron (CHEBI:33610), diatomic oxygen (CHEBI:33263), triatomic sulfur (CHEBI:33413) the average mass does make sense but the net charge doesn't.
IMHO the easiest fix to this problem would be simply to eliminate the "net charge" from the entities that do not have an INChI in them.

I think alot of these charge inconsistencies are related to structures containing R-groups. This can be dealt with by having a comment in the charge section saying that the Net Charge excl. R groups. We are currently doing this for the Average Mass and Monoisotopic Mass:

Some of these charge inconsistencies are related to structures containing R-groups. This can be dealt with by having a comment in the charge section saying the Net Charge excl. R groups.

Comments are not computable. Consider using a different property so tools can ignore this without string hacking.

Hi @cmungall
A quick solution would be to completely remove the charge field from all the parent classes that contain structures with R-groups. Will this be acceptable to you?


test: work around

Description

Type of change

[ ] New feature (non-breaking change which adds functionality)
[ ] Refactor ( rewrite or restructure code)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas

Data Results

none

Additional Info

none

closing the pull since target is reached in this https://github.com/rayanfer32/nexus-market-cap/pull/35 PR


How do i even open the program (not the jar file)

The run.bat doesn't work, idk how to run just a file (run, no extension), and i have no idea how to use the mvnw, do i need to install maven or something? Also, i don't want to use the jar, because i'm trying to add a sort i'm making, and i can't just import it because, it wants a java file, not a js file and idk how to code a sort in a java source file... Also, i'm planning to fork this repo, and i don't think i can compile a jar file from my fork, so could somebody help

Usually you just double-click or run in terminal, but I'm guessing you haven't installed the prerequisites. Regardless, a help question is not an issue with this repository; please join the Discord server (linked in the README) for help.

i cant log into my discord acc for some reason

did ./mvnw clean verify, it said compilation failure. Realizeed im running on a JRE.

Doing it again, switched to jdk-22 instead of jre-1.8. Suddenly after generating javadoc, got blasted with like 1000 warnings and stuff in like, 0.3 seconds. BUILD SUCCESS

Just did ./run. seems nothing is happening
nothing happened but its not prompting me to type something yet

IT RUN LETS FRIGGIN' GO