How to configure and invoke is not clear

Hi,
my swagger documentation full url is http://apidns:port/documentation.
I configured plug in at global level with swagger documentation url which is
spec url : http://apidns:port/documentation.
When I call same url http://kongdns:port/documentation from browser, it says route not found.
How do I configure and invoke documentation

Hello @satishmane ,
Have you created a Kong route on your gateway yet too with auth protection?
https://konggateway.com/my/proxy/service ?
Because once you have a proxy route established then you will be able to call:
https://konggateway.com/my/proxy/service**/specz**
To reach the specification documentation of your exposed spec. As a global plugin on Kong it makes less sense because every route you create on the gateway will expose the same spec, and if you have multiple services with different spec documents then you won't be able to expose them all properly, so my suggestion would be create plugin on route unless you only have on api service/spec behind your gateway(then global would work but you still need a Kong proxy route created for it to path off of.

thanks for quick reply.
Yes, after adding plug-in at route level, it is able to call documentation url. However it does not solve my problem. Basically I have swagger http://apidns:port/documentation. When I call this url from browser, it calls several api automatically to load swagger complete documentation page for all apis e.g. /documentation results into /swaggerui /swagger.json etc.  Does this plug-in not handle internal calls to /swaggerui /swagger.json etc when /documentation is called from browser

This plugin simply does a GET HTTP request on the URL mentioned in spec expose and returns that to client, if its a wsdl/wadl/openapi spec the content will load. As for loading a swagger ui page I am not entirely sure that works by default as its not how we use this plugin internally. Maybe a CORS issue?

Documentation it is not clear at all. Many developer needs a plugin like this but if you don't have any example :( . Your call shouldn't be http://apidns:port/documentation instead should be https://konggateway.com:port/..../mydocumentation. Because  with your link http://apidns:port/documentation you will need to expose this address so then why the gateway ..

Is there support for the function of swagger document aggregation? When I used the Kong-spec-expose plug-in officially provided by Kong, I found config spec_ URL variable only supports one API Spec URL?

Your correct it only supports 1 spec per configured proxy essentially. In a micro-service world where you have proxies per micro-service and each micro-service exposes their own OAS spec this model makes sense. Whats your use case?

Thank you for your prompt reply。
My use case is that when I have hundreds or thousands of microservices, developers need to individually access (or remember) the url of swagger-ui corresponding to each microservice each time, which is really cumbersome. Similar to springcloud gateway integration knife4j, you can easily switch to the api spec of other microservices only in one swagger-UI page.just like this：

I have the same but all my swagger file and UI are behind http://service:port/swagger/ I have hundreds of them I need expose this URL without authentication used by other routes or plugins in kong, but it's a relative path of my original service route.


Test fix on master and change of constant

corresponding rel PR https://github.com/cloudfoundry-incubator/service-fabrik-broker/pull/368


Unable to delete SEO-URLs and then saving

The content of the “SEO URL”-field (in the "SEO" tab) cannot be deleted and then saved.
However, this is mandatory if a SEO URL was initially created manually (or migrated) and I now want to generate a new SEO URL based on the template.
Manually created and migrated URLs are given the flag is_modified = 1 and are write-protected.
The only solution to generate a URL based on the template again would be to set the flag is_modified = 0, as the content of the SEO URL field currently can’t be saved as long as the field is empty.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37366.
[created from NEXT-37366, comment 486751]


About develop environment

Could you please provide your develop environment？ Like OS，version of pytorch，python and etc..
I got a lot of errors, and it's all about conflicts between versions of packages when running setup.py.

The author provided the training log in Google Cloud Drive, which has some environment details. It may help.


failed to append logs error on CLOUDRUN_PROMOTE step when deploying cloudrun services

What happened: For all deployments, CLOUDRUN_PROMOTE step has no log, other non-cloudrun steps have log. Piped log contains following pattern:
failed to report stage logs from last checkpoint	{"key": {"DeploymentID":"d9df5ce0-5b0b-495a-ae65-01ab4acdde04","StageID":"stage-0"}, "error": "rpc error: code = Internal desc = failed to append logs"}
github.com/pipe-cd/pipe/pkg/app/piped/logpersister.(*persister).reportStageLogsFromLastCheckpoint
	pkg/app/piped/logpersister/persister.go:198
github.com/pipe-cd/pipe/pkg/app/piped/logpersister.(*stageLogPersister).flushFromLastCheckpoint
	pkg/app/piped/logpersister/stagelogpersister.go:198
github.com/pipe-cd/pipe/pkg/app/piped/logpersister.(*stageLogPersister).flush
	pkg/app/piped/logpersister/stagelogpersister.go:155
github.com/pipe-cd/pipe/pkg/app/piped/logpersister.(*persister).flush.func1
	pkg/app/piped/logpersister/persister.go:145
sync.(*Map).Range
	GOROOT/src/sync/map.go:345
github.com/pipe-cd/pipe/pkg/app/piped/logpersister.(*persister).flush
	pkg/app/piped/logpersister/persister.go:136
github.com/pipe-cd/pipe/pkg/app/piped/logpersister.(*persister).Run
	pkg/app/piped/logpersister/persister.go:93
github.com/pipe-cd/pipe/pkg/app/piped/controller.(*controller).Run.func1
	pkg/app/piped/controller/controller.go:220

What you expected to happen: piped should push all logs to pipecd
How to reproduce it:

install pipecd
install piped with invalid gcp service account
add application, attempt deployment and fail
upgrade piped with correct gcp service account
observe logging issue on CLOUDRUN_PROMOTE step

Environment:

piped version: v0.21.0
control-plane version: v0.21.0
Others: GCP service account permissions: (I'm using the same service account for both control plane and piped)
Cloud Datastore Index Admin
Cloud Datastore User
Cloud Run Admin
Service Account User

@yliu-d Hi, Thank you for your report.
You are right. Our this doc is bad.
In the case of using GCS
https://pipecd.dev/docs/operator-manual/control-plane/installation/#using-firestore-and-gcs
the gcs-service-account needs roles/storage.objectAdmin role to be able to write log file to GCS bucket.
I have updated our doc (https://github.com/pipe-cd/pipe/pull/2723) and hope that adding will work for you.
Thanks.


Prototype running GitHub Actions locally

This will enable faster GitHub Action development. Could we use https://github.com/nektos/act?

act works but there are some subtle nuances:

a checkout action checks out the github repo, not your local repo; so you have to push things up (I'm still looking at whether a clone of a clone could circumvent this), but the actions that are being run do not appear to be the ones that are checked in, they appear to be whatever is the current state of the workflow in your working directory (this last thing makes sense because that's what you want to test anyway)
There appear to be some subtle differences between the images that are used by github and the ones used by act. For instance, on the github ubuntu-latest, you don't have to install docker-compose and it is present by default. Your local act-run will require you to install it if you want to use it.

So there is some friction...

@td-usds Both of those sound like the differences from GitHub actions probably outway the costs of setting this up. Would you agree, or do you think this could be a time-saver with more time spent working through the issues?

I think setting this up does not make sense at this point. For those tasks that may benefit from it (i.e. purely modifying github workflows and nothing else - which is rather rare), sure we can run it locally, but I don't think institutionalizing this makes sense.

Agreed. Thanks for investigating!


Cannot bind service at app level

As a user, I'm deploying a stream with service binding at an app level, but I'm unable to successfully run it. This used to be supported in M2; perhaps this was lost while refactoring to spring-cloud-deployer SPI.
stream:
dataflow:>stream create --name foo-mysql --definition "http | jdbc --tableName=names --columns=name"
dataflow:>stream deploy foo-mysql --properties module.jdbc.cloudfoundry.services=mysql

(where: mysql is the name of the service running in cf)
error:
2016-05-13T15:15:18.85-0700 [APP/0]      ERR Exception in thread "main" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:62)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at java.lang.Thread.run(Thread.java:745)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR Caused by: java.lang.reflect.InvocationTargetException
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at java.lang.reflect.Method.invoke(Method.java:497)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:54)
2016-05-13T15:15:18.85-0700 [APP/0]      ERR 	... 1 more
2016-05-13T15:15:18.85-0700 [APP/0]      ERR Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.cloud.stream.app.jdbc.sink.JdbcSinkConfiguration': Initialization of bean failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jdbcMessageHandler' defined in class org.springframework.cloud.stream.app.jdbc.sink.JdbcSinkConfiguration: Unsatisfied dependency expressed through constructor argument with index 0 of type [javax.sql.DataSource]: Error creating bean with name 'dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceAutoConfiguration$NonEmbeddedConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.sql.DataSource]: Factory method 'dataSource' threw exception; nested exception is org.springframework.boot.autoconfigure.jdbc.DataSourceProperties$DataSourceBeanCreationException: Cannot determine embedded database driver class for database type NONE. If you want an embedded database please put a supported one on the classpath. If you have database settings to be loaded from a particular profile you may need to active it (the profiles "cloud" are currently active).; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceAutoConfiguration$NonEmbeddedConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.sql.DataSource]: Factory method 'dataSource' threw exception; nested exception is org.springframework.boot.autoconfigure.jdbc.DataSourceProperties$DataSourceBeanCreationException: Cannot determine embedded database driver class for database type NONE. If you want an embedded database please put a supported one on the classpath. If you have database settings to be loaded from a particular profile you may need to active it (the profiles "cloud" are currently active).

