Latest circe-java8 no more defines Defaults time enc/decoders.

Regression with circe-java8 0.10.0 (0.9.3 does not exhibit that issue).
These are used here:
https://github.com/twilio/guardrail/blob/4e45d6b3c9df6f5b6ab9306fb086ea1d7eeaf1a9/modules/codegen/src/main/scala/com/twilio/guardrail/generators/CirceProtocolGenerator.scala#L340-L355
But no more defined:
https://github.com/circe/circe/blob/master/modules/java8/src/main/scala/io/circe/java8/time/JavaTimeDecoders.scala#L184
The methods have been renamed.
I'm new to Guardrail / Circe / etc.. wondering how / if I could help with it..

So, to start, welcome! Thank you for the report!
Looking at these implicits do:
implicit def decodeInstant: Decoder[Instant] = j8time.decodeInstant.or(decodeLong.map(Instant.ofEpochMilli))
implicit def decodeLocalDate: Decoder[LocalDate] = j8time.decodeLocalDateDefault.or(decodeInstant.map(_.atZone(ZoneOffset.UTC).toLocalDate))
implicit def decodeOffsetDateTime: Decoder[OffsetDateTime] = j8time.decodeOffsetDateTimeDefault.or(decodeInstant.map(_.atZone(ZoneOffset.UTC).toOffsetDateTime))

// Mirror
implicit val encodeInstant = j8time.encodeInstant
implicit val encodeLocalDateDefault = j8time.encodeLocalDateDefault
implicit val encodeLocalDateTimeDefault = j8time.encodeLocalDateTimeDefault
implicit val encodeLocalTimeDefault = j8time.encodeLocalTimeDefault
implicit val encodeOffsetDateTimeDefault = j8time.encodeOffsetDateTimeDefault
implicit val encodeZonedDateTimeDefault = j8time.encodeZonedDateTimeDefault

decodeInstant:

Attempts to decode an Instant using whatever format is default to circe's java8 time formatter.
If that fails, we attempt to parse a long and treat it as Epoch Millis (:exclamation:)

decodeLocalDate:

Attempt to decode a LocalDate using whatever format is default to circe's java8 time formatter.
If that fails, we attempt to decode an instant and assume it's UTC (:exclamation:)

decodeOffsetDateTime:

Attempts to decode an OffsetDateTime using whatever format is default to circe's java8 time formatter.
If that fails, we attempt to decode an instant and assume it's UTC (:exclamation:)

It would be good to break the fallback handlers out into explicit vendor extensions if these are actually desirable. Instead of type: string and format: date-time secretly handling milliseconds, it would be better to have type: integer and format: int64 with a vendor extension that specifies that the values are actually UTC milliseconds (or nanoseconds, or seconds).
Once an answer is determined for how to handle these fallback scenarios, describing a new type that represents the transition between Long and OffsetDateTime could look like this:
case class EpochMillis(value: OffsetDateTime)
implicit val encodeMillis: Encoder[EpochMillis] =
  Encoder[Long]
    .contramap[OffsetDateTime](_.toInstant.toEpochMilli)
    .contramap[EpochMillis](_.value)
implicit val decodeMillis: Decoder[EpochMillis] =
  Decoder[Long]
    .map(Instant.ofEpochMilli _)
    .map(_.atZone(ZoneOffset.UTC).toOffsetDateTime)
    .map(EpochMillis.apply _)

This would not be exposed to the user directly, similar to how respond members or file upload parts work.
I don't have answers about exactly how this should work, from a user perspective though, or from what already exists in the broader OpenAPI community though. What do you think?

@blast-hardcheese I think there's two issues here - correct me if I'm wrong.

A change in circe-java8 which prevent compiling.

Fallback handling to millis which is very implicit and should be corrected.

is a Show stopper for upgrading circe.

is a Bug that should be resolved (a breaking change if someone secretly relies on it).

Am I correct?
If so I propose to split the issue.


Add ReadOnly property to readOnlyLDAPuserStore

Purpose
Fixes : https://github.com/wso2/product-is/issues/17659

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6926125547

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6926125547
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6929135733


index.md: made LoadBalancer Ingress a valid IPv4

I signed it!

@ceocoder thanks man, good find!

@cdrage np, years of watching Hollywood movies and saying "Wait! that is not a real IP!" made it easy.  Like this one,


call pipe2 directly on Linux

A first shot at fixing https://github.com/nix-rust/nix/issues/414. This approach keeps the old implementation for platforms other than notbsd, because libc only exposes pipe2 in the notbsd module.
I've tested this by hand on my Linux machine in a couple ways:

Create a toy program that opens a pipe and passes it to cat, which hags if O_CLOEXEC doesn't get set properly. Confirm that it doesn't hang, but that it does if I pass 0 as the flags to libc::pipe2.
Delete the new implementation entirely, and delete the cfg guards on the old implementation, and confirm that above is still true.

I haven't actually tested a cross compilation build though. Is there a standard way to do that?

It looks like support for this used to exist, but was removed in https://github.com/nix-rust/nix/commit/9e935330dd252d4ec640197a6040df2aaeb583c9. Am I repeating the mistakes of the past?

Anything else I should do on my end to make this good to go?

@homu r+
It's perfect now. Thank you.

:pushpin: Commit 1d262d0 has been approved by fiveop

:hourglass: Testing commit 1d262d0 with merge 6ea8f7f...

:sunny: Test successful - status

@oconnor663 I just came across the fact that the released version doesn't do this. I'll see if we can release this week to get it out there. And tthanks for making this change!

@kamalmarhubi BSD support has also landed in libc master, though it hasn't been released there yet. We can expand this as soon as they release.

@oconnor663 oh cool! They are usually happy to release when asked. I'm trying to figure out if there are more things we want before asking. Otherwise we ought to be able to expand it quite soon indeed! :-)


WIP: add GPU tests

Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Do you need this reviewed boss? - @mudler

still playing with it, not really ready for review/merge


Coming Soon: Test new @immutable annotation

meta package now has @immutable. See https://github.com/dart-lang/sdk/issues/27750
Analyzer supports @immutable on HEAD, which ensures all fields are final.

See https://codereview.chromium.org/2775863004/
(landed, but not rolled...)

Blocked by https://github.com/flutter/flutter/issues/9042

Apparently we need a dev.11 build.  I've started experimenting in https://github.com/flutter/flutter/pull/9152

Sorry for the confusion on the dev version. :/
Here's the new blocking roll issue: https://github.com/flutter/flutter/pull/9151


Wrong path opened when using drive letter with relative path

Issue Type: Bug
at command prompt:
C:>md d:\Subfolder\Foo\bar
C:>echo TEst>d:\Subfolder\Foo\bar\File.txt
C:>cd d:\Subfolder
C:>code d:Foo\bar\File.txt
Expected: opens the file with "TEst" in it.
Actual: opens a new file at D:\foo\bar\File.txt
(errant \ is added between drive and folder, path generation should attach relative path onto "current folder" of the target drive.).  replace "CODE" with "DIR" and you will see the proper path used.
VS Code version: Code 1.24.1 (24f62626b222e9a8313213fb64b10d741a326288, 2018-06-13T17:51:32.889Z)
OS version: Windows_NT x64 10.0.17707

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (12 x 3492)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.93GB (5.89GB free)

Process Argv
c:\Program Files\Microsoft VS Code\Code.exe GitBuildSpec.WPTEdgeHTMLMinCheckin.txt

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

rainbow-csv
mec
0.4.2

csharp
ms-
1.15.2

PowerShell
ms-
1.7.0

Expected: opens the file with "TEst" in it.

Why do you expect this when you add d: to the path in this step? C:>code d:Foo\bar\File.txt

I expect the full path to the file will be d:\TestFolder\foo\Bar\File.txt.   Each drive a "current working directory" so when you "dir d:" you are asking to view whatever the current directory on D: is, not the root.   In my case, I was working in D:\TestFolder, switched to C:, and then wanted to refer to the files on D: relative to where I was working before.  "Dir D:" would have showed the contents of D:\TestFolder, and I expect a path that does not include a leading \ (after the drive specifier) will also start relative to D:\TestFolder.

You need to do C:>code d:\Subfolder\Foo\bar\File.txt, we don't (and can't AFAIK) track working directories  across drives.

After parsing a name from the command line, you pass the name to this function and the relative paths will be resolved.
https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-getfullpathnamea
From: Daniel Imms<EMAIL_ADDRESS>Sent: Monday, July 02, 2018 10:01 AM
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: Tiltowaite<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] Wrong path opened when using drive letter with relative path (#53312)
You need to do C:>code d:\Subfolder\Foo\bar\File.txt, we don't (and can't AFAIK) track working directories across drives.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode%2Fissues%2F53312%23issuecomment-401869107&data=02|01||7d4f918e31cf4598a79608d5e03d54ab|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636661476364247796&sdata=UiYLvp6ZeXN4t5LyDFwn4ktV58ImRZnLQMQQ6kuFMDA%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAmzd_rDw_uL3em5cXF6tFLrUUDV5uGM3ks5uClGygaJpZM4U8tDT&data=02|01||7d4f918e31cf4598a79608d5e03d54ab|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636661476364247796&sdata=NMSY0atM%2FIqlsdOqmXn%2BSydl%2Fqu7LY1IVIG1rRKU24U%3D&reserved=0.

That's cmd's job, we just show what cmd tells us to. Your request belongs in https://github.com/Microsoft/console


[5756 Identity Management Overhaul] Rewrite sentry to authenticate clients before signing

