Tidy get_datetime_index

Detailed Description
https://github.com/openclimatefix/nowcasting_dataset/pull/229#discussion_r730788607
do we need get_datetime_index in the ML models of the data sources
Context
Tidy up un-needed code
Possible Implementation
remove it, check everything still works

Ill close this for now. ML models got moved to nowcasting_dataloader and several PRs have been merged relating to this


Slow for large datasets

Thank you for creating a nice package. It is very handy to install such a functionality with pip.
However, I find this package to be rather slow for large datasets in comparison with the LinearRegDiagnostic class described in the Linear regression diagnostics example of statsmodels. This may indicate some inefficiency of the package.
Example:
df = sm.datasets.get_rdataset("ames", "openintro").data
res = smf.ols("np.log10(price) ~ Q('Overall.Qual') + np.log(area)", df).fit()

lmdiag
%%time
lmdiag.plot(res)

CPU times: user 15.1 s, sys: 215 ms, total: 15.3 s
Wall time: 16.1 s

LinearRegDiagnostic
%%time
LinearRegDiagnostic(res)()

CPU times: user 2.17 s, sys: 125 ms, total: 2.29 s
Wall time: 2.17 s

Hi @tueda , thanks for your feedback!
Interesting to see LinearRegDiagnostic. Never seen it before, it certainly wasn't there when I implemented lmdiag 4 years ago.
Looking quickly over their code, they do some calculations smarter than I did!
To be honest, looking at lmdiag now, with 4 years more experience, I think its code quality is really poor. E.g. with the same calculations being repeated for the various plots etc...
Unfortunately, I don't have the sparetime for a rewrite (which would be best). I see some low effort optimizations, which could give ~20% speed-up, and which I might be able to do, but I'm not sure if it's worth it:
I wonder if it makes more sense to archive lmdiag and redirect people to the faster and more feature-rich LinearRegDiagnostic instead?
May I ask, why you would prefer to use lmdiag instead of LinearRegDiagnostic?
(It's a shame, that they implemented this only as an "example" (w/o license?) and not integrated it in statsmodels...)

Interesting to see LinearRegDiagnostic. Never seen it before, it certainly wasn't there when I implemented lmdiag 4 years ago.

Indeed, the example notebook has appeared in v0.14.0, which is rather new.

Unfortunately, I don't have the sparetime for a rewrite (which would be best). I see some low effort optimizations, which could give ~20% speed-up, and which I might be able to do, but I'm not sure if it's worth it:

I understand that you are busy and that it is not easy to devote time to maintaining and improving the library. This is not urgent.

May I ask, why you would prefer to use lmdiag instead of LinearRegDiagnostic?

Personally, I prefer the simple syntax lmdiag.plot(res) to LinearRegDiagnostic(res)(). Another important advantage of lmdiag is that it can be easily installed by pip. It is very handy for use with Google Colab etc.: much better than copying long code from the example notebook.


question about plans

Hi
I see 5 years no changes. I guess this is something is left behind?
I was working on something similar and wondering if yours figure out some pain points
https://github.com/sakrist/jsb.

Hi,
Currently this is library is abandoned, yes.

Ok, you can close issue then. thanks for reply


How to read multiple messages from a single file or bytearray

It seems I am able to read a single message from a file, but as soon as there is more than 1 I get a wireerror(unexpectedwiretype(WireTypeFixed32)) error, looking at the code, it seems there is a !eof loop around field types for each message. Presumably when there are multiple messages these are also being decoded?

Protobuf messages are not internally length-delimited. Each message is always until the end of file.
The usual solution is to write them length-delimited. E. g. prepend each message with length, and read length before reading a message. CodedInputStream and CodedOutputStream provide utilities for that pattern.
This pattern is described in Google protobuf documentation: https://developers.google.com/protocol-buffers/docs/techniques#streaming


Revert explicit definition of U8 KV-cache

@andreyanufr

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Mixing with .NET Framework

Hi!
So I'm trying to sort of mix this package for a .NET 6 site (API) with an older .NET Framework site (UI). I'm trying to use this backplane with the .NET 6 site, and that classic Microsoft.AspNet.SignalR.SqlServer backplane for the .NET Framework site.
So my first question is even if I could get the table names to match with both libraries, would I be able to insert messages from the .NET 6 site and have my .NET Framework site read and process them correctly, given that the core SignalR libraries are different? I know some docs say you can't mix versions of the server and client, but I feel like this scenario is more like mixing two versions of the servers and trying to share the same database backplane. (Edit: Eh, I guess it's the same as mixing server and client)
Thanks!

No, you cannot do that. The data is entirely incompatible between SignalR Core and Classic SignalR, independent of the choice of backplane - the two versions represent messages significantly differently. On top of that, the way that data is encoded into the SQL Server tables is also entirely different between the two implementations of the SQL Server backplane.

Thanks for your quick response!


Map sub-command to nested yaml elements

my question is...
( how can I bind flags to nested yaml elements ?  )
I'm evaluation urfave/cli - so I'm a newbiew here - as foundation for the new camel-k cli which is now based on spf13/cobra and I'm trying to figure out how to property bind sub-command flags from a nested yaml structure.
As example the camel-k cli has a run sub command with it's own flags like dependency and I want to be able to load values for such flags from a YAML like:
run:
  dependencies:
  - foo
  - bar

I've created the following example:
func main() {
	var kubeconf string
	var namespace string
	var dependencies cli.StringSlice

	flags := []cli.Flag{
		&cli.StringFlag{
			Name:  "kamelconfig",
			Usage: "The location of the kamel cli configuration",
			Value: ".kamel/config.yaml",
		},
		altsrc.NewStringFlag(&cli.StringFlag{
			Name:        "kubeconf",
			Usage:       "The path to the kubernetes config file to use for CLI requests",
			Destination: &kubeconf,
			EnvVars:     []string{"KUBECONFIG"},
		}),
		altsrc.NewStringFlag(&cli.StringFlag{
			Name:        "namespace",
			Aliases:     []string{"n"},
			Usage:       "The `namespace` to use for all operations",
			Destination: &namespace,
		}),
	}

	runFlags := []cli.Flag{
		altsrc.NewStringSliceFlag(&cli.StringSliceFlag{
			Name:        "dependency",
			Usage:       "dependency",
			Destination: &dependencies,
		}),
	}

	app := &cli.App{
		Name:                 "kamel",
		Usage:                "kamel",
		EnableBashCompletion: true,
		Before:               altsrc.InitInputSourceWithContext(flags, altsrc.NewYamlSourceFromFlagFunc("kamelconfig")),
		Flags:                flags,
		Commands: []*cli.Command{
			{
				Name:  "run",
				Usage: "run",
				Flags: runFlags,
				Action: func(c *cli.Context) error {
					fmt.Println(dependencies)
					return nil
				},
			},
		},
		Action: func(c *cli.Context) error {
			fmt.Println(kubeconf)
			fmt.Println(namespace)
			return nil
		},
	}

	err := app.Run(os.Args)
	if err != nil {
		log.Fatal(err)
	}
}

I can't figure out how I can achieve what I'm looking for as:

the Before option is set on the root command: do I need to set it on each command ?
is there a way to set the name of the field used to search in the yaml source ? as example here I'd like to set that the dependency get translated to dependencies and the full key should be run.dependencies to properly navigate the path of the source

btw, I'm not even sure if it is possible

question +1

I'm also curious about this...

I'm also curious about this...

Nope

Nope

@lburgazzoli I added two lines to your code
package main

import (
	"fmt"
	"log"
	"os"

	"github.com/urfave/cli/v2"
	"github.com/urfave/cli/v2/altsrc"
)

func main() {
	var kubeconf string
	var namespace string
	var dependencies cli.StringSlice

	flags := []cli.Flag{
		&cli.StringFlag{
			Name:  "kamelconfig",
			Usage: "The location of the kamel cli configuration",
			Value: ".kamel/config.yaml",
		},
		altsrc.NewStringFlag(&cli.StringFlag{
			Name:        "kubeconf",
			Usage:       "The path to the kubernetes config file to use for CLI requests",
			Destination: &kubeconf,
			EnvVars:     []string{"KUBECONFIG"},
		}),
		altsrc.NewStringFlag(&cli.StringFlag{
			Name:        "namespace",
			Aliases:     []string{"n"},
			Usage:       "The `namespace` to use for all operations",
			Destination: &namespace,
		}),
	}

	runFlags := []cli.Flag{
		altsrc.NewStringSliceFlag(&cli.StringSliceFlag{
			Name:        "dependency",
			Usage:       "dependency",
			Aliases:     []string{"run.dependencies"},  // added this line
			Destination: &dependencies,
		}),
	}

	flags = append(flags, runFlags...)   // added this line

	app := &cli.App{
		Name:                 "kamel",
		Usage:                "kamel",
		EnableBashCompletion: true,
		Before:               altsrc.InitInputSourceWithContext(flags, altsrc.NewYamlSourceFromFlagFunc("kamelconfig")),
		Flags:                flags,
		Commands: []*cli.Command{
			{
				Name:  "run",
				Usage: "run",
				Flags: runFlags,
				Action: func(c *cli.Context) error {
					fmt.Println(dependencies)
					return nil
				},
			},
		},
		Action: func(c *cli.Context) error {
			fmt.Println(kubeconf)
			fmt.Println(namespace)
			return nil
		},
	}

	err := app.Run(os.Args)
	if err != nil {
		log.Fatal(err)
	}
}

and updated your .kamel/config.yaml as follows
$ cat .kamel/config.yaml
kubeconf: hello
namespace: dd
run:
  dependencies:
  - foo
  - bar

This is what I get when I run the code
$ go run main.go run
{[foo bar] true}
$ go run main.go
hello
dd

@dearchap thanks for looking into this, two notes:

dogin flags = append(flags, runFlags...) seems counter intuitive as the runFlags do not belong to the root command
adding run.dependencies as an alias has  a side effect right ? so one can do things like kamrl run --run.dependencies=foo