This is the right property to use based on the latest:
dataflow:>stream deploy foo-mysql --properties module.jdbc.spring.cloud.deployer.cloudfoundry.defaults.services=mysql
It used to be module.jdbc.cloudfoundry.service. @markfisher @markpollack What do you think about going back to this property key?

The fully qualified suffix after module.jdbc seems good as it will avoid collisions in the future.  I don't like the use of the word defaults, even if it was in yaml vs. property file syntax.  Related to that for k8s and mesos there isn't a defaults keyword.
See https://github.com/spring-cloud/spring-cloud-deployer-kubernetes/blob/master/src/main/java/org/springframework/cloud/deployer/spi/kubernetes/KubernetesAppDeployer.java#L283
and
https://github.com/spring-cloud/spring-cloud-deployer-mesos/blob/master/src/main/java/org/springframework/cloud/deployer/spi/mesos/marathon/MarathonAppDeployer.java#L175
I didn't check YARN, but I think we should be consistent across the board by having it be fully qualified with the deployer's @ConfigurationProperties prefix and remove the use of default.

PR is issued for addressing this. https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry/pull/38


assumedVersionScheme (and assumedVersionSchemeJava) default to "always"

steps
create a new sbt project (1.8.2)
$ cat build.sbt project/build.properties
scalaVersion := "2.13.10"
name := "scratch"
version := "1.0"
sbt.version=1.8.2

problem
❯ sbt  "show assumedVersionScheme"
[info] welcome to sbt 1.8.2 (Eclipse Adoptium Java <IP_ADDRESS>)
[info] loading project definition from /Users/👻/Desktop/scratch/project
[info] loading settings for project scratch from build.sbt ...
[info] set current project to scratch (in build file:/Users/👻/Desktop/scratch/)
[info] always

expectation
I was expecting the default to be more conservative. Users that want to yolo their dependency management should have to opt in to always IMO :-)
Those that got used to the old heuristics are probably not expecting this?

See https://www.scala-lang.org/blog/2021/02/16/preventing-version-conflicts-with-versionscheme.html
tl;dr is since sbt 1.5.0 I stopped using heuristics, and eviction error depends on opt-in information provided by versionScheme key by the library authors.


saad/bug-fix/bypassing-connect-page

https://www.loom.com/share/8b20616f8ea343089cb579a3eb242b93
ConnectVault function was firing on app load as well as when the button is pressed, removed from App Load, doesnt seem to create any issues.
Closes #83

I'm getting this error when I login in. It logs in successfully, starts to being up the UI and then I get this


Add asyncio to both slack packages

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/powershell-ubuntu:<IP_ADDRESS>362
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/powershell-ubuntu/tags
Get started by pulling the image:
docker pull devdemisto/powershell-ubuntu:<IP_ADDRESS>362

Docker Metadata

Image Size: 188.15 MB

Image ID: sha256:b940b24d9ae934bdb84dac482f0ab3156631aa494c5828b9f89a9330d957e9af

Created: 2022-12-15T10:48:18.453974461Z

Arch: linux/amd64

Command: ["pwsh"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PS_INSTALL_FOLDER=/opt/microsoft/powershell/7
DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=false
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8
PSModuleAnalysisCachePath=/var/cache/microsoft/powershell/PSModuleAnalysisCache/ModuleAnalysisCache
POWERSHELL_DISTRIBUTION_CHANNEL=PSDocker-Ubuntu-20.04
DOCKER_IMAGE=devdemisto/powershell-ubuntu:<IP_ADDRESS>362

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:e5e1b45f1f93af33dac9f94496d79162e5934687
org.opencontainers.image.version:<IP_ADDRESS>362


Backport: Ability to Enable Ingress SSL Without a Certificate

Backport a fix for https://github.com/rancher/rancher/issues/15021

@tfiduccia UI tag: 2.1.1 for backport testing

Available in v2.1.1-rc3


Synchronize sync workers

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #2361
Description
We use the recommended way for mutual exclusion: link
mutex.withLock will suspend the successive workers, without blocking the thread, until first worker releases the lock. Hence all work requests will be processed - and in FIFO order.
However we should be mindful of lock inheritance and avoid nested lock acquisition within the same coroutine hierarchy. Else it can potentially cause deadlocks. Other best way to solve this would be to improve the synchronize function to return a Flow . This allows for data synchronization without requiring explicit coroutine management within mutex.withLock blocks, potentially reducing the risk of deadlocks. [Check this issue]
TESTED manually using following piece of code.
class ConcurrentSyncTestWorker(appContext: Context, workerParams: WorkerParameters) :
    CoroutineWorker(appContext, workerParams) {
    override suspend fun doWork(): Result {
      val workerNumber = inputData.getInt(WORKER_NUMBER, 0)
      println("WorkerNumber $workerNumber started")
      mutex.withLock {
        println("WorkerNumber $workerNumber acquired lock")
        for(i in 1..100000)
          counter++
        println("Counter incremented 100000 by WorkerNumber: $workerNumber")
        return Result.success()
      }
    }

    companion object{
      val mutex = Mutex()
    }
  }

  @Test
  fun manualTest() = runBlocking {
    val jobs = List(100) {
      launch {
        TestListenableWorkerBuilder<ConcurrentSyncTestWorker>(
          context,
          inputData = Data.Builder().putInt(WORKER_NUMBER, it).build(),
        ).build().doWork()
      }
    }

    jobs.forEach { it.join() }

    println("Counter = $counter")
  }

  companion object {
    private const val WORKER_NUMBER = "worker-number"
    var counter = 0
  }

Outputs are aligned as expected. Final value of counter is always 100*100000.
However, could not verify the case when counter value is not updated correctly when mutex.withLock is absent. Need to run this many times to be able to observe incorrect concurrent behaviour.
Alternative(s) considered
Alternative: One alternative involves using a ReentrantLock within a try-catch-finally block. This approach essentially replicates mutex-like behavior to manage concurrent access to shared resources. It would require maintaining a job queue to handle work requests sequentially. Without a queue, workers would need to return Result.retry, leading to repeated attempts every 30 seconds.
Type
Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

I am not sure if automation test for this is a good idea. Because it takes lot of execution time to be able to verify the synchronicity of any concurrent jobs.  See how concurrent behavior is verified here.
Such long execution time, however, is very likely in case of long sync time in an actual app
@aditya-07

I figured how to test the mutex locking.
@aditya-07 @jingtang10


LightningCLI: config argument linkings in config file

🚀 Feature
Show and config linking in config file
Motivation
In current design of CLI, we need to construct one to one MyLightningCLIs, if we have linking arguments in our models. Provide this feature can save some time in doing this for we can use the default implementation LightningCLI
Pitch
data:
  num_classes: 2
model:
  num_classes:
    link_source:  data.num_classes
    link_compute_fn:  path.to.func
    link_apply_on:  instantiate

Alternatives
CLI:
  links:
    - source: data.num_classes
      target:  model.num_classes
      compute_fn:  path.to.func
      apply_on:  instantiate
data:
  num_classes: 2
model:
  num_classes: null

or for simple value linking:
data:
  num_classes: 2
model:
  num_classes: <-- data.num_classes

Additional context

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, finetuning and solving problems with deep learning

Bolts: Pretrained SOTA Deep Learning models, callbacks and more for research and production with PyTorch Lightning and PyTorch

Lightning Transformers: Flexible interface for high performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

I support this idea.
A separate cli: namespace in the config.yaml can potentially simplify other things that require subclassing LightningCLI right now - like this one.

@mauvilsa Any thoughts for json-arparse ?

Dear @quancs,
I believe this feature request should be open on json-argparse directly :)
Best,
T.C

I explain a bit how the linking of arguments feature came to be and why I don't like this proposal. The objective of config files should be only allow to configure stuff, otherwise there is a blurred line between what is source code and what is configuration. The linking of arguments is intended for cases in which always some value is derived from configurable values, i.e. the linked argument is not configurable. This is why when an argument is linked, it is no longer specifiable in the config file. In other words, linked arguments is not configuration and it belongs in the source code. Not wanting to subclass LightningCLI is not a good reason to add complexity to the config files.
@quancs could you please explain your use case which lead you to request this feature. There might be something that could belong in the config file. Or we could come up with a way to achieve what you need without adding complexity to the config.

