1.0 documentation review

As we are ramping up for the 1.0 release, which includes numerous changes and updates, the documentation may be out of date in some areas and missing descriptions of new features in others. The assignee for this issue would compare all of the comments and values in the example config file in next with the various documentation in next, and outline what is missing or outdated. As the ticket says, this is just a review, and not necessarily an implementation, so we are really looking to get a starting point on closing the gaps by knowing what they are, but appreciate any help with making corrections and additions to improve the documentation for 1.0 as well. We welcome all help!

Hi @jranson i would like to help with documentation for 1.0

Sounds great, thank you! Please hit me up with any questions.

Docs are all cleaned up in next


File API refactor

Purpose

Half of the previous file API was not written using the Java NIO API. The purpose of this PR is to rectify that. Fix #4386, Fix #3334, Fix #2637

Goals

Refactor the file API to make use of the Java NIO API
Add test cases for file copying and moving

Release note

Improved File API

Closing this since this has become outdated


Switching between workspaces is still slow

Changing focused workspace on the bar still takes about a second.
OS: macos Catalina 10.15.7

Hi!
As stated in #56 and #173, there isn’t a lot that can be done about that except few tweaks in settings.
Let me know if this is better after trying this.


Swap providers: finding transaction ensures correct value locked

Description
Bug: the finding of the initiate transaction does not check the value locked using the transaction. It would open potential attack vectors.
Submission Checklist :pencil:

[x] Check the value locked in the swap when finding/verifying an initiation transaction

@harshjv yea i just made up the order initially, but have stuck to it as much as i could among the swap functions. They should be largely consistent unless i've missed something


Bump pytest version.

TBR'ing this one in the hopes of some potential relief for #497

so much for that idea.


[Suggestion] - Should Bitbucket Smart Mirror have a livenessProbe?

Suggestion
I was wondering why the Helm chart does not have a option for setting up a livenessProbe for the Bitbucket Smart Mirror. There is a open port for the readinessProbe already there. Is there no need for a livenessProbe or should this be added in the future?
My other concern is about the Security Context of the Smart Mirror since it runs as the root user for the ability to change the volume permissions. Also you can't change the allowPrivilegeEscalation value either on the Values file unfortunately. I think this should be configured more securely if possible.
Product
Bitbucket
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @JSRAF thanks for suggestion. Could you elaborate more on your suggestions. It would help us prioritising this if you could provide good use cases(PRs, examples etc...).

Liveness probe has already made it to Jira. We're planning to add them to all charts.
As to the securityContext, it should be fully configurable.

So the initContainer is supposed to run as root and the main container would work if I applied the following securityContext settings to it?
securityContext:
  runAsUser: 2003
  runAsGroup: 2003
  runAsNonRoot: true
  allowPrivilegeEscalation: false
  readOnlyRootFilesystem: true
  capabilities:
    drop:
      - ALL

Running init container as root is sometimes required to fix permissions for shared home, however, that may not be required in every case. Moreover, once the permissions are fixed you may disable it and bitbucket should be able to write to shared home.
As to the main container, even though it's starting as root, all the processes are started as bitbucket user. You can definitely set a custom securityContext in values.yaml and run it as 2003 user.


Off chain FA2 token metadata tab not showing up.

I have this FA2 contract deployed on edo testnet with off_chain views for metadata. https://better-call.dev/edo2net/KT1PaRe6pHNZi8A4cNTzVZjjUMpomu7K97zK/operations
I have implemented custom view approach to the token metadata according to tzip-12. https://gitlab.com/smondet/tzip/-/blob/smondet-tzip-12-with-16/proposals/tzip-12/tzip-12.md#token-metadata-storage-access
For the above-deployed contract, it's not showing the tokens metadata tab. Incase the general approach is used it's showing the token metadata tab https://better-call.dev/delphinet/KT1PBL66suJeW2nBbWXgR9ex9gu7TFCmSgQg/storage
Does the https://better-call.dev/ platform support custom off_chain view for showing the FA2 token metadata tab?

Sorry for delay, token_metadata offchain view is not yet supported by BCD, we will add this feature in the next major release

Awesome! Is there a way by which I could check if my deployed contact off_chain views methods are working as expected for indexers & wallets read it correctly? This would be super helpful. Thanks.
Here's the contract which I would like to test https://better-call.dev/edo2net/KT1PaRe6pHNZi8A4cNTzVZjjUMpomu7K97zK/operations


test for trace command

Trace command was not working, see #178, but there was no test detecting this. Test to be added for trace command.

@tretmans I think the test for the trace command should be covered now in https://github.com/TorXakis/TorXakis/pull/259. Is only one test, but it might be enough for the time being...


Max Segment Slider Issue

The Max Segment Slider can only use mouse wheel to scroll down, can't scroll up.

Using mouse wheel can only make slider goes down (to left side shorter segment), but unable to goes up (to right longer segment).

The Elevation Step Slider is working normal, you can use mouse wheel scroll up or down.


Sidebar rendering bug

Steps to reproduce:

Open the sidebar
Open a new tab
Go back to the original tab

This has been solved


Support new package repo

After the update to 10.x, the packages are now in a new repo & use a different package name (gitlab-runner).
https://docs.gitlab.com/runner/install/linux-repository.html#installing-the-runner

Merged and released as v1.15.2. Thanks!


Add fullscreen-view switch to demo-snippet

Adds a d2l-switch to demo snippets that have the fullscreen attribute to enable a more truly full-screen experience.

