Paramaters matched to JSON fields are the wrong type

These parameters should end up as interface{}, not json.RawMessage.
CREATE TABLE "user" (
    "id" INT PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
    "metadata" JSONB
)

-- name: FindByAddress :one
SELECT * FROM "user" WHERE "metadata"->>'address1' = $1 LIMIT 1

type FindByAddressParams struct {
	metadata json.RawMessage
}

Initial report

https://play.sqlc.dev/p/cd6227106fb8fb969d1fc9699dd9c03046e26578c589268e30d23573f67037bb

Hi @kyleconroy, I have the same problem as in issue #738, I have table like this:
CREATE TABLE "user" (
    "id" INT PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
    "metadata" JSONB
)

but instead of having an object, I have an array of users:
[
    {
        "lic":"1137868E",
        "firstname":"Joe",
        "lastname":"Bag"
    },
    {
        "lic":"1295364R",
        "firstname":"HA",
        "lastname":"Dégue"
    },
]

then I wrote a query to get a user by "lic"
-- name: FindUserByLic :one
SELECT * FROM user AS u WHERE u.deleted_at IS NULL AND u.metadata @> $1; -- > $1 suppose to be like this '[{"lic":"1295364R"}]'

and I got this parameter:
type FindUserByLic struct {
	metadata json.RawMessage
}

here is my code:
	lic, err := json.Marshal(fmt.Sprintf(`'[{"lic":"%s"}]'`, req.Lic))
	if err != nil {
		return err
	}
	arg := db.FindUserByLicParams{
		Metadata: lic,
	}

	contests, err := server.store.FindUserByLic(ctx, arg) //find user by lic
	if err != nil {
		return err
	}

but in the end I had an empty array :/

That is not a bug, I have a solution for that or any parametrized representation of jsonb operations.
First you need to define the datatype of your parameter on your sqlc definitions, for example:
... and cl.records @> sqlc.arg(records)::jsonb -- Here you expect to input: '[{"id":"1234567890"}]'
Then in your go code, you would have to have an interface conversion to JSONB:
func InterfaceToJSONB(data interface{}) pgtype.JSONB {
	var jsonB pgtype.JSONB
	err := jsonB.Set(data)
	return jsonB
}

Last, running your query, you have this:
param3 := "1234567890"
someData, err := q.SomeQueryName(ctx, db.SomeQueryParamsParams{
		ParamName1:  param1,
		ParamName2: param2,
		Listings: InterfaceToJSONB(`[{"id":"` + param3 + `"}]`),
	})

This is fixed in v1.23.0 by enabling the database-backed query analyzer. We added a test case for this issue so it won’t break in the future.
You can play around with the working example on the playground


Errors Inbox Improvements

Overview

Merge develop branch
Adds new APIs for end user tracking and error group fingerprinting.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@637879a). Click here to learn what that means.
The diff coverage is 94.24%.

@@           Coverage Diff           @@
##             main     #791   +/-   ##
=======================================
  Coverage        ?   64.03%
=======================================
  Files           ?      264
  Lines           ?    26215
  Branches        ?     4483
=======================================
  Hits            ?    16788
  Misses          ?     8273
  Partials        ?     1154

Impacted Files
Coverage Δ

newrelic/core/attribute.py
95.90% <ø> (ø)

newrelic/core/error_node.py
100.00% <ø> (ø)

newrelic/api/settings.py
81.81% <73.33%> (ø)

newrelic/core/stats_engine.py
79.90% <86.95%> (ø)

newrelic/api/time_trace.py
85.15% <92.85%> (ø)

newrelic/core/transaction_node.py
96.36% <98.13%> (ø)

newrelic/agent.py
99.60% <100.00%> (ø)

newrelic/api/transaction.py
81.46% <100.00%> (ø)

newrelic/core/config.py
91.69% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


After bulk deletion of monomer abbreviations, Undo returns expanded monomers

Steps to Reproduce

Open file in Macro mode (Flex mode) monomers-cycled.zip
Switch to Micro mode
Select all structure by Rectangle tool and press Erase
Press Undo

Actual behavior
After bulk deletion of monomer abbreviations not all highlighted abbreviations deleted and Undo returns expanded monomers
Expected behavior
After bulk deletion of monomer abbreviations all highlighted abbreviations deleted and Undo returns deleted abbreviations on the same positions
Videos
https://github.com/user-attachments/assets/4108ff28-d4c2-4a6b-88d5-c24018d6f897
Desktop:

OS: Windows 11
Browser Chrome
Version 128.0.6613.120 (Official Build) (64-bit)

Ketcher version
[Version 2.26.0-rc.1]
Indigo version
[Version 1.25.0-rc.1]
Bug found during testing: https://github.com/epam/ketcher/issues/5400

Tested. Bug fixed.
https://github.com/user-attachments/assets/08cb4b00-b785-48e2-bca0-2239dbc2b70d
Desktop:

OS: Windows 11
Browser Chrome
Version 128.0.6613.120 (Official Build) (64-bit)

Ketcher version
[Version 2.26.0-rc.7]
Indigo version
[Version 1.25.0-rc.4]


Corrected the manifest.json file sample

comma is missed in manifest.json file.

Hi @subrahmanyam-pampana, thanks for pointing this out! We'll take a look.


Update index.md

Script Monitor setup developer docs typo

Thanks, @gyx-cf ! I'll go ahead and merge this small fix.


Release 0.1.0 broken by dependencies

Division by zero error now raised by sr3.
File not found error in csv2bufr due to change in mapping file name.

More details to follow.

a number of div/0 errors have been fixed in later versions... the errors were introduced whan adding metrics to the logging to add average transfer rates.

I'm not sure of best practice when it comes to importing external modules and libraries, Do we want to specify a version for the dependencies in the Dockerfile and requirements.txt files? At the moment we are using latest which can result in a working release becoming broken as is now the case for Release 0.1.0 of WIS2box.

explanation of why the dependency broke
Sarracenia changed the strategy for how dependencies are handled, allowing people to install what they need for a given deployment case.  prior to this change:  pip install metpx-sr3 would install all possible dependencies, for example pulling in dateparser, which itself triggers a dozen or so other packages to be downloaded, but is only used when polling an ftp server, so not used by the current configuration.  The pip packaging was changed to modularize functionality as "extras".  So one can make more compact distributions, and it is also much easier to create OS packages, this is part of stabilisation work for a release.  As of 3.0.15:

pip install metpx-sr3   - installs core only.
pip install metpx-sr3[mqtt]   - installs core + mqtt support.
pip install metpx-sr3[amqp,vip]   - installs core + support for high availability failover using vip.s
pip install metpx-sr3[ftppoll]  - adds support for ftppolling (requires dateparser)

2nd factor: docker image generation has been moved off of the metpx-sr3 onto a release branch, so it should cut down on the noise considerably.

The dockerfile just had to explicitly install the extras going forward.

@webb-ben does this make sense?

Agree it makes sense to only include dependencies as they are needed.
However we decide to handle version control, I think it makes sense to ensure that the dependencies are on the same version across the box. For sr3 that is going to be using the same version of pip/git archive in the wis2box Dockerfile as the docker image used for all of the other sr3 containers.
@petersilva in the #159 is still using v3.00.14 (https://github.com/wmo-im/wis2box/pull/159/commits/d3c354b8c8a3d6749464f912d8bb03acbd3a29ea)

Tom pinned the version in that branch... I had added the missing dép... It wasn't necessary to pin although people can.
Fixing the dép fixes the current issue

This has been fixed by #163.  @david-i-berry can you confirm/validate?

I am not sure the changes will be reflected in 0.1.0... Because 0.1.0 builds from the most recent zip archive of sr3 and csv2bufr. I believe would need to tag specific versions of these for 0.1.0 to work?

It's the pinning to :latest that causes the problems and that can introduce breaking changes when a dependency changes. This came about as i was trying to role back to the 0.1.0 release of the WIS2box but couldn't due to changes to both sr3 and csv2bufr.
For future the releases do we want to pin to version numbers?

We will definitely need to pin to sr3 and csv2bufr for the next release.