In the development of my model, I will try plenty of ideas, which results in plenty of model implementations, and for each implementation I need imp its own CLI. Or is there some way, I can share their CLI implementations? Or, the best practice is not to share CLIs?
Another reason for this feature is that I can clearly figure out where the shared parameters comes from in the config file. In the current design, we could not even know from the config file that there is a parameter that is needed for constructing the linking target. I guess that would add a little bit more complexity if we share our model with others, especially with the guys who are not familiar with lightning. Example from speechbrain (they also provide a yaml based config file). From this example, we could clearly know: all the paramters needed to construct the objects and which parameter is shared from which place. That is clearer for me.

HyperPyYAML, the yaml package used in speechbrain. It's functionality is very novel and useful. And the grammer is simple too.

Yaml already provides features like anchors that allow reusing parts of a config. Also there are many packages that implement interpolation on top of yaml, e.g. Ansible, and I think it would be great if optionally people would be able to switch in jsonargparse to a yaml library that supports it. However there has been a tendency of each package internally implementing interpolation without releasing a yaml library that can be reused. Great that HyperPyYAML exists standalone. Will look at it to see if it could be used to optionally swap pyyaml in jsonargparse.
However, note that my opinion remains the same. The objective of argument linking is non-configurable things. Interpolation is okay for some use cases, but not overuse it for things that should not be configurable.
@quancs I did get the idea that you wanted to try out many models. And I think is great if you have a single CLI for it. But still I don't think is a good idea to introduce into the config file the details of how to adapt different model implementations into a common interface. Interface adaptation should be in the source code. I was hoping that you give more specific details about your use case to see if there are needs I have not thought of.

HyperPyYAML, the yaml package used in speechbrain. It's functionality is very novel and useful. And the grammer is simple too.

@quancs with jsonargparse v4.1.0 released today now it is possible to change the yaml loader making it possible to add support for variable interpolation. Out of the box you can use OmegaConf, see https://jsonargparse.readthedocs.io/en/stable/#variable-interpolation, but if you want to use HyperPyYAML simply register a loader function that uses it https://jsonargparse.readthedocs.io/en/stable/#custom-loaders.

HyperPyYAML, the yaml package used in speechbrain. It's functionality is very novel and useful. And the grammer is simple too.

@quancs with jsonargparse v4.1.0 released today now it is possible to change the yaml loader making it possible to add support for variable interpolation. Out of the box you can use OmegaConf, see https://jsonargparse.readthedocs.io/en/stable/#variable-interpolation, but if you want to use HyperPyYAML simply register a loader function that uses it https://jsonargparse.readthedocs.io/en/stable/#custom-loaders.

Great! I will try, thank you for your nice work.

@mauvilsa variable interpolation not work. run python boring.py --config boring.yaml
boring.py
import os
from typing import List

import torch
from torch.utils.data import DataLoader, Dataset

from pytorch_lightning import LightningModule, Trainer

class Arch:

    def __init__(self, input_size: int, channels: List[int], a: int = 10) -> None:
        pass

class RandomDataset(Dataset):

    def __init__(self, size, length):
        self.len = length
        self.data = torch.randn(length, size)

    def __getitem__(self, index):
        return self.data[index]

    def __len__(self):
        return self.len

class BoringModel(LightningModule):

    def __init__(self, arch: Arch, channels: List[int] = [0, 1, 2, 3, 4, 5, 6, 7, 8]):
        super().__init__()
        self.layer = torch.nn.Linear(32, 2)

    def forward(self, x):
        return self.layer(x)

    def training_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("train_loss", loss)
        return {"loss": loss}

    def validation_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("valid_loss", loss)

    def test_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("test_loss", loss)

    def configure_optimizers(self):
        return torch.optim.SGD(self.layer.parameters(), lr=0.1)

from pytorch_lightning.utilities.cli import (LightningArgumentParser, LightningCLI)

class MyCLI(LightningCLI):

    def add_arguments_to_parser(self, parser: LightningArgumentParser) -> None:
        default_arch = {
            "class_path": "__main__.Arch",
            "init_args": {
                "a": "10",
                # "channels": "${model.channels}"
            },
        }

        parser.set_defaults({
            "model.arch": default_arch,
        })

        parser.link_arguments("model.channels", "model.arch.init_args.input_size", compute_fn=lambda channels: 2 * len(channels), apply_on="parse")

        return super().add_arguments_to_parser(parser)

from pytorch_lightning import LightningDataModule
from torch.utils.data import DataLoader
import os

class MyDataModule(LightningDataModule):

    def __init__(self, train_transforms=None, val_transforms=None, test_transforms=None, dims=None):
        super().__init__(train_transforms=train_transforms, val_transforms=val_transforms, test_transforms=test_transforms, dims=dims)

    def train_dataloader(self) -> DataLoader:
        return DataLoader(RandomDataset(32, 64), batch_size=2)

    def val_dataloader(self) -> DataLoader:
        return DataLoader(RandomDataset(32, 64), batch_size=2)

    def test_dataloader(self) -> DataLoader:
        return DataLoader(RandomDataset(32, 64), batch_size=2)

if __name__ == '__main__':
    cli = MyCLI(BoringModel, MyDataModule, seed_everything_default=None, save_config_overwrite=True, parser_kwargs={"parser_mode": "omegaconf"})

boring.yaml
seed_everything: null
trainer:
  logger: true
  checkpoint_callback: null
  enable_checkpointing: true
  callbacks: null
  default_root_dir: null
  gradient_clip_val: null
  gradient_clip_algorithm: null
  process_position: 0
  num_nodes: 1
  num_processes: 1
  devices: null
  gpus: null
  auto_select_gpus: false
  tpu_cores: null
  ipus: null
  log_gpu_memory: null
  progress_bar_refresh_rate: null
  enable_progress_bar: true
  overfit_batches: 0.0
  track_grad_norm: -1
  check_val_every_n_epoch: 1
  fast_dev_run: false
  accumulate_grad_batches: null
  max_epochs: null
  min_epochs: null
  max_steps: -1
  min_steps: null
  max_time: null
  limit_train_batches: 1.0
  limit_val_batches: 1.0
  limit_test_batches: 1.0
  limit_predict_batches: 1.0
  val_check_interval: 1.0
  flush_logs_every_n_steps: null
  log_every_n_steps: 50
  accelerator: null
  strategy: null
  sync_batchnorm: false
  precision: 32
  enable_model_summary: true
  weights_summary: top
  weights_save_path: null
  num_sanity_val_steps: 2
  resume_from_checkpoint: null
  profiler: null
  benchmark: false
  deterministic: false
  reload_dataloaders_every_n_epochs: 0
  reload_dataloaders_every_epoch: false
  auto_lr_find: false
  replace_sampler_ddp: true
  detect_anomaly: false
  auto_scale_batch_size: false
  prepare_data_per_node: null
  plugins: null
  amp_backend: native
  amp_level: null
  move_metrics_to_cpu: false
  multiple_trainloader_mode: max_size_cycle
  stochastic_weight_avg: false
  terminate_on_nan: null
model:
  arch:
    class_path: __main__.Arch
    init_args:
      channels: "${model.channels}"
      a: 10
  channels:
  - 0
  - 1
  - 2
  - 3
  - 4
  - 5
  - 6
  - 7
  - 8
data:
  train_transforms: null
  val_transforms: null
  test_transforms: null
  dims: null
ckpt_path: null

Oh, I see. It's not on the recent release...


chore: use renovate-presets-jvm to group updates

More an excuse to open a PR. I was skimming through projects on GitHub using Atrium and found also this one.
We can include it in the README of Atrium as third-party extension if you like.

Thanks for the PR!

We can include it in the README of Atrium as third-party extension if you like.

Gladly!

@robstoll do you plan to contribute this configuration upstream? Renovate is usually welcoming such improvements!

Gladly!

Done

do you plan to contribute this configuration upstream?

Was my first plan. I don't remember why I did it in an own repo in the end but I have something in mind that it was too cumbersome to contribute.

it was too cumbersome to contribute.

If you don’t mind, I’d create a PR if I find the time.

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

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


clear encryption info for temporary file

What problem does this PR solve?
Issue Number: close #5979
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/rebuild

/run-all-tests

/run-all-tests

/run-unit-test

/merge

/run-all-tests