What is the experience that you are looking for ?

I think what I see here is good enough,
As a suggestion, it would be nice if NewYamlSourceFromFlagFunc would accept also some sort of root node, like:
    Before: altsrc.InitInputSourceWithContext(
                    runFlags,
                    altsrc.NewYamlSourceFromFlagFunc("kamelconfig", "run")),

The flag is searched up the context chain so it is not strictly necessary to specify the root node, unless you want the search to stop at current level


Remove workaround for pub extern crate

On semi-recent Rust versions (I think 1.8+) this now works properly.
Closes #655

bors r+

This looks like a temporary failure in rustup.  We can try remerging.
bors r+ susurrus


[Navigation] Suggestion: Finish activity when BottomSheet is dismissed and there is nothing else on the backstack

Description
I am implementing DeepLinks into my app and in one of my use cases I am deepLinking into a bottomSheet() destination.
When I tap outside of the bottom sheet, then the bottom sheet is animated away but the scrim never goes away and the activity is not finished.
Steps to reproduce

DeepLink into a bottomSheet() destination.
Tap outside of the bottom sheet.

Expected behavior
The activity holding the Composables to be finish()ed, given that nothing else is in the backstack.
Additional context
I am not sure if this is a responsibility of navigation-material or not, or whether it should do it automaticallly. I found it weird that I had to do this manually. Plus I had to do some digging in order to figure out how to do this (searched for some sort of bottomSheet state first, but there is none).
As a workaround I am doing:
In my bottomSheet() destination:
backstackEntry.OnDestroy {
    if (navController.previousBackStackEntry == null) {
        finish()
    }
}

OnDestroy implementation :

@Composable
private fun NavBackStackEntry.OnDestroy(action: () -> Unit) {
    DisposableEffect(this) {
        val observer = LifecycleEventObserver { _, event ->
            if (event == Lifecycle.Event.ON_DESTROY) {
                action()
            }
        }
        lifecycle.addObserver(observer)
        onDispose {
            lifecycle.removeObserver(observer)
        }
    }
}

As per the docs, Navigation will never finish() your activity for you: the activity back stack is not part of the Navigation back stack.
You'll note that Navigation already correctly does not intercept the system back button when there is only one destination on the back stack - i.e., swiping back will close your activity (i.e., do the default behavior of the system back button).
I would strongly recommend reconsidering whether deep linking to a FloatingWindow destination, such as a bottom sheet makes any sense whatsoever: having your destination above whatever global UI you have outside of your NavHost and an empty NavHost underneath is what you are asking for, what you are getting, and exactly not what a user wants to see.
If you want a dialog styled activity that appears above another app, you'll want to create a separate activity for that deep link.


Package cmake modules in grpc-devel

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[ ] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary
I've encounted some source code that expects to find gRPCConfig.cmake under /usr/lib/cmake. The grpc upstream package typically provides this, but the Mariner spec was deleting these cmake files for some reason.
Change Log
Removes the logic to delete the *.cmake files, and packages them up in grpc-devel.
Does this affect the toolchain?
No.
Test Methodology

In progress.

Thanks for the gentle reminder :). I've added a changelog entry.
I also see spec linting isn't happy, but presumably isn't happy with what's already checked into main. What's the recommendation for changes like this? Is it preferred that I keep the change more minimal (i.e., as-is) or is it requested to get clean since I'm going in and touching the spec anyhow?

I also see spec linting isn't happy, but presumably isn't happy with what's already checked into main. What's the recommendation for changes like this? Is it preferred that I keep the change more minimal (i.e., as-is) or is it requested to get clean since I'm going in and touching the spec anyhow?

The generally accepted view is that linting is appreciated but not necessary for small, targeted changes. Sometimes the linter gives us some bad suggestions (mea culpa, working on addressing those), so I'd take suggestions with a grain of salt if they are questionable/don't seem to add much value. If you find a bad suggestion, feel free to open a bug in ADO and assign it to me for fixing.
In this case all of the suggestions look safe to take- fixing whitespace issues and alphabetizing build requirements shouldn't break anything here!


Submit PR only once but trigger multiple Jenkins test processes

In GitLab by @wknet123 on Feb 9, 2018, 11:21

In GitLab by @luotian-github on Nov 8, 2019, 07:46
Process #84,#85,#86

In GitLab by @luotian-github on Nov 8, 2019, 07:46
test devops issue

In GitLab by @wknet123 on Nov 8, 2019, 07:46
Please verify this issue to check whether it is still existing.

In GitLab by @luotian-github on Nov 8, 2019, 07:46
not found this problem

In GitLab by @sokril on Nov 8, 2019, 08:18
closed

In GitLab by @sokril on Nov 8, 2019, 08:18
assigned to @luotian-github


Cannot reattach to mern app after saving file

Testing #27463

Linux Ubuntu 16.04 in Parallels, 2 proc, 4gig memory, 128mb graphics memory

Insiders build

Settings ensure that I do not have autosave on:
"files.autoSave": "off"

launch.json (note runtimeExecutable is set to local nodemon):

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "protocol": "inspector",
            "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
            "runtimeArgs": [
                "--inspect=9222"
            ],
            "program": "${workspaceRoot}/index.js",
            "port": 9222,
            "restart": true,
            "env": {
                "BABEL_DISABLE_CACHE": "1",
                "NODE_ENV": "development"
            },
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        }
    ]
}

F5 to run/debug the app, takes some time for it to start

Edit server/dummyData.js (seems like any edit is fine, I simply added a new const content4

Save dummyData.js
Result in terminal (note the Starting inspector on <IP_ADDRESS>:9222 failed: address already in use):

[nodemon] files triggering change check: server/dummyData.js
[nodemon] matched rule: **/home/parallels/src/mern-starter/server/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] server/dummyData.js

[nodemon] starting `node --inspect=9222 index.js`
[nodemon] child pid: 8501
Starting inspector on <IP_ADDRESS>:9222 failed: address already in use
[nodemon] app crashed - waiting for file changes before starting...
cd /home/parallels/src/mern-starter ; env BABEL_DISABLE_CACHE=1 NODE_ENV=development /home/parallels/src/mern-starter/no
de_modules/.bin/nodemon --inspect=9222 index.js

Then I get this Error:
Get "Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED <IP_ADDRESS>...)

Cannot reproduce on macOS. Will now try to reproduce on ubuntu...

Cannot reproduce on ubuntu 16.04.
From the console output "Starting inspector on <IP_ADDRESS>:9222 failed: address already in use" I suspect that a node.js process is already running on port 9222 from a previous session.

I can reproduce this every time.
git clone https://github.com/Hashnode/mern-starter.git
npm install

launch.json:
{
    // Use IntelliSense to learn about possible Node.js debug attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "protocol": "inspector",
            "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
            "runtimeArgs": [
                "--inspect=9222"
            ],
            "program": "${workspaceRoot}/index.js",
            "port": 9222,
            "restart": true,
            "env": {
                "BABEL_DISABLE_CACHE": "1",
                "NODE_ENV": "development"
            },
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen"
        }
    ]
}

Is there anything else I can provide?

I still cannot reproduce.


Create global teams which could be used by each organization

Feature Description
My original concern was to find a way to made all repository (even privates) listable for each registered user cf. feature request #23117  (as I could not reopen the FR, I create a new one).
@wolfogre suggests my to use teams for this, which is a good way to solve my issue but it is not very "comfortable" to use. Because those teams have to be created for each organization and when a new user have to be added, it must be done for each organization!
It is possible to create a kind of "default/global/template teams", which could be used by each organization?
For example, a Gitea admin user creates global teams with default allowed accesses.
Then for each organization, those "global teams" are visible and could be used as they are or with"adjusted" allowed accesses.
This will allow administrators to managed those global teams, and all changes will be applied to any organization which uses those teams.
Is this feasible or will it break Gitea?
Screenshots
No response

Is this a duplication of #3642?

@lunny Yes! This is exactly what I need.
Sorry  for the noise, haven't see it.
Is this FR still "alive", is there a chance it could be implemented in a future release of Gitea?


Add columns for TransferData in Domain and Contact

Altered table Contact and Domain to add columns for TransferData.

This change is

db/src/main/resources/sql/flyway/V27__add_columns_for_transfer_data.sql, line 19 at r4 (raw file):
Previously, hstonec (Shicong Huang) wrote…

    add column transfer_billing_cancellation_id int8,
    add column transfer_billing_event_id int8,
    add column transfer_billing_recurrence_id int8,

So, I ended up with adding these 3 columns and transfer_autorenew_poll_message_id in Contact which should not include them. The reason is TransferData object is embedded in both DomainBase and ContactResource, and when we add a TransferData transferData field into the entity class, each field defined in the embeddable class will become a column of the entity, there is no way to exclude certain column.
The recommended solution would be have an abstract TransferData class containing the common fields, and then have a DomainTransferData and ContactTransferData extending it and contain their own fields. Obviously, this will change a lot of things and we need to verify if it is feasible especially when we are migrating the database.
So, my proposal is:

We continue with the single TransferData class, and add all transfer related columns in both Domain and Contact table. This would work in any condition because we just add some unused columns in Contact and our code controls that we won't write anything in them. (Also, this is actually what we do in Datastore).

Finish the migration to Cloud SQL, and deprecate the Datastore solely fields and annotations in TransferData.

Refactor the TransferData class to have two subclasses DomainTransferData and ContactTransferData.

Delete unused fields in Contact table.

If we feel that we still want to have the final class version before migration, we can still at least check this PR in to unblock the other work, then start investigating the feasibility to refactor the classes to make them work for both Datastore and Cloud SQL. Any thoughts? (I can put this in a one-pager for further discussion)

@cydeweys  Not sure if you noticed this but this answered your question why there are some fields in Contact but should not exist.


[DRAFT] Rename symbols in SIKE R1 code to avoid future naming/linking conflicts

Issue # (if available): https://github.com/awslabs/s2n/projects/7
Description of changes: Renames files/symbols of SIKE R1 code to avoid naming/linking conflicts when we eventually import SIKE R2 code.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (sikenamespace@7691d52). Click here to learn what that means.
The diff coverage is n/a.