Part of https://github.com/dapr/dapr/issues/5756
This is the first in a chain or PRs to complete this issue. The following PRs will implement the security changes for each of the other components.
This rewrites the sentry service to now authenticate clients before signing for their identity in a backwards compatible way.
It introduces a new pkg/security package. This package is designed to manage the components SPIFFE ID (fetched from sentry), and expose connection options for authentication and authorizing servers.
The sentry flag --token-audience has now been deprecated. The audience of the kubernetes token used by clients should always be the SPIFFE ID of sentry (not implemented in this PR). For backwards compatibility, sentry will still accept dapr.io/sentry which should be remove in v1.12.
Sentry will ensure clients request their app ID. Sentry will still accept clients sending a CSR request with the ID set to $namespace:$sa, however this exception should be removed in 1.12.
Sentry will still send the trust anchors in the sign response, but should be removed in 1.12 as trust distribution should happen out of band of signing.
Sentry will continue to include cluster.local as a DNS SAN on its serving cert, since pre v1.11 client authorize on this. This should be removed in v1.12
Sentry will also continue to include cluster.local as DNS SAN on the issuer certificate since this is used by the control plane components as serving certificates. Also to be removed in v1.12.
global.mtls.controlPlaneTrustDomain is a new top level helm chart to set the control plane trust domain. Currently only read by sentry.
The root CA is now created by sentry (no longer helm) and written to the dapr-trust-bundle secret. It also write the trust anchors to the config map dapr-trust-bundle. The control plane components will read the trust anchors from this ConfigMap as a volume mount.

Thanks for the review @ItalyPaleAle!

This is my first round of review, although there are still a few files missing.

One question is on why we are still using both a root CA cert and and intermediate CA cert. Can't we remove one from the chain, and just use the root CA?

Could do in future, but since this is what we are doing already today we should keep doing that until we are in a future version, past needing to rely on any old PKI. Remember that all components are currently consuming the issuing certificate and private key and using that for serving and clients. Changing up the chain structure will add to the backwards/forwards compat complexity. Ideally, we should not care what PKI setup Dapr is using so long as it follows correct PKI.

Also, since this is a major rewrite and reviewing this PR is not super easy (because the diff isn't much helpful), would you be available for a review during a call?

Yes, definitely makes sense to do this! :slightly_smiling_face:

@JoshVanL what will be the effect of these sentry changes wrt the CLI renew certificate command?

One question is on why we are still using both a root CA cert and and intermediate CA cert. Can't we remove one from the chain, and just use the root CA?

Could do in future, but since this is what we are doing already today we should keep doing that until we are in a future version, past needing to rely on any old PKI. Remember that all components are currently consuming the issuing certificate and private key and using that for serving and clients. Changing up the chain structure will add to the backwards/forwards compat complexity. Ideally, we should not care what PKI setup Dapr is using so long as it follows correct PKI.

The problem with the current approach is that because we throw away the root key, we can not renew the root CA certs. 10 years is a long time (and is probably too long), and yet that's how we got the Y2K and Y2K38 problems :)
Since we're making so drastic changes to Sentry, I think this would be the perfect time to remove this choice, which IMHO doesn't even make much sense (I get protecting the root CA key, but if the intermediate CA can sign certificates, this makes no difference at the end of the day).

@ItalyPaleAle Completely agree- lets do this in a followup PR.
I would like to see a better option set for sentry so the user can tune these things (with more sane defaults). This is also where we can introduce external CAs.

As there are already major overhaul changes going on, should we also rename Issuer CA to Intermediate CA? Intermediate CA is quickly understandable, whereas all this while I too have been thinking that what is this Issuer CA.

Sure thing, more  than happy to make this change!

@JoshVanL Good news :)

The E2E tests here confirm that we can run dapr 1.10 and 1.11 sidecars against "vNext" (with this PR)

Required a bit of a "hack" because current Dapr versions request a TLS certificate from Sentry by sending a CSR that has type "CERTIFICATE" in the PEM block, instead of "CERTIFICATE REQUEST". See: https://github.com/dapr/dapr/pull/6171/commits/4fcdf9317399ab883f348d6a47cc80172565a03f

Although we cannot write an E2E test for that, I manually verified that we can deploy a Dapr 1.11 control plane and use "vNext" sidecars. The sidecars do get a TLS certificate correctly from v1.11 Sentry, and things like service invocation works.

Although this scenario is not officially supported, it's something we still make an effort to allow, especially because there can be a version mismatch during upgrades.

/test

/ok-to-test

/test-sdk-all

/ok-to-test
/test-version-skew

/ok-to-test
/test-version-skew

/ok-to-test

/test-version-skew

/ok-to-test

/test-version-skew

One question is on why we are still using both a root CA cert and and intermediate CA cert. Can't we remove one from the chain, and just use the root CA?

Could do in future, but since this is what we are doing already today we should keep doing that until we are in a future version, past needing to rely on any old PKI. Remember that all components are currently consuming the issuing certificate and private key and using that for serving and clients. Changing up the chain structure will add to the backwards/forwards compat complexity. Ideally, we should not care what PKI setup Dapr is using so long as it follows correct PKI.

The problem with the current approach is that because we throw away the root key, we can not renew the root CA certs. 10 years is a long time (and is probably too long), and yet that's how we got the Y2K and Y2K38 problems :)
Since we're making so drastic changes to Sentry, I think this would be the perfect time to remove this choice, which IMHO doesn't even make much sense (I get protecting the root CA key, but if the intermediate CA can sign certificates, this makes no difference at the end of the day).

Dapr root and issuer certs are valid for 1 year, not 10.

/ok-to-test
/test-version-skew
/test-sdk-all

/test-sdk-all

/test-sdk-all

This PR is breaking service invocation and tracing ITs in Java SDK.

@artursouza those Java failing tests look unrelated to this PR. Here is a similar failure which was executed from the SDK test schedule https://github.com/dapr/dapr/actions/runs/5686772228

@JoshVanL This will be a release blocker.


Feat/product list--Products added to homepage from DB

Please can we include the db
should we use a "media" folder for static website images?
should the "media" folder be one level higher than other folders such as static and templates? it seems like it is outside the app's folder structure at the moment

Please can we include the db
should we use a "media" folder for static website images?
should the "media" folder be one level higher than other folders such as static and templates? it seems like it is outside the app's folder structure at the moment

done
we need to store cake images with their respective id and cake desrc, which is only possible through database hence the /media folder necessity
It's in the global scope, i am not sure if it needs to be brought under App specific folder


Using laravel 5.4 - cannot read property extend

hi, im using this package in my previous project but under laravel 5.4 im returning error. please kindly check

I just ran into the same problem. This has to do with Laravel Mix that comes with Laravel 5.4 now. The only way I've found out to use toastr with Laravel 5.4 is using npm. I've written a short post on how to do it step-by-step here: https://ashokgelal.com/2017/02/03/laravel-mix-with-toastr/

toastr use the JQuery lib. So, toastr.js / toastr.min.js needs JQuery loaded to work.
Easy FIX: Load jQuery before toastr.
Whoa...Problem solved

@arifpavel  @ashokgelal  I have the some problem in laravel 5.4,, and i load jQuery before toastr but still not work even i dont see any problem in console.. and i see the message on page source after submission:
My includes files:

My source after create an category

Thanks in advance for any help

Hello folks,
i ran into same problem today morning, after investing a few hours got the solution -
"LOAD JQUERY BEFORE TOASTR" 👍
Thanks.


Updated spec.schedulername to spec.schedulerName.

xref https://github.com/kubernetes/kubernetes/pull/41859

This change is

@k82cn Is this related to a particular release?

@chenopis , target is 1.6 ; but please wait for kubernetes/kubernetes#41770 merged, I'll ping you when it's ready :).

@k82cn No problem. I just wanted to make sure I tag this correctly. Also, would you mind rebasing and switching the base to release-1.6? Thx

@chenopis , sure, I'll rebase it to 1.6 branch :).

@k82cn thx!

@k82cn BTW, I moved this to the release-1.6 branch for you. =)

@chenopis , thanks very much :).

@chenopis , can you help to merge this PR?  kubernetes/kubernetes#41770  was merged last night :).

@k82cn Done! Thanks =)


Fix path

Fixed path to run the application correctly.

@nisunisu Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@pivotal-cla This is an Obvious Fix.

@nisunisu This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.


ViewState object has incorrect types for some submission payloads

Hello again! I found an issue with some of the types for view submission payloads.
The object in question is ElementValue which is used in ViewState.
Potential issues found

Missing selected_date property
Missing selected_time property
selected_conversations property is string but should be an array of strings
selected_channels property is string but should be an array of strings
selected_users property is string but should be an array of strings

For reference, here is the same type from Slack Bolt TS to compare against.

https://github.com/slackapi/bolt-js/blob/main/src/types/view/index.ts#L159
https://github.com/slackapi/bolt-js/blob/23cc0e16494c22783222821ebff789cfdaabeebd/src/types/view/index.ts#L132

These updates have been made in 3.13.0 and 3.14.0-beta1 👍


Adding errors to Kubelet events.

This will help while debugging issues that generate events.
Also removed unecessary log line.

LGTM.


_sync_author_metadata whenever

invoking _sync_author_metadata on pipeline or author validation is a good idea! It's also exactly the sort of thing we can't do if we're mutating the list in place (without assignment).

My proposed solution is to sync the metadata in any function which uses the author or contributor metadata. What are your thoughts on this?

I think that that would be one way to keep our author/contributor metadata consistent, but that seems a bit "brittle" to me -- e.g. suppose someone else opens a PR which implements "institutional affiliations" for the author/contributor metadata, they'd be writing methods which manipulate author or contributor metadata but (because it's someone else writing these) they don't remember to call _sync_author_metadata every time; IMO the best place to enforce this sync is whenever the pipelines attribute is assigned to (so you can't add a pipeline without triggering a sync).
We're using the pydantic library under the hood, which gives us an easy way to do this -- these are the relevant docs https://docs.pydantic.dev/usage/validators/ -- and there are a few examples on the Garden/Pipeline/Step classes using the syntax already (just nothing for the pipelines attribute, yet)

Also as a side note, the cli-module-scaffolding branch is the next one we're going to merge into main and it refactors things a bit -- if you get started before main is caught up, it might avoid a git-rebase-headache to start your new branch from that one rather than from main (not the end of the world either way though).

Would you recommend using root validators or just regular validators?
Also, it looks like validators don't run if an element is added to a list:

yep! that's exactly right, there are a few things we wanted to do with pydantic that aren't the default (and in my experience kind of hard to find in the docs), but I think that's the big one. For context, we wanted the ability to have "partial" Gardens -- e.g. doi is required eventually, but not known at creation time since we mint those using other required info, like authors/title.
all three of the Steps/Pipeline/Garden classes should already be configured to validate on assignment, iirc

It looks like there is another pr that's up for merging. Should I wait or start working on that?

that one should be merged soon (hopefully today); probably easiest for you to start your new branch from the 46-garden-create-command branch rather than main if you started in the meantime

I don't see the 46-garden-create-command branch though...

Sounds good. I'm just tacking on a @validator("pipelines") right before the _sync_author_metadata definition in the Garden class, and @validator("steps") for the Pipelines class. that should work, I believe.

Handled in the Garden class overhaul.


Add 'postal_code' validation rule

Introduced a new validation rule to check the correctness of postal codes based on country codes. This update also includes the addition of PostalCode.php for functionality and PostalCodeTest.php for testing. Schema examples and README file have been updated to reflect this change.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

17 of 18 (94.44%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 96.779%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Rules/Cell/PostalCode.php
17
18
94.44%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
2854

Relevant Lines:
2949

💛  - Coveralls


Comment's tone should be changed from suggestive to warning

https://github.com/OpenZeppelin/zeppelin-solidity/blob/master/contracts/crowdsale/Crowdsale.sol#L88
This comment should warn user that in default implementation forwardFund function can cause situation when owner can cheat the system by recycling ether trough the contract.

Ref
I've suggested in a thread on /r/ethdev this be reported here.
In particular, I wrote this, citing a slightly more verbose exploit description.
Summary
If Crowdsale is used unmodified, and the benefactor address wallet does not forbid withdrawal at least until the end of the crowdsale, then the operator(s) of wallet can "bounce" the funds back to the crowdsale, artificially increasing their share of tokens for no ether cost (other than gas). This is exacerbated if the token sale is uncapped.
The above is an underhanded way for (imaginary) uncanny crowdsale operators to gain a larger share of tokens than they would be claiming, for example, in marketing materials. Detecting it requires (manual) vigilance by other parties, while the sale is on-going, which can not be guaranteed.
Improvements
Code-wise, there is no way around it ("works as expected"). It can be made less severe by making the function's comment less suggestive, and more of a warning, in hopes that contract reviewers might spot it before the sale.
A separate "trickle funding" contract could also be provided, to act as the benefactor instead of a multi-sig wallet.

In other words, contract use guidelines should suggest that either:

the function must be overridden to check that there's no "funding loop"; or
the benefactor contract must not allow withdrawal of ether until the end of the crowdsale.

There could possibly also be a guide for auditors or crowdsale participants, that would urge to check for the above; but I'm not sure if such a measure can be efficient.

"The benefactor contract must not allow withdrawal of ether until the end of the crowdsale" - this only concerns cases where there is a minimum funding goal. If the crowdsale has been success I do not see a problem with an early withdrawing the funds.
This is especially beneficial to the token sale organizers and token holders to to convert some ETH immediately and diverse assets under the downward market conditions, so that they can get the maximum value for the project they support.

Thanks for the comments @veox and @vadimkerr! I agree with all of it.
Have you seen the RefundVault contract that RefundableCrowdsale uses? We could add a similar contract as a middle step for funds in general.

Ah!.. Yes, Vault sounds like the right kind of allegory.

Somewhat OT:
RefundVault would need a way to receive deposit()s from Crowdsale, meaning either the Vault being owned by Crowdsale (bad idea IMO), or removing the onlyOwner modifier in favour of an onlyAllowedSenders.
With the above change, time locks (e.g. with reenrant view calls to check if Crowdsale has ended), drip-funding instead of everything-at-once, or any other fancy schemes can be implemented by inheriting the RefundVault, and overriding appropriate functions.

But "drip-funding" for example would be unrelated to refunds, so I don't see it being implemented as a subclass of RefundVault.

Yup! That was a random OT rant. ;)

Additional discussion on this topic: https://blog.zeppelin.solutions/handling-crowdsale-funds-securely-c348467da74c

Indeed, a RefundCrowdsale doesn't have this issue due to using a RefundEscrow. We're discussing extending the Escrow model in https://github.com/OpenZeppelin/openzeppelin-solidity/issues/1099.

https://github.com/OpenZeppelin/openzeppelin-solidity/issues/529 presented a related requirement.