There appears to be 6 repos using the existing fullscreen.
I used this regex to search for instances: /d2l-demo-snippet[a-zA-Z0-9${}\[\]"-=\s]+?fullscreen/
(Github didnt like [^>])

BrightspaceUI/core
Brightspace/d2l-rubric
BrightspaceUILabs/navigation
Brightspace/discovery-fra
Brightspace/unified-content-experience
~Brightspace/blog.d2l.dev~ Likely don't want to change this
Brightspace/nova

All repos above use core >2.50 or ^2

I think this is looking pretty good. Just a minor question about the noScroll property. Not sure about the floating buttons visual-diffs... seems flakey.

Yeah, I don't know why they (and only they) would change some antialiasing.


Str class not found

Can someone fix this error?
Class "Winter\Storm\Support\Facades\Str" not found
In the update of WinterCMS v1.0.2 Winter\Storm\Support\Facades\Str facade has been removed and you can use Winter\Storm\Support\Str directly instead.
https://wintercms.com/releases/v1.2.0

Any progress with this issue ? has this plugin become obsolete ? Thanks


Add server support for chroma

Before this PR can be merged it needs:

[x] https://github.com/protectai/rebuff/pull/63 to be merged
[ ] Merge a minimal test case for chromadb Rebuff SDK instantiation
[ ] NPM release of rebuff
[ ] Update server/package*

@ristomcgehee I'll publish 0.1.0 once we have a minimal test for chromadb SDK instantiation and querying. If you'd like to PR that lmk

@ristomcgehee I'll publish 0.1.0 once we have a minimal test for chromadb SDK instantiation and querying. If you'd like to PR that lmk

@seanpmorgan Yeah, I can make a PR for that. I'll be traveling for work all next week, so it might be a couple weeks till I get to it if that's all right. Since Chroma doesn't have a hosted version, should we spin up a Chroma server before running the tests, maybe with Docker Compose?

0.1.0 published:
https://www.npmjs.com/package/rebuff

@seanpmorgan ready to be reviewed/merged


Remove hard-coded address-book route

Drop hard-coded routes in SPA that can are driven by content page labels.
Remove hard-coded routes

address-book
update-password
update-email
payment-details
update-profile
forgot-password
reset-password

Add AuthGuard

address-book component
update-password component
update-email component
payment-method component
update-profile
forgot-password
reset-password

Remove semantic routes for pages that are only driven by CMS.
Update sample data for pages that have not yet the /my-account/ prefix in the label

PR for sampledata is here: https://stash.hybris.com/projects/C3PO/repos/spacceleratorsamplesaddon/pull-requests/46/overview

e2e is most likely blocked till we install new sample data.

tested all pages with /my-account/
when logged in:

address-book (/)
update-password
update-email
payment-details
update-profile
forgot-password > oops (correct)
reset-password > oops (correct)

there's the 'not authorized to perform this action' for payment details, known issue.


[Improvement] Drop flink 1.14 version

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
After the Flink 1.17 release, we can drop the support of the 1.14 version.
How should we improve?
No response
Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

As per discussion, Kyuubi suppose to support the latest 3 feature versions of Flink, let's do it when the support for Flink 1.17 is ready (at least the PR in a good shape)

I think it's time to drop Flink 1.14 in master, @a49a do you have time to send PR?


Issue with Nginx Proxy and APIM 3.1.0

I'm facing a problem with apim and nginx when I'm using a custom path. I can't log in in carbon, when I try access via: https://mynginx/wso2am/carbon. I already have configured proxy_context_path, but the issue remains. It seems a problem with token CSRF.
That's the error

When I try to log in

That's my deployment.file
[transport.https.properties]

proxyPort = 443

 [server]
 hostname = "api.am.wso2.com"
 proxy_context_path = "/wso2am"
node_ip = "localhost"
#offset=0
mode = "single" #single or ha

base_path = "${carbon.protocol}://${carbon.host}:${carbon.management.port}"
#discard_empty_caches = false
server_role = "default"

[super_admin]
username = "admin"
password = "admin"
create_admin_account = true

[user_store]
type = "database_unique_id"

[database.apim_db]
type = "h2"
url = "jdbc:h2:./repository/database/WSO2AM_DB;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE"
username = "wso2carbon"
password = "wso2carbon"

[database.shared_db]
type = "h2"
url = "jdbc:h2:./repository/database/WSO2SHARED_DB;DB_CLOSE_ON_EXIT=FALSE"
username = "wso2carbon"
password = "wso2carbon"

[keystore.tls]
file_name =  "wso2carbon.jks"
type =  "JKS"
password =  "wso2carbon"
alias =  "wso2carbon"
key_password =  "wso2carbon"

#[keystore.primary]
#file_name =  "wso2carbon.jks"
#type =  "JKS"
#password =  "wso2carbon"
#alias =  "wso2carbon"
#key_password =  "wso2carbon"

#[keystore.internal]file_name =  "wso2carbon.jks"
#type =  "JKS"
#password =  "wso2carbon"
#alias =  "wso2carbon"
#key_password =  "wso2carbon"

[[apim.gateway.environment]]
name = "Production and Sandbox"
type = "hybrid"
display_in_api_console = true
description = "This is a hybrid gateway that handles both production and sandbox token traffic."
show_as_token_endpoint_url = true
service_url = "https://api.am.wso2.com:${mgt.transport.https.port}/services/"
username= "${admin.username}"
password= "${admin.password}"
ws_endpoint = "ws://api.am.wso2.com:9099"
wss_endpoint = "wss://api.am.wso2.com:8099"
http_endpoint = "http://api.am.wso2.com:${http.nio.port}"
https_endpoint = "https://api.am.wso2.com:${https.nio.port}"

#[apim.cache.gateway_token]
#enable = true
#expiry_time = "900s"

#[apim.cache.resource]
#enable = true
#expiry_time = "900s"

#[apim.cache.km_token]
#enable = false
#expiry_time = "15m"

#[apim.cache.recent_apis]
#enable = false

#[apim.cache.scopes]
#enable = true

#[apim.cache.publisher_roles]
#enable = true

#[apim.cache.jwt_claim]
#enable = true
#expiry_time = "15m"

#[apim.cache.tags]
#expiry_time = "2m"

And nginx configurations:
upstream sslapi.am.wso2.com {
    server localhost:9443;
}

upstream sslgw.am.wso2.com {
    server localhost:8243;
}

server {
    listen 80;
    server_name api.am.wso2.com;
    rewrite ^/(.*) https://api.am.wso2.com/$1 permanent;

}
server {
    listen 443 ssl;
    server_name api.am.wso2.com;
    proxy_set_header X-Forwarded-Port 443;
    ssl_session_timeout  5m;
    ssl_protocols SSLv2 SSLv3 TLSv1;
    ssl_ciphers  HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers   on;
    ssl_certificate /home/rfurtad/wso2.crt;
    ssl_certificate_key /home/rfurtad/wso2.key;

    location /wso2am {
        proxy_pass https://sslapi.am.wso2.com;
        proxy_set_header   Host                $host;
        proxy_set_header   X-Real-IP           $remote_addr;
        proxy_set_header   X-Forwarded-Host    $host;
        proxy_ssl_verify   off;
        proxy_set_header   X-Forwarded-For     $proxy_add_x_forwarded_for;
    }

    location /wso2am/carbon {
            proxy_pass https://sslapi.am.wso2.com/carbon;
    }
}
server {
    listen 443;
    server_name gw.am.wso2.com;
    proxy_set_header X-Forwarded-Port 443;
    ssl on;
    ssl_certificate /home/rfurtad/wso2.crt;
    ssl_certificate_key /home/rfurtad/wso2.key;
    location /wso2am {
            proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Server $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Host $http_host;
            proxy_read_timeout 5m;
            proxy_send_timeout 5m;
            proxy_pass https://sslgw.am.wso2.com;

        }

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;
}

What am I missing? I'm running apim on docker.

Hi @rfurtad ,
Better to use forums like stack overflow, slack or dev mailing lists to ask questions as there are more community participation over there. Better to keep the git issues for bug report and feature requests.
Also this seems to be related to product https://github.com/wso2/product-apim, if you insists on crating a git issue as this is not related to Product Identity Server.
I am closing this issue.


Install from NixOS channel

Strange that I have to install lorri with nix-env instead of just tossing it in my configuration file as environment.systemPackages = [ lorri ];. Is there going to be an upstream package in the future?
I tried making my own like this:
{ config, pkgs, ... }:

let
  lorri = pkgs.stdenv.mkDerivation rec {
    pname = "lorri";
    version = "rolling-release";
    src = pkgs.fetchFromGitHub {
      owner = "target";
      repo = "lorri";
      rev = "094a903d19eb652a79ad6e7db6ad1ee9ad78d26c";
      sha256 = "11i4kbwclwyvznyd9q69fq36fjasvs72ziz0555hl3fjbbq0n72q";
    };
  };
in
{
  environment.systemPackages = [ lorri ];
}

But it failed like this:
shkhgcxs3aljqz771rilj8c-nixpkgs-18.09.2436.395a543f360/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:177:11:
while evaluating the attribute 'system.activationScripts.script' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/nixos/modules/system/activation/activation-script.nix:67:9:
while evaluating 'textClosureMap' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/strings-with-deps.nix:70:35, called from /nix/var/nix/profiles/per-user/root/channels/nixpkgs/nixos/modules/system/activation/activation-script.nix:88:18:
while evaluating 'id' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/trivial.nix:14:5, called from undefined position:
while evaluating the attribute 'text' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/nixos/modules/system/activation/activation-script.nix:9:5:
while evaluating the attribute 'text' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/strings-with-deps.nix:77:38:
while evaluating the attribute 'sources' of the derivation 'etc' at /nix/store/yn6df0qzkshkhgcxs3aljqz771rilj8c-nixpkgs-18.09.2436.395a543f360/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:177:11:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/nixos/modules/system/etc/etc.nix:20:20, called from undefined position:
while evaluating the attribute 'source' at undefined position:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/modules.nix:75:45, called from undefined position:
while evaluating the attribute 'value' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/modules.nix:336:9:
while evaluating the option `environment.etc.crontab.source':
while evaluating the attribute 'mergedValue' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/modules.nix:369:5:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/modules.nix:369:32, called from /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/modules.nix:369:19:
while evaluating 'check' at /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/types.nix:240:15, called from /nix/var/nix/profiles/per-user/root/channels/nixpkgs/lib/modules.nix:370:10:
while evaluating the attribute 'allFiles' of the derivation 'crontabs' at /nix/store/yn6df0qzkshkhgcxs3aljqz771rilj8c-nixpkgs-18.09.2436.395a543f360/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:177:11:
while evaluating the attribute 'text' of the derivation 'system-crontab' at /nix/store/yn6df0qzkshkhgcxs3aljqz771rilj8c-nixpkgs-18.09.2436.395a543f360/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:177:11:
while evaluating the attribute 'passAsFile' of the derivation 'system-path' at /nix/store/yn6df0qzkshkhgcxs3aljqz771rilj8c-nixpkgs-18.09.2436.395a543f360/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:177:11:
illegal name: '.drv'

I installed it with home-manager with the following overlay
  nixpkgs.overlays = [
    (self: super: {
      lorri =
        let src =
          (pkgs.fetchFromGitHub {
            owner = "target";
            repo = "lorri";
            rev = "e943fa403234f1a5e403b6fdc112e79abc1e29ba";
            sha256 = "1ar7clza117qdzldld9qzg4q0wr3g20zxrnd1s51cg6gxwlpg7fa";
          });
        in pkgs.callPackage src { inherit src; };
      })
  ];

For now we are on a rolling-release schedule via lorri self-upgrade, which is a small wrapper around nix-env (see https://github.com/target/lorri#upgrading). We’ll migrate to semver (and push it to nixpkgs) once we stabilize the interface and functionality, but we want to be able to make fast iterations for now.

@sveitser Your solution looks good! But after I home-manager switch no lorri executable appears. How do I get home-manager to recognize the overlay?

@matthew-piziak I thought overlays put into ~/.config/nixpkgs/overlays would be applied automatically but that doesn't seem to be the case.
I think this should work in configuration.nix or  home.nix.
nixpkgs.overlays = [
  (import ./path/to/lorri.nix)
];

Aw, I tried that too, with a fully qualified path as well. No dice. :cry: :confused:

Hmm. Did you add lorri to home.packages ?

Yeah, I added pkgs = import <nixpkgs> and home.packages = [ pkgs.lorri ];

What if you apply the overlay in configuration.nix and add  lorri to environment.systemPackages ?
I'm using this
https://github.com/sveitser/nixconfig/blob/master/pc-common.nix#L20
https://github.com/sveitser/nixconfig/blob/master/home-nixpkgs/home.nix#L26
https://github.com/sveitser/nixpkgs-overlays/blob/71fd604a7ed4bb0c0f260c1fa6d3dd7f73e17ab1/lorri.nix

That did it! Yes! Thank you for bearing with me. :)
Now it's failing with a cargo error, but that's something I can take look into myself. I'm just happy my configuration is picking it up.

The following should work:
  lorri-src = builtins.fetchGit { url = https://github.com/target/lorri.git; rev = "8224dfb57e508ec87d38a4ce7b9ce27bbf7c2a81"; };
  lorri = import lorri-src { src = lorri-src; };
in ...

(if you don't pass src, it will try to clone from the git-less fetch result and fail)
You could also try to pass pkgs to reduce closure size, but then you probably have to override cargoSha256 as well.


Does text-generation-inference support macOS M1/M2(mps)?

Feature request
Screenshot from the documentation:

But I found it can't be built on macOS, and even if I modified the Makefile of the text-generation-server project and built it, it couldn't run successfully. I got an error; it seems that CUDA is a must:

Motivation
Run on macOS locally.
Your contribution
N/A

cc @Narsil I can't transfer to text-generation-inference.


Releasing pod vm binaries as part of release artifacts

A peer pod VM image (qcow2, AWS AMI or Azure VM image etc) needs the following:
Binaries:

kata-agent (src: https://github.com/kata-containers/kata-containers/tree/CCv0/src/agent )
agent-protocol-forwarder (src: https://github.com/confidential-containers/cloud-api-adaptor/tree/staging )
attestation-agent (src: https://github.com/confidential-containers/attestation-agent )
pause-image

Configs

systemd configuration files for kata-agent and agent-protocol-forwarder (src: https://github.com/confidential-containers/cloud-api-adaptor/tree/staging/podvm/files )

We do provide podvm_builder image with the tools and code to help with pod VM qcow2 creation. Currently we do not provide any such image to help with creation provider native images (eg. AMI).
Further, building all the required binaries is an extremely time consuming task. We need to better so that the process of pod VM image creation is simpler, repeatable and faster.
Sharing an initial proposal with an opinionated containerised workflow:

Provide container image with binaries and configs required for Pod VM image - kata-agent, agent-protocol-forwarder, attestation-agent,  pause image etc. This can be made available for every release (alpha, pre-release, tagged version etc)
Provide Dockerfile to consume podvm_builder and the above container image to create either qcow2 or cloud-provider native images. This should make it possible to create custom pod VM images by either cluster admin or users with the only requirement of having either docker or podman setup.
Provide K8s manifest (eg a job yaml) to use an existing K8s cluster itself to create the required Pod VM image.

From an implementation standpoint we can augment the existing github-action workflows to add support for item-1. For Item-2 we can reuse the podvm Dockerfiles as examples. Item-3 will be completely new work and might take some time to come up with a working manifest file.
Let's use this issue to brainstorm ways to improve the pod VM creation experience for cluster admins.

cc @stevenhorsman @surajssd @snir911 @huoqifeng @wainersm and anyone else interested in this aspect of peer-pods, ptal and share your thoughts.


TEN-82 added Enrol-current-user view

To test the page locally use the gg-stub (http://localhost:9949/auth-login-stub/gg-sign-in) and in the redirectUrl put "http://localhost:7750/tax-enrolment-assignment-frontend/enrol-pt/enrol-current-user-id". This will then present the page for a fixed user that has SA on another account

Ooh minor aside, can you up our coverage threshold with this ticket since it's still at 77% but we are actually at 85% coverage. Also, up the minor dependencies:
uk.gov.hmrc:http-caching-client              : 9.5.0-play-28           -> 9.6.0-play-28
uk.gov.hmrc:play-frontend-hmrc             : 3.4.0-play-28           -> 3.5.0-play-28

updated


fix: use HELMFILE_TEMPLATE_FLAGS in 'helmfile template'

the contents of https://github.com/jenkins-x/jx3-versions/blob/62fc4d6bff12a1c4bacfc87f6291d102fda5ef35/src/Makefile.mk#L62-L69 leads users to believe that they are able to configure additional helmfile template flags via the HELMFILE_TEMPLATE_FLAGS env var. this feature seems to have been lost in translation in this PR. according to slack records, there doesn't seem to be any explicit reason this was disabled
i personally have a use case of adding the flag --skip-tests to disable some noisy helm chart test pods rendered by helmfile template. ref https://github.com/jenkins-x-plugins/jx-gitops/pull/885

/ok-to-test

/retest
i guess


(FLK-E713) Test for membership should be 'not in'

Description
Tests for membership should use the form x not in the_list rather than not x in the_list. The former example is simply more readable.
Occurrences
There is 1 occurrence of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/robotichead/NearBeach/issue/FLK-E713/occurrences/

assign this to me

Thank you :) I will close this issue


It`s possible is use as video interpolation x2 fps to anime

Is it possible to use it in the mode of generating only one fps. What would x2 do to fps anime?

Is it possible to use it in the mode of generating only one fps. What would x2 do to fps anime?

For simple frame interpolation use Rife.
https://github.com/styler00dollar/Colab-RIFE


docs: new style guide - Inclusive language

Let's finally get around to creating, designing, and incorporating an AsyncAPI Style Guide!
Why the need?
In tech jobs, we often focus on our technology's technical aspects, such as functionality and performance. However, the documentation for our technology is equally important to the code itself. A style guide ensures consistency and clarity, establishes a consistent voice and tone in your documentation, makes it easier for multiple writers to work together on a single doc, and helps ensure documentation is accurate and up-to-date. When all of your technical writers follow the same guidelines, it's easier for readers to find the information they need and understand how to use your product or OSS technology.
What section of the AsyncAPI Style Guide is this issue for?

Inclusive language: Inclusive language enables everyone in your organization to feel valued, respected, and able to contribute their talents.

Some examples:

main v.s. master
allowlist/denylist v.s. whitelist/blacklist
placeholder data v.s. dummy data
gender-neutral (EX: they/them v.s. he/him)

Where should this go?
Let's create a new .md file for only the Inclusive language section of the new AsyncAPI Style Guide.
Create the following directory and place your file there: asyncapi.com/docs/community/styleguide/inclusive-language.md.
Extra Resources

Write the Docs: Style Guides
Gatsby Style Guide
Gatsby Docs Structure & Documentation Types
Mozilla Style Guide
Google Style Guide
Microsoft Style Guide

We're giving this one to @BhaswatiRoy  ✨✨

Hello @alequetzalli
Do we need to create a "community" folder under this directory and then add "styleguide" within it?
https://github.com/asyncapi/website/tree/master/pages/docs

for now yeah! we have decide differently later on the folder but for now that is the plan :D

Thanks, @alequetzalli
I have submitted the pr.

it's being worked on

Hey there @BhaswatiRoy, are you saying that you're adding more to this PR? (wanted to make sure I understood your comment) 😄
Either way, I am going to make another editorial round on it this week again :)