Adding Icons Option And Updating README

Now you can enable/disable icons.
If you set icons: false it won't even load fontawesome:
+  <% if (theme.icons){ %>
   <%- css('css/font-awesome.min.css') %>
+  <% } %>

I have also updated README accordingly

LGTM. Thank you, It looks awesome and helpful, I'll update it which I currently used.

There are lots of options for links placement:

On header right-hand
At the buttom after copyright content...
We can use <hr> or not...
Different color...
To be only on the home page, not archives or posts...

What do you think? Do you like its current position?

I think current header position is better, because of alignment with content.
What you said Improvement, I think it's great if we completed. Docs may become more words but theme may become more convenient for customization.


Not support from openapi_3 to swagger_2

From readme, it says to support. But I got this error,
Fatal Error: Unable to convert from openapi_3 to swagger_2
    at Promise.try (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/lib/base_format.js:160:13)
    at tryCatcher (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/util.js:16:23)
    at Function.Promise.attempt.Promise.try (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/method.js:39:29)
    at module.exports.BaseFormat.convertTo (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/lib/base_format.js:154:21)
    at Converter.getSpec.then.fromSpec (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/index.js:33:32)
    at tryCatcher (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/Users/shenghu/.nvm/versions/node/v7.8.0/lib/node_modules/api-spec-converter/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)

Is there anything I missing?

I'm sorry, that is a copy-and-paste error in the README. It would not be possible to convert an openapi_3 definition to swagger_2 easily, as information would be lost in several areas and some features are completely unsupported.

For a one-off conversion you could try https://apimatic.io/transformer but I'd suspect the output would need hand-editing.

I have raised a PR #135 to update the README - thanks for pointing it out!
Probably your best option is to convert the Swagger 2.0 definition to OpenAPI 3.0 and compare those? You could use api-spec-converter for the conversion in this direction.

@MikeRalphson thanks. I'll watch openapi-diff.

Closing this for now since it's fixed in the README. Converting 3 => 2 (lossily ofc) is something we'll consider down the line though.


Check for bower.json in app directories

34ff6dd introduced a bug where the PathSet would look inside the
EmberCli output directory for the presence of a bower.json file,
instead of inside the EmberCli application's directory (i.e. the input
directory).
This commit resolves that issue, and modifies the PathSet to properly
resolve the path to bower.json.

@f1sherman 0.10.0 has been released and contains those changes.

@seanpdoyle awesome, thank you very much! 🎉


[BUG] Failed to import image

What did you do
brew install k3d
k3d cluster create k3d-cluster

Some options show failed but the cluster was reported to be created successfully
❯ k3d cluster create k3d-cluster
INFO[0000] Created network 'k3d-k3d-cluster'
INFO[0000] Created volume 'k3d-k3d-cluster-images'
INFO[0001] Creating node 'k3d-k3d-cluster-server-0'
INFO[0003] Pulling image 'docker.io/rancher/k3s:latest'
INFO[0017] Creating LoadBalancer 'k3d-k3d-cluster-serverlb'
INFO[0019] Pulling image 'docker.io/rancher/k3d-proxy:v3.4.0'
INFO[0023] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access
ERRO[0023] Failed to start exec process in node 'k3d-k3d-cluster-server-0'
WARN[0023] Failed to get HostIP: error during connect: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/exec/f399257a752ecf04d7e2e369f049bb8a9d8cbc4eaa632da320738ac3530a9312/start": net/http: HTTP/1.x transport connection broken: unsupported transfer encoding: "identity"
INFO[0023] Cluster 'k3d-cluster' created successfully!
INFO[0023] You can now use it like this:
kubectl cluster-info

How was the cluster created?

k3d cluster create k3d-cluster

What did you do afterwards?

k3d commands?

k3d image import --cluster k3d-cluster gcr.io/<someimage>

docker commands?
OS operations (e.g. shutdown/reboot)?

What did you expect to happen
Images loaded in <some seconds>

Screenshots or terminal output
k3d image import --cluster k3d-cluster gcr.io/<someimage>
INFO[0000] Importing image(s) into cluster 'k3d-cluster'
INFO[0000] Saving 1 image(s) from runtime...
ERRO[0000] Failed to start exec process in node 'k3d-k3d-cluster-tools'
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x481d6a3]

goroutine 1 [running]:
github.com/rancher/k3d/v3/pkg/runtimes/docker.Docker.ExecInNode(0x4d7a480, 0xc0000b2000, 0xc000184500, 0xc000130a80, 0x5, 0x8, 0xc000130a80, 0x1)
	github.com/rancher/k3d/v3/pkg/runtimes/docker/node.go:323 +0xc3
github.com/rancher/k3d/v3/pkg/tools.ImageImportIntoClusterMulti(0x4d7a480, 0xc0000b2000, 0x4d8cbe0, 0x538fe28, 0xc00036cdb0, 0x1, 0x3, 0xc00061fba0, 0x0, 0x1, ...)
	github.com/rancher/k3d/v3/pkg/tools/tools.go:140 +0x180d
github.com/rancher/k3d/v3/cmd/image.NewCmdImageImport.func1(0xc0005b6580, 0xc00036cdb0, 0x1, 0x3)
	github.com/rancher/k3d/v3/cmd/image/imageImport.go:55 +0x385
github.com/spf13/cobra.(*Command).execute(0xc0005b6580, 0xc00036cd80, 0x3, 0x3, 0xc0005b6580, 0xc00036cd80)
	github.com/spf13/cobra@v1.1.0/command.go:854 +0x2c2
github.com/spf13/cobra.(*Command).ExecuteC(0x5350620, 0xc0000c4130, 0x5, 0x5)
	github.com/spf13/cobra@v1.1.0/command.go:958 +0x375
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.1.0/command.go:895
github.com/rancher/k3d/v3/cmd.Execute()
	github.com/rancher/k3d/v3/cmd/root.go:91 +0x5a
main.main()
	github.com/rancher/k3d/v3/main.go:27 +0x25

If applicable, add screenshots or terminal output (code block) to help explain your problem.
Which OS & Architecture

Linux, Windows, MacOS / amd64, x86, ...?

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro16,1
  Processor Name:	6-Core Intel Core i7
  Processor Speed:	2.6 GHz
  Number of Processors:	1
  Total Number of Cores:	6
  L2 Cache (per Core):	256 KB
  L3 Cache:	12 MB
  Hyper-Threading Technology:	Enabled
  Memory:	16 GB

Which version of k3d
k3d version v3.4.0
k3s version latest (default)

Which version of docker
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:21:11 2020
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:29:16 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Hi @gsquared94, thanks for opening this issue!
There are two things to notice here:

your issue is probably caused by a misunderstanding:

you named your cluster k3d-cluster, which will result in a cluster with a double prefix (as k3d enforces the k3d prefix): k3d-k3d-cluster
then you use the incomplete (single prefix) name for the image import and thus, k3d cannot find the cluster
using k3d image import --cluster k3d-k3d-cluster gcr.io/<someimage> or using a different cluster name from the start would "fix" this for you already

the nil pointer exception you see is definitely bad error handling on our side and has to be fixed (probably in v4.0.0)

Hi @gsquared94, thanks for opening this issue!
There are two things to notice here:

your issue is probably caused by a misunderstanding:

you named your cluster k3d-cluster, which will result in a cluster with a double prefix (as k3d enforces the k3d prefix): k3d-k3d-cluster
then you use the incomplete (single prefix) name for the image import and thus, k3d cannot find the cluster
using k3d image import --cluster k3d-k3d-cluster gcr.io/<someimage> or using a different cluster name from the start would "fix" this for you already

the nil pointer exception you see is definitely bad error handling on our side and has to be fixed (probably in v4.0.0)

Hi @gsquared94, thanks for opening this issue!
Sorry for the notification you probably got because of my first confused comment :grimacing:
There are two things to mention here:

bad error handling on our side (nil pointer exception): should be fixed in b36c49a (then you should also get better debugging output)
your error: can you verify (e.g. with watch docker ps -a, that the node containers and the tools container are running at the time of the error?

Hi @gsquared94, thanks for opening this issue!
Sorry for the notification you probably got because of my first confused comment :grimacing:
There are two things to mention here:

bad error handling on our side (nil pointer exception): should be fixed in b36c49a (then you should also get better debugging output)
your error: can you verify (e.g. with watch docker ps -a, that the node containers and the tools container are running at the time of the error?

Before following up on your suggestion, I updated my Docker Desktop to the latest version and that seemed to have fixed this for me. Thanks for your help.

Before following up on your suggestion, I updated my Docker Desktop to the latest version and that seemed to have fixed this for me. Thanks for your help.


minor changes

Codecov Report

Merging #210 (7ef9576) into develop (01c3eda) will increase coverage by 0.52%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #210      +/-   ##
===========================================
+ Coverage    97.56%   98.09%   +0.52%
===========================================
  Files           66       72       +6
  Lines         2668     2933     +265
===========================================
+ Hits          2603     2877     +274
+ Misses          65       56       -9

Impacted Files
Coverage Δ

test/test_auto.py
100.00% <0.00%> (ø)

test/test_blocks.py
100.00% <0.00%> (ø)

glasses/nn/blocks/__init__.py
100.00% <0.00%> (ø)

glasses/utils/ModuleTransfer.py
100.00% <0.00%> (ø)

glasses/models/classification/__init__.py
100.00% <0.00%> (ø)

glasses/utils/PretrainedWeightsProvider.py
96.29% <0.00%> (ø)

glasses/nn/regularization.py
100.00% <0.00%> (ø)

test/test_ResNeSt.py
100.00% <0.00%> (ø)

test/test_DeiT.py
100.00% <0.00%> (ø)

glasses/models/classification/resnest/__init__.py
96.36% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


add nightly docker setup for CI

motivation: test with nightly toolchain
changes: add docker compose setup for ubuntu 20.04 and nightly toolchain
requires #360

will pass after we merge the Docker fixes in #360


V-71999 - Verify the OS security patches and updates are installed and up to date.

This control needs to be implemented to check package versions against a list of available package security updates from Red Hat at https://rhn.redhat.com/errata.

See: https://github.com/dev-sec/linux-patch-baseline
On Jul 26, 2017 4:23 PM, "Jennifer Burns"<EMAIL_ADDRESS>wrote:

This control needs to be implemented to check package versions against a
list of available package security updates from Red Hat at
https://rhn.redhat.com/errata.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jburns12/inspec_profiles/issues/6, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABauaBmZhg1YwzgyjkV9kQj7dU87_KNzks5sR6A8gaJpZM4OkcKu
.

Implemented control and added linux_updates resource as found in above link. commit - 6d0a1fc4f569f28d2b08602c80e2644b3eb9e74f


update ts-jest to above 26.2.0 to address security vulnerabilities of…

This pull request updates ts-jest to above 26.2.0 to address security vulnerabilities of yargs-parser < 18.1.2, a sub-dependency of ts-jest

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[x] Underlying tools (?dependency?)
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[ ] No
[x] maybe: this project isn't containerized and I don't want to install yarn and things on my host

Other information:
I'm hoping your CI will figure out if this is a breaking change or not.
+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>
Low             Prototype Pollution
Package         yargs-parser
Patched in      >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2
Dependency of   @vue/cli-plugin-unit-jest [dev]
Path            @vue/cli-plugin-unit-jest > ts-jest > yargs-parser
More info       https://npmjs.com/advisories/1500

It is a breaking change, though we don't have a test for this.


Drop support for python 3.9

Type
Enhancement

Description
This PR updates the required Python version for the project. The change is made in the pyproject.toml file:

The requires-python version has been updated from ">=3.9" to ">=3.10". This is due to the use of structural pattern matching in bitbucket_server_provider.py, which was introduced in Python 3.10.

PR changes walkthrough
Relevant files                                                                                Configuration changes1 files

pyproject.toml

        pyproject.toml
The requires-python version has been updated from ">=3.9" to ">=3.10".

 +1/-1

User description
The bitbucket_server_provider.py uses structural pattern matching that was introduced in python 3.10, and so trying to run any command with python 3.9 will fail (because we import all the providers right at the top of pr_agent.git_providers)

👍


Treemap chart selection filter error

Describe the bug
Error when using selection filter by clicking on Tree map chart.
To Reproduce
Steps to reproduce the behavior:

Create TreeMap Chart and Bar Chart
Click on TreeMap part and apply Selection Filter
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I think It's bug relate to Echart library, So To solve this bug needs more time.


review request yml added

/autoupdate

/pfa

/pfa

/pfa

/pfa

/pfa

/pfa

/pfa

/pfa

/pfa

@Priyansh61 asked for your review @thejaysharma

/pfa

/pfa

/pfa

/ping-for-attention

/pfa

/pfa

/pfa

/pfa

@thejaysharma Please take a look at this PR. Thanks! :wave:

@thejaysharma /review

@thejaysharma Please take a look at this PR. Thanks! :wave:

@thejaysharma /review

@thejaysharma Please take a look at this PR. Thanks! :wave:

@thejaysharma /review

@thejaysharma Please take a look at this PR. Thanks! :wave:

@thejaysharma Please take a look at this PR. Thanks! :wave:

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

@thejaysharma /review

/review

/review

/review

/review

@thejaysharma /review

@thejaysharma /review


Inconsistent quit behaviour

q doesn't always quit.

changed quit to self.exit per textual docs.
fileio operation on exit. something is still trying to write? async overlaps? stdout hanging around?


Create some test cases that export compiled methods to be referenced in wikis.

The Booklet repository should not contains such exported images because, to generate them, we need to use a trait that is provided by a dependency baseline (the Essentials one).


Test GridTools C++ master

before merging I want to tag a new release in GridTools C++

bors try

bors try-

bors try

bors try

bors try

@jdahm Are you ready everywhere to use c++17, especially to drop support for CUDA < 11?

bors try

bors try

bors try


Fixes the dynamic/static library CMake logic

Reference Issue
The DLL PR #1861 introduced a regression when attempting to statically link PostgreSQL and SWIG on Linux.
What does this implement/fix? Explain your changes.
Fixes a bug inadvertently introduced in the static/dynamic library CMake logic
To help consistency with the past I decided to revert to the traditional behaviour (DLLs are not built on MSVC unless the RDK_INSTALL_DLLS_MSVC switch is set to ON). This will preserve previosuly existing scripts/workflows. On Windows by default static libraries will be built, and they will not have the _static suffix, just as it used to happen in the past before the DLL PR #1861.
Only if the RDK_INSTALL_DLLS_MSVC switch is explicitly set to ON (default is OFF), DLLs will be built.
Please note that currently on WIndows building DLLs and statically linking SWIG and PostgreSQL cartridge at the same time does not work. This however works fine doing two separate builds, one static and one dynamic.
I'll work on this as soon as I will have abit of time. If it becomes too hairy we could just force RDK_SWIG_STATIC=OFF and RDK_PGSQL_STATIC=OFF on Windows when
RDK_INSTALL_DLLS_MSVC=ON.
Any other comments?

Thanks Paolo. That worked for me on linux with both the SWIG wrappers and the cartridge.


add generate_enum_match assist

This adds a generate_enum_match assist, which generates is_ variants for enums (e.g. Option::{is_none,is_some} in std). This is my first attempt at contributing to Rust-Analyzer, so I'm not sure if I've gotten everything right. Thanks!
Example
Input
pub(crate) enum Variant {
    Undefined,
    Minor, // cursor here
    Major,
}

Output
pub(crate) enum Variant {
    Undefined,
    Minor,
    Major,
}

impl Variant {
    pub(crate) fn is_minor(&self) -> bool {
        matches!(self, Self::Minor)
    }
}

Future Directions
I made this as a stepping stone for some of the more involved refactors (e.g. #5944). I'm not sure yet how to create, use, and test window.showQuickPick-based asssists in RA. But once that's possible, it'd probably be nice to be able to generate match methods in bulk through the quickpick UI rather than one-by-one:
[x] Select enum members to generate methods for. (3 selected) [ OK ]
---------------------------------------------------------------------------
[x] Undefined
[x] Minor
[x] Major

Yay, CI has passed. I think this is ready for a review now!

see https://github.com/microsoft/language-server-protocol/issues/1164 for "quick pick" related discussion.

If you feel sufiiciently motivated, I'd love to see the impl of this idea:

For each refactor type, Dart documents a specific JSON format with data to be shown to the user as a feedback, and JSON format for the user's reply. It says nothing how the data is displayed in the UI -- client implements specific GUI for each refactor. This obviously means manual work for each (client, refactor) pair, but allows for the best possible experience.
An interesting facet here is that the communication protocol for a refactor is stateless. This works a bit like HTTP GET/POST for a form. Rather than the server recording that user X now views form Y after X does GET Y, the corresponding POST Y contains all the info required to restore the context.

See https://github.com/rust-analyzer/rust-analyzer/commit/2075e77ee5784e72396c64c9ca059763508219ff for how to implement extensions to the protocl.

Okay, update the PR with all proposed changes. This includes moving find_struct_impl to the assist utils!

If you feel sufiiciently motivated, I'd love to see the impl of this idea:

This will depend on my availability, but I may give it a shot. Thanks so much for sharing these references so far. It's giving me a better idea of what would be required to do this, and I may end up giving it a shot!

bors r+


Atom and/or package line-ending-select use inconsistent terminology - term 'status-bar'

The Atom 1.3.3 package 'line-ending-select' refers to the 'status-bar', but no menu command of Atom contains the phrase 'status-bar' and nowhere do I see something like a status bar. Moreover, Atom Help (from menu bar) does not know the term 'status-bar'. Searching on line for help by following help link 'For help, please visit: • The 'Atom docs' for Guides and the API reference' brings me to https://atom.io/docs. There I a search for 'status-bar' finds finally something, 4 web pages. Link '1.3 Getting Started : Atom Basics' looks best, however, searching on that page (https://atom.io/docs/v1.4.0/getting-started-atom-basics) for 'status-bar' fails: 'Not found'. Something is wrong here.

It is referring to the status-bar package. It is true that we interchangeably use the package name form "status-bar", the title-cased form "Status Bar" and sometimes even "status bar". Other than these various forms, I think that we pretty consistently use the words "status bar" to refer to the UI generated by the status-bar package.
Other than that, this appears to be a documentation request? Would you mind clarifying what you're looking for?

Sure but I do not know what is correct, since this was my first attempt at evaluating Atom and learning to know it a bit. However, I do for sure know this: I would like to have consistency throughout. What I hate are things as MicroSoft Word offers, e.g. a specialized term close to jargon used in a menu command, but when you search for it, e.g. in the help mechanism of Word, you never find it. Of you find some help text, as was the case now with Atom package 'line-ending-select' using term 'status-bar', but you don't find that explained anywhere, since the introductory text uses 'status bar' (as I now learned later).
But I do not know what is the more common term, 'status bar' or 'status-bar'. Having learned more about Atom I now know what it is and I now know that both terms are used in various places. Whichever it is, that one should be used throughout help texts, menu commands, guides, tutorials etc. so that Atom uses always one single term consistently. Then searching for it is easy and one finds the wanted explanations quickly. At least I would have wasted considerably less time in trying to understand what that status bar ought to be and where it can be found on my Atom screen.
Sorry for not being able to tell you exactly what the best solution is. If status-bar is correct, then the getting started text needs to be fixed. Otherwise, if status bar is correct, the help of the package line-ending-select needs to be updated.

I've opened a tracking issue for this since it is far more than just the line-ending-selector package that is going to need changing. Thanks for bringing this up!

Thank you.


Regulate plugin as BITRATE LIMITER

Hi @lelegard ,
Let me to explain this user-case:

When doing a MUXING (using TSDuck merge or an external tool) it's good to have some kind of lifeline for the input streams. For example, imagine that one of your IP multicast inputs begins to receive a lot of erroneous data because a network loop. Or imagine one HTTP input that floods the stream with an excesive burst of data.

In such scenarios a bandwith limiter can be a life preserver. The idea is that when one entry is in trouble, other entries are not disturbed. This can be done limiting the maximum bitrate of the input (without taking any further action). For example with something like -P regulate --max-bandwith 15000000. In this case, with a mux of 38Mbps and 4 VBR inputs the glitches when one input goes in troubles will be minimized.
What you think?

Two scenarios need to be specified:

What should we do when the bitrate is lower or significantly lower than the max ?
What should we do when the bitrate is higher than the max ?

In the first case, what is the current behaviour of -P regulate --bitrate 1500000 ? Is it ok for you ? I haven't made such tests myself but tsp cannot accelerate the stream. So, lower bitrates should remain unchanged.
In the second case, what should we do with the extra packets? Currently, regulate passes all packets but slow them down to the target bitrate. So, they accumulate and the complete chain is temporarily blocked when the global buffer is full. This is the intended behaviour for input files for instance. If the input is a real-time UDP/IP stream, then input packets are dropped and, as a result, regulate --bitrate already acts as a bandwidth limiter.
We may object that, while effectively limiting the bandwidth, there is probably a latency effect because of the buffer and the resulting stream can be somewhat chaotic.
One possibility could be to add a --drop option in regulate so that the plugin would drop packets in excess instead of making them wait.
As a synthesis, could you specify precisely what should be done, in details ?

Hi @lelegard ,

As a synthesis, could you specify precisely what should be done, in details ?

I'll try. :smile:
The target user-case is INPUTS before a MUXER. I feel this scenario explains the problem: If some input goes bad, then it's best to not disturb other inputs. The idea is leave the muxer (aka merge plugin or an external tool) to complete the task without generating errors with the programs that are ok. So, a first mesure is to apply a hard limit to the bitrate of each input to a maximum value. So, in case of a burst (temporal or permanent) in one input the muxer will never be saturated or collapsed for this reason.
I know that this countermeasure never be perfect. For example, using VBR inputs, is quite easy to overpass the limit. However, using CBR inputs, or inputs with small bitrate variations, this measure can resolve a lot of cases.

What should we do when the bitrate is higher than the max ?

It needs to drop packets. No more, no less.
However, it will be interesting if the drop is done in a smart way. For example, if the bitrate rebases the maximum, it's best to drop video packets in one chunk than drop N packets every M... or drop packets from any pid. This behaviour will generate errors in the video, but it maintains the integrity of the rest. Even if PCR packets are never discarded, and also are recomputed, then the stream will be "limited" but "processable".
This is only an example, but (I hope) it illustrates the objective. :smiley:
At time, the "input buffer" can be used to achieve partially this behaviour. So, if the bitrate is very high then it's cutted. However, this buffer isn't related to the bitrate. Futhermore, it only drops a large number of consecutive packets, that's the worst action.
I hope you can understand the problem and provide a simple and smart solution. In my opinion, this functionality can be incorporated in the regulate plugin, but if you prefer you can add a new limiter one.
What you think? More clear now?

Several remarks :
A plugin cannot have a global view on the input buffer or a group of packets in general. A plugin processes all packets one by one, one at a time. This is a limitation by design of tsp. It can be problematic sometimes. But it also makes TSDuck much simpler to maintainn and enhance.
We can start from the hypothesis that a plugin drops packets when the bitrate becomes higher that some limit.
This plugin would:

Constantly re-evaluate bitrate, based on PCR's, with a fast instantaneous rate, typically all pairs of consecutive PCR's.
Analyze all PSI to keep a permanent map of all PID's (which is video, audio, etc.)
When regulate would typically wait, this plugin drops packets instead.
But when a packet should be dropped, we consider the usage of this packet. Packets with video but without PCR are the first candidates for elimination.
When a packet should be dropped but is not a good candidate (PCR, PSI, etc), it is not dropped but this increases some kind of "packet credit". This credit must be paid back later. It should also not exceed some limit, after which more precious packets will be dropped anyway.

In the case of a merge, this plugin should be used in the merged tsp command, before actual merging. If you use the new plugin after merge, there is no way to know from which branch a packet comes.
Will this answer your problem? Do you see other constraint or specification?

Moreover, when selecting packets for elimination, what should be the strategy to select among good candidates? Should we eliminate video packets without PCR if they belong to distinct PID's? Or give the priority to one video PID? And which one? Dropping one video packet usually extends the damages beyond this packet. So, it could be more interesting to degrade one single video PID's instead of several ones. But, this also increase the "packet credit" and possible side effects.

Hi @lelegard ,
You're very good picking up the specs! :open_mouth:
As a summarize:

Plugin name: limiter. A new plugin is required to not disturb the complexity.
This plugin "removes" and not "erases" packets. That's any removed packet is discarded and not replaced by nulls. However, for more flexibility, an optional parameter like --erase can modify this default behaviour.
It can be applied to any stream, MPTS or SPTS.
Parameters: -P limiter --vpid XXX --bitrate NNN --vpid YYY --bitrate MMM --bitrate-max LLL.
Where, --vpid & --bitrate pair indicates at which video pid apply the limit. Multiple pairs are possible for MPTS streams. Only pids indicated can be smart limited.
When a video pid is limited, the strategy is simple: remove a consecutive number of packets to achieve the target bitrate for this pid. Packets with PCR aren't discarded. If it's possible, discard packets are between two PUSI marks.
The --bitrate-max indicates the total maximum bitrate of the entire stream. So this task is done after complete the video pid limiting. When it's required to drop packets at the end, any packet can be droped. So here a big chunk of consecutive packets are directly removed.
For a more flexibility, in fact --vpid can be applied to any type of stream. However, when it's not a video stream then no smart strategy is used. This can be useful for data streams.

You agree?

So, you would like to limit the bitrate per PID, not only the TS bitrate ? And with a different limit per PID ?
It seems a bit complicated. My understanding was that this plugin would be used to protect from input or merging plugins becoming crazy. So, in that case, the packet removal does not need to be so surgical.

Dear @lelegard ,
Sorry for the mistake! Your work is impresive, but sometimes I forget that this is an open project. I like to collaborate, and not disturb. And you're right, I'm mixing in my last post incorrect specifications.
So, let me summarize (again):

Plugin name: limiter.
Objective: Limit the total bitrate of an stream.
Target: Mainly for SPTS, as for MPTS only burden limit can be applied.
Parameters: -P limiter --pid XXX --bitrate NNN.
Param --bitrate: Required. Is the maximum bitrate permited for the stream. Over this limit packets are discarded in secuential chunks.
Param --pid: Optional. If it's used then a first stage removal is done only over this pid. If this substream is video, then a smart strategy is used. This strategy consist in try to remove chunks of consecutive packets between two PUSI marks. And all PCR packets are preserved.
Discard method: Pure packet removing, not erase them, so the output bitrate is reduced.

Now I feel the specifications are more simple and clear. :smile:
The idea is to use this plugin only with SPTS's before a mux/merge action.
You agree now?

Hi @lars18th
I just added plugin limit. Please review it and give us your feedback.

Hi @lelegard ,
Interesting implementation. I'm reading the documentation and it seems nice.
Thank you!
However, one suggestion:

Why not add too a --threshold4 for any audio PID and leave --threshold3 only for video? I prefer to discard only video packets and not touch audio packets! With the current implementation, audio doesn't have any preference over video.

In brief: -3 only for video, and new -4 only for audio.

Hi @lelegard ,
Another simple enhancement to the limit plugin:

Can you add support for the value "-1" in the thresholds?

The idea is to "disable" the threshold (so, "-1" equals to disabled). Why this? Well, the first threshold is for NULL packets. But, in case you like to remove only from specific pids then you can use a two stages like this:
tsp ... \
 -P limit -b 10000 --threshold1 -1 -p 2222 --threshold2 1 --threshold3 -1 \
 -P limit -b 10000 --threshold1 10 --threshold3 1000 \
...

In this case, in the first stage you remove only packets from pid 2222. And in the second stage you can remove the rest. Just to comment: another parameter like --no-strict can be required in the first stage to not drop more packets at last, so the bitrate can be exceeded.
The idea is leave to the user the option to stablish the preference of the thresholds.
You got it?
PD: Perhaps "0" is preferable, as "1" is the real minimum, and "-1" can be confused with the -1|--threshold1.

Hi @lelegard ,
I'm working in implementing some enhancements (separate thresholds for audio and video in the pid list, and the disable mode). However, I feel I found one BUG in your code:
See https://github.com/tsduck/tsduck/blob/master/src/tsplugins/tsplugin_limit.cpp#L210
I feel the correct code should be:
  _thresholdAV = _pids1.any() ? _threshold2 : _threshold1;

Because in this check https://github.com/tsduck/tsduck/blob/master/src/tsplugins/tsplugin_limit.cpp#L425
the threshold to check is _threshold2 when -pid is used and _threshold1 when not.
I'm right?

Hi @lelegard ,
I created this PR #190 to implement the improvements I requested.
If you merge it, then we will be able to close this issue.
Just one comment: with my enhancement only audio/video pids from the pid list are discarded. I don't see any sense to discard "other" pids from a service.
Regards.

Just one comment: with my enhancement only audio/video pids from the pid list are discarded. I don't see any sense to discard "other" pids from a service.

On the contrary, large data PID's could be good candidates to sacrifice in case of overflow. For instance, a large EPG PID can be considered as less important than other audio/video PID. Your choice.
No need to add a 5th threshold. I will integrate your PR and will modify it so that below threshold 3 all selected --pid are dropped (not only audio). So, specified video is dropped first, then audio or data.

I feel the correct code should be:
_thresholdAV = _pids1.any() ? _threshold2 : _threshold1;

You are right 😉

Hi,
I close this issue as the PR is merged: https://github.com/tsduck/tsduck/pull/190#event-2054838053
Thank you!


[Bug] FirebaseRemoteConfigApi.projects.remoteConfig.downloadDefaults incorrectly handles JSON responses

In the code snippet below, response will always be empty. Further investigation reveals that it's because of https://github.com/google/googleapis.dart/blob/master/generated/googleapis/lib/shared.dart#L9636 expecting data to be mapped to a data key.
final client = FirebaseRemoteConfigApi(<my client>);
final response = await client.projects.remoteConfig.downloadDefaults(_project, format: 'json'); // response will always be empty

I've had to create overrides for APIs that are broken like this - see https://github.com/google/googleapis.dart/tree/master/overrides
I need to understand what the data coming over the wire looks like so I can make a patch here.

It's just a simple JSON object with no nesting. Something like
{
  "a": "limited_time_offering",
  "b": "default_offering",
  "c": "true",
  "d": "1"
}

@Pante – would you send a permalink to the line? I think the source changed!

No problem! The affected method is downloadDefaults(...) which is caused by HttpBody.fromJson(...).

A version w/ this fix has been published: https://pub.dev/packages/googleapis/versions/10.1.0


Laravel 5.4 support ?

No.... I tried yesterday.... 5.3.9 maximun.

Hi! Yes, I need to add it in. Because Laravel does not follow semver, I've tied this package to specific versions so that if a new version comes out I can check it's working with the new version first.
I might be able to look at this today.

@lindyhopchris I'm working on a pull request right this moment, so if you hang on for an hour or two then we can take a look at it together when reviewing. :)

@jstoone  Ah, sorry, just pushed some changes to develop - hadn't seen your message.
Here's what I had - happy to take a PR for anything else I might have missed as I've only tested this in the demo app:
https://github.com/cloudcreativity/laravel-json-api/commit/23e4fbcb2016b3dd70f0074cf97a00e44852b9c9
For info, you have to use the BrowserKit test case for the testing to still work.

It'd be nice if the changes also worked in <5.4 which I think these might
I'm starting to get a bit fed-up with Laravel's approach to versions - the breaking changes mean it's really difficult to support older versions. I'm thinking after 5.4 I might have to switch this package to having a new version each time there's a new Laravel version, which would mean that to use the latest version of this package you'd always have to be on the latest version of Laravel. Any thoughts?
What does worry me is that the next Laravel is dropping support for PHP 5.6, which is a right pain as I've got applications that are going to be on PHP 5.6 probably until 5.6 is end of life.

Yea, it's unfortunate that it doesn't follow SemVer, but other packages that are coupled with laravel increment their major version for each new Laravel major version. In this way once the package looses backwards compatibility  you can add a note to the readme.
This adds cleaner code to each release branch, but it also might add some redundancy when it comes to maintaining and applying feature to older versions. But it has to be a conscious choice. Whether we should maintain older versions with new features.

all good points!
let me know when you've had a chance to try the develop branch in L5.4, because if it's working then I can tag it and update the readme

@lindyhopchris I've just started upgrading our API, I'll keep you posted!

@jstoone i think this is good to merge, unless you've hit any showstoppers?

@lindyhopchris yea, sorry for my slow feedback, figured out we had a lot of dependencies that needed to be upgraded/replaced which included our entire oauth system, which I'm porting to Passport. But I've had no problems with laravel-json-api, that was pretty straight forward. :)
So yea, I'd agree it's ready for a merge.

We are eagerly waiting for this state of art package for Laravel 5.4.

I have finished making a fork with the few functionality that I use adapting it for my cases, there was too much changes to upgrade without continuity garanty... Thank you very much for the package but I think it has not enough support....

So, will this package support 5.4 or not ??

@mspiderv yes, it will be updated. the work is done on the develop branch, I need to merge and tag it. I'm away this weekend so will do that on Monday morning.
Apologies for the delay, it's entirely down to other work priorities rather than not wanting to support this package.
@asantiago the package is supported and we have plans for improving it. Like any company though with commercial work deadlines, the time we can spend on it is obviously dependent on those deadlines.
It's great that people are using this package. We welcome contributions and will happily accept PRs. Supporting an open source project via contributions is the best way to support its growth and help it mature.

Version 0.6 released, with a very minor upgrade required (see the UPGRADE.md file).
To update:
$ composer require cloudcreativity/laravel-json-api:^0.6 --update-with-dependencies


[europa] Add new extractor for the European Commission video service.

The test URL for download is
http://ec.europa.eu/avservices/video/player.cfm?ref=I107758
Fixes #6528 and #6538

What's the point of this? It's identical to #6538.

This code is actually correct then, I just tested it wrong. And tests for this particular extractor are passing.

What's the point of this? It's identical to #6538.

Yes, except it is rebased to the current master.

Duplicate of #6538.


Rename gcloud-python-expenses-demo -> google-cloud-python-expenses-demo

This repository is only referenced by google-cloud-python itself. Now that we have extensive samples for google-cloud-python, should be just move this over to GoogleArchive?

What is GoogleArchive?

Our elephant graveyard: https://github.com/GoogleArchive

Ha. Fine with me, you just check with @tseaver though


Make sign-off regex more leniant

This changes the sign off checker to stop assuming everyone's name is matched by [\w ]+. (cough https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ cough).
Instead, we're just going to check for the absence of whitespace and assume that reviewers will do a visual test to make sure the name looks okay.
Also dropping the requirement for < and > to wrap the email, as not everyone does it and I don't think it's a hard requirement.

(Released in v2.0.3, and I moved the v2 tag forward accordingly.)


chore: bdd-gh-1585587559 to 0.0.1

chore: Promote bdd-gh-1585587559 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Unexpected token import

win10 64bit
always
刚init完之后  npm  run dev
打开localhost:8080  是可以正常访问的
但是 重启电脑后 npm  run dev
打开localhost:8080  就是一片空白  控制台报错
main.js?3479:1 Uncaught SyntaxError: Unexpected token import

如果在init的时候  不选eslint就没事。。。。

确认了  原来是是vscode的terminal的问题  用win自带的命令行就没问题了

I got the same issue, +1

main.js?3479:2 Uncaught SyntaxError: Unexpected token import
(anonymous function) @ app.js:702__webpack_require__ @ app.js:556fn @ app.js:87(anonymous function) @ app.js:587__webpack_require__ @ app.js:556(anonymous function) @ app.js:579(anonymous function) @ app.js:582

果然是vscode的问题， 就连在vscode中右键打开命令提示符来执行都不行，坑了很久。

I got the same issue +1, and I used vscode too.
my solution is add the code into webpack.base.conf.js as below:
      {
        test: /\.js$/,
        loader: 'babel-loader',
        exclude: /node_modules/,
        query: {
          presets: ['es2015']
        }
      },

This looks to be a vscode-specific problem, so it's unfortunately their bug rather than anything wrong with our configuration. @summitxf Thanks for documenting a fix for other users!


relativeCaretYPosition returns 0 on new line

If the cursor is in the middle or at the start of a word, relativeCaretYPosition returns 0 when Return pressed.
As a result, the view does not follow the cursor.
It happens because runJS("RE.getRelativeCaretYPosition();") in this case returns NaN.
To reproduce:
Run RichEditorViewSample,
select Swift or Objective-C,
type any character,
move the cursor to the start of the line,
press "return" till the cursor disappears below the bottom edge of the view. The view will not scroll.
Expected behaviour:
The view scrolls to show the cursor.

Tested on iOS 11.

I believe I fixed the issue. Please check the linked commit.
The problem was happening when editing a text node.

Its not solved yet as its easy reproducible


Adjust "Raptoreum" on QT loading screen

"Raptoreum" needs to either be removed or adjusted up and right to get rid of the overlap currently seen.

merged to develop


Add ICML 2025 and UAI 2025

like a bunch of other people I added an update before checking whether someone else had already done so :sweat_smile:
so this one is overlapping with #712, #721, and #708.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/585 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit 6c940c4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-BackendEngineExceptionError] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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


Fix windows rendering

Fixes: #651

Fixes: #651

Something odd is going on with DirectX12.
Found a temporary work around so will use that for the time being


Update stream-analytics-window-functions.md

grammar edit to improve readability.

@luoren-mck : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks @luoren-mck.

#sign-off


[STYLE CHANGE] add new logo in blog section

Description:
I wanna change moksh new logo in POWER OF KNOWLEDGE BLOGS section navigation bar.
Reason for Change:
[Explain the reasons behind the requested style change, such as usability, branding, or user experience.]
The Moksh logo is changed now that's an old one.
Screenshots or Design Mockups (optional):
[If available, include relevant screenshots or design mockups illustrating the requested style changes.]

Additional Information (optional):
@akshitagupta15june please assign this issue to me. I want to work on this issue under GSSoC'23.

Priority Level (optional):

[ ] Low
[ ] Medium
[ ] High

Timeline (optional):
[Specify any preferred or required timeline for implementing the style change.]
Possible Implementation Approach (optional):
[If you have any suggestions or ideas on how the style change could be implemented, feel free to provide them here.]

changes related to the blog section will be merged soon, pl do a new fetch in some time.


add image scans for storage service in CSM for Authorization

Description
add image scans for storage service in CSM for Authorization.
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

#https://github.com/dell/csm/issues/243

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[x] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[x] I have maintained at least 90% code coverage
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] Backward compatibility is not broken

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

[ ] Test A
[ ] Test B

run e2e test

Why are we making these changes now? Thanks!

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

E2E pass

rune2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test


WMSCapabilities() does not parse SRS tags inside capabilities file (mapproxy).

Problematic server is https://mapproxy.vsgis.ch/proxy/service?REQUEST=GetCapabilities
var parser = new ol.format.WMSCapabilities();

fetch('https://mapproxy.vsgis.ch/proxy/service?REQUEST=GetCapabilities')
  .then(function (response) {
    return response.text();
  })

WMSCapabilities() won't parse SRS tags, instead it returns "crs": null for every layer.
Is it a problem of "mapproxy" that uses SRS tags instead of CRS?
Thanks for any advice.
J.

Looks like our WMSCapabilities format only supports WMS version 1.3.0, but the service you are requisting only provides version 1.1.1.

Thanks for the info

So will you support 1.1.1？

So will you support 1.1.1？


fix: fallback main navigation [CU-8695xubyr]

Ticket
https://app.clickup.com/t/8695xubyr
Summary

fallback for at least one navigation available
zod typing issues

Test Plan

delete all navigations.
start strapi
after bootstrap navigation is present

Task linked: CU-8695xubyr Navigation not initialized


Language Translator

@Nehaaa3121 Could you please explain what your project is about?

yes sure. it will work as a translator where the user can check the translation of the sentence or word in any language. suppose if someone doesn't know the English  then they checkout the meaning on our translator web app.

@LiQuiD-404

/assign @Nehaaa3121

@Nehaaa3121 I have assigned you the issue now you can work on it.

@Nehaaa3121 I have assigned you the issue now you can work on it.

Thanks and if possible could you please approve my pr #283 .


Environment variables w/ "\n" fail

Firstly, this is a great tool, thank you for creating it!
I'm finding a little niggle trying to set an environment variable that is read from a file (i.e. containing newline characters).
I have something like this (see YAML doc):
# config/eb_deployer.yml
      - namespace: aws:elasticbeanstalk:application:environment
        option_name: MY_VAR
        value: |
          First line
          Second line

If I load this through IRB, all is fine:
require 'yaml'
deployer = YAML.load_file('config/eb_deployer.yml')
deployer['environments']['staging']['option_settings'].select{|opt| opt['option_name'] =='MY_VAR'}.first['value']
=> "First line\nSecond line"

When I come to run a deployment using the gem, I get an error:
(Namespace: 'aws:cloudformation:template:parameter', OptionName: 'EnvironmentVariables'): Not a List of Key/Value pairs.

Is there a way I can include file values in ENV that contain newlines without error?
Much appreciated!

A simplest way to handle it is you change it to be ",", then handle it in your application code.

Hey Xiao, thanks for the response, I ended up opting for a similar solution. It's a shame this can't be supported in the way I describe, but I guess that's more a limitation of the eb tool than anything else.

It's either EB aws-sdk bug, or more likely is EB server side bug.

@fredkelly
eb_deployer will just simply pass through any value you provide to ElasticBeanstalk api. Seems like ElasticBeanstalk service internally treats any multiple line value as a collection value. You may contact with AWS support for this.


After craft 3->4 upgrade, this plugin doesnt allow to show manually added menu items

Describe the bug
When I disable or uninstall CP NAV plugin, my menu items are there.
When I install or enable - they are not in the menu, nor within CP_NAV plugin.

This is how I register them:

Steps to reproduce

create my own module
register admin menu items

Application Info
PHP version	8.0.23
OS version	Linux 5.15.133+
Database driver & version	MySQL 5.7.32
Image driver & version	GD 8.0.23
Craft edition & version	Craft Pro 4.7.1
Yii version	<IP_ADDRESS>
Twig version	v3.4.3
Guzzle version	7.8.1
Plugins
Button Box	4.2.0
Control Panel Nav	4.0.11
Cookies	4.0.0
Field Manager	3.0.8
Google Cloud Storage	2.0.0
Navigation	2.0.25
Neo	4.0.3
oEmbed	3.0.7
Redactor	3.0.4
Redactor Anchors	1.4.1
Redactor Tweaks	3.0.1
Retour	4.1.14
Schedule	0.4.0
SEOmatic	4.0.38
Similar	4.0.0
Twigpack	4.0.0-beta.4
Typed link field	2.1.5
View Count	1.2.2
Vizy	2.1.15
Workflow	2.0.8
Modules
site-module	sitemodule\SiteModule
scout	scout\Scout
codeeditor	nystudio107\codeeditor\CodeEditor
verbb-base	verbb\base\Base
debug	craft\debug\Module
Craft CMS version
4.7.1
Plugin version
4.0.11
Multi-site?
No
Additional context
No response

For now, custom menu items defined in a module won't work, as both CP Nav and your module use the same event (Cp::EVENT_REGISTER_CP_NAV_ITEMS) to register items. As such, there's a collision between what is processed first, which is typically CP Nav, before your module.
The workaround is to create those nav items as manual CP Nav items. This is until we figure out a mechanism to listen to other events that make use of this event.


Fixed #25149 -- Replaced window.admin_utc_offset with a data attribute.

https://code.djangoproject.com/ticket/25149#ticket

buildbot, test on selenium.

@treyhunner, this is read for review at your convenience.

:+1: all of these changes look good to me


Add gelu ativation function to activations.py

Summary
Add gelu and fast_gelu activation functions to activations.py.
Related Issues
This issue
PR Overview
Add gelu and fast_gelu activation functions to activation.py.

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

Please stop opening new PRs when making commits. I'll close and let your newest open.
I don't think this should be merged into Keras.
Not widely used
Not published yet
Please submit your PR at keras-contrib.


Fix benchmark run:

Fix import;
Add workerpool execution time comparaison;
Rename worker scripts.

Improve eslint configuration and fix promise handling.
xx@xx benchmarks (benchmark|✔) % node myBench.js
Fixed pool take 943ms to work on 1000 tasks
Dynamic pool take 936ms to work on 1000 tasks
workerpool take 1261ms to work on 1000 tasks
worker threads pool take 10005ms to work on 1000 tasks

xx@xx poolifier-git (benchmark|✔) % npm run benchmark

><EMAIL_ADDRESS>benchmark /Users/I339261/SAPDevelop/poolifier-git
> npm run build && node benchmarks/bench.js

><EMAIL_ADDRESS>build /Users/I339261/SAPDevelop/poolifier-git
> npm run build:clean && tsc

><EMAIL_ADDRESS>build:clean /Users/I339261/SAPDevelop/poolifier-git
> rimraf lib

PioardiStaticPool x 4,352 ops/sec ±58.91% (8 runs sampled)
PioardiDynamicPool x 6,048 ops/sec ±38.56% (12 runs sampled)
Fastest is PioardiDynamicPool and PioardiStaticPool

Signed-off-by: Jérôme Benoit<EMAIL_ADDRESS>

@jerome-benoit
Maybe we should move the benchmark ci step behind the test step
does it make sense to benchmark it when the tests are failing?

This is what I would like at the end of the game on benchmarking:
https://github.com/fastify/fastify#benchmarks
This is what they do :
https://github.com/fastify/benchmarks/blob/master/.github/workflows/benchmarks.yml
They run benchmarks on a schedule and then publish results into their readme, continuous benchmarking with poolifier that win on everything else 🔥 👊 🏆
But I mean this PR is just to fix the current benchmark so we can just remove the step on the CI if you want and work on all this stuff later on

I see.
I can remove the CI step running benchmark and you can create an issue on the target to reach regarding automated benchmarks run ;)