After giving this some more thought, I now believe this is out of scope of the baseline Crowdsale contract (on which there's no concept of the crowdsale 'ending' due to a goal being reached, the funding window being closed, etc.). Such a feature can be implemented by passing an Escrow as the crowdsale wallet, but we cannot force this without fundamentally changing how the current model works.
Given that the tools exist to properly and safely develop this, I'm closing the issue and marking as won't fix. A dishonest fund raise will not be impeded by OpenZeppelin holding honest code.


Looks like it's not working if width isn't specified

When I copied the markup + Prerequisted CSS styles from the demo page, slider didn't work. It seems to be because in the demo you actually specify a fixed width for the li element.
.simple li {
	width: 270px;
	margin-right: 10px;
}
@media screen and (min-width: 640px ) {
	.simple li {
		width: 580px;
	}
}
@media screen and (min-width: 980px ) {
	.simple li {
		width: 880px;
	}
}

So my question is... is there a way to make it work out of the box, without specifying a width? I feel like it's a bit annoying to specify a fixed width in a responsive context.

Hey @SiamKreative,
this feature is currently not supported, because I didn`t want to handle styling in my JavaScript.
But if you want to set a own width of the slides dependent on the browser width you can always listen to the resize event and call lory.reset() afterwards which would re-initialize lory with the current widths of the slide elements.
Maybe this is a little Add-on. I really try to keep lory as lightweight as possible! The way to go would be  to use the callbacks in the options and the public-api. If you need something that you can actually implement this, just tell me.
cheers Max

I'm not sure you understood me correctly. I meant that Lory didn't work with PREREQUISITED HTML & PREREQUISTED CSS STYLES:

I had to manually specify a width in pixels for the <li> elements. This is what you're doing in your stylesheet [app.css)(http://meandmax.github.io/lory/demo/app.css) line 199. If the width is required for the script to work, then perhaps it would be a good idea to mention it in the documentation :)

Yes I understood you. I didnt add a width to the demo css because its always different. But you are right that I need to mention that you have to specify a width for the "li" element.
Thanks for the advice!
cheers Max


Openebs control-plane upgrade test case implementation

https://github.com/mayadata-io/oep-e2e/pull/801


Adding twitter tags

Would there be any interest in adding twitter card tags (detailed here)? I'd be willing to work on this if there's any interest and submit a pull request.

hi @platelminto that could be a great addition. Do you have some examples of the pages with this markup, and example outputs? Do you have an estimate of how popular is this markup?

Example pages:
https://shop-eu.kurzgesagt.org/
with markup:
<meta name="twitter:site" content="@kurz_gesagt">

  <meta name="twitter:card" content="summary">

  <meta name="twitter:title" content="kurzgesagt shop">
  <meta name="twitter:description" content="The official kurzgesagt online shop. Merch created with love. Posters, notebooks, clothes, plushies and more from the kurzgesagt universe.">

    <meta name="twitter:image" content="https://cdn.shopify.com/s/files/1/0252/6822/4088/t/64/assets/logo_twitter.png?v=14636856715189202634" />

https://store.taylorswift.com/products/i-would-die-for-you-in-secret-hoodie
with markup:
<meta name="twitter:card" content="summary"><meta name="twitter:title" content="“i would die for you in secret” hoodie">
  <meta name="twitter:description" content="FOLKLORE ALBUM COLLECTION

*please note we are doing our best to deliver your order as fast as possible, however, we may experience delays somewhere along the way as we try to keep everyone safe.Black hooded sweatshirt featuring "folklore album" printed in copper glitter on front and photo of Taylor Swift printed on back along with "All these people think love's for show, but I would die for you in secret" lyrics in copper glitter.
100% cottondepiction of this product is a digital rendering and for illustrative purposes only. actual product detailing may vary.Taylor Swift®©2021 TAS Rights Management, LLCUsed By Permission. All Rights Reserved.
">
  <meta name="twitter:image" content="https://cdn.shopify.com/s/files/1/0011/4651/9637/products/dieforyouhoodiefront_600x600_crop_center.png?v=1627046674">

https://github.com/
with markup:
    <meta property="twitter:site" content="github">
    <meta property="twitter:site:id" content="13334762">
    <meta property="twitter:creator" content="github">
    <meta property="twitter:creator:id" content="13334762">
    <meta property="twitter:card" content="summary_large_image">
    <meta property="twitter:title" content="GitHub">
    <meta property="twitter:description" content="GitHub is where people build software. More than 65 million people use GitHub to discover, fork, and contribute to over 200 million projects.">
    <meta property="twitter:image:src" content="https://github.githubassets.com/images/modules/open_graph/github-logo.png">
    <meta property="twitter:image:width" content="1200">
    <meta property="twitter:image:height" content="1200">

https://www.billboard.com/
with markup:
<meta data-rh="true" name="twitter:site" content="@billboard" />
<meta data-rh="true" property="og:site_name" content="Billboard" />
<meta data-rh="true" property="og:url" content="https://www.billboard.com/" />
<meta data-rh="true" name="og:image" property="og:image" content="https://static.billboard.com/files/2019/07/billboard-logo-b-20-billboard-1548-1092x722-1598619661-compressed.jpg" />
<meta data-rh="true" name="og:image:width" property="og:image:width" content="1092" />
<meta data-rh="true" name="og:image:height" property="og:image:height" content="722" />
<meta data-rh="true" name="og:title" property="og:title" content="Billboard - Music Charts, News, Photos & Video" />
<meta data-rh="true" name="twitter:title" property="twitter:title" content="Billboard - Music Charts, News, Photos & Video" />

These include a couple I just found now randomly, it looks extremely popular (to the extent of opengraph and json+ld).

Thanks for examples, looks quite popular indeed, +1 that it's useful.
Also it seems that this is already somewhat supported, for example this works
>>> extruct.extract('<!doctype html><html><head><meta property="twitter:card" content="summary">')
{'microdata': [],
 'json-ld': [],
 'opengraph': [],
 'microformat': [],
 'rdfa': [{'@id': '',
   'https://dev.twitter.com/cards#card': [{'@value': 'summary'}]}]}

But not this
>>> extruct.extract('<!doctype html><html><head><meta name="twitter:card" content="summary">')
{'microdata': [],
 'json-ld': [],
 'opengraph': [],
 'microformat': [],
 'rdfa': []}

👍  @platelminto anything I can do to help this along? Otherwise, I'll be building my own extraction for twitter cards. Unless anyone knows of another package that handles twitter cards already?

I have added the twitter card functionality in the #196 pull request. Please let me know if this works.


"Command 'crunchy' not found," (HELP)

I didn't use terminal tools before... idk but i'm getting this issue when I try to run this command:
$ crunchy --etp-rt "abcd1234-zyxw-9876-98zy-a1b2c3d4e5f6"
error: Command 'crunchy' not found, did you mean:
command 'crunch' from deb crunch
Try: sudo apt install
please help me :(

Hello! How did you get the cli and which version are you trying to use?
https://github.com/crunchy-labs/crunchy-cli/releases/tag/v3.0.0-dev.8 Should be the latest dev release that works.
Since you seem to be on a linux distribution you can run the following:
wget https://github.com/crunchy-labs/crunchy-cli/releases/download/v3.0.0-dev.8/crunchy-v3.0.0-dev.8_linux
chmod +x ./crunchy-v3.0.0-dev.8_linux
mkdir ~/crunchy-cli
mv ./crunchy-v3.0.0-dev.8_linux ~/crunchy-cli/crunchy
export PATH=$PATH:~/crunchy-cli/crunchy

and I'd recommend adding the export PATH=$PATH:~/crunchy-cli/crunchy to your .rc file.
The command should work as intended afterwards.

Hello! How did you get the cli and which version are you trying to use? https://github.com/crunchy-labs/crunchy-cli/releases/tag/v3.0.0-dev.8 Should be the latest dev release that works. Since you seem to be on a linux distribution you can run the following:
wget https://github.com/crunchy-labs/crunchy-cli/releases/download/v3.0.0-dev.8/crunchy-v3.0.0-dev.8_linux
chmod +x ./crunchy-v3.0.0-dev.8_linux
mkdir ~/crunchy-cli
mv ./crunchy-v3.0.0-dev.8_linux ~/crunchy-cli/crunchy
export PATH=$PATH:~/crunchy-cli

and I'd recommend adding the export PATH=$PATH:~/crunchy-cli to your .rc file.
The command should work as intended afterwards.

thanks now it work!
but when I try to download https://www.crunchyroll.com/series/GEXH3WKK0/vinland-saga it gives me this errors:
:: → Season 1 of series VINLAND SAGA is not available with en-US audio
:: → Episode 1 (Slave) of season 2 (VINLAND SAGA Season 2 (English Dub)) of VINLAND SAGA has no espanol subtitles
command used: $crunchy download -s espanol https://www.crunchyroll.com/series/GEXH3WKK0/vinland-saga[1]
so please how to make default audio to Japanese and how to put subtitle (what is countries encoding?)


feat: hide insufficient amount when no amount entered

Description
Hide the "Insufficient sell amount" label when no amount has been entered yet.
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
Small.
Testing
When no amount has been entered in the trade widget we should not show the "Insufficient sell amount" label.
Engineering
☝
Operations
☝
Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #4447   👈

This comment was auto-generated by Graphite.


The main thread behavior when given threadpool in computation

Hi, I'm doing benchmark on the multi threading performance on some CNN models.
As I'm not familiar with the pthread functions, I want to know the behavior of the main thread in computation. Specifically, I want to know if the main thread participates the computation as the threads in threadpool.
Thanks

Thank you very much!


Cleaning up our build process for windows a little

Mostly experimental for now.

This is probably worth looking through: we need to resolve the runtime library problem Monday.

Does it still qualify as a "DO NOT MERGE" btw ?

nah, good to go.
On Mon, Aug 31, 2015 at 4:24 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

Does it still qualify as a "DO NOT MERGE" btw ?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/3119#issuecomment-136526419.

Is there a reason why the compiler plugins projects aren't part of vcxproj.template ?

Scope control more than anything: this already got out of hand.
Totally makes sense to do in the future.
On Mon, Aug 31, 2015, 5:27 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

Is there a reason why the compiler plugins projects aren't part of
vcxproj.template ?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/3119#issuecomment-136536437.

Aaaand seems that I was too slow to try and merge it. Sorry.

Merged with head. Kicked off Jenkins.


Add workaround for OperatorHub.io for newer MicroShift version

Add workaround for OperatorHub.io for newer MicroShift version
With the new OLM version that is neede to run on the newer MicroShift
version, the OperatorHub.io stops working properly, for example with
the cert-manager operator [1]. That operator raises an errors in the
events:
    kubectl get events --sort-by='.lastTimestamp' -n olm
    (...)
    olm 3s  Warning   FailedCreate job/2e57cffb7b8c51388293af892eb8ab66ca8241b81b0bd19b31b3aa5f0bccaf3
    Error creating: pods "2e57cffb7b8c51388293af892eb8ab66ca8241b81b0bd19b31b3aa5f0bccaf3-" is forbidden:
    unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable
    by user or serviceaccount, provider restricted-v2: .initContainers[0].runAsUser: Invalid value: 1001:
    must be in the ranges: [1000370000,<PHONE_NUMBER>], provider restricted-v2: .initContainers[1].runAsUser:
    Invalid value: 1001: must be in the ranges: [1000370000,<PHONE_NUMBER>], provider restricted-v2:
    .containers[0].runAsUser: Invalid value: 1001: must be in the ranges: [1000370000,<PHONE_NUMBER>],
    provider "restricted": Forbidden: not usable by user or serviceaccount, provider "custom-scc": Forbidden:
    not usable by user or serviceaccount, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount,
    provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden:
    not usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden: not usable by user or
    serviceaccount, provider "hostnetwork": Forbidden: not usable by user or serviceaccount, provider "hostaccess":
    Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]

That commit adds a workaround for scc policies to
be possible to install the cert manager from the OperatorHub.io
[1] https://operatorhub.io/operator/cert-manager

Temporary hold on with merging that commit.
It seems that it still fails on installation of cert-manager: https://github.com/softwarefactory-project/sf-operator/blob/master/cli/cmd/dev/microshift/static/post-install.yaml#L27
Something is not ported to official release e.g. 0.27.0, because when I do:
# optionally
curl -LO https://github.com/operator-framework/operator-sdk/releases/download/v1.34.2/operator-sdk_linux_amd64
chmod +x operator-sdk_linux_amd64
operator-sdk_linux_amd64 olm uninstall

# then - https://operatorhub.io/how-to-install-an-operator

kubectl create -f https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/crds.yaml
kubectl create -f https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml

kubectl create clusterrolebinding cluster-admin-binding --clusterrole cluster-admin --user microshift

And after that:
kubectl apply -f https://raw.githubusercontent.com/softwarefactory-project/sf-operator/master/olm-deps/cert-manager.yaml

it works.

By comparing files: crds.yaml from version 0.24.0 (last working) and 0.26.0 (minimal version), files are more less same, but by comparing olm.yaml, there is an odd situation, because, in the 0.24.0:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: system:controller:operator-lifecycle-manager
rules:
- apiGroups: ["*"]
  resources: ["*"]
  verbs: ["*"]
- nonResourceURLs: ["*"]
  verbs: ["*"]

where in 0.26.0:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: system:controller:operator-lifecycle-manager
rules:
- apiGroups: ["*"]
  resources: ["*"]
  verbs: ["watch", "list", "get", "create", "update", "patch", "delete", "deletecollection", "escalate", "bind"]
- nonResourceURLs: ["*"]
  verbs: ["*"]

TBD

See this PR https://github.com/openstack-k8s-operators/ansible-microshift-role/pull/65 I was able to get olm default version 0.28.0 working and then install cert-manager and get it working out of the box. You can integrate those changes into that PR.

@morucci thanks for checking.
So instead of changing one entry in the policy, you would like to add all components privileged scc? TBH - I don't like it.
I even drop the oc adm policy add-scc-to-user privileged system:serviceaccount:olm:default, due it is not needed to install operators from the OperatorHub.io.
If we need such privileges in our project, maybe we should do that there, and here we can just leave the parameterized workaround as I proposed in the PR just to make the OLM been working here?

Probably the change https://github.com/openstack-k8s-operators/ansible-microshift-role/pull/65 would be merged.
I don't like the solution to add privileged permissions to some namespaces or serviceAccounts, but it might be easier to revert change when the OLM will support PodSecurityAdmission.


State: Starting

Hello,
since a few days the state of my MIELE washing machine is set to „starting“.
But it is turned off…
many ideas or workarounds?

Since today same problem with my dryer. The characteristic is set to 1.
what can I do?

Can you post the Homebridge logging of the Miele@Home plugin?

Hi! Problem solved!
I‘ve lost the connection with the Miele App.
After a reconnect everything worked fine

Thanks. Somehow awkward the Miele app influences the results obtained by the Homebridge plugin though.


Unify the low-power peripheral names and rename the RtcCntl driver

At present, depending on which chip you're targeting, this driver is initialized in one of two ways:
// esp32c6 & esp32h2:
let rtc_cntl = RtcCntl::new(peripherals.LP_CLKRST);

// Everything else:
let rtc_cntl = RtcCntl::new(peripherals.RTC_CNTL);

There are two major issues with our current implementation:

The peripheral singleton structs should have their names unified; it's confusing passing two different peripherals to the same constructor, depending on which chip you're using. It's also confusing that for the C6 and H2 the peripheral name is seemingly unrelated to the driver's name.
RtcCntl is just not a good name. This was chosen initially as it was used in the TRMs, however with the new naming schemes this is less relevant now. This name is also, IMO, incredibly misleading, as may people associate it with Real-Time Clocks instead.

So the question remains, what should we call these things?

For me, anything goes as long as it's not RTC. Let me throw LP_CNTL in the pool of possibilities :)

I double that - anything not containing RTC is fine to me

Is LP_CLKRST or even just CLKRST maybe not a bad name to use? It's at least consistent with some chips this way. Just a thought.

I think LP_CNTL is broad enough so that it covers the power domain stuff, too, that I think belongs to RTC in the S3. CLKRST is somewhat more ... concrete and may not be precise enough because of that.

Throwing my suggestion into the ring:
LPWR and LowPowerDomain


Fix host port removal

When a pod is being terminated, the event is sent out while the pod is
in the 'Running' phase in the registry (unless it has never started up
correctly). Change event handling in server.go to be able to correctly
remove host ports from the PodSpec.

This looks correct.  The logic around pod termination is unfortunately twisty and poorly named.  I think that could eventually be improved with a bit of tracing through everything.
:+1:


feat: narrow down ResilienceEvents interface

Please describe the changes this PR makes and why it should be merged:
Hi,
Thanks for the amazing library.
If I understand correctly, the ResilienceEvents interface needs to be changed to allow for tighter type checking.
Status and versioning classification:
2.1.3(latest)

LGTM, @thilllon TYSM


Card Visual Block

Card Block
Define a new block in convoworks with name Card Block which will make it easier to work with cards on Amazon Alexa, Google Assistant, Facebook Messenger and Viber.
Block Properties itself:

item -> preferable this is the selected object of an list item ow which we want to perform certain actions like order, even more details, call and so on (just a object no more no lesss)
item name -> under which name to store data item name
back button visible -> choose between hidden or visible back button. (works only on Alexa)
data item title -> Title of the item which will be displayed on the card
data item subtitle -> subtitle of the item which will be displayed on the card
data item description -> primary description of the item which will be displayed on the card
data item image url -> link to the image of an item in the card (preferable an https link should be used)
data item image text -> accessibility text of the image of an item in the card (Required if you want to display the image.)

Block Containers:

Read Phase -> display the card itself (this is added automatically) and support is added for other convoworks responses such as text response, set parameter, if and so on. Also if the text is added the default text response will be overridden.
On No Screen Supported -> will be executed instead if the device has no support for a screen
Card Actions -> will be executed when an action of the issued card was selected (more on those card actions later)
Additional Processors -> will be executed of another things of other processors are matched

Card Actions:

this should be a specialized processor
its filter checks for a card specific card event or utterance or anything of this nature
this should be defined in an separate interface and checked as the specified interface to avoid confusion between CardActionProcessors and Other Convoworks Processors.

Additional specifications:

Define new request interfaces IConvoCardRequest which will make it easier to get values from those requests from each platform and implement them in each PlatformRequest
Define new response interfaces IConvoCardResponse which will make it easier to define the final response for each platform and implement them in each PlatformResponse

Please also refer to the Dummy representation of the Card Block.

Couple things I would like to point out

This seems quite much related to the #9  lets see if they have similarities (talking about interfaces primary)
IConvoRequest and IConvoResponse extensions should be treated as separate task/issue (and covered with unit tests?)
The second task is actually a workflow component design and here is the major question should it be implemented as Block or should it be implemented as separate Element and separate Processor/Filter components

Here is an quick overview of the interface infrastructure for the Card Visual Element.
IConvoCardRequest makes it easier to detect any selected card action after a card response was sent.
interface IConvoCardRequest extends IConvoRequest
{
    /**
     * @return string
     */
    public function getSelectedCardAction() : string;
}

IConvoCardResponse makes it easier to declare an card response.
interface IConvoCardResponse extends IConvoResponse
{
    public function getCardResponse(IVisualCard $cardItem) : array;
}

IVisualCard is used in IConvoCardResponse->getCardResponse(IVisualCard $cardItem)  card response. This definition makes it clearer how the CardResponse should be formed.
interface IVisualCard {
    public function getCardVisualItem() : IVisualItem;
    public function getCardActions() : array;
}

IVisualItem is part of CardResponse.
interface IVisualItem
{
    public function getTitle() : string;
    public function getSubtitle() : string;
    public function getDescription() : string;
    public function getImageURL() : string;
    public function getImageText() : string;
}


Update _index.md

Some updated links
Description
Another user found some missing, broken and wrong links in this documentation. Found some of the correct links (i think.. please double check). Might add more later when i've found them.
Other missing links include:

https://docs.altinn.studio/api/guides/appownerintegration/receivingdata/#overordnet-prosess-sluttbruker - Wrong link on number 5
https://docs.altinn.studio/api/guides/appownerintegration/receivingdata/#instansiering-av-tjeneste - Missing link on how TE can instantiate an app possible links: (https://docs.altinn.studio/nb/api/apps/instances/#create-instance) || (https://docs.altinn.studio/nb/app/development/logic/instantiation/#eksempel-2---instansiering-kun-tillatt-for-applikasjonseier)

@aadnehm Better to put the remaining bugs into a new issue, and merge this PR?


Declaration of BuildsFluentQueries must be compatible with ExecutesQueries

library version 2.2.0 (Beta 1), php 7.3.1, laravel 5.7.29

PHP Fatal error:  Declaration of Matchory\Elasticsearch\Concerns\BuildsFluentQueries::id(?string $id = NULL): Matchory\Elasticsearch\Concerns\BuildsFluentQueries must be compatible with Matchory\Elasticsearch\Concerns\ExecutesQueries::id(?string $id = NULL): Matchory\Elasticsearch\Concerns\ExecutesQueries in .../vendor/matchory/elasticsearch/src/Query.php on line 37

Can be fixed by deleting all abstract functions from trait /src/Concerns/ExecutesQueries.php

Thank you for reporting - those were mostly only helpful during development anyway.


Does it work for weather / daytime style transfer?

I.e. sunny to rainy, morning to night, etc.

if training data involves these cases, these specific transfer can achieve better performance

I.e. sunny to rainy, morning to night, etc.
if training data involves these cases, these specific transfer can achieve better performance

I.e. sunny to rainy, morning to night, etc.
if training data involves these cases, these specific transfer can achieve better performance

马哥牛逼


Recommended wallet for pools

Hello, my pool luck had a sudden drop, i have installed the new wallet using clearnet branch, now my yiimp shows  v<IP_ADDRESS>-29c7021-bet, im i using the right wallet version?

If unsure:
git fetch && git checkout 4.0.3b
And then build based on that tag, although your version looks good to me as long as you aren’t on 5.0.x

@marpme ，hi，I want to know the yiimp pool could work well with the VERGE 5.0 ?  should I run verge without-tor?

Well VERGE-5.0 alpha is not stable enough to offer its services for a pool mining like yiimp.
Please wait for the beta release, as we have to fix some stuff (like mining issues etc)

hi  @marpme, thank you. another question, does the 4.0clearnet support algo blake2s?  or I can only set algo= blake? I  set algo=blake2s .  when I run VERGEd getinfo. I get  "pow_algo" : "scrypt",  so I want to know how to set algo=blake2s.

algo=blake2s works well on wallet 5.0 version.


Update kubernetes-client, ... to 5.7.0

Updates

io.fabric8:kubernetes-client
io.fabric8:kubernetes-model
io.fabric8:kubernetes-server-mock

from 5.6.0 to 5.7.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (5.6.0).
You might want to review and update them manually.
website/package-lock.json
website/yarn.lock

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.fabric8" } ]

labels: library-update, semver-minor, old-version-remains

Superseded by #263.


Ansible operator support for abort reconcile loops on failure

Feature Request
Is your feature request related to a problem? Please describe.
This is a followup from https://github.com/operator-framework/operator-sdk/issues/2372 , where that issue was actually quite convenient during development where the reconcile loop stops when Ansible fails unexpectedly.
Describe the solution you'd like
It would be nice if the watches.yaml file would let us toggle that behavior, for example by using a strict or any_errors_fatal attribute. By default this would be false, and when it is true, the reconcile stops on ansible failure.

Hi @TristanCacqueray,
Following the comment inline.

For example, I currently have a bug where 'Ingress' objects can't be created in OpenShift, and I would prefer the operator to stop at that point, instead it prints a long stacktrace repeatedly.

So, what you are asking as a feature request is the ignore_errors: true. If you add it in the task which will create the ingress as described in the comment https://github.com/operator-framework/operator-sdk/issues/2431#issuecomment-575901409 then, It will not re-trigger the reconcile when it happens which means that the error will not be faced twice.
Also, you can solve the same scenario by adding an Ansible conditional in the task and just perform the action to create an ingress resource when its schema is present in the cluster. See here a blog post that explains how to do it with the Go operator in the order to help you do the same with ansible.
In this way, I understand that all is sorted out here and I am closing this one. However, please feel free to ping us if you still needing helping with for we re-open this issue.


use command

Codecov Report

Merging #83 (f9f3fff) into master (35bb712) will decrease coverage by 30.58%.
The diff coverage is 62.13%.

:exclamation: Current head f9f3fff differs from pull request most recent head 6094f96. Consider uploading reports for the commit 6094f96 to get more accurate results

@@             Coverage Diff             @@
##           master      #83       +/-   ##
===========================================
- Coverage   74.56%   43.98%   -30.59%
===========================================
  Files          16       22        +6
  Lines         928      939       +11
===========================================
- Hits          692      413      -279
- Misses        236      526      +290

Impacted Files
Coverage Δ

lib/display.js
100.00% <ø> (ø)

lib/helper.js
96.10% <ø> (-1.30%)
:arrow_down:

lib/context.js
17.64% <17.64%> (-82.36%)
:arrow_down:

cmds/meta/arc/cs/cluster/list.js
30.00% <22.22%> (ø)

lib/parser.js
9.87% <25.00%> (-85.72%)
:arrow_down:

cmds/meta/arc-tool/config/list.js
40.00% <33.33%> (ø)

cmds/meta/arc-tool/config/set.js
38.46% <33.33%> (ø)

cmds/meta/arc-tool/config/delete.js
38.46% <40.00%> (ø)

bin/arc-tool.js
66.66% <66.66%> (-33.34%)
:arrow_down:

bin/arc.js
66.66% <66.66%> (-33.34%)
:arrow_down:

... and 24 more

Continue to review full report at Codecov.

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


Cant make Totals work

Hey,
I am running Checkmk version RAW 2.2.0p1 and Grafana 9.2.6 with the grafana-checkmk-plugin 3.1.0-beta1.
I get some power usage graphs out of checkmk and try to add all the usages into one Total.
Unfortunatelly all I tried did not work. It seems if I use a Total it always shows the highest value of the values to calculate but not the Total.
Do you have any idea?
Kind regards

thanks for the report, i can reproduce this:
query

result

some speculation: the problems root cause is that we don't have a global clock for all the graphs. each graph could be sampled at a different frequency. although they actually have the same frequency in this example, we don't transport this information to grafana.

we will have to investigate this, but this will probably take some time.

any news?


Encrypt file name for more privacy

May be not convenient.
Optional feature ?
To dig...

Or random file name, and title in some markdown metadata or tags?


Title:  'Call For Speaker !' should be changed to 'Call For Speakers ' and the button here should have the label 'Join as a speaker'

Is your feature request related to a problem? Please describe.

Here this div of the homepage is for calling the speakers so I believe it should be changed to Speakers and the label of the button should also be changed
Describe the solution you'd like.

This is my proposed solution
@agamjotsingh18  Please assign me this issue

I would like to solve this issue....Can you please assign to me

Too easy issue


Removes declarations of removed methods of the EditorPropertyRevert class

…lass.
The implementation of these methods was removed in 1806ec7c14a8f038c0ff33a88d19087225c8d7ab.

Thanks!


JS String Enum Conversion

The example shown in the bucklescript docs:
<EMAIL_ADDRESS>jsConverter]
type fruit = [
  | `Apple
  |<EMAIL_ADDRESS>"miniCoconut"] `Kiwi
  | `Watermelon
];