mysql2 dependency is leaking file descriptors to /dev/null

Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
Issue
When there are frequent occurrences of mysql connection issues there is a chance /dev/null will be opened one or more times and never closed.  Eventually this will lead to API failures when the open file limit is reached for the cloud_controller_ng process
{"timestamp":1499956214.6394343,"message":"exception not translated: Sequel::DatabaseDisconnectError - Mysql2::Error: Lost connection to MySQL server during query:
{"timestamp":1499958029.7996564,"message":"Request failed: 500: {\"description\"=>\"Database error\", \"error_code\"=>\"CF-DatabaseError\", \"code\"=>10011, \"test_mode_info\"=>{\"description\"=>\"D atabase error\", \"error_code\"=>\"CF-DatabaseError\"

Context
Was able to narrow this down to mysql2 dependency by attaching to the CC process using gdb and creating a command script when a file is opened that prints the stack trace
(GDB) catch syscall 2
(gdb) command
Type commands for breakpoint(s) 1, one per line.
End with a line saying just "end".
>silent
>print result
>bt
>c
>end
(gdb) c

the result was this stack trace which points to the mysql2 code disconnect_and_raise in client.c
0(gdb) #1  0x00007fcc42dab478 in open (__oflag=524290, __path=0x7fcc42df6110 "/dev/null") at /usr/include/x86_64-linux-gnu/bits/fcntl2.h:53
c(gdb) #2  invalidate_fd (clientfd=57) at client.c:228
(gdb) #3  disconnect_and_raise (self=self@entry=93854966580800, error=93854955159240) at client.c:599
c=(gdb) #4  0x0000555c4ad152a8 in rb_rescue2 (b_proc=b_proc@entry=0x7fcc42dabf40 <do_send_query>, data1=data1@entry=140515228349920, r_proc=r_proc@entry=0x7fcc42dab430 <disconnect_and_raise>, data2=data2@entry=93854966580800) at eval.c:846
55(gdb) #5  0x00007fcc42dad3ca in rb_query (self=93854966580800, sql=<optimized out>, current=93854955220200) at client.c:753
(gdb) #6  0x0000555c4ae5d896 in vm_call_cfunc_with_frame (ci=<optimized out>, cc=<optimized out>, calling=<optimized out>, reg_cfp=0x7fcc4055ced0, th=0x555c515f0f30) at vm_insnhelper.c:1642
(gdb) #7  vm_call_cfunc (th=0x555c515f0f30, reg_cfp=0x7fcc4055ced0, calling=<optimized out>, ci=<optimized out>, cc=<optimized out>) at vm_insnhelper.c:1737
(gdb) #8  0x0000555c4ae6b753 in vm_call_method (th=0x555c515f0f30, cfp=0x7fcc4055ced0, calling=<optimized out>, ci=<optimized out>, cc=<optimized out>) at vm_insnhelper.c:2176
(gdb) #9  0x0000555c4ae660b9 in vm_exec_core (th=th@entry=0x555c515f0f30, initial=initial@entry=0) at insns.def:994
c(gdb) #10 0x0000555c4ae69de1 in vm_exec (th=0x555c515f0f30) at vm.c:1650

currently we vendor mysql2 version 0.4.5 but there have been some changes to this part of the code that handle the mysql connections better.
https://github.com/brianmario/mysql2/commit/0e0144c459014f28997ae92f2873370046dd2353
https://github.com/brianmario/mysql2/commit/7879f1ee4f976e8b31a4378925f3b7621eb1b431
Steps to Reproduce
reproduced with pcfdev

cf dev start ( builds the pcdev env )
ssh into the vagrant vm

cf dev ssh

run a script that restart mariadb every  minute or so

while true; do monit stop mariadb_ctrl; sleep 10; monit start mariadb_ctrl; sleep 60; done &> /dev/null &

from cf cli curl the capi apps endpoint every 1 second to ensure there is an active db connection when maridb starts up.  Also push an app to generate some activity.

 while true; do cf curl /v2/apps?inline-relations-depth=1 ; sleep 1; done
 while true; do cf push; done

slowly over time observe the fd count group for the cloud_controller_ng process

root@agent-id-pcfdev-0:/var/vcap/sys/log/cloud_controller_ng# lsof -p 15877 | egrep null | wc -l
12
root@agent-id-pcfdev-0:/var/vcap/sys/log/cloud_controller_ng# lsof -p 15877 | egrep null
ruby    15877 vcap    0u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap    7w   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   20u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   21u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   41u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   42u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   43u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   45u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   46u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   48u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   49u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap   50u   CHR                1,3      0t0       6 /dev/null

Expected result
there should be no fd leak
root@agent-id-pcfdev-0:/var/vcap/sys/log/cloud_controller_ng# lsof -p 15877 | egrep null
ruby    15877 vcap    0u   CHR                1,3      0t0       6 /dev/null
ruby    15877 vcap    7w   CHR                1,3      0t0       6 /dev/null

Possible Fix
I upgraded the mysql2 dependency to version 0.4.8 and was not able to reproduce this using steps mentioned above.

Hi @randomtask1155, thanks for putting so much detail into your issue!  We were able to reproduce this issue on a Bosh Lite using your steps above and upgrading the mysql2 gem did seem to fix it.  We'll push a commit with that change soon. 👍

We bumped the mysql2 gem in this commit: https://github.com/cloudfoundry/cloud_controller_ng/commit/b96bb3a7b410effde5fd5f0e40fb8eb41f6bfcbd
I guess putting fixes #853 in there auto-closed this issue, but it's currently gone through the tubes and awaiting acceptance.  Reopening this so it can be closed once the Tracker story is accepted.


Support for Compose to React Native View Managers

The following error during linkPodDebugFrameworkIosSimulatorArm64 could only be resolved by setting the framework isStatic to true
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_RCTViewManager", referenced from:
       in shared.framework.o
ld: symbol(s) not found for architecture arm64
error: Compilation finished with errors


Minicalendar layout - UI

Current dependencies on/for this PR:

main

PR #205   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: wArkzInymIv8JGuTFogI


Setup playwright

Closes #4.
Adds an e2e test that navigates to the site, then to tx list, then to a tx detail, and checks that it renders.

The PR auto closed when I deleted the merged base branch because it didn't auto change to main


example commit

Issue #

Description of changes

New/existing dependencies impact assessment, if applicable

Conventional Commits

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

/release

/ci

/ci


Corrected buffBonus values

Thanks @seawalk24 , not sure how I messed that up. I musta put in dummy values early on and never swapped them out for the real thing. Thanks for the PR!

@amoeba Thank you for creating this very useful tool! One other thing that I noticed is that attribute cantrips are not being applied to skills. For example epic strength increases the buffed value of strength but not of heavy weapons.

This was brought to my attention and I wanna get this fixed right away. I've filed this as https://github.com/amoeba/accharplanner/issues/49 and will try to get it squared away soon.
Thanks for using it! Please hit me up here, in another issue, or on Discord (petridish#9636) if you have any feature requests or anything else really.


npm package version doesnt match repo version

I was wondering what was the source of remimi package on npm. It says version 1.1.0 but master branch says 1.0.0
Regards,
Iuri

Now using semantic-release so versioning is all handled at the time of publishing


Metrics deterministic results

[x] Partially addresses #4 and replace #102 along with #221
[x] Tests added.
[x] Updates entries to docs/source/api.rst for API changes.  -- will update if this appears to be on the right track
[x] Adds descriptions to appropriate "what's new" file in docs/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Merge with #221 when PR complete
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Updated just now with latest master and metrics-preprocessing updates.

Not passing some tests, will fix now.

@wholmgren @alorenzo175 I've updated metric's result dictionary and all tests are passing for reports and metrics. (I added a categories attribute to Report class) I've had to make some changes to reports.figures.construct_metric_series and report.template._metrics_script_divs to try and make it abstract to the category/grouping for calculating metrics.  I'm not sure how to edit the template.md for bokeh/ jinja to work with dict objects just yet.  Basically I need to make the report conditional on which groupings are available by a dictionary of of the figures_bar variable, so it should have keys of month, day etc. Any references you recommend or pointers?

Hmm, what you might do is make separate templates for day, month, etc. and then loop through/check which categories are there in template.md to include (https://jinja.palletsprojects.com/en/2.10.x/templates/#include) the appropriate category template. The jinja docs are usually pretty good, but it might take some trial and error with the syntax to do what you want.
Maybe something like (not sure all the jinja works)
{% for cat in figures_bar.keys() %}  # might have to use items
    {% include cat + '.md' %}   # maybe
{% endfor %}

And then monthly.md might look like
### Monthly

Metrics for each month of the analysis period are displayed in tables and figures below.

{{ '::: {.figures_bar}' }}
{% for figure in figures_bar['monthly'] %}
    { figure | safe }}
{% endfor %}
:::

@alorenzo175 Thanks. I'll give that a shot.

Updated with the discussed structure. There are still some issues with day metrics that need fixing and need to add a template report that includes all the other categories to test them out since I think they will also have issues. total and hour look as expected I think.

[ ] day
[ ] date
[ ] year
[ ] month
[ ] weekday

Updated the metric charts if someone can take a look and let me know if @wholmgren  or @alorenzo175 can take a look using below report request let me know if it looks ok?
{
    "name": "test",
    "report_parameters": {
        "start": "2019-08-21T00:00:00Z",
        "end": "2019-08-28T00:00:00Z",
        "filters": [],
        "metrics": [
            "mae",
            "mbe",
            "rmse"
        ],
        "categories": [
            "total",
            "year",
            "month",
            "date",
            "day",
            "weekday",
            "hour"
        ],
        "object_pairs": [
            ["9f657636-7e49-11e9-b77f-0a580a8003e9", "31ae8548-9a07-11e9-b2f4-0a580a8003d5"],
            ["9f657636-7e49-11e9-b77f-0a580a8003e9", "77be10e8-9c22-11e9-a974-0a580a8003d5"],
            ["9f657636-7e49-11e9-b77f-0a580a8003e9", "77e2474c-9c22-11e9-8cc3-0a580a8003d5"],
            ["9f657636-7e49-11e9-b77f-0a580a8003e9", "31fce5ba-9a07-11e9-a53f-0a580a8003d5"]
      ]
    }
  }

Updated the report and should be ready for review

Cool. I confirmed that the code runs without error and the report looks ok when using the configuration above. I'll look at it more carefully this afternoon.

@awig let me know if you need anything more from us to finish this PR.

@wholmgren Sorry, I lost sight of it. I'll get back on it.

2 remaining items:

[ ] replace jinja ifelse with loop using python mapping for specific metrics sections
[ ] replace the use of calendar categories to more descriptive text and replace integers with strings for appropriate category values for month and day of the week

Still having issues with the metrics TOC and the xaxis for Date, Month and Weekday

I'm okay with the metric bar charts in the report now. I'll work on resolving the conflicts now 🤞

@awig note #256 changed the metadata specs for the object_pairs key. Should now be a list of dicts as documented in that PR.

Oh this was just a few minutes ago. I'll need to remerge. thanks for the headsup

@wholmgren I noticed that object_pairs in test/data/report_metadata.json are still a lists. Is this a mistake or am I missing something?

that is a mistake and I'm not sure how `test_cli.py::test_report`` passes.

@wholmgren Okay thanks. I can at least just commit the changes on my end to fix this.  Sound ok?

yes thanks

@alorenzo175 Thanks for letting me know about #260 I'll remerge. There were some easy issues to fix but I still hadn't fixed all the merge conflicts from the last merge.

All tests are passing but when i try to run the cli i get the following 404 error message:
(venv37) pawi002-MBP:solarforecastarbiter-core pawi002$ solararbiter report ./report_metadata_all_categories.json -u<EMAIL_ADDRESS>-p Thepassword123! test_report_all_categories.html
...
  File "/Users/pawi002/software/solar_arbiter/solarforecastarbiter-core/solarforecastarbiter/io/api.py", line 101, in request
    response=result)
requests.exceptions.HTTPError: 404 API Request Error: NOT FOUND for url: https://api.solarforecastarbiter.org/forecasts/single/da2bc386-8712-11e9-a1c7-0a580a8200ae/metadata and text: {"errors":{"404":"Not Found"}}

I've updated the object_pairs in the json file to match what is in the conftest report_text
        "object_pairs": [
            {"forecast": "da2bc386-8712-11e9-a1c7-0a580a8200ae",
             "observation": "9f657636-7e49-11e9-b77f-0a580a8003e9"},
            {"forecast": "68a1c22c-87b5-11e9-bf88-0a580a8200ae",
             "observation": "9f657636-7e49-11e9-b77f-0a580a8003e9"},
            {"forecast": "49220780-76ae-4b11-bef1-7a75bdc784e3",
             "aggregate": "458ffc27-df0b-11e9-b622-62adb5fd6af0"}
        ]

Any ideas what is wrong?

You're hitting the production API which doesn't have that forcast (I think). Try setting --base-url=https://dev-api.solarforecastarbiter.org in the command

Also getting an error with dev:
requests.exceptions.HTTPError: 404 API Request Error: NOT FOUND for url: https://dev-api.solarforecastarbiter.org/forecasts/single/da2bc386-8712-11e9-a1c7-0a580a8200ae/metadata and text: {"errors":{"404":"Not Found"}}

Are there some other ids you can provide or what would be a quick request to find them that i have access to?

python -c "from solarforecastarbiter.io import api; token =<EMAIL_ADDRESS>'Thepassword123!'); sess = api. APISession(token, base_url='https://dev-api.solarforecastarbiter.org'); print(sess.list_forecasts())"

or get an access token with curl and curl /forecasts/single/
https://dev-api.solarforecastarbiter.org/#tag/Forecasts/paths/~1forecasts~1single~1/get

Sorry, what I said about dev is wrong. You do want to be hitting 'https://api.solarforecastarbiter.org' because it will actually have populated observations and forecasts.  I might try
"object_pairs": [
            {"forecast": "2cfed5da-9a07-11e9-bc1f-0a580a8003d5",
             "observation": "9e1c23da-7e49-11e9-9ec0-0a580a8003e9"},
            {"forecast": "2c725aac-9a07-11e9-99c8-0a580a8003d5",
             "observation": "9dfe124a-7e49-11e9-98c3-0a580a8003e9"},
]

Oh ok. Thanks. I'll give that a shot

That works thanks but the observation doesn't have any data at least for the time period that was already specified. I'll see if I can figure out some dates that work.

@wholmgren @alorenzo175 Ready for your re-re-review
Okay found updated the period and all conlficts are resolved, all tests are passing and the test report output html files look okay to me. btw: i tested on a 4 month period and it took only a few seconds 👍

@wholmgren Planning to make the suggested changes. I'll think about the refactoring once I'm done with the rest and let you know.

With the additional error checks in the metrics functions for timeseries being n > 2 tests are now failing instead of adding the ignore. I will need to fix these otherwise all the changes have been made.

np.nan is fine with me in that situation

@wholmgren @alorenzo175 Okay I think it is ready for one last review (hopefully)

@alorenzo175 Ok think i got them this time

yes

thanks @awig!


Docker service restart and exec

Feature idea
I belive docker service is missing a way to restart all replicas of service and way to exec on all replicas of service. Also logs available on one place would be great.
The reason is, that if you want to for example reload config file you updated in volume, you have to restart service inside container (reason of exec) or restart whole container (reason of restart). Without this features you have to remove the service and create new, which cause downtime...
The reason why logs would be great is obvious...
Steps to reproduce the issue:

docker service update --restart ...
This command would send HUP command to all replicas of service. --update-parallelism and update-delay would affect parallelism and delay of this action
docker service update --exec ...
This command would exec command on all replicas of service. --update-parallelism and update-delay would affect parallelism and delay of this action
docker service logs ...
This would show logs, same way as docker-cloud does.

logs support is already planned for 1.13

@frimdo I'm voting for this, although I would either stick to the kill -s command – as described in #27081 – in order for it to be consistent across all the Engine, Compose and Swarm/Service. Nevertheless, the parallelism/update option would definitely be useful there as well!

/cc @aluzzardi @mgoelzer

+1. Currently the only way to reload a configuration file you changed in a volume on all replicas, is to issue a docker service update, which would discontinue the service...

Workaround until this has been implemented:
Create a script on the Docker hosts:
#!/bin/bash

inotifywait -m -e create,move,delete /the/directory/to/watch/for/changes/ | while read watchline
do
	echo $watchline

	CONTAINER_ID=$(docker ps | grep -i MYCONTAINER | awk '{ print $1 }')

	if [[ -n $CONTAINER_ID ]]
	then
		docker kill -s HUP $CONTAINER_ID
	fi
done

Be sure to have it run through an init.d script (or however), as soon as the system/Docker boots. In a swarm cluster, this needs to be done on every host, of course.

@mrusme It sounds like there are three features requested here:

Restarting all tasks. This will spawn new container tasks for all existing tasks, honoring rolling update parameters. (@thaJeztah, do we have an issue for this?)
Task signaling (sending a HUP to replicas of a service) (see #27081).
Task exec. This is more involved. You can already do this by execing on the task host, but we don't autoroute this in swarm.

These are all orthogonal issues. I'd recommend resubmitting these as separate issues to we can focus on the individual users.

Issues #27551, #27552, #27553 created. This issue can be closed now.

@frimdo Thank you!


Added engine_getPayloadV4 and engine_newPayloadV4 for Prague (EIP-7002)

EIP-7002 has been confirmed for Prague and it requires changes in the ExecutionPayload leading us to ExecutionPayloadV4. This also impacts two Engine API methods, leading us to engine_getPayloadV4 and engine_newPayloadV4.
Please note that Prague will also have EIP-6110 that also introduce new fields to ExeuctionPayload. I noticed that @mkalinin has already an experimental spec for the changes here.
I am not sure what is the best way to consolidate those changes. We can either merge the changes related to EIP-7002 first, and later consolidate the changes from eip6110.md, or I can integrate eip6110.md changes into this PR. Let me know what is the best approach.
This is my first PR on this repo so I apologize if I missed anything in the process.
PS.: due to the size of the blobs field in the examples, we can't see the diff for src/engine/openrpc/methods/payload.yaml online.

Maybe try a single blob instead of 3?

Done. I have updated the examples with a single blob in each method.

Is it possible to omit them or shorten them significantly?

This is something to consider as well. But it might make the example an invalid object. I guess this depends on what we expect from the example (do we want it to be a valid object).

OpenRPC page wasn’t lagging with 3 blobs, tho we will have more of them every time a new version of getPayload method is created so reducing the example to a single blob makes sense to me. Not having a diff on GH is annoying too but I think we can deal with this complexity for the next few times, there should not be many changes in the future as Ethereum is ossifying 🔜 (don’t quote me on that).

I agree that we might need to look into a better way of handling the blobs as we add more and more versions. But I think this should be handled in a separate PR.
I took a quick look into how OpenRPC page loads the example data and it is smart enough not to push the whole content to the blobs to the DOM (it only adds 10k characters for each). And you can only copy the full content to clipboard. So even though the browser still needs to download the whole content, it prevents the page to getting too slow.
Reducing the number of blobs in each example to 1 per list results in a smaller footprint then before so at least we are not making things worse :)


A rule to require one to always use @ instead of this

A feature request.
A rule to require one to always use @ instead of this.

You seem to have many requests for new rules. To me they seem overly strict. Are you willing to start building and maintaining these new rules? I try to get bugs dealt with quickly, but I generally leave new rules to whoever is going to use them.

Yea, I will try to look into how to make them. But probably I will need some help initially. :-)

:+1: I'll definitely help answer questions. You can probably also find many similar rules to get started. The "Building Custom Rules" on coffeelint.org has an overview of what's available. Core and 3rd party rules all have the same API access.
I thought I wrote some documentation somewhere with some guidelines on each linter type, but I can't find it. It obviously isn't helping anyone :(

OK, can you then go through tickets and tell me what would be good names for the rules? So what you think I should name them? If you have any preferences.

I'd probably name this one no_this.
I think it's conceptually very similar to the rule about preferring is over == but its named prefer_english_operator and I think doesn't totally fit.


error with MatPlot and qt5

Steps to reproduce

Start python with qt5 backend
Run from qcodes.plots.qcmatplotlib import MatPlot; MatPlot()
An error is generated

Expected behaviour
No error should occur.
Actual behaviour
The following error is generated:
Traceback (most recent call last):

  File "<ipython-input-1-9f230cb3ab97>", line 1, in <module>
    from qcodes.plots.qcmatplotlib import MatPlot; MatPlot()

  File "D:\users\eendebakpt\Qcodes\qcodes\plots\qcmatplotlib.py", line 43, in __init__
    self._init_plot(subplots, figsize, num=num)

  File "D:\users\eendebakpt\Qcodes\qcodes\plots\qcmatplotlib.py", line 59, in _init_plot
    figsize=figsize)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\pyplot.py", line 1178, in subplots
    fig = figure(**fig_kw)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\pyplot.py", line 527, in figure
    **kwargs)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\backends\backend_qt5agg.py", line 43, in new_figure_manager
    return new_figure_manager_given_figure(num, thisFig)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\backends\backend_qt5agg.py", line 50, in new_figure_manager_given_figure
    canvas = FigureCanvasQTAgg(figure)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\backends\backend_qt5agg.py", line 216, in __init__
    super(FigureCanvasQTAgg, self).__init__(figure=figure)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\backends\backend_qt5agg.py", line 65, in __init__
    super(FigureCanvasQTAggBase, self).__init__(figure=figure)

  File "d:\software\Anaconda\envs\eendebakpt\lib\site-packages\matplotlib\backends\backend_qt5.py", line 239, in __init__
    super(FigureCanvasQT, self).__init__(figure=figure)