It's possible to create manual triggerable jobs in GitHub Actions: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
But I never used them before and they are relatively new

@jerome-benoit
Do you want that I approve this now so you can merge it? Or do you want to try a workflow_dispatch in this PR?

@jerome-benoit
Do you want that I approve this now so you can merge it? Or do you want to try a workflow_dispatch in this PR?

Let me return more null at promise resolution when the result is not used first.

I let one of you do the merge.
Thanks.


refactor: resolve relay.NodeID annotations when creating the schema itself

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release changes the way we check for relay.NodeID annotations to be done
later instead of in class initialization. This solves problems with trying to
evaluate type annotations before they are totally defined, and also allows
integrations to inject code for it in the type.

Here's the preview release card for twitter:

Here's the tweet text:
🆕 Release (next) is out! Thanks to Thiago Bellini Ribeiro for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


WIP vectors

Vector representation
Reader, reusing vng.vector.Reader

Likely to be slow due to interface overhead, but removing the overhead would require inlining and duplicating a lot of existing code.

Materializer, implementing zio.Reader

Likely to be slow due to interface overhead, but difficult to vectorize because zng is variable-length

I haven't been able to produce a valid vng file for thorough testing, but ZED_USE_VECTOR=1 go test ./... passes.

This currently reads the entire file as a single vector which is almost certainly too much. Other formats read a row group at a time, but there is no equivalent in vng. We could maybe just fix a maximum number of values to stream per vector batch, but we'll still pay for lz4 decompression to touch even the first row.
I reused much of the existing vng.vector.Reader code. In theory we should be able to make the vector code fast enough that it's the preferred pathway and the direct vng->Value readers can go away.
Everything is hidden behind ZED_USE_VECTOR for now.

