Update build and testing dependencies

Description
Updates many build and test dependencies and cleans up unused version tags in external_dependencies.txt.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

/check-enforcer override

Failing tests are flaky as they are timing related.


Genereated Trpc routes does not return types for relations

Description and expected behavior
Generated Trpc routes do not allow for retrieving the types of relationships (include).
Screenshots
✅ With original Prisma client:

❌ With generated trpc routes:

Environment (please complete the following information):

ZenStack version: 1.0.0-alpha.116
Prisma version: 4.12.0
Database type: Postgresql

Additional context
When I overwrite the generated procedure...

...typing works well

But I don't have the solution to dynamically attach types to the procedure input.

As a workaround, destructuring the input object allows all relations to be present, but as optional.

Hi @Azzerty23 ,
Thanks for bringing this up. Unfortunately, this is a current limitation of tRPC. Due to the way how tRPC infers types, the router's typing is determined statically and cannot automatically adapt to the input's shape as Prisma could. Here's a github issue about this topic: https://github.com/trpc/trpc/issues/3311.
As suggested in the github discussion, it's possible to wrap another layer of hooks around the trpc router to achieve such kind of typing (pretty much what ZenStack is doing with the @zenstackhq/react plugin for generating react hooks), but that'll introduce more complexity and also strange to use because it doesn't look like using tRPC anymore ...
The workaround you suggested can also be useful, although not ideal. At least you can get autocompletion to work for the relation fields. Maybe we can make that change to the trpc plugin?

I was not aware of this limitation in tRPC. I understand that you do not want to tweak tRPC. I hope that this issue will be solved through an enhancement of TypeScript and tRPC implementation. In the meantime, having an option to opt-in for the workaround would be great for sure!

Cool. Let me think about how to express that "opt-in" 😄.

Hi, @Azzerty23 I'm thinking about this issue again, and I feel maybe we can do something to "fix" trpc's typing, by casting its client hooks appropriately. Are you using trpc over Next.js with createTRPCNext now?

I spent some time poking around trpc's typing and couldn't find a way to hack it on the server-side router definition, but I think we can probably fix it on the trpc client side, since we're doing code generation anyway.
The change may look like this:
import { enhance } from '../routers/generated/next-utils.ts';

const trpc = enhance(createTRPCNext<AppRouter>({
    ...
}));

The enhance function is generated and only does type-casting, turning hooks like findMany etc. into Prisma-style generic typing so that the output's type adapts to the input.
What's unfortunate is the casting is client-specific, so I guess separate code needs to be generated for different client frameworks. Haven't looked deeply into this yet.
Does this make sense to you in general?

I see, indeed it seems to be the best approach!

Thanks! I'll continue exploring this route then.

Hi @Azzerty23 , this has been added in the latest "beta.3" release.
https://zenstack.dev/docs/reference/plugins/trpc#client-helpers


[Go Live][Jan 22]

Push to live

Docs Build status updates of commit 7dfe830:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 7dfe830:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

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


PHP 7.3 Support

I wanna use "parsedown" supported to PHP 7.3.
Is there a plan there?

+1 readme says it supports php7.2 while composer saying >5.3.0


An unexpected error occurred. Fails to resolve DNS. But a curl call directly to mockbin.org works

Summary
I am trying to configure a service to the kong gateway. I am following this link
However i am getting an error ,
{"message":"An unexpected error occurred"}
However a direct curl call for the same API works fine.
Have asked the similar issue on the kong forum, but no result, https://discuss.konghq.com/t/configuring-amazon-skill-management-api-with-kong-gateway-fails/1910
When i tried the command sudo kong check, i get configuration at /etc/kong/kong.conf is valid
but when tried without sudo, i get
*2018/09/24 12:12:43 [warn] 29362#0: 2 [lua] client.lua:518: init(): [dns-client] Resolv.conf file not found: /etc/resolv.conf, context: ngx.timer
configuration at /etc/kong/kong.conf is valid
I am under a corporate proxy. the resolve.conf is present in the expected path. (As i said before, the curl call works!!)
Steps To Reproduce

setup kong
Add service . https://mockbin.org
Add route. host : example.com
call the command curl -i -X GET
–url http://localhost:8000/
–header ‘Host: example.com’

Additional Details & Logs

Kong version ($ kong version) : 0.14.1

Kong debug-level startup logs ($ kong start --vv)
2018/09/24 12:25:29 [verbose] Kong: 0.14.1
2018/09/24 12:25:29 [debug] ngx_lua: 10013
2018/09/24 12:25:29 [debug] nginx: 1013006
2018/09/24 12:25:29 [debug] Lua: LuaJIT 2.1.0-beta3
2018/09/24 12:25:29 [verbose] reading config file at /etc/kong/kong.conf
2018/09/24 12:25:29 [debug] reading environment variables
2018/09/24 12:25:29 [debug] admin_access_log = "logs/admin_access.log"
2018/09/24 12:25:29 [debug] admin_error_log = "logs/error.log"
2018/09/24 12:25:29 [debug] admin_listen = {"<IP_ADDRESS>:8001","<IP_ADDRESS>:8444 ssl"}
2018/09/24 12:25:29 [debug] anonymous_reports = true
2018/09/24 12:25:29 [debug] cassandra_consistency = "ONE"
2018/09/24 12:25:29 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
2018/09/24 12:25:29 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2018/09/24 12:25:29 [debug] cassandra_keyspace = "kong"
2018/09/24 12:25:29 [debug] cassandra_lb_policy = "RoundRobin"
2018/09/24 12:25:29 [debug] cassandra_port = 9042
2018/09/24 12:25:29 [debug] cassandra_repl_factor = 1
2018/09/24 12:25:29 [debug] cassandra_repl_strategy = "SimpleStrategy"
2018/09/24 12:25:29 [debug] cassandra_schema_consensus_timeout = 10000
2018/09/24 12:25:29 [debug] cassandra_ssl = false
2018/09/24 12:25:29 [debug] cassandra_ssl_verify = false
2018/09/24 12:25:29 [debug] cassandra_timeout = 5000
2018/09/24 12:25:29 [debug] cassandra_username = "kong"
2018/09/24 12:25:29 [debug] client_body_buffer_size = "8k"
2018/09/24 12:25:29 [debug] client_max_body_size = "0"
2018/09/24 12:25:29 [debug] client_ssl = false
2018/09/24 12:25:29 [debug] custom_plugins = {}
2018/09/24 12:25:29 [debug] database = "postgres"
2018/09/24 12:25:29 [debug] db_cache_ttl = 0
2018/09/24 12:25:29 [debug] db_resurrect_ttl = 30
2018/09/24 12:25:29 [debug] db_update_frequency = 5
2018/09/24 12:25:29 [debug] db_update_propagation = 0
2018/09/24 12:25:29 [debug] dns_error_ttl = 1
2018/09/24 12:25:29 [debug] dns_hostsfile = "/etc/hosts"
2018/09/24 12:25:29 [debug] dns_no_sync = false
2018/09/24 12:25:29 [debug] dns_not_found_ttl = 30
2018/09/24 12:25:29 [debug] dns_order = {"LAST","SRV","A","CNAME"}
2018/09/24 12:25:29 [debug] dns_resolver = {"<IP_ADDRESS>"}
2018/09/24 12:25:29 [debug] dns_stale_ttl = 4
2018/09/24 12:25:29 [debug] error_default_type = "text/plain"
2018/09/24 12:25:29 [debug] headers = {"server_tokens","latency_tokens"}
2018/09/24 12:25:29 [debug] log_level = "notice"
2018/09/24 12:25:29 [debug] lua_package_cpath = ""
2018/09/24 12:25:29 [debug] lua_package_path = "./?.lua;./?/init.lua;"
2018/09/24 12:25:29 [debug] lua_socket_pool_size = 30
2018/09/24 12:25:29 [debug] lua_ssl_verify_depth = 1
2018/09/24 12:25:29 [debug] mem_cache_size = "128m"
2018/09/24 12:25:29 [debug] nginx_admin_directives = {}
2018/09/24 12:25:29 [debug] nginx_daemon = "on"
2018/09/24 12:25:29 [debug] nginx_http_directives = {}
2018/09/24 12:25:29 [debug] nginx_optimizations = true
2018/09/24 12:25:29 [debug] nginx_proxy_directives = {}
2018/09/24 12:25:29 [debug] nginx_user = "nobody nobody"
2018/09/24 12:25:29 [debug] nginx_worker_processes = "auto"
2018/09/24 12:25:29 [debug] pg_database = "kong"
2018/09/24 12:25:29 [debug] pg_host = "<IP_ADDRESS>"
2018/09/24 12:25:29 [debug] pg_password = "******"
2018/09/24 12:25:29 [debug] pg_port = 5432
2018/09/24 12:25:29 [debug] pg_ssl = false
2018/09/24 12:25:29 [debug] pg_ssl_verify = false
2018/09/24 12:25:29 [debug] pg_user = "kong"
2018/09/24 12:25:29 [debug] plugins = {"bundled"}
2018/09/24 12:25:29 [debug] prefix = "/usr/local/kong/"
2018/09/24 12:25:29 [debug] proxy_access_log = "logs/access.log"
2018/09/24 12:25:29 [debug] proxy_error_log = "logs/error.log"
2018/09/24 12:25:29 [debug] proxy_listen = {"<IP_ADDRESS>:8000","<IP_ADDRESS>:8443 ssl"}
2018/09/24 12:25:29 [debug] real_ip_header = "X-Real-IP"
2018/09/24 12:25:29 [debug] real_ip_recursive = "off"
2018/09/24 12:25:29 [debug] ssl_cipher_suite = "modern"
2018/09/24 12:25:29 [debug] ssl_ciphers = "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256"
2018/09/24 12:25:29 [debug] trusted_ips = {}
2018/09/24 12:25:29 [debug] upstream_keepalive = 60
2018/09/24 12:25:29 [verbose] prefix in use: /usr/local/kong
2018/09/24 12:25:29 [verbose] preparing nginx prefix directory at /usr/local/kong
2018/09/24 12:25:29 [verbose] SSL enabled, no custom certificate set: using default certificate
2018/09/24 12:25:29 [verbose] default SSL certificate found at /usr/local/kong/ssl/kong-default.crt
2018/09/24 12:25:29 [verbose] Admin SSL enabled, no custom certificate set: using default certificate
2018/09/24 12:25:29 [verbose] admin SSL certificate found at /usr/local/kong/ssl/admin-kong-default.crt
2018/09/24 12:25:29 [warn] ulimit is currently set to "1024". For better performance set it to at least "4096" using "ulimit -n"
2018/09/24 12:25:29 [debug] searching for OpenResty 'nginx' executable
2018/09/24 12:25:29 [debug] /usr/local/openresty/nginx/sbin/nginx -v: 'nginx version: openresty/<IP_ADDRESS>'
2018/09/24 12:25:29 [debug] found OpenResty 'nginx' executable at /usr/local/openresty/nginx/sbin/nginx
2018/09/24 12:25:29 [debug] testing nginx configuration: KONG_NGINX_CONF_CHECK=true /usr/local/openresty/nginx/sbin/nginx -t -p /usr/local/kong -c nginx.conf
2018/09/24 12:25:29 [debug] searching for OpenResty 'nginx' executable
2018/09/24 12:25:29 [debug] /usr/local/openresty/nginx/sbin/nginx -v: 'nginx version: openresty/<IP_ADDRESS>'
2018/09/24 12:25:29 [debug] found OpenResty 'nginx' executable at /usr/local/openresty/nginx/sbin/nginx
2018/09/24 12:25:29 [debug] sending signal to pid at: /usr/local/kong/pids/nginx.pid
2018/09/24 12:25:29 [debug] kill -0 cat /usr/local/kong/pids/nginx.pid >/dev/null 2>&1
2018/09/24 12:25:29 [debug] starting nginx: /usr/local/openresty/nginx/sbin/nginx -p /usr/local/kong -c nginx.conf
2018/09/24 12:25:29 [debug] nginx started
2018/09/24 12:25:29 [info] Kong started

