Add support for virtualized Nvidia GPUs

Description
Newer versions of Nvidia GPUs cannot be virtualized through OpenNebula.
Progress Status

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

PRs to merge in master:

code
docs


doc: reference: include two levels of titles in the toc

The Zephyr API grouping can be a bit difficult to maneuver. Ease this up a bit by expanding the table of contents to contain two levels of titles.
Signed-off-by: Henrik Brix Andersen<EMAIL_ADDRESS>

lgtm, but this just exposes the issue with the content we have under reference :(


Add css selectors from senego and seneweb

We use selectors to extract metadata from website
Below the needed metadata

title
url
pubdate
author

#3 Done!


Sw/add tailwind

Adds Tailwind. This is a preview of what this looks like.

Closed. Did not make progress on this.


[KYUUBI #1886] Add GetSchemas for trino engine

Why are the changes needed?

Add GetSchemas for trino engine
How was this patch tested?

[X] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #1902 (f35a92f) into master (68b9245) will increase coverage by 0.04%.
The diff coverage is 86.36%.

@@             Coverage Diff              @@
##             master    #1902      +/-   ##
============================================
+ Coverage     59.75%   59.80%   +0.04%
- Complexity      321      326       +5
============================================
  Files           291      292       +1
  Lines         14232    14255      +23
  Branches       1804     1810       +6
============================================
+ Hits           8505     8525      +20
- Misses         5001     5003       +2
- Partials        726      727       +1

Impacted Files
Coverage Δ

...che/kyuubi/engine/trino/operation/GetSchemas.scala
85.00% <85.00%> (ø)

...engine/trino/operation/TrinoOperationManager.scala
61.53% <100.00%> (+11.53%)
:arrow_up:

...rc/main/scala/org/apache/spark/ui/EnginePage.scala
78.97% <0.00%> (-0.48%)
:arrow_down:

...ache/kyuubi/operation/KyuubiOperationManager.scala
95.00% <0.00%> (+2.50%)
:arrow_up:

Continue to review full report at Codecov.

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

thanks, merged to master


feat: Module certification issues 2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: anjalimukundan:x: jbigeljbigel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 1.4.0-dev.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MINOR: Don't register signal handlers if running on Windows

The following happens on Windows for HUP:
[2017-10-11 21:45:11,642] FATAL  (kafka.Kafka$)
java.lang.IllegalArgumentException: Unknown signal: HUP
at sun.misc.Signal.(Unknown Source)
at kafka.Kafka$.registerHandler$1(Kafka.scala:67)
at kafka.Kafka$.registerLoggingSignalHandler(Kafka.scala:73)
at kafka.Kafka$.main(Kafka.scala:82)
at kafka.Kafka.main(Kafka.scala)
I thought it was safer not to register them at all since the additional
logging is a nice to have and we haven't tested it on Windows.
Also changed map to be concurrent and removed stray
printStackTrace in test.

Merging to trunk and 1.0.


default workflow and workdir

Coverage remained the same at 87.059% when pulling 50d7e7f98cd456355a33d34cb15ad0af4080c981 on defaults into 5289a3e36cf98b01125b5edf5472ee18f4c66dd9 on master.


Sentry v2 not working with php 7.3.x Call to undefined function Sentry\str_starts_with()

It's been months since I have this error and I thought that was fixed after so many versions released... I was in v1.7 before...and I have updated to v2.3.1 and now it's not working again. The problem is that you are using PHP functions from PHP v8 even though it says that v2 is working with PHP 7.2 and above.
Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?
PHP
Steps to Reproduce
Use PHP v7.3.x with sentry Laravel v2.3.1
Add in composer.json
"replace": {
  "symfony/polyfill-php74": "*",
  "symfony/polyfill-php80": "*"
}

Try to send an exception
Expected Result
Send exception normally to Sentry
Actual Result
Exception 5xx and this on logs
2021/03/23 19:10:14 [error] 2081#2081: *92239498 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function Sentry\str_starts_with() in /vendor/sentry/sentry/src/FrameBuilder.php:101
Stack trace:
#0  /vendor/sentry/sentry/src/FrameBuilder.php(67): Sentry\FrameBuilder->stripPrefixFromFilePath('...')
#1 /vendor/sentry/sentry/src/StacktraceBuilder.php(66): Sentry\FrameBuilder->buildFromBacktraceFrame('...', 101, Array)
#2 /vendor/sentry/sentry/src/StacktraceBuilder.php(46): Sentry\StacktraceBuilder->buildFromBacktrace(Array, '..., 101)
#3/vendor/sentry/sentry/src/Client.php(304): Sentry\StacktraceBuilder->buildFromException(Object(Symfony\Component\Debug\Exception\FatalThrowableError))
#4 /vendor/sentry/sentry/src/Client.php(218): Sentry\Client->addThrowableToEvent(Object(Sentry\Event), Object(Symfony\Component\Debug\Exception\FatalThrowableError))
#5 /...PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function Sentry\str_starts_with() in /vendor/sentry/sentry/src/FrameBuilder.php:101
Stack trace:
#0 /vendor/sentry/sentry/src/FrameBuilder.php(67): Sentry\FrameBuilder->stripPrefixFromFilePath('...')
#1 /vendor/sentry/sentry/src/StacktraceBuilder.php(73): Sentry\FrameBuilder->buildFromBacktraceFrame('...', 101, Array)
#2 /vendor/sentry/sentry/src/StacktraceBuilder.php(46): Sentry\StacktraceBuilder->buildFromBacktrace(Array, '...', 101)
#3 /vendor/sentry/sentry/src/Client.php(304): Sentry\StacktraceBuilder->buildFromException(Object(Symfony\Component\Debug\Exception\FatalErrorException))

You are replacing symfony/polyfill-php80 which blocks it from installing.
str_starts_with was introduced in PHP 8.0, so that is why that polyfill is there.
So this is a "bug" by your own making :)
Keep the PHP 8 polyfill and everything works as expected!

I am closing this issue because of inactivity, if there is still an issue please re-open / open a new issue so we can investigate 👍

Wow, that's great. Thank you very much~


can't parse empty select

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

select;
Parsing this SQL using JSqlParser with this statements
org.junit.ComparisonFailure: Expected query to parse but it failed to parse (error: Encountered unexpected token:<EOF> at line 1, column 6.

Expected behavior
query to parse
System

postgres
15
4.1

Select will need a body at least. EBNF is:
Select   ::= SelectBody

I am not going to change that.


Migrate to Terraform 0.12

Description
This PR is based and supersedes https://github.com/kinvolk/lokomotive-kubernetes/pull/45. It migrates the different providers and updates the documentation accordingly.
I would need some help here to test the providers I already tested and also to test the ones I wasn't able to test yet.
The commits are organized as follows:

preparatory commits, includes also fixes for some already existing problems, like https://github.com/kinvolk/lokomotive-kubernetes/pull/116.
run terraform 0.12upgrade, just run it without fixing anything.
fixes the problems introduced by the above.
update documentation / examples / ci.
use some features of Terraform 0.12, like array notation and  specific data types.

Status

Aws,  Azure, Google Cloud and Packet providers have been migrated and tested.
Baremetal and kvm-libvirt have been migrated but not tested yet.
DigitalOcean hasn't been migrated.

TODO

[ ] Update bootkube module source once https://github.com/kinvolk/terraform-render-bootkube/pull/33 is merged.
[ ] Update CI.

tested on kvm-libvirt, works fine

@rata I have saved a backup branch with more granular commits, I clean those up and pushed here. I hope this new version is easier to review.

@rata I think having a working tree on each commit and having small commits could be complicated. For instance, after running terraform 0.12upgrade it is needed to fix some issues by hand, if I do that in a single commit then it'll be not possible to understand what was changed by the tool and what was fixed manually.
I like the idea of having a working tree on all commits, but I'm don't know if it's worth to do so.

I think the overall diff looks good to me. Added some small comments. Thanks for tackling such a big PR! :)
One thing I'm confused is that it seems you created other PRs for fixes included here. The idea is to merge those and then adapt this?

Yes, while working on this I found some problems in Azure, since those are not related to this PR I opened a separated PR for that https://github.com/kinvolk/lokomotive-kubernetes/pull/116. That's now merged and I'll rebase it to include those changes.

On a side note, I still think we can improve the way commits are split, to be easy to review while still having a working tree in all commits (for easy bisect, etc.), but that seems out of scope for this PR and we don't have any rules on this yet.

The problem is that in order to do that I'll have to squash the commits where terraform 0.12upgrade and the fixes for that are done, if that's not a problem I can do that.
I think the following layout could work:

preparatory commits: update provider versions, rename count to worker_count
one commit per provider: run terraform 0.12upgrade, fixes problems, point bootkube to right place, update doc syntax
use array notation
use correct datatypes

Thoughts @rata, @invidian , @johananl ?

I think the overall diff looks good to me. Added some small comments. Thanks for tackling such a big PR! :)
One thing I'm confused is that it seems you created other PRs for fixes included here. The idea is to merge those and then adapt this?

Yes, while working on this I found some problems in Azure, since those are not related to this PR I opened a separated PR for that #116. That's now merged and I'll rebase it to include those changes.

Cool! :)

On a side note, I still think we can improve the way commits are split, to be easy to review while still having a working tree in all commits (for easy bisect, etc.), but that seems out of scope for this PR and we don't have any rules on this yet.

The problem is that in order to do that I'll have to squash the commits where terraform 0.12upgrade and the fixes for that are done, if that's not a problem I can do that.
I think the following layout could work:

preparatory commits: update provider versions, rename count to worker_count
one commit per provider: run terraform 0.12upgrade, fixes problems, point bootkube to right place, update doc syntax
use array notation
use correct datatypes

Thoughts @rata, @invidian , @johananl ?