Hey there @BhaswatiRoy, are you saying that you're adding more to this PR? (wanted to make sure I understood your comment) 😄
Either way, I am going to make another editorial round on it this week again :)

hello, I commented so that the bot doesn't mark it as closed :sweat_smile:

ooh! ha! I get it now 😂 @BhaswatiRoy

Just reviewed the PR resolving the issue In context, Issue will be closed soon once the PR is merged.

Still relevant

Waiting for @quetzalliwrites approval and to merge. Will mark this as complete and close once the PR gets merged soon.


Update extractor and importer dependencies

What
This pr updates the search-data-importer and search-data-extractor dependencies
How to review
Please check if the changes make sense
Who can review
Anyone except me

It looks good but I think it might be worth upgrading the go version to 1.18

yes but if we upgrade to go1.18, then linter needs to be uodated as well just to be consistent, if that is so we will have lots of lint failures. So it would be better if we can introduce this in a separate pr.


Failure to specify a TLD results in an invalid suggestion

Entry of certain invalid content results in the suggestion of domains such as "@com", "@edu", etc.
This seems to include many entries where a top-level domain is not specified.  For example, entering "a@b" suggests "a@com"; entering "a@ad" suggests "a@edu", etc.
Certain items are caught, such as "@ao", which suggests<EMAIL_ADDRESS>

Already fixed. Use domains, secondLevelDomains and topLevelDomains.


Migrate Pipeline off Retail Pools

For internal security reasons it is needed to migrate to internal machine host pool.
Deadline is 8th of March 2022.
(UPD: view Email with detailed explanation)

Thanks, @adrianhall! Closing


Setup weekly infrastructure call

I think that we have reached a point where we should perhaps split out the infrastructure call into a separate call and then just 1 person needs to report back to the Thursday call. Thoughts @AdoptOpenJDK/infrastructure

I'd second that