Operating system : Ubuntu 18

below is the error.log file info,

2018/09/24 11:31:59 [error] 1760#0: *1538 [lua] balancer.lua:806: execute(): [dns] dns lookup pool exceeded retries (1): timeout.  Tried: (short)mockbin.org:(na) - cache-miss
mockbin.org:33 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout
mockbin.org.eng.med.abc.com:33 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout
mockbin.org:1 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout
mockbin.org.eng.med.abc.com:1 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout
mockbin.org:5 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout
mockbin.org.eng.med.abc.com:5 - cache-miss/scheduled/querying/try 1 error: timeout/scheduled/querying/try 2 error: timeout/dns lookup pool exceeded retries (1): timeout
, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "example.com"
2018/09/24 11:59:57 [error] 1760#0: *17904 [lua] responses.lua:121: after(): failed the initial dns/balancer resolve for 'mockbin.org' with: dns lookup pool exceeded retries (1): timeout, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "example.com"
What could be the issue? seems like the gateway is not able to resolve the address

if you get the error without sudo, then it seems to me the process is unable to access /etc/resolv.conf due to limited rights. Make sure the rights are properly configured for the process to access /etc/resolv.conf.

Is there a way to provide a new resolve.config that only kong can use? Instead of the local /etc/resolve.conf .
Also, i tried changing the kong.conf file by disabling dnsmasq and providing the resolver address(say x.x.x.x) with following variable changes,
dnsmasq = false
dns_resolver = <IP_ADDRESS>,x.x.x.x

I followed @thibaultcha 's answer in this link

@bhargav01 The link is a very old issue. dnsmasq is not a dependency of Kong anymore since version 0.10, so setting dnsmasq = false will have no effect. Kong does not let you customize the resolv.conf path, and I am not sure if specifying dns_resolver would actually override the use of resolv.conf, maybe @Tieske can clarify? What are you seeing when you specify dns_resolver as such @bhargav01?

dns_resolver will only override the resolvers from resolv.conf the rest of what's taken from that file will still be in effect.

We haven't heard back about this so I am closing this for now. @bhargav01 please reopen if you still have questions or think Kong is not working properly.


DnsNameResolverContext#followCname only uses first name server

Motivation:
When following a CNAME it is possible there are multiple name servers to query against. However DnsNameResolverContext#followCname explicitly only uses the first name server address when attempting the query. This may lead to resolution failures because we didn't try all the available name servers.
Modifications:
DnsNameResolverContext#followCname should not just try the first name server, but it should try all name servers
Result:
More complete CNAME resolution.

Cherry-picked into 4.1 (fe5c69bdd9d65ddd604a03bfc71081b5bc2ad40a).
@Scottmitch thanks!


Dispose the AnimationController when an AnimatedSize is detached

I believe this will cause us to lose the current animation value and status when the object is temporarily detached from the tree e.g. during a global key re-parent.

The following test covers the concerns above:
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

class AnimatedSizeTest extends StatefulWidget {
  final double size;

  const AnimatedSizeTest({Key key, this.size}) : super(key: key);

  @override
  _AnimatedSizeTestState createState() => _AnimatedSizeTestState();
}

class _AnimatedSizeTestState
  extends State<AnimatedSizeTest>
  with TickerProviderStateMixin {
  @override
  Widget build(BuildContext context) {
    return AnimatedSize(
      duration: Duration(seconds: 1),
      vsync: this,
      child: SizedBox(width: widget.size, height: widget.size),
      curve: Curves.ease,
    );
  }
}

void main() {
  testWidgets('AnimatedSize animates through remount', (tester) async {
    final key = GlobalKey();

    await tester.pumpWidget(
      Column(children: [
        AnimatedSizeTest(key: key, size: 100.0),
      ]),
    );

    await tester.pumpWidget(
      Column(children: [
        AnimatedSizeTest(key: key, size: 200.0),
      ]),
    );

    await tester.pump(Duration(milliseconds: 500));

    expect(key.currentContext.size.width.round(), 180);

    // Remount
    await tester.pumpWidget(
      Column(children: [
        DecoratedBox(
          decoration: BoxDecoration(color: Colors.red),
          child: AnimatedSizeTest(key: key, size: 200.0),
        )
      ]),
    );

    await tester.pump(Duration(milliseconds: 250));

    expect(key.currentContext.size.width.round(), 196);

    await tester.pump(Duration(milliseconds: 250));

    expect(key.currentContext.size.width.round(), 200);
  });
}

This is intended to fix a memory leak.
The scenario I'm seeing is that each RenderAnimatedSize instance creates an AnimationController, which then asks the TickerProvider to create a Ticker.
But if the AnimationController is never disposed, then the Ticker is not disposed.  So the widget acting as the TickerProvider accumulates an unbounded set of tickers.
@Hixie

I agree with @goderbauer that this PR as written will introduce other issues, but the problem @jason-simmons describes is a real one... if we keep creating new RenderAnimatedSize objects, each one is going to create its own ticker, and they won't go away.
One solution might be to rename AnimatedSize to _AnimatedSize and then create a new AnimatedSize widget that's a StatefulWidget that mixes in SingleTickerProviderStateMixin, and whose build creates an _AnimatedSize with the vsync being itself. (That widget should probably take a vsync for historical reasons, but it should be ignored and deprecated.)
I wonder why we didn't do that in the first place... Am I missing something?

I don't see a good reason for the current behavior either. My suggestion on github also was to move the AnimationController into a stateful widget with a clear lifecycle.

An attempt to implement that design: https://github.com/flutter/flutter/pull/80554


Does not work in Linux mint 17.1 64-bit

Hello,
I've tested your software in my Linux Mint 17.1 machine but it does not seem to work properly.
The installation went smoothly, and I set up a hotspot using sudo hotspotd start and entered necessary info. The outputs suggest that hotspot is running, but it is not visible to any devices. I tried to connect to that in my iphone but it says not reachable.

Same here in Linux Mint 17.1 32 bits!!!

@andretnt  - Have you made sure that a firewall is not blocking your iphone from connecting?


Wormhole Transaction page not working

Hello team
I'm trying to access the Wormhole Transaction page, https://bigdipper.live/wormhole/transactions, to it is not loading the list of transactions. It is showing "Nothing to show".
Could you take a look please?
Thanks!

It takes a while to start showing the transactions:


Source maps are not relative to rootDirs

TypeScript Version:  2.1.1
Code
// Given a tsconfig.json of:
{
    "compilerOptions": {
        "outDir": "build/ts/",
        "target": "ES5",
        "module": "commonjs",
        "sourceMap": true,
        "sourceRoot": "/",
        "rootDirs": [
            "src",
            "build/ts/src"
         ]
    },
    "include": [
        "src/**/*",
        "test/**/*"
    ]
}

and a project structure of:

./src
./src/other.ts
./src/app.ts
./tsconfig.json
./test
./test/spec.ts
./build
./build/ts
./build/ts/src
./build/ts/src/other.js
./build/ts/src/other.js.map
./build/ts/src/app.js
./build/ts/src/app.js.map
./build/ts/test
./build/ts/test/spec.js.map
./build/ts/test/spec.js

Expected behavior:
The source map path should be relative to 'build/ts/src' rather than relative to 'build/ts'.
i.e
{"version":3,"file":"app.js","sourceRoot":"/","sources":["app.ts"],"names":[],"mappings":";AAAA;IACI,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC;AACvB,CAAC;;AAFD,sBAEC"}

