[5.2] Added reply_to field for SparkPost API request within SparkpostTransport

Added reply_to field for SparkPost API request within SparkpostTransport
Signed-off-by: Byron Smith byronsmith@30db80bfe262

What about the other drivers please?

Happy to contribute to the Mailgun transport, but mandrill is no longer a free service, and I don't have a EC2 instance for SES. I therefore wouldn't be comfortable implementing code I cannot test.
With that in mind, where does that leave me in terms of having this SparkPost improvement merged?


Error response from daemon: application/vnd.docker.distribution.manifest.v1+prettyjws not supported

Following the "Getting Started" README and executing make docker_build_and_up on a fresh clone of master results in the error Error response from daemon: application/vnd.docker.distribution.manifest.v1+prettyjws not supported
M1 Macbook (MacOS 13.3.1)
Docker Desktop 4.20.1

@des1redState Would you mind creating a PR for this?
/kind bug


Timestamp for measurement

https://github.com/DMTF/SPDM-Responder-Validator/blob/5ae6af6e38c2a902d144dd22218952766b095287/doc/7.Measurements.md
The measurement should have a time stamp field to indicate when the measurement was done.

I am confused here. SPDM spec does not mention time-stamp.
Are you asking feature request for SPDM specification? If so, please file an issue in SPDM-WG not here.


Crates.io release

Release rust sdk on crates.io and/or roadmap/timeline for release

Released under the crate hedera as 0.5.0


Publish operator manifests during release

This PR publishes the operator Kustomize project as a compressed bundle.

This isn't at the right place. my bad. Because operator manifests needs to be in operator release.


Icons are not accessible

Issue Type: Bug
Icons are not accessible. There should be tooltips for the icons (like settings, Accounts, and all the other icons I have no idea what they mean) or an option to show the text.
I am using Mac desktop version of Azure Data Studio
Azure Data Studio version: azuredatastudio 1.34.0 (83a4316cf89cbf961a0f09a72c861379cfd01fa9, 2021-12-15T20:50:08.229Z)
OS version: Darwin x64 21.3.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
7, 6, 6