Does anyone have any preference as to time? Wednesdays would work well for me and would mean that we could remember what to report back for the call on Thursday?? What times work best for everyone in @AdoptOpenJDK/infrastructure ??

Wednesdays are my busiest days for meetings, though Tuesdays and Thursdays get quite busy simetimes too. Not sure if people like Mondays or Fridays because they tend to get swept into long weekends and they're when public holidays tend to occur. I was going to suggest Thursdays, but f that's when the "main" meeting is, maybe that's not such a good idea. Tuesday afternoons (UK time)?

Tuesday afternoons are best for me as well

@bblondin how do Tuesday afternoons work for you?

@gdams I will assume you mean morning for me :)
I only have one meeting on Tuesday form 12:00-2pm EST

I have created https://calendar.google.com/event?action=TEMPLATE&tmeid=NDh0ZGxsdm9saXE0dmtuNnBjMTA4bTVkZXJfMjAxODAxMzBUMTUwMDAwWiBhZG9wdG9wZW5qZGtAbQ&tmsrc=adoptopenjdk%40gmail.com&scp=ALL. Please let me know if this works for everyone

That works for me

It works for me too.

Good for me too

Closing, We will see if everyone is able to attend the call tomorrow


Regression v11.1.0 -> v11.2.0

Basic info:

Node.js version: v6.11.2
jsdom version: v11.2.0

Minimal reproduction case
git clone git@github.com:callemall/material-ui.git
cd material-ui
git checkout a1a17995202db7f669451ad41690fc5e126a770c
yarn
yarn test:unit

or even better: https://github.com/callemall/material-ui/commit/a1a17995202db7f669451ad41690fc5e126a770c

Error: Uncaught [TypeError: Illegal invocation]
at reportException (/tmp/material-ui/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:63:24)
at invokeEventListeners (/tmp/material-ui/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:211:9)
at HTMLLIElementImpl._dispatch (/tmp/material-ui/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:111:7)
at Object.exports.fireFocusEventWithTargetAdjustment (/tmp/material-ui/node_modules/jsdom/lib/jsdom/living/helpers/focusing.js:73:10)
at HTMLLIElementImpl.focus (/tmp/material-ui/node_modules/jsdom/lib/jsdom/living/nodes/HTMLElement-impl.js:65:14)
at HTMLLIElement.focus (/tmp/material-ui/node_modules/jsdom/lib/jsdom/living/generated/HTMLElement.js:49:21)
at Object.Menu._this.handleEnter [as onEnter] (/tmp/material-ui/src/Menu/Menu.js:113:27)
at Object.Popover._this.handleEnter [as onEnter] (/tmp/material-ui/src/internal/Popover.js:228:18)
at Object.Grow._this.handleEnter [as onEnter] (/tmp/material-ui/src/transitions/Grow.js:81:18)
at Transition.performEnter (/tmp/material-ui/src/internal/Transition.js:235:15)
at Transition.componentDidMount (/tmp/material-ui/src/internal/Transition.js:167:12)

How does similar code behave in browsers?
It's working on IE11, Firefox 45, Safari 10.1, Edge 14, Chrome 49, jsdom v11.1.0 but fails with jsdom v11.2.0.

This didn't follow the definition of minimal reproduction case and the example in the issue template---especially the part about no third-party libraries. Let me close this until that can be fixed. Please ping this thread when the OP is updated with such an example.

the example in the issue template---especially the part about no third-party libraries

Sorry, I have missed that part.

Please ping this thread when the OP is updated with such an example.

We will stay on v11.1.0 for now. I believe I would need to understand the internal of jsdom post a minimal reproduction example. Let's wait and see if we are the only one affected.

I had the same issue on v11.2.0, using v11.1.0 it still works. Accessing the view property of a UI event triggers the error.
The issue surfaced when we triggered a focus event on an element while also using jQuery. jQuery adds the focusin and focusout events, in which it tries to access the properties of the original focus event.
It can be reproduced via:
const jsdom = require("jsdom");
const JSDOM = jsdom.JSDOM;

var dom = new JSDOM('', {
    contentType: "text/html"
});

var document = dom.window.document;

var testInput = document.createElement("INPUT");
document.body.appendChild(testInput);
testInput.addEventListener('focus', function(e) {
    console.log(e['currentTarget']); // outputs "HTMLInputElement {}"
    console.log(e['altKey']); // outputs "undefined"
    console.log(e['view']); // triggers the "Illegal invocation" error
});
testInput.focus();

The following error is triggered:
TypeError: Illegal invocation
    at FocusEvent.get [as view] (/projects/bar/node_modules/jsdom/lib/jsdom/living/generated/UIEvent.js:83:13)
    at HTMLInputElement.<anonymous> (/projects/bar/tests/ThirdParty/jsdom-focus-test.js:15:18)
    at invokeEventListeners (/projects/bar/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:195:27)
    at HTMLInputElementImpl._dispatch (/projects/bar/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:119:9)
    at Object.exports.fireFocusEventWithTargetAdjustment (/projects/bar/node_modules/jsdom/lib/jsdom/living/helpers/focusing.js:73:10)
    at HTMLInputElementImpl.focus (/projects/bar/node_modules/jsdom/lib/jsdom/living/nodes/HTMLElement-impl.js:65:14)
    at HTMLInputElement.focus (/projects/bar/node_modules/jsdom/lib/jsdom/living/generated/HTMLElement.js:49:21)

The expected behavior would be that the window is returned.

Well described. Also seeing the same, and also observing it's fixed @ 11.1.0

Great report @rsadza, this is exactly what we've been hoping for. Now that we have this, we can actually work on a fix. Will reopen!

See https://github.com/tmpvar/jsdom/pull/1979.

@TimothyGu Thanks for the fix 👏 !


In Usage, document authenticate(..., request=request)

The docs say "If you use django.contrib.auth.forms.AuthenticationForm directly, replace it with ratelimitbackend.forms.AuthenticationForm and always pass it the request object."
On this topic, they should also say "If you use django.contrib.auth.authenticate, pass it the request object.".

Fixed in #20


Auto corrected by following Lint Ruby Style/ParallelAssignment

Auto corrected by following Lint Ruby Style/ParallelAssignment
Click here to configure it on awesomecode.io

Coverage remained the same at 97.136% when pulling 778cecf833eec8e723fc2fbe0b64e3ea5562408c on awesomecode-lint-ruby-style-parallelassignment-47701 into 6f35b6f068f62083f4838f749eb9caa708dec50f on master.

Coverage remained the same at 97.136% when pulling 778cecf833eec8e723fc2fbe0b64e3ea5562408c on awesomecode-lint-ruby-style-parallelassignment-47701 into 6f35b6f068f62083f4838f749eb9caa708dec50f on master.


Animated widgets are too fast on Linux

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Use the attached minimal reproducible example
Run the project on Linux (native application) (specifically, I'm on Linux Mint 20, but it's likely that any Ubuntu target would have the same issue).
Click the menu button at the top left to toggle the animated position.

Expected results
The animation should take precisely 10 seconds to complete, independent of platform.
Actual results
The animation takes the full 10 seconds to complete on Android (and presumably other platforms, but I haven't tested this yet), but is much much faster than it should be on Linux (only around 1 second to complete).
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: 'Animation Duration Bug',
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool menuOpen = true;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        leading: InkWell(
          onTap: () => setState(() => menuOpen ^= true),
          child: const Icon(Icons.list),
        ),
      ),
      body: Stack(
        children: [
          AnimatedPositioned(
            duration: const Duration(milliseconds: 10000),
            left: menuOpen ? 20 : 300,
            top: 20,
            child: const Text('hello'),
          ),
        ],
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Ignore the different project name in the output
Building Linux application...

** (phone_iot_2:311558): CRITICAL **: 09:32:17.102: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.portal.Error.NotFound: Requested setting not found

** (phone_iot_2:311558): CRITICAL **: 09:32:17.104: Failed to read XDG desktop portal settings: GDBus.Error:org.freedesktop.portal.Error.NotFound: Requested setting not found
Syncing files to device Linux...                                    67ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

A Dart VM Service on Linux is available at: http://<IP_ADDRESS>:39967/aUyKHGya-IE=/
The Flutter DevTools debugger and profiler on Linux is available at: http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:39967/aUyKHGya-IE=/

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.6, on Linux Mint 20 5.4.0-153-generic, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.80.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

Hi @dragazo
I ran your sample  code on my machine (Ubuntu distro) but it works as expected:

Demo video
Screencast from 02-08-2023 14:15:59.webm

flutter doctor -v (stable & master)
[✓] Flutter (Channel stable, 3.10.6, on Ubuntu 22.04.1 LTS 5.19.0-46-generic, locale en_US.UTF-8)
    • Flutter version 3.10.6 on channel stable at /home/huynq/Documents/Working/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (7 days ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc3)
    • Android SDK at /home/huynq/Android/Sdk/
    • Platform android-31, build-tools 34.0.0-rc3
    • Java binary at: /home/huynq/Documents/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2021.1)
    • Android Studio at /home/huynq/Documents/android-studio
    • Flutter plugin version 67.0.1
    • Dart plugin version 211.7817
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.78.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.68.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.19.0-46-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 112.0.5615.121

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.13.0-16.0.pre.20, on Ubuntu 22.04.1 LTS 5.19.0-50-generic, locale en_US.UTF-8)
    • Flutter version 3.13.0-16.0.pre.20 on channel master at /home/huynq/Documents/Working/flutter_master
    ! Warning: `flutter` on your path resolves to /home/huynq/Documents/Working/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /home/huynq/Documents/Working/flutter_master. Consider adding /home/huynq/Documents/Working/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /home/huynq/Documents/Working/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /home/huynq/Documents/Working/flutter_master. Consider adding /home/huynq/Documents/Working/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9c184d475b (12 minutes ago), 2023-08-02 06:57:35 +0000
    • Engine revision 9dae7b708b
    • Dart version 3.2.0 (build 3.2.0-22.0.dev)
    • DevTools version 2.25.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc3)
    • Android SDK at /home/huynq/Android/Sdk/
    • Platform android-31, build-tools 34.0.0-rc3
    • Java binary at: /home/huynq/Documents/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2021.1)
    • Android Studio at /home/huynq/Documents/android-studio
    • Flutter plugin version 67.0.1
    • Dart plugin version 211.7817
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.78.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.70.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.19.0-50-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 115.0.5790.110

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Can you retry on profile or release mode and observe if the issue still appears? When checking this in profile mode, please notice if there are lots of janks or not. And please attach the timeline trace JSON file, you can find the instructions for it at https://github.com/flutter/flutter/issues/74833#issue-795394794.
Also, it is worth checking this on master channel as well.