Actual behavior:
Source map includes 'src/' in the path, even though the rootDir specifies build/ts/src as a root.
{"version":3,"file":"app.js","sourceRoot":"/","sources":["src/app.ts"],"names":[],"mappings":";AAAA;IACI,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC;AACvB,CAAC;;AAFD,sBAEC"}

The problem doesn't occur when there is no 'test' directory as part of the project as the generated files are placed in 'build/ts' rather than 'build/ts/src' and that can be used as the root instead.
I imagine this is a fairly common scenario. Outputting to a ts build directory with both source and test but using the 'src' as the root for the web application.

I was confused about this, too.  Apparently rootDirs is unrelated to rootDir, and doesn't affect the output.  [cite]

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


[Grid] Make item to expand if there are no more items in his row

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Observe Grid items that are laid out as the following:

Sometimes the items are rendered conditionally, and it can happen that the third item (xs=6) is not rendered. In that case it is often useful to expand the second item to take the whole width of the row.
This behavior would be turned on on an item with a flag. In the above example the second item would have:
<Grid item xs={6} growIfPossible>
(or even more flexible <Grid item xs={6} xsMaxGrow={12}> which would then allow different levels of expansion like <Grid item xs={6} xsMaxGrow={9}>)
Examples 🌈
No response
Motivation 🔦
No response

@croraf You can conditionally change the xs value of the second grid item to occupy the full row when the third item is not rendered.


Autoreload server on file change

Hello,
it's quite annoying to have to restart sane every time we change a server file.
Would it be possible to use the watcher already present for the client with the server files ?
There is a sails hook here providing this feature  but it does not seem to work with sane : https://github.com/sgress454/sails-hook-autoreload
I'm really new to Javascript on server and Node.js so I do not feel confident enough to work on a PR or even evaluate the amount of work it would require but I would love not going to my console to restart sane every time my server changes

@Systho You are right there seems to be an issue related to docker. If you use it without it should work fine though. I did just add that sane up is automatically appending the --verbose flag for sails so from the next version on you should see that the reload works.
Will look into docker support. But once that is fixed, was planning to add that. A PR once that is done would be accepted as well. It is quite simple, just adding it to https://github.com/artificialio/sane/blob/master/lib/commands/new.js#L290 :)

@Systho Latest version 0.11.4 of the autoreload hook fixes docker support, but it needs a custom setting for it. So you would also have to add a _autoreload.js to https://github.com/artificialio/sane/tree/master/templates/server/config that pre-configures the autoreload settings based on the --docker flag.
I know it can be daunting to get started with adding a new feature to a relatively big project, but I would encourage you to give it a try. If you have any more questions to get started I would be more than happy to answer them :)

Just tested and working with config/autorelaoad.js
var path = require('path');

module.exports.autoreload = {
  active: true,
  //use polling to watch file changes
  //slower but needed for the docker image
  usePolling: true, // this would be a variable in the template, probably {{autoPolling}}
  // Set dirs to watch
  dirs: [
    path.resolve('api','controllers'),
    path.resolve('api','models')
  ]
};

@Systho Feel up for the challenge?

I've done my best following your advices. It doesn't completely work as I would (editing blueprints for instance requires a full restart ) but that's mainly a concern for sails-hook-autoreload project.
Thank you for help (and I mean doing all the work ;) )


fix to make it compile with Xcode 9 beta 4

I'm not sure if this is new but the declaration for the navigationBar titleTextAttributes is:
@available(iOS 5.0, *)
open var titleTextAttributes: [NSAttributedStringKey : Any]?

so that caused a compilation error in the newest version of Xcode beta, this commit fixes it.
I'm not sure if this should be on the master branch or a feature branch for swift-4 but since it's the only public branch, here you go 😀.

As soon as Xcode 9 will be final version i will merge it

👍🏼

Already merged Swift 4 convertion


NYC Dependency "Wrong Version" Error?

Getting some bizarre dependency errors after updating (something changed in the last day?)
error "nyc#find-cache-dir#make-dir" is wrong version: expected "^1.0.0", got "2.1.0"

and similar...
Starting to investigate this more now.
Edit: It seems<EMAIL_ADDRESS>and<EMAIL_ADDRESS>are competing for dependencies?

find-cache-dir just released an update today which updated make-dir from ^1.0.0 to ^2.0.0.  I'm unsure what you've done but find-cache-dir is bundled with all current releases of nyc so it shouldn't have updated.  Possibly npm update or something like that breaks bundled modules (unless you're installing nyc from the git repo).

More precisely this happens when running
yarn check --integrity --verify-tree

Please post a link to a repository where you are seeing the issue.

Sure thing. Here are simple instructions to reproduce:
(1) Checkout https://github.com/blackflux/object-rewrite locally
(2) Run yarn install --freeze-lockfile
(3) yarn check --integrity --verify-tree -> succeeds
(4) Run yarn upgrade
(5) yarn check --integrity --verify-tree -> now fails

I believe you are experiencing a bug in yarn.  I'm getting a different error "nyc#make-dir#pify" is wrong version: expected "^3.0.0", got "4.0.1" but this tells me that yarn is not resolving the dependencies correctly.  Worth noting that yarn really shouldn't be messing with the nyc dependencies as they are bundled.  I didn't experience this issue with npm but I don't know how you would generate a working updated yarn.lock.

Oh boy... thanks for the quick help!
I'll report back here with any further findings, but feel free to close this for now. I will request a re-open as necessary.

I hope you find resolution, sorry I can't be more directly helpful.


Error with tags

Describe the bug

When try to create shortcuts on the tag list I only see one tag. And I've created more than one tag.
When I fixed one shortcut I cannot defixed it...

Steps to reproduce

Make some tags...

Try to make a shortcut with the second tag...

Fix a shortcut.

Try to defix it...

Screenshots or additional context

can not reproduce first one, i will try to fix the second

can not reproduce first one, i will try to fix the second

You can reproduce it with:
#tag1 #tag2 #tag3 (this only create tag3, one space separator)
#tag1  #tag2  #tag3  (this works, two space separator)

still can not, maybe you can try to reproduce on https://demo.usememos.com/ and let me know

In demo works fine!
Maybe it was something from the 0.8 version.

Feel free to reopen this issue if you have other questions.


FRR-K8S via CNO fixes

Wait for metallb pods to appear
Wait for the proper endpoints behind the metallb validation service
Pass the FRR-K8s namespace when running externally

/lgtm


sussy scan got a new site

Source information
sussy scan 1.4.41
Source language
Brazilian Portuguese
Source new URL
https://new.sussytoons.site/
Other details
the old site don't update chapter's
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

ops , i already make this request i guess , i don't know how github works


[Bug] horizontal label margin (distance) in vertical marklines not working

Version
5.3.2
Link to Minimal Reproduction
https://codepen.io/sverbach2/pen/PoQByvW
Steps to Reproduce

Load the codepen
Search for the label "I should have x-offset" in the chart
This label should have an offset of 30px, but none is applied
Note that issue only seems to appear when using vertical marklines, I do not encounter this issue on horizontal nor 2d-marklines.

Current Behavior
X-value of the distance property is not applied on the label when using vertical marklines.
E.g. distance: [30, 10] applies a 10px y-margin but 0px x-margin.
Expected Behavior
I would expect to be able to apply x- and y-distance on my markline labels.
E.g. distance: [30, 10] applies a 10px y-margin and 30px x-margin.
Environment
- OS: Windows 11, Windows 10
- Browser: Brave 1.39.111, Chrome 102.0.5005.63, Firefox 101.0,
- Framework: None

Any additional comments?
When using any other type of marklines (other than vertical ones), this bug will not occur.

This seems to be a bug.

Conclusion
distance and offset has almost the same function and offset works well with any direction. I would suggest use offset only and delete distance as an API for user.
Of course if you want to know why problem exists for distance, keep reading.

Problem Location

The place where the position of label is determined is as followed:
https://github.com/apache/echarts/blob/11a9247e7fab2e6ff9c60b545ba775e8c1b2412f/src/chart/helper/Line.ts#L449-L454
Here distanceX/Y is literally the user-specified distance and they are multiplied by d[0]/d[1]. d is derived here:
https://github.com/apache/echarts/blob/11a9247e7fab2e6ff9c60b545ba775e8c1b2412f/src/chart/helper/Line.ts#L365-L366
toPos and fromPos is the starting point and ending point of the line and d means whether they have differences on x or y coordinates. For example, d=[0,1] if the line is parallel to y axis and point at positive direction. Now that explains why distanceX won't work at label.x because d[0] = 0 and it deactivate the effect of distanceX.

I would submit a PR to either delete the distance API, or fix distance API. I consider the former one better because these two APIs are functionally replicate.


Date appearance blinking upon reloadData

I am saving state on dates and I toggle it when I press on the date. Then the state chages, I reloadData so I can display states.
I encountered a problem, when random date appearance blinks when I click, toggle and reloadData.
Here I recorded the behaviour in simulator:
https://streamable.com/6nked
Any idea?
EDIT: Similar issue: https://github.com/WenchaoD/FSCalendar/issues/940

Our app is having the same issue. I will post here if I find a solution. Appreciate if anyone else will do to the same.

@DavidBalcher Thank you for the comment, hopefully someone with ability to fix it answers.
I have found a 'workaround' for now.
What I did is I get the cell and IndexPath and I reload single cell from collectionView of the calendar.
Example:
if let cell = calendar.cell(for: date, at: monthPosition) {
    let index = calendar.collectionView.indexPath(for: cell as UICollectionViewCell)!
    calendar.collectionView.reloadItems(at: [index])
}
calendar.deselect(date)