Perhaps the existing tests are not sufficient - https://github.com/brimdata/zed/pull/4834/commits/aa16b6c3b67e63e2703ac425cf132d7921fb9e61. I'm going to mark this as a draft and figure out some more thorough tests.

Performance is terrible:
> hyperfine --warmup=1 'duckdb ./wrccdc_mono_10m.db -c "select service, count(*) from wrccdc_mono_10m where _path = \'conn\' and service is not null group by service order by service limit 10"'
Benchmark 1: duckdb ./wrccdc_mono_10m.db -c "select service, count(*) from wrccdc_mono_10m where _path = 'conn' and service is not null group by service order by service limit 10"
  Time (mean ± σ):     106.4 ms ±  11.7 ms    [User: 667.6 ms, System: 124.9 ms]
  Range (min … max):    79.8 ms … 121.2 ms    24 runs

> hyperfine --warmup=1  'zq -f zson \'_path=="conn" service!=null | count() by service | sort service | head 10\' wrccdc_mono_10m.vng'
Benchmark 1: zq -f zson '_path=="conn" service!=null | count() by service | sort service | head 10' wrccdc_mono_10m.vng
  Time (mean ± σ):      6.331 s ±  0.012 s    [User: 6.271 s, System: 0.106 s]
  Range (min … max):    6.314 s …  6.351 s    10 runs

