Inconsistency in Capact CLI getter commands

Description
Currently, we have inconsistency in our Capact CLI.
The capact hub interfaces get command prints only InterfaceRevisions wherecapact ti get prints TypeInstances and associated TypeInstancesRevisions. Printing type which aggregates revisions makes the output more verboase and complicated.
Maybe we should change CLI from caapct ti get to:

capact ti get for TypeInstances and only revisionsVersions (int)
capact tir get for TypeInstanceRevisions - here you can ask for first/latest/previous/given rev/all revs

capact TypeInstanceRevision get  (—resourceVersion=@all)
capact TypeInstanceRevision get —resourceVersion=@latest
capact TypeInstanceRevision get —resourceVersion=@first
capact TypeInstanceRevision get —resourceVersion=@previous
capact TypeInstanceRevision get —resourceVersion=13 = 13th revision

or capact TypeInstanceRevision get 13/@latest/@first/@previous/@all

Nice to have: In the same way, fix the interfaces and impls getters. The other way is to change the capact ti get to print only the TypeInstancesRevisions.
Reason
The inconsistency is problematic in our e2e guides. "Consistent approach is easier to maintain, is easier to rationalize, requires less cognitive overhead, and is easier to migrate or update as new conventions emerge or classes of bugs are fixed". Additionally, when you want to just get the latest TypeInstance revisions value, you need to deal with jq or other parse to do it:
capact typeinstance get {type-instance-id} -ojson | jq -r '.[0].latestResourceVersion.spec.value'

This also affected the recent introduction blog post for Capact where the scenario was based on CLI. It requires from user installation of jq tool. Additionally, we should think about supporting jsonpath directly. We can base on this implementation: https://github.com/kubernetes/cli-runtime/blob/master/pkg/printers/jsonpath.go
More over, we should improve our CLI to get rid of using the kubeconfig and provide an option to install  only our CLI and treat it as only required tool sufficient to interact with Capact. For example, we are not able to tail logs from executed Actions.


Provide kube-aws upgrade path

As of now, kube-aws provides no way to

upgrade a cluster to an new version
apply new configuration to nodes
rotate in new TLS assets

Depends on reproducible assets (#218) being resolved

related: https://github.com/coreos/coreos-kubernetes/issues/230

The kube-aws tool has been moved to its own top-level directory @ https://github.com/coreos/kube-aws
If this issue still needs to be addressed, please re-open the issue under the new repository.


Add support for c++ inheritance between components

Two options - either we re-use the webGME inheritance tracking (through the base pointer) or we make our own pointer that is separate from webGME's inheritance.

update the svg to be a template that can indicate that the component is a derived class.  Could also update to have other controls or indications on it - for library indication for instance.


Applied Element Template is not unlinked, when changing to not supported element type

Describe the Enhancement
When applying an task-specific element template to a task of a specific type (e.g., ServiceTask) and then changing the type of the respective task (e.g., to UserTask), the element template is still present. This is IMO an inconsistent state, since the element template configuration would not allow that template to be applied to a task other than ServiceTask.
Steps to Reproduce

Setup the following example element template

{
    "name": "Mail Task",
    "id": "com.camunda.example.MailTask",
    "appliesTo": [
      "bpmn:ServiceTask"
    ],
    "properties": [
      {
        "label": "Implementation Type",
        "type": "String",
        "value": "com.mycompany.MailTaskImpl",
        "editable": false,
        "binding": {
          "type": "property",
          "name": "camunda:class"
        }
      },
      {
        "label": "Sender",
        "type": "String",
        "binding": {
          "type": "camunda:inputParameter",
          "name": "sender"
        },
        "constraints": {
          "notEmpty": true,
          "pattern": {
            "value": "^[A-z0-9._%+-]+@[A-z0-9.-]+\\.[A-z]{2,}$",
            "message": "Must be a valid email."
          }
        }
      },
      {
        "label": "Receivers",
        "type": "String",
        "binding": {
          "type": "camunda:inputParameter",
          "name": "receivers"
        },
        "constraints": {
          "notEmpty": true
        }
      },
      {
        "label": "Template",
        "description": "By the way, you can use freemarker templates here",
        "value": "Hello ${firstName}!",
        "type": "Text",
        "binding": {
          "type": "camunda:inputParameter",
          "name": "messageBody",
          "scriptFormat": "freemarker"
        },
        "constraints": {
          "notEmpty": true
        }
      },
      {
        "label": "Result Status",
        "description": "The process variable to which to assign the send result to",
        "type": "String",
        "value": "mailSendResult",
        "binding": {
          "type": "camunda:outputParameter",
          "source": "${ resultStatus }"
        }
      },
      {
        "label": "Send Async?",
        "type": "Boolean",
        "value": true,
        "binding": {
          "type": "property",
          "name": "camunda:asyncBefore"
        }
      }
    ]
  }

Apply the template to a serviceTask
Change the task type to userTask
=> The element template is still applied

Expected Behavior
The element template shall be unlinked, if not supporting the respective new task type.
Why
If we don't have this, the user would get to an inconsistent state of the diagram (according to the element template configuration)
Environment

OS: Arch Linux Manjaro
Camunda Modeler Version: develop branch + develop branch bpmn-js-properties-panel on 6th October

Maybe we could listen for commandStack.shape.replace.postExecuted and check whether the template is still applicable. I think we already do similar for other events, cf. https://github.com/bpmn-io/bpmn-js-properties-panel/blob/9f2b08ed0803d2d76f6ad43021873868ba4798c8/lib/provider/camunda/element-templates/cmd/index.js

and check whether the template is still applicable.

I think we cannot check this in all cases since the template might be not available (e.g., file deleted).
Therefore we could:
A) only check this, if the template is still present
B) simply always unlink once you use the wrench
I would opt for B.

B) simply always unlink once you use the wrench

Sounds OK to me. 👍

The solution I've discussed with @azeghers is:

when the template cannot be found it will be unlinked
when the template can be found it will be unlinked if it can't be applied to the new element

CodeSandbox example: https://codesandbox.io/s/restricting-camundamodelertemplate-nyrtp?file=/src/index.js

Closed via https://github.com/camunda/camunda-modeler/commit/d03c2a69a1adc4dcf236afd049b195e40e098a77


Improve readability of usage text

Removes the special mention of -config.file, as it's not required if a
file with the default name "prometheus.conf" is available.
Separates flag and description by a newline to make it easier to read
the flags with long descriptions.

Before:
...

  -storage.local.dirty=false: If set, the local storage layer will perform
      crash recovery even if the last shutdown appears to be clean.
  -storage.local.index-cache-size.fingerprint-to-metric=10485760: The size in
      bytes for the fingerprint to metric index cache.
  -storage.local.index-cache-size.fingerprint-to-timerange=5242880: The size in
      bytes for the metric time range index cache.
  -storage.local.index-cache-size.label-name-to-label-values=10485760: The size
      in bytes for the label name to label values index cache.
  -storage.local.index-cache-size.label-pair-to-fingerprints=20971520: The size
      in bytes for the label pair to fingerprints index cache.

...

After:
...

  -storage.local.dirty=false
      If set, the local storage layer will perform crash recovery even if the
      last shutdown appears to be clean.
  -storage.local.index-cache-size.fingerprint-to-metric=10485760
      The size in bytes for the fingerprint to metric index cache.
  -storage.local.index-cache-size.fingerprint-to-timerange=5242880
      The size in bytes for the metric time range index cache.
  -storage.local.index-cache-size.label-name-to-label-values=10485760
      The size in bytes for the label name to label values index cache.
  -storage.local.index-cache-size.label-pair-to-fingerprints=20971520
      The size in bytes for the label pair to fingerprints index cache.

...

Looks fine for those long flag names.
If it doesn

@fabxc What about this?

LGTM. Thanks for giving things another look.


IoUring: Refactor IoUringIoOps to better match the underlying io_urin…

…g_sqe
Modification:
We should be able to support any io_uring operation in the future for this we should allow to setup the right struct.
Modifications:

Change constructor to match underlying struct
Remove public getters as these are only used internally and might change in the future
Rename static fields

Result:
More flexible implementation for io_uring

@chrisvest yeah but the leak even happens without this PR for some reason. I am still not sure why


Remove extra bottom padding and border from TableCard component

Contributes to TD-2464
Changes
Making this change to address a comment on a common issue here

Removig extra space and last border

UI/UX
Before

After

Testing notes

Check there is no extra space visible after last row in the Table Card

[x] Reviewed my own code-diff.
[x] ~Branch has been run in docker.~
[x] PR assigned to me or an appropriate delegate.
[x] Relevant labels added to the PR.
[x] ~Appropriate tests have been added.~
[x] Lint and test workflows pass.

@m4manjesh in future, please wait for all tests to finish running before you ask for a review in the teams chat and before ticking the box in the checklist.

@m4manjesh in future, please wait for all tests to finish running before you ask for a review in the teams chat and before ticking the box in the checklist.

Apologies, this is ready now.


install problem