With that code, I am able to reload single cell and calendar doesn't give that 'flash' effect.
Only problem here is with selecting dates from previous and next month so I had to hide them with
calendar.placeholderType = .none

Thank you @frasza! This was very helpful.
Made a few changes for my case to prevent the user from selecting the same date twice in a row.
`            guard self.calendar.selectedDate != date else { return }
        let cell = self.calendar.cell(for: date, at: .current)

        if let index = self.calendar.collectionView.indexPath(for: cell as UICollectionViewCell) {
            self.calendar.collectionView.reloadItems(at: [index])
            self.calendar.deselect(date)
        }`

up! I have the same issue

The reason why other cell blinking maybe the cell's selected flag is wrong when doing mutiple reloading operations.
Which I do to fix this is to override the system selected attribute,like this:
// FSCalendar.h
/**
 A flag marks cell's selection state,like cell's selected
 */
@property (nonatomic, assign) BOOL realSelected;

putting "calendar.reloadData()" before "calendar.select(date)" will solve the blinking problem

I am facing the same issue despite following the above solutions! Please help!

Add this variable
private var previouslySelectedDate: Date?

And do like this. this worked for me.
func calendar(_ calendar: FSCalendar, didSelect date: Date, at monthPosition: FSCalendarMonthPosition) {
        if let previousDate = previouslySelectedDate {
            calendar.deselect(previousDate)
            if let previousCell = calendar.cell(for: previousDate, at: monthPosition) {
                let previousIndex = calendar.collectionView.indexPath(for: previousCell as UICollectionViewCell)!
                calendar.collectionView.reloadItems(at: [previousIndex])
            }
        }
        if let cell = calendar.cell(for: date, at: monthPosition) {
            let index = calendar.collectionView.indexPath(for: cell as UICollectionViewCell)!
            calendar.collectionView.reloadItems(at: [index])
        }
        previouslySelectedDate = date
        self.delegate?.didSelectDate(date: date)
    }

    func calendar(_ calendar: FSCalendar, didDeselect date: Date, at monthPosition: FSCalendarMonthPosition) {
        if let cell = calendar.cell(for: date, at: monthPosition) {
            let index = calendar.collectionView.indexPath(for: cell as UICollectionViewCell)!
            calendar.collectionView.reloadItems(at: [index])
        }
    }


Enables Kafka binding tests

squashed and merged as https://github.com/spring-cloud/spring-cloud-stream/commit/0c76a1edd31b0667737697d2174ca0c62118172e


Resolve an infinite loop around impossible cron schedules

We got some infinite (or near enough to infinite) hot loops in cron-schedule-Next-ing code today.
While we don't yet have any concrete examples to investigate, I'm going to claim it's due to being 2 weeks away from the end of February, and February is weird.  People are probably accidentally scheduling things for Feb 30 or 31.
There does seem to be some invalid cron schedule parsing happening in robfig/cron, e.g. for 0 0 0 , 0, but the bulk of the blame for this rests on our code: .Next returns a zero-valued time if there is no next time, and that's .Before other dates... by a very large margin.
There's a decent chance the next .Next will return another zero value too, leading to a truly infinite loop.
Since a lot of this code was kinda ridiculous about not returning errors, I've just changed that and all callers.
In most cases there was a simple place "nearby" that already returned errors, so it just now returns another kind of error.

Because these invalid schedules are likely always invalid (robfig/cron checks 5 years of values, e.g. to work around leap years), and this would always infinite loop on those values, I believe it's safe to assume that these invalid cron schedules have never been written to databases.

Pull Request Test Coverage Report for Build 01865255-ee00-4713-9f0d-e7b43186ff45

45 of 83 (54.22%)  changed or added relevant lines in 8 files are covered.
158 unchanged lines in 17 files lost coverage.
Overall coverage decreased (-0.1%) to 57.112%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/util.go
5
7
71.43%

service/history/decision/checker.go
2
4
50.0%

service/history/execution/mutable_state_builder.go
3
5
60.0%

service/history/task/transfer_active_task_executor.go
2
4
50.0%

common/log/tag/tags.go
0
3
0.0%

service/frontend/workflowHandler.go
11
24
45.83%

common/backoff/cron.go
21
35
60.0%

Files with Coverage Reduction
New Missed Lines
%

client/history/client.go
2
38.1%

client/history/metricClient.go
2
45.3%

common/backoff/cron.go
2
66.67%

common/membership/hashring.go
2
83.54%

common/task/fifoTaskScheduler.go
2
85.57%

service/history/handler.go
2
47.15%

service/history/shard/context.go
2
66.52%

service/matching/taskListManager.go
2
78.72%

service/history/task/fetcher.go
4
91.24%

service/frontend/workflowHandler.go
5
59.86%

Totals

Change from base Build 01864c84-f59b-4822-a8e4-1c6ff770d9df:
-0.1%

Covered Lines:
84886

Relevant Lines:
148630

💛  - Coveralls


[Github] Add heading elements for account login page to improve accessibility & SEO

1. Why is this change necessary?
This change is necessary to enhance the accessibility of the account login page. Proper use of heading tags is a key principle of accessible web design as outlined by the Web Content Accessibility Guidelines (WCAG). Not only do they help screen reader users understand the structure and navigate the content more effectively, but they also provide semantic meaning to the document for assistive technologies. Additionally, although SEO is not a primary concern for a login/signup page, having a well-structured document is a good practice and ensures consistency across the platform.
2. What does this change do, exactly?
The change introduces h2 heading tags to the login-card and register-card sections of the account login page. Ideally you would also want an h1 element on the page, but this currently doesn't exist and I'd say the login-card and register-card are equal to each other in importance.
3. Describe each step to reproduce the issue or behaviour.

Go to the account login page e.g. https://shopware.bluebirdday.io/account/login
Inspect the login-card & register-card title
They are not wrapped in a heading element

4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

Imported from Github. Please see: https://github.com/shopware/shopware/pull/3659

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-35318
[created from NEXT-35318, comment 511883]


add destroy

Issues
#135
I can't tell if my method to remove the stylesheet is too risky. I figured it'll always be the last element in the head because its being appended in the javascript but I'm interested to hear your thoughts @samussiah

shoot, i merged before i saw your comment.  is the stylesheet attached to the crfHeatMap object?  is it possible to just remove that?


What do you want to see in kedro-pandera?

Description
Opening the floor for feature request discussion, what do you want to see in this plugin? What should it do and what it shouldn't do? Why is it important to you?

In addition to runtime validation through annotated python
So I’d be interested in exploring if we could use the new catalog metadata to declare this on a dataset level
You could then generate data docs like dbt does
You could then run something like kedro pandera test to run over persisted data

so dbt test doesn’t do runtime validation,it only does checks on persisted data or *materialised if we’re being pandemic
so in a running system its good to have these kind of checks as part of CI/CD
for Kedro’s purposes validation is important both at runtime and at rest

(STILL A WIP)
I will try to sum up the trials and errors I made and my current opinion about the design. It is not tottaly fixed yet but I think we could make a MVP out of it quite quickly.
First attempt : validation at runtime
My first idea was the following:
Declare the schema in your catalog
iris:
    type: pandas.CSVDataSet
        filepath: /path/to/data/iris.csv
        metadata:
            pandera:
                schema: <pandera_schema> # not sure neither about the format nor the name, see below

and a hook will perform runtime validation:
from pandera.
class PanderaHook:
    @hook_impl
    def after_context created(...):
        # pseudo code, I don't know the syntax
        for dataset in catalog:
            dataset.metadata.pandera.df_schema=DataFrameSchema(dataset.metadata.pandera.schema)

    @hook_impl
    def before_node_run(
        self, node: Node, catalog: DataCatalog, inputs: Dict[str, Any], is_async: bool
    ) -> None:
        for name, data in inputs.items():
	    df_schema=datasetcatalog.get(name).metadata.pandera.df_schema # pseudo code, I don't know the syntax
	    df_schema.validate(df)

Open questions about catalog configuration
Shoulds we use the "metadata" key to store ?

pb for interactive use in notebook?

What about an encapsulating dataset instead, like MLflowArtifactDataset? This is much more complicated though.
What about an after_catalog_created hook which decorate all load/save methods? This will not work when creating the dataset outside a context though.

How many nested level should we use in the metadata key?

should we use kedro_pandera? pandera? as a second level key?
should we use schema if this key contains a path to the schema rather than the schema itself? Even if it is a dictionnary, it is not the schema in a pandera way, so what the less confusing name?

What should the schema key contain:

a path to a yaml file?

Advantages :

delegate everything to pandera

Drawbacks :

we need to hard code the path to the yaml file which is a big problem when deploying, users will need to inject project path at runtime dynmaically with Templated/OmegaConfigLoader, looks like a bad development experience
the schema is really hard to write manually, we need to add an helper to generate it

a path to a python module that we import with importlib.import_module (eg. my_package.pandera.schema.MyIrisSchema)?

Advantages : the syntax to create a schema is much easier AND we can define custom checks instead of only using built-in ones
Drawback : this should rather been located in src, so the user will have to specify the module by himself, we cannot assume too much about the structure

The schema as a dictionary.

Advantages: this is very explicit and a good "documentation" in the catalog
Drawbacks :

This is very verbose and the catalog will soon be overcrowded.

We can leverage ConfigLoader to generate a schema with the same name in another catalog_schema_iris.yaml file, but I am afraid this will not be very clear that the 2 are merged automagically. Another option is to refer to it as ${iris_schema} but this will require users to add this line manually for each entry of the catalog

should we enable several of above solutons? all solutions? If yes, we should likely add a second metadata key to indicate how to load the schema? what would be its name and possible values?