> time ZED_USE_VECTOR=1 zq -f zson '_path=="conn" service!=null | count() by service | sort service | head 10' wrccdc_mono_10m.vng > /dev/null
________________________________________________________
Executed in   55.50 secs    fish           external
   usr time  111.28 secs    1.58 millis  111.27 secs
   sys time    1.63 secs    0.07 millis    1.63 secs

This is as well-tested as I can manage working around known bugs.

I fixed a bug in the vng writer that skipped null columns for primitives.
@nwt is working on the bug with NaNs in dicts.
The fuzzer triggers some bug that appears to be in segment handling.

With workarounds for the above, this branch survives fuzzing and can run simple benchmarks on a filtered and truncated version of the wrccdc dataset.

Performance is terrible:

As expected

I wasn't expecting it to be terrible.


wmii dies due to dead links in $PATH

I assume 6018bff57fed60742417caab1b12227736996fbe introduces a problem that causes wmii to die when there are dead links in the $PATH.  The window manager shouldn't depend on a cleaned up path.
In addition, the error message is misleading and might make the user believe he's missing a dependency ('dependencies' on javaws and pluginappletviewer really got my blood boilin' -.-)
#<Errno::ENOENT: No such file or directory - /usr/bin/javaws>
/home/dtk/.wmii-hg/control/action/launch.yaml:control:action:launch_menu_rehash:3:in `stat'
/home/dtk/.wmii-hg/control/action/launch.yaml:control:action:launch_menu_rehash:3:in `block (5 levels) in control'
/home/dtk/.wmii-hg/control/action/launch.yaml:control:action:launch_menu_rehash:2:in `select'
/home/dtk/.wmii-hg/control/action/launch.yaml:control:action:launch_menu_rehash:2:in `block (4 levels) in control'
/home/dtk/.wmii-hg/control/action/launch.yaml:control:action:launch_menu_rehash:1:in `map'
/home/dtk/.wmii-hg/control/action/launch.yaml:control:action:launch_menu_rehash:1:in `block (3 levels) in control'
/home/dtk/.wmii-hg/lib/wmiirc/handler.rb:20:in `call'
/home/dtk/.wmii-hg/lib/wmiirc/handler.rb:20:in `block in handle'
/home/dtk/.wmii-hg/lib/wmiirc/handler.rb:19:in `each'
/home/dtk/.wmii-hg/lib/wmiirc/handler.rb:19:in `handle'
/home/dtk/.wmii-hg/lib/wmiirc/handler.rb:61:in `action'
/home/dtk/.wmii-hg/control/action/launch.yaml:script:after:1:in `block in script'
/home/dtk/.wmii-hg/lib/wmiirc/config.rb:38:in `instance_eval'
/home/dtk/.wmii-hg/lib/wmiirc/config.rb:38:in `block in script'
/home/dtk/.wmii-hg/lib/wmiirc/config.rb:37:in `each'
/home/dtk/.wmii-hg/lib/wmiirc/config.rb:37:in `script'
/home/dtk/.wmii-hg/lib/wmiirc/config.rb:17:in `apply'
/home/dtk/.wmii-hg/lib/wmiirc/loader.rb:118:in `load_user_config'
/home/dtk/.wmii-hg/lib/wmiirc/loader.rb:23:in `run'
/home/dtk/.wmii-hg/wmiirc:5:in `<main>'

