Exclude tests from coverage results and instrument all files

[Current coverage][cc-pull] is 91.27%

Merging [#133][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.08%

@@             master       #133   diff @@
==========================================
  Files             6          4     -2
  Lines           301        298     -3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            275        272     -3
  Misses           26         26
  Partials          0          0

Powered by Codecov. Last updated by [443e0ac...ba4eee4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Automattic/monk/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/Automattic/monk/compare/443e0aca6143a2918d9c7bb5ccd24c14c8208a98...ba4eee4817fa16b074b1afb8f8956f3b3c3c97f1
[cc-pull]: https://codecov.io/gh/Automattic/monk/pull/133?src=pr

good point


Repeat MCP check if hitting OCPBUGS-22677

Indentation was not correct, retesting it

I'll finally close this one, the workaround will not help in this issue. It has already commented in the OCPBUGS that the real cause of the issue is OCPBUGS-22409, related to reserved CPU selection in the performance profile, same case than ours.


Align main titles vertically

The main titles on these pages are not placed the same way. (The blog post title is slightly above the other one.)
Is is possible to ensure they're placed the same way ?
/storybook/iframe.html?id=layouts--blog-post
/storybook/iframe.html?id=sidebar--usage-example

Finally figured out what's happening with this alignment bug here.
In the Blog Post example:
No display: flex is set on <main> container, which causes the margins to collapse, therefore causing the alignment bug.
In the With Sidebar example:
display: flex is applied, therefore preserving the margins, and things align correctly here.
For now we can force margins from collapsing by setting overflow: auto in the <article> element. I'll create a PR for this.
Related reading: https://stackoverflow.com/questions/16485810/how-to-fix-collapsing-top-and-bottom-margins


chore: add Gateway API survey banner

What type of PR is this?

What this PR does / why we need it:
Add a banner with the Gateway API survey link.
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

NONE

/cc @xtineskim as you may want to have say something about the aspect :)

/cc @xtineskim
as you may want to have say something about the aspect :)

Thanks @mlavacca!
/lgtm


Reusable buffers for compression in compiler

The new compressions classes should have versions of the methods that read from / write to streams.

Changing title to cover the remaining work as streams are available but not used.
By using the streams and some object pooling we should be able to improve the compiler (speed)

I realized, that "stream-support" was not what I wanted. The sstream classes are not easily reusable. @DavidNemeskey: Sorry, my bad.
I am now trying to change it, so that I pass a buffer object into the compression method.

implemented in https://github.com/cliqz-oss/keyvi/pull/49


switching to monospace font broken in line comments

to reproduce, find a diff, add a line comment and attempt to switch to monospace font

Hi @boneskull!
Thanks for reporting this problem! I'll have it fixed shortly.


Dependencies License list

All of the licenses for our dependencies.

Fixes https://github.com/influxdb/influxdb/issues/3888

@pauldix @toddboom @fred-influx I think we're out of compliance with the BSD licenses.
2. Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.

I'm pretty sure we have zero license files in our binary packages, which means we might be in violation.
Also, raft has the MPL which I don't know very well. Looks like it might have implications for our own licensing.
Apache license has a similar requirement, but statik doesn't have a NOTICE file so we're good:
If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

And there's this on the glyphicons license page:
GLYPHICONS Halflings are also a part of Bootstrap from Twitter, and they are released under the same license as Bootstrap. While you are not required to include attribution on your Bootstrap-based projects, I would certainly appreciate a visible link back to GLYPHICONS.com in any place you find appropriate (footer, docs, etc).

@pauldix @toddboom can we merge this?

Done!


Controller loading but not applied to page