Which other key should we have?
see: https://pandera.readthedocs.io/en/stable/dataframe_schemas.html

dtypes?
coerce?
strict?
Index?

Open questions about plugin configuration
TODO
How to add advanced configuration capabilites to the plugin ?
We can add a configuration file:

advantage: enable lot of customisation
drawback: more complex to use

What level of lazy validation should we enable ?

fail immediately the pipeline when a check fails?
fail immediately the pipeline when a dataset fails but try all checks of the dataset before failing?
run the pipeline until the end despite validation errors and raise an error at the end?
run the pipeline until the end despite validation errors and only raise warnings?

When should validation be triggered?

on dataset save?
on dataset load?
both?

Whatever we decide, this should likely be configurable.
Temporarily avoid validation, or only for given pipelines
TODO
Open questions about runtime validation?
TODO
CLI
TODO
How can we generate default schema and test for a dataset?

load a dataset in memory (highly inefficient)
infer schema
persist the schema (where - src/ or conf/ -  and how - python, yaml, ... - still to be defined)

Should we let users generate the schema of several datasets at the same time?
TODO
Other desirable features:

generate fake data with the CLI as a demo
run the pipeline with fake generated input for tests
validation for dataset which do not fit in memory? i don't really see how it will work with kedro run because data will be loaded in memory, but maybe a CLI to check a specific dataset?

Super nice work @Galileo-Galilei I'm super keen to help get this off the ground. I'm keen to write up my thoughts in detail later on, but I wanted to point to the built in methods which we should leverage here:

pandera.io.from_yaml
pandera.io.deserialize_schema

Yes, that's what I have been playing with. For many reasons i'll discuss later, from_yaml is hard to use but deserialize_schema seems the way to go ;) Not too much time this week but I'll resume next week and suggest a MVP. Hopefully we can release a 0.1.0 version next week. If you want to go on without me, feel free, @noklam has the rights on the repo.

Thank you again for kicking this off on @Galileo-Galilei , I've got a few year's worth of thoughts on this topic so would love to talk about the things I'd like to see in this space.
Also I'm interested in this Frictionless schema standard Pandera has started to support as well, it looks early days - but I do love an open standard.
As per your thoughts on YAML vs Python I think we're going to have to manage 3 patterns, users will inevitably want all 3 for different reasons -

Python schema declared in catalog
YAML schema declared in catalog
Python schema annotated in src (although pretty hard for us to control on a plug-in level)

1. Online checks

There is a run-time performance penalty every time the python function is called. I might be wrong on this, but I wasn't able to find a way of disabling checks on a global level.
If we wanted to provide say a CLI option to disable runtime checks we can ignore catalog checks, but for the annotated checks we may need to do some gross monkeypatching.

2. Offline checks

This is more like the dbt pattern of running checks on persisted data, you manage the performance penalty in a different way and some workflows are better suited to something like a nightly check rather than a runtime one.
This is somewhere where the Kedro catalog metadata integration like the one you suggest above feels really neat.
I would love a world where we have a kedro catalog validate command and all tests on non-memory datasets a run. Bonus points if this somehow scoops up the python API tests as well as the YAML declarative ones.

3. Interactive workflow (Jupyter)

I wonder if we could introduce a catalog.validate() method which runs tests declared in the catalog? This is why I've designed the snippet above in a somewhat generic validators structure
We could even allow for a prototyping workflow with catalog.validate("dataset_name", SchemaClass)...

4. Data docs

Again dbt has had this for years and it's just a no brainer, we could easily generate static docs describing what data is in the catalog, associated metadata and tests.
There is also an obvious integration point with enterprise catalogs like Alation/Colibra/Amundsen

5. Datasets in scope

I think if we support Pandas and Spark we cover the vast majority of use cases
Ibis and Polars would be my next picks if Pandera were to support them.

6. Inferered schemas

I get the motivation in inferring schemas as a way of bootstrapping users to do this properly, but I do like to err on the side of explicit rather than implicit.

All in all I'm super excited to help get this off the ground, @noklam if you could make me an editor that would be great. I'm also going to tag my colleague @isnegm who has used Pandera a lot at QB and has some very well thought out ideas on the topic. Medium term we should also validate our ideas/roadmap once they're a bit more concrete with Neils the maintainer :).

Very nice thoughts about this. I think it's already worth creating more specific issues for some of them!
Some quick comments:

don't know about frictionless, but I like the idea too. I had a lot of import issues while creating the MVP so the python package may be hard to handle
schema types support: we clearly need to support all the way to create such schema in pandera, and this is likely the very next thing to work on !
Online check : I have not used pandera enough to know how painful the performance penalty is, but this is really something to take into account. Regarding a potential flag to deactivate pander agloablly, I found the PANDERA_VALIDATION_ENABLED in documentation since 0.16.X but I don't know if it apply only to spark because it is in the spark section of the documentation?
interactive worklflow: I'd love to have something like this too. The design should be thought in details. Notice you can already do something like (ugly but still easy):

data=catalog.load("dataset_name")
catalog._data_sets["dataset_name"].metadata.pandera.schema.validate(data)

With the same logic, maybe a CLI command kedro pandera validate would be helpful too, I guess you sometimes just want to check a new dataset quickly.

data docs: I have mitigated feelings. I'd really want a way to use all the datasets metadata to document the project but I don't know what the right design is. I think that if we want to create HTML documentation from the schema, this rather belongs to pandera itself. A feature I'd love to have is a previex of the schema in kedro-viz, but I have absoluetly no idea of how to make this work.
datasets in scope : I think we should aime to be agnostic and support any dataset supported by the pandera backend, but if we need to reduce the scope, pandas and spark are the way to go ;)
inferred schema: Totally agree that they could be abused and they are not something we want to encourage users to use without modifications. That said from a development perspective the yaml file is far too tedious to write manually (especially if we have a lot of colum,s), we really need to support a way to generate it out of the box.

If we end up talking with pandera maintainers themselves to validate the roadmap that could be great, but we not even close for now :)

When using coerce=True with Pandera schemas, validating a dataset may also change the data content.
I think it would be great if the datasets that are validated are passed as inputs or outputs using their coerced+validated outputs. However, the before_pipeline_run doesn't seem to allow changing the actual dataset being passed to a node.

Just to be sure I get it well, there are 2 separate points here :

in pandera, if you do df_schema.validate(df, coerce=True),  the dataset is modified inplace to convert types. This does not work in kedro-pandera (the coercion applies only for validation but the dataset is unmodified, i.e. the pandera schema converts a field as float but the nodes uses the data as int). You'd like to modify the dataset on the fly so the node receives the sales types that the ones which are tested against the dataset. Do I understand correctly?
for the second point, this is not totally clear to me : you want us to return 2 different outputs so you can choose between the one you want dynamically?

@Galileo-Galilei
In both cases, what I am looking for is that after loading or saving the dataset, the dataset I will work with is the modified dataframe - because of coercion.

When loading: I am type-hinting my nodes with the Pandera schema that is expected in a function, the kedro-pandera plugin can help me ensure that that is exactly the data I will be receiving in the node.
When saving: In the catalog we have specified the schema of the dataframe. By allowing coerce=True, I can be sure that the dataset that was saved is actually matching the schema. So when my schema says a column is an int, I can be sure that the data that was saved also saved it as an int.

I don't think I need to 2 different outputs or choose between them dynamically. In my mind, the only datasets that go into a node, or are saved to locations - are the validated and possibly modified datasets.

I would to make a PR that changes where exactly the validations happen in kedro-pandera to illustrate what I mean.


does it support images to video ?

Hi ,
does this package  support images to video  ?

Could you give an example? I guess you want to create a video out of a series of images?

Yes that what I'm looking for

It's not supported out of the box but you can probably do it with some custom filters. I haven't tested this one but I think you need something like this:
FFMpeg::fromDisk('images')
    ->open('image%04d.jpg')
    ->addFilter('-r', 60)
    ->addFilter('-f', 'image2')
    ->export()
    ->toDisk('videos')
    ->inFormat(new \FFMpeg\Format\Video\X264)
    ->save('video.mp4');

Here are two resources to read more about it:
http://hamelot.io/visualization/using-ffmpeg-to-convert-a-set-of-images-into-a-video/
https://en.wikibooks.org/wiki/FFMPEG_An_Intermediate_Guide/image_sequence


HADOOP-17164 UGI loginUserFromKeytab doesn't set the last login time

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 33s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m  5s
trunk passed

+1 :green_heart:
compile
21m 50s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
18m 11s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
0m 49s
trunk passed

+1 :green_heart:
mvnsite
1m 26s
trunk passed

+1 :green_heart:
shadedclient
16m 21s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 38s
hadoop-common in trunk failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 57s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+0 :ok:
spotbugs
2m 17s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 14s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s
the patch passed

+1 :green_heart:
compile
20m 57s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
20m 57s
the patch passed

+1 :green_heart:
compile
18m  2s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
18m  2s
the patch passed

-0 :warning:
checkstyle
0m 48s
hadoop-common-project/hadoop-common: The patch generated 2 new + 83 unchanged - 0 fixed = 85 total (was 83)

+1 :green_heart:
mvnsite
1m 24s
the patch passed

-1 :x:
whitespace
0m  0s
The patch has 1 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shadedclient
14m 31s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 39s
hadoop-common in the patch failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 59s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
2m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
10m  1s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 47s
The patch does not generate ASF License warnings.

156m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2178

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux f5be6c9452a0 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 05b3337a460

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/artifact/out/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

checkstyle
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

whitespace
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/artifact/out/whitespace-eol.txt

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/artifact/out/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/testReport/

Max. process+thread count
2718 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2178/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Request for static libedgetpu.a