gets reformatted to (something like the following)
<EMAIL_ADDRESS>jsConverter]
type fruit = [
  | `Apple
<EMAIL_ADDRESS>"miniCoconut"] | `Kiwi
  | `Watermelon
];

This is probably not expected. The<EMAIL_ADDRESS>...] should probably go after | as was shown in the docs.

Hey! This is fixed in the 3.0.4. Make sure you've upgraded =)


[5.8] Fix 26186 allow serialize igbinary

This PR aims to fix #26186 adding the ability to configure the PhpRedis module to use any of its supported custom serializers  (php-builtin, igBinary, msgpack).
PredisConnection will use PHP's default serialize & unserialize

Please remove the extra blank file. :)

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

Hey @taylorotwell, the bug being addressed in this PR is #26186.
To be clear, the main issue is exposing a feature inside of PhpRedis. You see, PhpRedis allows different serializers when storing the data in redis (php-builtin, igBinary, msgpack). You might also be wondering if these serialization methods have any benefits. Well, here is a comparison using PHP: v7.2.15 and Laravel: v5.7.25.
PhpRedis (serializer: php)
Execution time: 00:01:36.9863
Cache storage used: 936.75MB
— — — — — — — — — — — — — — — — —
PhpRedis (serializer: igbinary)
Execution time: 00:01:37.3176
Cache storage used: 342.66MB

Taken from this post in Medium.
I understand your concern of project maintenance for sanities sake. But if I did this under a standalone package, I'd technically just be reproducing all of the PhpRedisConnections functionality. Have you considered extracting all of PhpRedis's functionality to its own package and only supporting predis in the core framework package ?

@taylorotwell Pinging you again for visibility on this bug. Also, if this code is to be delayed for merging. Could we at least keep the issue open ?
RE:

If you feel absolutely certain that this code corrects a bug in the framework

For reference, @driesvints Tagged the issue this PR addresses as a bug. Don't mean to just randomly tag more maintainers in here but if you feel this isn't a bug he might have more insight as to why this is a bug

@Dudemullet I flagged it as a bug because I believe the SERIALIZER_IGBINARY option isn't correctly handled. I think you can re-attempt this pr. Maybe against the master branch. Also make sure you remove the blank file and such from this pr.


Validated Architecture concept integration

As a pull request owner and reviewers, I checked that:

[X] Doc will follow, we have to refactor it
[X] Tests will follow, we need "some" resources for that feature

/test all

Looks good, not able to find any issue.


Tenancy Website detection returns NULL inside commands

Description
Tenancy Website detection now returns NULL inside commands. Let's say you run your custom command on all tenants:
php artisan tenancy:run custom:command

Now inside the command trying to identify the tenant does work like this
$website = app(Environment::class)->tenant();

I was expecting this to work and based on our source code it appears to have worked in the previous version. The commands themselves appear to be running fine.
How do you get tenant information for the command currently being run?
Information

hyn/multi-tenant version: 5.4
laravel version: 5.8
database driver and version: MySQL
php version: 7.3

tenancy.php config
<?php
/*
 * This file is part of the hyn/multi-tenant package.
 *
 * (c) Daniël Klabbers<EMAIL_ADDRESS> *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 *
 * @see https://laravel-tenancy.com
 * @see https://github.com/hyn/multi-tenant
 */
use Hyn\Tenancy\Database\Connection;

return [
    'key' => env('TENANCY_KEY', null),

    'models' => [
        /**
         * Specify different models to be used for the global, system database
         * connection. These are also used in their relationships. Models
         * used have to implement their respective contracts and
         * either extend the SystemModel or use the trait
         * UsesSystemConnection.
         */
        // Must implement \Hyn\Tenancy\Contracts\Hostname
        'hostname' => \Hyn\Tenancy\Models\Hostname::class,
        // Must implement \Hyn\Tenancy\Contracts\Website
        'website' => \Hyn\Tenancy\Models\Website::class
    ],
    'website' => [
        /**
         * Each website has a short random hash that identifies this entity
         * to the application. By default this id is randomized and fully
         * auto-generated. In case you want to force your own logic for
         * when you need to have a better overview of the complete
         * tenant folder structure, disable this and implement
         * your own id generation logic.
         */
        'disable-random-id' => false,
        /**
         * The random Id generator is responsible for creating the hash as mentioned
         * above. You can override what generator to use by modifying this value
         * in the configuration.
         *
         * @warn This won't work if disable-random-id is true.
         */
        'random-id-generator' => Hyn\Tenancy\Generators\Uuid\ShaGenerator::class,
        /**
         * Enable this flag in case you're using a driver that does not support
         * database username or database name with a length of more than 32 characters.
         *
         * This should be enabled for MySQL, but not for MariaDB and PostgreSQL.
         */
        'uuid-limit-length-to-32' => env('LIMIT_UUID_LENGTH_32', true),
        /**
         * Specify the disk you configured in the filesystems.php file where to store
         * the tenant specific files, including media, packages, routes and other
         * files for this particular website.
         *
         * @info If not set, will revert to the default filesystem.
         */

        // Disable tenancy disk as it doesn't handle public and private disks

        'disk' => false,
        /**
         * Automatically generate a tenant directory based on the random id of the
         * website. Uses the above disk to store files to override system-wide
         * files.
         *
         * @info set to false to disable.
         */
        'auto-create-tenant-directory' => true,
        /**
         * Automatically rename the tenant directory when the random id of the
         * website changes. This should not be too common, but in case it happens
         * we automatically want to move files accordingly.
         *
         * @info set to false to disable.
         */
        'auto-rename-tenant-directory' => true,
        /**
         * Automatically deletes the tenant specific directory and all files
         * contained within.
         *
         * @see
         * @info set to true to enable.
         */
        'auto-delete-tenant-directory' => true,
        /**
         * Time to cache websites in minutes. Set to false to disable.
         */
        'cache' => 10,
    ],
    'hostname' => [
        /**
         * If you want the multi tenant application to fall back to a default
         * hostname/website in case the requested hostname was not found
         * in the database, complete in detail the default hostname.
         *
         * @warn this must be a FQDN, these have no protocol or path!
         */
        'default' => env('TENANCY_DEFAULT_HOSTNAME'),
        /**
         * The package is able to identify the requested hostname by itself,
         * disable to get full control (and responsibility) over hostname
         * identification. The hostname identification is needed to
         * set a specific website as currently active.
         *
         * @see src/Jobs/HostnameIdentification.php
         */
        'auto-identification' => env('TENANCY_AUTO_HOSTNAME_IDENTIFICATION', true),
        /**
         * In case you want to have the tenancy environment set up early,
         * enable this flag. This will run the tenant identification
         * inside a middleware. This will eager load tenancy.
         *
         * A good use case is when you have set "tenant" as the default
         * database connection.
         */
        'early-identification' => env('TENANCY_EARLY_IDENTIFICATION', true),
        /**
         * Abort application execution in case no hostname was identified. This will throw a
         * 404 not found in case the tenant hostname was not resolved.
         *
         * @see https://hyn.readme.io/v3.0/docs/tenancy#section-hostnameabort-without-identified-hostname
         */
        'abort-without-identified-hostname' => env('TENANCY_ABORT_WITHOUT_HOSTNAME',true),
        /**
         * Time to cache hostnames in minutes. Set to false to disable.
         */
        'cache' => 10,
    ],
    'db' => [
        /**
         * The default connection to use; this overrules the Laravel database.default
         * configuration setting. In Laravel this is normally configured to 'mysql'.
         * You can set a environment variable to override the default database
         * connection to - for instance - the tenant connection 'tenant'.
         *
         * @see https://hyn.readme.io/v3.0/docs/tenancy#section-dbdefault
         */
        'default' => env('TENANCY_DEFAULT_CONNECTION'),
        /**
         * Used to give names to the system and tenant database connections. By
         * default we configure 'system' and 'tenant'. The tenant connection
         * is set up automatically by this package.
         *
         * @see src/Database/Connection.php
         * @var system-connection-name The database connection name to use for the global/system database.
         * @var tenant-connection-name The database connection name to use for the tenant database.
         */
        'system-connection-name' => env('TENANCY_SYSTEM_CONNECTION_NAME', Connection::DEFAULT_SYSTEM_NAME),
        'tenant-connection-name' => env('TENANCY_TENANT_CONNECTION_NAME', Connection::DEFAULT_TENANT_NAME),
        /**
         * The tenant division mode specifies to what database websites will be
         * connecting. The default setup is to use a new database per tenant.
         * In case you prefer to use the same database with a table prefix,
         * set the mode to 'prefix'.
         *
         * @see src/Database/Connection.php
         */
        'tenant-division-mode' => env('TENANCY_DATABASE_DIVISION_MODE', 'database'),
        /**
         * The database password generator takes care of creating a valid hashed
         * string used for tenants to connect to the specific database. Do
         * note that this will only work in 'division modes' that set up
         * a connection to a separate database.
         */
        'password-generator' => Hyn\Tenancy\Generators\Database\DefaultPasswordGenerator::class,
        /**
         * The tenant migrations to be run during creation of a tenant. Specify a directory
         * to run the migrations from. If specified these migrations will be executed
         * whenever a new tenant is created.
         *
         * @info set to false to disable auto migrating.
         *
         * @warn this has to be an absolute path, feel free to use helper methods like
         * base_path() or database_path() to set this up.
         */
        'tenant-migrations-path' => database_path('migrations_tenant'),
        /**
         * Seeds the newly created tenant database based on this Seeder.
         *
         * @info requires tenant-migrations-path to be in use.
         *
         * @warn specify a valid fully qualified class name.
         * @example App\Seeders\AdminSeeder::class
         */
        'tenant-seed-class' => null,
        /**
         * Automatically generate a tenant database based on the random id of the
         * website.
         *
         * @info set to false to disable.
         */
        'auto-create-tenant-database' => true,
        /**
         * Automatically rename the tenant database when the random id of the
         * website changes. This should not be too common, but in case it happens
         * we automatically want to move databases accordingly.
         *
         * @info set to false to disable.
         */
        'auto-rename-tenant-database' => true,
        /**
         * Automatically deletes the tenant specific database and all data
         * contained within.
         *
         * @info set to true to enable.
         */
        'auto-delete-tenant-database' => true,
    ],
    'folders' => [
        'config' => [
            /**
             * Merge configuration files from the config directory
             * inside the tenant directory with the global configuration files.
             */
            'enabled' => false,
            /**
             * List of configuration files to ignore, preventing override of crucial
             * application configurations.
             */
            'blacklist' => ['database', 'tenancy', 'webserver'],
        ],
        'routes' => [
            /**
             * Allows adding and overriding URL routes inside the tenant directory.
             */
            'enabled' => false,
            /**
             * Prefix all tenant routes.
             */
            'prefix' => null,
        ],
        'trans' => [
            /**
             * Allows reading translation files from a trans directory inside
             * the tenant directory.
             */
            'enabled' => false,
            /**
             * Will override the global translations with the tenant translations.
             * This is done by overriding the laravel default translator with the new path.
             */
            'override-global' => false,
            /**
             * In case you disabled global override, specify a namespace here to load the
             * tenant translation files with.
             */
            'namespace' => 'tenant',
        ],
        'vendor' => [
            /**
             * Allows using a custom vendor (composer driven) folder inside
             * the tenant directory.
             */
            'enabled' => false,
        ],
        'media' => [
            /**
             * Mounts the assets directory with (static) files for public use.
             */
            'enabled' => true,
        ]
    ]
];

Figured this out. Do not attempt to get the current tenant in the command constructor.
$website = app(Environment::class)->tenant();
Get tenant in the handle() method and it works as expected.


WIP - add vulkan hpp headers

This WIP PR  add support for using not only C vulkan headers, but and C++ headers #2347
What you think about:

Replace in Vulkan.hpp, VulkanImpl*.hpp headers and code to use vulkan.hpp header?
Basically we can leave it as is.
Add vulkancpp example?

Adding a quarter million lines of code to the repo feels like a bit much just to be able to use the Vulkan C++ API. I don't think I can approve such a huge influx of 3rd party code into the repo when we're hoping to get rid of 3rd party code from the repo.

@rtkid-nt Have you got Discord, I've noticed you're eager to contribute and it may be easier to join the discord server and have a discussion in there with some of the maintainers. There's lots to do, and you clearly have some ideas of further things that could be done so feel free to boogie on down to Discord!


Setting ProxyPreserveHost to its default value: Off

I never see the repos if this setting is set to on.  By default, mod_proxy recommends that it should be off: https://httpd.apache.org/docs/2.4/mod/mod_proxy.html.
"This option should normally be turned Off. It is mostly useful in special configurations like proxied mass name-based virtual hosting, where the original Host header needs to be evaluated by the backend server."

Thank you @cubfan20 for this PR.


[Feature] Map Field Style Options and Documentation Update

Added extra styles option for custom map field style.
Updated readme file documentation.

Good idea 👍


Can't Update Fastlane w/ sudo gem update fastlane

New Issue Checklist

[ ] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
I can't update Fastlane to the latest version. I've tried using the stand-alone installer to reinstall as well as running sudo gem update fastlane and neither are working.
When trying sudo gem update fastlane I am returned:

Updating installed gems
Noting to update

Complete output when running fastlane, including the stack trace and command used

Updating installed gems
Updating fastlane
Fetching: tty-screen-0.5.0.gem (100%)
Successfully installed tty-screen-0.5.0
Fetching: fastlane-2.15.1.gem (100%)
Successfully installed fastlane-2.15.1
Gems updated: fastlane tty-screen
Cleaning up installed gems...
Attempting to uninstall fastlane-2.13.0
Successfully uninstalled fastlane-2.13.0
Clean Up Complete
Detected fastlane is already in your path 🚀
xcdda:my-xplore ehorodys$ fastlane -v
fastlane installation at path:
/Library/Ruby/Gems/2.0.0/gems/fastlane-2.14.2/bin/fastlane

Environment
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.11.6

Ruby
2.0.0

Bundler?
false

Git
git version 2.10.1 (Apple Git-78)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.11.6 (15G1217)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib

OpenSSL Version
OpenSSL 0.9.8zc 19 Mar 2015

Is contained
false

Is homebrew
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
update_fastlane

# This is the minimum version number required.
fastlane_version "2.14.2"

# Fastlane Hooks
before_all do
   ENV["SLACK_URL"] = "https://hooks.slack.com/services/"
end

error do |lane, exception|
  slack(message: exception.message, success: false)
end

after_all do |lane, options|
  slack(message: @message)
end

# Multiplatform Lanes
desc "Asset Build"
private_lane :build do |options|
  #sh "gulp build --" + options[:env]
end

# Android Lanes
platform :android do
  # Valid Android Tracks: [alpha | beta | production | rollout]

  # Public Lanes

  desc "Submit a new build to Google Play"
  lane :deploy do |options|
    if !['dev', 'qa', 'prod'].include? options[:env]
      raise "Please provide 'env' option as 'dev', 'qa', or 'prod'"
    else
      case options[:env]
      when 'dev'
        build(env: options[:env])
        package()
        submit(track: "alpha")
       when 'qa'
        build(env: options[:env])
        package()
        submit(track: "qa")
       when 'prod'
        build(env: options[:env])
        package()
        submit(track: "production")
      else
        raise "Please provide 'env' option as 'dev', 'qa', or 'prod'"
      end
    end
  end

  # Private Lanes

  desc "Package APK"
  private_lane :package do |options|
    sh "cp -u /Users/Shared/keys/android/android_keystore.jks /Users/Shared/keys/android/release-signing.properties ./platforms/android/"
    #sh "ionic build android --release"
  end

  desc "Deploy to Google Play"
  private_lane :submit do |options|
    #supply(track: options[:track], apk_pahts: #["platforms/android/build/outputs/apk/android-release.apk"])
   # @message = "[Google Play] Deployed to " + options[:track].capitalize() + " Channel"
  end

end

# iOS Lanes
platform :ios do

  desc "Deploy to Internal Testflight"
  lane :internal do
    prepare()
    @message = "[AppStore] deployed to Internal TestFlight"
  end

  # Private Lanes

  desc "Prepare iOS"
  private_lane :prepare do |options|
    sh "ionic prepare ios"
  end

end```
</details>

<details><summary>`./fastlane/Appfile`</summary>

```ruby
json_key_file "automation.json" # Path to the json secret file - Follow https://github.com/fastlane/supply#setup to get one
package_name "org.ieee.mobile.pubs.myxplore" # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.14.2
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

i18n
0.8.0

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.10.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
<IP_ADDRESS>

json
1.8.6

generated on: 2017-02-14

From your other issue, could you try this?
INFO [2017-02-14 11:02:11.35]: Looking for updates for fastlane...
WARN [2017-02-14 11:02:11.45]: The update_fastlane action requires rubygems version 2.1.0 or greater.
WARN [2017-02-14 11:02:11.45]: Please update your version of ruby gems before proceeding.
INFO [2017-02-14 11:02:11.45]: $ gem install rubygems-update
INFO [2017-02-14 11:02:11.45]: $ update_rubygems
INFO [2017-02-14 11:02:11.45]: $ gem update --system

This is what I get:
xcdda:~ ehorodys$ gem install rubygems-update
Successfully installed rubygems-update-2.6.10
Parsing documentation for rubygems-update-2.6.10
Done installing documentation for rubygems-update after 0 seconds
1 gem installed
xcdda:~ ehorodys$ update_rubygems
RubyGems 2.6.10 installed
Parsing documentation for rubygems-2.6.10
Installing ri documentation for rubygems-2.6.10

=== 2.6.10 / 2017-01-23

Bug fixes:

* Fix `require` calling the wrong `gem` method when it is overridden.
  Pull request #1822 by Samuel Giddins.

------------------------------------------------------------------------------

RubyGems installed the following executables:
	/usr/local/Cellar/ruby/2.4.0/bin/gem

Ruby Interactive (ri) documentation was installed. ri is kind of like man
pages for ruby libraries. You may access it like this:
  ri Classname
  ri Classname.class_method
  ri Classname#instance_method
If you do not wish to install this documentation in the future, use the
--no-document flag, or set it as the default in your ~/.gemrc file. See
'gem help env' for details.

xcdda:~ ehorodys$ gem update --system
Latest version currently installed. Aborting.

Then trying to update Fastlane gives me the same as my first post.

I have the same issue.

The same here.
fastlane update_fastlane:
Updating installed gems
Nothing to update
Cleaning up installed gems...
Clean Up Complete

after download new version of fastlane from website:
fastlane is already installed at /Users/User/.fastlane/bin
Do you want to reinstall fastlane? The old directory, including any changes you made, will be removed! (y/N) y
The installer will now run the uninstall script to remove your existing fastlane bundle...
Do you want to uninstall fastlane from /Users/User/.fastlane/bin? (y/n) y
You can now remove fastlane from your search path by editing your unknown file.
fastlane was uninstalled successfully!
Done uninstalling, your regular installation will now commence. 🚕 💨
Installing fastlane to /Users/User/.fastlane/bin... this might take a few seconds
Successfully copied fastlane to /Users/User/.fastlane/bin

Updating installed gems
Updating fastlane
Fetching: tty-screen-0.5.0.gem (100%)
Successfully installed tty-screen-0.5.0
Fetching: fastlane-2.18.3.gem (100%)
Successfully installed fastlane-2.18.3
Gems updated: fastlane tty-screen
Cleaning up installed gems...
Attempting to uninstall fastlane-2.13.0
Successfully uninstalled fastlane-2.13.0
Clean Up Complete
Detected fastlane is already in your path 🚀

Hi everyone! I think there might be two issues going on in here based on different mechanisms of having installed fastlane.
@ehorodyski It looks like you may have installed fastlane from the Fabric Mac app, is that right? If so, you should be able to update by opening up the Fabric app again and clicking on the fastlane tab to see that an update is available.
 Do you know what version you had when you only ran fastlane update_fastlane?

Sorry, I should have mentioned a while ago that it seems to be working now. Not sure what I did, to be honest.
@ohayon -- I did not install the Fabric Map app. I installed it from the page where you set up a beta script and you download the zip that contains Fastlane within it.

Thanks for following up @ehorodyski ! 🚀


Tests

added tests
changed wget to show progress
changed to codait/max-base image
added . ignore files

Should we also change this to use requests so we standardize across all MAX models?


Test issue

This is just an issue to test whether the bot is tagging container registry issues correctly.

Please see email thread.


Add logging-operator to OperatorHub.io

It would be nice if logging-operator could be packaged and used with Operator Lifecycle Manager. As a side effect you could also promote your Operator, like other BanzaiCloud Operators already, on https://operatorhub.io
Instructions about packaging can be found here https://operatorhub.io/contribute and in more detail here https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md#manual-testing-on-kubernetes

Operatorhub.io automated the entire testing since last year. An update is now as simple as creating a new directory with all your new CRDs and the metadata file (CSV).


Container image with installer script and dependencies

Signed-off-by: Aishwarya Kamat<EMAIL_ADDRESS>

Thanks @aishwaryabk I will test this PR when I get to and let you know of any feedback.

@aishwaryabk Please remove the documentation from this PR. Once the https://github.com/ocp-power-automation/openshift-install-power/pull/140 is merged I will remove the do-not-merge tag.
Once we have the dockerimage in the repo, we need Travis pipeline for creating and publishing the images as per release version. After that we can update the documentation on how to use the docker image.

@aishwaryabk Please remove the documentation from this PR. Once the #140 is merged I will remove the do-not-merge tag.
Once we have the dockerimage in the repo, we need Travis pipeline for creating and publishing the images as per release version. After that we can update the documentation on how to use the docker image.

@yussufsh Updated the changes.

@aishwaryabk looks like you are making progress here.  Still targeting to wrap in this sprint?

/unhold


[FEATURE REQUEST] Way to use this with a touchscreen?

So, I am running Magic Mirror2 on a raspberry pi with a 7 inch touchscreen. As far as I can see, there is no way to swap pages in slide mode with the touchscreen. Is there any way to do this?

I would like this as well!

Make sure you have showPageControls: true in the module config and then you should have two "hidden" arrow buttons on the lower left/right corners to navigate. If using a mouse these will appear when you hover over them (you can force them to always show if you add some custom css to your custom.css file).

Can I just slide the page like on the phones?

Make sure you have showPageControls: true in the module config and then you should have two "hidden" arrow buttons on the lower left/right corners to navigate. If using a mouse these will appear when you hover over them (you can force them to always show if you add some custom css to your custom.css file).

What would that custom CSS be? I'd like the buttons to show all the time on my touchscreen.

What would that custom CSS be? I'd like the buttons to show all the time on my touchscreen.

.control label {
opacity: 0.5;
}


Refactored structure into many different smaller modules.

I separated the code into small modules for better locality of content.
Modules now differentiate between Oracles and QueryStrategies (QuerySynthesis, Sequential and Subspace).
All tests are passing.

Pull Request Test Coverage Report for Build 186

86 of 102 (84.31%)  changed or added relevant lines in 21 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 86.984%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/QueryStrategies/SubspaceQueryStrategies/SubspaceQs.jl
11
12
91.67%

src/Oracles/QuerySynthesisSVMOracle.jl
18
24
75.0%

src/QueryStrategies/SubspaceQueryStrategies/subspace_util.jl
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/QueryStrategies/qs_utils.jl
4
30.43%

Totals

Change from base Build 185:
-0.5%

Covered Lines:
695

Relevant Lines:
799

💛  - Coveralls


FL_HOCKEY_TIMEOUT fix for "undefined method `zero?'"

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
There was no type specified for FL_HOCKEY_TIMEOUT, and therefore it was passed to faraday as string, causing: undefined method `zero?'
Description
I set the config item type to Integer.
I did not actually test it, but given that the original version leads to undefined method, that path of execution can only become better with the change.

@janpio I recreated https://github.com/fastlane/fastlane/pull/13290 in this new PR.


Error: Main stack(20007988) was overflow

The Example "Create Document" is not working with my Arduino WiFi R4.
The code is attached.
Error Message:
13:43:45.150 -> Fault on interrupt or bare metal(no OS) environment
13:43:45.150 -> Error: Main stack(20007988) was overflow
13:43:45.150 -> ===== Thread stack information =====
13:43:45.150 ->   addr: 20007b00    data: 00000000
Do you have any idea how i can solve this problem?
Example.txt

That device memory is not enough for use with this library that relies on BearSSL which may not work in some ARM and SAMD devices.
This is the know issue that cannot be fixed.
You can try this better new library.


BIGTOP-3341. Support for Openssl 1.1.1.

manually tested by putting file into encryption zone with hadoop.security.secure.random.impl=org.apache.hadoop.crypto.random.OpensslSecureRandom on CentOS 8 (openssl-1.1.1-8.el8.x86_64).
ran smoke test of hdfs, yarn, mapreduce and kms on CentOS 7 (openssl-1.0.2k-19.el7.x86_64) to check regression on OpenSSL < 1.1.0 env.

docker:
        memory_limit: "12g"
        image: "bigtop/puppet:trunk-centos-7"
distro: centos
components: [hdfs, yarn, mapreduce, kms]
enable_local_repo: true
smoke_test_components: [hdfs, yarn, mapreduce, kms]

Looks promising. +1. Thanks @iwasakims.

merged. Thanks, @evans-ye.


sdhash crashes on Win 8.1 when comparing

I am able to generate hashes with no issues, but the application crashes when attempting to compare these hashes:
Unhandled exception at 0x00007FFFE9738B9C in sdhash.exe: Microsoft C++ exception:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >
at memory location 0x000000000062D438.

I figured it out -- the problem is with the : delimiter in the .sdbf file.  On Windows, the full file path is stored, which contains C:\.  This is causing the parser to have a bad_lexical_cast exception at sdbf_class.cc:161.  I recompiled the code with pipe delimiters and now it is working.


Add kubephp

Suggesting to add https://github.com/sherifabdlnaby/kubephp to Awesome PHP.
I understand that "self-promotion" is frowned upon, however, I found no similar project referenced here.
I put it under Infrastructure because it's as close to what kubephp is, which is being a Production base template for your docker image.
The second category that it might belong to is Development Environment, although kubephp helps with Development with the dev docker image, it's also a production docker image template and hence I didn't put it under 'Development Environment`.

Thanks for your suggestion.


fix(mount): fix parsing /proc/cmdline

Why is this PR required? What issue does it fix?:
NDM is crashing on new GKE setups due to a failure in parsing the /proc/cmdline file. This issue occurs when the file contains a root partition entry like root=/dev/dm-0, where the identifier type is not present
What this PR does?:

adds additional check of no.of items in the root= line while parsing
fix service account in ndm yamls

Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[x] Fixes #515
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[x] Has the change log section been updated?
[x] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

cc: @zlymeda

LGTM


[UI]: Missing network description

Issue description
The network descriptions are still placeholder texts + the legacy network placeholder refers to the "coordicide network".

Expected behaviour
no placeholders
Actual behaviour
placeholders
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Errors
No response
Duplicate declaration

[X] I have searched the issues tracker for this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed in https://github.com/iotaledger/explorer/pull/195.


removed html comment tag

@shawnweisfeld : Thanks for your contribution! The author, @KathrynEE, has been notified to review your proposed change.

@shawnweisfeld - Thank you for your submission - however, The commented out text was meant to be commented out. I'm removing it for now - as it is essentially redundant text. CLosing this PR without merging.