Hi,
I'm using angular + ui router, the controller is fetched, but the page doesn't render correctly.
ssd.config(['$stateProvider', '$urlRouterProvider', '$locationProvider', '$ocLazyLoadProvider', function ($stateProvider, $urlRouterProvider, $locationProvider, $ocLazyLoadProvider) {

...

$stateProvider
        .state('index', {
            url: '/',
            views: {
                '@': {
                    templateUrl: 'ssd/components/jumbotron/jumbotron.html'
                },
                'requests@index': {
                    templateUrl: 'ssd/components/requests/requests.html',
                    controller: 'requestsController',
                    resolve: {
                        requestsController: function ($ocLazyLoad) {
                            return $ocLazyLoad.load({
                                name: 'requestsController',
                                files: ['ssd/components/requests/requestsController.js']
                            });
                        }
                    }
                }
            }
}

Any ideas?

Hi, the name in the load function should not be "requestsController" but the name of the module that requestsController belongs to (probably the module ssd).

Thanks

The page now loads correctly, the controller executes code, but the html in the TemplateUrl doesn't render the parts where the controller has data.

Is the controller executed? Check with a console.log inside the controller

Ok found the problem.
Thanks.

Anytime :)


OpenVPN GUI: setting "Topology" not respected for CSCs

The OpenVPN server configuration allows to enable the "Topology" setting, which enables the "topology subnet" option in OpenVPN.
Unfortunately, when enabling this setting and combining it with Client specific overrides, it may lead to a flawed CSC (client specific configuration). The VPN client may report something like this:
'ifconfig': 10.x.x.2/10.x.x.1: ipv4_exception: malformed netmask```

As you can see from the message above, the CSC is still configured for "topology net30", while it should've been updated for the new "topology subnet" setting.

Actual CSC for "topology subnet":
```ifconfig-push 10.x.x.2 10.x.x.1```

Expected CSC for "topology subnet":
```ifconfig-push 10.x.x.2 <IP_ADDRESS>```

this one can only be solved in conjunction with https://github.com/opnsense/core/issues/296, in the current version you just don't know which server the override is bound to.

@fraenki both https://github.com/opnsense/core/issues/296 and this issue should be fixed win the following commit https://github.com/opnsense/core/commit/d101b28e4582bb68a329505bf17480e8302b6240
If you have time to test, just download the next files on a 16.1 release:
curl -o /usr/local/etc/inc/openvpn.inc https://raw.githubusercontent.com/opnsense/core/master/src/etc/inc/openvpn.inc
curl -o /usr/local/www/vpn_openvpn_csc.php https://raw.githubusercontent.com/opnsense/core/master/src/www/vpn_openvpn_csc.php
curl -o /usr/local/www/vpn_openvpn_server.php https://raw.githubusercontent.com/opnsense/core/master/src/www/vpn_openvpn_server.php

@fraenki any news here? :)

timeout.


Frequent pop-up for bug report submission

Microsoft PowerToys version
0.65.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Always on Top, Keyboard Manager
Steps to reproduce
Actions that trigger Crash pop-up window

[X] Using "Alt + Spacebar" for quick search.
[X] Clipping screenshot (Shift + Win + S) also trigger the pop-up window.
[X] Quick preview of files. Pressing "Spacebar" leads to no response and then prompt after 5 seconds with error.

✔ Expected Behavior
On using the above two-mentioned events the task should be completed.
❌ Actual Behavior
Random pop-up prompting for crash report submission pop up.
Other Software
No response

Can you post bugreport and screenshot of crash report submission pop up?
/needinfo


Source generator - Column ordering

Codecov Report
Attention: 44 lines in your changes are missing coverage. Please review.

Comparison is base (9b165ab) 87.17% compared to head (94ca159) 86.87%.

Files
Patch %
Lines

...heetah.TestHelpers/Assertions/OpenXmlAssertCell.cs
38.46%
8 Missing and 8 partials :warning:

...eetah.TestHelpers/Assertions/OpenXmlAssertSheet.cs
72.22%
5 Missing and 5 partials :warning:

...ourceGenerator/Extensions/CompilationExtensions.cs
61.90%
4 Missing and 4 partials :warning:

...adCheetah.SourceGenerator/WorksheetRowGenerator.cs
89.28%
1 Missing and 5 partials :warning:

...heetah.TestHelpers/Assertions/SpreadsheetAssert.cs
75.00%
1 Missing and 1 partial :warning:

...adCheetah/SourceGeneration/ColumnOrderAttribute.cs
0.00%
1 Missing :warning:

...dCheetah/SourceGeneration/WorksheetRowAttribute.cs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
- Coverage   87.17%   86.87%   -0.30%
==========================================
  Files         124      130       +6
  Lines        4366     4472     +106
  Branches      856      881      +25
==========================================
+ Hits         3806     3885      +79
- Misses        250      263      +13
- Partials      310      324      +14

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update links moved from japaric to rust-embedded

Clicking these links does forward the browser to the correct GitHub
repository but I thought maybe it would be better to just update the
URLs to the new location of these repositories.

bors r+


R3.5, update recipe, update windows build

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@bgruening Ready to merge. Thx

Nice! Thanks.


Make the body of a user-defined op a fully-fledged scope

tl;dr
In the Zed docs about statements several times we explain scopes as:

...the main scope at the start of a Zed program or a lateral scope defined by an over operator

However, there are valid reasons why a user might want to treat other ( )-enclosed code blocks (e.g, the body of a user-defined operator) like scopes.
Details
Repro is with Zed commit f1be6a4.
This topic was kicked off by a community user in a Slack thread. In their own words:

Can i define a function inline?

There was some back & forth about what was implied by the word "inline" here (e.g., in language contexts it often refers to this kind of concept from C++, which indeed did not seem to be what this user had in mind). I ultimately read back this simplified example that the user confirmed captured the essence of what they had in mind.
This works:
$ cat works.zed
func compute(num): (
  num * num
)

op square(val): (
  yield compute(val)
)

$ zq -version
Version: v1.14.0-17-gf1be6a4a

$ echo '2' | zq -I works.zed 'square(this)' -
4

However, this currently does not, as it produces a syntax error.
$ cat attempt.zed
op square(val): (
  func compute(num): (
    num * num
  )
  yield compute(val)
)

$ echo '2' | zq -I attempt.zed 'square(this)' -
zq: error parsing Zed in attempt.zed at line 2, column 20:
  func compute(num): (
               === ^ ===

In terms of why the user might find the second approach desirable, they confirmed:

The main problem is not wanting to pollute the global namespace.

Indeed, other languages have this concept of being able to define functions, constants, etc., that are local to the innermost scope, so it's understandable why users might hope to see it in Zed.
That covers a specific case of a func inside of an op, but if we want to approach this in a general way, it seems there's other variations we might want to cover, e.g., #5075 tracks the equivalent for user-defined functions.

Verified in Zed commit 18b3c7f.
Our Zed program with the user-defined function defined within the scope of the user-defined operator now parses successfully and produces the expected result.
$ zq -version
Version: v1.14.0-19-g18b3c7f8

$ cat attempt.zed
op square(val): (
  func compute(num): (
    num * num
  )
  yield compute(val)
)

$ echo '2' | zq -I attempt.zed 'square(this)' -
4

Thanks @mattnibs!

Amazing! Thank you for implementing this!


Change the parameters of the init_data and init_bss functions to immutable constants

The methods init_bss(.) and init_data(.) should treat their parameters as immutable constants, since semantically that is what they are and because it would lead to a cleaner API.
The documentation around line 35 of lib.rs, explains the usage of this crate requires another block of code to pull in the linker script addresses as external values, e.g.
static mut _sbss: u32;

Semantically, this symbol refers to the start of the .bss code segment (aka 'output section'). It makes no semantic sense for this to be mutable. As I understand it, the mutability of these variables is merely to allow us to reuse them directly in code. Implementation is leaking into API.
If that is the only reason, it seems like a poor tradeoff:
(1) we add mutability throughout the API when we don't actually need it
(2) we violate the semantics of the name of the variable ('start of the bss segment')
It would be better to make a mutable variable inside the method and copy the constant value to that temporary variable, then use that. Something like, for line 131:
   let mut src: u32 = sdata;
   let mut dest: u32 = sidata;

    while src < edata {
        ptr::write(src, ptr::read(dest));
        src = src.offset(1);
        dest = dest.offset(1);
    }

then all the linker variables could be treated as constants in the API.
cheers,
~adrian

I'm sorry, but it shouldn't make any difference whether sdata and sidata parameters are mutable or not, because it's not part of the API. If you take a look at documentation you can see that it doesn't even show the mut keyword for this parameters, because it doesn't affect the usage in any meaningful way.

As I understand it, the mutability of these variables is merely to allow us to reuse them directly in code.

No it's not. I believe you are confusing mutability of function arguments with mutability of the raw pointers for the memory they are pointing to. Semantically static mut _sbss: u32; is not a 32bit integer, it's only a special symbol. We must not read (or write) any value out of _sbss, we can only take its address (pointer to _sbss) and use it as a physical address of the memory section that we care about, in this case .bss. u32 here is just to set correct alignment, the actual u32 doesn't exist. And we need a *mut pointer here because we intend to write zeroes to that memory location, so _sbss needs to be mut, to allow us take this reference &mut _sbss and cast it to *mut u32

Like @pftbest said the mut in the parameter binding doesn't affect the signature of the function. The mut binding is just sugar as seen below:
fn foo(x: i32) {
    let mut x = x;
    // ..
}

// sugared version of `foo`
fn bar(mut x: i32) {
    // ..
}

Mutations done on the x variable won't affect the actual argument passed to foo or bar because it's a copy (memcpy) of the argument the function was called with.
let x = 0;
foo(x);
// x will always be `0` here
bar(x);
// x will always be `0` here

Hope that makes sense!
I'm going to close this issue as changing the binding have no effect on the semantics of the API. It would probably make the implementation a little more verbose though so best to keep the implementation as it is.


onConnectionFailedRtmp (FATAL EXCEPTION: pool-4-thread-1)

Hi, I have a problem with onConnectionFailedRtmp.
I try connect to unavailable server, but interface method "onConnectionFailedRtmp" crash activity and application.
Your example rtmp activities crash too
And after executing "onConnectionFailedRtmp" I turn on the rtmp server, but I can start stream, because error state ( FATAL EXCEPTION: pool-4-thread-1) remains
Log:
E/AndroidRuntime: FATAL EXCEPTION: pool-4-thread-1
Process: com.pedro.rtpstreamer, PID: 18276
kotlin.UninitializedPropertyAccessException: lateinit property output has not been initialized
at com.pedro.rtmp.utils.socket.TcpSocket.getOutStream(TcpSocket.kt:38)
at com.pedro.rtmp.rtmp.CommandsManager.sendClose(CommandsManager.kt:263)
at com.pedro.rtmp.rtmp.RtmpClient.disconnect$lambda-5(RtmpClient.kt:464)
at com.pedro.rtmp.rtmp.RtmpClient.$r8$lambda$L6f1XZSd9tdbDvwE21RqUPtnFoA(Unknown Source:0)
at com.pedro.rtmp.rtmp.RtmpClient$$ExternalSyntheticLambda1.run(Unknown Source:2)
device: Samsung s20 FE

Fixed here: https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/commit/8d6438dda707e4a5732eacc7f7175daa4ad26623
You can compile library version 2.1.9


Add letterbox preset

Sometimes an inexperienced mapper will map the letterbox (private mailbox) in front of a house as amenity=post_box (postbox or mail collection box). A dedicated amenity=letter_box preset would make this tagging mistake less common.
Terms include “letter box”, “letterbox”, “letter plate”, “letter hole”, “mail slot”, “mailbox”, and “private mailbox”. Note that the addr:* scheme is replaced by a post:* scheme.

Having a good icon for this will help mappers tell the difference 📬

I added this, including a field for the post:* scheme. I preemptively used the temaki-letter_box icon ID, meaning the icon is blank now but will appear once we merge the svg I drew for temaki and do a release.


The terminal process terminated with exit code:<PHONE_NUMBER>

VSCode Version: 1.46.1 (user setup)
OS Version: Windows_NT x64 10.0.17763
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

See https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch for steps on how to investigate what's going on.


GestureDetector in Marker not works

How can I get an event of marker tap or long press ?

When you build a Marker, you use any widget:
      return new Marker(
        width: 80.0,
        height: 80.0,
        point: latlng,
        builder: (ctx) => new Container(
          child: new FlutterLogo(),
        ),
      );

So instead of FlutterLogo you could use InkWell or some other widget with an onTap method. Detecting long presses might require you to use your own GestureRecognizer.
Moving this to https://github.com/apptreesoftware/flutter_map/issues/102

The top level widget is GestureDetector, all action is not triggered, but the on tap of map is triggered.

You should be seeing a tap event on the "innermost" widget (your marker) if it's handling the tap event:

The pointer down event (and subsequent events for that pointer) are then dispatched to the innermost widget found by the hit test.

https://flutter.io/gestures/

@johnpryan

Both tap will not trigger. Only the onTap of MapOptions was triggered.

I can't see why this isn't working for you - can you verify that the example is working with your setup? https://github.com/apptreesoftware/flutter_map/pull/103

I remove the interactive: false then works, I thought disable interactive is disable the map's interactive not marker's.


refactor: use nock to test 'StreamLabs'

Related to #53
This PR does a couple of things to allow us to use nock:

Adds nock as dev dependency
Adds jest.config.js to prevent jest to add jsdom more info
Use nock in the StreamLabs spec

🙏🏻🙏🏻

Can you elaborate on

Adds jest.config.js to prevent jest to add jsdom more info

?
I don't see the specific setting in jest.config.js


:bug: (docker) add missing migrations folder

Might be missing something, but doesn't this change also need to be added to the four Dockerfiles in the docker folder?

Good catch @shaankhosla ! Updated those too
(as you can clearly see - docker isn't exactly my strong suit :) )


Fix iOS Safari compatibility issue.

Resolves #28
I looked into this and tracked down the error and I believe I have a fix.
The error is:
[Error] ReferenceError: Can't find variable: Notification
	Global Code (draft.js:172)

Some research led me to this post which suggests the firebase library version is not compatible with the version of Safari on iOS.
To work around this I'm changing the definition of enableNotifications and notificationPermission to check if Notification is undefined before referencing it.
After making this change I was able to load the app on iOS Safari without any problem. I fired up a draft with 7 bots and made sure I could do 2-3 picks, but I did not test any further so I can't guarantee there are no other bugs on iOS as I haven't had time to do a very thorough test.

Indeed it looks like Notification is not supported on iOS Safari, which make sense!
Thank you for the test and fix!

 Thank you for making this and for making it open source. This project is awesome and I'm happy to help out where I can. Please open more "help wanted" issues if you'd like help - I'll be keeping an eye out for anything I can help with


Only SHA-1 algo in CertificateID

Could you explain why in class org.bouncycastle.cert.ocsp.CertificateID only using sha-1 algo ? If someone need to use more stronger algo, e.g. sha-2, how could it being used ?

CertificateID uses whatever hash algorithm is specified by the DigestCalculator passed to it. There is an algorithm identifier for SHA-1 defined in the class, but that's more as an old time courtesy.


system:node can't list namespaces

Some pods are stuck in ContainerCreating and show the following error
Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "e3d4a705961e37b849a3138a48f8ccfbb5f2dd9a74b3e70c69d0f4a327f90076" network for pod "netchecker-server-864bd4c897-46kfh": NetworkPlugin cni failed to set up pod "netchecker-server-864bd4c897-46kfh_default" network: Multus: Err in tearing down failed plugins: Multus: error in invoke Conflist add - "cni0": error in getting result from AddNetworkList: namespaces "default" is forbidden: User "system:node:k8s-55149838-190425041-2" cannot get resource "namespaces" in API group "" in the namespace "default"

Adding get, list, watch permissions for namespaces in the system:node ClusterRole removes this error message, but the default value for system:node doesn't seem to work.

Could you please let me know "how to install multus (daemonset yaml file or just copy?)", "multus CNI config (in /etc/cni/net.d)"?

Also do you have any information on what Kubernetes version you're using?

This was on v1.13 installed with Kubespray v2.9.0

Having same issue after the upgrade from v1.12.5.

I install kubernetes (v1.14.0) with kubespray v2.9.0/CentOS (kube_network_plugin=calico + kube_network_plugin_multus=true) but cannot see the such error (succeed to launch following yaml pod, *1), so need more information for the issue. In addition, kubeadm does not happen the issue.
I guess I miss something to repro the issue and I need your info for that. Could you please let me know following information?

net-attach-def yaml
pod yaml file
kubespray config
how to install multus (if you don't use kubespray to install multus)

# *1: yaml file tested with kubespray 2.9.0 + k8s v1.14.0 + CentOS 7.6.1810
---
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: vlan-eth1
spec:
  config: '{
                "cniVersion": "0.3.0",
		"name": "test",
                "plugins": [
                {
                        "type": "vlan",
                        "master": "eth1",
		        "vlanId": 1,
                        "ipam": {
                                "type": "static",
                                "addresses": [ { "address": "<IP_ADDRESS>/24", "gateway": "<IP_ADDRESS>" } ],
                                "routes": [ { "dst": "<IP_ADDRESS>/0" } ]
                        }
                },
                {
                        "type": "route-overwrite",
                        "flushgateway": false
                }]
        }'
---
apiVersion: v1
kind: Pod
metadata:
  name: pod-case-01
  annotations:
    k8s.v1.cni.cncf.io/networks: '[
            { "name": "vlan-eth1"
            }
    ]'
spec:
  containers:
  - name: pod-case-01
    image: docker.io/centos/tools:latest
    command:
    - /sbin/init

@Miouge1 @psiwczak One q for your setting. Do you use /etc/kubernetes/kubelet.conf for kubeconfig in /etc/cni/net.d/*multus.conf?

@Miouge1 and @psiwczak -- we just located this issue while looking through some backlog -- have either of you tried this with a recent version of Kubespray? We'd love to get some information on it.


Fix typo in SE-0365

This proposal is great! Fixing a small typo.
@calda @compnerd

I also updated "Authors" to "Author".


Optimize queries in migration order 0139_fulfil_orderline_token_old_id_created_at

Port of https://github.com/saleor/saleor/pull/11893

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: CLOUD-2505 Optimize order.0139_fulfil_orderline_token_old_id_created_at [15:44]


Doc doesn't show how to find specific parameter of _ember relationship

The documentation doesn't show how to find a specific parameter from a _ember relationship.
I try it: https://github.com/typicode/json-server#filter
My http query is below:
http://localhost:3001/locations/2/?_embed=locations_transl&locale=es
http://localhost:3001/locations?place_code=xxxxxxxxx&_embed=locations_transl&locale=es

Be careful: _embed results is very different of _expand results.

The second doesn't show all of results..
Please, I need a help to identify this.

@francisrod01 Could you please put some code example or use cases.

Sure @Nilegfx ! Thank you for your comment! :)
I was trying to access an attribute from a relationship table, without relating this foreign table to a foreign ID.
Example: I was relating a location table with place_id of Google Places, which is a string, with a service table without mentioned a location_id (ObjectID or integer field) in  service table.
It was a bad idea, I know, sorry about that!


Add multiapi for Python

This generates Python client with multi-api support in the CI

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

New container needs to be pushed with "python" as an aliases to "python3.6"
https://github.com/lmazuel/swagger-to-sdk/commit/0eda36bdc082a3a484274c913f058cce4e882517


Add tree widget

As per the issue (https://github.com/spectresystems/spectre.console/issues/144) I've added the ability to render a tree of IRenderables - let me know what you think.
TODO:

[x] Doc comments on all public methods

@mcon Oooh, looks awewome. Not in a position to review it right now, but I'll get on it first thing when I have some "me time". Great work! 👍

@mcon Is this ready for review?

@mcon Is this ready for review?

I'd say so, yes

I'd say so, yes


App crashing when being put into background with MapView component mounted

Bug report

Summary
Hi! I have recently ejected from expo, and ran into a new issue with maps. If I'm on a screen with a  component, whenever I place my app into the background it crashes. Running the application on iOS via xcode. The error in Xcode is shown as: Thread 26: EXC_BAD_ACCESS (code=1, address=0x10). I have tried to uninstall and reinstall react-native-maps since I have ejected from expo, but still having the same issue. I am able to reproduce with a fresh react-native (non-expo), application.

Environment info

react-native info output:
System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 933.69 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.15.0 - /var/folders/dj/fvcdsjcn3_s0g6cxb5kcq2wr0000gn/T/fnm_multishell_13416_1607353176693/bin/node
    Yarn: Not Found
    npm: 6.14.8 - /var/folders/dj/fvcdsjcn3_s0g6cxb5kcq2wr0000gn/T/fnm_multishell_13416_1607353176693/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.10.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
    Android SDK:
      API Levels: 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.2
      System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>58069
    Xcode: 12.2/12B45b - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_275 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ~0.63.3 => 0.63.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

    "react-native-maps": "0.27.1",

Steps to reproduce

Start a fresh react native application, install react-native-maps, use example map code from README.
Run application
Place application in background.

Describe what you expected to happen:

When application is reopened, everything is still working. (app not frozen, crashed, etc.)

Describe what you actually happens:

When put into background, app crashes with Thread 51: EXC_BAD_ACCESS (code=1, address=0x10)

Reproducible sample code

gist: https://gist.github.com/shorsher/5049b8ae3a27e113d6620a4935ff7362

After some further debugging, it seems hardcoding a height and width prevents the crashing from happening. But in my actual application I am using:
        width: Dimensions.get('window').width,
        height: Dimensions.get('window').height,

and the crashing is still occurring.
If I use something like 400/400, everything seems to be fine.

@shorsher: I believe this is still an issue, even in 0.29.3. I've filed #3957. Note, for your app, the results I get when testing: that setting an explicit width/height merely reduces the reliability of the repro, but the crash is still there. If you absolutely need to set a consistent width/height, and want a more consistent repro, here's what I've found tends to work (for me):

First set it to flex:1. Build & run the app, and switch out so that it crashes.
Now set it to width: 400, height:400, or whatever you like, and once again build & run.

Following the steps above, I'm able to get a nearly consistent repro even setting an explicit width/height. Wanted to let you know in case it might still be a problem in your app.


GUVNOR-2260: Guided Decision Table V&V - Improve initial analysis performance

drools-wb
(master) http://github.com/droolsjbpm/drools-wb/commit/60aaa964b
(6.3.x) http://github.com/droolsjbpm/drools-wb/commit/586f86942

Thanks @manstis

Merged w/o review as @Rikkola is probably the only person who has existing knowledge of this code.. and he's sunning himself somewhere on vacation.


Obey stripInternal compiler option

Is your feature request related to a problem? Please describe.
Some properties need to be public so other parts of the module can read them but undocumented to external packages.
Describe the solution you'd like
If a @internal js-doc comment is found don't emit documentation for it if the stripInternal flag is set to true.
Additional context
Typedoc has an excludeInternal option but it seems more natural to use the compiler option already there.
Let me know if you like the idea and I'll make a pr.

Heads up: just implemented the feature, it's gonna be in the upcoming 0.2.0 release :).


License File

Hi,
Thanks for creating xlsx_stream, this looks really useful for me as I have a reports generations processing getting killed by OutOfMemory using elixlsx to build the file 👍
Could you please add a License file to the repo?
I saw it is MIT in the package metadata, but having the MIT license in the repo would clarify.
Thanks again!

done. I will try to put together a proper README file, but this library is much more lower level than other libraries that create xlsx files, the value added here is very small and most of the work is done by xml_stream & zstream library. You need to be somewhat familiar with the xlsx specification. On the plus side, anything that can be done could be done via this approach. Custom styles etc could be easily added. Yes and this library is precisely written because we can't afford to keep everything in memory.

Thanks! Looking forward to the README, but the test looks like it shows how to get the complete file working 👍


DataLogger: odd behavior when dataset is empty

Issue: After adding a logger X axis is removed and then it crash when zooming if i had froze that axis. Can't find a way to add an axis to it. Adding a bottom axis to the logger doesnt change anything sadly.
ScottPlot Version: 5.0.21
Code Sample:
On WPF I've done that.
 Loaded += Graph.Plot.Add.DataLogger();

Hi @TenebrosFR, thanks for reporting this!
I discovered the issue relates to the automatic axis management and you can fix this by disabling it until you have data:
var dl = formsPlot1.Plot.Add.DataLogger();
dl.ManageAxisLimits = false;

However I'll make a code change now that will fix this behavior in the next release 👍

Changes made by https://github.com/ScottPlot/ScottPlot/commit/78262f5228db0ad1934787ce96b0568f798100d4 in DataLogger.cs were inadvertedly reverted in https://github.com/ScottPlot/ScottPlot/commit/0db48762150150d6521b71754133040c7a8645d1


Create console commands to edit data

Allows the editing of the data that normally is given by mods at runtime.

Added in #30


Wiki Tutorial 5 Missing Return on toString()

See title. I am having trouble seeing how to edit the wiki, otherwise I'd do it myself

Good catch, thank you for letting me know, all fixed now.


Update tendermint light client contract

Updated on berlin only.

This issue won't arise on the mainnet. So, on backlog for now.

Maybe consider this while upgrading for hopchain..


Add exec_config_source support to ConfigSource, allowing secrets to be generated by local scripts

Description:
There are circumstances where we want to use our xds control plane to push configuration to envoy, but the control plane does not have the necessary information available to it to allow it to push a fully formed resource.  One specific example of this is secrets which are only available on the instance itself – or secrets which may be known to the control plane, but are in an encrypted form and need decrypting on the instance before they can be consumed by envoy.
I've written up an outline of a design to address this use case

Thanks for the feature request. I'm not thrilled with building execute directly into the API, as it's highly environment dependent what this means and what the capabilities are. I think it would be better to just have an extension point here if there isn't one already such that you can build your own local execute extension. cc @envoyproxy/api-shepherds for thoughts.

I agree, adding this general-purpose mechanism to ConfigSource seems like overkill.
If the goal here is to get TLS certificate data from an external command, I think a better approach would be to use the CertificateProvider framework being built in #19582.

I like the idea of a config provider extension point that Matt suggests. It's just a generic extension point that will have an API to act as an xDS provider. Then @jamesmulcahy can implement this exec as an extension.

I think we should support an in-tree extension point, and then you can maintain a private extension for your use case? Does that work?

Yeah, that works for us!

@jamesmulcahy will you folks take on the implementation work here?

@htuch Sorry for the delay in replying; I was out on vacation.
Yes, we plan to take this on, but don't have line of sight to a specific point in time when we will get to this -- we're juggling a few other things at the moment.


Website doesn't work

http://www.williballenthin.com/registry/ is giving me a 404 Not Found error.

this GitHub repository is the canonical location for python-registry going forward

I've created a PR to update the URL in setup.py to point to GitHub.
I would also suggest changing the URL at the top of the GitHub page to point to https://pypi.org/project/python-registry/


Item names in Table 2

Is it possible to have informative item names in Table 2? Maybe not...

as discussed we close this


Revert "Make Cask::Artifact::Installer typesafe"

Reverts Homebrew/brew#18080

I think this can be closed now? @SMillerDev

Yeah, seems like it's fixed properly now.


Puppet wants to start a running instance

Using a manifest produced with puppet resource ec2_instance, I receive the following error:
Notice: /Stage[main]/Main/Ec2_instance[cassandra1]/ensure: current_value running, should be running (noop)

If the instance is already running (which it is), puppet should not attempt to start it.

Pretty sure that has been resolved with this https://github.com/puppetlabs/puppetlabs-aws/pull/251/commits

Ah, this appears so.  Running from master no longer has this issue.  Could we get a release cut to the forge for future puppet module installs?

@zleswomp perfect timing. We should be releasing 1.3.0 anytime soon, it was tagged just yesterday: https://github.com/puppetlabs/puppetlabs-aws/tree/1.3.0

Thanks @garethr!


Hang in overview page

I have this error... I can only see system information from RAM section all is loading in progress...
here the error
overview:127 Uncaught TypeError: Cannot read property 'wan' of null
at overview:127
at XMLHttpRequest.xhr.onreadystatechange (xhr.js?v=git-18.138.35484-521554f:75)
@jow-

Please provide the output of http://<IP_ADDRESS>/cgi-bin/luci?status=1 (change IP address accordingly)

{"swap":{"free":33550336,"total":33550336},"conncount":725,"leases":[{"expires":32717,"macaddr":"30:07:4D:1B:EE:6C","ipaddr":"<IP_ADDRESS>","hostname":"Galaxy-S8"},{"expires":27602,"macaddr":"9C:B6:D0:EC:F5:45","ipaddr":"<IP_ADDRESS>","hostname":"Ansuel-XPS"}],"leases6":[],"memory":{"buffered":9936896,"total":490807296,"shared":2965504,"free":374284288},"uptime":10622,"wifinets":[{"device":"radio0","networks":[{"ifname":"wlan0","disabled":false,"encryption":"mixed WPA/WPA2 PSK (CCMP)","bssid":"DC:EF:09:F2:5D:51","mode":"Master","quality":77,"noise":-103,"ssid":"No More Lag 5Ghz","link":"/cgi-bin/luci/admin/network/wireless/radio0.network1","assoclist":{"9C:B6:D0:EC:F5:45":{"rx_short_gi":true,"noise":-103,"rx_mcs":9,"rx_vht":true,"rx_mhz":80,"rx_nss":2,"tx_vht":false,"tx_ht":false,"tx_rate":22400,"tx_packets":813444,"tx_mhz":20,"rx_packets":473649,"inactive":2,"rx_ht":false,"rx_rate":866700,"signal":-63},"30:07:4D:1B:EE:6C":{"tx_mcs":9,"noise":-103,"tx_ht":false,"rx_vht":false,"rx_mhz":20,"tx_nss":2,"tx_short_gi":true,"tx_vht":true,"tx_rate":866700,"tx_packets":6731,"tx_mhz":80,"rx_packets":11037,"inactive":5074,"rx_ht":false,"rx_rate":24000,"signal":-49}},"txpoweroff":0,"bitrate":444.5,"txpower":30,"name":"Master "No More Lag 5Ghz"","channel":104,"country":"ZA","signal":-56,"up":true,"frequency":"5.520"}],"name":"Qualcomm Atheros QCA9984 802.11ac Wireless Controller (radio0)","up":false},{"device":"radio1","networks":[{"ifname":"wlan1","disabled":false,"encryption":"mixed WPA/WPA2 PSK (CCMP)","bssid":"DC:EF:09:F2:5D:52","mode":"Master","quality":0,"noise":-90,"ssid":"No More Lag","link":"/cgi-bin/luci/admin/network/wireless/radio1.network1","assoclist":[],"txpoweroff":0,"txpower":30,"name":"Master "No More Lag"","channel":1,"country":"ZA","signal":0,"up":true,"frequency":"2.412"}],"name":"Qualcomm Atheros QCA9984 802.11bgn Wireless Controller (radio1)","up":true}],"wan":{"proto":"pppoe","ipaddr":"<IP_ADDRESS>","link":"/cgi-bin/luci/admin/network/network/wan","netmask":"<IP_ADDRESS>","gwaddr":"<IP_ADDRESS>","expires":-1,"uptime":191,"ifname":"pppoe-wan","dns":["<IP_ADDRESS>","<IP_ADDRESS>"]},"localtime":"Sun May 20 01:40:41 2018","connmax":16384,"loadavg":[15808,17376,13344]}

@jow-

Is the output you see in the browser really preinted like this? ..."name":"Master "No More Lag 5Ghz""...? Seems the escaping of the inner quotes is broken.

Is the output of this command: lua -lluci.jsonc -e 'print(luci.jsonc.stringify([[Master "No More Lag"]]))' exactly "Master \"No More Lag\"" ?

Which browser do you use?

Chrome

Unfortunately I am unable to reproduce it here. Please check if you get any network errors or similar when open the debugger tools with F12.

@jow- i think i found the problem...
time lua /www/cgi-bin/luci  output this time
real    0m 13.33s
user    0m 0.57s
sys     0m 0.18s
i'm on stock, no additional configuration flag... any idea to backtrack all this extra time and slowness?


Add a combineStates function as an initial states collector

It would be great to have a function to collect all the initial states of our app in a single object to be passed to the createStore function, something like a combineReducers partner function to map the initial state taked by each reducer just using the object key names like this:
reducers/counter.js
export const actions = {
    increment: 'INCREMENT',
    decrement: 'DECREMENT'
}

export const counter = (state = 0, { type }) => {
    switch (type) {
        case actions.increment:
            window.localStorage.setItem('counter', state + 1)
            return state + 1
        case actions.decrement:
            window.localStorage.setItem('counter', state - 1)
            return state - 1
        default:
            return state
    }
}

export const initialCounter = async () => await parseInt(window.localStorage.getItem('counter'), 10)

reducers/index.js
import { combineReducers } from 'redux'
import combineStates from '../utils/combineStates'
import { actions as counterActions, counter, initialCounter } from './counter'
import { actions as todosActions, todos, initialTodos } from './todos'
import { actions as userActions, user, initialUser } from './user'

export const reducers = combineReducers({
    counter,
    todos,
    user
})

export const actions = {
    ...counterActions,
    ...todosActions,
    ...userActions
}

export const initializers = (async () => await combineStates({
    counter: initialCounter,
    todos: initialTodos,
    user: initialUser
}))()

index.js
import App from './components/App'
import { createStore } from 'redux'
import React from 'react'
import ReactDOM from 'react-dom'
import { initializers, reducers } from './reducers'
import registerServiceWorker from './registerServiceWorker'

const initializeApp = async () => {
    const store = createStore(
        reducers,
        await initializers,
        window.__REDUX_DEVTOOLS_EXTENSION__ && window.__REDUX_DEVTOOLS_EXTENSION__()
    )

    const render = () => {
        ReactDOM.render(<App store={store} />, document.getElementById('root'))
    }

    store.subscribe(render)
    render()

    registerServiceWorker()
}

initializeApp()

Reducers should not be accessing external values like localStorage.  The code may run, but that's not how reducers are intended to be written.
Redux lets you pass in an app-wide preloadedState argument to createStore.  It's up to you to decide how that data is put together, if you choose to do so.

I understand your point @markerikson, but what I was trying to show was not the setItem part, but the combineStates in the reducers/index.js.


Address perspective and channel reuse issues through introducing 'endpoint' concept

2021.08.09 - Tried to create a non recursive definition of endpoint.
Summary
Issue
The AsyncAPI community acknowledges that there are significant issues related to the understandability of the spec for new users, the flexibility to address various async topologies and the reuse of channels across multiple applications.
Proposed Resolution
To address these issues, the proposal allows:

Decoupling channels from applications and implementation details.  Channels instead exist as a decoupled, logical means of exchanging messages.
Explicitly describing the operations of all entities within an async topology

Result
The proposal gives users the ability within AsyncAPI to describe how:

an endpoint does interact with  logical channel(s)
an endpoint may interact with one application
a class of endpoints may interact with  logical channel(s)

Technical Summary
The proposal introduces a top-level endpoint entity to AsyncAPI, and relaxes restrictions on mandatory AsyncAPI properties and entities. In order to ensure consistent tooling behavior in the face of this new flexibility, it also introduces several business rules.
General Discussion
In v2.1 an AsyncAPI spec "MUST describe the operations an application accepts." Stated another way, an AsyncAPI v2.1 spec describes how an endpoint may interact with a single application. When used for code generation, the single application is assumed to implement the inverse of what is described in the spec.  In other words, if interacting endpoints can subscribe from named application, the spec assumes that named application publishes those messages.
For many use cases this is sufficient. This tends to true with users that are familiar with OpenAPI and implementing asynchronous client-server interaction.
However, as noted in the perspective issue, the mental gymnastics of "inverse implementation"  remain a challenge for both new and experienced users, particularly in the context of code generation.
Additionally, AsyncAPI struggles to capture some async topologies. For instance, broker-mediated topologies are not exclusively (or even predominantly) one-to-one interaction.  In fact, async architectures that use event brokers are typically a network of decoupled nodes interacting in complex ways. Here the assumption of inverse relationships fails, as components can:

Interact in a one-to-many-fashion, serving as information provider to multiple components, while simultaneously serving as information consumer from multiple components.
Selectively choose which events to receive from information providers
Reuse an existing channel, either sending additional messages into the channel, or retrieving messages from the channel.

Discussion of Specific Proposed Changes
Address additional use cases and issues by allowing explicit Endpoints
☐ Introduce a top-level endpoint entity to AsyncAPI.
An endpoint is entity that sends, receives, or sends and receives messages via a channel.  In AsyncAPI, an endpoint object represents either the implementation of a single endpoint, or a defines the capabilities of a generic class of endpoint.
In AsyncAPI an endpoint explicitly defines, from the perspective of the endpoint:

What operation(s) does/can the endpoint implement?

Using a reference, what channels does the endpoint interact with?
How does this endpoint interact with the channel?  Does it send data to the channel? Does it receive data from the channel? Or both?

Optionally, for each operation, which endpoint-specific protocol bindings are present?

If sending messages to the channel, then what is the address (e.g. Kafka topic)
If receiving data from the channel, the what is the address (e.g. IBM MQ queue name)

The resulting AsyncAPI structure looks like:

The introduction of endpoint and the resulting loose coupling addresses both the perspective and the channel reuse issue. Because endpoints are defined from their own perspective, using intuitive verbs, the new user experience improves and code generation becomes less problematic.  And by decoupling endpoints from channels by using references, channels can be reused by multiple endpoints.
Further Abstract Channel by genericizing verbs
The existing verbs in v2.1 (publish and subscribe) are linked to the pub-sub model of async interaction.  Queues, mailboxes, websocket endpoints all can serve as asynchronous channels, but do not require either publishing or subscribing.
This proposal
☐ Deprecates the subscribe verb, replaces with endpointSends.
☐ Deprecates the publish verb, replaces with endpointReceives
(During a transition period, tooling which reads AsyncAPI specs should continue to accept subscribe and publish.  Tooling which writes AsyncAPI specs should be updated to use endpointSends and endpointReceives.)
This change further abstracts the base Channel concept away from any implementation choice.  The implementation details can in turn be specified as bindings, either attached to the channel or the endpoint-operation, depending if they apply to the channel, or to an individual endpoint’s use of the channel.

On a practical level, further abstraction of Channel allows point-to-point asynchronous communication, either brokered or unbrokered, to be represented by Channels without bending the common definitions of "publish" and "subscribe".  This in turn increases consistency across a wider range of interaction styles.
Emphasize multiple physical realizations of underlying logical model
In examples to follow, the endpoint, channel and message entities are frequently presented as separate files.  However, this should not be taken as a requirement.  In fact, the increased use of references allows for a wide range of implementation options including:

Separating endpoints, channels and messages into separate files
Combining all entities into a single file
Dividing up entities by business domain
Utilizing a schema registry or event management portal in lieu of files

To facilitate this flexibility, the proposal
☐ Makes optional all top level entities (info, servers, channels, endpoints, components) .
The spec is unopinionated on what the best way to organize, govern, persist or access AsyncAPI.   In fact, a single organization may use different physical AsyncAPI representations of the same underlying set of logical async interactions.  And, depending on use case, an organization may choose to present only a piece of the overall architecture to an endpoint for reasons of security, simplicity, etc.
Differentiate Interface and Implementation when using endpoints
Currently AsyncAPI defines how a component MAY interact with the application.  This reflects the intention of the document to serve as a true API, closely paralleling OpenAPI. For consistency and backwards compatibility, this will continue to be the assumption in the absence of explicitly defined endpoints.
That said, a separate and legitimate use of AsyncAPI is generating and documenting a particular endpoint’s implementation.  OpenAPI (and REST) is tightly coupled to the HTTP/S protocol, so that verbs, URL, etc. can be assumed to be implemented using HTTP/S.  In contrast, the asynchronous world uses a wide variety of protocols.  Evidence of this is seen by provision of the specific binding information present in many AsyncAPI files and the growing number of code generation options.  The need to explicitly provide implementation information in the asynchronous world forces a more explicit spec that allows for implementation details to be recorded in a systematic way.
To accommodate this reality, this proposal:
☐	Adds an optional field called intent to endpoint with allowed values interface and implementation
☐	Adds an optional field called  required to operations, with allowed values true and false
intent indicates whether the purpose of this endpoint definition is an interface (defines a of class of endpoint) or the implementation of a particular endpoint.

For an interface endpoint, operations marked as required:true must be present in implementations of that interface.  For example, if there is a an interface called StreetLight with a required operation, then an implementation of that interface (StreetLightAt123MainStreet), must implement that operation.

☐ Adds the following business rules:

If the intent is implementation, it is assumed that the endpoint definition describes an implemented instance of the endpoint.  Thus all operations present in the file will be assumed to be implemented.
If the intent is interface, it is assumed to be an interface, describing possible operations that the endpoint MAY implement.
The default value of intent is interface, in keeping with v2.1 spec's view of the world.
If the endpoint is an interface,  endpoints which implement the interface MUST implement the operation.
The default value of required is false (not required)

Clarify Inheritance rules when using references
To achieve decoupling and reuse, the proposed spec relies heavily on references from one entity to another.  This (and the introduction of separate implementation and interface concepts) forces the spec to formalize the requirements with regards to inheritance when referencing another entity.
☐ Adds the following business rules:
In the case where Entity A references another entity B (e.g. another endpoint, channel, message), Entity A MUST inherit all the properties of Entity B (and likewise all the Entities that have been previously referenced). Entity A MAY modify a property of Entity B (and previously referenced entities) IF AND ONLY IF ONE OR MORE OF THESE CONDITIONS ARE TRUE:

Endpoints may choose exclude optional operations (those not marked as required:true)
There are parameters within the property (e.g. parameterized topic string).  If parameter is restricted via type, enumeration or pattern, Entity A MUST follow the restrictions.

Summary of Proposed Changes
All changes are non-breaking.
☐ Deprecate publish in favor of endpointSends
☐ Deprecate subscribe in favor of endpointReceives
☐ Introduce endpoints entity to allow explicit definition of endpoints, including whether the endpoint represents an interface or an implementation
☐ Allow for messages to be associated directly with channels
☐ Make all top level entities optional
☐ Make verbs within the channel definition optional.
These changes evolve AsyncAPI towards more robust enterprise functionality and resolve lingering issues that could prevent wider adoption.
Specific Examples
WORK IN PROGRESS
To establish a common frame of reference, the following examples use the Streetlights tutorial from AsyncAPI.com as a baseline.  As described in the tutorial, the company is called "Smarty Lighting and you do smart-city lighting systems".  To better explain the proposal's implications, each example adds additional complexity to the baseline tutorial.
As-is Streetlights  with AsyncAPI v2 Implicit endpoint
Demonstrates: Backwards compatibility with existing AsyncAPI specs
Adds to Streetlights: Nothing
The baseline Streetlights tutorial describes the API of a Message Broker.
The AsyncAPI v2.1 representation of the Streetlights is:
Streetlight API
channels:
  light/measured:
    publish:
      summary: Inform about environmental lighting conditions for a particular streetlight.
      operationId: onLightMeasured
      message:
        name: LightMeasured
		<<details omittted>>

As there are no explicit endpoints, it is assumed the API describes:

how an implicit endpoint may interact with one endpoint

So, the implicit clients may choose to send LightMeasured events to the event broker.
It's important to note this would be valid AsyncAPI file in both v2 and v3.  Tooling would continue to read the "publish" and "subscribe" verbs, although it would be expected that new versions of tooling would write "endpointSends" and "endpointReceives"
Here we can see the two issues:

Perspective issue: AsyncAPI code generators create an application that subscribes to the events.  This has proven to be difficult to explain to both new and existing users.

Channel reuse: the light/measured channel definition is tightly coupled to the application and to the pub-sub architecture.  If another application wishes to use light/measured, it would need to be included in its own AsyncAPI definition.

Explicit endpoints (AsyncAPI v3 style)
Demonstrates: More explicit definitions of actors could be beneficial in some situations
Adds to Streetlights: Conversion to AsyncAPI v3
In proposed v3 it becomes possible--though not mandatory--to explicitly create endpoints and/or classes of endpoints. The same Streetlights example becomes:
endpoint_streetlight.yaml
endpoint:
	StreetLight:
		endpointSends:
			light/measured
				$ref: /uri/channels/light/measured

channels.yaml
channel:
	light/measured:
			message:
				name: LightMeasured

As there are explicit endpoints, it is assumed the API describes:

how an explicit endpoint can interact with one to many logical channels

The potential benefits of using the v3 approach?

Perspective issue is less of a challenge.  When applying a code generator, it is clear that the StreetLight sends LightMeasured events

Channel reuse
Demonstrates:  Increased ability to reuse channels
Adds to Streetlights: Additional endpoints and channels
In proposed v3 it becomes possible--though not mandatory--to explicitly create endpoints and/or classes of endpoints. As endpoints interact in increasingly complex ways, decoupling the endpoints from channels increases reuse.
To demonstrate, this example adds a Control Hub endpoint, which receives light measurements from the streetlight.  In turn, it sends out commands which can turn the streetlight on.  Control Hub and Streetlight both reuse the same two channels.
endpoint_streetlight.yaml
endpoint:
	StreetLight:
		endpointSends:
			light/measured
				$ref: /uri/channels/light/measured
		endpointReceives:
			control/lightOn
				$ref: /uri/channels/control/lightOn

endpoint_controlhub.yaml
endpoint:
	ControlHub:
		endpointSends:
			control/lightOn
				$ref: /uri/channels/control/lightOn
		endpointReceives:
			light/measured
				$ref: /uri/channels/light/measured

channels.yaml
channel:
	light/measured:
			message:
				name: LightMeasured
	control/lightOn:
			message:
				name: LightControl

The potential benefits of using the v3 approach?

Channel reuse: as the streetlight references the channel, rather than having a separate copy in each of their AsyncAPI specs, it can be reused by new endpoints. (Note, that although the channels here are persisted in a file, they could instead be defined in a common file in GitHub, a database, a repository or other store.)

Use of Interface/Implementation and required tags
Demonstrates:  Additional possible interpretations of AsyncAPI
Adds to Streetlights: Additional streetlights, including some of which are external to the organization and describe implementations.
As event APIs become more sophisticated, there is an increased need for flexibility of inpretations and enterprise functionality.
In this example, the Streetlight API is provided to outside organizations. Streetlight owners can graciously crowd source their light measurements by sending them to Control Hub. However, external organizations do not need to receive Control Hub lightOn events.
To emphasize this, the intent of interface_streetlight.yaml is set to interface.  And while the light/measured operation is marked as required:true, the control/lightOn operation remains optional (the default value).
In contrast the implementation (endpoint_streetlight_833Sparrow.yaml) is set to intent:implementation.
endpoint_streetlight_833Sparrow.yaml
endpoint:
	StreetLight833Sparrow:
		intent:implementation
		$ref: /uri/endpoints/StreetLight
		endpointSends
			light/measured

interface_streetlight.yaml
endpoint:
	StreetLight:
		intent:interface
		endpointSends:
			light/measured
				required:true
				$ref: /uri/channels/light/measured
		endpointReceives:
			control/lightOn
				$ref: /uri/channels/control/lightOn

endpoint_controlhub.yaml
endpoint:
	ControlHub:
		intent:implementation
		endpointSends:
			control/lightOn
				$ref: /uri/channels/control/lightOn
		endpointReceives:
			light/measured
				$ref: /uri/channels/light/measured

channels.yaml
channel:
	light/measured:
			message:
				name: LightMeasured
	control/lightOn:
			message:
				name: LightControl

Here, the third possible intpretation of AsyncAPI is shown:

how an explicit endpoint does interact with one to many logical channels

In addition, enterprises can advertise their evented API products while clearly showing the functionality that the external API can and must provide.
Use of inheritance to specify which schema an endpoint uses amongst many in a channel
Demonstrates:  Inheritance and override logic
Adds to Streetlights: Multiple possible messages within in a channel
As applications evolve, they will introduce breaking changes in the messages that they send.  These breaking changes can cause failures for downstream applications. This is particularly true in brokers such as Kafka, where topics persist messages indefinitely, so that there may be multiple version of a message (or multiple message types) on the topic.
The decoupling of endpoints from channels allows implementers multiple ways to address this issue.
Wild West
Channel does not specify associated messages.  Instead, each endpoint specifies which message it sends.  Implies a lack of central governance, which means that applications receiving messages must be ready to adjust to breaking changes.
endpoint_controlhub.yaml
endpoint:
	ControlHub:
		endpointReceives:
			light/measured
				$ref: /uri/channels/light/measured
					message:
						$ref: '/uri/components/messages/LightMeasuredv1'
		endpointSends:
			control/lightOn
				$ref: /uri/channels/control/lightOn
					message:
						$ref: '/uri/components/messages/LightOnv1'

channels.yaml
channel:
	light/measured:
	control/lightOn:

Channel centric
Each channel specifies a single associated message, or a list of associated messages using oneOf.  In turn, each endpoint specifies which message it sends and/or receives.  If a channel contains a list of associated messsages, endpoints must select an option from that list .  This topology likely implies some sort of central governance or tooling of shared channels, as applications must modify both their own AsyncAPI spec and that of the shared channel(s).
endpoint_controlhub.yaml
endpoint:
	ControlHub:
		endpointReceives:
			light/measured
				$ref: /uri/channels/light/measured
		endpointSends:
			control/lightOn
				$ref: /uri/channels/control/lightOn
					message:
						$ref: '/uri/components/messages/LightOnv2'

channels.yaml
channel:
	light/measured:
			message:
				oneOf:
					- $ref: '/uri/components/messages/LightMeasuredv1'
	control/lightOn:
			message:
				oneOf:
					- $ref: '/uri/components/messages/LightOnv1'
					- $ref: '/uri/components/messages/LightOnv2'

Defer to schema registry
Lastly, enterprises could defer schema management to a schema registry. Rather than list specific versions, references point to a schema registry, which can be used at either code-time, compile-time or run-time.
endpoint_controlhub.yaml
endpoint:
	ControlHub:
		endpointReceives:
			light/measured
				$ref: /uri/channels/light/measured
		endpointSends:
			control/lightOn
				$ref: /uri/channels/control/lightOn

channels.yaml
channel:
	light/measured:
			message:
				$ref: 'http://schemaregistry.com/components/messages/LightMeasured#latest'
	control/lightOn:
			message:
				$ref: 'http://schemaregistry.com/components/messages/LightOn#latest'

Use of Interfaces for external API products
Forthcoming
Specifying Binding details.
Under this proposal, channels become much more logical.  Channels know only the following

Message can be sent to the input of  a channel
Messages can be received from the output of a channel
The channel is addressable
As a dumb pipe, messages entering the channel are the same as messages exiting the channel (@jhigginbotham and I disagree on this one)

Optionally, and to align with the schema registry use case, AsyncAPI allows channels to know

the message format(s) allowed within the channel

Making channels  logical objects defers implementation details to protocol-specific bindings.  This compartmentalizes implementation details, which has several nice properties:

Workarounds, like the unofficial AsyncAPI vocabulary translator for WebSocket users should become less needed, as protocols bindings can be individualized without translating what "publish" and "subscribe" mean in a particular context.
Swapping out implementations, like switching from Kafka to RabbitMQ or vice versa, don't mean changing the logical structure of your enterprise, just the physical bindings.

Symmetrical bindings- Input binding same as output binding
The simplest case is one in which the input binding  will always be the same as the output binding.  This is the case in Kafka.  Endpoints sending data use the same topic as endpoints receiving data. In this case, existing bindings should work and should be at the channel level.
channel:
	light/measured:
			message:
				oneOf:
					- $ref: '/uri/components/messages/LightMeasuredv1'
					- $ref: '/uri/components/messages/LightMeasuredv2'
			bindings:
				kafka:
					groupId:
						type: string
						enum: ['myGroupId']
					clientId:
						type: string
						enum: ['myClientId']
					bindingVersion: '0.1.0'
	control/lightOn:
			message:
				$ref: '/uri/components/messages/LightOnv1'

Asymmetrical bindings-  Input binding different than output binding
This  needs more work, and I would love input from @nictownsend, @dalelane, @jhigginbotham  and @damaru-inc  on this.
On the other hand, several async protocols can have asymmetric channels, where input and output bindings are are not the same (e.g. AMQP topic to queue, IBM MQ queue to topic, Solace SMF topic to queue).   To accommodate these use cases, the spec needs to have the ability to specify different channel input and output bindings.
Ideally, to keep the channel as logical as possible, the channel object itself would not know if it's symmetrical or asymmetrical.  That implementation detail would be left to the binding.
The question is where asymmetric bindings belong.   Thinking about things, there seem to be multiple possibilities:

The binding at that point belongs to a specific action, either sending data to the channel, or receiving data from the channel.  As such it should be housed under the endpoint-operation.  But that is tough for channel registries, because if you are discovering a channel you don't really know how to connect to the channel.

endpoint:
	ControlHub:
		endpointReceives:
			light/measured
				$ref: /uri/channels/light/measured
					ibmmq:
						destinationType: queue
						queue:
							objectName: myQueueName
		endpointSends:
			control/lightOn
				$ref: /uri/channels/control/lightOn
				bindings:
					ibmmq:
						destinationType: topic
						topic:
							objectName: myTopicName

The bindings belong at the channel, with input and output stanzas, since they are really how the channel is implemented.  This is the option that appeals to me the most, but I'm not sure how it would work with backwards compatibility.

channel:
	light/measured:
			message:
				oneOf:
					- $ref: '/uri/components/messages/LightMeasuredv1'
					- $ref: '/uri/components/messages/LightMeasuredv2'
			bindings:
				ibmmq:
					input:
						destinationType: topic
						topic:
							objectName: myTopicName
					output:
						destinationType: queue
						queue:
							objectName: myTopicName
					bindingVersion: 0.1.0

Async Request/Reply (Websockets, NATS)
In general, these can be described as two different channels.  Modifying the @derberg example:
endpoint:
	KrakenServer:
		intent:implementation
		endpointReceives:
			krakenCommands
				$ref: /uri/channels/krakenCommands
		endpointSends:
			krakenResponses
				$ref: /uri/channels/krakenResponses

endpoint:
	KrakenClient:
		intent:interface
		endpointSends:
			krakenCommands
				$ref: /uri/channels/krakenCommands
		endpointReceives:
			krakenResponses
				$ref: /uri/channels/krakenResponses

channels:
  /:
    krakenCommands:
      operationId: krakenCommands
      message:
        oneOf:
          - $ref: '#/components/messages/ping'
          - $ref: '#/components/messages/subscribe'
          - $ref: '#/components/messages/unsubscribe'
    krakenResponses:
      operationId: krakenResponses
      message:
        oneOf:
          - $ref: '#/components/messages/pong'
          - $ref: '#/components/messages/heartbeat'
          - $ref: '#/components/messages/systemStatus'
          - $ref: '#/components/messages/subscriptionStatus'

References to servers from bindings
Forthcoming

Love how much effort you've put into this proposal 👏 ❤
I have a few comments/questions:

I don't really get what's an endpoint. Is it a node in the architecture? In the definition of "endpoint", you use "endpoint" as part of the definition and that got me lost 😅 It says: "An endpoint represents either the implementation of a single endpoint, or a defines the capabilities of a generic class of endpoint." Recursion alert 🚨 😄
I love the effort you've put into making it backward compatible. IMHO, we should get rid of whatever is making the spec inconsistent so we don't carry this pain forward. We'll keep supporting v2 for some years so that's not a problem. If someone wants to stay on v2 they can.
Unless I'm missing something, I think this thing about the intent:implementation or intent:interface is just going to make things more complex for no reason. This may be related to point 2 above though.
I love that you've solved the channel reuse problem at the same time. I think this is key.
I love that you can override a channel's message from within the endpoint's operation. Even though it's "wild west" 😄 it's super useful in some cases.
Lots of your examples are not viable because you're combining $ref with other stuff (e.g., intents example) or making the $ref line the parent of something else (e.g., wild west example). $ref has a special meaning and it can be dereferenced (e.g., replaced by the referenced object) at any time. Having attributes at the same level is not allowed and those libraries allowing you to do that are combining the referenced object with the additional attributes. That would result in invalid referenced objects.

I wonder how would have modeled this proposal if you remove the backward compatibility constraint. I challenge you to reimagine it 😄

@fmvilas awesome feedback, thank you.  On point 6, I see what you mean.  I'm not as good at JSON as I should be.  Could we do something similar to OpenAPI spec:
components:
  schemas:
    Pet:
      type: object
      discriminator:
        propertyName: petType
      properties:
        name:
          type: string
        petType:
          type: string
      required:
      - name
      - petType
    Cat:  ## "Cat" will be used as the discriminator value
      description: A representation of a cat
      allOf:
      - $ref: '#/components/schemas/Pet'
      - type: object
        properties:
          huntingSkill:
            type: string
            description: The measured skill for hunting
            enum:
            - clueless
            - lazy
            - adventurous
            - aggressive
        required:
        - huntingSkill
    Dog:  ## "Dog" will be used as the discriminator value
      description: A representation of a dog
      allOf:
      - $ref: '#/components/schemas/Pet'
      - type: object
        properties:
          packSize:
            type: integer
            format: int32
            description: the size of the pack the dog is from
            default: 0
            minimum: 0
        required:
        - packSize

We're already doing that at Schema Object level (same as in OpenAPI). The Schema Object is a pure JSON Schema object, not something OpenAPI or AsyncAPI defines.

That was a long read! well done.
I think we should get rid of backward compatibility. Spec is not an API, we should just release new version and improve it best way we can to make sure others migrate + have as powerful converters as possible

@jessemenning I assume you want to champion this through? 🙂 Or can we consider this issue as needs champion? 🤔

@jessemenning do you want to drive it further?


include Edinburgh Uni in credits

Hi,
should probably include Edinburgh University in the credits at bottom of https://www.ebi.ac.uk/pride/archive/crosslinking
I am employed there on the 3d proteomics grant.
(Could add it as second affiliation of Juri Rappsilber.)
Cheers,
Colin

Update in this PR https://github.com/PRIDE-Archive/pride-web/pull/340


Skipping static resource max size is 2.1 MB causes service worker to not cache main.js.

Not sure if this should be posted here or SWPrecacheWebpackPlugin, but I figured it should be documented somewhere since it was rough to diagnose.
Description
When the webpack JavaScript bundle becomes to large, yarn build throws a warning:
Skipping static resource "/home/austin/cra-swcache-broken-repro/build/static/js/main.4f79027e.js" (2.77 MB) - max size is 2.1 MB
as is mentioned in #2433. This seems to cause SWPrecacheWebpackPlugin to skip adding the bundle to the list of assets it will cache, but this is not clear from the error message that this is the case. This breaks any offline functionality an app might have.
Expected behavior
Either a warning about file size and the file is still added to the cache, or a more explicit warning that this error is coming from or causing an error in SWPrecacheWebpackPlugin and that the resource won't be cached.
Actual behavior
As seen in the snippet bellow, there is no main.js in the generated service-worker.js.
"use strict";function setOfCachedUrls(e){return e.keys().then(function(e){return e.map(function(e){return e.url})}).then(function(e){return new Set(e)})}var precacheConfig=[["index.html","8271cbe9809a6bbeca76    83483ce358f0"],["static/css/main.9a0fe4f1.css","3473922d6aed4c20bb69846d6027cacf"],["static/media/logo.5d5d9eef.svg","5d5d9eefa31e5e13a6610d9fa7a283bb"]],cacheName="sw-precache-v3-sw-precache-webpack-plugin-" ...
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts<EMAIL_ADDRESS>node -v: v7.10.0
npm -v:4.6.1

Then, specify:

Operating system: Arch Linux
Browser and version: Google Chrome Version 58.0.3029.110 (64-bit)

Reproducible Demo
Demo
(Thanks for all the work you all have put into CRA, it has made my life a lot simpler!)

Ideally I want to remove that warning completely (the text is not very useful).
Instead I'd like to show a warning inline in the built file list.

To work around false positives like https://github.com/facebookincubator/create-react-app/issues/2433 I'm going to silence the warning for now.
If more people strongly about this we can add special code to handle this into CRA itself but for now I'd recommend adding a custom postbuild step.
  "scripts": {
    "build": "react-scripts build",
    "postbuild": "node check-service-worker.js",

check-service-worker.js
'use strict';

var fs = require('fs');

var manifest = require('./build/asset-manifest');
var sw = fs.readFileSync('./build/service-worker.js');

Object.keys(manifest).forEach(key => {
  if (key.endsWith('.map')) {
    return;
  }
  var path = manifest[key];
  if (sw.indexOf(path) === -1) {
    throw new Error('Not cached: ' + manifest[key]);
  }
});

If more people get burned by this and ask for this feature we can integrate it more tightly but for now I'm punting on this. If you feel strongly about this and want to help I'm happy to discuss an ideal way to handle this in a follow up issue.

I am having the very same issue here (my vendors bundle is just too large).
So what should be the actual expected behaviour? Why not including the file into the list of cached assets?

I was also burned by suppression of this very important message. My app was 2.2MB, which crossed the limit and thus main.js was left out from cache. Took me a longer than I care to admit to figure out why my app didn't work when there was no network. I finally found this lovely piece of code. By removing it I understood why main.js was not cached.
To fix my app I edited webpack.config.prod.js to contain this:
new SWPrecacheWebpackPlugin({
    // ...
    maximumFileSizeToCacheInBytes: 10 * 1024 * 1024,
}),

I'd say you should restore the message and maybe turn it into a warning instead of error. I admin I didn't quite understand the false positive problem, but having this as a warning won't cause the compilation to fail?


dapr --wait

URL of the docs page
https://docs.dapr.io/zh-hans/operations/hosting/kubernetes/kubernetes-deploy/#wait-for-the-installation-to-complete
How is it currently worded?
您可以使用 --want 标志来等待安装完成。
How should it be worded?
您可以使用 --wait 标志来等待安装完成。
Screenshots

Additional context

@skyao is this something you can help fix?

@hhunter-ms can I fix this typo? if yes please assign me to this.

@sakibian sorry for the delay - I've assigned you to this issue. thanks for your help!

@hhunter-ms Seems I've lost the folder structure correctly or I should look for other Chinese versions of this repository I don't know about.
If you look here:

Edit on page clicked.

Page is not found.

If we go back to the content folder there is only EN version available.

Did I miss something? or does it support the English version only?
Let me know, Thanks

@sakibian hm, good question - @msfussell thoughts?

@skyao checking back in on this - would you be able to take a look?

Closing per @skyao recommendation


generate Helm charts for each service controller

In addition to the kustomize-based manual install method currently used by the KinD-based e2e tests, we need to provide Helm charts for easily installing ACK service controllers.

[x] Push Docker images for built ACK service controllers to the newly-created DockerHub amazon/aws-controllers-k8s Docker repository
[x] Generate standardized Helm chart and values.yaml files for each ACK service controller in a new ack-generate helm CLI command
[x] Create an e2e test that verifies the installation of the ACK service controller via Helm into a KinD cluster
[x] Update the install and setup documentation

Is there documentation for this? I want to install aws-controllers-k8s with helm but having trouble finding docs on it


Brittany "Format Selected"  adds an extra new line

Maybe not so critical, but very, very, very annoying.
To reproduce:

Select a function
Call "Format Selected"
Enjoy an extra newline after your selection

For me new lines are getting added mid-selection or mid-file as well. Using VSCode, this only seems to be the case if I use CRLF line endings, the formatting works fine with LF.

@AlexeyRaga is this with the current master version of hie?  Because I understood that @lspitzner had sorted it out in the current brittany.


[Misdetection] Corrupted HTML file misdetected as ISO

What should the file have been detected as? What has the file been misdetected as?
A html with a lot of null files at the beginning is being detected as ISO.
Please link or attach the misdetected file below (Do NOT upload PII!)
magika_report.html.zip
Additional context
Less confidence would be nice, currently 0.9999

Thanks for reporting. Added this to missdetected samples to keep track of future improvements. (CLA was signed: https://opensource.corp.google.com/signcla/search?q=xiangchen96+)


Method to access Epoch seconds

The current second command returns a value between 0 and 59 - the number of seconds since the start of the last minute. This doesn't let you calculate the elapsed time between two events.
Add a new epochSeconds command that returns the number of whole seconds since 1 Jan 1970

PR Merged


Missing relations when migrating

I found this plugin today and it is exactly what my company needs. Great idea!
I've installed the plugin on a fresh netbox instance and got the following error while running upgrade.sh

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/init.py", line 446, in execute_from_command_line
utility.execute()
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/init.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/base.py", line 414, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/base.py", line 460, in execute
output = self.handle(*args, **options)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/base.py", line 98, in wrapped
res = handle_func(*args, **kwargs)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 91, in handle
self.check(databases=[database])
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/management/base.py", line 487, in check
all_issues = checks.run_checks(
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/checks/registry.py", line 88, in run_checks
new_errors = check(app_configs=app_configs, databases=databases)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/checks/urls.py", line 14, in check_url_config
return check_resolver(resolver)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/core/checks/urls.py", line 24, in check_resolver
return check_method()
File "/opt/netbox/venv/lib/python3.8/site-packages/django/urls/resolvers.py", line 480, in check
for pattern in self.url_patterns:
File "/opt/netbox/venv/lib/python3.8/site-packages/django/utils/functional.py", line 49, in get
res = instance.dict[self.name] = self.func(instance)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/urls/resolvers.py", line 696, in url_patterns
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/utils/functional.py", line 49, in get
res = instance.dict[self.name] = self.func(instance)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/urls/resolvers.py", line 689, in urlconf_module
return import_module(self.urlconf_name)
File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 848, in exec_module
File "", line 219, in _call_with_frames_removed
File "/opt/netbox/netbox/netbox/urls.py", line 9, in
from extras.plugins.urls import plugin_admin_patterns, plugin_patterns, plugin_api_patterns
File "/opt/netbox/netbox/extras/plugins/urls.py", line 28, in
urlpatterns = import_object(f"{plugin_path}.urls.urlpatterns")
File "/opt/netbox/netbox/extras/plugins/utils.py", line 31, in import_object
spec.loader.exec_module(module)
File "/opt/netbox/venv/lib/python3.8/site-packages/netbox_data_flows/urls.py", line 5, in
from . import models, views
File "/opt/netbox/venv/lib/python3.8/site-packages/netbox_data_flows/views/init.py", line 3, in
from .dataflows import *
File "/opt/netbox/venv/lib/python3.8/site-packages/netbox_data_flows/views/dataflows.py", line 82, in
class DataFlowRuleListView(generic.ObjectListView):
File "/opt/netbox/venv/lib/python3.8/site-packages/netbox_data_flows/views/dataflows.py", line 84, in DataFlowRuleListView
pk__in=models.DataFlow.get_disabled_queryset().only("pk")
File "/opt/netbox/venv/lib/python3.8/site-packages/netbox_data_flows/models/dataflows.py", line 219, in get_disabled_queryset
return cls.objects.filter(
File "/opt/netbox/venv/lib/python3.8/site-packages/mptt/querysets.py", line 22, in get_descendants
return self.model._tree_manager.get_queryset_descendants(self, *args, **kwargs)
File "/opt/netbox/venv/lib/python3.8/site-packages/mptt/managers.py", line 200, in get_queryset_descendants
return self._get_queryset_relatives(queryset, "desc", include_self)
File "/opt/netbox/venv/lib/python3.8/site-packages/mptt/managers.py", line 144, in _get_queryset_relatives
if not q:
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/models/query.py", line 324, in bool
self._fetch_all()
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/models/query.py", line 1507, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/models/query.py", line 57, in iter
results = compiler.execute_sql(
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1361, in execute_sql
cursor.execute(sql, params)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/utils.py", line 91, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "netbox_data_flows_dataflow" does not exist
LINE 1: ...ght", "netbox_data_flows_dataflow"."tree_id" FROM `"netbox_da..

I think you forgot to create some relations in the database as they were given in your development environment.

Thanks for your interest :)
For the moment, it is a work in progress and I plan to change most of the models to have something more practical now that I have a working poc, so I recommend you only play with this module in test.
The missing object is the table containing the dataflow, which should be creation in migration 0001, so that's strange. You can try this command to reapply the migrations of the module:
python /opt/netbox/netbox/manage.py migrate netbox_data_flows
I'll test more carefully on a clean install for next push, maybe I missed something.

Thank you for your response. I tried the command unfortunately it didn't resolve the issue. I looked at the first migration file but didnt find any traces of a table being created. But, please bear in mind that i'm not familiar with this kind of migrations

Can you please test again with the new release and let me know if you still have issues with the migrations?

I just tested out the v.0.2.0, works like a charm. Thank you!
Keep up the great work, I'm looking forward to how this project will develop, it has great potential in my opinion

Thank you!


Embed Google Analytics to track web app usage

Embed a GA tag within the Shiny application to give WSDA team feedback on app usage - e.g. where are users logging in from?

@jadeynryan does your team have a Google Tag Manager account already? I believe this will be a prerequisite for set up.

Yes I have an account, but it looks like we need the URL of the app to generate the tag. We can do this after deployment.


Docs website not updating

the link to the example controller implementation in https://sdk.operatorframework.io/docs/building-operators/golang/tutorial/
still points to the old v3 location. I checked the docs source in the repo, and it's already been updated to the new v4 location. Did our docs website not get updated when the release broke?

This should be fixed when we next cut a release during the release process.


Remove TokenUIAuthenticator configurations

Since TokenUIAuthenticator has not been in the code since carbon-3.x.x, its references will be removed

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4372862336
Status: success


⚠ Bofrost.de has degraded performance

In 8c19d02, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1552 ms

Resolved: Bofrost.de performance has improved in 3a7d825 after 1 hour, 4 minutes.


Access aria2 remotely

While accessing Aria2 web UI remotely, the currently downloading files don't show up. The login works fine but it starts with an empty download slot. Is this by design?

hmm ... this is super weird. It should show all the pending downloads from aria2. Are the downloads running in the background?

Yes. As in, I have Aria2 installed on a raspberry pi. Now I access WebUI and initiate downloads from the browser of another computer. So, nothing is running in the foreground so to speak.
When I move to another network, I a clear WebUI page with no ongoing downloads.

that sounds like a clear bug. Are you using the same authentication details and the same security token @n00b12345 ?

@ziahamza I'm using the same authentication (username & password) details. (I don't use a security token, call me extremely lazy)

on the same network, what if you use 2 different browsers to see the webui. Do you see consistent results?

Yes on the same network, regardless of the browser I use, I get consistent results.

This seems to be an aria2 bug @n00b12345 , as webui will not change depending on which network it is running under. ... perhaps report it here: https://github.com/aria2/aria2

Thanks. A small correction @ziahamza. I tried accessing it again from a data connection this time. I was assuming thus far that my browser was automatically providing username and password to Aria Web UI when accessing remotely. I was wrong. I'm not being asked username and password by Web UI when accessing remotely. Terribly sorry about the confusion.

@ziahamza Made a rookie error. Hadn't forwarded port 6800. Terribly sorry. Everything works fine now. Thanks for the help!


Fix some wording nits in the Web Bluetooth article.

@beaufortfrancois Here's my pass over the article. I haven't compiled it to HTML, so you should double-check that I didn't introduce any syntax errors.

LGTM!
@petele Can we merge this please?


XSS vulnerability on Legacy Form block

Create a legacy form, like a contact us form.
You can use this test (From Google Security scan) to expose the vulnerability

<form action="https://SERVER/contact-us/submit_form/1592#formblock1592" id="form" method="POST"><input name="ccm_token" value="1536831794:0c7e943cf7111f1dc9b20c0443a95bc2"><input name="Question1" value=""><input name="Question2" value="'-function(){alert()}()-">\"><aUdio src=x oNerror=alert()><"-'-function(){alert()}()"><input name="Question3" value=""><input name="Submit" value="Send message"><input name="qsID" value="1460794987"><input name="pURI" value=""><input type="submit"></form>

@lagosr could you provide a little more information on how this works? I can't reproduce any effect.
Also, you should consider disclosing possible vulnerabilities on hackerone: https://hackerone.com/concrete5/

I wasn't able to replicate this in my local site so I'm going to close this issue. If you are still able to get this to happen in your up to date copy of concrete5, please open an issue on https://hackerone.com/concrete5 or send an email to<EMAIL_ADDRESS>Thanks!


I need the solution for following

I'm attempting to create a quiz game designed to get users to create more interactive and engaging posts when they use my app. The app is called My Mt. Rushmore. The user will enter a question on a social media site they are logged in on. Then by uploading my app, they will allow people who view their answer to their question, a chance to respond with answers using their own Mt. Rushmore. My Mt. Rushmore app allows people to enter any 4 answers in the spaces allotted and my app will superimpose or replace the 4 president of the United States images on Mt. Rushmore with the images of the people they typed with their answers in the spaces. So, if I made a post on Facebook saying here's my Mt. Rushmore of greatest soccer players ever, Lionel Messi, Christian Ronaldo, David Beckham, and Pele; their facial images would automatically fit into My Mount Rushmore. Others may click the like button and agree or others may disagree and download the app and create their own, Mount Rushmore of soccer players. Either way, each time someone plays the game, they get more likes, more followers, and more engagement with each time they post using my app.

Don't know the solution to this since I'm pretty new to developing, however the idea is brilliant and it seems you got an algorithm already in mind.. hopefully someone will come and answer.. but good luck on the project!!

@thesoftwaresquad
this issue doesn't seem to describe a bug or a feature request
if you need assistance with your code please follow the link I want help writing my application in the new issue menu

@thesoftwaresquad
this issue doesn't seem to describe a bug or a feature request
if you need assistance with your code please follow the link I want help writing my application in the new issue menu

I've already tried this "i want help writing my application" here but stack overflow closed my question automatically so...

but stack overflow closed my question automatically so...

@thesoftwaresquad
I'm not a big fan of SO either, you may try discord, reddit or slack
but the main flutter repo is definitely not the right place for assistance on your personal code

but stack overflow closed my question automatically so...

@thesoftwaresquad
I'm not a big fan of SO either, you may try discord, reddit or slack
but the main flutter repo is definitely not the right place for assistance on your personal code

oh thank you, i will try reddit and slack.... :)


add the cookbook link

removed Beta for both Beam Playground and Tour of Beam
added the cookbook github link to the beam overview

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @svetakvsundhar

R: @damccorm