Would it be possible to remove the explicit dependency on libc++.so.1 and  libc++.so.1 . Those are old libraries from older Debian releases which I think the official build process uses. This prevents us from using libedgetpu.so on newer AARCH64 releases like 64 bit Gentoo on RPi4 (https://github.com/sakaki-/gentoo-on-rpi-64bit) .
Or alternatively please package the libc++ deps too, or better yet just open source libedgetpu.so :)
After fighting bazel on ARM64 and cross compiling etc. I have a simple CMake based CPP EdgeTPU example here: https://github.com/powderluv/etdemo

There is no dependency on these libraries in the latest libedgetpu.so in this repo:
$ curl -OL https://raw.githubusercontent.com/google-coral/edgetpu/master/libedgetpu/direct/aarch64/libedgetpu.so.1.0
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  773k  100  773k    0     0  1796k      0 --:--:-- --:--:-- --:--:-- 1795k

$ readelf -d libedgetpu.so.1.0  | grep Shared
 0x0000000000000001 (NEEDED)             Shared library: [libusb-1.0.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [ld-linux-aarch64.so.1]

great to know. I had an older version in the system path
powderluv@pi64 ~/github/etdemo/b $ ldd /usr/lib64/libedgetpu.so.1
linux-vdso.so.1 (0x0000007f9baac000)
libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x0000007f9b989000)
libgcc_s.so.1 => /usr/lib/gcc/aarch64-unknown-linux-gnu/9.2.0/libgcc_s.so.1 (0x0000007f9b965000)
libc++.so.1 => not found
libc++abi.so.1 => not found
libm.so.6 => /lib64/libm.so.6 (0x0000007f9b8b6000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000007f9b885000)
libc.so.6 => /lib64/libc.so.6 (0x0000007f9b706000)
/lib64/ld-linux-aarch64.so.1 (0x0000007f9ba7e000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000007f9b6df000)
libudev.so.1 => /lib64/libudev.so.1 (0x0000007f9b6a8000)
BTW - any chance this lib will be available in source form ? Just makes compilation in newer architectures easy (Gentoo / RISC-v etc)
Thanks

also any chance it could be a static lib.
EDIT title for static request

@powderluv we have something coming for you soon and you'll enjoy it :)

Can't wait for it 🤪

@powderluv
FYI :) https://github.com/google-coral/libedgetpu

More teasing :)
Can't wait for the sources. I only see the license and readme.

Done!


Close Buttons not working in Running Pipeline

Seems like there is still some problem with the Close Buttons in the Pipeline View.
I encountered it only when the Pipeline was showing running status but had completed midway.

I would also like to work on this issue, still need confirmation. @pombredanne

@OsmiumOP could you provide some steps to reproduce the issue? I couldn't get the button to not work so far.

The close buttons are working as expected in the current main branch.


Error when I execute ./throat.py migration apply

I get this error
 peewee.OperationalError: could not connect to server: Connection refused         Is the server running on host "localhost" (<IP_ADDRESS>) and accepting         TCP/IP connections on port 3306?

you running mysql? if not then that port needs to be changed. if you are running mysql then the server probably isnt up


Incorrect / invalid titles in the OG tags for /x/ modules

Third-party module pages such as https://deno.land/x/talk_lib/ returns an incorrect value in its title and og:title properties. For some reason it's also different locally. When looking at the network request for https://deno.land/x/talk_lib/, you see
<meta name="title" content="deno.land/x/undefined" />

and
<meta property="og:title" content="deno.land/x/undefined" />

And yet, when you look at the head in the devtools it's different again, most likely altered by the JS on the page. In the devtools it says
<meta name="title" content="deno.land/x/talk_libundefined">
<meta property="og:title" content="deno.land/x/talk_libundefined">

Looking at this now


Command suggest

PEx 've already had a useful command: pex user <user> group add <group> [world] [lifetime]
But incase we run this command again for a user with same group, the lifetime will be overridden with new lifetime. It would be great if there's a command like pex user <user> addtime <group> <lifetime> [world]
to give more time for that user to be in a group

No new features will be getting added to PEX 1.x, but @zml2008 may consider doing something like this for PEX 2.x since it's still in development.

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.


azure-arm: Add support to create disks in specific availability zones

azure-arm: Add support to create disks in specific availability zones
Description
Azure ARM's compute driver does not provide the ability to pass zones when creating a new volume. This change adds a new parameter that allows passing zones as a list of strings.
Some open questions for the maintainers:

I have also merged the disk API versions because the zones parameter was only supported in newer API versions. I do not fully understand the impact of bumping the API versions, but if tests pass, I think it should be fine. Thoughts?
The new API version also caused request and response payloads to differ i.e. the volume types are now passed as DiskSku objects instead of strings. How do we handle API changes? Is there documentation around making such API changes?

I have tested the following disk operations:

Create empty disks.
Attach disks to a VM.
Resize disks.
Detach disks.
List disks.
Delete disks.

Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[ ] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

Codecov Report

Merging #1736 (3693f21) into trunk (26f07ac) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            trunk    #1736   +/-   ##
=======================================
  Coverage   83.29%   83.29%
=======================================
  Files         400      400
  Lines       87770    87772    +2
  Branches     9331     9332    +1
=======================================
+ Hits        73104    73106    +2
  Misses      11486    11486
  Partials     3180     3180

Impacted Files
Coverage Δ

libcloud/compute/drivers/azure_arm.py
57.81% <100.00%> (+0.06%)
:arrow_up:

libcloud/test/compute/test_azure_arm.py
98.81% <100.00%> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

@Kami when you get a chance, can you please take a look at this change? Thanks in advance.

@pgandhi-delphix Sorry for the delay, I will look into it this weekend.

As far as your two questions go:

I have also merged the disk API versions because the zones parameter was only supported in newer API versions. I do not fully understand the impact of bumping the API versions, but if tests pass, I think it should be fine. Thoughts?

Integration tests would increase the confidence here, but sadly we don't have integration tests for Azure ARM.

The new API version also caused request and response payloads to differ i.e. the volume types are now passed as DiskSku objects instead of strings. How do we handle API changes? Is there documentation around making such API changes?

One option would be to allow user to pass api_version or similar argument to the constructor and then when user specifies a new version which uses new DISK_API_VERSION value, otherwise it would default to the previous value.


webserver crashes when serving multiple larger files

Im currently involved in a project requiring 5 larger (~15kb) files. The Problem now is, that the webserver crashes rather quickly and becomes unresponsive. Are there any solutions for that? Setting the backlog parameter helps to some extend but does not resolve the issue completely. Im running the latest micropython with frozen micro web src module.

@Tobinator32 : Have you found a solution to your problem? Was it really linked to the size of the files?

Hi. It seems like a general Problem with Micropython. See the discussion there: https://github.com/micropython/micropython/issues/12819
At this point it doesnt seem to be a problem specifically with your webserver.
Kind Regards Tobi

@Tobinator32,
Ah yes indeed, quite a discussion and with dpgeorge :)
MicroWebSrv2 never opens the complete file in memory, precisely to avoid worries about excessive reservations. So that's another problem.
Personally, I use MicroWebSrv2 quite a lot in CPython on large Web servers.
Thanks to you in any case!


VM Developer image Artifact download

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az artifacts universal download Extension Name: azure-devops. Version: 0.8.0.
Errors:
_sigint_handler() takes 1 positional argument but 3 were given
Traceback (most recent call last):
pip-install-v1m4qsu_\knack\knack\cli.py, ln 206, in invoke
cli\core\commands\__init__.py, ln 560, in execute
cli\core\commands\__init__.py, ln 618, in _run_jobs_serially
cli\core\commands\__init__.py, ln 609, in _run_job
...
azext_devops\dev\common\external_tool.py, ln 74, in run
    line = bline.decode('utf-8', 'ignore').strip()
TypeError: _sigint_handler() takes 1 positional argument but 3 were given

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az artifacts universal download --organization {} --feed {} --version {} --name {} --path {}

Expected Behavior
Environment Summary
Windows-10-10.0.17134-SP0
Python 3.6.6
Shell: powershell.exe

azure-cli 2.0.64

Extensions:
azure-devops 0.8.0

Additional Context

@geverghe : Any idea how this can be routed to artifacts team?
cc: @snankani

@elbatk - Could you guys have a look at this?

Closing this issue in favor of tracking it in the azure-devops extension repo.
Please see https://github.com/Azure/azure-devops-cli-extension/issues/831 for updates.


New Rule: Fake Storage Alert

/update-test-rules

/update-test-rules

Testing looks good here!

Are we going to account for legit "Approaching SharePoint Site Storage Limit" emails? I see those surfacing in some envs.

Yeah I should probably do that. I saw a couple in but couldn't tell if they were legit or not

Testing looks good, distribution is pretty even, some overlap with brand impersonation rules, this is net new coverage primarily.


Cached string representations of number-like argument-mode arguments are lost in arrays

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
During initial argument parsing - before considering what parameters these arguments will bind to - PowerShell parses tokens that can be interpreted as numbers as numbers, but caches the original string representation via invisible [psobject] wrappers.
Unexpectedly, this behavior doesn't work for elements of an array:
# Helper script block that reflects on the arguments passed.
$sb = {
  param($Value) # implicitly [object]-typed - see below for why
  foreach ($v in $Value) {
    [pscustomobject] @{
      StringRepresentation = $v.ToString()
      OriginalStringRepresentation = $v.psobject.ToString()
      Type = $v.GetType()
      IsPSObjectWrapped = $Value -is [psobject]
    }
 }
}

# Single-argument case: cached string representation is preserved.
& $sb 042

'---'

# Array-argument case: !! cached string representation is lost.
& $sb 042, 043