METRON-824 site-book generation is broken

Contributor Comments
Currently, if you attempt to build the site-book on master you get the following error:
ERROR OR ERRORS DETECTED:
ERROR: Header specification character (#) detected with indenting.  This is presumed to be an error, since it will render as text. If intentional, put a period or other printable character before it.
on line: 16 in file: ./metron-sensors/bro-plugin-kafka/index.md
    # curl -L https://github.com/edenhill/librdkafka/archive/v0.9.4.tar.gz | tar xvz

In order to fix this I changed metron-sensors/bro-plugin-kafka/index.md to use triple backticks instead of indentation to indicate the code block.  This allows it to parse properly in GitHub MD as well as our Doxia site-book docs.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron (Incubating).
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[X] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[X] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

For documentation related changes:

[X] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
bin/generate-md.sh
mvn site:site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Duplicate of #511 - @mattf-horton beat me by a minute!


Use lists to construct SVGs and join them later

This brings drawing all of https://github.com/googlefonts/noto-cjk/blob/main/Serif/Variable/TTF/NotoSerifCJKjp-VF.ttf into an SVG from ~637s down to ~8s on my machine.

That's quite a win. Thank you!


DEBUG_FD warning (from this project?)

I have process.on('warning') logging stuff in a project, I got this today, brand new:

(node:29558) DeprecationWarning: `DEBUG_FD` is deprecated. Override `debug.log` if you want to use a different log function (https://git.io/vMUyr)

  => Live-Mutex warning =>  DeprecationWarning: `DEBUG_FD` is deprecated. Override `debug.log` if you want to use a different log function (https://git.io/vMUyr)
    at Object.<anonymous> (/home/oleg/WebstormProjects/oresoftware/observable-persistent-queue/node_modules/debug/src/node.js:62:148)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/oleg/WebstormProjects/oresoftware/observable-persistent-queue/node_modules/debug/src/index.js:9:20)
    at Module._compile (module.js:571:32)

the git.io link links to this project, but otherwise I am not sure what to do. Can you help? thanks

DEBUG_FD is the environment variable. Do you have that set in your project? If so, how are you using it?

I don't set that variable..hmm, do native addons set the variable somehow? weird!

The variable is being set somewhere.  It will continue working until 3.0.  We added the deprecation warning to let everyone know that it will no longer be supported after the v3 release :)

@TooTallNate @thebigredgeek I think Webstorm sets it, when you use the Webstorm runner to execute a Node.js file

Ahhh shit haha.  That's no good.  Wonder if they have an issues list somewhere on github?

I have never seen it before, so it might not be Webstorm, but that's my best guess right now, and it's fairly plausible given the evidence.

Hello,
I think the DEBUG_FD variable was very useful to me. Is there a reason to deprecate it?
I run my apps on IBM Bluemix and when running in that environment I had the DEBUG_FD set to 1 so that my logs would NOT go into stderr (which is reserved for recording critical failures on bluemix). While running locally I leave it unset.
Hence DEBUG_FD allows the log location to be switched by environment. I believe the suggestion to override debug.log is not the same this because:

it is not easily controlled by an environment variable (unless you put an if block around it)
it requires writing code for something that DEBUG_FD accomplished very easily where the output stream to use needs to be switched not the log function itself.

@wallali with V3 we will introduce log middleware that will allow you to "replace" the normal output mechanism and redirect logs to wherever you want (stdout, stderr, logstash, etc).  So hang tight!

Hello, I also see this warning. I explicitly set env DEBUG_FD=1, because I don't want the default debug() to print to stderr.
So right now I'm doing:
const debug = createDebug('app'); // default debug() print to stdout, pm2 will save stdout to .log files
const logError = createDebug('app:error');
logError.log = console.error.bind(console); // logError() now prints to stderr, pm2 will save stderr to .error file

As I understand, to comply with the new version of debug I need to remove my env var DEBUG_FD=1. But then, how can I alter in ONE COMMAND, the default output of debug() ?
I'd like to remove these warnings...Many thanks!

@thebigredgeek Another very important use of DEBUG_FD I realise now is that it automatically redirects output from all of my modules and any modules I depend on that also use debug to stdout.
If I have to write code to do the redirect two problems arise:

The boiler plate code that does the redirect to std out needs to be written in each file that I require('debug');
Modules I depend on who also internally use debug whose code I do not control keep outputting to stderr and I cannot redirect them to stdout.

The advantage of DEBUG_FD (or a similar environment variable) is that it allows the stderr/stdout choice to be made later at the time of module usage by the clients of my module rather than at the time of module development.

The reason it was deprecated was because of the way that we were creating a WritableStream to that file descriptor was non-standard for Node.js and using some undocumented APIs. See https://github.com/visionmedia/debug/issues/280 for more details.
One thing we could do is retain backwards compat for DEBUG_FD when the value is 1 or 2 only (since that's just process.stdout and process.stderr respectively).

One thing we could do is retain backwards compat for DEBUG_FD when the value is 1 or 2 only (since that's just process.stdout and process.stderr respectively).

@TooTallNate I like this idea.

We should provide a "global" middleware hook in v3, such as:
import debug, { OutputMiddleware } from 'debug';

debug.replace(OutputMiddleware, (data, next) => { process.stdout.write(data); next(); })

I am really hoping we can reduce the swiss army knife API that we currently support.  Using middleware makes it easy for people to continue using existing environment variables by adding simple functions for output parsing.  I think that will be the ideal solution on both sides.

@thebigredgeek If the middleware example you provided is meant to be set only once then this looks good to me. Is it possible to use this middleware function with current version 2.6 ?
If not, is there a way to let the warning go away? Thanks!

@thebigredgeek Why not have that simple middleware built-in and loaded automatically by v3 to keep backwards compatibility with DEBUG_FD in v2?
I respect trying to improve this debug lib and I'm looking forward to seeing the middleware features. debug one of the most popular npm libs out there. Most of the thousands of consumers of this lib like it b/c it's dead simple and something they don't have to worry about changing.
We use DEBUG_FD and it's valuable configuration option. It's used ~800 times in code (js and json) alone on GitHub which doesn't include all the places developers are using it only as an environment variable.
This deprecation will cause a lot of unnecessary work for a lot of people, even if it's two lines of code.
Amount of Time/Effort = (troubleshooting the change/issue + searching GitHub + reading the release notes + reading issues + adding the configuration logic to include middleware to be loaded at the proper sequence in their app + committing change + testing + releasing) X (thousands of users)

@Jeff-Lewis yeah that's the direction I think we were planning on going with this.  Sorry for any miscommunication haha.  Debug will likely come bundled with several "pre-loaded" middlewares for backwards compatibility

@TooTallNate @ORESoftware Just an update. If you are using JetBrains products: link

This change is breaking all my code under WebStorm, any workaround? The @NejcZdovc link is not working.
"oops. We're sorry, but something went wrong."

@luiseduardobrito strange, it's working for me. Print screen of the site

@NejcZdovc Really weird, tried in another network+pc and worked. But thanks for the screenshot.
Well, this may help people with the same problem, I work commercially with this tools and I can't just say to my clients that I'll wait for WebStorm update. So I started downgrading the debug version minor by minor until I found a version that worked in my current setup.
NodeJS: 7.2
WebStorm: 2016.3.2
Debug: ^2.3.0
Now the warning is not displayed anymore in the console and the debug is working again. It's not ideal, but at least now my dev team is working again. If you actually downgrade this, remember to leave a TODO in your project to upgrade it back when WebStorm 2017 is released, like I did.

This is very unfortunate change which degrades developer experience significantly by making far more complex than it was previously to route the debug messages to stderror - which is a very common thing for people to do.
In our case, the only time when we care about rerouting the messages is when we are running in a docker environment, since the logout output from docker-compose looks terrible when all of our debug messages are being printed to stderr. Previously we could just pass an env var to our docker containers to accomplish this. Now, we now have to create a wrapper library, a bunch of custom code, and alter every single place where we require in the debug module in order to get the debug output where we want it and prevent the depreciation warning.
I can understand if you want to want to change the API and depreciate the feature in a future version - that's your call (although I'd argue that hurting DX is not in the interest of the project). However, it would be good if there were a way to suppress this depreciation warning so that users of the 2.x branch can continue to use the package as they always have done without this warning constantly appearing.

@thebigredgeek My project had also used DEBUG_FD to make sure debug goes to stdout in all submodules as @wallali mentioned: Modules I depend on who also internally use debug whose code I do not control keep outputting to stderr and I cannot redirect them to stdout.
Our project shows a red 'Error Occurred' message in the UI to alert users when there is output to stderr, so we intend to use stderr solely for errors. Debug logging is not something that we want to trigger this error message, its just debug info.
So I'm looking forward to a solution that allows this scenario to work.
In the meantime I'll try doing as @uiseduardobrito mentioned and downgrade the debug version to keep the desired functionality.

Awesome. Thank you for addressing this @thebigredgeek
It would be good to get a new patch release cut that includes this fix so that everyone who has been bugged by it can move on and forget about it at last!

@pi0 thanks for fixing, @thebigredgeek thanks for merging. A release would indeed be great.

I need to test a bit before releasing.  Will do so when I have some free time.  Currently slammed at work

I need to test a bit before releasing. Will do so when I have some free time. Currently slammed at work

@thebigredgeek would it be possible to publish a canary release to npm? I'm more than happy to test it as I've been seeing this message the whole day for a few weeks now.
Thanks for considering.

@thebigredgeek Please review & release 😭😭I (& probably many other people) are suffering that warn every day, every build, every reload... Please keep your awesome project awesome :)

I've released a package to prevent this, https://github.com/ex-machine/debug-fd-deprecated
It will take care of deprecation warnings for some time (some packages were already been hard-coded to debug@2.6.0).

@bisubus I've considered doing the same though the problem is that you now have to go through your app and update all import statements, only to revert it later.
In a small app this is not a big problem, in a large app more so.
So a release will be very well received, the patch has been merged two weeks ago now...

@beeman I've managed to do this by patching util.deprecate. This should be done once per app instance, as early as possible, because there are too many third-party packages that depend on debug. I've done this in polyfills.js.

Hey guys, will slice a release this afternoon

Hey @thebigredgeek, is this release already out? Looking forward!

2.6.1 is now live

Euh, I still got this issue when starting tests in webstorm :
(node:6312) DeprecationWarning: `DEBUG_FD` is deprecated. Override `debug.log` if you want to use a different log function (https://git.io/vMUyr)

@jy95 You likely got a dependency that depends on 2.6.0. Any way, see this if you need a hotfix.

@jy95 run npm ls debug.  You'll see any duplicitous versions that might be running.  If you find any that depend on 2.6.0, submit an issue on their github repos and link this issue to the issue.  I'll chime in on the projects and see if I can help push them along to the latest versions

@thebigredgeek Thanks. It seems it is the "eslint" package that use<EMAIL_ADDRESS>The culpit module is<EMAIL_ADDRESS>I will send them a issue


bad request when sending message to discord

making my own issue as i have some logs:
logs edited for op sec removed my eve esi token, but left my discord channel id there
DEBUG:requests.packages.urllib3.connectionpool:"GET /latest/universe/structures/REMOVECITADELID/?datasource=tranquility&token=REMOVEDMYTOKENFROMHERE HTTP/1.1" 200 162
INFO:discord.client:logging in using static token
DEBUG:discord.http:GET https://discordapp.com/api/v6/users/@me with None has returned 200
DEBUG:discord.http:GET https://discordapp.com/api/v6/users/@me has received {'verified': True, 'id': 'XXXXXXX', 'bot': True, 'discriminator': '8789', 'email': None, 'avatar': 'dcd6b90c54f0eb411cdc10339b958b5d', 'mfa_enabled': False, 'username': 'XXXXXXX', 'flags': 0}
DEBUG:discord.http:POST https://discordapp.com/api/v6/channels/301333445378965504/messages with {"content":"[2018-05-07 03:26:00] Citadel (Astrahus, "XXXXXXX - XXXXXXX XXXXXXX XXXXXXX") attacked (100.0% shield, 100.0% armor, 100.0% hull) in XXXXXXX (http://evemaps.dotlan.net/system/XXXXXXX) by XXXXXXX (https://zkillboard.com/character/XXXXXXX/) (XXXXXXX (https://zkillboard.com/corporation/XXXXXXX/) (XXXXXXX (https://zkillboard.com/alliance/XXXXXXX/)))"} has returned 400
[2018-05-07 04:24:28.793760] Exception in esi_notification_task
Traceback (most recent call last):
File "/var/www/reconbot/reconbot/tasks.py", line 28, in esi_notification_task
notifier.notify(message)
File "/var/www/reconbot/reconbot/notifiers/caching.py", line 14, in notify
self.notifier.notify(text, options)
File "/var/www/reconbot/reconbot/notifiers/splitter.py", line 7, in notify
notifier.notify(text, options)
File "/var/www/reconbot/reconbot/notifiers/discord.py", line 17, in notify
loop.run_until_complete(self._send_message(channel_id, text))
File "/usr/lib/python3.5/asyncio/base_events.py", line 387, in run_until_complete
return future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/var/www/reconbot/reconbot/notifiers/discord.py", line 25, in _send_message
await self.client.send_message(c, message)
File "/usr/local/lib/python3.5/dist-packages/discord/client.py", line 1152, in send_message
data = yield from self.http.send_message(channel_id, content, guild_id=guild_id, tts=tts, embed=embed)
File "/usr/local/lib/python3.5/dist-packages/discord/http.py", line 200, in request
raise HTTPException(r, data)
discord.errors.HTTPException: BAD REQUEST (status code: 400): Unauthorized
BAD REQUEST (status code: 400): Unauthorized

same issue here. tried so many times. mades new bots and still nothing.
maybe some to do with 2FA ??

Thanks for including logging information.
It's easier to see that the notification itself looks reasonable, isn't too long to be accepted by Discord API.
However, I'm still puzzled as to why it's happening - thus far I'm unable to reproduce the issue - with correct details and Discord set up in a straightforward way (without any required permissions) it seems to be working.
The closest hint I found in a different project is here, where they had issues with Discord responding HTTP 400 BAD REQUEST: Unauthorized due to how connection was used in the app.
Will dig into it deeper.

maybe some to do with 2FA ??
I doubt it is. Access tokens are for the bot user, not your personal Discord account.

Just noticed in the logs python 3.5. This issued is solved for me using python 3.6


Go: Mqtt auth support via ini extra fields

Thank you.
You are on a straight line and direct path to having hared.go become my 1st class choice for the daemon(and thus putting our Python version to pasture). The only thing I can think of which will do that is if you add TLS support. Just a thought. :-)


Is That All?

Is this property not also used to define a join, to filter records in a subform, as in
Item No.=FIELD(Item No.),Customer No.=FIELD(Customer No.),Customer Specification No.=FIELD(Specification No.).  (NAV 2017)?
From page37031449

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

ID: c6fe1de6-74da-1098-e988-901885d36241
Version Independent ID: c1982f56-661e-16e0-d6ed-b508bb1bf3e6
Content: SubPageLink Property - Dynamics NAV
Content Source: dynamics-nav/SubPageLink-Property.md
Product: dynamics-nav-2018
GitHub Login: @jswymer

Thanks for the feedback, we're sorry for not getting back sooner. This issue refers to NAV product documentation and we no longer update this docset.


Add tests for passthrough statistics

Is it sufficient to only test eviction count is > 0? Is this check more a test to see if evictions are occurring? I recall testing the exact number of evictions to be a little troublesome.

test this please


How can I find the tns slider instance from the container?

Hi,
I need to be able to find the tns instance from the container selector. In my setup sliders are created programatically. I need to be able to fire events on custom controls which supply the selector of the slider container.
The problem is I need to be able to run methods on the slider when the only info I have available to me is the container selector.
Here's an example to give you the idea of what i'm trying to do, i'm aware this code will not work as i'm trying to run a method on an element as opposed to the slider instance. It's just to show the what I need:
let myUniqueSlider = tns({
    container: '.js-unique-slider',
    items: 3,
    slideBy: 'page',
    autoplay: true
});

document.querySelector('.js-unique-slider').goTo('next');

Any help is very much appreciated,

Hi, myUniqueSlider is the instance you are looking for.
So you can do myUniqueSlider.goTo('next');
On Tue, Sep 5, 2017, 5:58 AM Matt Pilott<EMAIL_ADDRESS>wrote:

Hi,
I need to be able to find the tns instance from the container selector. In
my setup sliders are created programatically. I need to be able to fire
events on custom controls which supply the selector of the slider container.
The problem is I need to be able to run methods on the slider when the
only info I have available to me is the container selector.
Here's an example to give you the idea of what i'm trying to do, i'm aware
this code will not work as i'm trying to run a method on an element as
opposed to the slider instance. It's just to show the what I need:
let myUniqueSlider = tns({
container: '.js-unique-slider',
items: 3,
slideBy: 'page',
autoplay: true
});
document.querySelector('.js-unique-slider').goTo('next');
Any help is very much appreciated,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ganlanyuan/tiny-slider/issues/69, or mute the thread
https://github.com/notifications/unsubscribe-auth/AExGmzic-C612gPz8DROVYLoAYwAkOBjks5sfRtFgaJpZM4PMtpj
.

@ganlanyuan Thanks for that, in my project I am unable to know myUniqueSlider but I do know .js-unique-slider how can I get the former from the latter?

May I know how do you initiate the slider?

There is no way to get the slider instance only by a selector.


console.warn when using getToken

I'm seeing a yellow box warning in the app recently showing something like below.

It doesn't indicate anything wrong with it though. So I looked into the code and notice there's this warn inside the switch case.
https://github.com/tamagui/tamagui/blob/5f7fa105d7817f368e65435c47c010c2f46cfd07/packages/web/src/helpers/createPropMapper.ts#L457
I wonder if this really do indicate there's an issue with my configuration, perhaps.

No issue with your config. This will be fixed when #858 is merged.
It's just a debugging log that ended up in the final bundle.

Fixed in 1.9.13


Query: Adds support for LIKE statement and INT system functions to c# query parser to avoid gateway query plan call when service interop is not available.

Pull Request Template
Description
This PR adds LIKE support and INT system functions for SqlObject and the ANTLR parser. It updates the grammar file, the CSTtoASTvisitor and all the associated Sql DOM.
This PR also adds fixes for an outstanding grammar bug, #2201
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] This change requires a documentation update