TypeError: 'figure' is an unknown keyword argument

System
Windows, qcodes master commit 525949cee77be3f188e4a9c5085805c665b624dd

I had this error some time ago with an application I wrote myself. Then it was due to not using the appropriate matplotlib backend corresponding to the Qt version, but this doesn't seem to be the problem here.
Maybe it is something internal in matplotlib, since you're only doing a simple plt.subplots call?

Looks like something related to matplotlib ! What is the output of pip freeze ?

This is indeed caused by mixing QT5 and QT4 internally in the matplotlib backend.
PYQT5 switched to cooperative inheritance for subclasses.
Can you check if you have the QT_API environmental variable set.
In windows that would be
echo %QT_API%

in a cmd shell

The issue is related to Spyder using a different version of Qt then matplotlib in the ipython console. I can work around it by changing the Qt backend in the spyder preferences.

Should we close then ?

@unga I'll close the issue. It is something that needs to be fixed upstream.


Export the cf-components to make them accessible

Currently cf-components that utilize JS self-initialize without exporting their components, making the components inaccessible to the scripts that eventually require and utilize them. The init should eventually be removed with a Major release, but this is a stopgap solution for the time being to allow work elsewhere to continue.
Additions

Adds exports for each of the components

Testing

¯\(ツ)/¯ The final files aren't tested, should they be? They essentially just pass the component on while initializing it.