Expected behavior
StringRepresentation OriginalStringRepresentation Type         IsPSObjectWrapped
-------------------- ---------------------------- ----         -----------------
42                   042                          System.Int32              True
---
42                   042                          System.Int32              True
43                   043                          System.Int32              True

Actual behavior
StringRepresentation OriginalStringRepresentation Type         IsPSObjectWrapped
-------------------- ---------------------------- ----         -----------------
42                   042                          System.Int32              True
---
42                   42                           System.Int32             False
43                   43                           System.Int32             False

That is, adding a second argument resulted in the loss of the original string representations (042 and 043)
Also note that if you [object[]]-type the parameter, the cached string representation is lost even in the single-argument case, which is arguably a separate bug.
Error details
No response
Environment data
PowerShell 7.4.0

Visuals
No response

This issue is a real problem. I have a function which get user information based on their mobile number.
function Get-UserInformation {
    param(
        [ValidatePattern('^(\+33|0)[67]\d{8}$')]
        [string[]]$PhoneNumber
    )
    # ...
}

Having the leading zero trimmed with 2+ phone numbers makes the [ValidatePattern()] fail and if I remove it, the function no longer works as the phone number are no found in the base.
FWIW, in the dark ages of PSv2, this function worked like a charm without trimming leading zeros.


Revert "Upgrade go to 1.22 (#585)"

This reverts commit 53adfeed13af6121f11d8758914c0d7899654a90.

#634  👈
feature/proof-of-stake

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

Join @lazynina and the rest of your teammates on  Graphite


"feat: added rajiv gandhi technical institute, Bhopal"

Kindly review and approve the same.

@NeeleshJaiswal Pull request merged. Thank you!


proposal: cmd/vet: report len usage with strings

I have more than once seen unexpected behaviour, mostly related to string validation, caused by the len built-in function returning the count of bytes in the string, rather than the number of runes. For example:
func validate(name string) error {
	if len(name) > 64 {
		return errors.New("name cannot be longer than 64 characters")
	}
	return nil
}

In my experience, the author of code similar to the above is nearly always looking to get the number of runes in the string - not the bytes needed to represent when encoded as UTF-8. Of course, the code above is fully legal and therefore this often unexpected behavior does not surface until runtime.
I believe a go vet check that warns about using len in combination with a string argument would be valuable - especially to programmers that are learning Go.

How would you measure the size of a string if every use of len with string is flagged?
I think there's no way this will reach the accuracy bar needed for a cmd/vet check.

@seankhliao By casting to []byte first before passing to len

@seankhliao Thanks for correcting the title of the issue.
To answer your question regarding measuring the size of a string s: len([]byte(s)) would work.

vet checks are for things which are probably wrong, at the very least, and which wouldn't be the correct and idiomatic way to do a thing. I think that the behavior of len(s) is reasonably clear and usually correct.
I've only been using go for a few years but I don't think I've ever yet actually wanted to measure a string's length in runes.

Have you looked at how much code this would mark as invalid for a very marginal benefit?

I think this fails the 3rd criterion for new vet checks:

Precision:
Most of vet's checks are heuristic and can generate both false positives (flagging
correct programs) and false negatives (not flagging incorrect ones). The rate of
both these failures must be very small.

Just skimming over e.g. the strings package in the standard library I saw dozens of completely correct len(string) calls that would be flagged by this vet check.

Consider:

comparisons against 0: len(s) > 0
comparisons against other lengths: len(s) < len(t)
comparisons against a variable:len(s) != n

All of these are widely used and correct usages of len on string. Take a look at the correctness criteria for "cmd/vet" https://github.com/golang/go/blob/master/src/cmd/vet/README . I do not see a path forward without making the proposed check narrower than len(s) where s is an expression of underlying type "string".

This is impractical because getting the length of bytes is the most common use case and such change would break backward compatibility with all existing Go code to date.
If you believe something should be done about this, my suggestion to you is to open a proposal for adding to the len() documentation a note explaining that utf8.RuneCountInString can be used if you want to count runes in a string.


Basic multi-cloud support