That sound good to me, if it doesn't take too much time for you. It is, in a way, what I was trying to say here (haven't realized about the "after" changes, haven't review those probably at that time): https://github.com/kinvolk/lokomotive-kubernetes/pull/119#pullrequestreview-336819228. Sorry I wasn't clear there :-/
But I'll let others decide on this :)

preparatory commits: update provider versions, rename count to worker_count

It can be separated PR to minimize the impact of this PR (it's already large).

one commit per provider: run terraform 0.12upgrade, fixes problems, point bootkube to right place, update doc syntax

IMO all providers at a time is fine. If we decide to commit per provider, we should be consistent around that with further changes. Given that it's unlikely that this commits will be reverted, I think it should be fine to have one commit for all providers.

Rebased on latest master and pushed a commit, which changes CI to use Terraform 0.12.

Had to cherry-pick some commits from #112 to resolve version skew between kube-apiserver and kubelets.

I cherry-picked one more commit from https://github.com/kinvolk/lokomotive-kubernetes/pull/112 since it seems to be related to the bootkube failure. I adapted it to apply to baremetal as well.

Let's merge #112 first, what do you think?

Yes, so that we can drop the commits here again instead of trying to keep them in sync.

Given that it took us so much time to get there, I'll merge it now.


Allow get the number of result by action

This patch allow get the buld response status by action. Same result as len(r.Updated()), etc. but more performance (mostly in big bulk request)

What's wrong with len(Indexed()) etc.?

As for performance: Can you provide a benchmark?

i havent benchmark :( but just looked into the source: ByAction build a new items array.
if the bulk has >100k items, thats not only lots of cpu (unused memory copy) usage, but also high memory usage ~12Mb (pure sizeof(BulkResponseItem) == 128) too.


add SillyTavern

https://github.com/Cohee1207/SillyTavern
it's tavern ai, but with modifications that include use of for example different models etc. It's far more advanced in my eyes

Resolved by c1ebeea7a08570ea1899d51991ec607e2fb1dfab


initial PR for the framework reusing Vanilla Spark's unit tests

(borrowing from Gluten)
Closes #10745
This PR adds a framework to enabling Vanilla Spark UTs by:

Some utility Traits, most importantly RapidsTestsTrait and RapidsSQLTestsTrait for rapids test suite to extend, these traits: injects rapids backboned spark session to the base class, as well as allow testcase level exclusion/inclusion.
A centralized control center called RapidsTestSettings, which decides what suites/testcases are included/excluded.
A first batch of 8 suites are enabled, listed at https://github.com/NVIDIA/spark-rapids/pull/10743/files#diff-4be8dbebdd70379fcc56bae360c6997a9a2b6e66ce48b229c7ff289ae02a5222R41

Most of codes are copied from Apache Gluten, which also follows Apache license.
To respect their work I kept their origin Apache License header in the source code file.
Currently we only focus on spark 3.3.0.
Check out more details at our internal design doc.

build

build

build

build

build

build

build

build

build

build

build


Error message does not indicate which file is concerned

$ docker-app render wordpress/wordpress.dockerapp -f wordpress/with-secrets.yml
Error: yaml: line 14: did not find expected key

The name of the key could be nice too.
Version
$ docker-app version
Version:      0.1.0-52-gb207ad0
Git commit:   b207ad0
OS/Arch:      linux/amd64
Experimental: off
Renderers:

I believe this has been fixed. Running from ./examples:
$ docker-app render wordpress/wordpress.dockerapp -f wordpress/with-secrets.yml
Error: open wordpress/with-secrets.yml: no such file or directory


Focused specs

Is it possible to run one spec only? I had a look at the docs but didn't find any info about it. jasmine has a concept of focused specs fit, mocha provides an only method. I like tap much and such feature would make my work easier in some cases.
I can have a look at it and create a PR if it's in scope of the project.

You can run one file at a time pretty easily. Perhaps it's better to break your script out into separate files rather than trying to run something in the middle of a file.

Yeah, we've talked in the past about ways to do this, but it sort of runs counter to the design principles of node-tap.
Tap runs the test functions immediately, so that there's as close as possible correlation between the test file and the TAP output.  So that a file like this:
var t = require('tap')
console.log('one')
t.test('two', function (t) {
  console.log('two')
  t.pass('this is fine')
  t.end()
})
console.log('three')
console.log('four', function (t) {
  console.log('four')
  t.pass('also fine')
  t.end()
})

produces the following intelligible output:
one
TAP version 13
# Subtest: two
two
    ok 1 - this is fine
    1..1
ok 1 - two # time=9.269ms

three
four function (t) {
  console.log('four')
  t.pass('also fine')
  t.end()
}
1..1

That only works if tests are run before any subsequent tests are even encountered.  If there was a .only() method on the second test, then it wouldn't know until it had already run the first test, and the only way to do that is to make all the t.test() calls async, which means that console.logs came out of order.  They may come out of order anyway, of course, if a deferral of t.end() pushes them into a queue, but at least in the sync test case, it just runs top to bottom, and that helps debugging in a surprising number of cases.
(Hijacking console.log and pushing it into the same queue is a bad idea that I've tried.  It very much does not make things less confusing.)
It would be possible to say, from the top level, "only run tests matching some pattern", but then that's a bit hard to do in a way that's sensitive to child tests.
t.test('one', function (t) {
  t.test('two', function (t) {
    t.pass('this is fine')
    t.end()
  })
  t.end()
})

So, if I run tap test.js --only-run-tests-matching=/two/ then how does it know that a child test named "two" is coming when it encounters the parent test?  If I do --match=/one$/ then should it run the two child test?  (And if it doesn't, then the parent test is invalid!)  What if you do tap.plan(4) at the top, should we ignore the plan, or produce invalid TAP, or ignore the --match arg?  It's more complicated than it looks!
The state of the art currently is to use multiple test files.  It's a good idea anyway.  Each one gets a standalone process context, it's very clean and predictable.  You can do node test/foo.js to run the test file directly, or tap test/foo.js to get all the fancy output prettiness.
I do occasionally, in debugging, comment out huge chunks of a file or put a return halfway down, but that's more the exception than the rule, and I usually take that debugging action as a smell indicating that I should probably split the tests up into separate files.

Thanks for the explanation, that definitely makes sense. I believe that splitting the files is not always a solution though, e.g. you might have very few specs which take a very long time to run.
I know the issue is closed, but I though of other way to do it and maybe the solution below would make you interested. Basically only would be treated as syntax sugar for skipping all other tests.
The idea is quite simple:

add a first pass test to see if any of the specs has .only( (simple regexp would probably be enough)
if it doesn't continue as usual
if it has then preprocess the test files with some simple static code analysis, e.g.

input
var t = require('tap')
console.log('one')
t.test('two', function (t) {
  console.log('two')
  t.pass('this is fine')
  t.end()
})
console.log('three')
t.test.only('four', function (t) {
  console.log('four')
  t.pass('also fine')
  t.end()
})

output
var t = require('tap')
console.log('one')
t.test('two', { skip: true }, function (t) {
  console.log('two')
  t.pass('this is fine')
  t.end()
})
console.log('three')
t.test('four', function (t) {
  console.log('four')
  t.pass('also fine')
  t.end()
})

Would this make any sense?

@emilos You can definitely write such a thing without making any changes to node-tap.  You don't need my permission, but you have my blessing :)
I'd recommend not using a regexp.  Consider this program:
var o = 'only'
t.test[o]('only run this', fn)

Haha, thanks. I'd probably ignore cases like that. The first pass test would simply check if it makes any sense to make the static code analysis that would check if properly :) - it would be expensive to do it for every test file. It was worth asking anyway, thanks for your time!

With TAP, the general way to run a specific test, is to split that test out into a different test script.


windicss does not apply all styles when after build

Describe the bug
Sometimes windicss does not apply all styles when you first dev server run. In such cases, it is enough to reload the page and then all styles are applied as expected.
Minimal Reproductions

Clone repo: https://github.com/cawa-93/windicss-issue
Run npm run dev
After server start await a few seconds.
Open dev server url http://localhost:3000/
You can see that the styles were not applied. Unfortunately, in the demonstration repo, this problem is not reproduced every time and I do not understand why, in a larger project it happens every time. You may have to try several times before the problem recurs. . If reload page then styles will be loaded

Another Minimal Reproductions

Clone repo
Run npm run dev
Open dev server url http://localhost:3000/
Reload the browser page to ensure that the styles are applied.
Restart the dev server without closing the page in the browser. You can see that the opened page has been updated and the styles are missing.

Versions

vite-plugin-windicss: 1.4.5
vite: 2.5.4
framework(vue/react/svelte/etc): none

Additonal Context
OS: Windows 10
Browser: Firefox 93.0b9

Same as https://github.com/windicss/vite-plugin-windicss/issues/243


[Request] Add flameshot

Powerful yet simple to use screenshot software.
https://github.com/flameshot-org/flameshot
https://flameshot.org

Great if added.


Parse data from NY's historical PDFs

Responding to the call-out here: https://github.com/biglocalnews/warn-scraper/issues/476
This being my first commit to the project, and not knowing how the maintainers would like to handle the overlap between the data sources, I tried to take the least destructive approach.
And I think I obeyed the Contribution guidelines, but don't hesitate to holler if I haven't.
Also, in order to get the pre-commit hook to pass, I had to upgrade two dependencies in .pre-commit-config.yaml, due to changes in psf/black. (Cf.: https://github.com/psf/black/pull/2966 and https://github.com/asottile/blacken-docs/issues/141.) Let me know if there's another way you'd like that handled.

Added a commit addressing you (very reasonable) requests 👍

Looks like there's quite a bit of overlap, both in actual data and timeframes. I don't know enough, however, about the history/provenance of the non-PDF data files to suggest which source(s) should take precedence.


MVC - initFormAdvancedUI: universal stripes adjustment

Hi!
probably close https://github.com/opnsense/core/issues/5407
uses MutationObserver API to monitor style changes within striped tables. when row visibility changes, the parity of visible rows is adjusted for correct stripes display.
although it may seem horrible from a performance standpoint (observe for any "style" attribute changes in all .table-striped tables on the page for the sake of row parity control), no performance impact was noticed.
Thanks!

@kulikov-a looks good from my end, thanks!

@AdSchellevis  Thanks!!)


ModuleNotFoundError: No module named 'cityflow'

Hello,
I built cityflow from the source code.
The last process I did was 'pip install CityFlow'. (I did not get any errors)
While trying to implement some test, I got this error msg: ModuleNotFoundError: No module named 'cityflow'.

hello, have you got the solution to this problem?
I'have got the same issue.

Try run pip install . in CityFlow root directory


Sensitivity

I used SnowGlobe in a project and the project owner wanted the snow to appear more easily.
As you haven't provided direct access I added it.

Nice work, thanks !
Apologies for late merge.
Thanks again !


Update python env when updating poetry

Description

It seems that when running poetry lock in the latest poetry update from GH actions we are not using the latest python available
This add the instructions like in https://github.com/swappiehq/hemuli#someone-updated-python-and-now-my-environment-is-broken
Checklist

[ ] After merging this I have tested this by manually triggering the action in one of the internal projects

I don't this needed. I will link you the results of last run where we used this and it seems to be working fine 👍

Yeah I just checked the last run and everything seems ok


Please release new version with Babel 6

I notice that you have ember-cli-babel listed as version 6.x in master but not in the latest release.  Could you please release a version with babel 6?
Thanks!

@danwenzel ok :)

Thanks for the quick response!

Just finished


Update the discoveredclusters api

Update the DiscoveredCluster interface to match the new api spec
See user story https://github.com/open-cluster-management/backlog/issues/10770

/lgtm

/unhold

/lgtm

/approved

/lgtm


Issue with swiper.slideto() function

I am trying to use swiper.slideTo() function as a way to display a certain slide when a certain hyperlink within a div is clicked on but the swiper.slideTo() function stops working when I display two different sliders in the same HTML file.

@hassannadeem97 Could you provide the test code with bugs?

@ygj6 Nevermind, I was not implementing it properly.

so,I think issue can be closed?

yes


Fix: Spelling mistake

https://github.com/yelouafi/redux-saga-beginner-tutorial/blob/master/package.json#L7

@yelouafi I was wondering why a simple spelling mistake pull request is taking more than 7 days to merge.

sorry for the delay. And thanks


[BUG, MiniPay] Need to remove container from bottom navigation bar

Private Zenhub Image

fixed here: https://github.com/GoodDollar/GoodProtocolUI/commit/9dc1a6e105c4e7a5d41ab3e1c2a2c2e912073bc1


Message in stderr is breaking django-mjml

The fix to issue #1342 released in version 4.2.1 is breaking django-mjml template engine.
If using mjml v3 the message MJML v3 syntax detected, migrating to MJML v4 syntax. Use mjml -m to get the migrated MJML. is shown in stderr now, making django-mjml fail to render the template because it considers that any output in stderr an error running the command.
With mjml v4.2.0 it works just fine.

Well as the migration won't be available forever in the mjml client I think
it should still throw in the stderr ?
On Mon, Nov 26, 2018 at 10:46 PM Cristian Rosa<EMAIL_ADDRESS>wrote:

The fix to issue #1342 https://github.com/mjmlio/mjml/issues/1342
released in version 4.2.1 is breaking django-mjml template engine.
If using mjml v3 the message MJML v3 syntax detected, migrating to MJML
v4 syntax. Use mjml -m to get the migrated MJML. is shown in stderr now,
making django-mjml fail to render the template because it considers that
any output in stderr an error running the command.
With mjml v4.2.0 it works just fine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/1439, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAizzWO4wmlSzHK7LEAiomJyHhZYoDp7ks5uzGE3gaJpZM4Yz46T
.

--
Cordialement,
Maxime BRAZEILLES

I agree, I will fix it by migrating the templates to v4. I just wanted to point it out that depending on what do you consider the API of mjml, 4.2.1 was a minor relase that changed the API (moving stuff from stdout to stderr). Anyways, I will create an issue in django-mjml as well.
Thanks!

Well as we can't do really something about this, i'm closing the ticket.

Hello, we are going to reopen this issue and fix the behaviour by sending MJML validation errors to stdout instead. stderr should be used only for an actual failure in the MJML compilation, not syntax warnings.

What about stderr for strict & stdout for other level ?

Hi @ngarnier, I disagree with this - stdout should only be used for the actual output (so that you can redirect it to a file, and be sure you aren't sending your users an email with validation messages).
All diagnostic output should go to stderr, and I propose to add setting to select verbosity (warnings and errors, or errors only).

I think stdout must give us the result; any errors, warnings, etc. must be given us from stderr and verbosity option must filter the messages. It is simple and clearly.
I can't understand why changing standards everyday is normal practice in js-world.

Ok, I thought it was a problem for you to have the errors in stderr but as you're unhappy with both my proposal and @iRyusa, I guess I misunderstood. We're going to leave it as is.

I had this problem recently, the solution was to remove mj-container as mentioned here #1342 by @iRyusa

I having an issue after upgrading MJML from 3.3.3 to 4.14.0, I also cleaned the mj-container tags, here is the remaining issue:
    raise RuntimeError(f'MJML stderr is not empty: {force_str(stderr)}.')
RuntimeError: MJML stderr is not empty: mjml-migrate is deprecated and will be removed in mjml 5


Support for /Lang would be appreciated as that would make it possible to generate Accessible PDF's

All other properties can be set as far as I can tell, expect /Lang.
Example 3
http://www.w3.org/TR/WCAG20-TECHS/PDF16.html

Implemented in PR #1456

Appreciate it. Thanks!

Solved by PR #1397
Merged on 11 January 2018
Will be part of next version.


Open source CLI code

Is the source code of the CLI open source somewhere?
If not, are there plans to do so?
If not, I hereby cast my vote :ballot_box:

We are yet to open source the CLI's code, but we plan to eventually have it open source, once we are confident it is ready to be open to the public.
Thanks for casting your vote. It is good to hear that users of the CLI are also interested in it being open source.


prometheus-mongodb-exporter: 0.43.0 -> 0.43.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/percona/mongodb_exporter/releases.
meta.description for prometheus-mongodb-exporter is: Prometheus exporter for MongoDB including sharding, replication and storage engines
meta.homepage for prometheus-mongodb-exporter is: https://github.com/percona/mongodb_exporter
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.43.1 with grep in /nix/store/qmnfzwjl0w4iazarakdykyxy506q89hx-mongodb_exporter-0.43.1
found 0.43.1 in filename of file in /nix/store/qmnfzwjl0w4iazarakdykyxy506q89hx-mongodb_exporter-0.43.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

prometheus-mongodb-exporter

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/qmnfzwjl0w4iazarakdykyxy506q89hx-mongodb_exporter-0.43.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A prometheus-mongodb-exporter https://github.com/r-ryantm/nixpkgs/archive/a9db27f07c8e6c2222009aacbe047a18dc5d4b09.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a9db27f07c8e6c2222009aacbe047a18dc5d4b09#prometheus-mongodb-exporter

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qmnfzwjl0w4iazarakdykyxy506q89hx-mongodb_exporter-0.43.1
ls -la /nix/store/qmnfzwjl0w4iazarakdykyxy506q89hx-mongodb_exporter-0.43.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

prometheus-mongodb-exporter

Maintainer pings
cc @undefined-moe for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 367861

aarch64-darwin

:white_check_mark: 1 package built:

prometheus-mongodb-exporter


Deploy pages using artifact IDs

Closes: https://github.com/github/actions-results-team/issues/1988
Currently deployments are made using and artifact_url. This is done so that internally we call APIs while a run is still in-progress which is a big limitation with the current v1-v3 artifact actions. With the upcoming v4 artifact actions as soon as an artifact is uploaded then it is immediately available from the Artifacts API. The public API will allow us to work with artifact IDs which are much cleaner then working with a artifact_url.
As part of the changes I did the following

Add a new getArtifactMetadata method that fetches artifacts for a workflow run given a run ID and name
Remove all the old code that dealt with fetching the current artifact_url
Remove 3 packages that are no longer needed
Update all the existing tests
Add some new tests specific for artifacts

See this example run: https://github.com/bbq-beets/testing-artifacts-v4/actions/runs/6697548931/job/18197689133

It fails as expected because the code downstream in the API is not ready to handle an artifact_id. This is being worked on now in a subsequent PR internally.

End to End deployment with artifacts V4 now works! We can merge this in 😃


Feature/139456257/effective ui

What does this PR do?

Designs a landing page

Description of Task to be completed?

Build upon existing index.html file
Create new css file
Add links to head.jade

How should this be manually tested?
By running npm start
Any background context you want to provide?
N/A
What are the relevant pivotal tracker stories?
#139456257 Users should see a landing page with effective ui/ux
Screenshots (if appropriate)
N/A
Questions:
N/A

Coverage remained the same at 100.0% when pulling dee92c6656e39c4c32d0fb473772d230216f9a72 on feature/139456257/effective-ui into b6c3883d4ed5ad07c400b40074ff96da2f91bf7f on develop.


Add the Precision, Recall and F1 Score metrics in callbacks.py

Summary
Add precision, recall and f1 score metrics for binary classification.
Related Issues
This issue
PR Overview
Added precision, recall and f1 score metrics for binary classification in callbacks.py.

[n] This PR requires new unit tests [y/n] (make sure tests are included)
[y] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[y] This PR is backwards compatible [y/n]
[n] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

Thanks for the PR. When fixing a bug or adding a new functionality, tests helps us maintain your work and make sure it doesn't break in the future. Could you add tests please? Thanks!

A lot of issues with this PR. Please do not open a PR that is not in a good state.
If you need help please go to Slack/StackOverflow/Gitter/Google groups.
Metrics such as Recall or Precision must use the StatefulMetric pattern.
I know that @CharlesAuthier is working on this feature as well using StatefulMetrics and should have a PR ready by the end of the week.

We will upgrade the API for handling stateful metrics soon, based on the new API in tf.keras: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/keras/metrics.py
The new API will include built-in support for precision and recall. ETA is probably around January.

(contributions on this feature are super welcome, but please make sure to prioritize porting the new API)

@CharlesAuthier could you modify your work to do something similar the the TF implementation?

Yep


make both api-full and report mode output the api.json file

Description
Hello! We would love to have the full api.json file available also for the report mode, and this PR enables it. In our use cases, we sometimes check the generated HTML reports, and also we have automation to analyze the api.json file generated by the api-full mode. It would be nice to have it available for report mode.
If you need to make it as a separate option to not to change the current behavior, please let me know.
Thanks!
Type of change
Please delete options that are not relevant, and add any that may be relevant.

[x] Minor changes

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Single Account, Single Service and Single Region
[x] Single Account, Single Service and Multiple Regions
[x] Single Account, Multiple Services and Single Region
[x] Single Account, Multiple Services and Multiple Regions
[x] CrossAccounts, Multiple Services and Multiple Regions

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have tested this change with all regions and services
[ ] Any dependent changes have been merged and published in downstream modules

Thx! Can you amend the code to remove the support of "--api-mode" entirely, and always generate 3 of the files?
1/ html
2/ api-full
3/ api-raw?

Thx! Can you amend the code to remove the support of "--api-mode" entirely, and always generate 3 of the files?
1/ html 2/ api-full 3/ api-raw?

Hi @kuettai , thanks for the feedback. That sounds good. Of course, I can work on it :)

@kuettai, I have removed the user option runmode and make HTML report, api-raw.json and api-full.json always available in each AWS account's folder. I test it with one of our AWS accounts and it works as expected. Please double-check and get back to me if you have further suggestions :)


Html output not working

This tutorial is very simple and easy, but even after following these steps I haven't been getting an output link for my coded UI tests.
I'm using the 2017 enterprise version and went to the config files. I wasn't sure which .NET framework I was using so I first tried one then the other. After each, I closed visual studio, reopened, built the solution, and ran one of my tests. There's no output option for my tests.
When I hardcode my individual tests using loggerOverrideState I do get the output link. Do you have any advice for what to do next if the instructions here don't work like what happened with me?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: beb72d4a-65af-25d0-82c9-ce448f513139
Version Independent ID: ff79c27a-44b9-21cf-fbdf-1af82246a3d6
Content: Analyzing Coded UI Tests Using Coded UI Test Logs - Visual Studio
Content Source: docs/test/analyzing-coded-ui-tests-using-coded-ui-test-logs.md
Product: visual-studio-windows
GitHub Login: @gewarren
Microsoft Alias: gewarren

@boraprachi or @pvlakshm Do you know if these instructions are still valid to enable logging?
Target .NET Framework version 4 with no App.config file present in the test project:

Open the QTAgent32_40.exe.config file. By default, this file is located in %ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE.
Modify the value for EqtTraceLevel to the log level you want.
Save the file.

Target .NET Framework version 4.5 with no App.config file present in the test project:

Open the QTAgent32.exe.config file. By default, this file is located in %ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE.
Modify the value of the EqtTraceLevel to the log level you want.
Save the file.

Oops, tagged the wrong Prachi Bora @PBoraMSFT.

@gewarren : Yes, these instructions are still valid.
You should see which QTAgent*.exe process is getting launched for running the tests and modify the value of EqtTrace in that particular QTAgent*.exe.config file.

@goldilocked Perhaps watch the Details tab in Task Manager to see which QTAgent*.exe process is launched when you run the test. Then, modify the corresponding .config file, as Jayarani suggests. Also, do you have an App.config file in your test project?

I looked at details and saw QTAgent32.exe was running every time I ran a CodedUI test. I went and checked QTAgent32.exe.config and it's one of the files I changed when I first started trying to add automatic tracking.
I don't believe there's an App.Config for this specific test project. I looked and noticed that another test project for a different type of test has an App.Config, just to cover my bases I tried adding  in a systems diagnostics node to see if that would affect my tests, it didn't and I'm still getting one png instead of the full action html logging I should be getting. I don't see any other app.config files in the solution.
What I ended up doing was just adding Playback.PlaybackSettings.LoggerOverrideState = HtmlLoggerState.AllActionSnapshot; as the first line to every test. At this point it's not worth spending the extra time to get it to work automatically when I can copy and paste this line and get what I need. Especially when we're phasing out our CodedUI project soon to prepare for VS 2019
Thank you for your help, I appreciate you taking some time to help me with this issue!

i want my codedUI test log in text format rather then html file. how can i do that


⚠ Quirk Club Argentina (Payment Gateway) has degraded performance

In e1bad8a, Quirk Club Argentina (Payment Gateway) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/payment-gateway-ml) experienced degraded performance:

HTTP code: 200
Response time: 9618 ms

Resolved: Quirk Club Argentina (Payment Gateway) performance has improved in b9173c5.


CI failures in torch19

[x] test_tensorboard_writing (linux, win): #194
[x] test_empty_shared_dataset (win): #194
[x] test_transform[tuple-None-indices53-None-True] (linux): #194
[x] test_annotate (linux, win) #196
[x] test_apply_annotation (linux, win) #196
[x] test_scoped_anchor (linux, win) #197
[x] test_export_testcase (linux, win) #197
[x] test_tensorboard_writer (linux, win): #194
[x] test_queue_writer (linux): #194

linux: https://ci.preferred.jp/pytorch-pfn-extras.torch19-linux/73786/
win: https://ci.preferred.jp/pytorch-pfn-extras.torch19-win/73789/

The UserWarning raise while importing torch.utils.tensorboard can be resolved by updating setuptools to the newest version.

Now all CIs are green!


feat: raise NoDefaultIndexError from read_gbq on clustered/partitioned tables with no index_col or filters set

Please review https://github.com/googleapis/python-bigquery-dataframes/pull/636 first, as this PR builds on that.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes internal issue 335727141
🦕

Looks like test_read_csv_bq_engine_throws_not_implemented_error is a real failure. Will address.

Looks like test_read_csv_bq_engine_throws_not_implemented_error is a real failure. Will address.

Done! Looks like from https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.read_csv.html index_col=False is equivalent to our DefaultIndexKind.SEQUENTIAL_INT64. I see no reason to raise NotImplementedError in that case, so I've updated those tests and made some slight tweaks so that they are treated the same.


uuhelp_parser: add links to homepage and repo

When viewing the crate right now, apart from via looking at the dependencies it's hard to find the associated project and repository.
Add the missing info.

Thanks!


New version: SKDataAS.ORMCore version 202303211

- [X] Have you signed the Contributor License Agreement?

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow
Microsoft Reviewers: Open in CodeFlow

Duplicate of #100305


Column Formatting html attribute?

can I set attributes to export inside html?

            0.11251442

Yes. Some examples:
Currency USD
Percentage
Date
Date/Time

excellent, thanks a lot.


consider: use Loco.rs for the API

Hi, after reviewing the actix based code for your API, workers, migrations, and scripts, I believe if you move the API to be Loco based (https://github.com/loco-rs/loco) you'll be able to do without the boilerplate/infra code, and gain many more capabilities in the long run. Although Loco is "Rails for Rust", it suffers from virtually no bloat, it's Axum based, and you can compile away parts you don't need using feature flags.
Feel free to close if not relevant 👍

We are not focussed on switching the http stack at this moment. I picked actix because I'm most familiar with it. We can reevaluate in future and use Loco if it provides unique benefits over actix.


Output index for video sub-sampling

I'm looking into it, Simon. Any context you could offer about what settings you selected under the video recording menu would be helpful.

Great! I ticked "record video", "enable video sub-sampling", and "output video index". I think I set sub-sampling rate to -5 Hz.
When I un-ticked "output video index", I could successfully run an experiment while outputting a sub-sampled video.

These details are very helpful, thanks. I'll try to recreate it on my end.

I was able to recreate the error, and I think the issue has been fixed. It's working on my end. Let me know how it goes.


move to worker sites

Codecov Report

Merging #75 (62d9204) into main (a01a2dc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #75   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           53        53
  Lines          909       909
=========================================
  Hits           909       909

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 a01a2dc...62d9204. Read the comment docs.


CNF-11823: build manager and exporter with strictfipsruntime flag

As part of the for effort of achieving FIPS compliancy for NROP operator, this step is needed - both binaries must be built with the strictfipsruntime flag

/hold
let's consider this change after the branch-out of 4.16


Please consider documenting parameters and adding more examples.

For now it's difficult start working with the project.
The MVTools.denoise() get a lot of parameters, which have not obvious meaning.
Please consider adding parameters description and short usage guide (which is the best/fast for anime, movie, live movie ...) to the README.md.
And also please add example of preset usage (NOISY, FAST, ...).

The MVTools.denoise() get a lot of parameters, which have not obvious meaning.

All these functions do is wrap around the mvtools plugin, please see mvtools doc for more information.

The MVTools.denoise() get a lot of parameters, which have not obvious meaning.

All these functions do is wrap around the mvtools plugin, please see mvtools doc for more information.

May you adding link to the project README for other people?

There is still no link to the MVTool documentation in the README file.


how to use custom image for the Badges of any event?

Your best bet is probably to use a custom template:
https://github.com/mattlewis92/angular-bootstrap-calendar#custom-directive-templates


1.24 CSR rendered config not copied after node join

Summary
I have a HA cluster consisting of three nodes that we are currently upgrading to 1.24:
kubectl get nodes
NAME         STATUS     ROLES    AGE   VERSION
node-00-01   Ready      <none>   62m   v1.24.2-2+b841ff9cb797c4
node-00-02   NotReady   <none>   62m   v1.24.2-2+b841ff9cb797c4
node-00-03   NotReady   <none>   63m   v1.24.2-2+b841ff9cb797c4

We found when the two additional nodes join to node-00-01, they reach the state NotReady, whereas the initial node is Ready. It turns out the server certificates on the joining nodes never get regenerated once the CA cert is copied over. The contents of csr.conf just contained changeme, whereas the csr.conf.rendered contained all of the information we expected.
I ran the following snippet from the method produce_certs() which returns true, so I would suspect the certs should get regenerated:
#!/usr/bin/env bash

SNAP_DATA=/var/snap/microk8s/current
SNAP=/data/snap/microk8s/x1
produce_certs() {
    local force
    if ! "${SNAP}/usr/bin/cmp" -s "${SNAP_DATA}/certs/csr.conf.rendered" "${SNAP_DATA}/certs/csr.conf"; then
        force=true
        cp ${SNAP_DATA}/certs/csr.conf.rendered ${SNAP_DATA}/certs/csr.conf
    else
        force=false
    fi
    echo "$force"
}

produce_certs

In addition to this, we found that the --node-ip argument on node-00-02 or node-00-03 was reset to the ip of the node they were joining to node-00-01. This seemed to happen during the node join or after running microk8s refresh-certs -e server.crt.
What Should Happen Instead?

Certificates should regenerate on joining nodes.
Kubelet args --node-ip and/or --address arguments should not be set to the ip of the node they are joining to. Ideally, these arguments should be configured by the end user so they can configure the networking themselves.

Reproduction Steps

Deploy three microk8s nodes using v1.24.
Configure the --node-ip argument the kubelet's config file to match the IP set in /etc/hosts (must resolve to the hostname of the node).
As per the microk8s documentation, join the additional nodes to the first node.

Introspection Report
Contains sensitive data.
Can you suggest a fix?

Not too sure how to go about resolving the certs issue but manually copying the csr.conf and regenerating the server cert (followed by a restart) fixed it.
Avoid setting the --node-ip or --address arguments in kubelets config.

Are you interested in contributing with a fix?
Yes, happy to work on providing a fix given some advice on the problem/direction.

Hi @bc185174 thank you for reporting this.
Would it be possible to share some inspection tarballs from the nodes? We recently did a fix around node-ip [1] that is about to be released on stable. Thank you.
[1] https://github.com/canonical/microk8s/pull/3216


Potential Razor/Visual studio javascript bug

script defined above does gives script1006 due to the if condition clause. If you change the "distance<0" clause to true, everything works. I am guessing something in the razor engine may be causing this or I might be missing something simple.

Here is the script that does not return a script 1006

I think you have found a bug. The < character in your original scripts leads to invalid JavaScript in the generated .g.cs file. Repro code:
<script>
    Blazor.registerFunction('JavaScriptAlert', (message) => {
        var distance = 5;
        if (distance < 0) {
            alert(message);
        }

        return true;
    });
</script>

Result in .g.cs:
    builder.OpenElement(8, "script");
            builder.AddContent(9, @"
    Blazor.registerFunction('JavaScriptAlert', (message) => {
        var distance = 5;
        if (distance ");
            builder.AddContent(10, "< 0) {\n            alert(message);\n        }\n\n        return true;\n    });\n");
            builder.CloseElement();

Workaround: Replace < in JavaScript with <. After that change, generated JavaScript is correct and works as expected.
@SteveSandersonMS can you confirm that this is a bug? Or is this intended behavior and special characters like < have to be escaped in Blazor templates?

Thanks for reporting this.
Firstly, you're correct that the misinterpretation of the < character does look like a Razor parser bug.
However, putting <script> elements inside Blazor components is almost always a mistake. Blazor components are added and removed dynamically, and that's not compatible with <script> tags in general, whose effects cannot be removed by removing them from the document.
I'll file a separate issue to track prevention of <script> elements inside Blazor components. That will address the underlying issue better.

Filed #552


Hide Toolbar button if there are no TST parts on the current vessel.

Also, consider hiding toolbar button if there are no TST parts on the vessel. Would be really nice. Thanks!
It's already done in InfernalRobotics, if that helps.

Coded. In test.


SLH block-feedback

Since we have worked out the SLH rule for applying feedback to a whole block of output channels at once, this should be implemented in the circuit_algebra module.
We might also want to lift the restriction that Feedback can only happen from the bottom output channel (this adds needless permutations that make the resulting SLH expressions more complicated).
The printing and circuit visualization will also have to be modified, but we can internally expand the block-feedback into nested feedbacks to make this easy. Lastly, the documentation needs to be reviewed.

That's OK. There will be about 4 weeks until I can start working on it.
(Note that on more careful reading, multiple channel feedback was always there in the original references. Due to the generality and redundancy of the abstract formalism it is actually admitted on two separate levels.)
We''l see what turns out to be the best approach: a single permutation step to bring all the lines into a contiguous corner block, or the more direct solution of building a non-diagonal adjacency matrix (essentially permuting the I in I - S_{ff} instead).
For visualization I think we should avoid expanding to nested single channel feedbacks. That does not result in the circuit diagram we want to see.


Add regression test

This PR adds a regression test for #2958.

Coverage remained the same at 100.0% when pulling 97c7a35a2b25132646124612c0481bfbf45b7f92 on issue2958 into eb6541a30cd16a38afdf423d459051ef2c1005d6 on develop.


Feature request: execute multiple scenario's in one native feature file in specified order

When multiple scenario's are defined in one native feature file they are executed in reversed alphabetical order. This is caused by the line of code in NativeTestCase.swift:

testCaseClass.testInvocations().sort { (a,b) in NSStringFromSelector(a.selector) > NSStringFromSelector(b.selector) }

Without this sort operation the test invocations (aka 'scenarios') are executed in alphabetical order, which is natural for tests in an XCTestCase class. However, I found this unexpected behaviour when executing multiple scenario's from one native feature file. I would expect the scenario's to be executed in the order that they are specified.
My proposal is to remove the sort operation, and implement/refactor 'something' which makes sure that the scenario's are executed in the order that they are specified in the native feature file.
Any ideas, suggestions?

I'll be honest - I have no idea why that sort is there. I suspect to make the order consistent while I was debugging it, though you're right; the order is somewhat strange! I would also expect the test cases to be executed in the order they are defined. I can think of two ways to do this:

Add a property to NativeScenario which is it's position in the feature (though this will probably just be it's index in the NativeFeature's scenarios collection). Use this number instead of the selector name when sorting the tests

Add a number to the dynamically created test method name so that they run in the right order automagically (though this is relying on XCode being consistent in it's test run implementation!)

How is number 2 relying on Xcode? Assuming that we change the name of the test selector, and we maintain the call to sort, the order would be defined by that?
I don't have a strong preference for either, but perhaps number 2 would be slightly simpler to implement and understand.

Ah - yes you're right, we run each test ourselves inside that loop. Number 2 doesn't depend on Xcode at all! As long as we check that sort puts test2MySecondTest after test10MyTenthTest we should be fine :) I guess this is what unit tests are for!

@kerrmarin I agree with the option "Add a number to the dynamically created test method name" for simplicity reasons, and to keep a sorting operation in place so we don't need to rely on Xcode's sorting of tests in a XCTestCase class
@nap-sam-dean the sort should put test2MySecondTest before test10MyTenthTest right..?

@smaljaar I've updated my comment :)

@kerrmarin I guess this can be closed now #65 is merged?

Yup


body_entered collisions events are sometimes missed

Describe the bug
body_entered event of RigidBody2D is not always called when collision happens. This is frequent when the colliding body moves fast and bounces off a surface.
When comparing Godot Physics with Box2D it seems that Godot Physics always reports the collision successfully. However, with Box2D it is missed often. Most likely the event is not propagated to Godot side if the contact only happens during physics sub-stepping.
To Reproduce
Use the attached project. Play the scene. A ball is shot towards a wall and bounces off it. A message is printed when body_entered event is called for the ball.
Run it first with using Godot Physics. The message is always printed. Then try with Box2D. The message is usually not printed.
If you reduce the initial speed of the ball enough then the Box2D will also begin to print the message, but can still sometimes miss.
Expected behavior
Expected that body entered and exit events are reliably called as it does with Godot Physics.
Project
Attached test project
CollisionMissedBug.zip
Versions (please complete the following information):

OS: Windows 10
Godot v4.2 rc2
Box2d v0.9.2

Ok, I was checking if there was a separation in PostSolve, but there are cases when there isn't, and they are colliding. Anyway, probably I shouldn't check if they are colliding or not, since the callback is called anyway when collision happens(probl has to do with sub stepping). After I removed that if the events are generated correctly.


Some build failures on Windows don't stop Jenkins jobs

Some build failures like in http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-9798/1/pipeline/432 don't seem to stop the Jenkins jobs. Instead, it probably halts the process, but since it does not terminate, Jenkins thinks that it is still running.
An intermediate solution would be to reduce the timeout of Jenkins job. Long term solution would be a proper termination of the process and thus immediate failure detection by Jenkins.

@marcoabreu Has this issue been resolved ?

Nope

@marcoabreu @piyushghai Any update? resolved yet?


db.update $pull on array of objects

Hi, more of a question than an issue.
I have a document containing an array of objects.
{
  "_id": "abcd1234",
  "name": "randomStuff",
  "list": [
    {
      "name": "the first element",
      "value": "1234"
    },
    {
      "name": "the second element",
      "value": "5678"
    }
  ]
}

And I wish to update this document by removing a determined object in the array.
I used db.update with the $pull.
var toRemove = {
  "name": "the first element",
  "value": "1234"
};

db.update({_id: 'abcd1234'}, {$pull: {list: toRemove}}, {}, (err) => {
  console.log(err);
});

But I get Error: Unknown logical operator $$hashKey.
Is it a bug or just that the $pull does not support "object matching" ?
Thanks!

After some time I found out that some other lib did inject some attributes in my object so it was not the same when updating.


Publish @next on npm

Agreed, publish release v2.0.0 on npm.

@vkurchatkin, can you give me npm publish access?

I have fork this and publish koa2-connect on npm, wish this will help you guys :smile:
P.S. Also has improve compatibility with webpack-dev-middleware and webpack-hot-middleware.

Hey @cyrilluce, that definitely encouraged me, thank you. I just published v2.0.0 on npm and I'm very happy to incorporate the code on your fork. If you're inclined to re-merge the projects, please open a PR and we can start the discussion.

@olconstant 	Can you please email me<EMAIL_ADDRESS>- been trying to get in touch about something re: blogging/tech and can't find your public email anywhere haha, I tried a few I found but they all bounced back


namespace hijacking; CGMES-NC Header-AP-Voc-RDFS2020 wrong terms

These terms in CGMES-NC Header-AP-Voc-RDFS2020 are junk: not meaningful names, namespace hijacking (dcat, dcterms), start with uppercase. Must be fixed:
dcat:Resource7 a rdf:Property ;
dcat:Resource8 a rdf:Property ;
dcterms:Resource1 a rdf:Property ;
dcterms:Resource10 a rdf:Property ;
dcterms:Resource11 a rdf:Property ;
dcterms:Resource12 a rdf:Property ;
dcterms:Resource13 a rdf:Property ;
dcterms:Resource2 a rdf:Property ;
dcterms:Resource3 a rdf:Property ;
dcterms:Resource4 a rdf:Property ;
dcterms:Resource5 a rdf:Property ;
dcterms:Resource6 a rdf:Property ;

Here both the URL and type are wrong:
rdf:LangString a rdfs:Class ;

The correct is rdf:langString a rdfs:Datatype. Please fix the URL (you use as cims:dataType) and don't repeat a definition (it's a standard term).
The URL is wrong (uppercase), and the comment has a grammatical error:
prov:Entity a rdf:Property ;
  rdfs:comment "The entity that generated by this activity." ;

These external terms are defined anew. This is considered namespace hijacking and should be avoided.
Unless there's a good reason for it, eg you change the definition to something more appropriate to CGMES/NC, or fix the domain.
adms:versionNotes a rdf:Property ;
dcat:endDate a rdf:Property ;
dcat:hasVersion a rdf:Property ;
dcat:inSeries a rdf:Property ;
dcat:isVersionOf a rdf:Property ;
dcat:keyword a rdf:Property ;
dcat:nextVersion a rdf:Property ;
dcat:previousVersion a rdf:Property ;
dcat:seriesMember a rdf:Property ;
dcat:startDate a rdf:Property ;
dcat:temporalResolution a rdf:Property ;
dcat:version a rdf:Property ;
dcterms:accessRights a rdf:Property ;
dcterms:accrualPeriodicity a rdf:Property ;
dcterms:conformsTo a rdf:Property ;
dcterms:creator a rdf:Property ;
dcterms:description a rdf:Property ;
dcterms:identifier a rdf:Property ;
dcterms:issued a rdf:Property ;
dcterms:license a rdf:Property ;
dcterms:publisher a rdf:Property ;
dcterms:references a rdf:Property ;
dcterms:replaces a rdf:Property ;
dcterms:rights a rdf:Property ;
dcterms:rightsHolder a rdf:Property ;
dcterms:source a rdf:Property ;
dcterms:spatial a rdf:Property ;
dcterms:title a rdf:Property ;
dcterms:type a rdf:Property ;
euvoc:status a rdf:Property ;
prov:atLocation a rdf:Property ;
prov:generatedAtTime a rdf:Property ;
prov:hadPrimarySource a rdf:Property ;
prov:specializationOf a rdf:Property ;
prov:wasAttributedTo a rdf:Property ;
prov:wasGeneratedBy a rdf:Property ;
prov:wasInfluencedBy a rdf:Property ;
prov:wasRevisionOf a rdf:Property ;

I doubt the value of redefining external terms.
Eg this one has 2 unmerged definitions.
And if it's deprecated, why even use it and redefine it?
dcat:hasVersion a rdf:Property ;
  rdfs:comment
"""This resource has a more specific, versioned resource.
This property is intended for relating a non-versioned or abstract resource to several versioned resources, e.g. snapshots [PAV].
The notion of version used by this property is limited to versions resulting from revisions occurring to a resource as part of its life-cycle. Therefore, its semantics is more specific than its super-property dcterms:hasVersion, which makes use of a broader notion of version, including editions and adaptations.
This property is deprecated.""",

"""This resource is a version of a non-versioned or abstract resource.
This property is intended for relating a versioned resource to a non-versioned or abstract resource.
The notion of version used by this property is limited to versions resulting from revisions occurring to a resource as part of its life-cycle. Therefore, its semantics is more specific than its super-property dcterms:isVersionOf, which makes use of a broader notion of version, including editions and adaptations.""" ;

In the last release we clean up the deprecated stuff.
On the part dcterms:Resource6 a rdf:Property  this comes from the declaration of the inverse associations. in order to be able to export them we need for association end role name and in cases where dcat or cterms does not define we had to invent something.
We need to discuss how to solve this.

In ontologies, it is recommended to just use external terms (optionally using owl:imports), but not redefine them.
In the UML you cannot use an external term unless you also define it in the UML?

While analyzing datatype prop ranges, I found more cases of namespace hijacking.
@Sveino PowerSystemProjectGroup is brand new, right?
So @griddigit-ci please check whether "In the last release we clean up the deprecated stuff" is actually done.
dcat:Resource.hasVersion	xsd:anyURI
dcat:Resource.isVersionOf	xsd:anyURI
dcat:Resource.keyword	xsd:string
dcat:Resource.version	xsd:string
dcat:Resource.versionNotes	xsd:string
dcat:endDate	xsd:dateTimeStamp
dcat:keyword	xsd:string
dcat:startDate	xsd:dateTimeStamp
dcat:temporalResolution	xsd:duration
dcat:version	xsd:string
dct:PowerSystemProjectGroup.description	xsd:string
dct:PowerSystemProjectGroup.identifier	xsd:string
dct:PowerSystemProjectGroup.title	xsd:string
dct:Resource.accessRights	xsd:string
dct:Resource.conformsTo	xsd:string
dct:Resource.creator	xsd:string
dct:Resource.description	xsd:string
dct:Resource.identifier	xsd:string
dct:Resource.issued	xsd:dateTime
dct:Resource.license	xsd:string
dct:Resource.modified	xsd:date
dct:Resource.publisher	xsd:string
dct:Resource.rights	xsd:string
dct:Resource.rightsHolder	xsd:string
dct:Resource.title	xsd:string
dct:description	xsd:string
dct:identifier	xsd:string
dct:issued	xsd:dateTime
dct:rights	xsd:string
dct:rightsHolder	xsd:string
dct:title	xsd:string
rdf:Statement.object	xsd:string
rdf:Statement.predicate	xsd:string
rdf:Statement.subject	xsd:string

Also, CGMES-NC/ttl/Header-AP-Voc-RDFS2020 defines a dataspace dcat-cim: in which it creates its own versions of dcat terms.
This is a veiled form of namespace hijacking. Simply use DCAT terms, don't define your own versions.

dcat-cim should only represent the CIM extension of DCAT. I have send an email addressing the detail.

Fixes md:Model.version from xsd:integer (IMHO wrong) to xsd:string)
I agree. This is not a problem when converting md:Model.version -> dcat:version but the revers would be difficult. I think we just then break the md:Model.version contraints.

dcat-cim: do you need another namespace for just a few terms? You got md.
Version as integer: then eg "002" would be returned as 2. And using multiple components may make sense, eg "2.5.3"

The plan is to move away from md and dm. If you like the dcat-cim (needed for alternative dataset) we will try to get it into dcat standard.
I am OK that we might have issue to move from dcat:version to md:version.

you ask:

PowerSystemProjectGroup is brand new, right?
Yes, but I think we need to change this model. However, both PowerSystemProjectGroup and PowerSystemProject should be in NC namespace.

What props will you have in dcat-cim?
As for proposing it for standardization: I'm at https://semantic.internationaldataspaces.org and right now there's a big discussion of DCAT profiles (DCAT-AP, GeoDCAT-AP, BregDCAT-AP, MobilityDCAT-AP, etc) and people are saying "that's too many!"
Maybe coming from the electricity industry your additions will be accepted. But even if it doesn't get accepted for standardization, doesn't mean you cannot use these new props

We should have a discussion on this on how to proceed


增加菜单进入小程序事件

关联issues
https://github.com/jxtech/wechatpy/issues/389

Codecov Report

Merging #397 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #397   +/-   ##
======================================
  Coverage    72.7%   72.7%
======================================
  Files          74      74
  Lines        2671    2671
======================================
  Hits         1942    1942
  Misses        729     729

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 f8bea22...5458643. Read the comment docs.


No module named "OpenApiCommonModelMessages_pb2"

Got this error message when doing:
python OpenApiClient.py
Using python 3.9 as required.
Rem:  the project requires also: pip install protobuf

Hi,
This project is not finished yet and we just started developing it.
Please wait for a release.


Add JSONP support for monitoring routes

See #100

Also, the response content-type for jsonp is application/javascript

Damn finally...

@pkieltyka : done, thank you :smile:

If not done already could someone update README to reflect the JSONP functionality?

@derekcollison : What kind of information you want to see in README related to this PR?
P.S.: Personally I'm thinking that README.md should be very lightweight for first impression. JSONP is a low level detail which should be in another file. Perhaps in a dedicated monitoring documentation or a file named API.md in root folder which contains everything about gnatsd with all the details.

The README has a monitoring section, just add a one liner that says it
supports JSONP via the callback arg and a simple example. No need for each
endpoint, just one IMO..
On Tue, Aug 18, 2015 at 5:29 PM, Fatih Cetinkaya<EMAIL_ADDRESS>wrote:

@derekcollison https://github.com/derekcollison : What kind of
information you want to see in README related to this PR?
P.S.: Personally I'm thinking that README.md should be very lightweight
for first impression. JSONP is a low level detail which should be in
another file. Perhaps in a dedicated monitoring documentation or a file
named API.md in root folder which contains everything about gnatsd with
all the details.
—
Reply to this email directly or view it on GitHub
https://github.com/nats-io/gnatsd/pull/103#issuecomment-132402750.

This good to go?

I just added a note to README about JSONP. I think it is okay to go...


GitHub - Find repositories with vulnerabilities (Dependabot)

As a GItHub administrator,
I want to find in the organization I manage all the repositories for which there are alerts of vulnerabilities
So that I can contact project's maintainers

See GraphQL API doc for GitHub

See also this explorer and this thread in Stack Overflow


fastlane match appstore – 503 Service Temporarily Unavailable

Discussed in https://github.com/fastlane/fastlane/discussions/21178

Originally posted by SinceTheCross April  4, 2023
[14:34:07]: Starting login with user ''
Available session is not valid any more. Continuing with normal login.
Unable to find 'X-Apple-HC-Bits' and 'X-Apple-HC-Challenge' to make hashcash
Looking for related GitHub issues on fastlane/fastlane...
➡  Reading keychain entry, because either user or password were empty
https://github.com/fastlane/fastlane/issues/21119 [open] 1 💬
2 weeks ago
➡  Action to inject a specific properties file to override one in an IPA?
https://github.com/fastlane/fastlane/issues/503 [closed] 3 💬
26 Sep 2016
🔗  You can ⌘ + double-click on links to open them directly in your browser.
[!] The request could not be completed because:

503 Service Temporarily Unavailable

503 Service Temporarily Unavailable
Apple

After executing fastlane match appstore, this error was returned, but the system certificate has been successfully imported

Hy there i can see your post and i must say
Here are a few steps you can take to troubleshoot this issue:
Retry Later: Since the error message suggests that the server is temporarily unavailable, it's a good idea to wait for a while and then try the command again. The issue might be resolved on the server side.
Check Server Status: If you suspect that the issue might be on the server side, check the status of the service you're trying to access. You can check the status of Fastlane's services on their official website or forums.
Network Issues: Ensure that you have a stable internet connection. Sometimes, connectivity issues can lead to server-related errors.
Thanks and regards
MarjoriJohnson

first try not to using too many match method at once
if first step still not resolve your error, try clean fastlane spaceship cookie

rm $HOME/.fastlane/spaceship/*/cookie

I just have same issue a moment ago !

well , turn out
rm $HOME/.fastlane/spaceship/*/cookie
is beneficial. i was noticing a strange message
'Available session is not valid anymore. Continuing with normal login.'
which is not helpful but it seems that fastlane doesn't invalidate the session as it should be.
deleting cookies made me relogin again and enter my 2FA cred. which helped

Same here:

bundle exec fastlane match nuke distribution

Give the same answer for 4 days straight. Any solutions?

Hey @vbrunko-voc, update fastlane to the latest version did the thing for me!
https://github.com/fastlane/fastlane/releases/tag/2.225.0

Please update faslane with - fastlane_update_fastlane

@paullbn @sahilnag08
Thank you, worked for us


fix(idempotency): TypeError when calling is_missing_idempotency_key with an int

Description of changes:
Fix for is_missing_idempotency_key which  can raise a TypeError: 'int' object is not iterable
for the follow code
BasePersistenceLayer.is_missing_idempotency_key(1000)

Checklist

[x] Meet tenets criteria
[x] Update tests
[x] Update docs
[x] PR title follows conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #315 (038190c) into develop (b6e61e2) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #315      +/-   ##
===========================================
- Coverage    99.88%   99.82%   -0.06%
===========================================
  Files           91       91
  Lines         3340     3345       +5
  Branches       162      165       +3
===========================================
+ Hits          3336     3339       +3
- Misses           2        4       +2
  Partials         2        2

Impacted Files
Coverage Δ

...wertools/utilities/idempotency/persistence/base.py
99.36% <100.00%> (+0.02%)
:arrow_up:

aws_lambda_powertools/utilities/parser/types.py
71.42% <0.00%> (-28.58%)
:arrow_down:

aws_lambda_powertools/metrics/base.py
100.00% <0.00%> (ø)

aws_lambda_powertools/metrics/metrics.py
100.00% <0.00%> (ø)

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 b6e61e2...038190c. Read the comment docs.

@heitorlessa  funny way of doing it:
assert type(None).__name__ == "NoneType"

First name I actually see type(obj).name tbh as opposed to instance ;)
On Sun, 7 Mar 2021 at 09:09, Michael Brewer<EMAIL_ADDRESS>wrote:

@heitorlessa https://github.com/heitorlessa funny way of doing it:
assert type(None).name == "NoneType"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/pull/315#issuecomment-792236028,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZPQBEY43RE5PTXNUQ4JC3TCMYB3ANCNFSM4YXRJGBQ
.


[WIP] Registration Status

This is a WIP to make the register button work appropriately. It's a WIP because I still need to do:

[ ] title view layout
[ ] tests for title view
[ ] tests for network models (see below)

This PR makes significant changes to the networking done in the auctions' network models, and I'd like to explain my reasoning. I've broken each request-type (fetch the sale, the sale artworks, and the registration status) into their own network models. They can all fetch exactly one thing, and then store that thing locally. That's it. I want to keep these super-lean and follow the single-responsibility principle.
I think that's easy to get behind, but I have each fetch function return a Signal, and then the AuctionNetworkModel just calls the others' fetch methods and assembles the results. It's doing this with Interstellar, so I'm cautious about going too outside eigen's reference frame.
If the general idea of isolating network models sounds good, I'll add some tests. If you have feedback on the use of Interstellar, please let me know :+1:
Fixes #975.

OK, merged latest in from master. Going to continue to work on the three remaining TODO items.

  | 1 Error
------------- | ------------
    :no_entry_sign: | No CHANGELOG changes made

  | 2 Warnings
------------- | ------------
    :warning: | PR is classed as Work in Progress
    :warning: | Needs testing on a Phone if change is non-trivial

  Generated by :no_entry_sign: danger

Alrighty! Managed to get some coding in today. Likely won't get a chance to look at this until Friday, there's a showstopping Kiosk bug that needs to be fixed before the Friday Mocktion.
This "works" but is untested. Oh, and it doesn't actually work:

Haven't had a chance to really dig into it. It looks like the header stack view is getting covered up by the sticky header. @orta if you have a chance, I'd love some suggestions on this.

Oh, and there's a missing "info" button asset I need to add >.<

. It looks like the header stack view is getting covered up by the sticky header. @orta if you have a chance, I'd love some suggestions on this. I tried rotating to force a re-layout but no dice.

You need to make sure the stack is fully re-laid out before triggering to the collection view that the height has changed

@orta the problem was on my end, forgot the - on a bottom-edge constraint.
I've decided to punt on the view tests, because the other constituent views aren't tested either, and I think the tests more properly belong in the view controller snapshot tests in #972  (instead of testing each view individually + aggregated in the view controller anyway, no need to redundantly test, but this might warrant a bigger discussion).
iPhone:

iPad:

CI was failing comparing two (ObjC) enums in my Swift unit tests. I've updated Circle's config to Xcode 7.1 to try and fix.

Danger is complaining of a missing changelog entry, but there is one there... Maybe we're behind on versions.

Will look on Monday, stuck with a phone for a bit

Danger thing is known, been wondering I'd the commit range is wrong

Cool cool – commit range sounds plausible, this is a pretty long-lived PR.

I disagree with respect to not doing the tests for the view, ideally we want to be creating re-usable UI components, testing at the view level encourages that. Moving this up to VC level means we get a lot of "AuctionXXXView" views which are now only really useful within one context, and no-one will think to re-use them.

Looks good, only this might make more sense as raiseError ? is a blocker :+1:

ideally we want to be creating re-usable UI components

Agreed, will add some tests. Probably will involve moving testing traits to Forgeries.

OK, so we're using a branch of Forgeries pending https://github.com/ashfurrow/Forgeries/pull/15 getting merged. I added tests for the title view as requested, using both iPad and iPhone. I know we have something like this already for device-independent snapshotting but that's mainly around UIDevice, I think? So it may be worth thinking of a better abstraction for trait classes. But not right now >.<

OK! Got that other PR merged, and moved this to Forgeries 0.6.1.

"I think this is good for final review", he said trepidatiously.

But in the past tense, yay!


Add reno releasenote configuration

example, to be reviewed

There's already this:
https://github.com/salt-formulas/salt-formula-nova/blob/master/Makefile#L73
https://github.com/salt-formulas/salt-formula-nova/blob/master/CHANGELOG.rst
Do we have some more specific use-cases than using git commit messages for generating changelogs?

@fpytloun commented on Jul 11, 2017, 3:54 PM GMT+2:

There's already this:
https://github.com/salt-formulas/salt-formula-nova/blob/master/Makefile#L73
https://github.com/salt-formulas/salt-formula-nova/blob/master/CHANGELOG.rst
Do we have some more specific use-cases than using git commit messages for generating changelogs?

There is whole epic/user-story for MCP for release notes and upgrade documentation. Reno is one of the tool's that would be easy to automate, native and recognized withing the community. Currently we want to evaluate it. Basically we head for release notes for MCP/Formulas and upgrade instructions (a separate documentaion within MCP) to cover features and important fixes. vs. track commit history. Pls. Reach R.Satek on slack.

Re failed tests - Seems a revision is not available on travis. Bug reported here: https://bugs.launchpad.net/reno/+bug/1703603

test's now passing can be merged.


Page0 Retry for failed authentication request

Retry RETRY_COUNT times at intervals of RETRY_INTERVAL_SEC seconds as specified on src/app/settings.ts
Open new tab with the failed request url, as cloud orchestrators ought to redirect the request to the url for authentication

@ikicha @k311093 PTAL
To be merged after #187


RHEL compatibility

Description
Since this is still the official chrony cookbook, and there are still people that want it working on RedHat distributions, it might be worth retrying the closed Pull Request by sspans, along with an extra parameter for the chrony.conf file location, since it's also different when installed with yum.
Issues Resolved
https://github.com/chef-cookbooks/chrony/issues/4
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

It seems like there is Cookstyle failing. Is there any progress on this?

Closing this since we merged in #8


base: use default values for options

I can't seem to re-open #348, but this PR should fix #346 as per comments there. :+1:

thank you for this @lewiscowper, we hope to receive more contributions from you. :beers:


Minor rough spots.

@m-reza-rahman, have you signed the contributor agreement or is Microsoft a signatory? The agreement is here: https://github.com/oracle/weblogic-kubernetes-operator#contributing-to-the-oracle-weblogic-server-kubernetes-operator-repository

Please close this PR. Cc: @m-reza-rahman  @rjeberhard  @mriccell   See #1940.

This PR is superseded.


new schunk description structure

merge with: https://github.com/ipa320/schunk_modular_robotics/pull/124

What are the changes in the cob3.rviz file for?

oh, my bad ,I should commit it in a separated pull request...
The problem was the joint name of the kinect, should be cam3d_link instead of head_cam3d_link , there was no transform between head_cam3d_link and cam3d_frame and was not possible see the PointCloud in RVIZ: https://github.com/ipa320/cob_common/commit/cf7d1dbff1cdb300282c393896bfc2271dfca0a0

visual review: OK


Added accessors

@gnavvy -  All positions now use array format and all layers use accessors that application can override.

Apps no longer have to transform data to a specific format to use deck.gl.
Also apps can now pass any iterable objects (e.g. Immutable Lists) as deck.gl data props.

This is a breaking change that will be merged to dev branch and initially published in a 3.0.0 beta release.

@gnavvy - Some work still remains on Choropleth and Grid Layers.

Addressed @gnavvy's review feedback


Update test vectors per the RFC README

Originally opened as https://github.com/interledger/java-crypto-conditions/issues/55
The cryptocondition spec's README has some test vectors for library validation. There is a PR (rfcs/crypto-conditions/pull/14) that adds some additional vectors. We should ensure that the java library has full support for all test vectors.

Before implementing this fix, we should instead prefer completing #7, which will probably negate this as an issue.


Is ovpn import supported by SoftEther client?

Can I import ovpn file to and connect to third-party server (not SoftEther)? I used paid VPN service and was given a config.

SoftEther Client only supports SoftEther own VPN protocol. So it is not feasible to support the import function of another protocol
Did that answer your question?

Yes, indeed.


restart server then all shop disappear

It is very buggy.. so disappointed. Now it is 5 times for my server....
Paper version git-Paper-1430
ShopChest version 1.12.3
MYSQL version.

same exact thing just happened to my server when we updated to paper. and i really love this plugin. hope to see the issue solved. would help if you posted the error log tho

This only happens with Paper, but it should be fixed with 7874262 (wait for the next update).


Updates to the setup script and the run script

Brought the setup script better in line with the gcm version, for easier maintenance.
Removed lines in the setup script related to REPLAY, since CTM does not run REPLAY.
In ctm_run.j: fixed the transition date between MERRA2_300 and 400.

DO NOT APPROVE yet...  this needs one more revision

OK for approval now


why allways  retrun that, i can't find what problom {'code': 500, 'message': 'Request Timeout'}

why allways  retrun that, i can't find what problom {'code': 500, 'message': 'Request Timeout'}

I'm experiencing a similar issue. In my local setup, everything is functioning correctly. However, when I deploy it to production, I encounter a Timeout error.
Any clue or troubleshoot?

I've seen this happen for a few reasons:

curl_cffi interfering with 'requests'
ip banned by CF

i think the ip u used to scrape is blocked by cloudflare. you should try adding proxy to the request.

I have updated. Please check again with the latest version. If the problem persists, you can add blockMedia: false to the request.


how to open another file in the new frame after split the editor window?

I can use C-w s to split the window now, but the split window will open the same file.
I have no way but to use mouse to click another file on the project navigator. it is really hard for me.
does there any method to open another file in the splited frame,
like vim :e somefile. and a xcode-shortkey.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9989228-how-to-open-another-file-in-the-new-frame-after-split-the-editor-window?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github).

How about Cmd-Shift-O to search for the file you want to open in the other window, then press Opt-Enter to open it.

I think this is honestly the most acceptable answer. I don't believe there is any funtionality for opening files via XVim. This kind of makes sense as Xcode doesn't always care about filesystem layout and implementing an 'e' command could prove more difficult than it seems.
I suggest this be closed out and the workflow mentioned above be used, if keyboard shortcuts are desired. Otherwise, opening a XVim split and then using the mouse is about your only other option.


use create_new_auth_token for sign up

This PR re-uses the create_new_auth_token method in the session controller.  Previously the code was not limiting the number of tokens generated.  It now uses a method that checks the max_number_of_devices config.

@mgwidmann review please

@mgwidmann updated

:+1:

@weddingwire/code-review review please

Is this a bug with the actual gem that you should open a PR for them to merge the fix too?


Issue41460: Type conflict on infer fields

Rationale
An error arises when a field's type is inferred, but past the number of values used to infer that type, there is a value that conflicts with the already-inferred type. The changes allow the user to return to their domain and make manual edits to the field types.
Related Pull Requests

https://github.com/LabKey/labkey-ui-components/pull/389

Changes

Update components version

@RosalineP FYI, I kicked off a targeted TeamCity run of the following tests so that we can verify for any regressions. Looks like the BVTs didn't have coverage for the file import case, but these tests should cover it:
DailyA: SharedStudyTest,ListTest,NabAssayThawListTest
DailyB: AssayExportImportTest
DailyC: StudyScheduleTest,StudyExportTest,MultiplePKUploadAssayTest,SampleTypeTest


Website redesign

Redesign of projectelectron.rockarch.org with new multi-page Jekyll theme. Compiles project content including transfer specification, project values, user research artifacts, and basic information about the project.
The components.md page needs attention, as I would like a review of how much detail to include (particularly in the Repository and Discovery sections at the end).
In general, a fresh eye to find any glaring problems or omissions would be appreciated, and any feedback on design is welcome.

I made some changes - implemented cards, embedded the gist scripts into the site, and made a few styling tweaks. @helrond let me know if you think this needs anything else before merging.


[MM-23997] Ensure channel mentions permission is set on edit post

Summary

Pass useChannelMentions to the Textbox component on the edit post modal

Ticket Link
https://mattermost.atlassian.net/browse/MM-23997
Screenshots

@fmunshi
Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Fetching origin
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-#5296-upstream-release-5.22-1586469791
Branch 'automated-cherry-pick-of-#5296-upstream-release-5.22-1586469791' set up to track remote branch 'release-5.22' from 'upstream'.
+++ Downloading patch to /tmp/5296.patch (in case you need to do this again)

+++ About to attempt cherry pick of PR. To reattempt:
  $ git am -3 /tmp/5296.patch

Applying: MM-23997 Ensure channel mentions permission is set on edit post
Using index info to reconstruct a base tree...
M	components/edit_post_modal/edit_post_modal.jsx
M	components/edit_post_modal/edit_post_modal.test.jsx
M	components/edit_post_modal/index.js
Falling back to patching base and 3-way merge...
Auto-merging components/edit_post_modal/index.js
Auto-merging components/edit_post_modal/edit_post_modal.test.jsx
Auto-merging components/edit_post_modal/edit_post_modal.jsx
CONFLICT (content): Merge conflict in components/edit_post_modal/edit_post_modal.jsx
Patch failed at 0001 MM-23997 Ensure channel mentions permission is set on edit post
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

+++ Conflicts detected:

UU components/edit_post_modal/edit_post_modal.jsx

+++ Aborting in-progress git am.

+++ Returning you to the master branch and cleaning up.


Update ReadMe in section Example for 3.1.x.

Project still under development?

Thanks for the contribution.
I do not understand the changes you made. You changed the method references to lambdas? What is the idea behind this? I prefer the method references because they are more concise and equally clear.
No, this code is not under development any more. The 3.1 version is  in production since 2014. However the 3.0 code has some contributions i want to add to the 3.1 code base.

Hi,
thx for your answer.
I haven't see any release 3.1.x in the release section (newest is infomas-asl-3.0.5 from 19.Oct.2015). I want to integrate you branch release-3.1 (or the release jar 3.1) directly in my little library Lib-Action ( https://github.com/Naoghuman/lib-action) because I want to use the Lambda version (3.1.x) there.
The original example with method references in section Example Usage (3.1.x versions) in the ReadMe don't work for me. When I changed to the lamdas (see in my commit) then the code works and I can scan the classes and methods like in your example with my own annotations. See also the method scan() in ActionFacade#scan().
So I think there is a typo in your example section.

Ok, clear. Will take a look at it. Will be next Wednesday.
And the code is not released to Maven Central. Will fix that too (this todo is way too long overdue :( )


Reduce the verbosity of the slack reporter

Hi @ngs ! First-off, great job on the integration!
How can you reduce the verbose logs from test suit? Currently, it logs the result from each test case that runs within a test suit, which sometime may contain 10-20-30 or more test cases. How to make logs in Slack to show the total number of passed/failed test cases but without verbose output for each test case?

Actually the latest pull request (https://github.com/ngs/nightwatch-slack-reporter/pull/3) has solved the problem. Your can set slack_send_only_failed_tests : true  to achieve this.
However, this feature is not updated in the npm repo yet. (As npm nightwatch-slack-reporter stills downloads commit from Sep, 2016)

Resolved it


Flatpak/AppImage release

Describe the solution you'd like
Would it be possible to have either a Flatpak or AppImage release for Linux? great app :)

Thanks! Flathub is on roadmap, but not sure when I manage to release wallet there,
https://github.com/users/steel97/projects/2