hello my name is carlos, I am trying to install the nginx-rtmp-module
Install required packages
sudo apt-get install build-essential libpcre3-dev libssl-dev zlib1g-dev
Download NGINX source
http://nginx.org/download/
wget http://nginx.org/download/nginx-1.15.2.tar.gz
tar -zxvf nginx-1.15.2.tar.gz
Download NGINX RTMP module source
https://github.com/arut/nginx-rtmp-module
git clone https://github.com/arut/nginx-rtmp-module.git
Compile NGINX with the RTMP module
cd nginx-1.15.2
./configure --with-http_ssl_module --add-module=../nginx-rtmp-module
make
But when I do the make it gives me this error:
../nginx-rtmp-module/ngx_rtmp_eval.c: In function ‘ngx_rtmp_eval’:
../nginx-rtmp-module/ngx_rtmp_eval.c:160:17: error: this statement may fall through [-Werror=implicit-fallthrough=]
160 |                 switch (c) {
|                 ^~~~~~
../nginx-rtmp-module/ngx_rtmp_eval.c:170:13: note: here
170 |             case ESCAPE:
|             ^~~~
cc1: all warnings being treated as errors
make[1]: *** [objs/Makefile:1349: objs/addon/nginx-rtmp-module/ngx_rtmp_eval.o] Error 1
make[1]: se sale del directorio '/home/adminvitoria/nginx-1.15.2'
make: *** [Makefile:8: build] Error 2
any can help me please!!!!!!

You can probably fix it by doing what is mentioned here: https://github.com/arut/nginx-rtmp-module/issues/1283#issuecomment-439217412


Allow remotes to not open a legacy substream

This tackles the first bullet point of this comment: https://github.com/paritytech/substrate/issues/5670#issuecomment-690117333
At the moment, when a connection is established and peerset slots reserved, nodes have to open a legacy substream and all notification substreams. Once all these substreams are open, the actual opening is reported on the API layer.
Amongst the notification substreams, the block announces substream contains a handshake that mimics the handshake of the legacy substream.
This PR changes the code so that we report the actual opening if all notification substreams are open, even if the legacy substream is closed. In that situation, the handshake of the block announces substream is reported as the handshake.
Since the handshake actually differ a bit (there is no protocol version system anymore), I've done two changes:

In protocol.rs, we now try to parse the handshake as either the legacy handshake or the block announces handshake.
The system_peers JSON-RPC call no longer has a protocol_version field. I believe that this shouldn't have been exposed in the first place.

I'm going to open another pull request on top of this one that changes the code to no longer open a legacy substream altogether. EDIT: https://github.com/paritytech/substrate/pull/7076 We should merge this PR only if the CI of that other pull request is green. However, we need to publish a version between this PR and that other PR.
Nodes having both PRs will no longer be able to connect to nodes that have neither. The opposite stills works: nodes without these two PRs will still be able to connect to nodes with both. As such, this change is considered acceptable.

Nothing weird happening on the burn-in. The node is surprisingly better connected than it was before its reboot, but version that was on the node was quite old and we can't attribute this change to this pull request.

The node is surprisingly better connected than it was before its reboot, but the version that was on the node was quite old and we can't attribute this change to this pull request.

In case you want ot compare to an up-to-date master deployment, canary-sentry-ew4-0 would be an option.

I did the change to have the first protocol always containing the handshake.

bot merge


Fix openshift-ansible repo sync for azure jobs

@openshift/sig-azure

@kargakis, thanks for this!


UDS to add new endpoint /catalog to return STAC catalog

This endpoints returns all collections, I think.


"collision between" with cffi

I get a collision with cffi against itself when trying to install Python 3.8 and raylib-python-cffi.
collision between `/nix/store/m00mi8warrl8kh7qbssrlcnhmnhd5aqs-python3.8-cffi-1.14.5/lib/python3.8/site-packages/cffi-1.14.5.dist-info/WHEEL' and `/nix/store/sp2pz3j1j0csa27m75mdrrhb52pm1c6w-python3.8-cffi-1.14.5/lib/python3.8/site-packages/cffi-1.14.5.dist-info/WHEEL'

As you can see, the same version has been pulled out twice, but with different hashes.
Here's my cut down shell.nix which demonstrates the issue
{ pkgs ? import <nixpkgs> {} }:

let
  mach-nix = import (builtins.fetchGit {
    url = "https://github.com/DavHau/mach-nix/";
    ref = "3.3.0";
  }) {};
  raylib-python-cffi = mach-nix.buildPythonPackage {
    src = builtins.fetchGit {
      url = "https://github.com/adamlwgriffiths/raylib-python-cffi";
      ref = "dynamic-only";
      rev = "d65c7407fc8b151c0c777771df6a6187b52a74a6";
    };
  };
  custom-python = mach-nix.mkPython {
    python = "python38";
    packagesExtra = [
      raylib-python-cffi
    ];
    providers = {
      _default = "nixpkgs,wheel,sdist";
    };
  };
in pkgs.mkShell {
  buildInputs = with pkgs; [
    custom-python
  ];

  shellHook = ''
    export USE_EXTERNAL_RAYLIB=
  '';
}

Ok, I'm having more trouble with cffi in a different shell where im trying to pull in poetry.
Not sure what's going on.
Executing pipInstallPhase
/build/SecretStorage-3.3.1/dist /build/SecretStorage-3.3.1
Processing ./SecretStorage-3.3.1-py3-none-any.whl
Requirement already satisfied: cryptography>=2.0 in /nix/store/b09a13zp017h964rbq3pfsq6x83ka2xm-python3.8-cryptography-3.4.7/lib/python3.8/site-packages (from SecretStorage==3.3.1) (3.4.7)
Requirement already satisfied: jeepney>=0.6 in /nix/store/h4j7xgj69f61fz6y6yyrh771lljww59k-python3.8-jeepney-0.6.0/lib/python3.8/site-packages (from SecretStorage==3.3.1) (0.6.0)
INFO: pip is looking at multiple versions of <Python from Requires-Python> to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of secretstorage to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement cffi>=1.12 (from cryptography)
ERROR: No matching distribution found for cffi>=1.12
builder for '/nix/store/g54fhzi2iyij6imjsywx35fw86rvxrb4-python3.8-secretstorage-3.3.1.drv' failed with exit code 1

Ok so this has been causing me a lot of trouble with anything that pulls in cffi - which turns out to be quite a few libs (twine, poetry, etc).
The solution seems to be to explicitly specify the same dependency (cffi>=1.12) in the mach-nix.mkPython.requirements field.
Eg:
  custom-python = mach-nix.mkPython {
    requirements = ''
      setuptools
      cffi>=1.12
      twine
    '';
...

The problem seems to be caused by different provider settings passed to buildPythonPackage and mkPython.


Upgrade docsy to v0.10.0

This is just for review, you should probably just push this directly once it's been reviewed.

For an easier diff to review: https://github.com/google/docsy/compare/main...Kladki:docsy:upgrade-docsy
I am wondering if we should create a v0.8.0 branch before merging this. Since matrix-spec locked this module to a specific commit, if we rebase the main branch the commit will be gone, so CI won't be able to build it until the commit is updated.

To be able to get rid of the use of canonifyURLs, we need to change our commits to use relative paths instead of absolute paths, i.e. removing the leading /.
For example, "/js/jquery-3.7.1.min.js" becomes "js/jquery-3.7.1.min.js".

This PR has been superseded by https://github.com/matrix-org/docsy/pull/5. Nevertheless, thanks for your work in helping us get there!


lua: Manage imported public keys in stream handle

Commit Message: This patch manages the imported public keys in the stream-handle object instead of "exposing" it as pointer through lua_pushlightuserdata.
Risk Level: Low
Testing: Existing tests
Docs Changes: N/A
Release Notes: N/A
Fixes #12485
Signed-off-by: Dhi Aurrahman<EMAIL_ADDRESS>

cc. @yxue


Assumptions about cellular networks

In most situations it is not possible to run a service on a device connected to a cellular network. This is because such devices have private IP addresses within the cellular network, which have no meaning outside the cellular network.
Given this, logical segments for routes through a gateway into and out of the cellular network, and between the backhaul network and cells in the cellular network are created using subclasses that embody restrictions on what connections can be made. This ensures that system modeller users don't need to go in and add a lot of controls representing firewall policies on these routes for threats that can't happen.
However, the assumption is that the base stations and backhaul router devices do not allow connection forwarding rules to be set up. Such rules can be used to provide a proxy on a gateway for a service on a LAN inside the gateway, allowing such a service to be accessed from outside the gateway.
It is reasonable (at least at the present time) to assume that a public cellular network operator will not provide connection forwarding as part of their service. To do so may create security problems and would impose operational constraints, so they just don't do this. Indeed, the assumption used is that one cannot connect to mobile devices from outside the cell they are in, let alone outside the cellular network.
It is not so reasonable to assume that connection forwarding rules could not be set up within a private cellular network. This assumption is currently used (the same construction patterns are used for all cellular networks), but may need to be changed.
See also issue #151, which describes a different bug in the cellular network construction pattern sequence. It may make sense to address both these issues in a single set of changes.

The best approach to addressing this issue may be to assume that the absence of connection forwarding normally used in public cellular networks does not hold (at least not by default) in a private cellular network. This means users will need to apply controls for any restrictions they require, and that would be easier for them if more of the assets are asserted.
One way to implement this would be to amend cellular network construction patterns so they work correctly if any implementing assets are asserted (base stations, radio access networks and the backbone router and network). This is also necessary to create a consistent set of fixes for #151.
It would be possible to address #152 at the same time by including the following:

[ ] Limit insertion of an inferred backbone router to public cellular networks. This means a private cellular network will only have a backbone router if it is asserted, which also means it will have a location (even if only the global public space 'World').
[ ] Allow insertion of an inferred backbone network provided by this router for any cellular network, but making it accessible from the location of the backbone router if the cellular network is private. This causes the regular segment construction patterns to work for routes through a private backbone router to and from other networks.
[ ] Allow insertion of inferred base stations and radio access networks for any cellular network.
[ ] Add a location for each inferred base station in a private cellular network, and make the radio access network and backbone network accessible from its location. This causes the regular segment construction patterns to work for routes into and out of the cell via the base station.

The resulting domain model update will not then be backward compatible with all existing system models. For one thing, it would be possible to deploy services on devices connected via a private cellular network, with clients outside the cell where the service is deployed. This is currently impossible, but removing the restriction should not cause problems for users. However, users may also fail to include a backbone router for every private cellular network, especially in legacy system models where previously they were filled in by construction patterns.
To handle and explain these compatibility issues, we can add a couple of modelling error threats:

[ ] A check for private cellular networks not provided by a backbone router. This should prevent users forgetting to add backbone routers for private cellular networks, including cases where they are missing in legacy system models.
[ ] A check for private cellular networks provided by a backbone router with a set of base stations, and a description referring to this issue, explaining that users must now select controls expressing connection routing restrictions in these networks.

The first of these should have no control strategies, forcing the user to add a backbone router to remove the error.
The second can have a control strategy to signal acknowledgment of the issue, but no control strategies representing selection of routing restriction controls (since it is possible that a user may not want these restrictions). Until such controls are selected, threats addressed by those controls will appear as a source of risk, so any consequences of not using those controls should be clear.

To implement the above model, we need to:

allow cellular network infrastructure assets to be asserted, so users can override default assumptions where appropriate,
ensure construction patterns that add inferred infrastructure allow for the possibility that some elements may be asserted,
ensure that inappropriate relationships are not inferred to exist to/from asserted infrastructure assets,
ensure that appropriate classifications and relationships are added for inferred infrastructure assets.

The first two of these requirements should have been met ages ago - we just didn't encounter a need for a partially asserted cellular network infrastructure, so took the easy approach of assuming it would always need to be inferred. To address this, the following changes should be made:

[ ] Make the BaseStation and RAN asset class assertible, so users can assert them if required.
[ ] Add a new assertible relationship 'implementsCN', and use this instead of 'implements' in all patterns in which the target is a cellular network, so users can relate any asserted RAN and backbone network assets to a cellular network.
[ ] Split the construction patterns that create the inferred backbone and radio access networks and base stations so each pattern adds only one of these assets, and connections from client hosts and to the locations of inferred hosts are added afterwards.
[ ] Ensure each of the modified patterns creating these inferred assets includes a check that the asset does not already exist.

Using a separate pattern to add each inferred asset or relationship makes it possible to skip asset creation where the asset already exists, without also skipping the creation of subsequent relationships or related assets. Note that the existing sequence already has a separate pattern to create the backbone router and it has a check that the router exists. These changes therefore only affect the patterns for creating the backbone and radio access networks and base stations, plus their relationships.
We must then make changes to ensure that appropriate relationships are created for cellular network infrastructure assets, which differ slightly depending on whether the cellular network is public or private. The first such changes are:

[ ] Limit insertion of an inferred backbone router to public cellular networks.
[ ] Add a modelling error threat to flag a cellular network with no providing backbone router.

These changes ensure that a private cellular network has an asserted backbone router, so any external connections can be added via its asserted relationships (even if there are none). This is not necessary for a public cellular network because if no such external connections are specified, we can assume it is connected to the Internet, so it is OK to have an inferred backbone router. Note that since the pattern used to do this comes after PH-S+W, if the backbone in a public cellular network is inferred, it is not assigned a physical location, which is equivalent to assuming it is an unspecified, secure location.
Further changes are then to insert an appropriate location information for backbone routers and base stations:

[ ] Add a pattern in the host location sequence before pattern PH-S+W, which finds asserted base stations with no location, and infers they are located in the space served by their radio access network.
[ ] Add a similar pattern after creation of inferred base stations in the cellular network construction sequence, but restricted to private cellular networks, so their base stations have appropriate locations even if inferred.
[ ] Add a modelling error threat to find base station hosts with more than one location.

The modelling error is needed because if a radio access network covers more than one space (e.g., a street and a shop on that street), and the location of its base station is not asserted, then the inferred location would be ambiguous. The modelling error should direct the user to include the base station if not already asserted, and specify its location explicitly.
Finally, to get the right class of logical segments, the following changes are needed:

[ ] The RAN asset class representing a radio access network should be classified as an L2 subnet but not an L3 subnet. This ensures the generic patterns that create routes via the providing router into or out of a subnet do not apply to a RAN.
[ ] Patterns L3cCrC+OSg and CcBrR+CSg which create closed segments via a backbone router into its backbone network, or via a base station into its radio access network should be limited to public cellular networks.
[ ] Two similar patterns should be added that create open segments instead where the cellular network is private.

These changes ensure that the routing restrictions indicated by a closed segment, which prevent service connections to mobile client devices, and only assumed to exist by default for public cellular networks.

Step 1: make the BaseStation, RAN and CoreNetwork asset classes assertible, so users can assert them if required.
The only complication is that we then need to specify icons so they can be displayed in the asset palette and canvas. These were created using inkscape, but they are not great so should be replaced if anyone can come up with better icons.

Steps 2-3: Add subtypes of the existing relationship 'implements' (from a logical subnet to an abstract subnet) into two subcases: one indicating that the subnet implements a WiFi hotspot, and the other a Cellular Network. Make the second of these assertible.
Where appropriate, alter construction patterns and threats that use 'implements' so they use one of these subtypes.
Added subtypes 'implementsHS' (for WiFi hotspots) and 'implementsCN' (for cellular networks), both subtypes of 'implements' with the second (but not the first) tagged as 'assertible' (which, due to a system modeller bug, also means 'not hidden').
Note that a WiFi hotspot is just a (usually asserted) WiFi subnet provided by a mobile device. This means the subnet could exist in more than one physical location, so it must be treated as though it is abstract, with an inferred concrete WiFi subnet providing the implementation in each location. The problem then is that users may specify controls at the (abstract) hotspot which should affect threats to the (concrete) subnets in each location.
To handle this, threat patterns include both the subnet attacked, and the subnet it implements, so control strategies can include controls located at the latter subnet. Where a WiFi subnet is not a hotspot that could appear in several locations, there is a self-referential 'implements' (which should now be 'implementsHS') so the subnet matches both roles in the threat, and controls are included in control strategies in the same way.
Changed 'implements' to 'implementsHS' where the pattern refers to a WiFi hotspot or non-hotspot: affects construction patterns WS-H+I, WpHSH-aF+WH, HcWHS+c and PcWH+c, and threats LS.C.WiFiSSoH.3 and LS.IS.WHmWS.8. In the first threat, the subnet is a non-hotspot identified via a self-referential 'implements' so it cannot refer to a cellular network RAN, while the other patterns are explicitly related to WiFi subnets.
Threats I.A.GdHRSi.6, I.A.GdHRS.6, I.Auth.HRSGSoS.3, I.Auth.HSRSoGS.3, LS.L.RSSH.1, LS.L.RSS-HP.3, LS.L.RSSH-P.3 have not been changed because they apply to any radio subnet including RANs and Hotspots. In practice, the radio subnet in the first of these is always a WiFi subnet (one with a self-referential 'implements' indicating it is not a hotspot), so the relationship need not be made more specific to exclude matched to a RAN.
The cellular network construction patterns must also be changed, but they also require other changes so this is described below.

Step 7: Ensure network control relationships currently added separately by PcCN+c are also added for the backbone network, and allow for the possibility that there may already be an asserted controlling process for some subnets.
Construction pattern PcCN+c is replaced by PcCNLS-S+c. This applies to any logical subnet that 'implementsCN' a cellular network, specifying control over the backbone as well as the radio access networks (since any of these may be asserted. The pattern also has a check that there is no existing controlling service to avoid duplicating or conflicting with asserted control arrangements.

Steps 8-9: Limit insertion of an inferred backbone router to public cellular networks. Add a modelling error threat to flag a cellular network with no providing backbone router.
Handled by replacing construction pattern CN-R+R with PCN-R+R, in which the cellular network must be public, and the gateway host role has a less restrictive class (see above). A modelling error is then added using the original CN-R matching pattern, which detects any cellular network that is not provided by any (backbone) router.
Note that there is no need to check for cellular networks that lack a backbone network, because if the backbone router is defined via a 'providedBy' relationship, the backbone network will be inferred if not already present.

Steps 10-12: Add a pattern in the host location sequence before pattern PH-S+W, which finds asserted base stations with no location, and infers they are located in the space served by their radio access network. Add a similar pattern after creation of inferred base stations in the cellular network construction sequence, but restricted to private cellular networks, so their base stations have appropriate locations even if inferred. Add a modelling error threat to find base station hosts with more than one location (a base station should not be mobile).
Patterns CNS+RAN+BS-S+l and PCNS+RAN+BS-S+l insert the location of the physical host of a radio access network base station. CNS+RAN+BS-S+l does this for any cellular network, and is used prior to any other device location inference to ensure a sensible location is used for an asserted base station if not otherwise specified. To accommodate this, the sequence numbers of the existing patterns have been altered. PCNS+RAN+BS-S+l is used later to add the location of any inferred base station - but only for private cellular networks.
A threat CN.E.CNRAN2dS.9 was also added to detect cases where a base station has ambiguous locations.
It became apparent that there is no threat to detect fixed hosts with multiple locations (whether or not they provide radio access networks). Such a threat would not suffice here because a radio access network could be provided by a mobile device. However, at present this is only supported if the mobile device has only one location (i.e., it does not move), as the idea is that the radio access network serves a fixed set of locations.

Steps 13-14: Replace patterns L3cCrC+OSg that creates segments for a route from external IP subnets into the backbone network of a cellular network, and CcBrR+CSg which creates segments from there into the cell radio access networks, such that segments of distinct types are created for public and private subnets.
Pattern CcBrR+CSg has been replaced by UCcBrR+CSg and PCcBrR+DSg. The first applies if the cellular network is public and creates a closed segment, indicating that port forwarding is not supported into the cell. The second applies if the cellular network is private, and creates a reverse NAT segment indicating that port forwarding is assumed to be supported.
Pattern L3cCrC+OSg has been replaced by L3cCrUC+CSg and L3cCrPC+DSg. The first applies if the cellular network is public and creates a closed segment, indicating that port forwarding is not supported into the backbone network. The second applies if the cellular network is private, and creates a reverse NAT segment indicating that port forwarding is assumed to be supported.

Steps 15-16: The RAN asset class representing a radio access network should be classified as an L2 subnet but not an L3 subnet. Regular logical segment construction patterns L3c-rGrL3+DSg and L3rGrL3+OSg should check there is no existing segment before creating one.
Making a RAN a L2 network only ensures the generic segment construction patterns do not apply to routes into or out of a RAN, avoiding duplication with UCcBrR+CSg and PCcBrR+OSg.
Adding a check to L3c-rGrL3+DSg and L3rGrL3+OSg ensures they do not create duplicate segments where a segment has already been created by L3cCrUC+CSg.

Steps 17-18:  Pattern CSCLS-ii+PNC, which creates a network access context for reconnection of a stolen client, which certainly could be done via a cellular network. Threats LS.L.HL3S.1, LS.L.HL3S.2, LS.M.HprL3SAC.1 model network privileges, and I.O.RoH.3 models overload attacks given access to networks. These should all work if the network in question is a radio access network.
Pattern CSCLS-ii+PNC has been modified so any L2 or L3 subnet matches the reconnection subnet role.
Threats LS.L.HL3S.1, LS.L.HL3S.2 and LS.M.HprL3SAC.1 have been replaced by LS.L.HL23S.1, LS.L.HL23S.2 and LS.M.HprL23SAC.1, which use a different matching pattern in which the relevant role can be fulfilled by L2 as well as L3 subnets.

This set of Test Cases
conforms with current domain modelling assumptions.
The tests all involve a cellular network connected via its backbone router to the Internet. There are two private spaces served by the cellular network:

Space 2: contains phone P2 running service S2, and phone P3 running client C3 which uses S2.
Space 1: contains phone P1 running client C1, which uses service S2 and S1

Service S1 is hosted on laptop H1 which is connected directly to the Internet, and also hosts client C2 which uses service S2.
This arrangement gives us client-service connections: C1-S1 (cell to the Internet), C1-S2 (cell to another cell), C2-S2 (Internet to a cell) and C3-S2 (within the same cell). With the assumptions documented above, we expect the following results:

Issue-152-Test-01a: uses a public cellular network whose implementation is entirely inferred: base stations providing radio access networks in Space1, Space2 and the World (since this is a public cellular network), plus a backbone network to which the base stations are connected, provided by a backbone router connected to the Internet. The phones should get inferred connections to the radio access networks in their locations.
Issue-152-Test-01b: as Test-01a, except the backbone router is included in Space3, which is a third private space. Inference rules should fill in the rest of the implementation: a connection from the asserted router to the Internet (since this is a public cellular network), the backbone network provided this router, and the three base stations connected to this providing radio access networks to which the phones are connected in their locations. The asserted router should play its role and there should be no inferred duplicate.
Issue-152-Test-01c: as Test-01b, except the backbone network is also included (provided by the backbone router), along with a base station in Space2 connected to the backbone network. Inference rules should fill in the rest of the implementation: a connection from the asserted router to the Internet (since this is a public cellular network), the remaining two base stations connected to the backbone network, and the three radio access networks provided by the base stations, to which the phones are connected in their locations. The asserted assets should play their roles with no inferred duplicate.

These three cases should allow connections C1-S1 and C3-S2 but not C1-S2 or C2-S2 because they involve to a service running on a cell from clients outside that cell. Arguably, C3-C2 should also be disallowed, but at present we assumed routing restrictions only affect routes into the backbone network or into a cell, not routes within a single cell.
A quick check of the results can be found from the modelling error threats, which report the presence of client-service communications for which there is no available network path. A full check requires inspection of the inferred assets and relationships to confirm that the inference rules complete the cellular network infrastructure without duplicating any elements that have been asserted.
Unfortunately, Test-01b did not give the expected behaviour, because it is affected by issue #154. This can be addressed by including an extra assertion, so the version in the attached collection uses this version, labelled 'Issue-152-Test-01b+Kludge-4-154'.
The test set also includes the following cases:

Issue-152-Test-02a: same as Test-01a, but uses a private cellular network. This should produce a modelling error demanding that the backbone router be added, along with connections to other networks, since these cannot be assumed in a private cellular network (we can't just assume it is connected to the Internet). The absence of a backbone router and network means no radio access networks are created, so no client-service connections are allowed.
Issue-152-Test-02b: same as Test-01b, but uses a private cellular network, and the backbone router is connected to the Internet. This eliminates the modelling error seen in Test-01a. The inference rules should fill in the rest of the infrastructure as in Test-01b, but without adding a base station and radio access network in the World (since a private cellular network is not assumed to cover all public spaces). The asserted assets should be involved with no inferred duplicates.
Issue-152-Test-02c: same as Test-01c, but uses a private cellular network, and the backbone router is connected to the Internet. We should get the same results as Test-01b but with more of the roles filled by asserted assets, and no inferred duplicates.

Because fewer assumptions can be made about a private cellular network, more facts must be asserted. As a result, Test-02b is unaffected by issue #154, so the attached collection includes the unkludged version.
In Test-02a, the absence of a backbone router and network means no radio access networks are created, so none of the client-service connections are allowed. We should get five modelling errors (one per client-service connection, and one flagging the absence of a backbone router). In Test-02b and Test-02c, we should find all four connections are allowed, because in a private cellular network we assume the operator adds connection forwarding policies allowing connections to services running in a cell from other cells or from outside the cellular network.

Tests now all give the expected results, assuming the kludges are used to avoid difficulties with issue #154.
Committed on branch 151.
Next steps on this branch:

address #151, which depends on addressing #152 and vice versa
maximise the use of inference to find network accessibility, so this only needs to be asserted where it cannot be inferred, which represents the best solution for #154 (and should remove the need for kludges)

Results from tests for issue #151 reveal that we need some extra assumptions regarding how devices behave when connected to a cellular network (radio access network) and another network. There are lots of subcases:

Device connected to a cellular RAN in a location where it is also connected to an IP subnet.
Device connected to a cellular RAN in a location in which it is also providing a (typically wireless) IP subnet (a hotspot).
Device connected to a cellular RAN in a location where it is paired with another device via USB.
Device connected to a cellular RAN in a location where it is paired with another device via Bluetooth.

In cases (3) and (4), we model the device-to-device pairing connection as an L1 subnet, so like cases (1) and (2), the concern is to understand what messages can be routed to/from/via the device between the cellular network and a local L1/L3 subnet.
It should always be possible for a connected device to route connections to the cellular network, even if it may be prohibited under the cellular network operator's contract. As the cellular RAN does not use the same address space as the other subnet, it is always necessary for the connected device to insert source addresses for connection requests originating in the other subnet. This means the route via the connected device into the cellular RAN should be modelled as a NATSegment.
This also holds if the cellular RAN is replaced by an IP subnet (i.e., it is not an exception to the usual rule), except in case (1). There, routing between IP subnets by a device that does not provide either subnet only makes sense where addresses on either side can be compared and distinguished. That being the case, address translation would not be necessary, so the routes in both directions would be modelled as OpenSegments.
The remaining question is whether connections can be made from clients on the cellular network via a connected device to services on the other subnet. There are two reaasons why this may not be possible:

Public cellular network operators do not allow clients to make connections to other devices on the cellular network.
Clients connecting from or via the RAN would not know the address for a service on the IP subnet.

The first issue does not affect the way routes via the connected device are modelled. See below.
The second issue can be circumvented if the connected device is configured to forward connections. That should be modelled via a DeNATSegment. Normally, that is not possible in cases (3) or (4), as discussed in issue #157, but it is possible in cases (1) or (2). As before, the only difference if the cellular network were replaced by an IP subnet is that case (1) would then use an OpenSegment.
The first issue cannot be modelled in terms of the routes via the connected device. It can only be modelled in terms of the way a connected device sends messages to the cellular RAN. If the operator allows direct device-to-device connections, the base station behave like IP router/switch devices, and RAN subnets like IP subnets (even if using L2 addresses). If both devices are within the same cell, they go across the local RAN via the base station. If not, connection requests are routed from the source RAN into the backbone network, and thence via a second base station into the destination cell's RAN.
If the cellular network operator does not allow device-to-device connections, the routes from the backbone network should be modelled as ClosedSegments. However, this only inhibites connections between devices on different cells. Within a cell, the RAN must act like a separate subnet per connected client device, so the base station must route between these subnets. With that in place, one can model the prohibited route by using a ClosedSegment.
So - there are two further actions needed to get the correct results:

[ ] Review and fix the Logical Segment classes created for routes into and out of the cellular RAN via a connected device. At this stage, this includes fixing issue #157.
[ ] Alter the way a cellular network RAN is modelled, so it no longer provides direct device-to-device connections, but routes them via the base station.

This issue is now addressed apart from two aspects:

introducing more generous network accessibility inference rules (issue #155)
changes to the model of routes within a subnet (issue #159).

Addressing #159 will require changes to a lot of threats, so it can't be addressed very quickly. On that basis, it seems appropriate to address #155 as quickly as possible, then merge in those changes along with previous changes to address #151 and #152 (i.e. from branch 151).
This will leave issue #159 still open, as a starting points for further changes.

New tests added to the MS Access Domain Model Editor DB revealed some self-referential relationships that did not connect the same node in two patterns associated with public and private cellular network route construction.
These errors could have led to spurious logical segment assets (routes through gateways) to be inferred through base stations if they were mobile and also providing a WiFi hotspot. This is an extremely unusual situation not found in any of the test cases used to verify changes addressing issues #152 or #151. At present, the domain model does not support mobile base stations.
The error therefore has no consequences. However, it is worth fixing now so it won't cause problems if the domain model were to be extended to allow mobile base stations. Since such things do exist, such an extension would be entirely reasonable.
This has now been done in branch 151.

Last bugs now fixed, leaving only the aspects covered separately under #159.


Internal builds failing to find Microsoft.Tye.Extensions.Configuration.pdb

Internal builds have been failing to find the Microsoft.Tye.Extensions.Configuration.pdb file in builds. This has failed the last 3 internal builds: https://dnceng.visualstudio.com/internal/_build/results?buildId=590188

Guess:
netstandard2.0, set symbol type to embedded.

Fixed now?

Fixed.


[auto-render] add an option to ignore $ outside of latex expressions

If it's possible for escaping $ to normal $, then latex $ (expressions) $ would not be any problem.
I wanted to make my own hack for this, but I'm not used to string so far.
Is there any plan to support dollar sign escaping?

We already have logic that should skip over backslashes:
https://github.com/Khan/KaTeX/blob/c79fb5893686ac0b8c4d8ec33ea1b940d2e4a0c4/contrib/auto-render/splitAtDelimiters.js#L16

Maybe it's not working?

That only works for escaping $ inside of math, but not outside of it. @PaulSohn can you give an example of what you're trying to do?

If this is the delimiter:
{ left: '$', right: '$', display: false }

and I want to render this text:
I will have you \$2 if you solve $y = x^2$.

The first $ is ignored but the \ is still output.

Rendering this text:
I will give you \$2 if you can solve $y = x^2$.

with this delimiter:
{ left: '$', right: '$', display: false }

results in
<#text>I will give you \</#text>
KATEX MATH
<#text>y = x^2</#text>
<#text>$.</#text>

where <#text> denotes a text DOM node.

Agreed, can not write dollar sign outside of math equations...

@PaulSohn can you use different delimiters, e.g. \(,\) and \[,\]?

I'm going to close this since it's going to be very difficult to implement something that handles the different behaviors people want.  Also, there is a workaround by using different delimiters.

There is more than one way to do this. If you are using the KaTeX auto-render extension, then you can delimit your math with \(…\) instead of $…$. Or you can nest the whole phrase in … tags.
Some markdown parsers only recognize the closing $ as a math delimiter if it is not followed by a number. Sometimes I think we should do that too.

Thanks for replying. I simply replaced my $ with $ and this made Katex ignore it. I'm putting it out so that someone else also tries it.

Would be nice for MathJax processEscapes compatibility: http://docs.mathjax.org/en/latest/options/preprocessors/tex2jax.html#configure-tex2jax

@Trass3r can you open a new issue for processEscapes?

Isn't it exactly this issue?
When set to true, you may use \$ to represent a literal dollar sign. Typically this is set to true if you enable the $ ... $ in-line delimiter

I'm re-opening and have changed the title to indicate that we'd like an option to ignore \$.

To have \$ render as a normal $ and not as the beginning of inline latex I added one line of javascript that replaces \$ with $.

I have made a pull request that changes the autorender in the following way:

If a left delimiter is preceded by a backslash (\), the backslash is stripped and the delimiter is ignored (math mode is not entered). So \$40 is greater than \$30 gets transformed to $40 is greater than $30, if $ is configured to be a starting delimiter. If it is not, the backslashes are left untouched.

I think this is safe and sane enough behavior to have as a default. The only way existing users are affected by this is if they have a backslash immediately (no whitespace or anything) followed by a delimiter that enters math mode. I can't think of any scenario where one would want that, and if one still does one can do \$ or \$ (or a variety of other methods, zero-width spaces, etc).
This also means that \\( becomes just a literal \( and such - it is not limited to $.

Katex cannot express $ in math expressions like
$$
\$100 + \$100 = \$200
$$


After Click on Allow it is showing Error.Login Consent is not Working in the Teams Desktop and in Browser.

After Click on Allow it is showing Error.Login Consent is not Working in the Teams Desktop and in Browser.

No, You cannot get images from teams.microsoft.com. Also the images which you have given in the adaptivecard should be publicly available. For more information could you please check this docs?

Which Document are you following? Could you please share repro steps? Also could you please share request body?


[v3.3.1] Trying to fix stuck workflows

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#49  👈
#48
dev

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

Join @GoodM4ven and the rest of your teammates on  Graphite

Merge activity

May 21, 9:21 AM EDT: @GoodM4ven started a stack merge that includes this pull request via Graphite.


Update WhitePaper.md

Tried to fix some spelling, grammar, and punctuation to help the paper read better.

good project


We're 99.9% sure there's only one Croconys spawn point for Burt

Stating "(South)" in "Croconys Seashore (South)" appears to be extraneous. Not once since launch have I actually seen Burt in the purported northern position.

Hmmm, yup just ran a query against all my accumulated data (at least since the site went live), never seen one upvoted for North.
Not sure where I pulled that from but I think some of the reference guides may be wrong then. 😅

Also tracks partially back to #6


RefCounted and Unique do not forward all fields of underlying data structure

joseph.wakeling (@WebDrake) reported this on 2015-07-26T11:43:51Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=14830
Description
Observed when trying to create a ref-counted random number generator:

    import std.random, std.typecons;
    static assert(isUniformRNG!Random);
    static assert(isUniformRNG!(RefCounted!Random)); // FAILS

So far as I can tell, the problem is the check for the existence of the isUniformRandom boolean enum in the isUniformRNG template check:
https://github.com/D-Programming-Language/phobos/blob/master/std/random.d#L137-L140

i.e. while this check passes:

    static assert(is(typeof(Random.isUniformRandom)));

this corresponding one fails:

    static assert(is(typeof((RefCounted!Random).isUniformRandom)));

Clearly one could put the blame on the isUniformRNG template check here, but my feeling is that RefCounted should be able to forward _all_ properties and fields of the underlying type, including compile-time enum flags like isUniformRandom.

joseph.wakeling commented on 2015-07-26T12:20:22Z
Same happens with Unique!Random:

    static assert(isUniformRNG!(Unique!Random));   // FAILS

joseph.wakeling commented on 2015-07-26T11:45:13Z
See also Issue #10888.  Both these issues have nasty consequences for working with std.random functionality.


Website work upto 21 July, 2022

@AsavariA The reason it failed is because you do not have any tests.


Fonts

This change is

Review status: 0 of 17 files reviewed at latest revision, 22 unresolved discussions.

demos/fonts/App.vue, line 65 at r1 (raw file):

</template>

<script>

can we put the typescript in a separate file, and same for the other .vue files?

demos/fonts/components/Sample.vue, line 16 at r1 (raw file):

==============================================================================-->

<!-- <:Window on:scroll="measure()" on:resize="measure()" /> -->

remove this

demos/fonts/components/Sample.vue, line 78 at r1 (raw file):

  },
  methods: {
    // select: function(event) {

remove

demos/fonts/components/Tray.vue, line 22 at r1 (raw file):

    :style="{height: height + 'px'}"

  >

put > on the line with }"

demos/fonts/components/Tray.vue, line 94 at r1 (raw file):

      return math.divide(this.direction, length);
    },
    // selectedScalar: function() {

remove

demos/fonts/utils/ChunkedQueue.ts, line 22 at r1 (raw file):

export class Queue {
  public interval: number;

public is default in ts

demos/fonts/utils/ChunkedQueue.ts, line 24 at r1 (raw file):

  public interval: number;
  public elementsPerChunk: number;
  private _timeoutID: number;

remove the underscores, private is good enough for ts style

demos/fonts/utils/ChunkedQueue.ts, line 37 at r1 (raw file):

  add(cb: () => void, id: number, priority: number) {
    this.remove(id);
    if (id === undefined) id = -1;

Replace with:
if (id == null) {   id = -1; }
Double equals will do an implicit cast to catch both undefined and null. TypeScript google style also says always have {}. Same comment for "priority" below

demos/fonts/utils/ChunkedQueue.ts, line 58 at r1 (raw file):

  }

  _nextChunk() {

why the underscores? if this is meant to be private, remove underscore and call it "private", same everywhere else

demos/fonts/utils/ChunkedQueue.ts, line 65 at r1 (raw file):

    if (!this._running) {
      this._running = true;
      this._timeoutID = setTimeout(this._run.bind(this), this.interval);

use a closure for consistency with our codebase
setTimeout(() => this._run(), this.interval);

demos/fonts/utils/ChunkedQueue.ts, line 77 at r1 (raw file):

    if (this._queue.length) this._kick();
  }

remove blank line

demos/fonts/utils/FontExamples.ts, line 15 at r1 (raw file):

==============================================================================*/

import { Array1D } from 'deeplearn';

Can you make sure clang-format command line tool, clant-format vscode extension, and tslint vscode extension are installed? It will fix this formatting problem..
make sure you save all the other files too (there are formatting issues in other files)

demos/fonts/utils/FontModel.ts, line 21 at r1 (raw file):

let variables: { [varName: string]: NDArray };
let math: NDArrayMathGPU;

can you make these scoped to FontModel

demos/fonts/utils/FontModel.ts, line 27 at r1 (raw file):

export class FontModel {
  public metaData = "A";

single quotes

demos/fonts/utils/FontModel.ts, line 28 at r1 (raw file):

export class FontModel {
  public metaData = "A";
  public dimensions = 40;

public is default in typescript

demos/fonts/utils/FontModel.ts, line 51 at r1 (raw file):

  load(cb: () => void) {
    const checkpointLoader = new CheckpointLoader(
      "https://storage.googleapis.com/learnjs-data/checkpoint_zoo/fonts/");

single quotes

demos/fonts/utils/FontModel.ts, line 67 at r1 (raw file):

  }

  remove(id: number) {

remove

demos/fonts/utils/ModelCache.ts, line 18 at r1 (raw file):

export class Cache {

remove blank line

demos/fonts/utils/ModelCache.ts, line 33 at r1 (raw file):

  get(id: number, argsArray: Array<{}>) {
    //TODO actually cache/retrieve the values.

// TODO(shancarter)

demos/fonts/utils/ModelCache.ts, line 51 at r1 (raw file):

    return this._paused;
  }

remove blank line

demos/fonts/utils/Utils.ts, line 17 at r1 (raw file):

import { NDArray, Array1D, Scalar, NDArrayMathCPU } from 'deeplearn';

const math = new NDArrayMathCPU(false);

no need to pass false

demos/fonts/utils/Utils.ts, line 49 at r1 (raw file):

export function unit(v: NDArray) {
  const n = Scalar.new(norm(v).get());
  if (n.get() === 0) console.warn("Divide by zero");

use {}

Comments from Reviewable

Should be good to re-review. I snuck in a few new features, apologies. :)

Couple of minor things then I will merge. If

Review status: 7 of 18 files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

Comments from Reviewable


Still cannot click on Manage Courthouse

What version of Node.js are you using?
17.3.0
What version of npm are you using?
7.10.0
What operating system are you using?
Windows Server 2019
What version of SnailyCAD are you currently using?
1.4.3
Describe the Bug

Still have the error when clicking on Manage Courthouse
Expected Behavior
To be able to go to Manage Courthouse page
To Reproduce
No response

I'm unable to reproduce this error. Try rebuild the client and make sure your translated JSON files aren't corrupted.


changed-markdown-files should be changed-files

Hi!
I think changed-markdown-files should be changed to just changed-files here:
https://github.com/developer-friendly/blog/blob/932e49325177427f97a30a63dbea9c3175ac5748/docs/blog/codes/2024/0004-dynamic-github-actions-matrix/step2-determine.yml#L12
and here:
https://github.com/developer-friendly/blog/blob/932e49325177427f97a30a63dbea9c3175ac5748/docs/blog/codes/2024/0004-dynamic-github-actions-matrix/full-ci-definition.yml#L44
Links:
The article:
https://developer-friendly.blog/blog/2024/03/09/github-actions-dynamic-matrix/
The code repo:
https://github.com/meysam81/github-actions-dynamic-matrix

Please look at the discussion here, there are some other fixes https://github.com/tj-actions/changed-files/discussions/2245

Links:
The article:
https://developer-friendly.blog/blog/2024/03/09/github-actions-dynamic-matrix/
The code repo:
https://github.com/meysam81/github-actions-dynamic-matrix

Hey @rafrafek
Thanks for your initiative :hugs:
I have dealt with the other issue (#37).
I will deal with this one when I get some time. In the meantime, any contribution is welcome if you've already sort it out on your end. :rose:
Regards.

Hey @meysam81,
I did the fix for the meysam81/github-actions-dynamic-matrix repo, please review and update the article.
https://github.com/meysam81/github-actions-dynamic-matrix/pull/1


Validate unscoped services without a scoped interface

Follow-up for https://github.com/gradle/gradle/pull/28682
Covers an additional case of strict service scoping validation when a class registered as a service is not annotated with @ServiceScope but also none of its super-interfaces. Previously, such services bypassed the scope validation logic.

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


[FEATURES] Add favorite section with posts saved

Add a feature to save posts that you like to read again in feature.

@MadalinNitu Thanks for the suggestion but I'm not looking to add features as described in the project readme.


Disruptor EventHandler callback on Disruptor shutdown?

I have an EventHandler that buffers data and writes it to disk when the buffer fills.
@Override
public void onEvent(FrameEvent event, long sequence, boolean endOfBatch)
        throws Exception {
    ByteBuffer frame = event.getFrame();
    frame.reset();
    if (frame.remaining() > buffer.remaining()) {
        writer.writeFromMarkToLimit(buffer);
        buffer.reset();
    }
    buffer.put(frame);
}

I would like to get notified when the disruptor gets halted or shut down so that I can flush my buffer. How could I do this?
I saw that EventProcessor has a halt() callback, but I have no idea how to use the EventProcessor interface. I don't know what the getSequence() or the run() methods are supposed to do and I can't seem to find any examples.

Hi,
Have your implementation of the EventHandler also implement LifecycleAware and you will receive callbacks on start and stop of the thread that is running your handler.  Note that onShutdown will only be called if you the thread get a chance to exit cleanly.  This may not happen if you JVM is killed or crashes.
public class MyHandler implements EventHandler<Object>, LifecycleAware {
    public void onEvent(Object event, long sequence, boolean endOfBatch) {
        //...
    }
    public void onStart() {
        // ...
    }
    public void onShutdown() {
        // Flush your data here.
    }
}


Failed automatically fetch 2 packages on Buster

Hi
Issue: RPi 3b+. On latest Buster ( InRelease repo ) "--install-upgrade" fails automatically fetch 2 packages: "pciutils" and "gldriver-test".
Flow: By some reasons script is looking up for those packages in *.raspberry.org. Installation gets aborted with "can not fetch package" message in console.
Workaround: Before run the script, install these packages manually
sudo apt-get install pciutils
sudo apt-get install gldriver-test
after that start the script as per instructions - it will finish successfully and everything will work just fine after restart.
Overall: @idev,1 thanks alot for this script, great job!

Hi, thanks for using the script and reporting an observed issue.
Just to inform you that I have not replicated this scenario in latest Buster OS but, it seems that the packages "pciutils" and "gldriver-test" has nothing to do with the execution of the script.
It might be a problem related to upgrading the existing OS using "--install-upgrade" option.
I will keep you updated once i fix this issue.
Thanks
Pankaj

Hi,
and thanks for checking it!
Indeed it looks very much as an issue with packages upgrade for OS itself.

Hi
I have fixed the bugs in a new branch "rpihotspot-bugfixes" script related to broken logic due to latest Raspbian Buster OS updates.
Can you please run this new branch script in your Buster Lite/Stretch OS and let me know if its solving your reported problem ? so that, it will help me in incorporating the same changes into "master" branch.
Below given are the fixes:

Replaced apt with apt-get as apt in recent Buster OS was enable to fix the broken links while OS upgrades. Hence, switched back to classic apt-get solution.

Handled doCleanup() function to properly operate over dhcpcd enabling releated to Buster OS upgrade problems.

Handled doInstall() function to properly check if the required dependencies are downloaded or not and if, its not downloaded then, prompting the error message and then, quickly exiting the installation process.

Thanks
Pankaj

Hi,
Tried and seems your changes did the trick. Script did its job without any error messages.
Thanks alot for fixing it!

Thanks for verifying the updates !


[Bug] Problem with installing Leon in LXC containers

Specs

Leon version: 7039918 (Downloaded with Git command from Github.)
OS (or browser) version: Ubuntu 21.04 (Running in LXC Container on Proxmox Virtual Environment)
Node.js version: 17.4.0, NPM Version: 8.3.1
Complete "leon check" (or "npm run check") output:

root@LeonAI:/home/leon/leon# leon check
✔ Checking that the setup went well

<EMAIL_ADDRESS>check
babel-node scripts/run-check.js

.: CHECKING :.
[It's just that.]

(if using Docker) Complete "npm run docker:check" output:
(optional) Leon package version:

Expected Behavior
Leon should install dependencies with the new "leon create birth" command.
Actual Behavior
It throws out an error if I try to type "Y" on the CLI screen after I executed the leon create birth command, that asks to install dependencies for leon (see screenshot), but if I type "n" on that screen, it just proceeds and installs Leon. Leon does even start using "leon start" but if I try, for example, to type "hello" in the Web UI, it just says "Sorry, I have an issue with the "Greeting" module of my "Leon" package!". I tested multiple NPM and NodeJS versions, all with the same behaviour.
How Do We Reproduce?
Run Leon with the root user in an LXC Container (Enabled features: keyctl and Nesting)
Extra (like a sample repo to reproduce the issue, etc.)

Hey! :wave: @nicholaskoerfer
Thanks for your report!
Indeed it is a bug we will need to investigate and to figure out how to fix it. :+1:
Explanations
To install apt packages, we need to be root.
To do so, we use a npm package: sudo-prompt.
This allows to prompt the user with a graphical OS dialog to enter the necessary password to be root.
The problematic keyword here is graphical, I'm not familiar with LXC containers but I don't think you are able to run UI.
Problematic line: https://github.com/leon-ai/leon-cli/blob/9da431c5c692d520d13c742bf3f154ce18808d8f/src/services/Requirements.ts#L84
Solution
We should be able to prompt the user to be root directly in the terminal without UI.
That should fix the issue.
Workaround/Investigation
Currently to still be able to install Leon, you need to manually install Python and Pipenv.
We will need your help to investigate so hopefully we can fix the issue.
Could you run manually each line of this script and share with us, the output and errors you encounter: https://github.com/leon-ai/leon-cli/blob/develop/scripts/dependencies/install_apt_packages.sh
Thanks! :smile:


[bindings] root.quit overrides help_menu.quit

Hello! Thank you very much for your work!
The title pretty much says it all, the value set in help_menu.quit is ignored (both the default one and a custom one), because it is overriden by whatever the value in root.quit is (both if changing this binding to a custom one and if leaving the default value).
EDIT:
gitu --version -> gitu 0.25.0
System: Archlinux

@loralb do you have a use-case to bind help_menu.quit and root.quit to different keys?
I'm considering doing something about the duplication of these in https://github.com/altsem/gitu/issues/257


Make the drop and drag feature functionable in donate animal form

Describe the bug
A form opens Donate Animals link in navbar and in that there is feature to upload animal's image
which does not work.
To Reproduce
Steps to reproduce the behavior:

Go to 'donate.html'
Scroll down to 'Your Pet's Image'
Click on 'Drop files to Attach, or Browse box'
See error

Expected behavior
On uploading image, the uploaded image should show on top-left-corner
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: windows
Browser  chrome
Version 113.0.5672.127

I would like to fix the upload image box
Could you Assign it to me

ok assigning you

Are  you still working on it @ANKITy102 ?


XSS in README.html

Bug Description:
https://try.gogs.io/calzoneman/readme-pwned/src/master
Gogs Version:
Whatever runs on try.gogs.io
Git Version:
All
System Type:
All
Error Log:
No
Other information:
You got do be kidding me.

Please shut down your test-instance and do a thorough security review before offering gogs up for download. It is not yet ready to run publicly accessible. if you think, pwning the test instance with XSS is unimportant, as there is no important data there: if I understand it correctly you get at least the e-mail addreseses and full names of people using social logins and visiting your repository. This can be enough to mount a successfull phishing-attack. So yes, there is actually important data there.
(also, you should create and advertise a mail address where vulnerabilities can be disclosed responsibly)

Appears to be more or less a duplicate of https://github.com/gogits/gogs/issues/828


Similar crates

Hi, we were discussing creating a common crate for sensors like this, you might be interested: https://github.com/nnarain/lsm6ds33/issues/2
I was about to implement a driver for this device before I discovered your work!

Interesting idea! Replying on the other issue :D

I guess the work on that went cold :/


Not compatible with WUP Apps targeting Win10

When trying to add the nuget package to a WUP project targeting Windows 10 (.NET Core), it fails and there's several messages like this one:
Install-Package : Some packages are not compatible with UAP,Version=v10.0 (win10-x64).
At line:1 char:1

Install-Package TinyMapper

- CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
- FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand

now should work


Wip test out diff methods for fulfill order

change destination branch to dev

cleaned up in https://github.com/nawangwe/opensea-whitelabel-website-template/pull/18/commits


frozen scene bug (after migrating v9 to v10)

Foundry vtt 10.291
dnd5e System 2.0.3
Health Estimate 29.5.7
Other modules activated: NO
Description of the problem.  After migrating the world from v9 to v10, there seems to be a strange problem happening with the Health Estimate. When activating the module (no other modules active), the hp estimate message over the token in the canvas does not appear above the tokens, and the scene-canvas freezes.
Img console log

Test: in a new test world
I cannot replicate the problem. It seems to work. It seems to be due to some conflict with migration.

Just to be sure, does this happen to the scene without Health Estimate activated too? The first error is thrown by the dnd5e system trying to render the HP bar, and the second is cut short, but it's probably the same source.

No, when I deactivate Health Estimate the bug disappears in that scene (then i can open sheets, move tokens... again). I have isolated the problem, because I have deactivated/activated one by one the modules.
It is true that in a new test world with another scene the bug does not occur.
I will try during the day in another scene of the migrated world.

If you create a brand new scene, does this error happens?
Also, your log shows 3 errors, is the third one just like these two?

I created a new scene, and the error manifested itself when dragging a token (actor) onto the canvas. If I don't do this, the error does not manifest itself as far as I can see.
Console error (other scene, and new scene.... with actors in the canvas)

Hm, can you export that scene and upload it here? Or even zip that world's folder and upload it here? I can't reproduce this with my world.

Hm, can you export that scene and upload it here? Or even zip that world's folder and upload it here? I can't reproduce this with my world.

Secene and actor.zip (via Wetransfer link)
https://we.tl/t-IXomlMRYcK

I couldn't reproduce the error.

By the way, does this happen only with the module enabled? As in, does running with it disabled works fine?

Yes, it is with the module activated that the problem is reproduced (without the module, the foundry runs well). I will try to migrate again from another pc, from v9 to v10, this time deleting the Healt Estimate, and doing a clean install.
In case it comes back, I can give you access to my world, or pass you a copy of my world.

I put the bug on discord, and I got this reply...
dev7355608 — today at 21:51
I came across this error recently in another module. I briefly looked at Health Estimate's code. Maybe the font size is not 0 but invalid. Try to reset the font size and reload
game.settings.set("healthEstimate", "core.menuSettings.fontSize", "x-large")

i put that command in the console and the bug was gone.... but the font of Health Estimate is too big :P


how to play midi with different instrument

i have to play a midi with many different instrument in different channel,but this can only play midi in one instrument at the same time.please help me

That's not a bug with this code.
Take a look at my MIDISynth repository - multiple timbres on different channels.


Add trust opt in app info to bypass checking permission

This closes #237.
I set trust option of numgen app to True, so the qiwiscall requested by it are bypassed to check permission.

Now, all actions work well! @kangz12345


[Request]: Will you use the pigeon plug-in to refactor the code?

Plugin
Any one
Use case
pigeon | Dart Package
Proposal
It seems that pigeon will be more efficient, and it is also officially recommended.

It wouldn't bring any benefits except adding additional overhead for maintenance. So for now no such plans.


DB_USER and DB_PASS became required for all database types

DB_USER and DB_PASS were optional for mongodb, and DB_PASS was optional for many other database types. However, due to recent changes, they now became required for all database types. Failed to supply either one will fail the backup. See error:
[ERROR] ** [db-backup] error: neither DB_USER nor DB_USER_FILE are set but are required
[ERROR] ** [db-backup] error: neither DB_PASS nor DB_PASS_FILE are set but are required
This can be fixed either from the upstream or in this repo. I will work on a temp fix.

I'll take a look at your fix, but in the Readme it states:
If you are trying to backup a database that doesn't have a user or a password (you should!) make sure you set CONTAINER_ENABLE_DOCKER_SECRETS=FALSE
This is a byproduct of us checking for Docker Secrets. Let me know if it works for you?

I like it! I will merge the PR as this fixes having to set the container docker secrets flag. Thank you for this.

Tagged as tiredofit/db-backup:2.2.0

@tiredofit Thanks for the prompt response. 👍
Sorry, I should have checked the updated README. I have been using this image for long and didn't notice the changes made in the README file.


KSP solver

The default KSP is slow. We need to accelerate it.

Through the global.sh script, we find a group of the optimal parameters for  mn(100100) scale as follows:
-ksp_type bcgs -pc_type bjacobi -sub_ksp_type preonly -sub_pc_type sor


AutoFormat feature does not indent function declaration in function calls properly

VSCode Version: 1.24.0
OS Version: Windows 10

Hello everybody !
The following issue is also present on a vanilla fresh install of VSCode Insider.
With the AutoFormat function; when trying to make function declaration inside a function call .then( the indentation of the first function is broken. Subsequent function indentation work as expected until the parenthesis is closed :

As you can see the first function gets aligned as though it was under .find(. As we can see ESLint (active on the project) is picking up on it.
Below you can see that when I manually place the function on the next line, it then indents properly.

Best day to you all 👍

Duplicate of https://github.com/Microsoft/TypeScript/issues/14589


Make it eager

Right now the extension doesn't log network requests if the tab is not focused. It means you have to refresh to get the log. Making it eager should fix it.

Requests are logged if the tab has been focused at least once since devtools was opened. Prior to this, the app has not booted, and therefore no script execution can happen.
A fix for this would be to detect first load and call chrome.devtools.network.getHAR() to return historic network requests and load them into the app.
Are you aware of another method? I am not sure what you mean by "make it eager"?

Eager means it should log as soon as possible, regardless of user interaction. Since you said the extension doesn't execute in the background, the other way around sounds like the solution, getting historic network requests and provide the log for it. Sounds easy to implement too.

PR has been merged for this via the method described above.
https://github.com/warrenday/graphql-network-inspector/pull/17
I'll release this to chrome store soon.

Give this man a huge round of applause. Awesome work @warrenday.


Setting/modifying BIOS settings

We have a need to modify several default BIOS settings when building a new server.  We are currently using the hprest command to do this but would like to have chef do this instead.   Can support for modifying BIOS settings be added to this cookbook?
Here is an example of a few BIOS settings we change from default;
PowerProfile MaxPerf
PowerRegulator StaticHighPerf
ProcHyperthreading Disabled
ProcNoExecute Enabled
ProcTurbo Disabled
ProcVirtualization Disabled
Thanks.

Hey @kreyno96it, yes we can certainly add these settings. We will implement them into the existing ilo_bios resource.


Cleanup and update rescript edgedb

Current dependencies on/for this PR:

main

PR #8   👈

This comment was auto-generated by Graphite.


Enable Tunnel Access from within VS Code

[x] Add command to run the code server on your machine
[x] Allow to configure machine name for tunnel
[x] Copy to clipboard action with vscode.dev URL
[ ] ~Render status bar item when a tunnel connection is established to current machine~

Marking this as closed to clear out the inbox. If there's more work here, let's make a new issue for next iteration.


Use python-saml 2.1.6

python-saml 2.1.6 release
includes a security fix, please use it instead of 2.1.3
Some documents reference old version:

social/tests/requirements.txt
docs/backends/saml.rst

There is a new release with security improvements 2.2.0.
I highly recommended to use it instead previous versions.

Dependency updated and enabled Python 3 integration in social-core.


Check for run script instead of mono run time

Since the path to the mono runtime binary has changed, we must check for the presence of the run script to determine whether the package exists or not.

@DustinCampbell Should we change the path for the mono binary - https://github.com/OmniSharp/omnisharp-vscode/pull/2255/files#diff-b9cfc7f2cdf78a7f4b91a753d10865a2L182 to be bin/mono.osx ?

Closing in favor of : https://github.com/OmniSharp/omnisharp-vscode/pull/2256


version 1.0.1 is not in npm

username, password is not supported by version 1.0.0 which is the latest in npm.
Please fix

published v1.0.1 to npm


Bug: Performance issues since v14.5

Description of the bug
Since we upgraded ng-mocks from version 14.4.0 in our project, our Unit Tests are 3x slower than before. We narrowed the performance degradation down to either v14.5.0 or v14.5.1 (we couldn't get 14.5.0 working without errors).
This is quite an issue for us, since our Unit Test Suite in said project contains ~7k Tests which used to run in 20-60 seconds depending on the machine. These now take 1-3 minutes.
An example of the bug
I'm unsure on how I can demonstrate this as I'm not allowed to share the project as-is. I'm pretty sure though you can take any project, up-/downgrade ng-mocks between v14.4.0 and v14.5.1 and notice a severe performance impact.
Link:
Expected vs actual behavior
No performance degradation compared to v14.4.0.

Hi @pascal-puetz,
thank you for the report.
Could you check how it works with the latest version?
If it's still bad.
Could you record CPU profiler during the test execution and share it with me?

Closing due to silence. Feel free to reopen it with the requested info or steps how to reproduce.
Thank you in advance.


add flags for grammar generation; consolidate get_config_path_str() and get_save_path_str(); prep for supercloud

Looks good. Feel free to ignore, but I think it would be nice to dump two things into the logs (i.e. print) for our future reference:

The full CFG (are we doing this already?)
The git commit (assuming that we are always going to run with a clean git diff on supercloud)

Done, thanks for the suggestion.


Change the testnet bridge from BUSD to TFT

blocked on:
Testnet TFT is out of our control

Changed in https://github.com/threefoldtech/threefold_hub/pull/41

verified


Work out issues with Geoscience Ontology W3ID usage

The GSO used the w3id.org platform for setting up resolvable IRIs. There are some problems with the rewrite rules where the advertised names in the different namespaces are not being handled correctly. These need to be corrected if we're going to be able to count on the IRIs being resolvable. To get things started, I ended up writing correct values into the URL same as properties in the GeoKB, but this is not the right way to do it. I did post an issue on this to the Loop3D repo, but it doesn't look like anyone is monitoring that at the moment. We can fix the problem ourselves with a pull request to the w3id repo (same place we have a /usgs/ namespace for other purposes), but we kind of need to determine how much of an ownership stake we want to take in the Geoscience Ontology moving forward and whether we want to fork it for our purposes or contribute to the core.

This was resolved by the GSO maintainers, but I need to run back through and verify resolvability on all the identifiers we have same as relationships with.


implement gender-preferences in sever

add preferences for gender to the user entity (none at initiation)
can be changed later (account for the event that a user updates their profile)

has this been solved with pull request #162 ?


Very helpful

Very helpful, thankyou

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

ID: fe168fc3-2ed2-b3e6-ce30-cac721165ceb
Version Independent ID: 8d63fbd7-12c4-9a94-92f6-969e7eb41037
Content: Git branching guidance - Azure Repos
Content Source: docs/repos/git/git-branching-guidance.md
Product: devops
Technology: devops-code-git
GitHub Login: @apawast
Microsoft Alias: sdanie

@peterdragon -- Peter, you're welcome!


Protected Attributes breaks Heroku deployment of Rails 4 apps

Using Rails 4.0.0.beta1 with protected_attributes makes heroku deployments fail on precompilation, even using config.assets.initialize_on_precompile = false and heroku labs user-env-compile. Here's a sample of the stack trace:
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_record/mass_assignment_security/attribute_assignment.rb:15:in `attributes_protected_by_default'
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_model/mass_assignment_security.rb:332:in `block in protected_attributes_configs'
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_model/mass_assignment_security.rb:217:in `yield'
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_model/mass_assignment_security.rb:217:in `protected_attributes'
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_model/mass_assignment_security.rb:123:in `block in attr_protected'
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_model/mass_assignment_security.rb:122:in `each'
       /tmp/build_2ts1np9ko79to/vendor/bundle/ruby/2.0.0/gems/protected_attributes-1.0.0/lib/active_model/mass_assignment_security.rb:122:in `attr_protected'

I have no idea why this is the case, but removing protected_attributes from my gemfile immediately fixed the problem.
I'll do some more research and post notes if I figure out what the gem was doing that caused this problem, but in the mean time I wanted to post this issue in case others are running into the same problem.

I believe this is still valid.
The issue is if attr_protected is used, then rails will try to connect to the DB at startup. This prevents asset compilation in an environment where the DB is not available - eg, when building the app into a Docker image.
This is triggered by the call to primary_key in ActiveRecord::MassAssignmentSecurity::AttributeAssignment#attributes_protected_by_default
https://github.com/rails/protected_attributes/blob/master/lib/active_record/mass_assignment_security/attribute_assignment.rb#L15
I don't know if this is fixable or if it just needs to detect the lack of DB connection and show an error message with a suggested solution (ie manually set the primary key in the model)?

I resorted to monkey patching the attr_protected method to do nothing if a certain environment variable is set (which we set when we call assets:precompile)


Remove sig data arg and ret fields to reduce size

Addressing #5183

Ooh, I missed an important detail! args and rets are both in the same abi_args array, so the first one doesn't necessarily start at 0.

More precisely, SigSet::abi_args is laid out with each signature having rets first and then args. This is ensured by from_func_sig, which has a comment saying "Handle retvals first, because we may need to add a return-area arg to the args."
As a result,

self.args_start == self.rets_end.
self.rets_start == prev.args_end, or 0 if there is no previous SigData.

I believe that's the cause of the test failures. They were all off-by-one because the inputs that failed had exactly one return value.
I think this means we could save some more space by keeping one u16 length and one u32 offset in each SigData, but I don't think we should try to do that until we've fixed this version using two u32 offsets. Anyway, if I'm counting right, reducing a u32 to a u16 won't make the struct smaller right now because of padding and alignment, but it could help later combined with other changes.
I'm not totally happy with how confusing this will be for anyone trying to maintain this code in the future, but I think it's worth doing if we add some comments. In particular, extend the comment at the beginning of from_func_sig to mention that the args and rets methods rely on the order in which they're added to abi_args; and add a comment to the args and rets methods saying to see from_func_sig for details.

@jameysharp updated!

I believe this is correct and a good change, but it's tricky enough that I'd like to get a second review from either @cfallin or @fitzgen.


Put the write into the IoContext.

Follow up to https://github.com/arangodb/arangodb/pull/10474

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/7337/

This is gonna make things slow

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/7349/

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/7352/

The problem is that we have correctness problems with SSL and VST and many concurrent requests. The code as it currently is is broken with SSL. In view of the feature freeze and the start of QA testing, let's merge this now and do more performance investigations next week.


🧟♀🧟♂🧟♂🧟🧟♀🧟♂🧟

😱

( no seriously, straceD leaves lots of zombie sh processes.. )

Ahhh, that's slightly clearer :)
Oops.  I didn't realize terminate() doesn't wait(). Should be fixed now.

There's more edge cases. Looks like I have more reading to do.

Seems to be okay now. Though I should still do that reading...


No release found

In the release section there are no release available for now, so i cannot download this extention at this moment

#99


Add more free books javascript

[X] [Eloquent Javascript] (http://eloquentjavascript.net/)
[X] Speakingjs
[X] JavaScript Allongé
[X] [Exploring ES6] (https://leanpub.com/exploring-es6/read)

Who am I ?
Linkedin : frederickinrio
Github: fredericksilva
:heart: +  :family: + :coffee: + :computer: + :facepunch:

sorry! already exists free-programming-books.md#javascript


Update web page

The branch was merged, but seems like I forgot to update the PR and wasn't synced correctly.


Fix potential infinite generator in Market.trades.

Since 5924ac129721f432f3e44d8390dba0c895014ab0 was added, Market.trades is a generator and not a function. In it, there is a single exit condition -- cnt >= limit. However, this condition might never be reached for situations, where the number of returned results is less than required limit.
The simplest test to verify this is to open an empty market  -- trades will never return. Similar thing could happen if you ask for, eg, 50 trades, but the start - stop interval only has 30.

Codecov Report

Merging #150 into develop will decrease coverage by 0.02%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           develop     #150      +/-   ##
===========================================
- Coverage    43.87%   43.84%   -0.03%
===========================================
  Files           34       34
  Lines         3305     3307       +2
  Branches       718      719       +1
===========================================
  Hits          1450     1450
- Misses        1637     1639       +2
  Partials       218      218

Impacted Files
Coverage Δ

bitshares/market.py
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Good catch! Thanks!


Enhanced links

Please add custom links support. It is now impossible to save "chrome://" or "chrome-extension://"links
related: #87

As far as I know this is not allowed by Chrome and I don't think there is anything I can do about it. Thank you.


Reduce tab size in notes panel

Fixes #5591
New tab size:

Hmm 1 is maybe too low, 2 is probably good middle ground

Changed to 2.


Some links in Godot Editor help don't work.

Operating system or device - Godot version:
Manjaro XFCE Edition - Godot 3.0 alpha (https://github.com/godotengine/godot/commit/9a502d3c17d4701b0fd8390e515c52a69dc0bf85)
Steps to reproduce:
Open help->Classes->Viewport.
Press first few method names like clear(), find_world().

I think this issue is the same as one I noticed a while ago. It's been like this for quite a long time on the 3.0 master branch at least.
In most pages, (test Node, Viewport) - without scrolling, links below "Public Methods" do not work, but links above do. You can also see the cursor is stuck as the "link clicking" cursor while over the non-working region. If you scroll down so that "Public Methods" is the first visible line, the links work.
In pages like @GDScript (because it has no links before Public Methods?), all the links work without scrolling.

Been like this for a long time..  https://github.com/godotengine/godot/issues/3671

Duplicate of #3671 indeed.