I don't know what the responsible patch is doin', but it would be great if he wouldn't crash WMII.

That's really strange.  We're looping on the result of Dir.entries so those files should exist.  Anyway see if d30f1e3d7d6465faa1b5103ad64c6046ae1976e9 fixes the problem.

yepp, you fixed it. thx.


Update deploying-the-defender-easm-azure-resource.md

Please update regions and add westeurope to the list of available regions

@danielledennis
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Data no longer in DataFrame format

Hi,
Since I updated to entsog-py 1.0.2 the downloaded data cannot be correctly formatted by Pandas and remains as a long string. This was not the case with the previous versions.
Lucas

Hi Lucas,
Could you share exactly what endpoints you are using to get your data? Also share some example code so I might have a look. On my end it's working correctly, but I don't use all endpoints/options.

I believe the issue is that you have
data, url = client.query_operational_data(start=start,
end=end,
indicators=['physical_flow'])

instead of
data = client.query_operational_data(start=start,
end=end,
indicators=['physical_flow'])

``Hi again,
I've compared the latest version of entsog.py (1.0.2) with the one I was using privately (0.9.0) and realized that the function query_operational_data() is no longer present for the EntsogPandasClient. This means that the program is actually running the version of query_operational_data() written for EntsogRawClient and returning data in JSON format or something similar. This is why pandas could not parse it.
I just finished a hot fix by adding the older version of
def query_operational_data(self,
                               start: pd.Timestamp,
                               end: pd.Timestamp,
                               country_code: Union[Area, str],
                               period_type: str = 'day',
                               indicators: Union[List[Indicator], List[str]] = ['physical_flow'],
                               verbose: bool = True) -> pd.DataFrame:

and modifying the EntsogRawClient to this, so it could lookup operator by country:
  def query_operational_data(self,
                              start: pd.Timestamp,
                              end: pd.Timestamp,
                              period_type: str = 'day',
                              indicators: Union[List[Indicator], List[str]] = None,
                              point_directions : Optional[List[str]] = None,
                              operator : Optional[str] = None,
                              offset : int = None,
                              ) -> str:

       params = {
           'from': self._datetime_to_str(start),
           'to': self._datetime_to_str(end),
           'periodType': period_type
       }

       if operator is not None:
           params['operatorKey'] = operator

       if offset is not None:
           params['offset'] = offset
           params['limit'] = OFFSET

       if indicators is not None:
           decoded_indicators = []
           for indicator in indicators:
               decoded_indicators.append(lookup_indicator(indicator).code)

           params['indicator'] = ','.join(decoded_indicators)

       if point_directions is not None:
           params['pointDirection'] = ','.join(point_directions)

       if operator is not None:
           params['operator'] = ','.join(operator)

       response = self._base_request(endpoint='/operationaldatas', params=params)

       return response.text, response.url

Hopefully my changes are clear and can help others.

Greetings,
I have been running entsog-py 1.0.1 successfully for the last several months. These last few days, it began to exhibit problems.
Running a test in Python, the following lines:
from entsog import EntsogPandasClient
import pandas as pd
client = EntsogPandasClient()
fromDate = pd.Timestamp('2020-07-01', tz='Europe/Brussels')
endDate  = pd.Timestamp('2020-07-31', tz='Europe/Brussels')
opDataDF=client.query_operational_data_all(start = fromDate, end = endDate, indicators = ['renomination', 'physical_flow'])
produce this error:
/usr/lib/python3.11/site-packages/urllib3/connectionpool.py:1045: InsecureRequestWarning: Unverified HTTPS request is being made to host 'transparency.entsog.eu'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(
/usr/lib/python3.11/site-packages/urllib3/connectionpool.py:1045: InsecureRequestWarning: Unverified HTTPS request is being made to host 'transparency.entsog.eu'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.11/site-packages/entsog/decorators.py", line 144, in day_wrapper
frame = func(*args, start=_start, end=_end, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Any suggestions?

Hi eprinc-mp,
As I suggested in some other issues, you'll need to update the package to version 1.0.2. It seems ENTSOG have done some internal update which renders it impossible to send a verified (through https) request to the server using python. That's why I solved it with a tempory fix, which is:
requests.get(url, verify = False)

From your error message I can tell you have successfully updated to 1.0.2. as it's producing warnings rather than errors. These warnings are to tell you an unverified https request is being made; which is basically the temporary fix for V1.0.2. (the verify = false).
In short, you don't have any errors but rather warnings you can ignore until it's fixed in the next version.

Thank you for your reply and effort.
But in the end, no data is being returned with Version 1.0.2; is that correct?
Max

Depends, you're requesting a month of data; which could take about 30 seconds to a minute I believe. Since you are also requesting two parameters, it might take a bit longer. I have no issues on my end running your script. It just outputs the warning every time it makes a request. I might hide it in a future version, but you can also manually hide it using:
import urllib3
urllib3.disable_warnings()


Arch Linux AUR package

Is your feature request related to a problem? Please describe.
I created AUR package for Arch Linux: https://aur.archlinux.org/packages/cargo-deny/
The installation instructions for Arch Linux users:
yay -S cargo-deny

Describe the solution you'd like
I suggest adding this (as installation instructions or just a mention of the link) to the README

Neat! My one concern would be a new release being published without a corresponding update to the AUR package, and people filing issues against the version in AUR that were fixed/addressed in later versions, but that's just a hypothetical for now.

I subscribed for the releases on GitHub, and anyway, Arch Linux users  are used to flagging the version on the repository (there is such feature). Yet, feel free to ping me if there is an issue related to the package


Move to jupyter-widgets

How do you feel about moving this to the jupyter-widgets org to be the official cookie cutter?

I probably want to keep my own copy, but if that means to transfer to jupyter and then fork back, I'm happy with that. That being said, I'd argue for also keeping a minimal cookiecutter in pure JS, with minimal tooling. It is a good learning resource, and is handy for those who want to integrate widget development into their own tooling setup.

Transferred. Feel free to rename / update readme as appropriate.

Thanks! I agree about also keeping a minimal js cookie cutter.

@vidartf - Is it all right with you if we apply the standard Project Jupyter licensing and copyright statements to the files in this repo, at least the ones that make sense? (I don't think applying a license to the templates makes sense...)

Oh yeah, I didn't realize the root repo was missing a license. Standard BSD-3 etc. should be OK.


fix: update to eye v10.16.23

fix: update to eye v10.16.23

:tada: This PR is included in version 16.15.24 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v16.15.24

Your semantic-release bot :package::rocket:


Carthage Error

Xcode version: 10.1
Build version low
"Incompatible Swift version - framework was built with 4.1.2 (swiftlang-902.0.54 clang-9<IP_ADDRESS>) and the local version is 4.2.1 (swiftlang-1000.11.42 clang-1<IP_ADDRESS>)."

duplicate of #5949