Closing issues
To automatically close an issue: closes #2201

| binary_scalar_expression K_OR binary_scalar_expression

please remove these rules

Refers to: Microsoft.Azure.Cosmos/src/Query/Core/Parser/sql.g4:118 in c3a4d03. [](commit_id = c3a4d039b43f06b83eafcf9ebfe0b78a9cdf719a, deletion_comment = False)

| binary_scalar_expression K_OR binary_scalar_expression

please remove these rules
Refers to: Microsoft.Azure.Cosmos/src/Query/Core/Parser/sql.g4:118 in c3a4d03. [](commit_id = c3a4d03, deletion_comment = False)

will update this in a separate PR, as discussed, it is out of scope of this PR


Extfilenew not found with pathstyle unix

Describe the bug
When using path_style='unix' on Windows, the extfile cannot be added to the mdu since it cannot be found:
ValidationError: 1 validation error for ExternalForcing
extforcefilenew -> test_model_bc.ext -> boundary -> 0 -> forcingFile
  File: `C:\c\test_model\test_model.bc` not found, skipped parsing. (type=value_error)

It is searching for a windows style path (which is good), but the c-drive is added twice. In a less portable test, it was searching for the unix-style path (which could of course not be found).
Also, I deliberately used different names in the pli/bc files of the testcase below. If it does not cost a lot of overhead, it might be nice to validate if the name combinations are valid (low priority).
To Reproduce
This is a MWE to reproduce:
import os
import hydrolib.core.dflowfm as hcdfm