Since fixed via pinning csv2bufr, bufr2geojson, wis2box-api and wis2box-ui on wis2box release (documented at https://github.com/wmo-im/wis2box/wiki/ReleaseManagement)


I am unable to log in

sorry about the title I guess I did the labels wrong. I just installed the safari extension and the login button appears to do nothing at all.

Shall we apply other social login such as BitChute / Reddit / Mastodon ?

I can replicate. This issue is website-related - will look into fixes. In the meantime, please go to https://dissenter.com and log in through there. After doing so, you will be logged in and able to use the extension.

So I tried that I logged into the website but it still isn't working. I am currently logged in to the website but not the extension.

I am having the same problem. Logging into the site does not fix the problem either.


[SPARK-36977][DOCS][PYTHON] Drop references to Python 3.6 support in docs and python/docs

What changes were proposed in this pull request?

Remove or adjust references to Python 3.6 in docs and python/docs.
Why are the changes needed?

To reflect removal of support in Spark 3.3  (SPARK-36145).
Does this PR introduce any user-facing change?

Updated documentation only.
How was this patch tested?

Manual rendering of individual docs.

Test build #144087 has started for PR 34242 at commit 0f26b14.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48565/

We'll have to fix setup.py for Python version, and remove things like https://github.com/apache/spark/blob/master/python/pyspark/context.py#L233-L239 but they can be done separately.
Merged to master.


fix(nuekit-server): allow resolving index.html with base url

Fixes server not knowing index routes, e.g. localhost:8080/blog by adding index.html to links not having any extension, resulting in a file request to localhost:8080/blog/index.html

Solid work again. Thanks!


Improvement: links in footer.

Provide links for

Documenation
Feedback
Terms
Support

FYI, I've got a start of documentation.
The others might involve @robinbb.

Closed with https://github.com/Granola-Team/mina-block-explorer/pull/438


build function to remove duplicate photos in sorted directories after renamed based on mergin column name/tag

reduce bloat

not going to be simple since mergin photos are renamed on their way to the server!  could maybe deal with that in the Q form though

closed here https://github.com/NewGraphEnvironment/fpr/issues/42


Different Results Generated from 0.10.1 MXNET R Package and 0.9.4 MXNET R Package

Dear Users and Developers,
I worked in a project about data mining which using convolutional neural networks based on MXNET R package. And when I use the old version of MXNET R package 0.9.4, I got a pretty good result. However, the error rate generated by updated version( 0.10.1) was two times higher than the error rate generated by old version (0.9.4). I had checked the source code in github (https://github.com/apache/incubator-mxnet/tree/master/R-package), and found that developers added more mx functions, more parameters in some functions. So I guess that maybe these cause the differences between two results generated by old version package and updated version package. Also, I kept the same random seeds on the top of my codes.
My question is that whether there are some errors/mistakes in old MXNET R package?
Thanks!
Best

I haven't noticed issues between 0.9.4 and 0.10 and I'm not aware of changes in R package that were tied to bug, though corrections in the backend library might explain the difference.
Just a guess here, but if the model has BatchNorm, there have been some adjustments to its parameters. If using SGD optimizer, could be worth trying training with a different learning rate or use another optimizer like adadelta to compare the versions behavior.

@yuzhouchen92 Can you share an example?

@jeremiedb  Yes, my model concludes BatchNorm, and using SGD as my optimizer. I had tried different learning rate, momentum, and used other optimizers, but the result generated from 0.10.1 R package was still worse than the old one. Sure, I will re-check the BatchNorm layer. Thanks for your suggestion!

@thirdwing Because my data was provided by one bank, so I maybe could not put the whole thing here. I will share one toy example here later.

@nswamy @sandeep-krishnamurthy Could you please label the issue as Pending Requester Info

@sandeep-krishnamurthy @nswamy Could you please close this issue due to inactivity
@yuzhouchen92 Please feel free to reopen if closed in error


Table footnotes

It is customary for table footnotes to be attached to the table. It is unclear how best to capture that semantically, though. There are various options, none really pleasant:

Put them in the figcaption for the figure that contains the table. (That's what I've implemented so far, but it's not great.)
Put them in the table's own caption — but that seem wrong, especially since that is already where we put the caption.
Put them in a tfoot cell that colspans the width of the table. Sort of sensible, but the colspan bit feels hacky.
Put them in an ol inside the figure, after the table. This is legit. Note that semantically that means that the figure is also representing the ol — but I think that's not incorrect. The ol would have the right DPUB ARIA markup of course.

I tend to lean towards the last option. Any thoughts?

Is there always only one table per figure? [Many publications have multiple, figures, etc. in the same container]. If so then I'd agree with [4] , else we have to have something attached to the table itself which would have to be [2] or [3] - in which case I'd favour [2].

This is something that is not described yet but that we need to cover: figure composition (#53). The theory is that every table is always contained in a figure, so we always have a single container available. That has many advantages in terms of styling and modelling, including the one you point at here.
Then if you can compose figures inside of another. So if you have two tables in a table figure they become 1A and 1B.


cmd/go: add option to ignore local replace/exclude directives

If you have a go.mod with replace/exclude directives, those are used when building that module as the top-level target but not when used as a dependency. It might be helpful to have a command-line build flag that means "ignore those even in the top-leevel module" so that you can test more easily in the configuration users will see.

Note that change https://golang.org/cl/126696 states 'Fixes #24666' (this issue), which is presumably what triggered gopherbot to close this issue, but as far I as can see from quick look it looks like the piece of the CL related to this particular issue was in the first patch for the change but then (purposefully) dropped during the review process.
Not sure if the 'Fixes #24666' in the CL was left purposefully or accidentally, but at least wanted to add this comment here indicating that -mod=release does not seem to exist on master.
Description from the original patch:

If invoked with -mod=release, the go command ignores replace and exclude
directives in go.mod, essentially viewing the module as it would when
released and used as a dependency of another module.


Vulnerability roundup 77: git-2.23.0: 3 advisories

search, files

[ ] CVE-2018-1000110 (nixos-19.09, nixos-unstable)
[ ] CVE-2018-1000182 (nixos-19.09, nixos-unstable)
[ ] CVE-2019-1003010 (nixos-19.09, nixos-unstable)

Scanned versions: nixos-19.09: 5f506b95f9f; nixos-unstable: c1966522d7d. May contain false positives.

19.09 is very EOL.
master is at 2.29.2
Our work here is done.

@redvers Many many thanks for plowing through all vulnerability roundup issues and closing obsolete ones. This is very much appreciated.
(pick just a random one for the kudos)


Refactor into separate subcrates, API refactor

I've done some significant rework of the repo, and most of these choices are off the cuff and suiting me in my own use case, so I don't expect them to be everyone's cup of tea. However I did the work of separating things into distinct mods, as well as added a procedural macro which I think DRYs up the addition of new commands significantly.
So in summary:

fixed a segfault in freeing a null ptr
added support for extracting Reply::Error and Reply::Array types from redis
bumped crate version to 0.2.0
separated Command into RedisCommand and RedisCommandAttrs, allowing part to be derived
#[derive(RedisCommandAttrs) support in a procedural macro (redis-command-gen subcrate)
updated redismodule.h to support redis 4.0-rc3 (current)
added call4 for variadic call with arity of 4 (though I'm not sure I use it)

In conclusion, I think that we're now 90% of the way to extracting a useful crate to publish on crates.io, but I didn't get around to that, and wanted to see how this would be received before I went ahead and did that.
I'd love to know people's thoughts.

Obviously I need to learn some more about travis, however I was unable tonight to get the tests running for linux, because of what I suspect is a toolchain issue with the ci scripts. I think it's related to the trust stuff? Sorry for breaking this...

Hi @dwerner, I just wanted to drop a note in to say that this is great! I've had a busy couple of weeks and haven't been able to take a very close look yet, but will soon. Thanks for putting all this together!

Thanks man, and please, if I can improve things, please let me know.

I added a redis_module!() macro to ease creation of RedisModule_OnLoad in a consumer's crate. As an example of using the modules as they are, I wrote https://github.com/dwerner/redis-copyhash.

Genius! That just took a significant amount of friction out of redis module development for me. Thanks, @dwerner.
🍺

Hey @dwerner, apologies again for the extended wait on this one.
I'm interested in trying to get this pulled into mainline. Would you mind taking a pass over it yourself to see if there's anything in here that you might yourself change now that Rust has moved on by a few months?
Aside from that, here's a couple high level comments just to get us started off here:

Given that we've now branched off into more modularity, what do you think about trying to add a few module-specific tests? I think some of redis-command-sys is going to be pretty tough because you need an online Redis, but it might be nice to have a small sample Redis command for redis-command-gen module so that we exercise it's fairly considerable macro and also provide a basic usage example as a secondary benefit.
I think it would be nice for the new redis-command-gen and redis-command-sys crates to have a description string in their Cargo.toml. I think the naming uses terms that are a little too general for people to get a good grasp on them.
Could we get some documentation somewhere demonstrating how to use the gen crate, the sys crate, or both? Possibly just something light in individual README files.
Regarding the command API, the static_handle="CL_THROTTLE_COMMAND" struck me as a slight leak in implementation details. Really users probably only care about the commands they're creating, and might be confused that they have to add arbitrary secondary identifiers to them to pass to redis_module!. Do you think it'd be possible to redis_module! to take command names like redis_module!("redis-cell", 1, "cl.throttle"); or struct names like redis_module!("redis-cell", 1, ThrottleCommand) (or something like that)?

Once again, thanks for very significant work on the project!

Hi @dwerner , any update on your side regarding latest comment from @brandur  ? Thanks in advance.

Chiming in a bit late but since the goal is to simplify the bindings to the C headers I wanted to point out that we could leverage the bindgen crate. The only annoyance is that we will still need to write a small wrapper around the static init function that has already been done here.

@dwerner  @brandur
It seems a bit stale now. I wonder if there's any chance of any action. I think I'm going to take the cell + store bits and fork them into separate crate because that's the only part I care about it, and it can be reused in projects that are not even redis related.
Any comments?

I think the partial extraction of redis specific stuff should live in it's own crate, I just never got around to it. If you make progress, it would be cool to contribute to that.

@dwerner https://github.com/dpc/ratelimit-gcra

@dwerner
I looked at this PR, and it looks like a right approach. However, as I only care about algo. itself, and redis part is unnecessary for me, I am not planing to do anything here other than extracting the algo itself.
I am planning to publish the algo crate on crates.io, as I need it for my own project. If anyone is interested in owning it, I am happy to hand it over.


Opentelemetry configuration

Closes #301

Summary:
Tries to replace our current shared configuration with OT one. This doesn't cover all of the features e.g. setting configuration after class transformations are registered, but we think that this is not a critical issue for us.

I was trying to run the pr with the otel agent to test the config but got the following error (for both sbt task and intelij idea run):
Sbt task: sbt "project example" runWithOtelAgent
ERROR io.opentelemetry.javaagent.OpenTelemetryAgent
java.lang.IllegalStateException: The agent was not installed, because the agent was found in '/Users/lg/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/io/opentelemetry/javaagent/opentelemetry-javaagent-bootstrap/1.10.0-alpha/opentelemetry-javaagent-bootstrap-1.10.0-alpha.jar', which doesn't contain a Premain-Class manifest attribute. Make sure that you haven't included the agent jar file inside of an application uber jar.
	at io.opentelemetry.javaagent.OpenTelemetryAgent.verifyJarManifestMainClassIsThis(OpenTelemetryAgent.java:102)
	at io.opentelemetry.javaagent.OpenTelemetryAgent.installBootstrapJar(OpenTelemetryAgent.java:83)
	at io.opentelemetry.javaagent.OpenTelemetryAgent.startAgent(OpenTelemetryAgent.java:53)
	at io.opentelemetry.javaagent.OpenTelemetryAgent.premain(OpenTelemetryAgent.java:44)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
	at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)

Is it related to the javaagent-tooling dependency? Do you experience it as well?

@lgajowy Yeah, TBH I didn't run this with to OTEL agent, but I get this too. It seems to be more severe than I thought, I spend some time investigating this yesterday and I don't have a solution yet. We probably need to discuss this - I don't wan to be dramatical, but this might even force us to abandon switching to OTEL config in extension...

@worekleszczy
I think we should not call the ConfigInitializer.initialize() at all. It's something that the opentelemetry agent does for us in the AgentInstaller. I was able to confirm on my clone of this PR that when you:

remove the javaagent-tooling completely and stop using the configInitializer
run with the otel agent
call OpentelemetryConfig.get() in the MesmerModule

You still get our default values and are able to overwrite them via system props. So this is the approach I suggest for otel agent.
If we really want to still support the Mesmer agent:
lazy val enabled: Config = {

    val config = OpenTelemetryConfig.get()

    if (!config.getAllProperties.keySet().toArray[String].exists(_.contains("mesmer"))) {
      // build the config from scratch for the mesmer agent
      OpenTelemetryConfig
        .builder()
        .readProperties(
          MesmerConfigPropertySource.getProperties
        ) // you'd probably need to move the MesmerConfigPropertySource to the core
        .readSystemProperties()
        .readEnvironmentVariables()
    }

But that is imho not necessary and is just another reason to drop the mesmer agent right away and focus on the otel extension.

@worekleszczy
I think we should not call the ConfigInitializer.initialize() at all. It's something that the opentelemetry agent does for us in the AgentInstaller. I was able to confirm on my clone of this PR that when you:

remove the javaagent-tooling completely and stop using the configInitializer
run with the otel agent
call OpentelemetryConfig.get() in the MesmerModule

You still get our default values and are able to overwrite them via system props. So this is the approach I suggest for otel agent.
If we really want to still support the Mesmer agent:
lazy val enabled: Config = {

    val config = OpenTelemetryConfig.get()

    if (!config.getAllProperties.keySet().toArray[String].exists(_.contains("mesmer"))) {
      // build the config from scratch for the mesmer agent
      OpenTelemetryConfig
        .builder()
        .readProperties(
          MesmerConfigPropertySource.getProperties
        ) // you'd probably need to move the MesmerConfigPropertySource to the core
        .readSystemProperties()
        .readEnvironmentVariables()
    }

But that is imho not necessary and is just another reason to drop the mesmer agent right away and focus on the otel extension.

@worekleszczy
Tested the PR and compared with #344:
I passed the following properties:
-Dio.scalac.mesmer.module.akkahttp.connections=true
-Dio.scalac.mesmer.module.akkahttp.request.time=true
-Dio.scalac.mesmer.module.akkahttp.request.counter=false

When I put a break point in AkkaHttpAgent in line 42
in #328: I get config that holds 3x false for the akka HTTP agent and that results in HTTP being disabled
in #344: I get true, false, true, as expected.
The behavior in #328 doesn't seem right and I'd expect to witness the behavior from #344 in #328 (did I miss something?)


Addition proposal: OpenVidu video conference platform

OpenVidu offers tooling and SDKs to build your own video and audio streaming application, similar to what Twilio offers in that space, but aimed at groups and business who would like to keep the whole platform on-premises.
OpenVidu installs with 3 components: a main video conference orchestration server, an open-source WebRTC media server (Kurento), and a sample end-user video conference application making use of the former two. The included client SDKs are offered for Node.js and Java platforms, as well as iOS and Android clients through React Native and ionic apps.

@j1elo thanks for your PR! OpenVidu looks really awesome :)
Don't you think what Zoom might be a better option for "alternative to"? But anyway, it's up to you :)

We thought about it but not really; Zoom is just one kind of application that you would be able to make using OpenVidu, but in essence we're closer to Twilio in the sense of providing tools and pre-made components that allow creating services such as Zoom.
Thanks for merging and for maintaining this list!


Add night-not-found feature

Because why not

Can we up the contrast on the 404? I find it really hard to see.

Try seeing it in the dark.
Jokes aside, filters is rather limited and the 404/message block is a single piece, so to make that more visible I can only lighten the landscape, which kinda defeats the purpose. Maybe I'll try adjusting it when nighttime comes again.

No luck. Even a 0.05 brightness increase makes it lose that night feeling. The "404" doesn't have great contrast but it's visible enough unless you use the dark theme in direct sunlight. There's text under it with perfect contrast anyway.


October 5th, 2020 Community Meeting

Please add a topic in this thread and add a link to the Github issue associated with the topic.
Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting
(optional) Paste the image of an animal :smile:

cdCon evangelism - get social (media!):

Simplify install instructions: #385

Merging #415
Exposing RenewDeadline parameter #414
Key features/fixes/enhancements for v1.0 #412

#419: Elevator pitch on remote artifacts support;
#382: CLI PoC project, EP will come soon;

Community meeting feedback:

#415 PR is good for adding a single new linux capability. We will open a new issue for the other capabilities @adambkaplan proposed, and most probably get a new PR from it.
For #414 issue, is ok to proceed to the implementation. @adambkaplan provided good feedback on support a configmap from where we could read configurations. We will open a new issue to discuss on the proposed approach.
For #385 , PR got feedback and should be merged soon. The naming behind the "Build" generated some noise, for now we would be calling scripts and related artifacts either "build-controller" or "build-operator", subject to change.
@otaviof introduced #419 . All to provide feedback on the proposal. We had some discussions around this, the overlap with other features and some of the use cases behind it.
@otaviof to provide a proposal for #382 , then all are expected to provide feedback. There is already a CLI prototype, so is also recommended to play around with it. See  https://github.com/otaviof/shp
We discussed #412 (v1.0 desired items), it seems we are all fine with the list. Lots of work to do :shipit:
We should consider https://github.com/shipwright-io/build/blob/master/docs/proposals/local-registry-image-specs.md for BETA.

❗❗ As a reminder, community meetings should try to avoid as much as possible vendor specific topics for driving discussions. This helps the project to grow on the right direction (vendor neutral one). ❗ ❗


Added getter for KafkaStreams in order to get QueryableState

Hi guys. In order for being able to get the QueryableState, we need to access KafkaStreams object.

@ivanursul ,
Thank you very much for pointing that out, but looks like you make a PR against wrong repo.
That should be https://github.com/spring-projects/spring-kafka 😄
Please, move it there and we'll review and merge.


Fix the default value population for new documents

#2158  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite


Setting examples for JFrog support missing / JForg not supported

I'm trying to use this extension with a JFrog artifactory located on a company server. It is not working. Now, I am not sure if it is due to lacking support or to a misconfiguration on my end. The README states, that JFrog is supported, however in the example settings.json there is no example for JFrog.

You're right, in the past I've only checked the query endpoint and it was correct bud didn't test the version endpoint. Unfortunately, there is no endpoint for getting the package version in JFrog.


Version bump does not update package-lock.json

Starting with npm 5, manually running npm version patch will update version in both package.json and package-lock.json. The direct manipulation of the package.json file done by this script, leaves the lockfile out of sync.
The lockfile should be committed to source control by default as well.

Looks like just setting options.additionalFiles: ['package-lock.json'] will do the trick.


AppBadgePlus.updateBadge(0) not working

when calling AppBadgePlus.updateBadge(0) on Android the app badge number stop depending on the package and start counting the notifications in the notification drawer
expected to completely remove the number

Same issue, my badge when calling AppBadgePlus.updateBadge(0) on  Android doesn't work

@RuiTB @quocviet1996 Could you please offser me your device brand and os version?

Starting with Android 8.0 (API level 26), notification badges—also known as notification dots—appear on a launcher icon when the associated app has an active notification. Users can touch & hold the app icon to reveal the notifications, along with any app shortcuts.

@windows7lake my device is a Samsung a22 5g with Android 13 and One UI 5.1

@RuiTB  Sorry. I had try to figure out a solution to solve this problem. But find no way form samsung develper website. It seems to have nothing to do on it, the badges just control by launcher.
According to the description of the official open document of Android：

Starting with Android 8.0 (API level 26), notification badges—also known as notification dots—appear on a launcher icon when the associated app has an active notification. Users can touch & hold the app icon to reveal the notifications, along with any app shortcuts.

@RuiTB I think You should use system default Badge, actually you should use this package under Android 12.
From Android 12, I believe android system manage the badges you should not override it.
Give it condition like
bool get _isAndroidAutoManageBadge {
return int.parse(Platform.operatingSystemVersion.split('.')[0]) >= _androidAutoManageBadgeVersion;
}
if (!_isAndroidAutoManageBadge) {
// process your badge logic here
}
I hope it helps


Lambda dogbox whatever

coverage: 74.471% (-0.08%) from 74.555%
when pulling e0916b07da95da01331f7717ddc7067ad028c9bf on lambda-dogbox
into 88d973a45b3d7f1df54bea944f9598f2c972702c on master.


Exporting certain info from this chart so that it can be consumed by other charts/applications

I was trying to port https://github.com/validatedpatterns/medical-diagnosis to use this chart and noticed the following pattern. In that pattern they export service url and external url into a configmap. This configmap gets created directly in the namespace that will then reference it:
apiVersion: v1
kind: ConfigMap
metadata:
  name: service-point
  namespace: "{{ .Values.global.xraylab.namespace }}"
  annotations:
    argocd.argoproj.io/sync-wave: "-4"
data:
  url: "{{ .Values.odf.serviceUrl }}"
  url-external: "{{ .Values.odf.externalUrl }}.apps.{{ .Values.global.datacenter.clustername }}.{{ .Values.global.datacenter.domain }}"

Then applications will use it like this:
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: risk-assessment
  namespace: {{ .Values.global.xraylab.namespace }}
  annotations:
    argocd.argoproj.io/sync-wave: "20"
    argocd.argoproj.io/compare-options: IgnoreExtraneous
spec:
  template:
    metadata:
        annotations:
          autoscaling.knative.dev/target: '1'
          revisionTimestamp: ''
    spec:
      containers:
      - image: quay.io/rh-data-services/xraylab-risk-assessment:latest
        ports:
        - containerPort: 5000
        env:
...
          valueFrom:
            configMapKeyRef:
              name: service-point
              key: url

So I was wondering what our options are to tackle this. Fundamentally this boils down to "Can helm use values from another chart?" The answer to that is pretty much a "No, it cannot"
So I can think of the following approaches of the top of my head:

We simply let the chart that needs this replicate those two values somehow on their own. This is probably the simplest approach, although if somebody tweaks the values in the ODF charts that won't be reflected anywhere else.
We add a configmap where we export some of this data. This has the drawback that a configmap is useful only in the namespace where it will be used and the ODF chart has no knowledge of these namespaces. So the other parts of a pattern would still need to find a way to copy this configmap in other namespaces
Some other clever mechanism I have not thought of

I am sort of leaning towards 1. but I'd like to get some feeback from others before going down this path

2 but we allow the destination namespace to be configurable?

Or a list?

Yeah either we do 2) with a list or we just use .Values.odf.serviceUrl & co in the consumer, that way a global override would "just work (TM)". Maybe doing 2 is more explicit and hence a bit preferable?

Spoke to Jonny and since it seems a pretty niche requirement for medical diagnosis and the values are pretty much hardcoded, we will just create that configmap in that pattern and keep this chart a bit simpler.


Pipeline/build fails with: AWS Control Tower cannot deploy the required stack set.

AWS Control Tower failed to set up your landing zone completely: AWS Control Tower cannot deploy the required stack set. To continue, add the AWS CloudFormation service to the trust relationship for the AWSControlTowerStackSetRole and try again. Learn more

Count: 1
References:

https://eu-west-1.console.aws.amazon.com/codesuite/codebuild/824014778649/projects/BuildAndTestProject-cF59jfsVuO1q/build/BuildAndTestProject-cF59jfsVuO1q%3A60f3642d-527a-48cb-b556-8c5e1ccdbaa9?region=eu-west-1

has not been happening a long time, so closing here


Vedic sunset/sunrise?

I try to use the functions nextSunrise, nextSunset, lastSunrise, lastSunset. I noticed that the data differs from my astrology software Maitreya8.
For example for 2022/04/07,
Charleston = GeoPos (32.861389, -79.903611)
CharlestonTZ = pytz.timezone('US/Eastern')

I get:
lastSunrise<2022/04/07 06:59:35 -04:00:00>
lastSunset<2022/04/07 19:44:20 -04:00:00>
nextSunrise<2022/04/08 06:58:19 -04:00:00>
nextSunset<2022/04/08 19:45:03 -04:00:00>

however Maireya8 shows me:
2022-04-07
Sunrise: 07:02:43
Sunset: 19:40:09
2022-04-08
Sunrise: 07:01:28
Sunset: 19:40:51
That's quite a big difference.
So I found swisseph manual which states:

The astronomical sunrise is defined as the time when the upper limb of the solar disk is seen appearing at the horizon. The astronomical sunset is defined as the moment the upper limb of the solar disk disappears below the horizon.
The function swe_rise_trans() by default follows this definition of astronomical sunrises and sunsets. Also, astronomical almanacs and newspapers publish astronomical sunrises and sunset according to this definition.
Hindu astrology and Hindu calendars use a different definition of sunrise and sunset. They consider the Sun as rising or setting, when the center of the solar disk is exactly at the horizon. In addition, the Hindu method ignores atmospheric refraction. Moreover, the geocentric rather than topocentric position is used and the small ecliptic latitude of the Sun is ignored.
In order to calculate correct Hindu rising and setting times, the flags SE_BIT_NO_REFRACTION and SE_BIT_DISC_CENTER must be added (or'ed) to the parameter rsmi. From Swiss Ephemeris version 2.06 on, a flag SE_BIT_HINDU_RISING is supported. It includes the flags SE_BIT_NO_REFRACTION, SE_BIT_DISC_CENTER and SE_BIT_GEOCTR_NO_ECL_LAT.

So I tried the following code:
print (Datetime.fromJD(swe.rise_trans(swe.julday(2022, 4, 7), swe.SUN, self.data.lat, self.data.long, 0, 0, 0, swe.CALC_RISE, swe.BIT_DISC_CENTER)[1][0], "-04:00"))
print (Datetime.fromJD(swe.rise_trans(swe.julday(2022, 4, 7), swe.SUN, self.data.lat, self.data.long, 0, 0, 0, swe.CALC_SET, swe.BIT_DISC_CENTER)[1][0], "-04:00"))

But what I'm getting is very crazy data:
<2022/04/08 02:24:39 -04:00:00>
<2022/04/07 09:24:09 -04:00:00>

Any idea what I'm doing wrong here?
Thanks for any help!

I just made it work! I use the following version - which is probably too cumbersome but at least it works.
sunrise = Datetime.fromJD(swe.rise_trans(jd_start=swe.julday(int(self.date.strftime("%Y")), int(self.date.strftime("%m")), int(self.date.strftime("%d"))), body=swe.SUN, lon=self.long, lat=self.lat, rsmi=swe.CALC_RISE | swe.BIT_HINDU_RISING)[1][0], offsetformated)


mitmproxy will not run using Python 3.7.0

Installed mitmproxy and started it.
Following message was returned:
############################################################################
mitmproxy requires Python 3.6 or higher!

Please upgrade your Python intepreter or use our mitmproxy binaries from
https://mitmproxy.org. If your operating system does not include the
required Python version, you can try using pyenv or similar tools.
############################################################################
System information
sam-precision-m4800
description: Laptop
product: Precision M4800 (05CC)
vendor: Dell Inc.
version: 00
serial: CFJBR52
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 vsyscall32
configuration: boot=normal chassis=laptop sku=05CC uuid=44454C4C-4600-104A-8042-C3C04F523532
*-core
description: Motherboard
product: 0X3C7N
vendor: Dell Inc.
physical id: 0
version: A00
serial: /CFJBR52/CN1296355BGEL9/
*-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A19
date: 05/14/2017
size: 64KiB
capacity: 11MiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz
vendor: Intel Corp.
physical id: 43
bus info: cpu@0
version: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz
slot: SOCKET 0
size: 954MHz
capacity: 3900MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti retpoline tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts cpufreq
configuration: cores=4 enabledcores=4 threads=8
*-cache:0
description: L1 cache
physical id: 44
slot: CPU Internal L1
size: 256KiB
capacity: 256KiB
capabilities: internal write-back
configuration: level=1
*-cache:1
description: L2 cache
physical id: 45
slot: CPU Internal L2
size: 1MiB
capacity: 1MiB
capabilities: internal write-back unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: 46
slot: CPU Internal L3
size: 8MiB
capacity: 8MiB
capabilities: internal write-back unified
configuration: level=3
*-memory
description: System Memory
physical id: 47
slot: System board or motherboard
size: 16GiB
*-bank:0
description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
product: EBJ81UG8EFU0-GN-F
vendor: Elpida
physical id: 0
serial: FCACABD5
slot: DIMM B
size: 8GiB
width: 64 bits
clock: 1600MHz (0.6ns)
*-bank:1
description: DIMM [empty]
product: [Empty]
vendor: [Empty]
physical id: 1
serial: [Empty]
slot: DIMM C
*-bank:2
description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
product: EBJ81UG8EFU0-GN-F
vendor: Elpida
physical id: 2
serial: F5ACAB8B
slot: DIMM A
size: 8GiB
width: 64 bits
clock: 1600MHz (0.6ns)
*-bank:3
description: DIMM [empty]
product: [Empty]
vendor: [Empty]
physical id: 3
serial: [Empty]
slot: DIMM D
*-pci
description: Host bridge
product: Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 06
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pci pm msi pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:16 ioport:e000(size=4096) memory:f7e00000-f7efffff ioport:e0000000(size=268435456)
*-generic:0
description: Unassigned class
product: Illegal Vendor ID
vendor: Illegal Vendor ID
physical id: 0
bus info: pci@0000:01:00.0
version: ff
width: 32 bits
clock: 66MHz
capabilities: bus_master vga_palette cap_list rom
configuration: driver=radeon latency=255 maxlatency=255 mingnt=255
resources: irq:29 memory:e0000000-efffffff memory:f7e00000-f7e3ffff ioport:e000(size=256) memory:f7e40000-f7e5ffff
*-generic:1
description: Unassigned class
product: Illegal Vendor ID
vendor: Illegal Vendor ID
physical id: 0.1
bus info: pci@0000:01:00.1
version: ff
width: 32 bits
clock: 66MHz
capabilities: bus_master vga_palette cap_list
configuration: driver=snd_hda_intel latency=255 maxlatency=255 mingnt=255
resources: irq:17 memory:f7e60000-f7e63fff
*-display
description: VGA compatible controller
product: 4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:30 memory:f5800000-f5bfffff memory:d0000000-dfffffff ioport:f000(size=64) memory:c0000-dffff
*-multimedia:0
description: Audio device
product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:00:03.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:33 memory:f7f34000-f7f37fff
*-usb:0
description: USB controller
product: 8 Series/C220 Series Chipset Family USB xHCI
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:00:14.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:26 memory:f7f20000-f7f2ffff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 4.13.0-37-generic xhci-hcd
physical id: 0
bus info: usb@3
logical name: usb3
version: 4.13
capabilities: usb-2.00
configuration: driver=hub slots=15 speed=480Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 4.13.0-37-generic xhci-hcd
physical id: 1
bus info: usb@4
logical name: usb4
version: 4.13
capabilities: usb-3.00
configuration: driver=hub slots=6 speed=5000Mbit/s
*-communication
description: Communication controller
product: 8 Series/C220 Series Chipset Family MEI Controller #1
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=mei_me latency=0
resources: irq:31 memory:f7f40000-f7f4000f
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eno1
version: 04
serial: 34:e6:d7:5c:bc:2b
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.13-3 latency=0 link=no multicast=yes port=twisted pair
resources: irq:28 memory:f7f00000-f7f1ffff memory:f7f3d000-f7f3dfff ioport:f080(size=32)
*-usb:1
description: USB controller
product: 8 Series/C220 Series Chipset Family USB EHCI #2
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:16 memory:f7f3c000-f7f3c3ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 4.13.0-37-generic ehci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 4.13
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
vendor: Intel Corp.
physical id: 1
bus info: usb@1:1
version: 0.04
capabilities: usb-2.00
configuration: driver=hub slots=6 speed=480Mbit/s
*-multimedia:1
description: Audio device
product: 8 Series/C220 Series Chipset High Definition Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:32 memory:f7f30000-f7f33fff
*-pci:1
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:16 ioport:2000(size=4096) memory:cf200000-cf3fffff ioport:cf400000(size=2097152)
*-pci:2
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #3
vendor: Intel Corporation
physical id: 1c.2
bus info: pci@0000:00:1c.2
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:18 memory:f5c00000-f5efffff
*-network
description: Wireless interface
product: BCM4352 802.11ac Wireless Network Adapter
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlp3s0
version: 03
serial: ac:e0:10:5b:14:83
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=<IP_ADDRESS>1 (r587334) ip=<IP_ADDRESS> latency=0 multicast=yes wireless=IEEE 802.11
resources: irq:18 memory:f5e00000-f5e07fff memory:f5c00000-f5dfffff
*-pci:3
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #4
vendor: Intel Corporation
physical id: 1c.3
bus info: pci@0000:00:1c.3
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:19 ioport:d000(size=4096) memory:f7300000-f7cfffff ioport:f1400000(size=10485760)
*-pci:4
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #5
vendor: Intel Corporation
physical id: 1c.4
bus info: pci@0000:00:1c.4
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:16 ioport:c000(size=4096) memory:f6900000-f72fffff ioport:f0a00000(size=10485760)
*-pci:5
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #7
vendor: Intel Corporation
physical id: 1c.6
bus info: pci@0000:00:1c.6
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:18 ioport:a000(size=8192) memory:f5f00000-f68fffff ioport:f0000000(size=10485760)
*-pci:6
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #8
vendor: Intel Corporation
physical id: 1c.7
bus info: pci@0000:00:1c.7
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:19 memory:f7d00000-f7dfffff
*-generic
description: SD Host controller
product: SD/MMC Card Reader Controller
vendor: O2 Micro, Inc.
physical id: 0
bus info: pci@0000:11:00.0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=sdhci-pci latency=0
resources: irq:19 memory:f7d01000-f7d01fff memory:f7d00000-f7d007ff
*-usb:2
description: USB controller
product: 8 Series/C220 Series Chipset Family USB EHCI #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:21 memory:f7f3b000-f7f3b3ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 4.13.0-37-generic ehci_hcd
physical id: 1
bus info: usb@2
logical name: usb2
version: 4.13
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
vendor: Intel Corp.
physical id: 1
bus info: usb@2:1
version: 0.04
capabilities: usb-2.00
configuration: driver=hub slots=8 speed=480Mbit/s
*-usb:0
description: Generic USB device
product: BCM20702A0
vendor: Broadcom Corp
physical id: 5
bus info: usb@2:1.5
version: 1.12
serial: ACE0105B1484
capabilities: usb-2.00
configuration: driver=btusb speed=12Mbit/s
*-usb:1 UNCLAIMED
description: Generic USB device
product: 5880
vendor: Broadcom Corp
physical id: 8
bus info: usb@2:1.8
version: 1.01
serial:<PHONE_NUMBER>ABCD
capabilities: usb-1.10
configuration: maxpower=100mA speed=12Mbit/s
*-isa
description: ISA bridge
product: QM87 Express LPC Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: driver=lpc_ich latency=0
resources: irq:0
*-storage
description: RAID bus controller
product: 82801 Mobile SATA Controller [RAID mode]
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 04
width: 32 bits
clock: 66MHz
capabilities: storage msi pm bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:27 ioport:f0d0(size=8) ioport:f0c0(size=4) ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f060(size=32) memory:f7f3a000-f7f3a7ff
*-serial UNCLAIMED
description: SMBus
product: 8 Series/C220 Series Chipset Family SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 04
width: 64 bits
clock: 33MHz
configuration: latency=0
resources: memory:f7f39000-f7f390ff ioport:f040(size=32)
*-scsi:0
physical id: 1
logical name: scsi0
capabilities: emulated
*-disk
description: ATA Disk
product: ST500LM000-1EJ16
vendor: Seagate
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: DEMC
serial: W764W5ZN
size: 465GiB (500GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=557fc104
*-volume:0
description: Windows NTFS volume
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
version: 3.1
serial: 4801-e201
size: 498MiB
capacity: 500MiB
capabilities: primary bootable ntfs initialized
configuration: clustersize=4096 created=2017-11-28 13:45:05 filesystem=ntfs label=System Reserved modified_by_chkdsk=true mounted_on_nt4=true resize_log_file=true state=dirty upgrade_on_mount=true
*-volume:1
description: Windows NTFS volume
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 3.1
serial: 1a0a957c-6296-6e40-8db7-b9a506d25ec5
size: 318GiB
capacity: 318GiB
capabilities: primary ntfs initialized
configuration: clustersize=4096 created=2017-11-28 13:45:14 filesystem=ntfs state=clean
*-volume:2
description: Windows NTFS volume
physical id: 3
bus info: scsi@0:0.0.0,3
logical name: /dev/sda3
version: 3.1
serial: 187c-1c4f
size: 459MiB
capacity: 475MiB
capabilities: primary ntfs initialized
configuration: clustersize=4096 created=2017-11-28 18:49:09 filesystem=ntfs modified_by_chkdsk=true mounted_on_nt4=true resize_log_file=true state=dirty upgrade_on_mount=true
*-volume:3
description: Extended partition
physical id: 4
bus info: scsi@0:0.0.0,4
logical name: /dev/sda4
size: 146GiB
capacity: 146GiB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume:0
description: Linux swap / Solaris partition
physical id: 5
logical name: /dev/sda5
capacity: 15GiB
capabilities: nofs
*-logicalvolume:1
description: Linux filesystem partition
physical id: 6
logical name: /dev/sda6
logical name: /
capacity: 130GiB
configuration: mount.fstype=ext4 mount.options=rw,relatime,errors=remount-ro,data=ordered state=mounted
*-scsi:1
physical id: 2
logical name: scsi1
capabilities: emulated
*-cdrom
description: DVD reader
product: DVD-ROM DU-8D5LH
vendor: PLDS
physical id: 0.0.0
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/dvd
logical name: /dev/sr0
version: FD11
capabilities: removable audio dvd
configuration: ansiversion=5 status=nodisc
*-battery
product: DELL GXMW9D1
vendor: SMP
physical id: 1
version: 03/31/2015
serial: 0AB0
slot: Sys. Battery Bay
capacity: 66600mWh
configuration: voltage=11.1V

How did you install mitmproxy?
Which Python version are you using?
What operating system and version?
Please post the output of mitmproxy --version.

OS is:                             Ubuntu 18.04
mitmproxy is:                  4.0.3
'mitmproxy --version' returns message I have to have Python 3.6 or higher.
I have installed Python 3.7.0 but command  'Python3 --version' returns that I have 3.5.2 installed.
Will ferret out that problem and get back here later.

Thanks for closing.

I am getting the same error. What did you find?

I had a similar problem, then realized that I need to reinstall the mitmproxy after upgrading to Python 3.7


CDS API Changes

Hello, it looks like CDS will be completely moving to CDS-Beta on September 26th, with legacy CDS no longer accessible after this date:
https://forum.ecmwf.int/t/the-new-climate-data-store-beta-cds-beta-is-now-live/3315
From their website, it appears the front-end, back-end, and cloud infrastructure will all be changing. How should we accommodate for this in the existing CDS data requests, such as in the example notebooks?

Any update on this ?


Update to 3.15

Is there a task or vision to update esri from 3.13 to 3.15 and to swap from slurp over to a bower install or those artifacts?

Not really, I have recently worked on a project where we used Dojo-Bootstrap w/ JSAPI 3.15 and a bower build, so I can confirm that it all works.
Pull requests are welcome!
However, I personally don't start my projects w/ Dojo-Bootstrap these days. I find that unless it's essentially an entirely mobile-focused project, the pros of avoiding jQuery don't outweigh the cons.
Also, the Dojo-Bootstrap project does not (as far as I'm aware) have a plan to support the upcoming release of Bootstrap 4.

Thanks Tom!  I see your point on that.  If I do have time I might work on a pull request.
Would you guys have other repos on here that I can look at to mimic my projects.  I've tried a couple of yeoman generators but didn't like the structure.  I liked this one for the use of Grunt, with building out dojo profiles and everything. Hoping to learn more at the developer summit!  Thanks again.


Support Request: How do I add my August Lock using your plugin?

Describe Your Problem
No QR code so how do I add this to HomeKit?
Relevant log output
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found
[7/28/2024, 8:08:48 PM] Registering platform 'homebridge-august.August'
[7/28/2024, 8:08:48 PM] [August] Loaded homebridge-august v2.2.7-beta.24 child bridge successfully
[7/28/2024, 8:08:48 PM] Loaded 0 cached accessories from cachedAccessories.0EFEED1CCD50.
[7/28/2024, 8:08:48 PM] [August] Validated, Discover Devices: ReferenceError: Config errors found:
Missing config.installId or AUGUST_INSTALL_ID env var
[7/28/2024, 8:08:48 PM] Homebridge v1.8.4 (HAP v0.12.2) (August) is running on port 32891.
[7/28/2024, 8:08:48 PM]

NOTICE TO USERS AND PLUGIN DEVELOPERS
> Homebridge 2.0 is on the way and brings some breaking changes to existing plugins.
> Please visit the following link to learn more about the changes and how to prepare:
> https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0

Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found
[7/28/2024, 8:08:49 PM] [Garage Door] Restoring existing accessory from cache: Garage (id: E0FFF13EC1B1_1)

Config for homebridge-august
{
    "name": "August",
    "credentials": {
        "augustId"<EMAIL_ADDRESS>        "password": "deletedforsecurity",
        "notice": "Keep your tokens a secret!",
        "isValidated": true
    },
    "platform": "August",
    "_bridge": {
        "username": "0E:FE:ED:1C:CD:50",
        "port": 32891
    }
}

Screenshots

Not sure where I find the QR code or do I hold it close to the August Lock?

Device & Model
August Smart Lock + Connect
Node.js Version
v20.16.0
NPM Version
not sure
Homebridge Version
243-50-078
Homebridge August Plugin Version
v2.2.7-beta.24
Homebridge Config UI X Plugin Version
No response
Operating System
It's running on my Synology 920+

For some reason you have no installID. Remove the invalid config and try validating again.

It’s been a while messing with code, do you mean remove that line of code in the config? On Jul 29, 2024, at 12:07 AM, Donavan Becker @.***> wrote:
For some reason you have no installID. Remove the invalid config and try validating again.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

It’s been a while messing with code, do you mean remove that line of code in the config?

You just need to go into your plugin config to remove that so the plugin can re-validate.

I get this now. I get a QR code to add it to my homekit network but it
never shows up anywhere for me to lock and unlock the door...
Any advice? Thanks!
[image: Screen Shot 2024-07-31 at 1.37.54 PM.png]
[image: Screen Shot 2024-07-31 at 1.36.53 PM.png]
On Mon, Jul 29, 2024 at 9:17 AM Donavan Becker @.***>
wrote:

It’s been a while messing with code, do you mean remove that line of code
in the config?
You just need to go into your plugin config to remove that so the plugin
can re-validate.
—
Reply to this email directly, view it on GitHub
https://github.com/donavanbecker/homebridge-august/issues/128#issuecomment-2255917133,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKFG3QZBMAGHTSTLUTIKX4TZOY6E7AVCNFSM6AAAAABLTHHJSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJVHEYTOMJTGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

No real support. lol yea GitHub points. On Aug 31, 2024, at 7:47 AM, github-actions[bot] @.***> wrote:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

No real support. lol yea GitHub points.

Some people have lives. So you added the child bridge?

Yes, It’s all good, I don’t need it anymore. Buying a unifi locking solution.Thanks for reply please continue with life. It really is more important than side repos. Sorry for my curt response.On Aug 31, 2024, at 9:03 AM, Donavan Becker @.***> wrote:
No real support. lol yea GitHub points.
Some people have lives. So you added the child bridge?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


composition API dashboard

What this PR does / why we need it (변경 내용 / 필요성):
composition API dashboard
Which issue(s) this PR fixes (관련 이슈):

#122

Special notes for your reviewer (리뷰어에게 하고 싶은 말):
Thank you.
Additional documentation, usage docs, etc. (기타 관련 문서, 사용법 등):
https://vuejs.org/guide/typescript/composition-api.html

Codecov Report
Attention: 267 lines in your changes are missing coverage. Please review.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

pkg/alerter/alerter.go
100.00% <100.00%> (ø)

pkg/handler/handle_spa.go
33.33% <ø> (ø)

pkg/handler/handler.go
100.00% <100.00%> (ø)

pkg/handler/probe.go
100.00% <100.00%> (ø)

pkg/handler/router.go
100.00% <100.00%> (ø)

pkg/handler/status.go
100.00% <100.00%> (ø)

pkg/mocker/context.go
100.00% <100.00%> (ø)

pkg/service/alerting/types.go
100.00% <100.00%> (ø)

pkg/service/datasource/datasource.go
100.00% <100.00%> (ø)

pkg/service/status/status.go
100.00% <100.00%> (ø)

... and 23 more

:loudspeaker: Thoughts on this report? Let us know!.


Contribute

Again, much appreciate this project.  Are you taking any contributions? I'd like to add timezone and other options?

Definitely, I welcome contributions.
Maybe I should add that to the README.


Parameters twisted for GetConsentKey

Hey guys,
on my way though the code which writes into the PersistedGrants table I found these bits of code which seem to be wrong.
The first parameter of the GetConsentKey function is the subjectId and the second one is the clientId. But all invocations of this method pass clientId as first and subjectId as second parameter. This seems wrong to me.
I guess this is not evil but at least not really clean.
https://github.com/IdentityServer/IdentityServer4/blob/74827bc4df39c2234d9490ba5ce032ce806ab475/src/IdentityServer4/Stores/Default/DefaultUserConsentStore.cs#L34-L48

Merged and fixed, thanks!


Allow for names with spaces

On the first run, the user has to set the player name. Unfortunately the player name will not include characters after a space in the name. So if you enter John Doe as the player name, the name will be saved as John.

Just sent over a PR :)

scanf("%[^\n]s", score);
or getline(cin,str);


InsertManyWriteConcernException should extend BulkWriteException

When doing a bulkInsert into an MongoDb, that already has conflicting data in it, the following code throwns an InsertManyWriteConcernException if executed using Fongo:
      BulkWriteOperation bulkWriteOperation = collection.getDbCollection().initializeOrderedBulkOperation();
      dbObjects.forEach(bulkWriteOperation::insert);
      bulkWriteOperation.execute();

The InsertManyWriteConcernException is not part of the actual Mongo driver and therefore never thrown in a production-enviroment. If the InsertManyWriteConcernException would extend BulkWriteException you could catch the same Exception as you would while running with an actual MongoDB. Is there a reason, why you decided to throw your own Exception instead of the one used in the official driver?

I think this was fixed in #334 and was merged in master. The problem is that the latest stable version 2.1.1 is behind master (currently on fa0d307). Only the 2.2 RCs include the fix. Some more discussion was made on #343.


basic linting

I just wanted to go to bed and see this again 🤣 . Can we first only do stuff like formatting? And take it step by step? This gives me a real headache.

If everything apart from the formatting (and things like only allow braceless return inside if it is a oneliner) is removed this is OK.
I think having the linter being more strict about const-correctness is fine but I also would defer this, as already said in some of the other PRs.
Same goes for explicit and default for Ctor declarations. It is not a bad idea to use but sometimes they change things in a way one doesn't expect.

This gives me a real headache.
That's why I did the initial review ;)

If everything apart from the formatting (and things like only allow braceless return inside if it is a oneliner) is removed this is OK.

Yes, there's not actually that much else going on (some of my comments are repetitions of the same rules).

I think having the linter being more strict about const-correctness is fine but I also would defer this, as already said in some of the other PRs.
Same goes for explicit and default for Ctor declarations. It is not a bad idea to use but sometimes they change things in a way one doesn't expect.

Then I'd suggest to convert the const, default and explicit to lint warnings (that one can choose to ignore), so they are not auto-formatted.
I think we should also probably disable the max. line length, this should also hopefully allow own linebreaks there again.
And we shouldn't force (but allow?) inlined structs / function returns.
Then the diff probably reduces substantially compared to what it currently is, but we still have a linter/formatted for the basic stuff in place.


README: Add a logo

Surely, we gotta have a cute :whale: whale + doctor (medical or PhD) combination logo at the top of the README: a whale with a graduation cap, a whale with a stethoscope, a whale with a test tube?

For now added Stencila https://github.com/stencila/dockter/commit/b1e62dfddc424677d9c25a7d451ca6b4fa491f62


Featuer dashboardv2 design

What type of PR is this?
This PR if for the proposal of overwriting the Karmada dashboard.

/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/assign @RainbowMango


Backtick parsing issue when inside code block

Example: https://github.com/lucaslorentz/caddy-docker-proxy/pull/170/files/d7b7e438515d8d05bf86d42de17c8f5983ab6963..fa5dd9cb1b4257fd48c8ff1cd1b8132d94660e9b#r458945992
This comment has backticks inside the code block, but when viewed on this page, they go missing. See here instead on the main issue page instead of the review page: https://github.com/lucaslorentz/caddy-docker-proxy/pull/170#discussion_r458945992

https://github.com/sindresorhus/refined-github/blob/a82f849bd4a745542642b9453c12a6ec18c381aa/source/features/parse-backticks.tsx#L31


[MVCC PR] Improve forward scan

What have you changed? (mandatory)
This PR is an improvement over the proposed Mvcc refinement PR.
It:

Mostly removes the usage of near_seek in forward scan
Prevents key clone in more cases
Adds very verbose comments

What are the type of the changes? (mandatory)

Improvement (non-breaking change which is an improvement to an existing feature)

How has this PR been tested? (mandatory)
CI
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Later.
Add a few positive/negative examples (optional)

@MyonKeminta @zhangjinpeng1987 PTAL

Please share the bench results.

Will there be benchmark results for this single PR?

Rest LGTM

@MyonKeminta might not. There might be a benchmark for this impl and our original MvccReader.

/run-integration-tests


code cleanup: virt-launcher: Handle unhandled error

What this PR does / why we need it:
The error returned from many functions was simply ignored, and it was not clear if that is intentional or a bug.
This PR either marks these errors as intentionally ignored, or handles them.
Release note:
None

/sig code-quality

Ok, I will split this into multiple PRs, and leave out the ones I'm unsure about.
/close


Jm/ts host sig

This implements typescript support for the runtime/host.

Tidied up and started as fresh branch / PR https://github.com/loopholelabs/scale/pull/29


Increase gRPC message size

Hello,
I encountered the following error while running a task with TPI:
│ Error: Plugin error
│
│   with iterative_task.data-segmentation,
│   on main.tf line 6, in resource "iterative_task" "data-segmentation":
│    6: resource "iterative_task" "data-segmentation" {
│
│ The plugin returned an unexpected error from plugin.(*GRPCProvider).PlanResourceChange: rpc error: code =
│ ResourceExhausted desc = grpc: received message larger than max (9953646 vs. 4194304)

Due to the error, the provisioned EC2 instance stopped producing expected outputs, but still kept running. I could not run terraform destroy and had to terminate the instance and all other resources manually.
When running the same task on a smaller subset of data, the task completes successfully.
If I understand correctly, gRPC uses the default 4MB message size unless configured to allow a larger size. Is there a way for TPI plugin users to configure this setting?
Environment Details:
Terraform v1.5.7
on linux_amd64
+ provider registry.terraform.io/iterative/iterative v0.11.19

@LahiLuk I'll have to look into it, can you share a minimal example that will result in the error? If it is as simple as adding an option when we initialize the gcp client feel free to open a PR yourself, currently, I can't give you a timeline as to when I can resolve this.

Hi @dacbd,
anything that will produce a log larger than 4 MB should result in the error. Here's an example:
terraform {
  required_providers { iterative = { source = "iterative/iterative" } }
}
provider "iterative" {}

resource "iterative_task" "grpc-error-example" {
  cloud   = "aws"
  machine = "t2.micro"
  spot    = -1
  image   = "ubuntu"
  region = "eu-west-1"

  storage {
    workdir = ""
    output = ""
  }
  script = <<-END
    #!/bin/bash
    while true; do
      echo "Hello, World!"
      sleep 0.01  # Slow down log creation a bit
    done
  END
}

I'm not sure if I'll be able to open a PR since I'm new to Terraform, and I've never used Go, but I'll try and look into it.
It seems in any case that other providers were able to increase the maximum message size, see for example terraform-plugin-go.
In the meantime, do you have a suggestion for a workaround? A crude one I came up with is to redirect all shell output to a file, but that complicates log monitoring... Since TPI is geared towards running ML experiments, I find it a bit weird that no one ran into this issue yet, since those logs tend to be quite detailed and the datasets large...

@dacbd,
I also forgot to mention... It seems that the task itself actually keeps on running after the error, and the logs keep being written to s3. It's just that any terraform commands run locally fail with the error.

@0x2b3bfa0 can you try and take a look at this, I'm hoping it might be as simple as updating our terraform-provider-sdk, or we need to add something more to the plugin.Serve https://github.com/iterative/terraform-provider-iterative/blob/763e7a1026bca3d31790727c52dacb5e02e98abf/main.go#L13C2-L17


chore: bdd-sbhg-1587768132 to 0.0.1

chore: Promote bdd-sbhg-1587768132 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


feat: init ark lib + tests

resolves #254

I am closing this one as this duplicates #273 and have too much stuff from different topics done in the same PR.
I will split those afterwards


proposed copy edits to rustdoc chapter

(updating a link, and making commands more literally copy-pasteable)

So doxidize is officially the future rustdoc 2?

@steveklabnik ^^ What, if anything, should be said about future-rustdoc?

I think, for now, we should simply remove the references to this project. It's not in a state where we want people to poke at it, and it's not going to be until the fall, at least.

Ping @zackmdavis

@mark-i-m pong (just scrapped the sentence entirely)

Thanks!


Added a useful resource

Have added a useful resource about the data structures & algorithm from the scaler topics in the reference section.

That's awesome @Vaishnaviamirayada! Thanks for collaborating.


Added DawnScanner json report importer

I followed these instructions to add dawnscanner JSON report importer (https://github.com/thesp0nge/dawnscanner).
dawnscanner is another security scanner for ruby web applications, including Rails, Sinatra and Padrino.
dawnscanner supports JSON output (with -j option)

@jaguasch Thanks for the submission. Would you mind fixing these linting errors and submitting a sample file to this repo?
Found violations: dojo/tools/dawnscanner/parser.py
	E302 @ 8:1 - expected 2 blank lines, found 1
	W291 @ 9:40 - trailing whitespace
	W293 @ 30:1 - blank line contains whitespace
Found violations: dojo/tools/factory.py
	W291 @ 137:47 - trailing whitespace
The command "./travis/script.sh" exited with 1.

@jaguasch Thanks for the submission. Would you mind fixing these linting errors and submitting a sample file to this repo?
Found violations: dojo/tools/dawnscanner/parser.py
	E302 @ 8:1 - expected 2 blank lines, found 1
	W291 @ 9:40 - trailing whitespace
	W293 @ 30:1 - blank line contains whitespace
Found violations: dojo/tools/factory.py
	W291 @ 137:47 - trailing whitespace
The command "./travis/script.sh" exited with 1.

@aaronweaver  here is the PR with the sample-scan-file for dawnscanner tool https://github.com/DefectDojo/sample-scan-files/pull/12 and already commited flake8 fixes

@aaronweaver good to merge?


Securing HTTP In end points

We currently only support naive basic auth security against HTTP In node end points via the httpNodeAuth setting. We need a more flexible, secure solution to this.
We recently introduced adminAuth setting to improve the security of the admin api. This was done with credential based oauth initially, but with a mind to how it could be extended to other schemes.
We were able to benefit from being opionated as to how our own admin api should be secured. I don't think we can be as opionated when it comes to how users are able to secure the HTTP Apis they create within Node-RED.
I think there are two possible approaches:

be opinionated and define a settings object (like adminAuth) that encapsulates the configuration of some auth scheme for the http nodes.
allow the user to define their own middleware, via settings.js, that would apply to all http routes (not admin ones). This middleware would be inserted at the start of the HTTP route handlers (probably after parsers etc, but certainly before the node-defined middleware. The user can then write whatever authentication scheme they want.

I'm currently erring towards option 2

Would it be possible to support node-specific auth{entication,orization} settings? E.g. if you want one particular endpoint to allow X but another to allow Y,Z?

The immediate requirement we have is to enable a single auth scheme to all http nodes - which this issue covers. The use case we have is also suited to doing this via settings.js rather than within the editor itself.
That doesn't mean we wouldn't extend it to support multiple schemes in the future - although that poses a number of design challenges, such as how each node gets configured to the appropriate auth scheme, how much is done via settings versus in the editor etc.

Could this middleware be used to address this issue with Node-Red on Bluemix:  https://github.com/node-red/node-red-bluemix/issues/7 ?
Perhaps httpNodeMiddleware should also be able to take an array of middlewares so that several can be added at a time?

@deldrid1 the plan is to support an array of them, but I wanted to get the single-case in to satisfy an immediate need.
This could absolutely be used to enforce https to the http nodes - but wouldn't do it for the editor itself. I meant to ask, is your requirement to do this just for the nodes, or the whole thing?

I would like to support securing the whole thing.  Secure nodes with an insecure node/flow editor doesn't seem very secure :)

We added the adminAuth option in 0.10:
http://blog.nodered.org/2015/02/08/version-0-10-1-released/
On Thu, 14 May 2015 17:56 deldrid1<EMAIL_ADDRESS>wrote:

I would like to support securing the whole thing. Secure nodes with an
insecure node/flow editor doesn't seem very secure :)
—
Reply to this email directly or view it on GitHub
https://github.com/node-red/node-red/issues/631#issuecomment-102102135.

I have that turned on.  The issue is that I can't enforce HTTPS on Bluemix without some middleware on the express instance... (and since this is something that should be turned on by default IMHO, I don't want to fork https://github.com/node-red/node-red-bluemix, wrap Node-Red in an Express.JS app, and apply the middleware myself).

Ah right, I see what you meant.
Being able to enforce https will be a separate (boolean) option. The custom node middleware is primarily for a different set of use cases.

That works for me!
I just saw your commit and it looked like it might be able to address my need.  I don't mind making the changes myself but not being too familiar with the Node-Red core (and not having the time) has led to me not getting there yet...


Code comlpetion not working for variables

Bug Report

🔎 Search Terms

Completion, IntelliSense
🕗 Version & Regression Information

Tested in 'Nightly' version - the problem is not fixed.

This changed between versions 5.0.4 and 5.1.3

⏯ Playground Link

Playground link with relevant code
💻 Code

let foo: number = 1
fo

🙁 Actual behavior
Completion list ater fo does not contain foo item.
🙂 Expected behavior

Completion list ater fo contains foo item.

This has been changed in<EMAIL_ADDRESS>so the likely culprit is https://github.com/microsoft/TypeScript/pull/52690 , cc @zardoy

Huh, odd - you'd expect that ASI would kick in and have the parser act as if there's a semicolon after the 1

@DanielRosenwasser @zardoy @RyanCavanaugh issue still exists:
const obj = {
  name: '',
} as const

If I add ; semicolon it starts to work:
const obj = {
  name: '',
} as const; // <- added semicolon

TS Version: 5.2.0-dev.20230717 and same with 5.1.6
Playground: https://www.typescriptlang.org/play?ts=5.1.6#code/MYewdgzgLgBCBGArGBeGBvAUDGYCGAtgKYBcMA5OQDSYC+MeEMoksA9GzAIIAmPMAbgZh+AS1gB3EACcA1hEyYgA

@RyanCavanaugh @DanielRosenwasser  Let me know if I should open a new issue or we re-open this one


Start of github org structure doc

Issue: #42
Description
Understanding the current structure of the zalando github organizations to outline team structure, current permissions structure and org member defaults.
Delivery
Document outlining the current orgs and their team structure, including what effects this have on best practices for team workflows on github open source projects.
Types of Changes
_What types of changes does your code introduce?

Documentation/ non-code

Tasks

[ ] outline organisations and team structure
[ ] examine side effects on team workflows on github

[ ] code reviews
[ ] pull requests
[ ] branching and merging

@therealpadams - need the zalando org ownership to gather more data on its team / member structure

Added stats for the incubator org - I assume the organisation is similiar in main Zalando org - added general findings and effect on workflow - ready for review @therealpadams @princiya


Revert "Upgrade to Rails 5.1.4"

Reverts alphagov/signon#589
The migration in this PR was incorrect, and needed to be updated. To keep master in a deployable state I am reverting this for now and will create a new merge with the correct migration (currently in #591 )

The migration in this PR was incorrect, and needed to be updated. To keep master in a deployable state I am reverting this for now and will create a new merge with the correct migration (currently in #591 )

I don't know much about the context of this, but please could you put this information in the commit.

@danielburnley Has this migration already run on Integration, will merging this leave integration in an inconsistent state?
Similarly have you checked this works ok on Integration?

The original migration failed on staging so it was rolledback - as this is just a revert it will just put integration back to what it was yesterday prior to the merge


Creating S3 replication for existing buckets

Hi @TheBellman,
This repo is very helpful, but i just wanted to know how can this repo be used for existing source and destination buckets? Substituting S3 bucket ARN's would work?
Dushyant

More or less - you certainly can add your own ARNs, however to run it out of the box you might need to also set up terraform and the terraform backend.


Update local build instructions in the docs

This PR adds hints in the documentation to locally build scikit-decide with poetry.
More specifically, the documentation now indicates the environment variables that must be set prior to locally building and installing the library with poetry.
Not properly setting those environment variables can result in deactivating some options in scikit-decide, e.g. algorithm parallelism.
Those environment variables are set by the building and deployment github actions but they were not mentioned in the documentation for the people who want to build the library on their own.
The PR also updates the link to poetry's website and installation script which were outdated.

This commit adds hints in the documentation to locally build scikit-decide with poetry.
More specifically, the documentation now indicates the environment variables that must be set prior to locally building and installing the library with poetry.
Not properly setting those environment variables can result in deactivating some options in scikit-decide, e.g. algorithm parallelism.
Those environment variables are set by the building and deployment github actions but they were not mentioned in the documentation for the people who want to build the library on their own.
The commit also updates the link to poetry's website and installation script which were outdated.


Misunderstanding in the docs

Taking the text from here:

In Electron's releases page you can find archives of chromedriver, there is no difference between Electron's distribution of chromedriver and upstream ones, so in order to use chromedriver together with Electron, you will need some special setup.

The two sentences disagree with each other. From what I understand you will need some special setup should be you won't need some special setup.

The chromedriver shipped in Electron is exactly the same with the upstream one, so by default it will only work for Chrome browsers instead of custom browsers like Electron. In order to use chromedriver together with Electron you have to tell it where to find Electron and makes it think Electron is Chrome browser.
Pull request to make the document clearer is welcomed.


Test case stops working as expected when used with socket.io

Hi there!
I have written e2e test case for different functionality for the application which is in angular2-webpack-starter in which i have used socket.io. After user login i am connecting to socket server and if connection is successful then all test case are failing and giving different error for different test case and if socket is not connected then all test case works fine with no error.
what i think is this issue is because socket connection is remain open after connection to server is done and protractor is waiting to complete the angular process because of browser.ignoreSynchronization or browser.waitForAngular.
I have already asked my question on stackoverflow but i am not able to find any solution for it and because of it i am adding the same at here to know if some one also facing the same issue and found any solution for it or not.

Hi there!
I'm sorry that you haven't found any answers, but your question is still better suited for StackOverflow or Gitter.
If you find that your question is not receiving any answers, you may want to refine it by isolating your problem to a minimal, complete, verifiable example or adding more detail.
Hopefully that makes sense, good luck! 😄
Thanks!

So i just wanted to reference a solution found on a different issue which solves this issue here: https://github.com/angular/angular/issues/11853#issuecomment-277185526.


npm start > localhost:3000/test
Node 6.3.1

npm 3.10.5

Mac OS 10.11.6
Chrome 52.0.2743.116 (64-bit)
react                  15.3.0  →  15.3.1
react-dom              15.3.0  →  15.3.1
react-router            2.6.1  →   2.7.0
react-router-scroll     0.2.1  →   0.3.1 <--- rolled back
redux-immutable         3.0.7  →   3.0.8
babel-loader            6.2.4  →   6.2.5
eslint                  3.3.0  →   3.3.1
eslint-plugin-import   1.12.0  →  1.13.0
eslint-plugin-react     6.0.0  →   6.1.2
karma-chrome-launcher   1.0.1  →   2.0.0
postcss-loader          0.9.1  →  0.10.1
ERROR: app.js?2de9:126 Uncaught TypeError: __WEBPACK_IMPORTED_MODULE_10_react_router_scroll___default(...) is not a function
Caused by  react-router-scroll         0.2.1  →   0.3.0
Rolled back to 0.2.1 apparently waiting for react-router 3 https://github.com/taion/react-router-scroll/issues/28

Coverage remained the same at 98.942% when pulling 92ae4d5d8e1dc3ada439b5ce621504ddcb8521fc on gihrig:update-deps into 7bae788cf344da09a2b67545ffc788216513a653 on mxstbr:dev.

Amazing! :shipit: please merge this

Coverage remained the same at 98.942% when pulling 47c7e13eb14b3b32a65caa223c9ee483a54bd97e on gihrig:update-deps into 7bae788cf344da09a2b67545ffc788216513a653 on mxstbr:dev.

"included' the removal of the unused history see #879 thanks to @brandondurham

@mxstbr While waiting for netlify, poking around, I noticed we have a merge conflict brewing when master gets ahead of dev. Currently dev is 3 commits ahead, 4 commits behind master.
IMO the solution is to merge master into dev when any changes are made to master, which should be rare.
Do you see any reason why this should not be done now? If it's OK with you I can do this, if you like.

Please do!

@mxstbr Netlify seems to have decided to deploy all open PRs and jammed... Any ideas?

Yeah, ignore and merge :wink:

Yeah, ignore and merge 😉

@mxstbr Would that be a "manual merge" from the cli?
Thanks for taking care of this, I have been out all day.

No, I can merge PRs even when certain status checks haven't yet passed. whistle I've made Netlify un-required for now!


Fix task hover behavior & add create program button

Description of changes:

Fix task row hover behavior
Add create program button to the programs list screen
Program naming logic: Please update it to auto-generate “Disease name + Gene therapy” as the program name
Fix: If the user deletes all programs in the workspace, it should take the user back to the eligibility questionnaire. There is something funky going on right now and the page goes blank instead
Fix: Initial on the avatar should be purple instead of grey

Demo: https://master.d2lm5e4wpqbv56.amplifyapp.com
Checklist

[ ] Tests have been added and are passing
[ ] Documentation has been updated

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

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


[Enhancement] [Cherrypick] Make maximal varchar string length configurable in fe.conf and be.conf. (backport #38957)

backport #38957
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[x] This is a backport pr

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.10 out of 11 committers have signed the CLA.:white_check_mark: wyb:white_check_mark: stdpain:white_check_mark: luohaha:white_check_mark: chaoyli:white_check_mark: fzhedu:white_check_mark: packy92:white_check_mark: mingmxu:white_check_mark: fenganli:white_check_mark: Smith-Cruise:white_check_mark: liuyehcf:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


[AST] Use the correct Self PA for resolution of typealiases in protocols.

Previously, the following example
protocol P {
    associatedtype A
    typealias X = A
}
protocol Q {
    associatedtype B: P
}

func requirementOnNestedTypeAlias<T>(_: T) where T: Q, T.B.X == Int {}

would result in the generic requirements/signature of requirementOnNestedTypeAlias
being something like:
Requirements:
  τ_0_0 : Q [inferred]
  τ_0_0 : P [inferred]
  τ_0_0[.P].A == Int [explicit @ bad-type-alias.swift:14:37]
  τ_0_0[.Q].B : P [protocol @ bad-type-alias.swift:14:28]

That is, the look-up of A happens on T (aka τ_0_0) which introduces the
P conformance.

I've updated this in a fairly invasive way.

@swift-ci please smoke test

@swift-ci please smoke test

Looks like some compiler crashers regressed due to the llvm_unreachable.

Another update, removing the reimplementation of #7563, among other things.
There's an unfortunate FIXME in getNestedType that is stopping diagnostics about typealiases with mismatching types from being emitted eagerly, instead they are currently only emitted when the typealias is used.

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 4927c77e0c4aa3b48db75e29435e994ced831354
Test requested by - @huonw

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 4927c77e0c4aa3b48db75e29435e994ced831354
Test requested by - @huonw

I recommend smoke tests :)

@swift-ci Please smoke test and merge

@swift-ci please smoke test Linux


Add GitHub Action for automatic release

@jiripetrlik have you had a chance to look at this again?

Not relevant any more, closing.


Flux Helm Chart CRD deployment marked as keep is throwing reinstalls off

Describe the bug
When I try to re-install flux using helm charts (on a deployment that I have flux deleted), I get this error:
release flux failed: customresourcedefinitions.apiextensions.k8s.io "helmreleases.flux.weave.works" already exists

This is due to this change: https://github.com/weaveworks/flux/pull/1543
I'm not exactly sure of the technical details behind this, but since this was added, I assume that this is required for flux deletion to work properly. However, marking a helm release as "keep" will bring problems when the release is being installed again after deletion. This can manifest itself when trying to provision/re-provision a cluster using terraform-helm-provider (I would really like to use ansible for this, but terraform has horrible ansible support, and ansible has horrible helm support).
Helm says this:

The annotation "helm.sh/resource-policy": keep instructs Tiller to skip this resource during a helm delete operation. However, this resource becomes orphaned. Helm will no longer manage it in any way. This can lead to problems if using helm install --replace on a release that has already been deleted, but has kept resources.

On your introduction page, it recommends that the crd is not automatically created by the chart and be created separately through kubectl with a url to an outdated crd yaml (at least when compared to the crd yaml in the chart itself).
To Reproduce
Steps to reproduce the behaviour:

Add flux repo helm repo add weaveworks https://weaveworks.github.io/flux
Install flux with auto crd

$ helm install --name flux \
--set git.url=git@github.com:weaveworks/flux-get-started \
--set helmOperator.create=true \
--set helmOperator.createCRD=true \
--namespace flux \
weaveworks/flux

Delete flux: helm delete --purge flux
Install flux again

$ helm install --name flux \
--set git.url=git@github.com:weaveworks/flux-get-started \
--set helmOperator.create=true \
--set helmOperator.createCRD=true \
--namespace flux \
weaveworks/flux

Expected behavior
It should be easy to re-install flux
Proposal
There should be a separate chart to install the updated CRDs, helmOperator.createCRD should now default to false and the readme updated with new instructions to release new CRD chart first (readme should also caution users to delete flux release completely before releasing CRD)
Do let me know if you want a PR for this (since I'm going to create the separate CRD chart on my own anyway)

In our install docs we recommend the CRD to be deploying using kubectl apply https://github.com/weaveworks/flux/blob/master/site/helm-get-started.md#install-weave-flux
Moving the CRD to it's own chart will not solve the problem since Helm can't handle CRD updates, when the CRD struct changes Helm will error out see https://github.com/helm/helm/issues/5853
Since Helm doesn't implement a 3-way merge, there is no way to ensure CRDs will be updatable. Please use kubectl apply -f https://raw.githubusercontent.com/weaveworks/flux/master/deploy-helm/flux-helm-release-crd.yaml and  --set helmOperator.createCRD=false until Helm v3 supports managing CRDs lifecycle https://github.com/helm/community/pull/64

I realised that  https://raw.githubusercontent.com/weaveworks/flux/master/deploy-helm/flux-helm-release-crd.yaml and https://github.com/weaveworks/flux/blob/master/chart/flux/templates/helm-operator-crd.yaml are different.
The one in the chart has an additional resource, fluxhelmreleases.helm.integrations.flux.weave.works. Which one is the correct one?

until Helm v3 supports managing CRDs lifecycle helm/community#64

It doesn't seem like helm v3 is going GA anytime soon (and this feature is still in the discussion stage). Wouldn't it be more prudent to set the default value of helmOperator.createCRD to false to avoid such issues?
Personally, I would remove this CRD in the chart altogether and force users to create the CRD using kubectl to remove confusion around this.
Eg, Remove the confusion around the situation where it still works even if I don't follow the recommended installation steps (making me question the authenticity/updatedness of the recommendation) and then running into problems later due to this (after already diving knee deep)

@isen-ng you are right, the apply command is wrong since it installs the old CRD that's no longer used, we'll fix it, thanks for pointing this out. As for why the defaults don't match the recommended install, is due to historical reasons. When we first released the chart there was no "helm.sh/resource-policy": keep annotation in place and Helm would delete the CRD when upgrading. To avoid this for our early adopters we decided to keep the createCRD=true.

We should consider setting createCRD=false and removing the old fluxhelmreleases CRD from the chart for the 1.0 release of Helm Operator cc @hiddeco

Maybe just have a pattern similar to the istio-init chart (which is only ever used as helm template)?

@starkersI that doesn't make sense for us since we don't have 20+ CRDs like Istio. Also the istio-init is not used only with template, that chart packages the CRDs into 3 jobs. Here is how you use Helm to deploy the Istio CRDs https://github.com/weaveworks/flagger/blob/master/test/e2e-istio.sh#L16

Agreed.. I frankly just use something like this:
kubectl apply -f https://raw.githubusercontent.com/weaveworks/flux/${GITHUB_TAG}/deploy-helm/flux-helm-release-crd.yaml