Cache Control

#600
Advanced Caching of Images and few other assets as required.
@anushbhatia Sir, you may review it. The rest of the info I have send on slack. Thank you!

Resolve the conflicts

Done Sir!


create project structure - Milestone 1

Project folder must be structured for both plutarch and aiken

MerkleTree

Plutarch
Aiken

Linked List

Plutarch
Aiken

Trie

Plutarch
Aiken

ideally each project folder should contain

.envrc
flake.nix

fix #4


AOT snapshot size regression due to bool checks

https://github.com/dart-lang/sdk/commit/7d90df42f1c9f245395a09cf4c7af29e16763201 caused the regression of AOT snapshot size (instructions size) on Flutter apps.
To reproduce, build local flutter engine with particular version of dart sdk and run
cd flutter/examples/flutter_gallery
flutter clean && flutter build aot -v --release --preview-dart-2 --local-engine android_release

Before (at https://github.com/dart-lang/sdk/commit/4da52281aa35b6c1951b3e269a6934412b15b105):
[+9584 ms] VMIsolate(CodeSize): 5667
                   Isolate(CodeSize): 2456900
                   ReadOnlyData(CodeSize): 2081200
                   Instructions(CodeSize): 7204912
                   Total(CodeSize): 11748679

After (at https://github.com/dart-lang/sdk/commit/7d90df42f1c9f245395a09cf4c7af29e16763201):
[+10108 ms] VMIsolate(CodeSize): 5667
                    Isolate(CodeSize): 2488484
                    ReadOnlyData(CodeSize): 2159256
                    Instructions(CodeSize): 7572112
                    Total(CodeSize): 12225519

/cc @crelier @a-siva @mkustermann @mraleph

Since the checks were missing in strong mode, adding them back obviously increased code size.
I suppose that kernel should not emit the CheckBoolean flow graph node if type inference can guarantee that the value is bool and not null.

Current baseline (at 09e1766e6caa537e1271fbce04ebcbf8212b6569):
Instructions(CodeSize): 7357472
Total(CodeSize): 11898704

Baseline + bool checks reverted (7d90df42f1c9f245395a09cf4c7af29e16763201)
Instructions(CodeSize): 7022720
Total(CodeSize): 11456672

With optimizations (b29f19f4e1eea82b1dc3623f614d65fe4ddf6d1b, 83f5b1f740c92534e8e0e42d07af90842c6a232d):
Instructions(CodeSize): 7159120
Total(CodeSize): 11648470


Typeguard failing for undefined variable

TypeScript Version:  3.8.3

Search Terms:
error TS2532: Object is possibly 'undefined'.
Typeguard bug undefined filter
Typescript typeguard not working
Code
const arr = [{ time: 1 }];
const startDate = undefined;

if (startDate) {
    const filtered = arr.filter(item => item.time >= startDate);
}

Expected behavior:
No error.
Typescript compiler works and passes the above code because we have a Typeguard around accessing startDate
Actual behavior:
The Typescript compiler reports the following error.
yarn tsc
TS2532: Object is possibly 'undefined'.
const filtered = arr.filter(item => item.time >= startDate);
                                                 ~~~~~~~~~

Workaround
Use the non-null assertion operator !.
const filtered = arr.filter(item => item.time >= startDate!);

Disable the line if using eslint.
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion

Playground Link:
Playground Link

The absolutely correct thing to do here would be to narrow startDate to never and then error on that instead, but the error is effectively correct in its intent and for a problem like this, any error is good enough.

If startDate was a union type likeDate | undefined, type never would be applicable here. The typeguard would still error.

This code works fine:
const arr = [{ time: 1 }];
const startDate = Math.random() > 0.5 ? 100 : undefined;

if (startDate) {
    const filtered = arr.filter(item => item.time >= startDate);
}

Consider the following code:
const arr = [{ time: 100 }];
const obj = { startDate: Math.random() > 0.5 ? 100 : undefined };

if (obj.startDate) {
    const filtered = arr.filter(item => item.time >= obj.startDate);
    console.log(filtered);
}

(property) startDate: number | undefined
Object is possibly 'undefined'.(2532)

Playground Link

@RyanCavanaugh Thoughts?


Add CirceSensitiveDataEntityDecoder

/** Derive [[EntityDecoder]] if implicit [[Decoder]] is in the scope without need to explicitly call `jsonOfSensitive`
  *
  * Note that it varies from [[CirceEntityDecoder]] in that, when failing to decode [[io.circe.Json]] to an `A`,
  * the JSON will not be included in the raised [[Exception]]. In the event the JSON includes sensitive data, this trait is,
  * arguably, a better choice since it eliminates the risk of logging sensitive data, e.g. due to logging a raised [[Throwable]]
  * that includes the sensitive JSON.
  */

I will add specs later today. Thinking about it more, I am not sure if one of the decoding failures could include sensitive data￼.

I wonder if adding a subtype of DecodeFailure which has sanitized and details components, similar to ParseFailure, would make sense to handle this case. That would allow redaction for other decoding failures with other media types as well.

I see the following sub-types of DecodeFailure:

My initial guess is that, to support your idea on 0.21.x, @isomarcte, that would involve, for all instances of DecodeFailure's sub-types, to remove any sensitive data that's passed as a message, i.e. required by org.http4s.MessageFailure? Please say more, David. Thanks.

It has been a general principle to not put request information in messages.

Looking at ParseFailure, is ParseFailure's comment on details, namley "may freely echo a Request," at odds with your "to not put request information" statement, @rossabaker?
/** Indicates an error parsing an HTTP [[Message]].
  *
  * @param sanitized May safely be displayed to a client to describe an error
  *                  condition.  Should not echo any part of a Request.
  * @param details Contains any relevant details omitted from the sanitized
  *                version of the error.  This may freely echo a Request.
  */
final case class ParseFailure(sanitized: String, details: String)

@kevinmeredith I was thinking of something like this.
final case class SanitizedDecodeFailure(sanitized: String, details: String, override val cause: Option[Throwable]) extends DecodeFailure {
  override def message: String = sanitized
}

object SanitizedDecodeFailure {
  def fromDecodeFailure(value: DecodeFailure, sanitize: String => String): SanitizedDecodeFailure =
    value match {
      case value: SanitizedDecodeFailure => value
      case otherwise: DecodeFailure =>
        SanitizedDecodeFailure(sanitize(otherwise.message), otherwise.message, otherwise.cause)
    }
}

Then you could opt in any EntityDecoder like this,
val decoder: EntityDecoder[F, A] = ???
val sanitizedEntityDecoder: EntityDecoder[F, A] = decoder.handleErrorWith{
  case e => EitherT.leftT(SanitizedDecodeFailure.fromDecodeFailure(e))
}

Looking at ParseFailure, is ParseFailure's comment on details, namely "may freely echo a Request," at odds with your "to not put request information" statement, @rossabaker?

sanitized can describe in broad terms what's wrong with the request, but can't repeat any information.  For example, you can say "malformed JSON", but you can't say "Malformed boolean: expected true or false, got troo".  But details could give that latter level of detail.  Echoing request information into a response is dangerous for XSS attacks, so we maintain sanitized as a safe thing that can go in default responses and details as something reserved for server-side logging.  If people want the details because it's an intranet app, they're welcome to use them, but we maintain tighter security by default.

Thanks, @rossabaker, for writing up https://github.com/http4s/http4s/pull/4012#issuecomment-747850280. I admit that I'm still foggy on the intent of message, sanitized, and details. However, I expect that I'll learn more as I follow any further discussions of SanitizedDecodeFailure.
Thanks for sharing https://github.com/http4s/http4s/pull/4012#issuecomment-747527228, @isomarcte.
I still admit that I don't entirely understand how SanitizedDecodeFailure would be threaded throughout the 0.21.x code-base. sanitize: String => String seems a bit coarse to me, i.e. sanitizing a String rather than a, let's say an A, yet I don't have any better ideas.
Given that, it seems to me that a few options exist:

merge + cut a release of this PR since it solves a problem at-hand of logging JSON (which can include sensitive data) that fails to decode to A
@isomarcte opens a PR against this branch or a separate PR against main that adds SanitizedDecodeFailure, as well as implements an equivalent CirceSensitiveDataEntityDecoder using SanitizedDecodeFailure

Or, another option, it seems to me, is to do step 1 first, and then step 2 afterwards.
What do you think, @rossabaker @isomarcte?

Hi @rossabaker and @isomarcte - any thoughts, please, on https://github.com/http4s/http4s/pull/4012#issuecomment-748413263? In short, I'm proposing moving forward with this PR as-is as it provides a useful EntityDecoder[F, A] to import to avoid logging sensitive data. My partial understanding is that, if SanitizedDecodeFailure gets added, then the internals of CirceSensitiveDataEntityDecoder could, perhaps, be re-factored to use such an approach.

@kevinmeredith I'm fine with that, though my opinion doesn't carry much weight. I think we could add SanitizedDecodeFailure in series/0.21, and there may even be an argument that it should be used by default for all EntityDecoder instances, but if you want to go this route in the meantime I think it is still a net gain.
I doubt I'll get to making a PR for SanitizedDecodeFailure for a bit still if you can't/don't want to take a pass at it @kevinmeredith .

Hey Ross - is this one good to go? Thanks!

I was seeing if anyone else wanted to weigh in, but it's been open a while. :+1:


Add Kinetica vectorstore to Langchain

Overview
This PR adds Kinetica to the list of vectorstores instrumented in Langchain.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (develop-ai-limited-preview-3@c8d3a99). Click here to learn what that means.

Additional details and impacted files
@@                       Coverage Diff                       @@
##             develop-ai-limited-preview-3    #1080   +/-   ##
===============================================================
  Coverage                                ?   81.88%
===============================================================
  Files                                   ?      192
  Lines                                   ?    21113
  Branches                                ?     3693
===============================================================
  Hits                                    ?    17289
  Misses                                  ?     2761
  Partials                                ?     1063

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Live query for data sync

Is there any way for implementing data sync on live query in javascript client library ??
If yes , How to ?
If not , How can we implementing this ??

Not sure what you mean, but that seems to be a question for the JS-SDK, please reopen on https://github.com/parseplatform/parse-SDK-JS


Feature: Integrate code coverage for PHP

In order to setup code-coverage detection there's a few steps an individual typically has to follow which this project could offer right from the start, some at least explained in docs/README.
Detailed Description
By default a SonarQube project is marked as failed (after a scan) when code-coverage hasn't been setup and integrated (assuming you have tests or are planning to add them).
Therefore, instead of disabling the code coverage checks we must set them up and a few steps are involved in doing so.
The setup process may vary slightly from language to language but having a basic guide to follow for PHP specifically could give something for other languages to be based off.
Additional Context
As mentioned, this will be helpful to achieve code-coverage detection in SonarQube.
Possible Implementation

Install phpunit and Xdebug
Update the phpunit.xml
Generate coverage report with phpunit --coverage-clover coverage-report.xml
Update the SonarQube project properties:

sonar.php.coverage.reportPaths=coverage-report.xml
sonar.php.tests.reportPath=tests-report.xml

Some other steps may also be required but this is a very quick insight and a PR will be followed up with a proper implementation.
Alternative Implementation
n/a
Your Environment
Localhost SonarQube version used: 1.0.0
Operating System and version: macOS Big Sur 11.1

@denizaygun the primary objective of this project was to provide a developer friendly CLI tool to setup and interact with SonarQube without requiring developers to have the knowledge on how to install SonarQube and SonarScanner dependencies or how to use Docker CLI. As per the Disclaimer section in the readme.
Please note: This readme assumes you are familiar with SonarQube and will not be covering on
how to setup projects in SonarQube and configure sonar-project.properties files to analyse a project.
Please visit SonarQube Documentation for additional instructions.

SonarQube can analyse up to 27 different languages and in the Guides category of the SonarSource Community forum you might find instructions on generating the test coverage and execution reports.
I have updated the Laravel SonarScanner template in v0.1.2 to include test coverage & execution properties.
# --- test coverage & execution properties ---

# Comma-delimited list of paths to Clover XML-format coverage report files.
# Paths may be absolute or relative to project root.
#sonar.php.coverage.reportPaths=

# Path to the PHPUnit unit test execution report file. Path may be absolute or
# relative to project root.
#sonar.php.tests.reportPath=

I have enabled the Wiki section in the repo to allow us to provide additional documentation on configuring SonarQube project properties. The repo does have a Discussion section as well for developers to provide suggestions or need additional assistance.
However if developers are struggling to use SonarQube and not the CLI tool that this repo provides; I would recommend developers to visit SonarSource Community forum. Since they would be more successful in receiving a resolution for their issue because this repo is not affiliated with SonarSource SA and is not an official product

@denizaygun the primary objective of this project was to provide a developer friendly CLI tool to setup and interact with SonarQube without requiring developers to have the knowledge on how to install SonarQube and SonarScanner dependencies or how to use Docker CLI. As per the Disclaimer section in the readme.
Please note: This readme assumes you are familiar with SonarQube and will not be covering on
how to setup projects in SonarQube and configure sonar-project.properties files to analyse a project.
Please visit SonarQube Documentation for additional instructions.

SonarQube can analyse up to 27 different languages and in the Guides category of the SonarSource Community forum you might find instructions on generating the test coverage and execution reports.
I have updated the Laravel SonarScanner template in v0.1.2 to include test coverage & execution properties.
# --- test coverage & execution properties ---

# Comma-delimited list of paths to Clover XML-format coverage report files.
# Paths may be absolute or relative to project root.
#sonar.php.coverage.reportPaths=

# Path to the PHPUnit unit test execution report file. Path may be absolute or
# relative to project root.
#sonar.php.tests.reportPath=

I have enabled the Wiki section in the repo to allow us to provide additional documentation on configuring SonarQube project properties. The repo does have a Discussion section as well for developers to provide suggestions or need additional assistance.
However if developers are struggling to use SonarQube and not the CLI tool that this repo provides; I would recommend developers to visit SonarSource Community forum. Since they would be more successful in receiving a resolution for their issue because this repo is not affiliated with SonarSource SA and is not an official product


support define a watcher whose key is symbol * to watch all properties of data

example
new Vue({
    data: {
        name: "hal",
        age: 30
    },
    watch: {
       "*": function(prop, newVal, val){
            console.log(prop + " changed: " + val + " --> " + newVal);
       }
   }
})

I'm not at my computer to check this but can't you just watch "$data" with Vue to the same effect?

Ah no you can't! +1 Although perhaps watch $data might be more intuitive.
http://jsfiddle.net/4qs8kkan/1/

But this would not trigger on nested data changes, right?


Change numbers in the bossbar to roman style and change the pattern color

Hi, can you please add a possibility to change the bossbars pattern and the numbers? I would like to use roman numbers instead of the regular ones.

493f94264d2c20eaa6293df60156cee3a04d278b

493f942

Hi, I saw you closed the thread. Does it mean that it will be added with the next update?

Yes, with next update you can use roman numbers to represent playes levels

Yes, with next update you can use roman numbers to represent playes levels

Thank you very much! Now jobs and skills plugin will look similar in the bossbar!

Yes, with next update you can use roman numbers to represent playes levels

I downloaded the latest update and couldn't find how to use Roman numbers. Please help.


Green Tea Leaves Direwolf20 1.19 1.12.0

Green tea leaves in this modpack arent available for some reason. They show up in crafting recipes or matcha latte but not in just enough items and when i try to get them from breaking leaves off trees with a knife from the modpack i dont get any. Not sure if i should be putting this bug report here or for the modpack so im just doing both. Thanks.

Ensure the config has it enabled. That's all the support I can provide. If a bug exists in a minimal environment, I'll investigate.


Move the words about Koalas in workers

In some cases such as apply, transform, apply_batch, or tranform_batch, Koalas still requires to be installed in worker nodes, see https://github.com/databricks/koalas/issues/1826.
This PR removes some wordings about the installation in workers for now, and makes it deferred to future work.

Codecov Report

Merging #1910 (6374e5d) into master (d1747f3) will decrease coverage by 1.80%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1910      +/-   ##
==========================================
- Coverage   93.18%   91.37%   -1.81%
==========================================
  Files          41       41
  Lines       10009     9929      -80
==========================================
- Hits         9327     9073     -254
- Misses        682      856     +174

Impacted Files
Coverage Δ

databricks/koalas/__init__.py
68.75% <0.00%> (-17.19%)
:arrow_down:

databricks/koalas/spark/functions.py
88.88% <0.00%> (-7.41%)
:arrow_down:

databricks/conftest.py
89.83% <0.00%> (-7.28%)
:arrow_down:

databricks/koalas/accessors.py
86.43% <0.00%> (-7.04%)
:arrow_down:

databricks/koalas/namespace.py
78.17% <0.00%> (-6.07%)
:arrow_down:

databricks/koalas/generic.py
88.37% <0.00%> (-4.78%)
:arrow_down:

databricks/koalas/frame.py
93.47% <0.00%> (-3.14%)
:arrow_down:

databricks/koalas/typedef/typehints.py
91.37% <0.00%> (-2.59%)
:arrow_down:

databricks/koalas/utils.py
93.18% <0.00%> (-2.53%)
:arrow_down:

databricks/koalas/testing/utils.py
78.57% <0.00%> (-1.95%)
:arrow_down:

... and 12 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 d1747f3...6374e5d. Read the comment docs.


Probably outdated documentation

In (Graphics.Input & Graphics.Input.Field)'s documentation, there seems to be referring to Signal.Channel a lot, like in the first line here, and actually all over the examples:
http://package.elm-lang.org/packages/elm-lang/core/2.0.1/Graphics-Input
The API definition seems to be correct, though.
Graphics.Input.Field documentation page:
http://package.elm-lang.org/packages/elm-lang/core/2.0.1/Graphics-Input-Field
Unfortunately, I'm not comfortable enough yet with Signal.Message to fix it myself.

The changes would be very mechanical:

Signal.Channel becomes Signal.Mailbox
Signal.channel becomes Signal.mailbox
Signal.subscribe x becomes x.signal
Signal.send x becomes Signal.message x.address

That should be it.

Done with the mechanical steps. If anyone could review again before sending the PR, that'd be nice. Or should I send the PR directly since I've reviewed? (Excuse me, still learning the etiquette)
The new Graphics.Input.elm: https://github.com/hossameldeenfci/core/blob/patch-1/src/Graphics/Input.elm
The new Graphics.Input.Field.elm: https://github.com/hossameldeenfci/core/blob/patch-2/src/Graphics/Input/Field.elm

Looks good, just one change missing, in this line: the Markdown link to send should now probably go to message as well.
I think it's okay to send the PR then.

Edited. Sent the PR.


Use pkg/errors for custom errors and wrapping message

display stackstrace with the verbose flag.

:/ not a fan of implicit "magic" code. The beauty of go is that code is
usually easily understandable even if you're not familiar with a library.
:+1: then
On Wed, May 31, 2017 at 11:59 AM Steve Durrheimer<EMAIL_ADDRESS>wrote:

@sdurrheimer commented on this pull request.
In cmd/promu.go
https://github.com/prometheus/promu/pull/69#discussion_r119318467:

@@ -54,8 +55,7 @@ var Promu = &cobra.Command{
// This is called by main.main(). It only needs to happen once to the rootCmd.
func Execute() {
if err := Promu.Execute(); err != nil {

fmt.Println(err)

Strangely cobra was doing it by itself. Removing this line did fixed the
double error display.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/promu/pull/69#discussion_r119318467, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAANaGviuMH2SmKoNXEUKsGf-thFmsbvks5r_ToXgaJpZM4Nn_Xx
.

I agree, I just didn't found how to prevent cobra from doing it, in that way I could display it myself. I will double check shortly.

@grobie Looks like there is a way to silence the cobra Execute() error printing.

@grobie Updated

Renamed er as printErr


Update to latest logger

Problem
The Alephant Publisher Queue is used by Newbeat which is using an updated CloudWatch logger (the CloudWatch logger now has an updated interface).
Solution
We need to modify Alephant Publisher Queue to use the latest Alephant Logger (as that's what the updated Alephant CloudWatch Logger uses). Then update the metric calls to match the new interface.
Release Plan
I believe this will be a patch release rather than a minor or major (as we're modifying code to fix some other library that has changed).

:cake:


Add support for millisecond formats

I get this stack trace for a valid entry in Exchange:
Date String 9999-12-30T23:59:59.9999999Z not in valid UTC/local format
microsoft.exchange.webservices.data.util.DateTimeParser.parseInternal(DateTimeParser.java:85)
microsoft.exchange.webservices.data.util.DateTimeParser.convertDateTimeStringToDate(DateTimeParser.java:47)
microsoft.exchange.webservices.data.EwsServiceXmlReader.readElementValueAsDateTime(EwsServiceXmlReader.java:128)
microsoft.exchange.webservices.data.GetPasswordExpirationDateResponse.readElementsFromXml(GetPasswordExpirationDateResponse.java:32)
microsoft.exchange.webservices.data.ServiceResponse.loadFromXml(ServiceResponse.java:109)
microsoft.exchange.webservices.data.GetPasswordExpirationDateRequest.parseResponse(GetPasswordExpirationDateRequest.java:61)
microsoft.exchange.webservices.data.ServiceRequestBase.readResponse(ServiceRequestBase.java:388)
microsoft.exchange.webservices.data.SimpleServiceRequestBase.readResponse(SimpleServiceRequestBase.java:163)
microsoft.exchange.webservices.data.SimpleServiceRequestBase.internalExecute(SimpleServiceRequestBase.java:47)
microsoft.exchange.webservices.data.GetPasswordExpirationDateRequest.execute(GetPasswordExpirationDateRequest.java:80)
microsoft.exchange.webservices.data.ExchangeService.getPasswordExpirationDate(ExchangeService.java:1622)

This would be nice. I've got a program that relies on modified times to sync items, but I've noticed that EWS only transmits down to seconds, not hundredths or milliseconds. I don't know if its the fault of EWS itself, or the ews-java-api. But if milliseconds come over the wire, it'd be nice to include them. As it is, I need to do a best guess to the closest second check :/

This got broken when they moved from java date formatters to joda ones. I think they need to add the millisecond one here: https://github.com/OfficeDev/ews-java-api/blob/cf42b78594fa7f4aa2b70bf2f9c17801f8feead3/src/main/java/microsoft/exchange/webservices/data/util/DateTimeParser.java#L24
DateTimeFormat.forPattern("yyyy-MM-dd'T'HH:mm:ss.SSSZ").withZoneUTC(),

The string in question looks to be a bit in the future? (9999-12-30T23:59:59.9999999Z) is it correct or are there other bugs as well?

Yes that's a valid entry in Exchange when you set password expiry date to inifnite/max value/never expire. In anycase, that's a legal date time value (and the max that can be represented).

But ofcourse you can repro this bug with vanilla 2014-12-30T23:59:59.9999999Z


Add slate-lists

Adds basic support for lists.
Includes:

schema
enter on blank line unwraps the list

Todo:

nested lists

Just updated to include support for sub lists. It's still a little buggy and needs some cleanup and updated tests.


Update Composer installation

Use multi-stage builds https://docs.docker.com/develop/develop-images/multistage-build/ (needs Docker >=17.05)
Use Composer v2

Thank you very much for the report and your support.


Verbosity level

What
Deploy limitador with specific verbosity level
Currently, only verbosity level 1 to 4 (both included) are allowed. Any verbosity level out of that range should be rejected
apiVersion: limitador.kuadrant.io/v1alpha1
kind: Limitador
metadata:
  name: limitador-sample
spec:
  verbosity: 2

Verification Steps
dev setup
make local-setup

Deploy the limitador CR with verbosity level set to 2
k apply -f - <<EOF
---
apiVersion: limitador.kuadrant.io/v1alpha1
kind: Limitador
metadata:
  name: limitador-sample
spec:
  verbosity: 2
EOF

Check deployment is correct
kubectl wait --timeout=300s --for=condition=Ready limitador limitador-sample

Should return
limitador.limitador.kuadrant.io/limitador-sample condition met

Check command line
kubectl get deployment/limitador-limitador-sample  -o yaml | yq '.spec.template.spec.containers[0].command'

should look like this
- limitador-server
- -vv
- --http-port
- "8080"
- --rls-port
- "8081"
- /home/limitador/etc/limitador-config.yaml
- memory

Note: -vv has been added to the command line

Codecov Report

Merging #119 (e7b65ab) into main (f6a01e8) will decrease coverage by 2.26%.
The diff coverage is 100.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #119      +/-   ##
==========================================
- Coverage   68.62%   66.37%   -2.26%
==========================================
  Files          16       14       -2
  Lines        1157      794     -363
==========================================
- Hits          794      527     -267
+ Misses        324      256      -68
+ Partials       39       11      -28

Flag
Coverage Δ

integration
?

unit
66.37% <100.00%> (+0.12%)
:arrow_up:

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

Components
Coverage Δ

api/v1alpha1 (u)
100.00% <ø> (ø)

pkg/helpers (u)
∅ <ø> (∅)

pkg/log (u)
31.81% <ø> (ø)

pkg/reconcilers (u)
36.76% <ø> (ø)

pkg/limitador (u)
88.88% <100.00%> (+0.09%)
:arrow_up:

controllers (i)
∅ <ø> (∅)

Files
Coverage Δ

api/v1alpha1/limitador_types.go
100.00% <ø> (ø)

pkg/limitador/deployment_options.go
93.61% <100.00%> (+0.43%)
:arrow_up:

... and 2 files with indirect coverage changes

@Kuadrant/engineering ready for review!


Moving tweet searches and geocodings to org owner in case of user deletion

@Kartones could you please CR this?

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

:+1:


Didn't this use a document?

Didn't this use a document?
What parameters are required for sending positioning?
How to display team members in the local map?
Is there a backend management interface?

Didn't this use a document?
There is no documentation. Only the code

What parameters are required for sending positioning?
See request.form in https://github.com/luka5/livetracking/blob/main/app.py#L41-L55

How to display team members in the local map?
Anyone who sends data with a unique name will be shown on the map

Is there a backend management interface?
No storage, no management interface. Just a MVP.

I don't know why, it's not displayed on the phone, but on the web

(myenv) locus@locus:~/livetracking$ python app.py

Serving Flask app 'app'
Debug mode: on
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
Running on all addresses (<IP_ADDRESS>)
Running on http://<IP_ADDRESS>:5000
Running on http://<IP_ADDRESS>:5000
Press CTRL+C to quit
Restarting with stat
Debugger is active!
 Please see https://github.com/luka5/livetracking/blob/main/app.py#L40 You need to set /api/v1/track with POST :)

(myenv) locus@locus:~/livetracking$ python app.py

Serving Flask app 'app'
Debug mode: on
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
Running on all addresses (<IP_ADDRESS>)
Running on http://<IP_ADDRESS>:5000
Running on http://<IP_ADDRESS>:5000
Press CTRL+C to quit
Restarting with stat
Debugger is active!
Debugger PIN: 272-882-707
<IP_ADDRESS> - - [12/Sep/2023 12:04:09] "POST /api/v1/track HTTP/1.1" 500 -
Traceback (most recent call last):
File "/home/locus/myenv/lib/python3.8/site-packages/flask/app.py", line 2213, in call
return self.wsgi_app(environ, start_response)
File "/home/locus/myenv/lib/python3.8/site-packages/flask/app.py", line 2193, in wsgi_app
response = self.handle_exception(e)
File "/home/locus/myenv/lib/python3.8/site-packages/flask/app.py", line 2190, in wsgi_app
response = self.full_dispatch_request()
File "/home/locus/myenv/lib/python3.8/site-packages/flask/app.py", line 1486, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/locus/myenv/lib/python3.8/site-packages/flask/app.py", line 1484, in full_dispatch_request
rv = self.dispatch_request()
File "/home/locus/myenv/lib/python3.8/site-packages/flask/app.py", line 1469, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
File "/home/locus/livetracking/app.py", line 42, in api_upload
time = datetime.fromtimestamp(int(request.form.get('time')))
ValueError: invalid literal for int() with base 10: '20-04-09'

There are new problems again. It seems that the error is due to a time issue. Locus Map, how to set the request parameters here
I set it this way, why did the error occur
http://<IP_ADDRESS>:5000/api/v1/track
lat =
lon =
alt = {m}
speed = {m/s}
battery = {%}
gsm_signal = {%}
name = qqq123
time = HH-mm-ss

time = {s} works as expected.
http://$IP:5000/api/v1/track
lat =
lon =
alt = {m}
speed = {m/s}
battery = {%}
gsm_signal = {%}
name = ......
time = {s}

Great, finally displayed on the webpage
How to display team members with shared locations in Locus Map software

<IP_ADDRESS> - - [12/Sep/2023 13:58:17] "GET /leaflet-gpx/pin-shadow.png HTTP/1.1" 304 -
<IP_ADDRESS> - - [12/Sep/2023 13:58:17] "GET /leaflet-gpx/pin-icon-end.png HTTP/1.1" 304 -
<IP_ADDRESS> - - [12/Sep/2023 13:58:17] "GET /leaflet-gpx/pin-icon-start.png HTTP/1.1" 304 -
<IP_ADDRESS> - - [12/Sep/2023 13:58:44] "POST /api/v1/track HTTP/1.1" 200 -


Update files silently (without opening them)

It works great and again a big thanks for that!
 If you refactor >20 files, it's a bit distracting.
Could we have some setting (or a separate command), to save all changes silently, without opening the files?

For now I'd rather not, as there are potential bugs that that would hide (see #2), so I'd like a bit of enforced verification that things are reasonable. In the future as this becomes more stable this might happen. That being said, I believe replace in the search viewlet does the same thing and I don't think there's an option to disable it (I could be wrong there).

Just a remark on search viewlet's behaviour:
It makes sense there, because otherwise user can't see each occurance anywhere. But in case of your extension user has already checked the occurrences and changed only what he wanted... so there's no need for double checking.
I understand it's not there because of possible bugs, but maybe you could let user do decide... at least in the near future as you've said.
I really use this feature a lot and I have never encountered any errors though.
Plus it's easier to check if changes are correct using git diff tool, than checking 10+ files manually in vscode.

Any chance you could add this as an optional setting with a severe warning that it might produce errors and that it is the responsibility of the user if they toggle it on?

Isn't this fixed already? The files do not open for me when I run the command.


Suggestion: Replace "+" signs on character tab with magnifying glass

The character sheet generally uses a magnifying glass to denote compendium search, except for the character tab, where the selection is denoted with a plus sign. This leads to confusion among new players: they are subconsciously prepared to click plus everywhere else, but the system expects them to click the magnifying glass.
It's a minor issue, but replacing the pluses with magnifying glasses will make it slightly more intuitive and consistent

Try updating your system install.

Ah, I see in the changelog, it has actually been implemented. The question being closed as "not planned" misled me for a moment. Nevermind then, thanks!


Moved setScreenName to the main thread on iOS

I ran into an issue where setScreenName was working on Android but not iOS. The FIRAnalytics documentation mentioned that setScreenName must be called on the main thread, so I moved the call to the main thread. Now setScreenName appears to be working on iOS.

I see now that you guys are already working on fixing this as well as updating the FIRAnalytics lib.


hints about empty strings/lists

I noticed that things like x ++ [] were already detected by hlint, but x ++ "" wasn't. So I went through the hints file and tried to add all meaningful variants of hints on empty strings/lists where one variant was "missing".
I actually didn't add all. In https://github.com/ndmitchell/hlint/blob/a62a3b56d7e76715633d266939f40ac9b2e94301/data/hlint.yaml#L629 there would have been altogether three variants to add.
Likewise in https://github.com/ndmitchell/hlint/blob/a62a3b56d7e76715633d266939f40ac9b2e94301/data/hlint.yaml#L834
In the latter case, I actually wondered (independently of the matter of strings vs. lists) why there aren't hints firing on zip [] x and zip x [] (instead of just on zip [] []).

Thanks for the patch. I've applied some of these (as a separate patch), but not all:

Things like anyM on "" seem super unlikely. I know someone could technically do it, but I doubt it crops up in reality.
Lots of people use overloaded strings, meaning "" isn't quite equivalent to [] - that means that null x and x == "" don't do the same thing in many cases.

I've pushed a subset in 8ccf7eb17cd5548e425a4830cdd498ed644a8b61. Let me know if you think any of the ones I've missed might still be useful.


How to zoom to fit automatically

Hey,
I'm exploring using Blazor.Diagrams for rendering a read-only tree view in my app.
I've seen the code (and demos) for using GraphShape to automatically arrange nodes, plus the ZoomToFit method, to get everything lined up and visible.
My question is, is there a way to do this without any user interaction.
Rather than have a user click a button to arrange and zoom the diagram, ideally I'd want that to happen automatically.
So my code would:

Create the diagram
Add nodes, ports, links
Auto-layout and zoom to fit

All without any user interaction.
Is that possible?
Thanks!

Hello,

Do you know the size of your nodes beforehand?
Are you going to be using ports or direct links between nodes?

If you're using ports, do you know their size and positions beforehand and without CSS?

Hi,
I have the same question, did you find a solution?
Thanks,
Dilan

Still having issues with this when trying to ZoomToFit with SVG nodes.

Hi,
I have the same question. Any update on that issue?
Thanks
Marcel


Lock export settings after starting the workload

While you're exporting, it's currently possible to toggle the overlay options and cause some of your frames to show game video and some not show game video. Making this option locked after you start the encode seems like it wouldn't be a hard feature to add, and prevent any accidental clicks from messing up any progress.

Yes, this is a good proposal, I'll envision trdrop to be also an "exploratory" tool as well, that's why I kept everything modifiable. But making such a "lock" should be easily done.


docs: add commands to install Vite inside an existing folder

Description
The Getting Started guide lists commands to install Vite, but all the listed commands install Vite inside a new folder created during installation.
The guide is missing the commands for installing Vite inside an existing folder. I am adding them to help users who may not know the commands, to help reduce confusion and provide clarity.

Thanks for the PR, however we had already received another PR for this: https://github.com/vitejs/vite/pull/16321

Thank you!


Issue with node multiples handles connections

What platform were you using when you found the bug?

React Flow / Svelte Flow version: @xyflow/react 12.0.3
Browser and version: Google Chrome 126
OS and version: macOS Sonoma 14.5

Live code example
No response
Describe the Bug
When starting a connection between 2 nodes and not finishing it, an edge is created for the first handle when making a second connection from the same node but on a different handle.
I'm trying to understand what I could be doing wrong to have this issue
Steps to reproduce the bug or issue
I don't manage to reproduce the issue in a code sandbox, but it goes like this:

Create a node with multiple source handles
Try to link the first handle to another node, but stop before finishing the connection
2 edges are created when only 1 should have been

Expected behavior
As a user, I expect the first edge to not appears when making the second connection
Screenshots or Videos
https://github.com/user-attachments/assets/3d62abbe-46ff-4f12-9334-7164af0246ab
Additional context
I made some validation check through the isValidConnection props, but since the handles act as the connection is valid it doesn't seem to come from there

I believe this issue is fixed in 12.0.4, can you try upgrading and checking if the issue persists?

Thanks for the fast answer, I will try to upgrade 👍

I upgraded, and it's indeed working as expected, thanks for the support


GetSessionAndUserError with Nuxt-auth using typeorm and synchronize: false

Environment

Operating System: Darwin
Node Version:     v18.16.0
Nuxt Version:     3.6.1
Nitro Version:    2.5.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      vite, css, app, auth, modules, runtimeConfig
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
No response
Describe the bug
Hello,
I'm using Nuxt-Auth last stable version with TypeORMLegacyAdapter and my relational database.
Everything is working fine with "synchronize: true" in my adapter settings.
But whenever I put "synchronize: false" instead of "synchronize: true", I'm getting a "GetSessionAndUserError" and "https://next-auth.js.org/errors#session_error metadata.findEmbeddedWithPropertyPath is not a function TypeError: metadata.findEmbeddedWithPropertyPath is not a function".
I does not seem to come from my database: I switched from mysql to postgres and it is not working either.
Any idea why I get this annoying error preventing me to deploy to production?
Thanks a lot for your help!
Samuel
Additional context
No response
Logs
[next-auth][error][SESSION_ERROR]                                                                            12:08:13
https://next-auth.js.org/errors#session_error metadata.findEmbeddedWithPropertyPath is not a function TypeError: metadata.findEmbeddedWithPropertyPath is not a function
    at /Users/***/Sites/vuejs/***/node_modules/typeorm/query-builder/SelectQueryBuilder.js:2112:36
    at Array.forEach (<anonymous>)
    at SelectQueryBuilder.buildRelations (/Users/Samuel/Sites/vuejs/immocarto/node_modules/typeorm/query-builder/SelectQueryBuilder.js:2107:32)
    at SelectQueryBuilder.applyFindOptions (/Users/Samuel/Sites/vuejs/immocarto/node_modules/typeorm/query-builder/SelectQueryBuilder.js:1626:22)
    at SelectQueryBuilder.setFindOptions (/Users/Samuel/Sites/vuejs/immocarto/node_modules/typeorm/query-builder/SelectQueryBuilder.js:69:14)
    at EntityManager.findOne (/Users/***/Sites/vuejs/***/node_modules/typeorm/entity-manager/EntityManager.js:543:14)
    at getSessionAndUser (/Users/***/Sites/vuejs/***/node_modules/@next-auth/typeorm-legacy-adapter/dist/index.js:348:44)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  name: 'GetSessionAndUserError',
  code: undefined
}

Hi @SamG92,
I sadly cannot help you much with this issue, as it fully results from NextAuth. If you are still planing on continuing the investigation, please reach out to the NextAuth team and see if they can support you. I am sorry that I cannot be much of help here.


Add job to create/build artifact

PR adds a GitHub action to make the artifact being built downloadable

We needed to archive the build so that we could perform a diffoscope (for yesterday's deliverable)


[AutoPR mariadb/resource-manager] fix Go SDK package path for mariadb stable release

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5298

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/4191


feat: Added New Rating component (basic)

I added a basic rating component!
There are below functions.

Size ('sm' | 'md' | 'lg' )
rating (star numbers)
add text beside
add amount of reviews and link

"Advanced rating", "Score rating", "Rating comment" and "Review content" functions seems difficult and have not been implemented yet.
↓Demos
https://user-images.githubusercontent.com/56023847/206466621-62c4650f-eae5-46eb-8e46-80b4230e2295.mov

LGTM


Check compatibility with windows

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.02%) to 94.037%

Totals

Change from base Build<PHONE_NUMBER>:
-2.02%

Covered Lines:
757

Relevant Lines:
805

💛  - Coveralls


[Deangular] Tile map and region map

OpenSearch Dashboards is targeting remove angularJS package by the od 2.11 (11/5) for security concerns. There are two maps that still depends on angularJS.

Remove angular-sanitize from tile map plugin
Clean out opensearch_dashboards_legacy usages in tile map and region map

I see a TODO in tile map and think we should investigate and prepare early.
// TODO: Determine why visualizations don't populate without this
import 'angular-sanitize';

@vamshin could you take a look and assign this task to someone? Thank you.


[Mobile] No cursor is showing after typing

Issue using Android (both physical and emulator)
The cursor is simply disappearing after I start typing as shown in the attached video clip.
It happens since I'm calling setState when that text is changing, since I need to manipulate the layout when a specific text change happened.
_quillController.addListener(() {
 setState(() {});
}

The users can't know where they are, which is of course annoying.
How do I work around it?
https://user-images.githubusercontent.com/16115860/198979384-7333162d-c35b-4db8-9059-f7febe08f1f3.mp4

Thank you for the report, this issue has been open for a while and since there are no interactions with it, we had to close it
but if you still facing this issue, or other issues or you have any other questions, feel free to contact us anytime you want.


Revert "update requirements.txt"

Reverts zy7y/dfs-generate#39

(base) ➜  dfs-generate git:(master) ✗ pip install -r requirements-build.txt
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
ERROR: Could not find a version that satisfies the requirement python_version>=3.8 (from versions: 0.0.2)
ERROR: No matching distribution found for python_version>=3.8


Render fails when referneces but no citatoins

An error showed up when I tried to render in pdf with no citations in the text (i.e., an empty ref list). Although it shoul'dnt happen quite often, it would be nice to not have it
ERROR:
compilation failed- error
LaTeX Error: Something's wrong--perhaps a missing \item.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...

l.186 \end{CSLReferences}

see manuscript.log for more information.

Or a more explicit error message, like : "can't build a reference with no citations in the text. Remove the reference building function or add a citation"

Version 3.2.1 fixed the problem, I think. It removes the #refs div and the "References" heading if no citations are found.


"Creator" role is still needed for the user who is trying to trigger the YAML pipeline when the environment doesn't exist

In the doc for the "Creator" permission role it says "Not applicable for environments auto created from YAML pipeline."
However according to my test, the "Creator" role is still needed for the user who is trying to trigger the YAML pipeline when the environment doesn't exist. Otherwise the environment cannot be automatically created and there will be an error showing like "Environment xxx could not be found. The environment does not exist or has not been authorized for use."

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

ID: 77d95db6-9983-7346-d0eb-4b7443e4e252
Version Independent ID: 0a22cccc-318d-592f-d1ab-09ec01d88087
Content: Create target environment - Azure Pipelines
Content Source: docs/pipelines/process/environments.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

Thanks @mszixie! I'll update the documentation today.


Adds ProxyListener to Infra IR

Introduces the ProxyListener type that describes the listener(s) of the managed proxy infra. This will allow the Infra Manager to perform incremental updates of Kube Services whenever a Gateway address or listener is updated.
xref: #180
Signed-off-by: danehans<EMAIL_ADDRESS>

Codecov Report

Merging #181 (ae61d22) into main (e20d7ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #181   +/-   ##
=======================================
  Coverage   61.74%   61.74%
=======================================
  Files          20       20
  Lines        1814     1814
=======================================
  Hits         1120     1120
  Misses        632      632
  Partials       62       62

Help us with your feedback. Take ten seconds to tell us how you rate us.


net: l2: ieee802154: mgmt: allow beacons without assiciation bit

The Association permit bit shall be set to zero if the coordinator does not accept association requests.
Not accepting association request ist not a reason to filter the beacons from this coordinator during network scan. It is still a network, just one you cannot associate with.

Thanks, Fabian, for this PR. I think you're right, that even those networks should reported that one cannot associate to. But then it is not enough to just not drop them. I think we should at least:

Report the flag in the shell, see https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/l2/ieee802154/ieee802154_shell.c#L216
Update the corresponding unit test to ensure the flag is properly reported. You should test once with and once w/o the flag set. You can expand the test_scan unit test in ieee802154_shell_test.c but please don't just duplicate the test but keep it DRY. If you're on it, you could also test with and w/o beacon payload to ensure that your new feature is also fully covered.

* Report the flag in the shell, see https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/l2/ieee802154/ieee802154_shell.c#L216

Except, that this is not part of the shell, but part of the ieee802154 management layer. To report it in the shell, you would need to copy the bit to the scan context and read out the scan context from the shell.
I could log the information, but it would probably be best if this is DEBUG log level because it is not needed normally and will clutter the log.
With #76190 in mind, you could replace the payload field with a pointer to the pkg, so that the notified layers could access all information from the package, but then you probably don't need most other fields in the ieee802154_req_params struct and would have to do a major rewrite.
What is the way you want to go with it?

Except, that this is not part of the shell, but part of the ieee802154 management layer. To report it in the shell, you would need to copy the bit to the scan context and read out the scan context from the shell.

Yes, that's what I had in mind, similarly to what you did with the beacon payload.
Probably this pattern doesn't scale well in the long run as a lot more fields may be added in the future. But let's not overthink it for now as I'll be able to refactor that scanning process once it's getting out of hand.

you could replace the payload field with a pointer to the pkg

No, I wouldn't do that because it would require clients to know too much about the internal structure of packages which would break encapsulation.

@rlubos Could you give this a second look to see whether it could be merged?

@aescolar is there a reason my tests were cancelled?

Sorry for that: https://discord.com/channels/720317445772017664/733037890514321419/1267759879460753438

Sorry for that

Np. tests manually restarted. Thanks for scheduling the fix.


Update headset to 1.5.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as c7c2552267ca166e9a4b96de5c5a1147cc0676c5. Your contribution is still credited to you.


[release-1.25] Update helm chart rolebinding to use events.k8s.io

This will publish a new helm chart when it merges
Fixes https://github.com/kubernetes-sigs/descheduler/issues/986
Fixes #959

/hold

/approve

/hold cancel

/lgtm


Multi-target support

Hey, from my perspective we need to move a elastic connection string configuration from a Helm release parameters configuration to the separate CDR. For example, this CDR should have a next name Cluster. After that, we can use the following approach, all CDRs related to elastic object creation need to include a new option with the name a Cluster configuration.

@HryhoriiDidenko thanks for the idea, it will help with separating the operator and target ES/Kibana configuration. I will try it out and see if it's feasible, but so far, I don't see any issue.

@xco-sk Hey, think we need to stay available for connection string configuration from Helm release parameters, as default. It is needed for backward compatibility. But if we want to use a different cluster we need to create a new CDR with a connection string and point this CDR to specific resources.

@xco-sk Do you have some README on how to start developing your service?

Hi @HryhoriiDidenko, sorry, no README about developing yet, I should create one. But essentially, all resources are scaffolded with kubebuilder. I will write at least a few points on how to develop new CRDs and what/where to implement the logic behind them.

any idea when this might be tested and merged in?  it would be a very useful feature.  i have mutliple elasticsearch clusters, and it would be great to be able use these custom resources for all of them.

Hi @georambo, the implementation is in progress. Sorry, it takes so long, I underestimated the number of changes needed (e.g. the resource delete in ES controllers has to be refactored to the "finalizers" style, same as we got in Kibana controllers). Will keep you posted here, thanks for the patience :-)

Hi @georambo, the implementation is in progress. Sorry, it takes so long, I underestimated the number of changes needed (e.g. the resource delete in ES controllers has to be refactored to the "finalizers" style, same as we got in Kibana controllers). Will keep you posted here, thanks for the patience :-)

No worries, I appreciate the effort on this operator, and it's very useful.

I'm finalizing the implementation and testing of the feature, so in the next couple of days, the version with multi-target support will be released if no major issue appears.

The multi-target support is now implemented in v0.5.0, if you use helm, please run helm repo update beforehand to get the latest helm chart. The migration guide is present in the README.
There is also detailed documentation of 2 new CRDs present, see ElasticsearchInstance and KibanaInstance. See also updated documentation of other resources with a description of new spec.targetInstance.name field.
The change is backward compatible - when the field is not present, the default configuration (operator config( is being used.
Please let me know if there is an issue or if help is needed.

works like a charm.  great stuff. thank you.


Exception: wasm operand stack overflow ?

Steps to reproduce
Trying to execute a QuickJS engine with WAMR.
qjs.txt
The qjs.wasm is uploaded as qjs.txt.
three mode:
（1）interpreter : iwasm qjs.wasm
（2）JIT: cd JITbuild  and iwasm qjs.wasm
（3）AOT: wamrc -o qjs-wamr.aot qjs.wasm and iwasm qjs-wamr.aot
Expected result
Successfully execute the qjs.wasm in all the three mode and print:
"QuickJS - Type "\h" for help
qjs > ^C"
Actual result
（2）and （3）could successfully execute, but （1）got some problem with the output:
Exception: wasm operand stack overflow
Environment
macOS or ubuntu both got the problem
WAMR 18-05-2022

Hi, wasm operand stack overflow was thrown due to not enough stack size, please use iwasm --stack-size=n to enlarge it, for example:
iwasm --stack-size=102400 qjs.wasm

Thanks a lot !


Fix typo and else

Fixed an additional letter caused by saving the file using shortcuts, lol.
Maybe I'll find something else I can contribute

@krbrs did you manage to find "something else" to contribute?

Nothing yet - I'll convert the PR for the typo


Is the AccountData compatible with Instance?

The system module require an AccountData and the balances module require a StoreMap.
But if I've 2 balances, how to configure the runtime?

Also the DustLost should trigger by both of the 2 balances' total < ED. Any elegant way to achive this?

First note that pallet_balance can also not make use of AccountData and use a dedicated storage map though performance won't be as good (see the file frame/balances/src/tests_local.rs )
For now I don't see how it is possible to use AccountData for multiple module easily,
you can still implement StoredMap trait for each balance by hand on a new type I think:
struct StoredMapAccoundDataForBalance1;
impl StoredMap<AccountId, AccountData<Balance1>> for StoredMapAccountDataForBalance1 {
// Implement functions by calling the frame_system stored map
}

But this is just a suggestion I'm not sure if it will works


Update dotnet-core.yml

Added types to pull_requests, so they should trigger cleanup of PR created Azure Static Site.

Codecov Report

Merging #3 into main will increase coverage by 0.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
+ Coverage   98.45%   98.80%   +0.35%
==========================================
  Files          70       70
  Lines        2857     2857
  Branches      244      244
==========================================
+ Hits         2813     2823      +10
+ Misses         27       19       -8
+ Partials       17       15       -2

Impacted Files
Coverage Δ

...tor/Identifiers/InterfaceResponseTypeIdentifier.cs
97.82% <0.00%> (+21.73%)
:arrow_up:

Continue to review full report at Codecov.

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


Arbitrary waveform in ASG generates unexpected waveform

I am trying to output a custom, periodic signal using the ASG. As a test, I want to output a ramp between -500 mV and 500 mV. Looping OUT1 to IN1 and running the attached test script, I get this unexpected waveform:

from pyrpl import Pyrpl
from pyrpl.async_utils import sleep
import numpy as np
import time
import matplotlib.pyplot as plt

self=Pyrpl(config='testing',hostname="<IP_ADDRESS>")
self.scope=self.rp.scope    # oscilloscope (signal acquisition class)
self.asg=self.rp.asg0       # arbitrary signal generator class

self.fsweep=5000 # Frequency of repetition of the ramp
self.asg.output_direct = "off" # Turn asg off
self.scope.input1='in1'
self.scope.average=True # "Enables averaging during decimation if set to True"

# Set acquisition parameters: https://redpitaya.readthedocs.io/en/latest/appsFeatures/examples/acqRF-exm1.html
decimation=8
sampleClock=125e6
buffSize=2**14
self.scope.decimation = decimation
self.fs=sampleClock/decimation  # sampling frequency
self.n=(int)(self.fs/self.fsweep)      # number of datapoints per ramp
self.buffTime=buffSize/self.fs # Max acquisition time

# Configure trigger
# trigger on the input signal positive slope
self.scope.trigger_source = 'asg0'
self.scope.trigger_delay = self.buffTime/2
self.scope.threshold = 0
self.scope.hysteresis = 0.01

# Setup arbitrary signal generator: waveform='halframp'
waveform=np.linspace(-0.5,0.5,self.n)
self.asg.data=waveform
#self.asg.setup(frequency=self.fsweep, amplitude=0.1, offset=0, waveform='halframp', trigger_source='immediately') # This works
self.asg.output_direct = "out1"

# Acquire and plot data
ch1,ch2 = self.scope.curve()
plt.plot(ch1)
plt.show()

I have tried for 10 hours to understand asg.py, using the information from #335, but still I wasn't able to find a way to set up a custom waveform for the ASG.
Is there a bug or am I missing something?

Here is an example how to do this:
from pyrpl import Pyrpl
from pyrpl.async_utils import sleep
import numpy as np
import time
%matplotlib inline
import matplotlib.pyplot as plt

p = Pyrpl(config='', hostname="rp", gui=False)
asg = p.rp.asg0
scope = p.rp.scope

# user constants
fsweep = 5000 # Frequency of repetition of the ramp
decimation = 8
sampleClock =125e6
buffSize = asg.data_length  # 2**14
fs = sampleClock/decimation  # sampling frequency
buffTime = buffSize / fs  # Max acquisition time
n = (int)(fs / fsweep)  # number of datapoints per ramp

scope.setup(
    input1='asg0',  # can directly look at asg signal, no need to output it (though you could)
    average=True,
    duration=0.001, # another way to specify decimation indirectly by the total trace duration
    # the asg generates a digital trigger signal when it crosses index=0 of its waveform, which we trigger on with the asg0-setting
    trigger_source='asg0',
    # trigger_delay is not needed, since we start acquisition when the signal starts (i.e. trigger_delay=0)
    # trigger_delay = self.buffTime/2
    # the settings dont matter because trigger_source is not "ch1_positive_edge"
    # threshold=0,
    # hysteresis=0.01,
)

# set asg to something harmless - DC with 0 volts
asg.setup(
    output_direct='off',
    frequency=fsweep,  # repetition rate of the waveform (assuming 2**14 points)
    amplitude=1,  # amplitude = 1 => custom waveform gets multiplied by unity on the FPGA
    offset=0,  # no offset, so we faithfully reproduce the waveform
    waveform='dc',  # choose DC, so the waveform is zero to start with
    trigger_source='immediately',  # I think mostly this setting was missing in your example -> asg never started
)

# replace asg data with custom waveform
waveform = np.linspace(-0.5, 0.5, n)
asg.data = waveform
# important: n is only slightly larger than 3000 with above parameters
# this means we will not fill the buffer of 2**14 points, and the rest of the waveform will be zero.
# it is unclear what you want - you should be clear on this, as there are many "hidden" settings in the
# asg that might enable you do do that

# if you want to switch on the analog signal
#asg.output_direct = "out1"

# Acquire and plot data
ch1, ch2 = scope.curve()
times = scope.times
plt.plot(times, ch1)
plt.show()

I know the waveform I generated is likely not what you want, but you have not really told me. The issue I a having comes from n being less than 2**14, i.e. not filling the entire buffer.
One way would be to stretch your waveform to fill the entire buffer (change n to 2**14 in above example). This is the best solution most of the time, as it gives you the largest interpolation grid (good phase resolution) for outputting the desired waveform.
Another option, if you really have to use 3125 or so points, is to modify the asg such that it only outputs the first 3125 points of its buffer, and then wraps back to the start. Internally, the asg has a counter of 30 bits, and at each clock cycle it adds _counter_step to this value. It then takes the highest 14 bits of this counter as the index of your waveform to output. You can specify

a custom value _counter_wrap where this counter will start over from zero (by default at 2**16 * 2**14 - 1),
the counter step _counter_step (indirectly encoding your signal frequency),
with _sm_wrappointer, whether after wrapping, the counter should start at zero (False), or take into account the accumulated counter offset (i.e. just subtract _counter_wrap from the counter when its time to wrap it). This is an important distinction when _counter_step / _counter_wrap is not integer. By default, _sm_wrappointer=True.

Thanks a lot @lneuhaus for the detailed answer!
I was able to output a custom, periodic signal of length n by setting the counter wrap accordingly:
asg._counter_wrap=n*2**16

I hope this helps other users setting up the ASG. Maybe a link to this issue in the API manual would also be useful!


Add resolve(run, node, parent) to BlueTestResultFactory

Description
See JENKINS-XXXXX.
Submitter checklist

[ ] Link to JIRA ticket in description, if appropriate.
[ ] Change is code complete and matches issue description
[ ] Appropriate unit or acceptance tests or explanation to why this change has no tests
[ ] Reviewer's manual test instructions provided in PR description. See Reviewer's first task below.
[ ] Ran Acceptance Test Harness against PR changes.

Reviewer checklist

[ ] Run the changes and verified the change matches the issue description
[ ] Reviewed the code
[ ] Verified that the appropriate tests have been written or valid explanation given

@jenkinsci/code-reviewers @reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Error Communication Link Failure

System information:

MacOS big Sur 11.4
DBeaver 21.1.1

Connection specification:

Mysql 5
dbeaver.io/files/jdbc
SSH

Describe the problem you're observing:
I keep on receiving error
SQL Error [08S01]: Communications link failure¶¶The last packet successfully received from the server was 351,120 milliseconds ago.  The last packet sent successfully to the server was 42,900 milliseconds ago.
Steps to reproduce, if exist:
I able login but after awhile when i want to execute query , it will come out that error.
I need to invalidate it or disconnect which gonna took awhile , then only i able to execute the query.
It will keep on repeating each day.
Include any warning/errors/backtraces from the logs

hi @noorsyamiera92 ,
please try to set keep-alive interval in connectionproperties

I already put 10000, but its still the same.
I keep on receiving communication link failure.
On Thu, Jun 24, 2021, 4:52 PM Dziyana @.***> wrote:

hi @noorsyamiera92 https://github.com/noorsyamiera92 ,
please try to set keep-alive interval in connectionproperties
[image: image]
https://user-images.githubusercontent.com/31996417/123233269-97d5ca00-d4e2-11eb-99a0-3554ef5b475a.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/12964#issuecomment-867461732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJXMMIGOO5RP744X3FBUCALTULW5DANCNFSM47GZT3GA
.

@noorsyamiera92 you should put it to a lower value, not higher. Like 60.
At 10000 it's probably too late to keep the collection alive.


@azure/communication-common Azure Core 2.0 Migration

Packages impacted by this PR

@azure/communication-common
and once migrated, transitively its dependencies

Issues associated with this PR

#20056
#15594

Describe the problem that is addressed by this PR

https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/core/core-rest-pipeline/documentation/core2.md

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/core/core-rest-pipeline/documentation/core2.md

Are there test cases added in this PR?

[x] Yes

Provide a list of related PRs (if any)

#19043
#17045

Checklists

[x] Added impacted package name to the issue description
[x] Does this PR needs any fixes in the SDK Generator? NO
[x] Added a changelog (if necessary)

Changes

old policy preserved to maintain the backward compatibility and allow gradual migration of the ACS libraries and moved to /src/credential/auth-policy-v1/
new policy created in /src/credential/auth-policy-v2/ (based on @azure/core-rest-pipeline)
reduced the number of references to @azure/core-http to minimum (enable easier future removal of the dependency)
removed circular dependencies (detected by npx madge --circular --extensions ts ./)
removed SubtleCrypto & related shims

Migration guide for ACS modalities

createCommunicationAuthPolicy -> createCommunicationAuthenticationPolicy
createCommunicationAuthenticationPolicy -> createCommunicationAuthenticationPolicy

// Old code
const authPolicy = createCommunicationAuthPolicy(credential);
const pipeline = createPipelineFromOptions(internalPipelineOptions, authPolicy);
this.client = new IdentityRestClient(url, pipeline).communicationIdentity;

// New code
this.client = new IdentityRestClient(url, { endpoint: url, ...internalPipelineOptions });
const authPolicy = createCommunicationAuthenticationPolicy(credential);
this.client.pipeline.addPolicy(authPolicy);

API changes have been detected in @azure/communication-common. You can review API changes here
API changes
+ createCommunicationAuthenticationPolicy: (credential: KeyCredential | TokenCredential) => PipelinePolicy
+ export declare function createCommunicationKeyCredentialPolicy(credential: KeyCredential): PipelinePolicy;

API changes have been detected in @azure/communication-common. You can review API changes here
API changes
+ export declare function createCommunicationAuthenticationPolicy(credential: KeyCredential | TokenCredential): PipelinePolicy;
+ export declare function createCommunicationKeyCredentialPolicy(credential: KeyCredential): PipelinePolicy;

The PR contains a new version of the auth policy that is used by several ACS modalities (SMS, ShortCodes, NetworkTraversal, Identity, PhoneNumbers). To preserve the backward compatibility and allow gradual onboarding by the aforementioned modalities, I'm keeping both the old and the new version of the policy. To avoid naming collisions while not having to suffix the new one with sth like "V2", I've decided to use slightly different names for the new policy:

createCommunicationAuthPolicy -> createCommunicationAuthenticationPolicy
createCommunicationAuthenticationPolicy -> createCommunicationAuthenticationPolicy

Also, all these methods are marked as @hidden to be excluded from the docs, and I marked the old ones with @deprecated.
I was considering removing the old policy entirely since it's marked as @hidden and not supposed to be used by customers but in the end, I decided not to because I couldn't find any Azure guidelines that would allow me to do so.
@xirzec @bterlson Could you please let me know what approach you would recommend and if it's the current one, then approve the related API view?

@xirzec @bterlson Could you please let me know what approach you would recommend and if it's the current one, then approve the related API view?

Our normal approach in these sorts of situations (we're updating a core package) is to bump the major version and do the break (so ditch the old policies and export the new ones with the same name) and then have dependent packages upgrade incrementally.

Both have their pros and cons. If we delete the old one, we should migrate all the client libs in a single PR...a bit more work but less code to maintain in the end. If we stick with the current approach, we allow for gradual onboarding and still can decide to remove it later, once everyone's onboarded.

I agree with @xirzec.
By doing a major version update for communication-common, we will be free to remove dependency on core-http. The rest of the communication libraries can move to this new major version in different PRs.

@xirzec I have removed the old policy and replaced it with a new one. No APIView has been generated, I suspect it's because I have bumped the major version as you suggested. Can you please give a final approval so that we can merge this PR? The API change is visible here: https://github.com/Azure/azure-sdk-for-js/pull/20337/files#diff-aa1c3b86239992f00aa0ef7192f0f24632b66e2a0b086a001189b2670cba75e7

@xirzec in the end, I managed to create an API view for this PR manually. can you please approve it there as well?
https://apiview.dev/Assemblies/Review/cd646a2eb52342bd84aa3d1e3fb4285e/7e0a3470c9584f4cbacba31220aa2889?diffRevisionId=f86bf33908884a1bb597730856d29199&doc=False&diffOnly=True

API changes have been detected in @azure/communication-common. You can review API changes here
API changes
- createCommunicationAccessKeyCredentialPolicy: (credential: KeyCredential) => RequestPolicyFactory
- createCommunicationAuthPolicy: (credential: KeyCredential | TokenCredential) => RequestPolicyFactory
+ export declare function createCommunicationAccessKeyCredentialPolicy(credential: KeyCredential): PipelinePolicy;
+ export declare function createCommunicationAuthPolicy(credential: KeyCredential | TokenCredential): PipelinePolicy;

@xirzec in the end, I managed to create an API view for this PR manually. can you please approve it there as well? https://apiview.dev/Assemblies/Review/cd646a2eb52342bd84aa3d1e3fb4285e/7e0a3470c9584f4cbacba31220aa2889?diffRevisionId=f86bf33908884a1bb597730856d29199&doc=False&diffOnly=True
edit:

oh, the PR API views started working again.... so you can also approve this one: https://apiview.dev/Assemblies/Review/b0a054c7d9674778b508a925f4ed1519?diffOnly=True&diffRevisionId=4766e5b3b88041948d84fb1cfefcdf1a sorry for the confusion😁

I approved both! so you're super approved. 😆

Lets go! Lets go!


fix: use theme colors

fix use theme colors in global.dart and noNetworkConnectionSnackBar.dart

@KalleHallden application colors at the bottom of theme_color.dart i picket from git history of global.dart, because they vanished in last merge  into alpha branch :)

Thanks for working on a fix, but there were some other things that needed to be fixed so I made a PR #106 that fixes these issues.


avoid erroneously hiding new plan comments

currently, if both globaldev and dev have new plans and run in that order, comment for globaldev would be hidden.

Lol


Development PNG Images on Android

While developing, we've run into an issue of PNGs not displaying while running Android in development (in particular in the ./core package). SVGs appear to still work as expected.
I experimented a lot with the metro bundler and react native config to no avail as of yet. Any insight here @cvarjao?

@JamesKEbert , got an example on how PNG is being used?

If on the ./core/App/screens/PinEnter.tsx screen you change the  source:
<Image
   source={require('../assets/img/logo-large.png')}

And you can change the png to any png in the ./core/App/assets/ directory you want, it won't show up during development.
(or were you looking for a branch?)

I had the same problem, I saw that the image show when I call image to uri.
It seems to be a path issue in Android.
ex)
<Image         source={{           uri: 'https://i.ibb.co/qF8qRnK/upload-1.png',         }}         resizeMode="cover"         style={{ height: 100, width: 100 }} />

closing stale issues


fix: fix vertical alignment of interpretation action buttons TECH-1085

Fixes TECH-1085

Key features

align vertically all action buttons

Description
The renderProps approach is used to be able to add custom styles to the wrapper span elements.

Screenshots
Before:

After:

Verified that the icons are indeed vertically centered. LGTM


Test against scipy.fft when available

Follow-up of #2355 and #2998. Now that SciPy v1.4.0+ is out, we should try to test against it when it is available (and fallback to the old test suite when it's not).
In addition, two more tests are added to wherever applicable. First, scipy.fft.set_backend(cupyx.scipy.fft) should be tested. Second, when v1.5.0+ is present, within the set_backend() scope plan != None should function correctly without raising NotImplementedError.
cc: @peterbell10 @grlee77

I think test_*_backend() should be backported to v7, but not test_*_backend_plan() because #2998 was not backported. Let me know if you want me to prepare the backport PR.

Hi @toslunar, changes are made, PTAL.
Note that in 750bffd I applied a more stringent criteria for skipping irfftn tests (#3084), because those tests ran fine on my P100 machine with CUDA 9.2. It's better to stick to what was done originally (#2922).

@toslunar Question: Is the CI set up to test recent SciPy?

@toslunar Question: Is the CI set up to test recent SciPy?

Not yet.  I was trying to tweak the CI configuration in chainer/chainer-test#559, but I'm sorry that it's stalled.

Ah OK, no worries, just curious. Thanks 🙂

With chainer/chainer-test#581, is this PR still blocked?

With chainer/chainer-test#581, is this PR still blocked?

Yes.  scipy_newest_upper_version is used only in chainer-py35, chainer-slow, and chainer-doc.

Jenkins, test this please.

Jenkins CI test (for commit 10d96bbdd5a7aa534bea8337c8f447a96086a608, target branch master) succeeded!

Thank you, @toslunar!


Reconcile Kubernetes manifests

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

There are old Kubernetes manifests in /kubernetes that we should remove or otherwise reconcile with the Kubernetes deployment repo at https://gitlab.com/ncsa-blast/kubernetes.

Describe the solution you'd like

We should probably just delete the existing /kubernetes folder or replace its content with a Readme.md file linking to the deployment repo mentioned above.

Describe alternatives you've considered

Additional context

Resolved in #202 (commit 6d3a395c1ca48c3d1c0effa1f7ddd2b0d595739d)


Issue with the light and dark mode

Describe the bug
in the dark mode every thing is fine but in light mode the animations on the about us page are not visible properly and the text on the contact us page is not visible,
To Reproduce
just turn on the light mode and see the contact us page and the about us page
Expected behavior
everything should be properly visible even  when the modes are toggled in beyween
Screenshots

Please assign this issue to me @Akshatchaube01

@Akshatchaube01  can u assign me this issue u can consider the both the requests and pick the best out of both the pull requests

This issue has been fixed


Added info on the control header and default_path

Default path gets reset by a new control header
Default path can be used as a general prefix for samples, not just a path prefix

The way the control header information is worded in the sfz book makes it seem that all controls opcodes should be reset on a new control header and not just default_path, but sforzando does not implement this behavior and it's not entirely unreasonable.

Manually added this new info to default_path and control header pages. Thanks!

Taken care of manually.


split up css classes

What do you think of this new way of managing all the css classes?
There will be two new gulp tasks that create two css files for either site and projector. The files included are given in the core/static/css/site.css (resp. projector.css) with import statements. The gulp task parses them and put everything together. Every app should get a site.css and  projector.css as well as css files for parts like the diff-view. These files gets imported by every app's site.css/projector.css.
This should be the the import order:
core/static/css/site.css
  - core/static/css/core/site.css
      - fonts.css
      - helper.css
      - mediaqueries.css
      - osTable.css
      - ...
  - motions/static/css/motions/site.css
      - diffView.css
  - users/static/css/users/site.css
  - ...
core/static/css/projector.css
  - core/static/css/core/projector.css
      - fonts.css
      - helper.css
      - slides.css
      - ...
  - motions/static/css/motions/projector.css
      - diffView.css
  - users/static/css/users/projector.css
  - ...

Please check #3253, #2209 and #3011. Of course we can change the way we handle CSS and we do not have to use the jspm loader but concat all together. I only recommend to think about this for a moment.

@normanjaeckel I switched to sass. Is this now ok? I'll do a _variables.scss with all things we use often (OS colors, alert boxes colors, sizes, fonts, ..).

Ok, looks good. I do not understand why we use and underscore here but if you do it is ok for me.

@normanjaeckel I do not like the underscore neither, but this is sass syntax for partial stylesheets:
If you have a SCSS or Sass file that you want to import but don't want to compile to a CSS file, you can add an underscore to the beginning of the filename. This will tell Sass not to compile it to a normal CSS file. You can then import these files without using the underscore.

You can test the site. should be ok for the first splitting.


Insecure SSL connection

Hello!
This package can't work other insecure connections. In some cases (like proxy) it's necessary.
Implement this feature please.

You can override the HttpClient with  client.SetHTTPClient, this should help,


FCC's built-in console doesn't show console.log() output (Chrome)

User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36.
The text in the FCC pseudo-console gives the impression that console.log() outputs will appear there.
/**
  * Your output will go here.
  * Any console.log() -type
  * statements will appear in
  * your browser's DevTools
  * JavaScript console as well.
  */

I thought that the last FCC update added this feature but in Chrome 53.0.2785.116 on Windows, the browser console is still the only way to see console.log() output.  I discovered this because students in the chat were confused.  If the FCC console is working as intended, I believe that the text should be clarified.

Hey there. The console.log() statements will not show up in the output window ("FCC pseudo-console" in your words). Only the selected data shows up in the output windows, usually the return values of the functions (whose empty body is provided in the challenge) which are tested.
And generally the return value of the top-most function is displayed in the browser. There are challenges that do not have a function wrapping them, so the term "output" is used.
I have confirmed the above info from the FCC Contributors gitter chat room. You can join there and ask more questions about this.

Also fwiw, the console.log statements do show up in the browser Dev Tools and I think it's worth pointing campers there so they learn those tools as a side-effect.

@karuppiah7890 My suggestion is that if this is the intended behavior (as your comment indicates), then the text
/**
  * Your output will go here.
  * Any console.log() -type
  * statements will appear in
  * your browser's DevTools
  * JavaScript console as well.
  */

should probably be changed.  Saying that  the statements will appear in the DevTools console "as well" is giving the impression that the statements can be seen in both places.

@ArielLeslie I completely agree. I think it should be done. @dhcodes Your comments on this ?

I agree with the change

In this file and this file,
remove  as well from:
/**
  * Your output will go here.
  * Any console.log() -type
  * statements will appear in
  * your browser's DevTools
  * JavaScript console as well.
  */

This is the current behavior with React.

@BerkeleyTrue you mean with React, it will show up in both the output box and the devtools console?

@dhcodes Yes, console.logs from will show up in the output window.
We run two different processes for each challenge, the main process that generates the output and the preview, and the test process, which will iterate through the tests.
The first process will actually proxy the calls to console.log so that it shows up in the output window.
The second will not and these will show up in the dev tools console.

Sounds good. Let's close this then since it will be fixed by the React update?

I completely agree, though I think console.log(), console.warn(), and console.err() should be added.  It would be as easy as making wrappers for each to change the innerHTML of whatever id displays output.


Customize TwitterPicker using TypeScript

Hi there! Thank you for the awesome component.
I am using your library + typings + TypeScript. Now I am gonna implement a 'no-color' feature so I added a 'none' value to my 'colors' array so it generates a div with title="none" as a result. However, if you look at handleChange function in TwitterPicker you should see a validation at line 114:
color.isValidHex(hexcode) && onChange({
So I never receive a callback when clicking at a particular color. Now I need to create my own 'EnhancedTwitterPicker' component in Type Script to avoid that. Do you have any suggestions how to do that? I don't think we have any typings for sub-component such as Swatch or ColorWrap. Another approach is to override handleChange function but it's also impossible because it's been defined within a closure. Please, let me know what do you think.

I am going to go ahead and close this. If you are still having an issue please try using the newest version of this package. Otherwise, you can open a new issue.


[setup] add pulumi params to config

What does this PR do?
Add support for parsing log level and lot to stderr to local config file
Which scenarios this will impact?
Tasks
Motivation
Tasks are currently broken when local config contains pulumi params
Additional Notes

/merge

/merge


Update apt-utils for dell overlay

Update apt-utils for dell overlay.

:+1:

👍

@iceiilin @RackHD/corecommitters

:+1:


Add blankline_before_or_after_brace option.

Environment: rustfmt 1.4.37-stable (f1edd042 2021-11-29) (with no configuration file)
Currently, blank lines before the opening brace { or after the closing brace } are removed.
fn main() {

    println!("Hello, world!");

}

↓
fn main() {
    println!("Hello, world!");
}

This style is hard to read especially when the signature (plus where clause) and the body are long:
use regex::Regex;
use std::process::Command;
use std::process::Output;

fn _some_function<T, U, V, W>(
    _some_param_1: T,
    _some_param_2: &U,
    _some_param_3: Vec<V>,
    _some_param_4: &[W],
    _some_param_5: String,
) -> String
where
    T: Iterator,
    T::Item: Clone,
    U: std::fmt::Display + Sync,
    V: std::hash::Hash,
    W: PartialEq + PartialOrd,
{
    let regex = Regex::new(r"\$\((.*)\)").unwrap(); // <--- I want a blank line above this line!

    let mut s = String::new();

    match regex.captures(&s) {
        Some(c) => {
            let command = c.get(1).unwrap().as_str();
            let range = c.get(0).unwrap().range();
            let res: Output = Command::new("bash").args(["-c", command]).output().unwrap();
            let res: String = String::from_utf8(res.stdout).unwrap().trim().to_string();
            s.replace_range(range, &res);
        }
        None => (),
    }

    let a = 5;
    println!("{}", a);

    std::env::args().for_each(|e| println!("{}", e));

    String::from("hello")
}

I've checked all the stable and unstable configuration options listed in  Configuring Rustfmt, but it seemed there was no option to preserve blank lines before or after braces.
So this is a feature request:
blankline_before_or_after_brace
Default value: false
Possible values: false, true, preserve
Behavior:

false (default): No blank line before or after braces is allowed.

true: Always insert a blank line before or after each brace.

preserve: Preserve the style in the original code.

Realize some old branching decisions have complicated the ability to parse the issue tracker, but this is largely duplicative of #2868 and implementation in #4303.
Hopefully most, or at least a good chunk of #4303 could be backported as a starting point though I think it'd be worthwhile to revisit the implementation in light of the ask above/question I surfaced in https://github.com/rust-lang/rustfmt/pull/4303#issuecomment-652741059

Thank you for you response. I've read the three links you gave plus #4438 , but I don't fully tell the time series and the current status.
My understanding of the time series is

The option did once exist, and its name was remove_blank_lines_at_start_or_end_of_block. (#2868 (comment))

This option was removed at some time. (#2868 (comment))

#2868 was issued to revert the removal of the option.

This revert (but only with around opening brace and renamed to preserve_block_start_blank_lines?) was finally implemented and merged. (#4303)

#4438 was issued which says preserve_block_start_blank_lines is simply unavailable (though merged in #4303).

Now I'm very confused. In #4438, someone says Closing since I discovered that apparently, it's for v2 but not v1.4. and a screenshot of the documentation which refers to the option is posted. However, if I now check the documentation of v2.0.0-rc2 (when I first issued this issue, I only checked master version), preserve_block_start_blank_lines doesn't exist.
Maybe I misunderstand something...?

Maybe I misunderstand something...?

Yes, you're understanding is off, but my apologies if I've caused any confusion.
tl;dr - Your feature request was (partially) implemented, but it was implemented on a different branch that was for an experimental version of rustfmt which was never released, and which will not be released any time soon (if ever). As such, the feature still needs to be implemented on the main/official rustfmt version, but I've tagged in details from the experimental work because it should serve as a useful reference, and potentially even has some work that can be directly utilized by cherry-picking commits from the other branch

@calebcartwright can you assign this to me? Will try cherry-picking, and if I have any issues I'll reach out

@calebcartwright can you assign this to me? Will try cherry-picking, and if I have any issues I'll reach out

We've got triagebot wired up, can you try adding a comment with @rustbot claim?

Also, thanks for your interest @murchu27! We don't exactly have contributors racing each other with competing PRs so you should be all clear to work on this one :grinning:
We do need to figure some things out relative to the solution prior to grabbing any commits though. Would encourage you to take a look at some of the dialog/questions/considerations and share any thoughts or proposals you may have.

@rustbot claim

Nice one, and yes I'll carve out some time over the weekend to read more into this

Hi @murchu27, is there any way to implement that as a custom option?

Hey @ppamorim , by "custom option" do you mean "config option"? If you're asking whether I've made progress on this, then unfortunately not!
It's still very much on my task list, but happy to hand this over to someone else if there's a taker. I know @ayazhafiz worked on this before, but I'm not sure if they have time to contribute right now


Add chrome options

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- dotnet/SimpleSauce/EdgeVersion.cs  1
- dotnet/SimpleSauce/SauceDriver.cs  1
- dotnet/SimpleSauce.Test/SauceOptionsTests.cs  1
- dotnet/SimpleSauce/SauceOptions.cs  2
- dotnet/SimpleSauce.Test/EdgeTests.cs  1
- dotnet/SimpleSauce/SauceSession.cs  2
- dotnet/SimpleSauce.Test/BaseTest.cs  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- dotnet/SimpleSauce.Test/SauceDriverTests.cs  1

See the complete overview on Codacy


running Build (from sublime) terminates server

Just noticed if I run Build (make) directly from Sublime LSP stops working. The Restart server is required.
Here is the output:
LSP: <--  textDocument/publishDiagnostics
Running  make
LSP: LSP stderr process ended.
LSP: LSP stdout process ended.
LSP:  --> textDocument/didChange
Traceback (most recent call last):
  File "plugin.core.documents in /home/kuba/.config/sublime-text-3/Installed Packages/LSP.sublime-package", line 110, in <lambda>
  File "plugin.core.documents in /home/kuba/.config/sublime-text-3/Installed Packages/LSP.sublime-package", line 121, in purge_did_change
  File "plugin.core.documents in /home/kuba/.config/sublime-text-3/Installed Packages/LSP.sublime-package", line 195, in notify_did_change
  File "plugin.core.rpc in /home/kuba/.config/sublime-text-3/Installed Packages/LSP.sublime-package", line 62, in send_notification
  File "plugin.core.rpc in /home/kuba/.config/sublime-text-3/Installed Packages/LSP.sublime-package", line 71, in send_payload
OSError: [Errno 9] Bad file descriptor

A stopgap solution which seems to work in my case is to bypass entire exception block:
        except BrokenPipeError as err:
            # sublime.status_message("Failure sending LSP server message, exiting")
            # exception_log("Failure writing payload", err)
            # self.process.terminate()
            # self.process = None
            pass

Not sure how harmful this change will be ;)
My guess this is sending next request to the clangd server. Perhaps terminating the process in case of any issues is too severe...?

Hi, thanks for investigating!
Your guess is correct, after make was started, a content change was sent to clangd which failed.
Are you sure clangd survives the BrokenPipeError after you commented out the process.terminate() ?
The cause could possibly be clangd terminating on make, or the BrokenPipeError is a phantom error we need to handle more precisely.

After the change I can still jump to definition (using lsp_symbol_definition) so clangd seems to still be running in the background.

If this is still occurring, I would like to see some logs from clangd around the time that a brokenpipeerror occurs.


Add listidr method for gcs

Closes https://github.com/PrefectHQ/prefect-gcp/issues/118
Example

Screenshots

Checklist

[ ] References any related issue by including "Closes #" or "Closes ".

If no issue exists and your change is not a small fix, please create an issue first.

[ ] Includes tests or only affects documentation.
[ ] Passes pre-commit checks.

Run pre-commit install && pre-commit run --all locally for formatting and linting.

[ ] Includes screenshots of documentation updates.

Run mkdocs serve view documentation locally.

[ ] Summarizes PR's changes in CHANGELOG.md

These suggestions sound pretty great! I haven't used PurePosixPath so far, but I'll handle it. However, wouldn't be better to keep the final return state as a list to benefit from existing methods like sort? I think of something like list({set_comptehension}).
I'll come back tomorrow with updates! Thank you!

From: Andrew @.>
Sent: Wednesday, January 25, 2023 8:34:41 PM
To: PrefectHQ/prefect-gcp @.>
Cc: razvanvilceanu @.>; Author @.>
Subject: Re: [PrefectHQ/prefect-gcp] Add listidr method for gcs (PR #121)
@ahuang11 commented on this pull request.

In prefect_gcp/cloud_storage.pyhttps://github.com/PrefectHQ/prefect-gcp/pull/121#discussion_r1087030845:

   if bucket_path is not None:

       unique_folders = list(set([blob.name.split(os.sep)[1] for blob in blobs if "." not in blob.name.split(os.sep)[1]]))

       return [folder for folder in unique_folders if folder]

   else:

       return list(set([blob.name.split(os.sep)[0] for blob in blobs if blob.name.endswith(os.sep)]))

We can probably simplify by:

using a set comprehension directly
using PurePosixPath to handle discovery of folders
removing the if/else

Something like this:
from prefect_gcp.cloud_storage import GcsBucket
from pathlib import PurePosixPath
bucket = await GcsBucket.load("my-bucket")
blobs = client.list_blobs("my-sbx-bucket")
{str(PurePosixPath(blob.name).parent) for blob in blobs}
—
Reply to this email directly, view it on GitHubhttps://github.com/PrefectHQ/prefect-gcp/pull/121#discussion_r1087030845, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJSHYZDWGMQSANRBZZ76BGLWUFW4DANCNFSM6AAAAAAUGEULDM.
You are receiving this because you authored the thread.Message ID: @.***>

However, wouldn't be better to keep the final return state as a list to benefit from existing methods like sort? I think of something like list({set_comptehension}).

Sure, at the end, you can do sorted({...}) to sort and convert to list.

Fixed the tests and ran pre-commit and everything passes, is there anything else that runs on git workflow that I should take care of?

I applied a quick fix to the tests; there's nothing else to take care of in this PR now. Thank you for contributing!

thanks for the help @ahuang11, couldn't have done it without you


feat(ac): support power consumption stats

This converts total_energy_consumption and current_energy_consumption in long term statistics.
That way, we're able to use it in the Energy Dashboard.

This converts total_energy_consumption and current_energy_consumption in long term statistics.
That way, we're able to use it in the Energy Dashboard.

You should add following code to the file sensor.py to make it works properly.
    @property
    def state_class(self):
        return self._config.get("state_class")

You're right. I've Forgot to push it.

You're right. I've Forgot to push it.

OK, thank you @rokam


Dart program run issue in VS CODE

VS Code Version:

Version: 1.85.1 (user setup)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:49:37.021Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

OS Version:  Windows 10

Steps to Reproduce:
Run this Dart code in VS CODE:
import 'dart:io';
void main() {
var isLoopContinue = true;
var attempts = 0;
while (isLoopContinue == true) {
stdout.writeln("Enter email:");
var email = stdin.readLineSync();
stdout.writeln("Enter password:");
var password = stdin.readLineSync();
if (email ==<EMAIL_ADDRESS>&& password == "123456") {
print("Login successfully");
isLoopContinue = false;
} else {
attempts++;
if (attempts > 3) {
isLoopContinue = false;
print('Your account has been blocked!');
} else {
print('Invalid credentials. Please try again.');
}
}
}
}

This is the issue when we write first input and press enter:
Enter email:
<EMAIL_ADDRESS>Unknown evaluation response type: null
#0      DartDebugAdapter.evaluateRequest (package:dds/src/dap/adapters/dart.dart:1076:7)
#1      BaseDebugAdapter.handle (package:dds/src/dap/base_debug_adapter.dart:141:20)
#2      BaseDebugAdapter.handleIncomingRequest (package:dds/src/dap/base_debug_adapter.dart:447:7)
#3      BaseDebugAdapter._handleIncomingMessage (package:dds/src/dap/base_debug_adapter.dart:295:7)
#4      ByteStreamServerChannel._readMessage (package:dds/src/dap/protocol_stream.dart:82:18)
#5      ByteStreamServerChannel.listen. (package:dds/src/dap/protocol_stream.dart:53:24)
#6      _RootZone.runUnaryGuarded (dart:async/zone.dart:1594:10)
#7      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#8      _DelayedData.perform (dart:async/stream_impl.dart:515:14)
#9      _PendingEvents.handleNext (dart:async/stream_impl.dart:620:11)
#10     _PendingEvents.schedule. (dart:async/stream_impl.dart:591:7)
#11     _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#12     _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#13     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#14     _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:185:5)
Code is ok when we run this code from CMD by "dart run filename.dart"

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!