model_name = 'test_model'
dir_output = r'c:\test_model'

path_style = 'unix' # windows / unix

#create dummy files
if not os.path.exists(dir_output):
    os.mkdir(dir_output)
file_pli = os.path.join(dir_output,f'{model_name}.pli')
with open(file_pli,'w') as f:
    f.write("""name
                1    2
                1.0    2.0
                3.0    4.0
                """)

file_bc = os.path.join(dir_output,f'{model_name}.bc')
with open(file_bc,'w') as f:
    f.write("""[Forcing]
               name              = right01_0001
               function          = timeseries
               timeInterpolation = linear
               quantity          = time
               unit              = minutes since 2001-01-01
               quantity          = waterlevelbnd
               unit              = m
                  0.000000 2.50
               1440.000000 2.50
                """)

ForcingModel_object = hcdfm.ForcingModel(file_bc)
boundary_object = hcdfm.Boundary(quantity='waterlevelbnd',
                                 locationfile=file_pli, #TODO: does not check if name of forcing is found in plifile
                                 forcingfile=ForcingModel_object)

mdu_file = os.path.join(dir_output, f'{model_name}.mdu')
mdu = hcdfm.FMModel()
ext_file_new = os.path.join(dir_output, f'{model_name}_bc.ext')
ext_bnd = hcdfm.ExtModel()

ext_bnd.boundary.append(boundary_object)
ext_bnd.save(ext_file_new,path_style=path_style)

mdu.external_forcing.extforcefilenew = ext_file_new #TODO: file not found if unix path_style

Expected behavior
The extfile is found, independent on the platform-style
Version info (please complete the following information):

OS: Windows
Version main branch

@priscavdsluis : the duplicate C:\C\ may be something small that needs looking into, but in general this is not supported until issue #480 has been resolved.
cc @veenstrajelmer

Would be great if the duplicate is indeed resolved, more complex conversion can indeed be resolved in that separate issue. The validation does work for all other files (net, oldext, etc), so would be great if the validation of newext also works like they do

@MRVermeulenDeltares, @veenstrajelmer:
From the example:
mdu.external_forcing.extforcefilenew = ext_file_new

Should be replaced with:
mdu.external_forcing.extforcefilenew = ext_bnd

This is because extforcefilenew should be an ExtModel and not a path.

Should we fix #480 first? That issue is not currently on the board.
Shall we create a separate issue for the incorrect pli-file?
@veenstrajelmer & @rhutten

Assigned the issue to @rhutten, She will look into it to determine if we should fix #480 first.


how to delete a column/row?

not the values in the cells, but the whole column/row

Yes, I would love to be able to delete a row or column.

+1 I would also like to be able to do this.
I currently do this in a very inefficient manner by copying all rows below one step up.

Copied from the docs:
// Cut one or more rows (rows below are shifted up)
// Known Issue: If a splice causes any merged cells to move, the results may be unpredictable
worksheet.spliceRows(4,3);

// remove one row and insert two more.
// Note: rows 4 and below will be shifted down by 1 row.
var newRow3Values = [1,2,3,4,5];
var newRow4Values = ['one', 'two', 'three', 'four', 'five'];
worksheet.spliceRows(3, 1, newRow3Values, newRow4Values);

// Cut one or more cells (cells to the right are shifted left)
// Note: this operation will not affect other rows
row.splice(3,2);

// remove one cell and insert two more (cells to the right of the cut cell will be shifted right)
row.splice(4,1,'new value 1', 'new value 2');

How About deleting a whole column?

For that please use spliceColumns:
https://github.com/exceljs/exceljs/blob/7a32223f6f0b73e2455ffa3ed5f94980b2401b34/lib/doc/worksheet.js#L214


Binary Operators with object

In the test cases is one example for and which should be clarified:
{
"data": [
true,
{}
],
"expected": {}
}
It's used in an and condition. If {} is resolved to false, should the expected then not be false instead of {}?

This is compliant to what JsonLogic does, at least according to the documentation and the original JS implementation. The first falsy value is returned (which is {}), or the last element in the operand list.

Okay, thank you:) I can close this issue.


ThemeData colorSwatch ignored with Brightness.dark

Due to this line and the below lines that set default values, ThemeData that is dark and has a primarySwatch doesn't correctly set other values.
Not sure if this is intended behaviour?

@jonahwilliams I think this is still valid and should be reopened.
Your explanation is clear, but that's not what this issue is about. What I think that's important to consider here is that the primarySwatch property is a 'shortcut' to set multiple other properties, but currently that's happening ONLY FOR LIGHT BRIGHTNESS.
So either there's a lack of consistency and this property should be updated to work the same way with any Brightness or it should be renamed to lightBrightnessPrimarySwatch. Don't you agree?

@jonahwilliams This issue is still unresolved despite it being closed. Then brightness is set to dark, the primarySwatch is ignored and it uses a teal color palette instead. This seems like a wrong behaviour.

Seems like this was by design:
https://github.com/flutter/flutter/pull/3002
Best quick workaroundu is to specify the following values explicitly:
toggleableActiveColor textSelectionHandleColor accentColor as they all default to teal at the moment.

Well, I don't quite understand the design decision then.

cc @HansMuller
What do you think about changing the following line
https://github.com/flutter/flutter/blob/bf8208cd14a89280676758ce9ddb8c45cb31a199/packages/flutter/lib/src/material/theme_data.dart#L283
accentColor ??= isDark ? Colors.tealAccent[200] : primarySwatch[500];