Notes

Should we just bite the bullet and do another Major release by properly exporting without initializing?

Todos

Stop initializing

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the development playbook
[x] Passes all existing automated tests
[ ] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] Visually tested in supported browsers and devices (see checklist below :point_down:)
[x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[x] Reviewers requested with the Reviewers tool :arrow_right:

¯(ツ)/¯ The final files aren't tested, should they be? They essentially just pass the component on while initializing it.

Files that just call other modules don't need a unit test in my opinion, they should be covered by the individual modules' tests.


Increase User-Friendliness of PTRun Value Generator

Description of the new feature / enhancement
Right now the value generator plugin in powertoys run only give empty box, there are no any helper

Compared with time date plugin, it will give you some options and give you some suggestions of what values this plugin can provide

What I'm going to suggest is adding dropdown just like time and date plugin
So, it will add suggestion, for example esc:data or base64d and give the quick description about how to use this command
This suggestion is coming from my frustration because I keep forgetting the usage of this plugin and should spend more time to read the documentation before I can fully utilize this great tool
Scenario when this would be used?
This will be helpful to faster know all of the feature this plugin can do, without looking for the documentation page
Supporting information
No response

That's definitely a must have.

I  would like to look at this, this will be my first contribution

@JeremyCPE
Your contribution is welcome and thank you for your work on this. Feel free to open a PR. If you have any further questions don't worry to ask them.

Hi @JeremyCPE, I want to know how is your progress regarding this issue
I made this simple PoC to give more concrete idea about my suggestion

I also haven't made a contribution to this repository yet, maybe we can collaborate together :)

Hi @azlkiniue , I haven't started to work on this issue.
As it doesn't like to be a big change I don't think a collaboration is necessary, so you can just take this issue :)
Thanks !


draft: avm recursion

Please read contributing guidelines and remove this line.

@jeanmon

Will be proceeded by jeans work


Update values schema for sidecarInjectorWebhook

@elfinhe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

mandiff_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Reopening per discussion offline.

@elfinhe: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

mandiff_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

mandiff_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mandiff_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

mandiff_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mandiff_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

gencheck_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

mandiff_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mandiff_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

gencheck_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test gencheck_operator

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mandiff_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mandiff_operator

test_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test test_operator

gencheck_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test gencheck_operator

mesh_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test mesh_operator

lint_operator
d285770b25d5a49dd4d6d6cb1d28fc92bdd38a9d
link
/test lint_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Need help:
I used 'make gen' to generate the values_types proto, but it will use github.com/gogo/protobuf/protobuf/google/protobuf instead of github.com/gogo/protobuf/types.
Also it will replace 'map[string]interface{}' with self defined type 'TypeMapStringInterface'.
Can someone teach me how to generate the .proto.go when change values_types.proto?
@ostromart, @morvencao


Remove deprecated dependencies

github.com/pkg/errors is deprecated in favor of the standard library
go.uber.org/multierr was used once and it's now part of the standard library in Go 1.20

Looks like the CI is failing due to the Go version used by GH Action being < 1.21.3

maybe we should set check-latest: true in the setup-go action configuration to force that action to skip the cache


Connection test fails forever after starting with inactive network

The connection test to WAN server fails forever, even if re-connect to active network after starting with inactive network.
I inspected the behavior with using Wireshark. It maybe seems the app can't connect to valid DNS server.

refs: https://github.com/nodejs/node/issues/1644

refs: github.com/nodejs/node/issues/1644