Memory (System)
32.00GB (0.43GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

@lucyzhang929 Could you verify if you're seeing this too? I see the tooltips just fine on Windows

I am able to see the tooltips on Mac. The tooltips do take one or two seconds to appear especially the first time I hover over the icons.

Closing as "no repro" since we are seeing hover tooltips in this scenario.  Please try ensuring the application was responsive when testing this scenario and leave the mouse hovering over icon for a few seconds while the tooltip is being shown.  Thanks for reporting this issue.


Click in a MDI Tabed windows

Hi,
I'm trying to click on a tabbed  MDI window and I do not get it.
I can click on the typical tab-type components of the Windows with multiple information, since I locate them with the inspector. But I can't locate the tabs of the MDI windows. Neither does the "x" to close them.
I can capture the MDI window through his handler and all the elements of each of the MDI windows, but not the tab to select it and focus it (the windows is hide for the selected windows of the focused tab).
Any idea of how you can access these elements?, are graphical elements or windows objects?
Thank you

Hi @macervera,
Can you clarify if you can see the MDI tabs using Inspect and which exact MDI application that you're using?
Can you try seeing if you are able to access the tabbed elements from UI Recorder?

Hi,
I can't see the MDI tabs using Inspect.
The application is the typical VB application that have a Main form and open MDI tabbed windows when you click in the menu options.
I try with UI Recorder and don't see the MDI tabs. The UI Recorder suggest me a click by coordinates.
Regards,

Hi again,
When i use Inspector in order to see the tab, inspector show the MDI window. I download the Source and i can see the tab.
It's possible click the tab using the MDI  windows or other functionality of WinAppDriver.
Regards,

Hi @macervera,
Are you using Inspect.exe or Appium Inspector? If Inspect.exe is unable to identify the MDI element, then WinAppDriver will not be able to interact against it. This is by design.
Can you post a screenshot of Inspector identifying the element if I misunderstood?
Thanks

Inspector.exe don't see the MDI tab, it only can "see" the MDI window.
There are a way to Bring to Front the MDI window? In .NET or VB i can use the BringToFront() method, can i use some similar method in WinAppDriver? this will simulate the tab click.
Regards,

Hi @macervera,
Is it "Inspector" or "Inspect.exe"? If it isn't in Inspect.exe, then WinAppDriver will not be able to automate against it.
As far as bringing it to the front, perhaps you can try using a SendKeys from the session and see if you can send a "CRTL + TAB" command to iterate between the tabs?

Sorry, its inspec.exe.
The control is a DevExpress control and dont expose the objects to be automated.
I see in the DevExpress wiki that by default the DevExpress controls are hidden to the automation, in order to increase his performance. There are a control property (that must be setted by the development team in the source code) to show the control to the automation tools.
Thanks,


Expose node agent INGRESS_GATEWAY_FALLBACK_SECRET and SECRET_WATCHER_RESYNC_PERIOD as Helm configurations

Expose SECRET_WATCHER_RESYNC_PERIOD and INGRESS_GATEWAY_FALLBACK_SECRET as Helm configurations.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@Monkeyanator: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
28e03ee40b3a299c6916ba96cbc7c7e82345b96d
link
/test e2e-simpleTests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
28e03ee40b3a299c6916ba96cbc7c7e82345b96d
link
/test e2e-simpleTests_istio

integ-new-install-k8s-tests_istio
28e03ee40b3a299c6916ba96cbc7c7e82345b96d
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simpleTests_istio

What do we need these for? Users can set these without being in values.yaml and they are already documented as env vars on istio.io

These configurations aren't documented here like nodeagent.env.CA_PROVIDER and nodeagent.env.CA_ADDR are. Might be that we could just change the docs, but the per-component docs are generated from the values.yaml comments.

@istio/wg-security-maintainers please take a look


Login error code: 5024

I encountered a situation where I could not log in. Here are the logs.
09:18:02: Please log in to continue.
09:18:10: Login error code: 5024
09:18:10: Your login attempt was denied by CAPTCHA.
09:18:10: Please try again in 12+ hours.
09:18:10: Exiting...
09:18:11:
09:18:11: Application Terminated.
09:18:11: Close the window to exit the application.

The ones already logged in are working properly, but new logins are not available. I tried the browser and the login for the relevant account is working fine.

This is usually caused by logging into multiple accounts, Twitch has made restrictions on this, and it also tells you that it takes at least 12 hours


nk.storageList returns private objects

Description
Calling nk.storageList(null, collection_name, 10) returns objects that should not be readable.
Steps to Reproduce

Create various storage objects with permissionRead set to 0, 1, 2
Call nk.storageList(null, collection_name, 10)
Inspect the results and see that all objects are returned

Expected Result
Only objects that have public read permission or belong to the current user should be returned
Actual Result
I get a response like this:
[
    {
        "collection": "cards",
        "version": "2488e59d6392a3412a72e21d5c9b3d3f",
        "permissionWrite": 1,
        "createTime":<PHONE_NUMBER>,
        "updateTime":<PHONE_NUMBER>,
        "key": "6be82de6-2dd3-46da-8350-5f1040cd5b82",
        "permissionRead": 0,
        "value": {
            "text": "This card is only user 1"
        },
        "userId": "a4ff99bb-f481-46ef-ba22-1e78406e6473"
    },
    {
        "permissionRead": 0,
        "permissionWrite": 1,
        "createTime":<PHONE_NUMBER>,
        "value": {
            "text": "This card is only user 2"
        },
        "userId": "b2da6a30-4bcc-4184-8e53-824d0302ebc1",
        "version": "db0efeee4f01f50c936994f39a761bda",
        "updateTime":<PHONE_NUMBER>,
        "key": "baf11449-9e7c-4cff-b46e-5ddde1250523",
        "collection": "cards"
    },
    {
        "permissionRead": 2,
        "createTime":<PHONE_NUMBER>,
        "updateTime":<PHONE_NUMBER>,
        "key": "8a703ab0-45f2-434f-9403-3432d7399dbb",
        "collection": "cards",
        "userId": "a4ff99bb-f481-46ef-ba22-1e78406e6473",
        "version": "d230ffb0a87e7b70b7072d740ffc422e",
        "permissionWrite": 1,
        "value": {
            "text": "This is a public card"
        }
    }
]

Context
Using JS RPC functions that I added to nakama-project-template.
Your Environment

Server version: 3.16.0+27ba93d3 running in Docker

Update: based on the documentation for storageList, instead of null, I should pass in an empty string for the user ID. But I tried that as well, and end up getting this error:
template_nk_backend   | {"level":"error","ts":"2023-09-07T14:49:05.948Z","caller":"server/runtime_javascript.go:551","msg":"JavaScript runtime function raised an uncaught exception","mode":"rpc","id":"get_cards","error":"TypeError: expects empty or valid user id at github.com/heroiclabs/nakama/v3/server.(*runtimeJavascriptNakamaModule).storageList.func1 (native)"}

You are running this code in the server runtime. The server bypasses the permissions at all.

You are running this code in the server runtime. The server bypasses the permissions at all.

That doesn't make sense. According to the documentation, and common sense, storageList without a user id should only return publicly readable objects. Yeah, I could manually filter them, but then I'd still be doing that on the server, or risk exposing private information on the client, and it would break pagination of the results. Much better to fix the bug in storageList so that it returns the correct items.

This is the expected behaviour from calls from the server runtime, for the permissions to apply one should use the client facing APIs.

In case anyone else comes here with a similar problem, I found the documentation for the client side API here: https://heroiclabs.com/docs/nakama/concepts/storage/collections/#list-objects


Try ClimaCore with CUDA ext

This PR tries out https://github.com/CliMA/ClimaCore.jl/pull/1687

Most jobs passed, the only failures seem to be from known breaking changes in ClimaCore, and imports that need fixed in ClimaUtilities. I opened an issue. I'll close this PR and merge https://github.com/CliMA/ClimaCore.jl/pull/1687


Invalid timestamps

https://github.com/prometheus-community/stackdriver_exporter/pull/84 introduced timestamps, this produces invalid data for some metrics.
stackdriver_tcp_lb_rule_loadbalancing_googleapis_com_l_3_external_rtt_latencies_count{...} 1 -62135596800000

cc @lahsivjar

Ack, will investigate this today

@SuperQ Created PR for fixing it, #94


Url.Action takes attribute routing in to account, but not clear how

Description of the problem:
Url.Action("index", "base", new { loginid = clientKeep.Login, pwd= pwd}, "https");

Returns
https://Contoso.com/default.aspx?login=<login>&pwd=<pwd>
where the action in the BaseController is:
       [ HttpGet]
       [AllowAnonymous]
       [Route(""), Route("default.aspx"),Route("index")]
       public async Task<IActionResult> Index([FromQuery] string loginid, [FromQuery] string sessionid)
       {
       }

where I would like to have
https://Contoso.com?login=<login>&pwd=<pwd>

the default.aspx is for backward compatibility.
I tried to change the order of the routing attributes, but this did not change the result.
I think it should be predicable and controllable which of the routing attributes is used.
Microsoft.AspNetCore.App 2.1.1
Microsoft.NetCore.App 2.1.0
dotnet --info:
Host (useful for support):
Version: 2.1.5
Commit:  290303f510
.NET Core SDKs installed:
No SDKs were found.
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Thanks for contacting us, @vankampenp.
@JamesNK, can you please look into this? Do we need to add some documentation to make this clear or is this something we missed? Thanks!

/cc @rynowak

This happens because when the attribute router matches the routes, matching routes are sorted before being evaluated and only the first result will be used to generate the URL. For the sorting, the comparer will look at the route order and the precedence which is being calculated to give more complex routes a higher precedence.
Since the empty route "" has no complexity at all, it has a zero precendence, while the non-empty routes have a non-zero precendence. And since all Route attribute have the default order of 0, the two non-empty routes will be preferred over your empty route. And then it’s just a matter of what comes first in the alphabet which is why default.aspx wins over index.
The fix for this is pretty simple: You just have to set an explicit order on the attributes:
[Route("")]
[Route("index", Order = 1)]
[Route("default.aspx", Order = 100)] // legacy might as well get an order of 100
public async Task<IActionResult> Index() { … }

That way, the empty route will be sorted before your other routes, so that’s what’s going to be used to generate the URL for the action.

@poke Thanks for the excellent and clear answer. Your solution works.
I would have never guest the alphabet  sorting for creating the Url. Basically I assumed that there was a default Order attribute. My bad.

Thanks @poke for the explanation.
I want to also mention about this part:

And then it’s just a matter of what comes first in the alphabet which is why

This is something we do so that routing has a predictable and consistent behavior when its ambiguous which one to choose. If you're relying on this for correctness then it's not good, but unfortunately not easy to detect. Using Order to control the behaviour is the right thing to do.


added favicon to docs

this PR adds favicon to reason docs.
started learning ReasonML, opened tons of tab, lost reason docs, realized reason doesn't have a favicon.

Nice. Thanks!


Fix missing version information in user-agent header

Motivation:
HttpClient sends the 'user-agent' header with incorrect version
information. It's sending artifactId instead of artifactVersion.
Modifications:

Use artifactVersion instead of artifactId
Use correct class loader

Result:
The 'user-agent' header value includes the version information.

Current coverage is 65.62% (diff: 66.66%)

Merging #284 into master will increase coverage by 0.10%

@@             master       #284   diff @@
==========================================
  Files           303        303
  Lines         11954      11955     +1
  Methods           0          0
  Messages          0          0
  Branches       1750       1750
==========================================
+ Hits           7832       7845    +13
+ Misses         3287       3278     -9
+ Partials        835        832     -3

Powered by Codecov. Last update f6eb92f...436723d

LGTM 👍

Thanks, @kawamuray


Integrate pyproject.toml into the project

This patch adds pyproject.toml as a better alternative to requirements.txt. It helps to standardize the project configuration and dependencies in a well-defined manner. By utilizing pyproject.toml, we can specify the build system, project metadata, and manage dependencies all in one place.

It looks weird, I didn't get a warning locally about linters when I committed.


Add Digitalocean - post processor option

As discussed in SIG/Cloud channel
This is the implementation of what was recommended by DigitalOcean at
https://github.com/digitalocean/marketplace-partners in order to build
an image that passes all tests.

@renich Thank you for PR


Error on non-Debian Linux distros and VS Code: unknown package

Hi all,
I have followed the exact instructions on how to install Lean on VS Code I could find on https://leanprover-community.github.io/install/linux.html which also happen to be the instructions specified for this project and despite my best effort when I try to import modules (e.g. here data) from mathlib4 I get:
unknown package 'data'
You might need to open '' as a workspace in your editor

From what I can gather in the official instruction above there is no mention that mathlib4 needs separate installation steps and the documentation suggests that I should have been installed together with the VS Code extension and/or the main elan-init.sh step. Otherwise I would have expected separate instructions in the link above.
Am I missing something obvious here? Is there some path environment variable I can use to just set the path to the mathlib library if I simply clone it or documentation about how to do this I have missed?
Thanks in advance.

Just to add: I believe this is a Github issue because if I was right above it indicates lack of sufficient documentation on how to do this and something we could try and fix (I am willing to contribute if you would prefer so).

Indeed, just a bit later I realized that all the imports have been renamed in lean 4 (which I guess while breaking a lot of old compatibility is justifiable by the major version counter) but unfortunately encountered the very same problem importing the newer modules. I even tried manually placing the library and then separate lean files and trying to import them as:
[pevogam@vagrant experiments]$ find -maxdepth 2
.
./Test
./Test/test.lean
./Mathlib
./Mathlib/Util
./Mathlib/Algebra
./Mathlib/Data
./Mathlib/Lean
./Mathlib/Deprecated
./Mathlib/CategoryTheory
./Mathlib/Analysis
./Mathlib/Mathport
./Mathlib/Control
./Mathlib/Logic
./Mathlib/Order
./Mathlib/InformationTheory
./Mathlib/Geometry
./Mathlib/AlgebraicGeometry
./Mathlib/Combinatorics
./Mathlib/MeasureTheory
./Mathlib/ModelTheory
./Mathlib/RepresentationTheory
./Mathlib/Tactic.lean
./Mathlib/Topology
./Mathlib/LinearAlgebra
./Mathlib/RingTheory
./Mathlib/Dynamics
./Mathlib/Probability
./Mathlib/SetTheory
./Mathlib/GroupTheory
./Mathlib/NumberTheory
./Mathlib/Init
./Mathlib/Testing
./Mathlib/AlgebraicTopology
./Mathlib/Computability
./Mathlib/Tactic
./Mathlib/Condensed
./Mathlib/FieldTheory
./imports.lean
./test2.lean
./exploration.lean

where
[pevogam@vagrant experiments]$ cat imports.lean
import test2
import Test.test

results in unknown package 'test2' or if I comment out the first line in unknown package 'Test'. The same happens for the Mathlib I manually placed as a folder within the project and any out-of-the-blue Mathlib folder I try to import globally that should have been installed somewhere.
Note that I copied the folder after I could not important any supposedly preinstalled package. Any expressions with built-in keywords work fine with the Lean interpreter.
I originally tried using mathlib4.Mathlib as well as  Mathlib  in an extra file in cloned Lean examples repo (I hope this didn't mess up anything, I still installed the VS Code plugin with the single recommended click). The above was then my attempt to move to a separate project that I would open as folder in VS Code. No module could be imported, preinstalled, manually copied, manually created, or otherwise.

Did you follow the instructions in https://leanprover-community.github.io/install/project.html (linked at the bottom of the link in your first post above)?
In general copy-pasting mathlib to a new directory will not produce a workable tree.
Mathlib and other lean dependencies are managed by lake, a program installed with lean. And the dependencies are managed for you based on a lakefile.lean and other auxilliary files in your project.
Are you trying to clone and work on mathlib or create a project with mathlib as a dependency?

Also I should say that Lean doesn't really follow the traditional semver, its more like major version number is a complete rewrite with little guarenteed backwards compatibility at all. middle number is possibly breaking changes also and maybe only the smallest number is bugfixes etc.

Did you follow the instructions in https://leanprover-community.github.io/install/project.html (linked at the bottom of the link in your first post above)? In general copy-pasting mathlib to a new directory will not produce a workable tree, neither will any other manual approach.

I tried the exact instructions and after I could not find the library by importing it (and read a page about importing lean modules), I decided to try these manual steps as a last resort.

Mathlib and other lean dependencies are managed by lake, a program installed with lean. And the dependencies are managed for you based on a lakefile.lean that you write and other auxilliary files in your project (that are not really to be human edited).
Are you trying to clone and work on mathlib or create a project with mathlib as a dependency?

Just trying out a simple standalone project that needs a few Mathlib imports. I just pushed a bit harder and got it working with a bash script like
$ cat new_workspace.bash
workspace=$1
project=$2

lake +leanprover/lean4:nightly-2023-02-04 new ${workspace} math
cd ${workspace}
lake update
lake exe cache get
mkdir ${project} || echo "Create project manually in the new worskpace"

echo "Workspace created"

that could be a simpler alternative to the somewhat overlapping description in these two sources:
https://leanprover-community.github.io/install/project.html
https://github.com/leanprover-community/mathlib4/wiki/Using-mathlib4-as-a-dependency
Considering how easy it was to run Lean directly by installing an add-on with VS Code I thought installing the mathlib4 would already be available but it seems I was wrong and I apologize for costing you some time here. In any case regarding the two sources above I would recommend this change, let me know what you think.

Also I should say that Lean doesn't really follow the traditional semver, its more like major version number is a complete rewrite with little guarenteed backwards compatibility at all. middle number is possibly breaking changes also and maybe only the smallest number is bugfixes etc.

Good to know, I already expected breaking changes from the major version increment.

The suggested change wasn't reviewed, merged or rejected so I expected the related issue to be open and thus tracked properly until then.

You'll need to tag that issue with awaiting-review if you want it to show up on the review queue that people look at (see https://leanprover-community.github.io/contribute/index.html#lifecycle-of-a-pr). As there are ~600 open PRs most potential reviewers will not end up seeing it, or realise that it is complete until then.

You'll need to tag that issue with awaiting-review if you want it to show up on the review queue that people look at (see https://leanprover-community.github.io/contribute/index.html#lifecycle-of-a-pr). As there are ~600 open PRs most potential reviewers will not end up seeing it, or realise that it is complete and ready for review until then.

As a contributor I don't think I have the necessary permissions to set labels on pull requests - in fact the link you shared confirms this and suggests that I should first ask for a write access? This might be a bit of an overkill for the contribution size but in any case thank you for the hints and pointers.

Yeah that is another issue with PRing from forks, I forgot about that too.
I do think it would be valuable to make the contribution process for small doc changes easier, it would probably allow more people to get started contributing that may not otherwise. @semorrison what do you think of adding the std / core "comment to add label" action to mathlib (if it isn't already) and explicitly spelling out that the if someone wants to make a quick doc edit they can do so in this way (and add the label) without having to join zulip state their plans and wait to be approved?


dua: 2.14.2 -> 2.14.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Byron/dua-cli/releases.
meta.description for dua is: "A tool to conveniently learn about the disk usage of directories, fast!"
meta.homepage for dua is: "https://github.com/Byron/dua-cli"
meta.changelog for dua is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/1nn3h28p58wj8grlcq8rj6l6f1bg2fjj-dua-2.14.3/bin/dua passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 2.14.3 with grep in /nix/store/1nn3h28p58wj8grlcq8rj6l6f1bg2fjj-dua-2.14.3

found 2.14.3 in filename of file in /nix/store/1nn3h28p58wj8grlcq8rj6l6f1bg2fjj-dua-2.14.3

directory tree listing: https://gist.github.com/a666b4624dcd86863ccac3fd960b6d6c

du listing: https://gist.github.com/b2db2809876c053a52a75ce5f4f51301

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dua

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1nn3h28p58wj8grlcq8rj6l6f1bg2fjj-dua-2.14.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dua https://github.com/r-ryantm/nixpkgs/archive/70e82969cdec98201f3f6cf8491dd47a5c2558d9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1nn3h28p58wj8grlcq8rj6l6f1bg2fjj-dua-2.14.3
ls -la /nix/store/1nn3h28p58wj8grlcq8rj6l6f1bg2fjj-dua-2.14.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dua

Maintainer pings
cc @killercup for testing.

Result of nixpkgs-review pr 131517 run on x86_64-darwin 1

1 package built:

dua

I think this is fine to merge


Update README to bring inline with the new ember-cli-deploy

Please do not merge this. It is a work in progress.
Please feel free to comment on or modify anything you think makes sense and adds value.
Closes #49

Lads, here's my first crack at a new README.  Feels like there are still a few things up in the air but it's a start.  Please leave feedback.
Questions and comments that I have currently are:

Have left the example config/deploy.js blank as I don't feel what we currently have is a good reflection of where we are going.
Have only added ember deploy at this stage as I'm unclear as to what will actually be needed other than that.  ember activate feels very specific to the lightening deployment approach.  Happy to add it back in if need be.
I have taken the detail on what a plugin hook should resolve/reject with from the ember-cli ARCHITECTURE.md file.  It sounded reasonable.  Let me know if it's not.
Will we provide a Plugin object that can be extended?  This seems like it could be a good idea.
Following on from number 4 above, will we instantiate the plugin with a UI instance to allow it to write to the console?  This is how Tasks and Commands are created and seems like a good idea for us.
Maybe it could be a good idea for us to have a PLUGINS.md or PLUGIN_HOOKS.md file in the root which gives a detailed overview of what makes up a plugin and what the hooks are for.  Especially, if the list of hooks grows this might become useful.  And it means we can keep the README to be more about what ember-cli-deploy is about generally.

Anyway, that is a bit of a brain dump.  I welcome any feedback.

Looking good so far. Some of this could end up living in DEVELOPING_PLUGINS.md per #71. I'm going to tag this for 0.5.0.

Closing in favor of all the awesome docs work that has landed.


Update to latest NodeJS runtime which contains latest Openwhisk package, 3.16.0

The NPM package for 'openwhisk' was recently upgraded from 3.15.0 -> 3.16.0.
The change was done in the NodeJS runtime repository to update the package.  That change can be found here: https://github.com/apache/incubator-openwhisk-runtime-nodejs/pull/75/files
This change is to update OpenWhisk to have the latest version of the NodeJS runtime.

https://github.com/apache/incubator-openwhisk-runtime-nodejs/pull/75 merged already.


yb_show_latency also alters player pings

yapb seems to also change the 'regular player'-pings, when using these parameters:
yb_show_latency "2"
yb_ping_base_min "14"
yb_ping_base_max "38"

thought this option only affects the bots ping?!
using latest yapb-master on linux, with latest rehlds/regamedll_cs/reapi/metamod-r.

yup

Should be fixed in latest commit.

thank you - the players ping seem fixed now.
but it seems like the bots dont comply to the yb_ping_base_-parameters anymore.


Build is failing on master after upgrading cross-undici-fetch

After merging https://github.com/dotansimha/graphql-yoga/pull/1261, the build and vercel deployment on master started to fail. The reason for this is the patch for service-worker-mock, which does no longer exist.
$ patch-package && husky install
--
02:40:50.853 | patch-package 6.4.7
02:40:50.853 | Applying patches...
02:40:50.857 |<EMAIL_ADDRESS>✔
02:40:50.859 |<EMAIL_ADDRESS>✔
02:40:50.861 |<EMAIL_ADDRESS>✔
02:40:50.863 |<EMAIL_ADDRESS>✔
02:40:50.864 |<EMAIL_ADDRESS>✔
02:40:50.865 | Error: Patch file found for package service-worker-mock which is not present at node_modules/service-worker-mock
02:40:50.865 | ---
02:40:50.865 | patch-package finished with 1 error(s).
02:40:50.868 | error Command failed with exit code 1.
02:40:50.868 | info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
02:40:50.915 | Error: Command "yarn" exited with 1

It exists here;
https://github.com/dotansimha/graphql-yoga/blob/master/examples/service-worker/package.json#L19
Vercel ignores it somehow...

vercel ignores the examples folder because of the .vercelignore entry: https://github.com/dotansimha/graphql-yoga/blob/14d8811c50ba1666b86100a9aa498782cf91e890/.vercelignore#L1

Because of the scripts/vercel-ignore-build-step.sh script, this build failure got unnoticed as it skips renovate PRs.
We originally introduced that script in order to reduce noise and a clogged-up vercel build queue for all the PRs created by renovate. However, as we are now batching renovate updates into less frequent PRs it should be fine to run vercel builds/deployments on every PR.

Fixed!

Closed as part of https://github.com/dotansimha/graphql-yoga/pull/1265


global: addition of JSON/XML file previewer

Adds support for JSON and XML file previewing (closes #18)

Signed-off-by: Alexander Ioannidis<EMAIL_ADDRESS>

Coverage decreased (-0.4%) to 92.484% when pulling 444376d183087c2614ed38a921ff4e73cf0dbf76 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.484% when pulling c4009f9b8b022b460b70c3dd8d370a11f34830d0 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.484% when pulling 040ec52b829af34e1188fb13761d4a2c0c852c77 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.484% when pulling 0312d41e8b35e39a9d155e5abe17dfaf9bf0c799 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.484% when pulling 73bbb6efe8789566c88d332ec3d47ff4d52eeffd on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.484% when pulling df49a2c4fc4e54569f5f617d69446af028ef3921 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Perhaps the extensions should be called json_prismjs and xml_prismjs, so that later we can support other previewer engines for the same format.

Coverage decreased (-0.4%) to 92.508% when pulling a3894fa0daaaecb24c0e16bb5671a2dc26d935cd on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.508% when pulling 4885932b23c236a5d5f0662250c85b7e00dddb51 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

Coverage decreased (-0.4%) to 92.508% when pulling ea3188b332cbfd60cd98801e4a813b73d7e25ab5 on slint:xml_json_previewer into d4f8167f01a9012bc73528d8303fb313c7bbe60c on inveniosoftware:master.

@slint Really good work, thanks! :-)
@jirikuncar I don't have the rights, but as far as I can tell :shipit:


Define a test/demo case

The current code seems to be assume that all MC files will be processed and they are all processed.
A common test folder might be useful

Automatising this in a CI process is challenging...However, currently it exists a way of easily creating (by symlinking) a small production of the current AllSky MC prod on any desired path
https://github.com/cta-observatory/lstmcpipe/blob/master/lstmcpipe/scripts/generate_test_lapalma.py


Add module "base64id" to compression blacklist

See: https://github.com/tessel/project/issues/347

@apekearo this has been fixed and released in<EMAIL_ADDRESS>


Bitcoins missing since one month

I send 3 bitcoins in my wallet created in Copay and then the next day my bitcoins diappear and only 0.47 Bitcoin is left in my wallet, I have contacted the support service right away, now one month has passed, several peoples answered my request with some standard responses, and my bitcoins are still missing. Is it true that copay secure our bitcoins?

No please report to bbb.org

Please file a complaint with https://www.bbb.org/ as they are only ones to take notice with our issues! 2 weeks nothing from bitpay customer service other people months.. people want their money every complaint builds traction!!
BitPay keeps closing my issues with no solution everything is being recorded and I will not stop until the end of this company or people get there money back!! I have tried the input of 12 words into another wallet doesn’t work I tried everything I can do on my end doesn’t work and my BTC isn’t even in the same wallet anymore something is very fishy here!!!!

Hello,
We apologize for the long delay in follow up. Bitcoin grew a lot in 2017. This resulted in doubling the number of support inquiries we get, so it has taken much longer to get back to you. We have hired additional staff and made improvements to our support process to be more effective.
We are re-arranging our tickets in order to improve our service.
Please update your BitPay wallet app to the latest version, and let us know if you have any more issues.
If you are using the BitPay wallet on your mobile device, please update the wallet application in the App Store (iOS) or Google Play Store (Android). If you are using the wallet on a desktop computer, you can download the most recent version of the BitPay wallet here.
Since this thread did not have any responses in a while we will be closing it.
Please if you still need support, open a new one, we will be happy to help you.
Thanks.

@yycc6
I can recover your wallet if you want need help send me email<EMAIL_ADDRESS>


Define default maximum accelerations for MoveIt

This defines default values for maximum joint accelerations, as MoveIt is otherwise not able to perform time parametrization. The 5rad/s² are from the discussion in https://github.com/UniversalRobots/Universal_Robots_ROS2_Description/issues/46.
This patch only passes these limits to MoveIt. While we could also add them in ur_description, this seems incorrect. The robot does not inherently have any limits on joint accelerations (only on torques), and other software using ur_description might be able to handle this differently.

Thanks for testing this, as well @sea-bass