to
accentColor ??= primarySwatch[500];

Or perhaps another colour based on the swatch but that is not teal.

@dancojocaru2000, @lrimkus, @mattarau, @lucaslcode  - I've opened a new issue that covers accentColor's future:  Remove accentColor and accentTextTheme from ThemeData et al. #56918.
Any change to the current definition of accentColor would "break" existing app's - typically by causing golden image tests to fail. The long-term plan is to abandon accentColor in favor of ColorScheme.secondaryColor, so rolling out accentColor updates isn't desirable at this time.

Any progress on this? It's really annoying.

Please comment on #19089 with your case as that issue is open and better describes the problem.


Providing practical examples of polygons with holes

Hello!
I'm using Goost for the first time, and I'm having some difficult drawing a Polygon with a hole in the middle
Do you think you could provide some practical examples?
I would like to do exactly this:

My issue is that even using the properties from the Goost merge method, my Polygon2D object still can't understand the polygon vertexes to draw the clipped polygon.
Here's a repository for reproduction:
https://github.com/renatodex/goost-clip-polygon-example

I have transferred this issue to a dedicated goost-examples repository now. The bug/enhancement is tracked in godotengine/godot#41447. There's no way to draw polygons with holes in Goost without re-implementing the Polygon2D node, so it's better that holes support is added directly in Godot's Polygon2D node instead. It may be feasible to implement some Polygon2D variant in Goost itself, but requires design work for something like this to be usable by many.

Cool!
Thanks for the support on that @Xrayez !
As a temporary solution, I've ended up rendering multiple Polygon2D objects, so at least I can see them in the editor and use some of the features from Polygon2D.
I will definitively move into a more robust implementation as soon Godot team have time to explore this kind of enhancement,
And regardless of receiving Godot updates, which will probably take around 25 or 30 years (lol), the Decompose functionality from Goost module is already TRULLY AMAZING!
Regardless the Polygon2D interface, I think when writing something like:
...
var merge_result = GoostGeometry2D.decompose_multiple_polygons_into_convex([polygons])
var polygon2d = Polygon2D.new()
polygon2d.set_polygons(merge_result)

We should definitively expect Polygon2D to automatically Decompose nodes using the configured Engine, using the same pattern you use at the Goost module.
If Godot already have some kind of decomposing logic, I don't see why they could not use the same decomposition under the hood for set_polygons method.
This could of course be something you could support at Goost, but I would only focus on that now if, and only if, the Performance gain could be really really positive when drawing complex Polygons.
Thanks again!

Yes, I think I could implement this myself in Godot's Polygon2D directly in fact, but yeah the speed at which this can be done is bottleneck`ed by the review process, and it's likely that the implementation has to be agreed upon first (else my particular implementation may be rejected), so waiting for response in godotengine/godot#41447.

I'm currently implementing boolean operator nodes in 2D, PolyNode2D is converted to Node2D, so this should help debugging polygons with holes more or less easily (may as well solve your underlying use case, I presume), feedback welcome!


Fixes for dependencies and subscribers properties in sensu::check.

Fixes two issues with the Puppet configuration:

The dependencies property is not handled correctly by the provider causing it to be added or removed with alternate runs; and
Set subscribers property in sensu::check as undef to prevent empty array output in configuration.

This failure seams to be an issue with the puppet module itself. It fails on my branch and on master on my machine at the moment?


[Remote debugging] Stopping ps remote session from REPL causes problem on remote debugging

Stopping debugging does not fix the problem, and it leaves VS into below status, even though debugger gets stopped. We have some error handling and clean up work needs to be done for those cases.

Another repro for this problem is "stop remote process was attached to" during remote debugging.


Update index of libraries

🎉
I would rather keep then in the README. Essentially having this list is the only purpose of this repository, so why move the index into a separate click?

I agree! One stop shop.

Essentially having this list is the only purpose of this repository

Well arguably there's contribution guidelines, badge info, and conferences. But sure, I'll change that.

Thanks @pauldraper, LGTM we can iterate from here.


Provision Dart Services running the latest stable, beta and dev releases

This is the server-side half of https://github.com/dart-lang/dart-pad/issues/774

Add an entry for old.api.dartpad.dev for stable -1.

We have API end points running for stable channel -1 (old.api.dartpad.dev), stable channel (stable.api.dartpad.dev), beta channel (beta.api.dartpad.dev), and dev channel (dev.api.dartpad.dev).


Bump up rk-gin rk-grpc version to v1.2.4

Codecov Report

Merging #7 (3c318fc) into master (b99ab99) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 3c318fc differs from pull request most recent head 3abe6a8. Consider uploading reports for the commit 3abe6a8 to get more accurate results

@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   88.88%   88.88%
=======================================
  Files           1        1
  Lines          63       63
=======================================
  Hits           56       56
  Misses          4        4
  Partials        3        3

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 b99ab99...3abe6a8. Read the comment docs.


Step 8 on the NewResourceModuleSubmissions.md Needs Adjustment

Step 8 of the NewResourceModuleSubmissions.md document requires that the new resource module is transferred to the PowerShell Organization. However, this is only possible if the person transferring the Module is a member of the PowerShell Organization (which most of us aren't).
I ran into this problem when I transferred xDFS over. The way we solved it was that I transferred the repo over to @KarolKaczmarek and then he transferred it into the PowerShell Organization.
It might be worth noting that this will process will need to be used.

Updated the document with clearer instructions to transfer the module to me first so that I can transfer it to PowerShell. Also included a link to the instructions for transferring a module.


docs(readme): Update discord links to home-operations

Description of the change
Update discord links to home-operations
Checklist

[X] Title of the PR conforms to the Conventional Commits standard.
[X] Scope of the of the PR title contains the chart name.
[ ] Chart version in Chart.yaml has been bumped according to Semantic Versioning.
[ ] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[ ] Variables have been documented in the values.yaml file.

Thanks for taking the time to submit the PR!!


[REQUEST] velocity old

currently I only have the velocity in my cheat, but I wanted that when I landed on the ground my speed appears on the velocity side between ()
example:

pass me ur discord

kenedy#8441

save that value when ur on ground
and show it up

@koon666 if you have it can u send pls? :(      braken#0133

@JacksonDon how? im new on c++ o_0

@JacksonDon how? im new on c++ o_0

example:
auto velocity = player->velocity().length2D() + 0.5; interfaces.surface->printText(std::to_wstring(velocity));


Update demo

Update demo to use latest react-native

@ratson Thanks for taking the time to update the demo. Unfortunately I can't get it to run in your branch. Can you describe the steps you use to run the demo?
After a quick look at the code, I think this issue might be that the dependencies in the root package.json need to be updated to match the dependencies you've updated in demo/package.json

cd demo
yarn
yarn react-native run-ios

@ratson thanks for describing the steps you used to run the demo app. That does work, but there are a few issues. Prior to these changes we were running the demo from the root directory as described in the readme, and we were able to pick up changes from /lib without rebuilding. With this change, it looks like victory-native is being yarn installed, so it's not possible to pick up local changes. I don't mind changing the steps to run the demo, but being able to use the demo to see development changes is a hard requirement. Can you update this work so that 1) the demo app still picks up changes to lib/ and 2) and changes in the steps required to run the demo app are described in README.md?
Thank you for working on this! I really appreciate the help!

@boygirl Update instructions for local development, see if it works for you.

@ratson I'm still not able to see changes to lib in your branch. I'm testing this by changing the render method of lib/components/victory-primitives/tspan.js so that it will always render the same string ("HI!"), but the labels in the demo remain unchanged. I think the alias is not working.

@boygirl I could see the update. Did you enable hot reload for test? I add --reset-cache to start the server, see if it helps.

@ratson yes, it works! Thank you so much for the help!


V10 updates

Grid, footer, header, style updates for v10

fyi @lovemecomputer latest v10 work, wondering if we should merge into v10 or wait for your PR? let's discuss tomorrow.


random failures with virtiofs

I have seen some random failures on the virtiofs CI, the failure is related with an unexpected /opt/kata/bin/qemu-virtiofs-system-x86_64 present. I see that most of the time happens after running the functional tests, see http://jenkins.katacontainers.io/job/kata-containers-tests-ubuntu-18-04-virtiofs-PR/255/console

Hi @GabyCT , I know something which may related with this issue. if you run kata-runtime with virtiofs round after round , eg :
for i=0; i<10; i++ {
kata-runtime run kk
}
the round may not continue for the second because in the second round it will warn as no qmp.sock available. the root cause is that the the qemu process spawned by the first kata has not exited completely when the second kata started.
I try to debug this issue and find that if we compile the qemu without "--static", this issue will not occur. but I don't know why for now.
I can't tell if the issue I report is the identical one with yours, but can be a reference.

Seems that this issue was not seen in a while, probably need to have stress test with virtiofs to launch many times until find this kind of issues as @jongwu  points.

Closing this issue @jongwu  please open an issue if needed for the case you have seen.