It seems fixed this problem.
If that problem relapsed, please report on this issue or make a new issue.


[DO NOT MERGE] Remove workarounds for passthrough hash

Now that multipage-frontend no longer requires any special passthrough
hash this can be removed

Corr look at that add to remove ratio ✂


Update await.js

Just formatted it a bit... this was a mess
Type

[ ] Bug Fix
[ ] Functions: <Function Name>
[ ] Callbacks: <Callback Name>
[ ] Handlers: <Handler Type>
[ ] Others: ______

Dependencies (Third Party Modules) needed: <Name | Github Link> (Maximum: 20MB~ size)
Want a credit? Discord tag or other social media link: <DiscordTag | OtherSocialMediaLink>
Referenced Issue: #NaN (Answer for an issue, if any)
Description
Just formatted the file

nvm it better to have messy code


Face detection bug

Problem
Hello !
I'm using JeelizWeboji and I have some bugs with the face detection. Sometimes (it's rare) the weboji does not bug and it reproduces well what we do on the webcam.
But many times, the weboji close one or the two eyes (open & close quickly) while your eyes are open (even if you are looking at the screen).
Same thing with the mouth, your mouth is close but the weboji have the mouth open (open & close quickly).
It looks like it couldn't detecting well you face...
Here is a video where I'm just looking at the screen without doing anything :
https://user-images.githubusercontent.com/25428670/132245415-2c72a468-8ba0-4871-8708-d54431234550.mp4
Questions
Do you have any explaination or solutions ?
Can you explain me, how the face detection works ? (I think I saw a doc about it but I can't find it anymore)
Hardware

Webcam : https://www.dell.com/fr-fr/shop/accessories/apd/a9580031
PC : https://www.dell.com/fr-fr/shop/cty/pdp/spd/g-series-5090-desktop

Note :
We already tried to have a light behind the webcam (so facing us), it's a bit better but we still have the problem...

Hi,
I cannot debug this without having the video input too (your face).
I need 2 videos: the output rendering and the input video both, and the input video alone.
You are only showing the output rendering.
The input video should be in a good quality. Backlight, face too much zoomed out, viewing angle, low lighting can deteriorate the quality.
In kiosk mode, I strongly encourage to have light sticks around the screen to enlight the face, avoid backlights and remove shadows. Having a light is good but you need good lights, like in photography. Not strong and extensive.
Face detection is not open sourced in this library.
I can work to optimize and disable some morphs, but I will charge for this. Please contact me at<EMAIL_ADDRESS>to get more information.
Best regards,
Xavier

I have tuned more accurately the stabilization of the values returned by the neural network to have less jittering in the last commit.
I hope it will make it work better.


ocssvc: better names for properties: ocs.go

Perhaps some of the names could be better and self-explanatory, e.g.:
type CapabilitiesDav struct {
  Chunking string `json:"chunking" xml:"chunking"`
  }

ChunkingVersion instead of Chunking?
Otherwise its going to be an endless guessing game in the source code to figure out what it means.

better naming makes sense, but the usage is limited to the ocs service ... at least for now.


Feat: Improved UI of pricing page

Describe the feature
Pricing page doesnt look good and text is also not visible in it .
I added proper color to text so that it looks good in light and dark mode.
Also improved it's footer
Add ScreenShots
Before:
https://github.com/anuragverma108/SwapReads/assets/162733812/33dc99ba-d019-4af3-be59-9a59e63af010
After:
https://github.com/anuragverma108/SwapReads/assets/162733812/fd58f93e-9cf5-47f2-9154-3c426f987ac0
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@anuragverma108 @RitiChandak @RishabhDhawad @huamanraj I want to work on this issue please assign it to me and review my PR , If you like my work please merge it under gssoc


Expose the (add/remove)Directory functions via the theme()->getLayers…

…()->getDirectory() call
This allow's modifications to still add an external Theme directory outside of the Elkarte theme folder structure, similar to how you can on Elkarte 1.1

Appears like a good item to expose ... merged

Why do you need to get the list of directories?
And anyway you should not get it from the templates but from the theme loader I guess...

Why do you need to get the list of directories?
And anyway you should not get it from the templates but from the theme loader I guess...

I wanted the current instance, that seemed the best way. I use it like this in TinyPortal https://github.com/Tinyportal/ElkTP/blob/50e67d905587ed69d80bc6b3ef801b59fff2b6ed/TinyPortal/Integrate.php#L563


Consolidate openjdk test targets

We may run different JVM options for different JVM implementations in OpenJDK tests. For example, we have test targets jdk_math and jdk_math_j9. They run the same OpenJDK test but with different JVM options.
It looks like we can consolidate these test targets into one by leveraging our makefile.
For example, set special OPENJ9_OPTIONS for openj9 jvm in openjdk.mk. The default value is empty. It can be used in variation in playlist.xml. We can do similar settings for -timeoutHandler....
The purpose of this is to consolidate OpenJDK test targets and reduce the number of targets. Having the same test name for different JVM will make maintenance, debug, and triage easier.

@LongyuZhang Could you help with this task? Thanks

@LongyuZhang Could you help with this task? Thanks

PR is delivered. Close this issue.

PR is delivered. Close this issue.


<EMAIL_ADDRESS>install error - access to settings.xml is denied

I got an error on cemu install. The app is installed despite the error, but I believe settings.xml is incorrect.
It created a folder called settings.xml instead of a file, inside persist folder.
Log:
Installing 'cemu' (1.26.2f) [64bit]
Loading cemu_1.26.2.zip from cache.
Checking hash of cemu_1.26.2.zip ... ok.
Extracting cemu_1.26.2.zip ... done.
Running installer script...
Linking ~\scoop\apps\cemu\current => ~\scoop\apps\cemu\1.26.2f
Creating shim for 'Cemu'.
Creating shortcut for Cemu (cemu.exe)
Persisting settings.xml
Persisting controllerProfiles
Persisting gameProfiles
Persisting graphicPacks
Persisting mlc01
Persisting sharedFonts
Persisting shaderCache\transferable
Persisting keys.txt
Running post-install script...
New-Item:
Line |
5 |         New-Item -ItemType File "$dir$_" | Out-Null
|         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Access to the path 'C:\Users\ricar\scoop\apps\cemu\current\settings.xml' is denied.
'cemu' (1.26.2f) was installed successfully!
'cemu' suggests installing 'cemuhook'.
'cemu' suggests installing 'extras/vcredist2015'

cc @beyondmeat

This PR fixed it for me:
#638


Data: project addition by codewithavantika

Add a new project to the list
I want to add my Flask URL Shortener project in the project list.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Completed. Thanks for your contributions 🎉 ❤


Problem with downloading files

Hi. I have a problem with downloading files. Website is load successfully, but didn't downloading files. I click on Download button, but file not appear in Downloads folder.
Informations:
OS: Linux
Webview: WebKitGTK-4.0

Download is a browser functionality, not the rendering engine functionality. I believe you need to implement the browser yourself.

@Anil8753

Download is a browser functionality, not the rendering engine functionality. I believe you need to implement the browser yourself.

I use this C++ script.


Crash after attempting to delete requests

Steps to reproduce the problem:

MITM some traffic, over say, 20 minutes
Start deleting (explicitly pressing "d") requests in the dump
After deleting some, mitm crashes.

What is the expected behavior?
Not to crash, I suppose.
What went wrong?
Stack trace:
Traceback (most recent call last):
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/console/__init__.py", line 614, in run
    self.ui.run_wrapper(self.loop)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/vendor/lib/python2.7/site-packages/urwid/display_common.py", line 757, in run_wrapper
    return fn()
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/console/__init__.py", line 845, in loop
    k = self.view.keypress(size, k)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/vendor/lib/python2.7/site-packages/urwid/container.py", line 1128, in keypress
    return self.body.keypress( (maxcol, remaining), key )
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/console/flowlist.py", line 269, in keypress
    return urwid.ListBox.keypress(self, size, key)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/vendor/lib/python2.7/site-packages/urwid/listbox.py", line 987, in keypress
    key = focus_widget.keypress((maxcol,),key)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/console/flowlist.py", line 147, in keypress
    self.state.delete_flow(self.flow)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/console/__init__.py", line 331, in delete_flow
    ret = flow.State.delete_flow(self, f)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/flow.py", line 548, in delete_flow
    self.flows._remove(f)
  File "/usr/local/Cellar/mitmproxy/0.11.3/libexec/lib/python2.7/site-packages/libmproxy/flow.py", line 462, in _remove
    self._list.remove(f)
ValueError: list.remove(x): x not in list

mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
Shutting down...

Any other comments?
This could be a one-off, I'm having difficulty reproducing consistently it but thought it would be best to log it here in case someone else sees it and can. I'm also unable to give you the session (I didn't save it, and it contained sensitive data).

mitmproxy version: mitmproxy 0.11.3
Operating System: OS X 10.10.3

Hi there. This issue has been fixed on the current master - a new release (0.12.1) will be out in the next week. In the meantime, if you're keen, you can check out the github master. Thanks for reporting the problem!


license and copyright ?

maybe it is on purpose but the README states the MIT license but the license file is missing from the repository. Is the license MIT ? and who is the copyright owner and what is the copyright year?

Thanks, fixed in https://github.com/Neural-Systems-at-UIO/WebAlign/commit/92c64efb1b3a1d5046d4cb05b48979455eb52a4d


feat(doc): Add guidance for developers about using autoware evaluator

Description
Related issue:

https://github.com/autowarefoundation/autoware-documentation/issues/548

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@xmfcx I used the Others section for this documentation but I couldn't be sure if it is the correct place or not.

cc @xmfcx @mitsudome-r
Hi,
The document is ready for review, but there are some blockers:

Regression Test Procedures:

In the issue created by Fatih, one of the conditions was: Procedures for running regression tests to ensure no disruptions are described.
To achieve this, we must download all scenarios from Autoware Evaluator to run them locally. However, during our discussion with Igata-san in the ODD WG, we decided this wouldn't be feasible because map versions in the cloud can vary, and a scenario depends not only on the map but also on its specific version.
Alternatively, developers can execute tests in the cloud for their PRs using Autoware Evaluator.

Access to the AWF Project:

We discussed with @mitsudome-r -san in previous weeks that the AWF Project will be made public (accessible without login), but this hasn't been implemented yet. Once it is, I may need to update the documentation links. Currently, this process is mentioned as Under Development in the documentation.

Except for these points, the document is ready for review. If there is any missing point or possible improvement, let me know.

cc @xmfcx @mitsudome-r
After we discussed with Igata-san how people should be invited to the AWF project, I updated the documentation. Until make the AWF project more open, we decided to ask the new user to join ODD WG once to share his/her interest for now (Because of the AWF project's limited resources).
Currently, this PR is ready for review.


ti-tv-ratio-sample.sql

ti/tv ratio calculation per sample

Coverage remained the same at 62.766% when pulling ca13d93922f31af8c0dbe8a3023cd3441c124d5a on bthiruv:patch-2 into 14fedc30f99d53134adf74b195fffdb9763d5475 on googlegenomics:master.

Thank you @bthiruv !  I'll merge this at the same time I add a plot for it.


fix(MethodChainMutatorSpec): Fix group name, so it matches the name of the mutator.

Nice find!

Thanks! Next time please scope a commit like this with test(..). That way, it won't end up in our release notes as a bug being fixed. :+1:


dotnet commands interpret string content

Hello guys, not sure to be at the right place.
I am running this command:
dotnet pack -c Release /p:Version=1.0.0-beta-002 /p:PackageReleaseNotes="* BREAKING CHANGE: Fix icons display and implement Font Awesome helpers
 * Fix #61: Add `is-fullwidth` support for Table element
 * Fix #59: Add color support for the navbar compoenent
 * Fix #67: Enforce DSL synthax with `[<RequireQualifiedAccess>]` attribute
 * BREAKING CHANGE: Fix #70: Make button support different elements. To have the same behavior as before, replace: `Button.button` with `Button.button_a`"

And I get this error:
MSBUILD : error MSB1006: La propriété n'est pas valide.
Commutateur :  replace: `Button.button` with `Button.button_a`

Basically it's saying: The property is invalid
I suspect the engine, to catch the keyword replace even if it's in a string argument. I would expect the engine to not catch string content from cli arguments.

Ok, so it's seems the problems come form the ,.
When I execute the next command, I removed the comma, it's working.
dotnet pack -c Release /p:Version=1.0.0-beta-003 /p:PackageReleaseNotes="* BREAKING CHANGE: Fix icons display and implement Font Awesome helpers
 * Fix #61: Add `is-fullwidth` support for Table element
 * Fix #59: Add color support for the navbar component
 * Fix #67: Enforce DSL synthax with `[<RequireQualifiedAccess>]` attribute
 * BREAKING CHANGE: Fix #70: Make button support different elements. To have the same behavior as before replace `Button.button` with `Button.button_a`"

Glad you found the issue. http://github.com/nuget/home is probably the best place to open issues on dotnet pack. I'm going to go ahead and close this here but if you think there is a bug to be fixed, go ahead an open an issue there.


Add DelegateWeakEventManager, WeakEventManager, AsyncCommand & AsyncValueCommand

Fixes https://github.com/xamarin/XamarinCommunityToolkit/issues/293
Docs for Toolkit PR https://github.com/xamarin/XamarinCommunityToolkit/pull/597/files
What changes to the docs does this PR provide?

Adds DelegateWeakEventManager and WeakEventManager<T>

PR Checklist
Please check if your PR fulfills the following requirements:

[x] For new pages, used the provided template.
[x] For new features, added an entry in the Table of Contents.
[x] Ran against a spell and grammar checker.
[x] Contains NO breaking changes.

Other information

Docs Build status updates of commit 3323e03:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/helpers.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c74bff1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/helpers/delegateweakeventmanager.md
:warning:Warning
View
Details

docs/helpers/weakeventmanagerextensions.md
:warning:Warning
View
Details

docs/helpers/weakeventmanagert.md
:warning:Warning
View
Details

docs/objectmodel/asynccommand.md
:warning:Warning
View
Details

docs/objectmodel/asyncvaluecommand.md
:warning:Warning
View
Details

:warning:Warning

Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers.md
:white_check_mark:Succeeded

docs/helpers/delegateweakeventmanager.md

Line 89, Column 3: [Warning-file-not-found] Invalid file link: '../weakeventmanagert.md'.

docs/helpers/weakeventmanagerextensions.md

Line 45, Column 3: [Warning-file-not-found] Invalid file link: '../delegateweakeventmanager.md'.
Line 46, Column 3: [Warning-file-not-found] Invalid file link: '../weakeventmanagert.md'.

docs/helpers/weakeventmanagert.md

Line 75, Column 3: [Warning-file-not-found] Invalid file link: '../delegateweakeventmanager.md'.

docs/objectmodel/asynccommand.md

Line 158, Column 3: [Warning-file-not-found] Invalid file link: '../asyncvaluecommand.md'.

docs/objectmodel/asyncvaluecommand.md

Line 162, Column 3: [Warning-file-not-found] Invalid file link: '../asynccommand.md'.

Line 0, Column 0: [Warning-microsoft-graph-api-failed]

Call to Microsoft Graph API failed: Code: generalException
Message: An error occurred sending the request.
 Try closing and reopening the PR. If you get this Error again, file an issue.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 559ed5b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/helpers/weakeventmanagerextensions.md
:warning:Warning
View
Details

docs/helpers/weakeventmanagert.md
:warning:Warning
View
Details

docs/objectmodel/asynccommand.md
:warning:Warning
View
Details

docs/objectmodel/asyncvaluecommand.md
:warning:Warning
View
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers.md
:white_check_mark:Succeeded

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md

Line 45, Column 3: [Warning-file-not-found] Invalid file link: '../delegateweakeventmanager.md'.
Line 46, Column 3: [Warning-file-not-found] Invalid file link: '../weakeventmanagert.md'.

docs/helpers/weakeventmanagert.md

Line 75, Column 3: [Warning-file-not-found] Invalid file link: '../delegateweakeventmanager.md'.

docs/objectmodel/asynccommand.md

Line 158, Column 3: [Warning-file-not-found] Invalid file link: '../asyncvaluecommand.md'.

docs/objectmodel/asyncvaluecommand.md

Line 162, Column 3: [Warning-file-not-found] Invalid file link: '../asynccommand.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8acc0c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers.md
:white_check_mark:Succeeded

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 20280b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5ad4e49:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 598ec48:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fe744b9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit dc55174:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 31b4135:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a1a7f5e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 555af40:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/helpers/delegateweakeventmanager.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagerextensions.md
:white_check_mark:Succeeded
View

docs/helpers/weakeventmanagert.md
:white_check_mark:Succeeded
View

docs/objectmodel/asynccommand.md
:white_check_mark:Succeeded
View

docs/objectmodel/asyncvaluecommand.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Compilation with Visual Studio 2015 Community

I'm trying to compile libuvc with vs 2015 but it fails because of the pthread.h.
How can I compile libuvc with vs 2015 ?

Build pthread for windows found at "https://github.com/GerHobbelt/pthread-win32.git" and include it in the CMakeLists.txt of Libuvc

You can also do the following:
replace
#include <pthread.h> in libuvc_internal.h
with
#ifdef _WIN32 #include "winpthreads.h" #else #include <pthread.h> #endif
After doing so, you must comment out the timespec struct in winpthreads.h, since windows has it shipped in later sdk versions.

Thanks