Changed "white" to "cloud1" where appropriate for clarity
QDR configured for entire collectd/* prefix as multicast

Included change in infrared deployment template as well
Eventually this will be default, see https://review.opendev.org/#/c/678961/

Templated smoketest job and collectd
Smoketest now handles its own smart gateways

Instantiates one smart gateway and one collectd per "cloud"

Each test pod checks for only it's own messages

Also ensures they come from the right smart gateway

Documentation is nearly complete, will follow up with it soon.
Testing
I ran this with up to 4 simulated clouds (./smoketest.sh 4) and it worked each time. I confirmed from the test pod logs and by manually exploring in prometheus that each pod successfully delivered messages though the correct smart gateway.
During testing I did see test pods fail (though with the retries they still succeeded within the timeout and passed the test). I investigated the failed pods and found that they delivered messages to the smart gateway and it processed them, but sometimes the prometheus ServiceMonitor is slow to add new targets, so they are not always scraped soon enough to pass the test. This was the cause of the retries, and once the target gets added to Prometheus, one of the pods would pass. I briefly explored trying to wait on the targets to appear but got a permission error from the prometheus API trying to query targets and did not sink any more time into it.

 Test multiple IR-based OpenStack clouds connecting to a single QuickLab instance


[SPARK-28198][PYTHON][FOLLOW-UP] Run the tests of MAP ITER UDF in Jenkins

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/24997 missed to add pyspark.sql.tests.test_pandas_udf_iter to modules.py. This PR adds it.
Why are the changes needed?
Currently, Jenkins does not run the test cases. We should run them.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Jenkins should test.

Test build #116331 has started for PR 27141 at commit b1e4f01.

Merged build finished. Test PASSed.

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

Test build #116331 has finished for PR 27141 at commit b1e4f01.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Merging it - I am 100% sure this change is correct and tests passed.

Merged to master.


Certificate generation without extensions

Using the supplied command to create the debug certificate causes the app to receive the following error:
javax.net.ssl.SSLPeerUnverifiedException: Hostname localhost not verified:
       certificate: sha1/xPOGU6cVKsoJj0fEGu9lCgoSZU8=
       DN: CN=localhost,O=Debug Cert,C=US
        subjectAltNames: []
javax.net.ssl.SSLPeerUnverifiedException: Hostname localhost not verified:
        certificate: sha1/xPOGU6cVKsoJj0fEGu9lCgoSZU8=
        DN: CN=localhost,O=Debug Cert,C=US
        subjectAltNames: []

This is probably caused by a missing configuration of the v3 extension section.
I've found a possible solution to the issue using the following command to generate the certificate:
openssl req -x509 -new -nodes -days 100 -key root-ca-privkey.pem -out root-ca.cert.pem -subj "/C=US/O=Debug certificate/CN=localhost" -extensions v3_ca -config openssl_config.txt

You can find the file openssl_config.txt here.
I hope this helps.

Someone update the codelab instructions please.

Thank you for the report and input. Text has been updated.


add new layout for wallet selector

closes #145
closes #162

This part of the design is yet to be implemented. Also, Clicking the add wallet button should auto-fill some required details like selecting the asset own the clicked btn Or we can just have one add wallet btn below the cards?

more

Transactions would now be part of the general tabs, that is after overview, so this design doesn't stand anymore
Oh yes, good catch, I'd make it select the wallet based on the button clicked

The app UI not match with figma, I think indicator should on the right and and expand the display range

USD value not show on wallet group

The app UI not match with figma, I think indicator should on the right and and expand the display range

USD value not show on wallet group

what figma page are you looking at, below is the correct figma design in the desktop page on figma

balances do not show up on testnet, the reason it shows the total usd balance is due to this recently merged PR https://github.com/crypto-power/cryptopower/pull/177


Run scripts for multiple selected packages

Stack:

#508
#506
#502
#500 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #508


Seams / Dividers

Consider adding seams / dividers between the cards.

See http://www.google.com/design/spec/components/dividers.html


[SP-3358] - Backport of PDI-13148 - NPE in Slave Server Monitor Tab (…

…6.1 Suite)
@pamval, @mbatchelor, here is backport of  https://github.com/pentaho/pentaho-kettle/commit/756033cb97db5ca04cb3d93f6faf8024ca741eec to 6.1. Thanks.

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  ui/src/org/pentaho/di/ui/spoon/SpoonSlave.java


doc: Update release notes for issues closed in this release

This list was created by what issues where closed from Sept 7th and everything tagged with either a 1.10 milestone or no milestone at all.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Also this is just the issues closed, not the PRs.


Unexpected termination status: 64

Hi,
I'm experiencing issues when using the latest versions of Tartlet (0.4) and Tart (1.7.0) together. Specifically, when I click "Start," the virtual machines don't start. In the logs, I see the following information:
2023-06-29T13:07:58Z [VirtualMachineFleetLive] [Info] Start virtual machine named macos-ventura-xcode:14.3.1-1
2023-06-29T13:07:58Z [EphemeralTartVirtualMachine] [Info] Clone Tart image named macos-ventura-xcode:14.3.1 to macos-ventura-xcode:14.3.1-1...
2023-06-29T13:07:58Z [EphemeralTartVirtualMachine] [Info] Run Tart image named macos-ventura-xcode:14.3.1-1...
2023-06-29T13:07:58Z [VirtualMachineFleetLive] [Info] Virtual machine named macos-ventura-xcode:14.3.1-1 stopped with message: Unexpected termination status: 64

However, if I manually start the virtual machine through the "Edit Virtual Machine" option, it starts as expected.

I found the following logs in the systemlogs:
error	22:25:07.137901+0200	Tartelet	Failed making ephemeral virtual machine as resources could not be created: cancelled
error	22:25:07.138052+0200	Tartelet	Could not create virtual machine named ventura-xcode:14.3.1-1: cancelled

@stmitt Are you seeing this issue with Tart 1.7.0 specifically? I just tested with the newest version of Tart, as of writing this that is 1.9.1, and that seems to work fine.

@simonbs yes i'm still seeing this issue with Tart 1.9.1. Specifically when using this image: https://github.com/cirruslabs/macos-image-templates/pkgs/container/macos-ventura-xcode/101275224?tag=14.3.1

@stmitt Do you know if the issue occurs when using other images too?

@simonbs I was able to create a image following the tartelet instruction which works. Do the cirruslabs images work with your setup?

@stmitt I have not tested with CirrusLabs' images. I can't see why they shouldn't work though.

I found out what the issue in my setup was:
I named the cloned image "macos-ventura-xcode_14.3.1". Since the colon is used as a separator in the tart run command, the command is failing. Therefore, I propose to replace all colons in the directory with underscores. I created a PR that does that: https://github.com/shapehq/tartelet/pull/43

Closing this as #43 is merged.
Thanks for looking into the issue and providing a fix! 🙏


App is allowing operations even when ledger is locked?

Hi
I recently started using the app. It's great.
However i noticed one security issue that is concerning.
Once i open the app and let it idle for a while so ledger enters system wide PIN lock mode (willl request to reenter ledger pin again), the app is still running in background and allowing all kind of operations.
The PGP app does not respect the fact that ledger is "locked" and the fact that ledger is demanding pin re-entry after system defined timeout period. You can perform all kind of operations once ledger enters timed-out PIN lock. The only protection against this is using UIF for now that requests you to confirm operation (and you won't be able to confirm unless you enter PIN).
Shouldn't the PGP app respect the fact that ledger is somehow "locked" ?
In BTC app it will not allow access to the keys and operations once ledger got locked.
Reproduction:

Set ledger system wide timeout for pin lock to 2 minutes
Open PGP app
Wait until ledger locks the screen and demands pin
You can still perform all operations with PGP app, even when the screen is locked.

Fix seems to be easy, just adding line of code that checks if ledger is in this pin-lock mode and refuse to do any kind of operations until it's unlocked.

Hello,
App has been reforaced in v2.0.0. It is still in develop branch, not yet merged on master, neither deployed on Ledger Live.
I am not able to reproduce your issue: once the device is locked, I cannot send any command, and the card is no more detected. I need first to unlock my device to be able to perform any operation, and then validate again my pin.
Please double check on your side...


New release for fresco 1.0.0

Could you please make a new release of the library that uses the dependencies I updated about a month ago?

Just update fresco to latest version.  The released library doesn't care about fresco version.
dependencies {
    compile 'com.facebook.fresco:fresco:1.0.1'
    compile 'me.relex:photodraweeview:1.1.2'
}


Support for Legacy UI features like FrameSequenceTracker and PipelineReporter

The ui.perfetto.dev site doesn't appear to include support for some of the legacy UI features such as FrameSequenceTracker, PipelineReporter, or InputLatency::*. What is the plan for enabling these features in the new perfetto UI?

Can you clarify with some more detail what they are? Not even sure what you are talking about  (some of the things you mentioend can mean too many things, like InputLatency::*).
The plan is not to carry over all the features as-is. THere's a long tail of features that likely will stay only in the "open with legacy ui" path.

Expanding a bit more, there is a plan for the UI to become more modular and allow people to create extensions / plugins to deal with these long tail use cases like this.
The failure mode of the legacy ui is trying to have all the possible feature, which makes it a project impossible to run and maintain, and doomed to accumulate unmaintained code written by people who just one some feature and then run away.
We decided to start this journey (modularizing the perfetto UI) as we were slowly creeping into the "let's re-add all the legacy features" game, which would reintroduce all the problems.
Unfortunately re-architecting the UI, while being a priority for us, is also going to be a massive task and will take a while (don't have a solid estimate right now as we are just getting started, but somewhere in the 1y ballpark)

Thank you for the additional context.
InputLatency is a tracing visualization of LatencyInfo (chromium.src's ui/latency/latency_info.h) that tracks input event timings as they work through the various stages in the pipeline. They are exposed in the legacy UI under the browser process and let one quickly identify slow input event processing for further analysis. For example, I use it regularly to understand scrolling performance.
FrameSequenceTracker lets one more easily understand Chromium's ability to produce frames in response to a frame generating action such as a scroll. For example, it lets one easily see if a scroll produced only 93 of the expected 100 frames of animation along with which frames were slower or missed. This is then leveraged to dig deeper into why those specific frames were slow.
PipelineReporter lets one visualize (with timing information) the steps that a frame goes through both processes and in parallel with other frames as it moves from viz/gpu to renderer to viz/gpu before ultimately being presented on screen. This is frequently used in parallel with FrameSequenceTracker to understand why frames weren't produced at the desired rate.
The most recent comment about modularizing the UI and supporting an extension/plugin model makes a lot of sense. I'm not surprised that the legacy UI has acquired a lot of stale functionality for the reasons you mention.
Going forward, if there is a modularized UI that supports plugins/extensions in ~1y, what is the roadmap for the existing functionality that the legacy UI does provide? Is it something like:

UI modularization and extensibility system put into place in ~1y (using your ballpark estimate)
Teams are given some bound timeframe to re-write their functionality using extensibility mechanism
Legacy UI continues to be supported for that timeframe before being removed

Or is there another plan?

In my mind:

The legacy ui button won't go away from the "open as legacy ui" for a long while (even past the y)
It's going to be up to teams to create equivalent of new features once the modularization is there. I suppose that popular features like frame tracer and the like might be ported, other small ones that nobody / few people care about will only live in the legacy ui.

it really depends by how many people want that and if they are willing to contribute.

@deepanjanroy in case he has opinions

I agree with<EMAIL_ADDRESS>These features will only be available in the legacy UI until
(a) Perfetto UI is more extensible and
(b) someone is willing to write the extension.
(a) is the harder part. Once (a) is done, each individual feature likely won't be too difficult to implement.

Thank you for the additional information. Sounds good and I'll look forward to the Perfetto UI extensibility work landing!


How can I convert shap values to probability increase/decreases?

Really cool library, still trying to wrap my brain around it.
So currently, I know how to convert the base (expected) value from log odds to probability, with
odds = np.exp(explainer.expected_value)
odds / (1 + odds)

This works fine, but the problem comes when I try and convert each individual shap value to a probability increase/decrease. That formula doesn't work, so I'm wondering how I can get the percent increase/decrease that each feature contributes

Basically, what percent do each of the lengths (like the length I annotated in red on the picture) take up?

Making shap values explain in terms of probability isn't really possible (some level of approximation is required). Read the thread here: https://github.com/slundberg/shap/issues/29#issuecomment-371877433
If you so happen to be using TreeExplainer with "interventional", there's a model_output="probability" you can try.


chore(install): add host discovery info to nerstorage payloads

This PR introduces host discovery info to nerdstorage payloads during the install process.
cc @devfreddy @jbeveland27

@ctrombley this looks pretty good.
What would be good to test, and I assume I'll query nerdstorage after the install to see the discovered manifest?

@Julien4218 I added some testing criteria above.


fix: Prevent content from being restarted after Postroll ads

Fixes https://github.com/shaka-project/shaka-player/issues/4445
After watching post roll ads, this.video_.play() was called on a completed content in the onAdComplete event. The content would then restart from the beginning.
We now flag that the content is completed before we call this.adsLoader_.contentComplete(). On the callback, we prevent the video element from replaying if this flag is set.
This fix is based on the Advanced Sample on the googleads-ima-html5 repo

@gingman can you sign the CLA? Thanks!

@avelad done. The check is now green.

Thanks for your contribution!


Take over maintenance of the github-pr-resource

Hi there,
I've set up a Concourse pipeline for maintaining the github-pr-resource, leveraging the already-existing fork done by VMware in the cloudfoundry-comunity org.
With the 1.7.0 release just out, I've demonstrated I could build the resource using recent Golang and have it run on recent Alpine. The resulting released image is there: cfcommunity/github-pr-resource. With the help of pipeline templates (that I'm also maintaining), I've tailored nice Concourse pipelines that can bump deps, build, test and publish easily images for Concourse resources.
Later on with cloudfoundry-comunity/github-pr-resource, I plan to bump the dependencies further, and review and accept more pending PRs.
For now, the telia-oss repo hasn't had any new commit since February 2021. Issues & PRs have dramatically piled up there, and people have (legitimately) become bitter about that important resource not being properly maintained. Long story short, it has been inactive for enough time now, and the community should focus on some fork where the code can be submitted, tested, reviewed and accepted.
That's what I'm suggesting with the cloudfoundry-comunity fork today.
Best,
Benjamin

I don't understand why the DCO check doesn't refresh appropriately after I've properly signed my commit off. Any help appreciated!


data.txt is missing info

I don't see "grandeikk.com" under the "emailondeck.com" provider or "shbiso.com" under "temp-mail.org"
Both have been available for a few days.
Both do show up when using the api though

Thanks, this is because they have been harvested today. They will be available tomorrow at the Repo. We push every 24h to the repo but API is live.

Is there anything I can help with for harvesting? I do have a few servers
that could run some docker stuff to help if needed...
On Wed, Jun 29, 2022 at 1:14 PM 7c @.***> wrote:

Closed #19 https://github.com/7c/fakefilter/issues/19 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/7c/fakefilter/issues/19#event-6901047963, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARHYG24SPIVFASPUSQLYOLVRQOXVANCNFSM52FESA7A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Your help, in submitting issues is greatly appreciated. We do have enough resources for 300 more providers for sure.

Great, as long as they don't get blocked and have enough cross-geo variety...!