deis push: push to Deis from local Docker graph

From @renegare on December 6, 2014 14:25
In order to deploy a privately built image to deis cluster
As a developer
I would like to execute the following commands to push and deploy a local image

`deis push <local_image_name>:<tag>`
`deis deploy <local_image_name>:<tag>` # not to be confused with `deis pull`

Currently as of deis v1.0.2 all of this is possible, but through the [not so elegant] steps:
docker build -t <app_name>... # build your image locally
docker tag <app_name>:latest <IP_ADDRESS>:5000/<app_name>:`git rev-parse --short HEAD` # tag your app locally
ssh -Nf -L 5000:<IP_ADDRESS>:5000 core@$REGISTRY_HOST # port-forward the deis-registry port (make sure also your docker daemon allows this insecure registry)
docker push <IP_ADDRESS>:5000/<app_name>
killall ssh # not elegant
deis pull <core-host-docker-registry-service-ip>:5000/<app_name>:<tag> # actually deploy your image

This clearly not elegant (I have it running on a CI #ignant) and a few too many moving parts.
I'm hoping for a discussion around this, I am still oblivious to any related concerns around the possibility of this feature.
Copied from original issue: deis/deis#2680

From @PierreKircher on December 6, 2014 14:30
wont work everywhere ..:> http://content.screencast.com/users/blackdolpinmedia/folders/Jing/media/e712a502-2c06-4fce-bca6-40d54557d8c7/00000013.png
to example .. is a simple vrrp ( floating ip aka lbl construct ) .. the nodes them self just got a privat lan.. so youd need to push the stuff throw the lbl + register the registry on the deis-router which is not the case right now .. nor does deis support auth for the internal reg .. (security consirn) .. use a external privat registry .. thats the best bet right now

From @renegare on December 6, 2014 14:49
@PierreKircher the hackyway I described above, is by creating a direct connection to the deis-registry (and has nothing to do with a load balancer or router). One can use fleetctl / deisctl to track down the IP of the deis-registry unit.
What I never made clear from the beginning is that deis does not currently support private docker registries (correct me if i am wrong). And that was the driving factor of this.
Not every one pushes through the Buildpacks, and Dockerfile deployment takes a long time to build.
Finally: no deis components have been modified in order to achieve this. More of hacked work flow than a hack in the code.

From @mboersma on December 6, 2014 15:38
@renegare we did actually have a PR at one point to add deis push to the mix: https://github.com/deis/deis/pull/1412. I can see how it would be useful. I've kept these commits in a branch in case we want to resurrect it. I think the main issue was how to deal with registry authentication, but there may be more to it than that.

From @renegare on December 9, 2014 12:36
@mboersma, am I right in assuming that if we had a deis push command, all requests will need to go through the lbl > router > controller > registry?
If so (which I think is entirely possible) performance concerns me and will invalidate the usefulness of this feature. E.g. pushing a heavy image blocks other app requests from getting through etc ...
How does git push flow internally work from a high level?

From @renegare on June 8, 2015 13:46
Nice one guys. Been AWOL, but great to see this.

From @carmstrong on June 7, 2015 19:55
This feature is on our open roadmap: http://docs.deis.io/en/latest/roadmap/roadmap/

From @wenzowski on March 11, 2015 8:15
/bump to join this thread

From @bacongobbler on December 9, 2014 16:6
http://docs.deis.io/en/latest/understanding_deis/concepts/#build-release-run
git push goes from lbl > router > builder, which builds the image, pushes it to the registry and notifies the controller that a new build has been created.

From @aledbf on June 26, 2015 23:32
@bacongobbler please do not remove deis pull. I use a remote registry to deploy to production, not something from a local docker graph

From @bacongobbler on June 26, 2015 23:38
I guess there's no true need to remove it. The motivation to remove deis pull is that it's a giant hack to pull in an image, with intimate logic around the v1 image layer format. It doesn't work with v1.6+ images at all and we cannot support it with the v2 registry unless we re-implemented the crazily slow "pull, push, pull" workflow with a docker engine, so we'd need to do that in tandem with #3814.
cc'ing @mboersma for visibility since he's working on the v2 registry

From @bacongobbler on June 26, 2015 22:24
So to think about this feature, there are a few things I can think of. If this is good, then I'll move to a more formal proposal with doc changes:

break out the authentication API in the controller as its own microservice. It should be pluggable, having the ability to communicate to other auth servers (like LDAP). This'll most likely be pulling out the existing auth service built into the controller and re-implementing it as a standalone service
update reference docs, API docs, architecture diagrams etc. to reference this new service
lock down auth access through registry v2's pluggable auth system by communicating to this new auth microservice. This means we're blocked until we close #3814, since the v1 registry has no pluggable auth service
provide a client workflow that wraps docker push with the auth server + a call to the controller to create a new build
deprecate deis pull with this new workflow. This might be just a big fat warning in the client before we remove those endpoints in a future release.

Does that seem reasonable to everyone? :)

From @alexanderkiel on August 25, 2015 21:17
I really like the idea from @renegare of a simple deis deploy <image> and I like to extend it to remove the need of a deis push before it. The deis client could handle the retrieval of local or remote images and just deploy it through one single API. There is no need that the deis servers pull images from somewhere or that I have to push images into the deis registry before I can deploy them. All I want to do is: create an app, deploy an image and config it.

This issue was moved to teamhephy/workflow#42


⚠ Cioos Pacific CKAN has degraded performance

In 92fe9db, Cioos Pacific CKAN (https://catalogue.cioospacific.ca) experienced degraded performance:

HTTP code: 200
Response time: 11715 ms

Resolved: Cioos Pacific CKAN performance has improved in 718f2c0 after 16 minutes.


Merge v1.31.2 into main

This merges the v1.31.2 changes into main for the upcoming v2.0 release.
The changelog is a bit convoluted because of the v1.31.2 release happening in parallel with v2.0 development. Maybe we can condense the 2.0.0 and 2.0.0 Preview 1 notes? Let me know your thoughts.

Thanks for the pull request @j9liu!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.

Thanks @j9liu! I re-added v1.31.2 to the changelog, because we don't want to lose the history of that version. I also added the one "Addition" from v1.31.2 to the v2.0.0 section. It's a little awkward to have these two different versions listed in a single changelog, but I don't think it's worth the trouble to separate them. So in the absence of that, the idea is just 1) list all the versions that we've released, 2) put them in chronological order, 3) the changes listed are relative to the previous version in that "line".


Api 7384

Added a test for binaryAttachment which has a URI rather than the includedBinaryObject which we haven't yet implemented logic for. This means the test is failing but I didn't want to forget this scenario


Multiple instances of the integration doesn't work for EU users

Is your feature request related to a problem? Please describe.
When adding a second login from the EU, the second integration won't add as it says it is a duplicate
Describe the solution you'd like
A second instance of the integration should work
Describe alternatives you've considered
N/A
Additional context
General support for multiple instances was added to the  integration in #3.
This works in the US, but the problem is the integration relies on each CPAP having a unique serial number.
This is setup in the US version, but in the EU version the serial number is not plumbed through. This is because it does not show up on the dashboard which is the only information I had an example from when adding EU support, as I do not have an EU account and cannot create one.
To address this I need a HAR file for the MyAccount Profile

Login to myAir
Open the developer console.
Open the 'My Account' page.(https://myair.resmed.eu/MyAccount.aspx)
Export a HAR file
Send this HAR file to me or attach it here.
For step 4, here are some instructions for Chrome: https://support.google.com/admanager/answer/10358597?hl=en

Be careful to NOT enter your password when you have the network tab open. This may end up including your myAir password in the har file which we want to avoid. Login first and then open the developer console, open the page, and capture the HAR file.

Thanks for your quick reply. Hereby my har file as asked
myair.resmed.eu.har.zip
.

@HummelsTech I have pushed an update. Please try upgrading through HACS to 9139e29 and let me know if it works

Now I can add both CPAPs, but the readings for both are the same. The second sensor gives me the same values as the first.

For cpap_sleep_data_last_collected, this is a bug. This only works in NA right now, but the wrong sensor was excluded. the next update will fix this.
As for both devices reporting the same data, let me dig into this.

There is some information you can collect for me that will help.

Access the HA config directory using the terminal, samba plugin, or however you edit HA files
open the file .storage/core.entity_registry
Find one of the CPAP sensors, any one that is currently working will do, and paste the entry into this issue
Check to see if that  particular sensor show up more than once(which you can identify by the same Original Name), if it does, paste the entry for all the occurrences into this issue.

After install second account all values are correct, but after a restart of home assistant both sensors are unavailable.

Hope you have enough info to address the issue

Thanks for the information. I have found a subtle bug that might be causing this and have pushed a fix. Please update, test and let me know.
Thank you also for the icon suggestion.

Thanks again, but now I can't load the integration. Unknown error occurred

Uhoh! Can you send a screenshot of what you see regarding ResMed in the logs in Settings->Logs?

I've fixed an issue I found, please try updating again to latest.

@HummelsTech I'm going to close this issue, but please re-open if you still have issues.

Sorry again for the delay, but with last update the first bug came up again. when I config the second CPAP it gives me message: Device is already configured

hm, so for the EU the email address is used to determine if a device is already configured. I'm assuming these devices must have different email addresses for their associated accounts, right?
Here is something to try:

Turn up logging for this integration by adding these lines to your configuration.yaml, DO NOT add the default: info line though, as this will make all integrations print a lot more lines: https://github.com/prestomation/resmed_myair_sensors/blob/master/.devcontainer/configuration.yaml#L3-L6
Remove your current config for resmed
Reboot
Add the integration twice, once for each account
Send me all the log lines that mention resmed. we should see one line for each mentioning the serial number, which should contain your email address. Please sanitize the addresses, but confirm to me if they show up the same.

Can only add one CPAP when I try to add the second I get the message

I understand, but I need the associated log messages when this happens

I try to find those

Logger: homeassistant.components.sensor
Source: helpers/update_coordinator.py:161
Integration: Sensor (documentation, issues)
First occurred: 20:33:19 (1 occurrences)
Last logged: 20:33:19
Error while setting up resmed_myair platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/resmed_myair/coordinator.py", line 39, in _async_update_data
self.sleep_records = await self.myair_client.get_sleep_records()
File "/config/custom_components/resmed_myair/client/legacy_client.py", line 111, in get_sleep_records
page = await self.get_dashboard_html()
File "/config/custom_components/resmed_myair/client/legacy_client.py", line 106, in get_dashboard_html
async with self.client.get(EU_CONFIG["dashboard_url"]) as dashboard_res:
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 559, in _request
await resp.start(conn)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 898, in start
message, payload = await protocol.read()  # type: ignore[union-attr]
File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/resmed_myair/sensor.py", line 200, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 161, in async_config_entry_first_refresh
raise ex
homeassistant.exceptions.ConfigEntryNotReady: Server disconnected

Interesting! This looks like maybe your internet was having a hiccup, but this should have been retried and I don't think is the cause of our issues. were you able to turn on Info logging and find the lines about serial numbers?

Strange but true. Now it works I think my account had a hick-up thanks for all your help and understanding.

Yay! I'm going to close this but please open a new issue if you have issues or feature requests. thanks!


Run apollo-server-hapi versioned tests on Node 16

Feature Description
During triage of https://github.com/newrelic/newrelic-node-apollo-server-plugin/pull/75 it turned out there was a bug with Node.js v16.  In order to allow the PR to be merged, the tests for apollo-server-hapi were pinned to exclude v16: fix here.  When Node.js v16 becomes LTS, the tests on should be revisited to see if the fix has been made.
Additional context
The issue surfaced in Node.js with this PR https://github.com/nodejs/node/pull/33035.  The effect for apollo-server-hapi versioned tests are they just hang: See affected CI run.  This is because the readable stream(http request), prematurely is destroyed.  hapi has a listener for this, handle close, which basically just stops processing the request.  You can reproduce the issue with this apollo hapi app and make this curl request:
curl --location --request POST 'http://localhost:6000/graphql' \
--header 'Content-Type: application/json' \
--data-raw '{"query":"query GetRoids {\n  asteroids(date: \"2020-08-12\") {\n    id,\n    name,\n    miss_distance_km,\n    close_approach_date,\n    relative_velocity_km_per_hour,\n  }\n}","variables":{}}'

The code in Node.js has been reverted: revert PR, but was only made to v15.  There is still an open issue in Node.js for fixing this https://github.com/nodejs/node/issues/38657, which I assume will happen before v16 becomes LTS.
Priority
[Must Have]

apollo-server fixed this but the release hasn't been shipped yet. This PR adds Node 16 support for apollo-server-hapi https://github.com/apollographql/apollo-server/pull/5150.  We will have to lock down the versioned tests regardless to account for this.  It's worth noting we will be possibly dropping support for hapi < 20 for Node 16 for the agent https://github.com/newrelic/node-newrelic/issues/771 but this is a separate plugin and worth a discussion on how to support this plugin in node 16

While we have other issues with v3, it looked like this fix had been in v3 so we can potentially tackle this for v3+.

Likely requires this to be resolved first: https://github.com/newrelic/newrelic-node-apollo-server-plugin/issues/103


External Secrets Operator Onboarding

Onboarding external secrets operator
Summary

Test Plan

Checklist

[X]  No images hosted from dockerhub
[ ]  Are dashboards present to understand the health of the application.  There must be at least 1 of these

[ ]  all databases should have dashboards
[ ]  ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
[ ]  you can use plural from-grafana to convert a grafana dashboard found via google to our CRD

[ ]  Are scaling runbooks present

[ ]  all databases must have scaling runbooks
[ ]  you can use the charts in pluralsh/module-library to accelerate this

[ ]  do you need to add config overlays?

[ ]  inputing secrets
[ ]  configuring autoscaling

[ ]  If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
[ ]  All major clouds must be supported

[ ]  Azure
[X]  AWS
[ ]  GCP

Prerequisites:

Policy to access AWS Secret Manager (included in terraform main.tf)
Role to be assumed via IRSA, with trust relationship with EKS OIDC provider and permission based on the policy created above
output.tf should contain account_id and the service account name included in OIDC qualified subjects
k8 values.yaml.tpl should include ServiceAccount variable with the correct annotation including the account id and the role to be assumed (defined above)


WIP Added class constant indexing for #84

So I index all types used in the Constant Pool as Class Constants, and make a Map from the used type to the user of the type as a ClassInfo.
I thought about mapping to DotName but given that they can only belong to the index (since we indexed them), it's not clear that it's worth it.
I thought about mapping to a Set<ClassInfo> but that type doesn't implement hashCode/equals and so it was lying. In the end I've gone like most parts of the API (I did see a Set<ClassInfo> somewhere but it was alone) and used List even though there are no duplicates. At least the type doesn't lie about unicity, though it lies about ordering.
I've a question wrt Index.create() which is a static public method, so probably I'll need an overload for backwards compat, to accomodate for the new extra param, right?
As for the index format, I've bumped to V10, and tucked a Map<DotName,List<DotName>> right after the type list.
This should be all tested.
I'll add docs and remove the index size test once we agree on how to proceed with this PR.
Let me know what you think.

Damnit, it should have been a draft PR but I can't seem to be able to change this after the fact…

Ah, found it :)

Superseded  by #112


pull request for e2e test at 12/05/2016 04:15:04

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix: setting a higher upper limit of 1.17.0 for helm binary

fixes https://github.com/jenkins-x/jx/issues/6760

/test boot-vault-tls

/approve

/lgtm


Hope to add download control component

When downloading more than a few hundred chapters, the download will always pause itself and you must restart the app to continue downloading. However, after several restarts, the download task is cancelled by itself. Also, the download does not support continue downloading. When you click on the download again, it will start from the beginning, so you will never be able to download the whole novel.
I hope that the download control can be added or continue downloading can be supported.

You are right, this plugin need a download state management, and I just plan to  spend some time to improve this  plugin.


cannot persist cookies between different casperjs processes

i got a nodejs file that spawns casperjs as a worker to do certain tasks.. one is to login, once logged in I store the cookie in a file.
when i spawn the next casper worker.. i want it to to use the cookie rather having to login again.. both these methods failed:

when i spawn the worker capserjs I add the --cookies-file=./cookiefilename ie:

var child = spawn('casperjs',['monsterScrape2.js','--cookies-file=./'+cookieFileName]);

this also fails even if I run the above command on the command line..

within the casperjs worker file.. I make it read and set the cookie from a file ie:

var casper = require('casper').create();
var cookieFileName = 'monsterCookie.txt';

// grab cookies from file
var fs = require('fs');
var utils = require('utils');
var cookies = fs.read(cookieFileName);

casper.page.setCookies(cookies);

casper.start('https://domain/page.html', function() {
    //FAIL! cookies aren't used here
    this.debugHTML();
});

casper.run();

notes:

it was mentioned earlier in https://github.com/n1k0/casperjs/issues/39 that start removes cookies from the page? if so how do I prevent that?
I know that sessions persist within the same phantomjs page object (see here https://gist.github.com/abbood/5347252) and same happens within the same casperjs page object (see here https://gist.github.com/abbood/5347287)
keep in mind that I store cookies as is in the file (ie without any json/cookie parsing at all).. so my cookie file looks exactly like this

[General]
cookies="@Variant(\0\0\0\x7f\0\0\0\x16QList<QNetworkCookie>\0\0\0\0\x1\0\0\0\n\0
\0\0YCNTR=LB; expires=Tue, 09-Apr-2013 17:12:05 GMT; domain=.recruiter.domain.co
m; path=/\0\0\0qUID=13eb22f-<IP_ADDRESS>-1365523938; expires=Mon, 30-Mar-2015 16
:12:18 GMT; domain=.domain.com; path=/\0\0\0]UIDR=1365523938; expires=Mon, 30-Ma
r-2015 16:12:18 GMT; domain=.domain.com; path=/\0\0\0[R_LANG=en; expires=Thu, 09
-May-2013 16:16:06 GMT; domain=.recruiter.domain.com; path=/\0\0\0\x94\x43=4gpUm
UGr2jgDrs4xOJVrGaNbD8DtYSd1E6quyLhe3E4F3EAGhbRJucnDgRVDeHh0; expires=Thu, 09-May
-2013 16:16:06 GMT; domain=.recruiter.monstergulf.com; path=/\0\0\0\x94WT_FPC=id
=20cf093f17f2c6f3d041365495136954:lv=1365495369854:ss=1365495136954; expires=Fri
, 07-Apr-2023 08:16:09 GMT; domain=.domain.com; path=/\0\0\0\xc4\x41\x43OOKIE=C8
ctADE3OC4xMzUuMTQ3LjM5LTI4NzQ5NzQ0LjMwMjkxMjYxAAAAAAAAAAABAAAAmyoBAMo+ZFHhPWRRAQ
AAAAJWAADKPmRR4T1kUQAAAAA-; expires=Thu, 09-Apr-2015 16:16:10 GMT; domain=statse
.domain.com; path=/\0\0\0Yv1st=CE061E87215F2D73; expires=Wed, 19-Feb-2020 14:28:
00 GMT; domain=.domain.com; path=/\0\0\0\x84\x43OOKIE_ID=<IP_ADDRESS>-23687497
44.30291261; expires=Fri, 07-Apr-2023 16:16:11 GMT; domain=cookie.domain.com; pa
th=/DCS000065_7K5I\0\0\0\xbe\x41\x43OOKIE=C8ctADE3OC4xMzUuMTQ3LjM5LTIzNjg3NDk3ND
QuMzAyOTEyNjEAAAAAAAABAAAAQQAAAM0+ZFHNPmRRAQAAAAEAAADNPmRRzT5kUQAAAAA-; expires=
Fri, 07-Apr-2023 16:16:13 GMT; domain=cookie.domain.com; path=/)"

If you have a look at the sources you'll find that CasperJS does not interact with cookies at all. The only thing it does, is passing the command line parameter via native_args() to the underlying engine.
Please have a look if there is an issue with --cookies-file and the specific engine version you are using. Closing for now, because it seems unrelated to CasperJS code.


Update x11 sf::Cursor::Hand to be consistent across OS's

Description
It's my understanding that sf::Cursor::Hand is intended to be the mouse cursor indicating a clickable item. I am not able to test what it looks like on macOS, but on Windows sf::Cursor::Hand is indeed the clickable hand icon. On x11, however, there are two hand icons -- xc_hand1, and xc_hand2.
SFML is currently using xc_hand1, which is an open hand that is usually used in the context of dragging windows. This pr changes sf::Cursor::Hand to use xc_hand2 as that's the clickable indicator.
Please see the image below

It's possible that there are some themes out there which use xc_hand1 as the clickable indicator, but the default themes for every major distro I looked at (adwaita, ubuntu, fedora, breeze kde, linux mint, xubuntu) all use hand1(open hand) hand2(clickable).
How to test this PR?
#include <SFML/Graphics.hpp>

int main()
{

    sf::RenderWindow window(sf::VideoMode({600, 800}, 32), "Cursor Test");
    window.setFramerateLimit(144);

    sf::Cursor cursor;
    if (cursor.loadFromSystem(sf::Cursor::Hand))
        window.setMouseCursor(cursor);

    while (window.isOpen())
    {
        for (auto event = sf::Event{}; window.pollEvent(event);)
        {
            if (event.type == sf::Event::Closed)
            {
                window.close();
            }
        }

        window.clear();
        window.display();
    }
}

SFMLBuildMaster: Build this please.

Can confirm macOS uses the 2nd style cursor

I've also checked SDL2 and GLFW, and they both use hand2.
If accepted can we also merge this into 2.6 branch as well?

If accepted can we also merge this into 2.6 branch as well?

I don't see why not. In that case it'd be easier for this PR to target 2.6.x then it will automatically land in master after we do our next backmerge.

If accepted can we also merge this into 2.6 branch as well?

I don't see why not. In that case it'd be easier for this PR to target 2.6.x then it will automatically land in master after we do our next backmerge.

Is there a way I can change the target branch, or do I have to resubmit?

SFMLBuildMaster: Build this please.

Thanks for spotting and reporting this!


provide better documentation for marker nav cmd.

Description
Adds documentation for the marker NAV command.
closes: #2128

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Added relevant changelog entries under .changelog/unreleased (see Adding Changes).
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Summary by CodeRabbit

New Features

Updated CLI command for adding or updating marker net asset values, now requiring an additional argument for valuations.
Expanded command descriptions and examples to clarify usage and requirements for net asset valuations.

Documentation

Enhanced long description and examples for better user understanding of how to provide net asset valuations.

%%> ./build/provenanced tx marker add-net-asset-values --help

Adds net asset valuations for a marker.  Net asset values are expressed as a ratio
between an amount of coin paid (price) and a volume of token which are equivalent.
The denomination of the amount paid (price) must exist on chain as a separate marker
or be supplied as a [usd] integer which is valued in mils (0.001) USD.  The volume
is supplied as an integer count of the current token.

Usage:
  provenanced tx marker add-net-asset-values <denom> <valuation[;valutation...]> [flags]

Aliases:
  add-net-asset-values, add-navs, anavs

Examples:

  Set a value of 1USD = 1markercoin (Note USD is denominated in mils)
  $ provenanced tx marker add-net-asset-values markercoin 1000usd,1

  Provide more than one valuation in a single call
  $ provenanced tx marker add-net-asset-values markercoin 1000usd,1;5000000000nhash,1

  Note: When the valuations are recorded, each will indicate the address of the admin who provided the value.
  This will be published in the associated event data and captured in the NAV record.


General] Payment request is invalid: Error Domain=PKPassKitErrorDomain

Hi,
I use apple pay with the plugin flutter_stripe.
When I pay with Apple pay in the currency of my card (€). Apple pay is loading and works.
When I pay with Apple pay in another currency ($) Apple pay is raising an error in my debug log.
General] Payment request is invalid: Error Domain=PKPassKitErrorDomain Code=1 "Invalid in-app payment request" UserInfo={NSLocalizedDescription=Invalid in-app payment request, NSUnderlyingError=0x281bd8c00 {Error Domain=PKPassKitErrorDomain Code=1 "PKPaymentRequest must contain a property 'countryCode' of type 'NSString'
I think it's a bug in the plugin.
Can you please check?
Is it a known bug?
Is there a workaround?
Thanks,

If you look at the error in detail, it looks like you are missing the countryCode property. Have you set it in the payment configuration file appropriately? (see example].

Closing this issue since the cause was identified.
Feel free to reopen if the issue persists.


[turborepo] And turbopack problem with turbo.json and webpack HMR

What version of Turborepo are you using?
1.6.3
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Describe the Bug
When I have the file "turbo.json" in my monorepo, the Next13 app with turbopack use webpack hmr when Im trying to use "turbopack hmr",  that make a collision and got this error:

Expected Behavior
Without turbo.json file:

With turbo.json file:

To Reproduce
Create a monorepo with turborepo, create a nextjs13 app in "app" folder:

change "next dev" to "next dev --turbo" in package.json of the app, run dev.

Reproduction Repo
No response

This issue is rather old so I'm going to figure that this has been cleared up since then.


https://godoc.org/github.com/go-playground/validator/v10 is 404d

Package version eg. v8, v9:
v9/v10
Issue, Question or Enhancement:
The godoc for both v9 and v10 is 404d. :'(
Code sample, to showcase or reproduce:

I'm not sure where these links came from @kaelanfouwels but the lonks in the v9 & v10 readme's work as expected:
v10 - https://godoc.org/github.com/go-playground/validator
v9 - https://godoc.org/gopkg.in/go-playground/validator.v9

Ah, the readme currently lists the url with an extension of /v10 on the github.com url.

perfect thanks @kaelanfouwels, merged and will release with some other things today :)


Issue #37: Deleting the signals_code folder after generator finishes

@rmutter @baylee
Not sure if I should mock the os methods, but since the signals_code directory is actually created, I thought it made more sense to actually check for the existences of the directory rather than to mock the methods and check that they were called.

@walkingtowork some quick organization notes

@rmutter Changes made.


README

The readme should include installation instructions (fine to start off with TBD), along with usage examples

Closed by #3


Release v0.28.0

v0.28.0 Jul. 2, 2021
Enhancements

Added support for showing a Individual Conditional Expectations plot when graphing Partial Dependence #2386
Exposed thread_count for Catboost estimators as n_jobs parameter #2410
Updated Objectives API to allow for sample weighting #2433

Fixes

Deleted unreachable line from IterativeAlgorithm #2464

Changes

Pinned Woodwork version between 0.4.1 and 0.4.2 #2460
Updated psutils minimum version in requirements #2438
Updated log_error_callback to not include filepath in logged message #2429

Documentation Changes

Sped up docs #2430
Removed mentions of DataTable and DataColumn from the docs #2445

Testing Changes

Added slack integration for nightlies tests #2436
Changed build_conda_pkg CI job to run only when dependencies are updates #2446
Updated workflows to store pytest runtimes as test artifacts #2448
Added AutoMLTestEnv test fixture for making it easy to mock automl tests #2406

Perf tests will complete around the EOD I think, will post in channel


httpError sufficient permission error despite api pulling data from my service account.

SYSTEM:  Command google_analytics returned: Error: <HttpError 403 when requesting https://analyticsreporting.googleapis.com/v4/reports:batchGet?alt=json returned "User does not have sufficient permissions for this profile.". Details: "User does not have sufficient permissions for this profile.">
I have added my google service account json and renamed it to Firebase.json , and also added permission to GA, however I amm still getting this error. the API is reporting pull requests however with 100% error. Is there something wrong  with my installation ?

Auto-GPT-Google-Analytics: 0.1.0 - This is a plugin for Auto-GPT-Google-Analytics.
Welcome back!  Would you like me to return to being AnalyticsGPT?
Continue with the last settings?
Name:  AnalyticsGPT
Role:  Web Analytics Expert
Goals: ['Get pageviews for the past 30 days', 'Terminate']
API Budget: infinite
Continue (y/n): y
AnalyticsGPT  has been created with the following details:
Name:  AnalyticsGPT
Role:  Web Analytics Expert
Goals:

Get pageviews for the past 30 days
Terminate
Using memory of type:  LocalCache
Using Browser:  chrome
THOUGHTS:  I think the first step is to get the pageviews for the past 30 days. I can use Google Analytics for this. I should also save the date in the past 30 days that I want to get the pageviews for, so I can use it later if needed.
REASONING:  Getting the pageviews for the past 30 days will give me an idea of the website's recent performance. This information can be useful in making decisions about future strategies.
PLAN:
Use the 'google_analytics' command to get the pageviews for the past 30 days.
Use the 'get_date_in_past' command to get the date 30 days ago and save it to a file.
CRITICISM:  I need to make sure I am using the correct metric for pageviews and that I am saving the date in the correct
format.
NEXT ACTION:  COMMAND = google_analytics ARGUMENTS = {'metric': 'pageviews', 'date_in_past': '30daysAgo', 'date_in_future': ''}
Enter 'y' to authorise command, 'y -N' to run N continuous commands, 's' to run self-feedback commands'n' to exit program, or enter feedback for ...
Input:y
-=-=-=-=-=-=-= COMMAND AUTHORISED BY USER -=-=-=-=-=-=-=
SYSTEM:  Command google_analytics returned: Error: <HttpError 403 when requesting https://analyticsreporting.googleapis.com/v4/reports:batchGet?alt=json returned "User does not have sufficient permissions for this profile.". Details: "User does not have sufficient permissions for this profile.">
THOUGHTS:  It seems that I do not have sufficient permissions to access Google Analytics. I will need to find another way to get the pageviews for the past 30 days.
REASONING:  Without access to Google Analytics, I will need to find another way to get the pageviews for the past 30 days. I can try using the 'get_hyperlinks' command to get the pageviews from the website's sitemap.
PLAN:
Use the 'get_hyperlinks' command to get the pageviews from the website's sitemap.
CRITICISM:  I need to make sure that the sitemap contains the pageviews information and that I am parsing the information correctly.


Storage parameters.json does not exist (issue from the backend build)

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.15.1
Amplify CLI Version
v9.2.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual update
Amplify Categories
storage
Amplify Commands
add
Describe the bug
In my amplify project i run
Amplify add storage

Once the storage in added localy i push my backend using Amplify push
One the backend is pushed i build/deploy my application from Amplify but i get this issue during the build backend :

Expected behavior
Want tobuild / deploy my application including storage resource created from amplify cli
Reproduction steps
amplify add storage
amplify push
build app
GraphQL schema(s)

# Put schemas below this line

Project Identifier
Project Identifier: e729fe38a8479db15c640454220f0835
Log output

# Put your logs below this line

Additional information
The Storage folder and the parameters.json file are in the amplify folder in my local :

Hey @julienlaurent-migso :wave: thanks for raising this! From the path in the stack trace, it appears the CLI is looking for parameters.json in the storage category's directory rather than the build/ directory nested within. Can you confirm the CLI version used in Amplify Hosting matches the version used locally? I'm curious if the CLI version is pinned to an older version of the CLI that is not recognizing cli-inputs.json (instead of parameters.json, this changed a few major versions back)

Hi  @josefaidt, Thank you for your answer.
Concerning the Amplify Hosting version :

And locally:

How can i fix this issue ? Do i need to move the parameters.json to the storage folder (same position than cli-inputs.json)  inside S3 ? I tried to move it from my local and amplify push it again but it's not working.

Hi @josefaidt,
I don't know why but i have launched again a build from another computer with the last Amplify/cli and now it's working..

Hi @julienlaurent-migso, I'm having the same issue on 9.2.1 and was wondering what version you used to get the build working?  (In other words...what was the "last" amplify/cli version that worked for you)
Thanks!

hi @bentonmize, the last version for me is related to 9.2.1
I can't explained how i have fixed this issue .. try to push again your backend (updating something).
On my side i remember that i have worked from another computer / pulled my amplify backend / updated the graphql schema / pushed the new version of the backend and my amplify app was able to build again ..

Hey @julienlaurent-migso apologies for the delay,

I don't know why but i have launched an amplify push from another computer with the last Amplify/cli version and now the build is working..

Interesting! It appears an older version of the CLI was being used when the error originally occurred, however can you confirm whether your successful mitigation was from running amplify push manually or git push with the automated workflow?

Hi @josefaidt,
Yes i confirm it, see below my steps:

amplify upgrade (global)
clone gitlab folder
npm install
amplify pull
update graphql schema
amplify push
gitlab commit
Amplify build automatically with the CI/CD activated
Result: everything is working well

Hey @julienlaurent-migso does the Amplify build with Amplify Hosting's CI/CD also build the backend (typically with amplifyPush --simple)? If so it appears the manual amplify push may have resolved something

Hey @josefaidt, yes i am using this command

Hey @julienlaurent-migso apologies for the delay but I am glad to hear that you were able to resolve this with a manual amplify push execution. I'm tracking this issue along with a few others for CLI+Hosting-related issues and inconsistencies. Continuing to work on a reproduction to confirm whether the CLI is impacting the workflow here

Hey @julienlaurent-migso I've added the ops-deploy label to help us track issues related to deployment safety, and given the issue is no longer being experienced and was not reproducible I will close this for the time being.

I am experiencing the same issue. Attempted mitigation steps above which didn't resolve the issue.
I had working version deployed via CI/CD. Completed the following steps and can no longer build:

Updated to latest CLI ("amplify upgrade")
Removed previous auth ("amplify auth remove")
Added new auth in order to change configs to use SSO ("amplify auth add")
Tested locally successfully
amplify push
git push
CI/CD triggered with build fail
2022-11-14T06:16:50.802Z [WARNING]: ✖ There was an error initializing your environment. 2022-11-14T06:16:50.816Z [INFO]: 🛑 Failed to pull the backend. 2022-11-14T06:16:50.816Z [INFO]: File at path: '/codebuild/output/src159328036/src/xxxxxxxx-xxxxxxxxxxxx/amplify/backend/auth/xxxxxxxxxxxxxxxxxxxxcf7697d7/parameters.json' does not exist

Add'l info:
amplify CLI version: 10.4.1
Local node version: v18.6.0
Amplify node version: v16.18.1

I'm facing the same issue.  These kinds of unresolvable failures are making Amplify completely unusable.  I may have to move to another platform. :-(

Update: This was resolved by adding the file "cli-inputs.json" into the commit.  The error message indicated it was missing "parameters.json", so it was not clear that the real missing file was "cli-inputs.json".  I think the error message needs to be improved.
But for anyone facing this issue, check to see if you need to commit a file named "cli-inputs.json".


Bencode Subcommands

Add bencode subcommands for interacting with bencoded data:

imdl bencode validate --input PATH validate bencode file(s) at PATH, showing any validation errors encountered
imdl bencode convert --format yaml PATH convert bencoded files at path to given format.

This seems less valuable now that torrent validation and display are covered by other subcommands.


git clone https://github.com/cevap/ion ask for username and password

When I do a git clone https://github.com/cevap/ion in Ubuntu 16.04 I get this:
Cloning into 'ion'...
Username for 'https://github.com':
Password for 'https://github.com':
Never happend before. Has something changed ?

Works again, dont know what happened :)


Add PICS DRLK.S.F08 to DRLK yaml tests

Add missing PICS DRLK.S.F08 checks to DRLK yaml tests

How to proceed with this?

How to proceed with this?

Prod people on Slack to review this?

@chrkroh this requires some merge fixes (likely just running zap regen after merging with master)


Empty request body documented

See:
http://apidocs.cloudfoundry.org/225/space_quota_definitions/updating_a_space_quota_definition.html
If the request/response body is empty it shouldn't be shown in the documentation.

It now shows name being changed.
http://apidocs.cloudfoundry.org/release-candidate/space_quota_definitions/updating_a_space_quota_definition.html


cmake: Prevent it from looking for packages in / when cross-compiling for Windows.

This pull request is for the staging branch because it will cause a mass rebuild.
I was using the CMake from nixpkgs in my own project (outside of nixpkgs) to cross-compile some software for Windows.  That software uses the find_package command to find Qt5Widgets.  CMake was finding the Qt5Widgets package on my build system and trying (unsuccessfully) to use it.  Obviously, that goes against the whole point of purity in Nix.  This pull request adds a patch that comments out a line that adds / to the CMAKE_SYSTEM_PREFIX_PATH.  Thanks!
Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Thanks!


rotoraero vartrees

add necessary vartrees for picking up outputs from rotoraero simulations
@andrewning

added basic vartrees in rotoraero_vt.py, sufficient for our current uses.


Fix CustomObject bug destroy & Ragdoll Size & new effect & Decay AHP

GetVoltage() - Remove this it looks to me like HeavyController.ActiveGenerators * 1000 and more complicated
ragdoll.netIdentity.UpdatePositionRotationScale() - This basically sends a new Spawn message and since you spawn it literally the next line of Code you don't need it, also fix the formatting
public static Synapse.Api.Ragdoll GetRagdoll(this Ragdoll rag) => Map.Get.Ragdolls.FirstOrDefault(x => x.ragdoll == null && x.ragdoll == rag); I think this should be ragdoll != null
public static Door GetDoor(this Interactables.Interobjects.DoorUtils.DoorVariant door)
{
	return Map.Get.Doors.FirstOrDefault(x => x.VDoor != null && x.GameObject == door.gameObject);
}```
 It's not wrong but the formatting is weird compared to all others

Is there a reason why you added so many null checks for synapse object lists?

I created a plugin to edit maps and place schematics, but that only happened when I deleted schematics, doors, generators, etc. They happen that they are not removed from the list which causes null values and therefore errors


Implemented ServiceLoader in Entrypoint

Description

Motivation and Context

[ ] I have raised an issue to propose this change (required)

Which issue(s) this PR fixes

Fixes #
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Version change (see: Impact to existing users)

Impact to existing users

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I've read the CONTRIBUTION guide
[ ] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thanks for contributing this @kameshchauhan .
I'll pester @alexellis so we get this merged :grin:  .
I've also worked on https://github.com/openfaas/templates-sdk/pull/3   .
It's done (need to test publish and sign).
Could you do a review please?

Thank you for your contributions. I think we already have this covered though. Can you take a look at yesterday's commits?

The PR adds tests for service loader.
It does not change the code that exists.

We already have the ServiceLoader see: https://github.com/openfaas/templates-sdk/tree/master/java11/entrypoint/src/main/java/com/openfaas/entrypoint and https://github.com/openfaas/templates-sdk/tree/master/java11/entrypoint/src/main/resources/META-INF/services

Given that this PR is trying to do something we have now, we should probably close it, unless there's something else we want from it in a new PR?

@alexellis , Please see the diff. The PR adds a test for the service loader functionality.
It does not change the code.
I've mentioned this in my previous commend.

This can't be merged until the commits are cleaned up, currently there are around 15 which are rather messy but also include unnecessary merge commits. Starting a new branch may be easiest, or running git reset or git rebase. Plenty of info online for how to do this.
The title of the PR would also need to be updated as per the commit i.e. "add a test for the service loader".


Release v1.0.0

LGTM

There is an integration test failure

@baude Try making this 5sec in another commit https://github.com/containers/aardvark-dns/blob/main/test/helpers.bash#L481

/lgtm


Finish connection between iOS App and Smart Speaker

Fixes #410
Changes: Update device activity after the successful connection between SUSI iOS App and SUSI Smart Speaker and show the success message.
Screenshots for the change:
N/A

@chashmeetsingh @mariobehling Please review and merge!


How to associate base_url between admin panel and site for two environments?

The situation:

There are 2 sites - Admin Panel and Store Site.
There are 2 environments - stage and prod.
I need to check the correct sorting of products on Store Site.
No direct access to the DB (to obtain sourсe sorting data for comparison). Therefore, the original data can be obtained only from Admin Panel page.

My scenario:
Given I am on "http://stage.admin.lcl/products/sorting"
And I remember the products sorting
When I am on "http://stage.store.lcl/home"
Then I compare the products sorting with Admin Panel

In my case, the dough is very related the Admin Panel and Store Site.. But I have no other way to get the source data for the test.
At the same time, it is necessary to test the scenario in different environments - stage and prod.
How do I specify the base_url for each site and each environmets, that would use the relative URLs in the scenarios?
Thanks.

What @gggeek said


Use get_proof in account data fetching to reduce number of RPC calls

Reduces the number of RPC calls for accounts from 3 to 2 (or even 1 if code fetching can be skipped when we know the code hash is empty).
I left the old code in for now because I see it working faster, but who knows how it might behave in different scenario's.

We have discussed using batch json RPC as json RPC support that feature, like
[
  {"jsonrpc": "2.0", "method": "subtract",
    "params": {"subtrahend": 23, "minuend": 42}, "id": 1},
  {"jsonrpc": "2.0", "method": "xyz"},
  {"jsonrpc": "2.0", "method": "dummy", "id": 2},
]

However, here for get account, get_proof does exactly the same thing I think.
could be a option if in future multi-get_proof becomes the bottle neck.

If get_proof would contain the code as well I think it would be the best it could be, but unfortunately still a separate call necessary now for that when there is code.
A batched (or I guess even a parallelized one on the client side to open multiple requests) get_proof would indeed help a lot for fetching the actual merkle proofs.

A batched (or I guess even a parallelized one on the client side to open multiple requests) get_proof would indeed help a lot for fetching the actual merkle proofs.

Batch maybe easier to impl as no async issue? we can do it now and also control it with a feature flag. I can not remember why we did not impl it before A7, maybe because unstable is unstable and no perf pressure (due to plenty of op blocks).

Oh I thought this required custom node support but it is actually supported by the standard json rpc API! Okay yeah we should support this! Will do this tomorrow if nobody else works on it in the meantime.

Oh I thought this required custom node support but it is actually supported by the standard json rpc API! Okay yeah we should support this! Will do this tomorrow if nobody else works on it in the meantime.

"@Noboby Else" is already working on that for a while, let's fire him as you can complete it in a pretty short time :)


Add srish-03's fileupdate gems

I HAVE A CREATED A FILE , CREATED A PULL REQUEST, A BRANCH ,COMMIT

created a branch, created a file and made a commit, and opened a pull
request


Enable Ark to store backups/etc. under a prefix within an object storage bucket

Fixes #167
I'd still like to add some more unit tests within pkg/persistence, but other than that this should be ready for a solid review.
NOTE: this PR includes a small change to the ObjectStore plugin interface (adding a prefix parameter to the ListCommonPrefixes method).

I started on some unit test updates, but before I go further I would like to get folks' input on the last commit I pushed - which demonstrates a test pattern I'd potentially like to use here, and in some other spots across the code base.
The change is to use a test fake instead of a mock for pkg/cloudprovider/ObjectStore, which is a dependency of the type we're testing (pkg/persistence/objectBackupStore).  The test fake is hand-implemented in pkg/cloudprovider/in_memory_object_store.go.  The implementation should be semantically ~equivalent to a real cloud-provider implementation of cloudprovider.ObjectStore, but it stores all of its data in-proc in a standard golang map.  It also exports all of its internals and provides some helper methods, which make using it within the context of a unit test easier.
I think mocks have their place, and I'm not proposing eliminating them from our toolkit.  But I do think that, in a lot of cases, using a well-crafted fake can reduce the complexity and cognitive overhead associated with tests.  Rather than having to set up mock expectations every time we want to use one, the expectations about how an interface implementation should work are embedded in the test fake implementation itself.
Would like everyone's input on this before deciding whether to proceed further in this direction.
cc @nrb @carlisia @ncdc @wwitzel3

I think this is a great approach. I've used this same approach for storage backends. An in-memory fake that satisfies the interface made writing unit tests much less painful.

alright, I went ahead and updated the rest of the tests using the fake, and added scenarios for prefixes, so you can now see what it looks like across the board.  Still open to feedback.

Will squash before merge!

@carlisia @nrb gentle reminder that this PR is ready for a full review.

Ready for squashing!

annnnd now all of a sudden a test is failing. looking into...

had a flaky test due to comparing things that could be ordered differently. should be fixed now.

Still looks good. Squish away.

it's as squashed as I'd like it to be


[FEATURE] ability to set the axis label's width

Feature request.
When having multiple line charts stacked on top of each other, they can't line up if you have varying digits on the Y Axis.
It would be useful if you could set the width of the labels on the Y Axis.

Duplicate of #4340

The workaround doesn't seem to work with v3. Is it possible that afterFit callback has been removed?
This prints the instance of the scale with v2.93 but nothing with v3.
  scales: {
    yAxes: [{
      afterFit: instance => console.log(instance)
    }]
  }

@dbauszus-glx did you find a working solution for v3?

@lessless I have not. Any help is welcome.

@dbauszus-glx this is kind of hacky, but I was able to fix the left axis width by setting the maximum axis width to zero and the left padding for the chart layout to 100:
scales: {
    yAxes: [{
        afterSetDimensions: function(axes) {
            axes.maxWidth = 0;
            console.log(axes.width);
        }
    }]
}

layout: {
    padding: {
        left: 100
    }
}


Allow Pull Requests to create a unique Preview Environment

Many hosting platforms including firebase and heroku have "review apps" or unique deployments when a Pull Request is created. It would be amazing if you could have a way to create a temporary deployment for a pull request.

@jmarbutt Thank you! preview environments are in our roadmap. We are now rebuilding our infrastructure so this will have to wait until that is finished.

Yeah I figured that is probably pretty complicated to implement but something I have really enjoyed in Firebase and Heroku.

Hi guys,
Talking about the preview environment and how it could be difficult to pass an environment variable to Vercel or Netlify, I was looking into an article about building an HTTPS-intercepting javascript proxy and though this could be something worth exploring.
Now, my backed knowledge is very limited so what I might be suggesting doesn't make sense at all :)
So what if, instead of passing an environment variable to Vercel or Netlify, instead you have an HTTPS-intercepting proxy on Nhost that whenever you create a PR it would intercept the traffic and route it to the preview environment. I know that whenever we create a PR Vercel generates a URL for this PR, maybe somehow grab this URL and redirect traffic to the preview environment from this URL.
By doing so, you wouldn't need to worry about the different front-end hosting providers.
Does any of it makes any sense?

@alveshelio thank you for your suggestion. We will consider it when building the feature. I didn't know about HTTPS-intercepting proxy until now.

For anyone looking at this issue, one way to circumvent it ( until we have preview environments) is by creating a new application, connecting it to the same GitHub repository and editing the branch to the one from the PR.


bpf: fix incorrect inline asm output operands sections

In some places, certainly because of copy-paste we use the inputs operands instead of the output operands section.
I also spotted some incorrect constraints, r+ instead of +r for example.

mmh they are more I missed many, I only searched for rg "asm volatile.*::" so far.

Good work

Thanks, I pushed a few other fixes. I'll try to get John's review on this one.


Feature Request: Allow ruff to read from config

Hi,
ruff can read from config files in the repo:
https://github.com/erickgnavar/flymake-ruff/blob/master/flymake-ruff.el#L38
WDYT

Happy to accept a PR for this, but I'm really not a big fan of linters that expect you to figure out the project type and pass through this sort of parent configuration file they may need. Really ruff should just take the path to the file you're wanting to format as an extra option it can figure if there's any configs or something else in the project that it may want to use for formatting.

Ruff also has this command line flag: --config
https://docs.astral.sh/ruff/configuration/#command-line-interface


[WIP] profiling builds

Working on a proof of concept: add specific flags to the release builds to include more debug info for better callstacks when profiling. An attempt to implement https://github.com/mapbox/cpp/blob/master/glossary.md#profiling-build. The question will be whether the binaries are too large (> 1.5 the size). We'll see. If not, then this should overwhelmingly help for profiling and the rare instance of crash debugging.

Codecov Report

Merging #753 into master will increase coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #753      +/-   ##
==========================================
+ Coverage   96.23%   96.37%   +0.14%
==========================================
  Files          42       42
  Lines        8810     9141     +331
==========================================
+ Hits         8478     8810     +332
+ Misses        332      331       -1

Impacted Files
Coverage Δ

src/mapnik_map.cpp
100% <0%> (+0.07%)
: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 12ac477...3217328. Read the comment docs.

Closing this, handled by #804


Error trying to patch the KAO image for 4.14.0.-rc4

Recently we try to patch the images for new pre-release version 4.14.0 and it ends up failing due to a merge conflict on the Dockerfile:
...
Cloning into 'crc-cluster-kube-apiserver-operator'...
+ pushd crc-cluster-kube-apiserver-operator
/var/lib/jenkins/workspace/eng-crc-brew-image/crc-cluster-kube-apiserver-operator /var/lib/jenkins/workspace/eng-crc-brew-image
+ git remote add upstream https://pkgs.devel.redhat.com/git/containers/ose-cluster-kube-apiserver-operator
+ git fetch upstream rhaos-4.14-rhel-8 --no-tags
From https://pkgs.devel.redhat.com/git/containers/ose-cluster-kube-apiserver-operator
 * branch              rhaos-4.14-rhel-8 -> FETCH_HEAD
 * [new branch]        rhaos-4.14-rhel-8 -> upstream/rhaos-4.14-rhel-8
+ git checkout --track origin/rhaos-4.14-rhel-8
Switched to a new branch 'rhaos-4.14-rhel-8'
branch 'rhaos-4.14-rhel-8' set up to track 'origin/rhaos-4.14-rhel-8'.
+ git merge --no-ff -m 'Merge commit 00e953ab5c1424c17885b388237657f393afe6b5 into rhaos-4.14-rhel-8' -m 'MaxFileSize: 104857600' 00e953ab5c1424c17885b388237657f393afe6b5
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
Automatic merge failed; fix conflicts and then commit the result.

I've done the merge manually and pushed the changes, this should work fine now.


feat: add polar polygon support

Adds support for polar polygons by splitting them by the meridian plane for display/query in 2D. Additionally, queries for OGC servers such as GeoServer are now split over the antimeridian in the event that the remote server does not allow coordinates outside of the longitudes [-180, 180].
resolves #540, #579
Test:

Draw polygons that contain or pass near the poles (tip: create a pole place by manually entering the coordinates) in 3D (try both EPSG:4326 and EPSG:3857) and verify that they display properly in 2D
Import some similar polygons and verify that the behavior is the same
Draw a polygon (not a box/rectangle) over the antimeridian with a GeoServer WFS layer on. Verify that it splits the polygon over the antimeridian and does not return an error about longitudes outside of [-180, 180].

Ah, that test failure reminds me: JSTS, when splitting/polygonizing, does not linearly interpolate the altitude between the two points. Do we want to do that?

This algorithm does not work well for large polygons due to the stereographic projections. I'm considering adapting Cesium's approach of splitting the polygon by the meridian plane in 3D Cartesian space.


incorrect html_root_url

Currently, the crate’s doc(html_root_url) is set as https://doc.rust-lang.org/libc/<target>, for example https://doc.rust-lang.org/libc/x86_64-unknown-linux-gnu, but that will redirect to https://docs.rs/libc/<target>, for example https://docs.rs/libc/x86_64-unknown-linux-gnu which simply states that the requested resource/crate does not exist.

Ah oops! The domain here is intended to be rust-lang.github.io, which should fix the issue!


Number of Compiler Errors

Hi Ivan,
I'm trying to import the framework into a project (via pods) but am having a few issues I thought you might be able to shed some light on.
First of all, I'm getting 6 compiler errors from the pods and an additional error "No Such Module" when I attempt to import the framework (images attached).
The steps I've followed are merely setup and installed the podfile with the Swift 2.0 branch, opened the workspace in xCode 6.3.1, inputted the import statement and built the project.
Thanks for your help!
P.S. in reference to my previous question involving getting the touch point to move between two different points on the y-axis, I managed to develop a method, although I am sure it could be done more elegantly - happy to upload if you are interested.

Hi,
you need XCode 7 (beta 4) to use the Swift2.0 branch. XCode 6 only supports Swift 1.2.
As I mentioned in your previous question, the intersection issue should be fixed now and it was also merged in the swift2.0 branch.

Appreciated. Thanks.


more precise lane connector overlays.

Problem:
if lanes have sharp curves the bezier will not fit the road

Solution:
We need to cut beziers rather than merely moving its start point.

quick fix. cool


Multiple namespaces

In the readme :
You'll have two primary environments - staging and production - and use Kubernetes namespaces to isolate them.
But no reference of staging namespace (only production).
I see the labels used are differents, but shouldn't the readme be worded differently then ?

Hey @skylve! Great point. That is vestigial from a previous iteration of the tutorial that did not deploy as a canary. Thanks for pointing it out.
How did the rest of the tutorial treat you?

Fixed now.


DOC: add v0.3.0 release notes

Also add some utility scripts (stolen from Scipy) to easily update the release notes.

With this PR and the one for fixing version numbering I think we're about ready to tag the release.

LGTM

Pushed a couple more commits to address the move to the new org, version numbering in the docs, etc.

@grlee77 if you want to check that the last commits look good, then I think we can merge this and tag v0.3.0

@grlee77 if you want to check that the last commits look good, then I think we can merge this and tag v0.3.0

not sure if it was intentional, but there is still one reference to http://www.pybytes.com/pywavelets/ in index.rst.
Otherwise this looks good to me.

Thanks, good catch. Forgotten to sync README.rst and index.rst. Those probably shouldn't be exact copies of each other (different purposes), but that's for another time. Fixed in amended last commit.
PEP 400 version fix is needed for Appveyor PR - pip refuses to install something called 0.3.0.dev- now.


timezonemap: init at 0.4.5

Motivation for this change
Needed for cinnamon
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

merge?

thanks @mkg20001


Scale the vote investment slider logarithmically

This is a Feature Proposal
:tophat: Description
Putting the slider on a logarithmic scale means that we'd have more room to be precise to select a few votes, at the cost of less room to be precise when we put them almost all in.
For example, we could calibrate the scale to have the following behavior : up to 33% of the sliding bar we'd choose between 0 and 10, from 33% to 66% between 10 and 100, and between 100 and 1000 for the last third.
A function for the above example would be :
let n be the current total of votes
let p be the position of the handle

Amusingly, the 1000 in this formula is not directly related to the actual total of votes.
To be complete, and to show the correct length for already invested votes, we'd need the inverse function, mapping the quantity of votes to the fraction of the width of the bar :

One should note that these formulas do not exactly reflect the conditions stated above because of the  zero f(0)=0 condition that makes the linear regression impossible, but they match closely enough :
f(0) = 0
f(33%) = 9
f(66%) = 99
f(1) = 1000

Another feature would be to show the current amount of selected votes right above the sliding handle, (and moving with it) in HUGE yellow numbers, so that they would show up right above your finger on mobile.
Ticks on the bar at 10 votes and 100 votes would probably help too.

Finally, the slider should not even show up until the user has selected one of the ballot options.
We observed two separate new users being confused about it, trying the slider before ticking a ballot option, being denied, and assuming that's a bug, 'cause that's what users do. A little bit of brainstorm with them resulted in the ideas exposed above.

This all does not preclude having a way to fine-tune the amount of votes in the modal afterwards (see #153), but it would make the slider less shaky because it would not have to care for the sliding speed, nor repositionment, nor exceptions at the extrema.
:pushpin: Related issues

#164
#153
#44

We will definitely implement a logarithmic scale on the slider. I agree with this. Did a basic implementation some time ago, but left it out due to other priorities. Thanks for bringing up the math.

It was our pleasure ; we actually had a lot of fun pinning the formulas down ! As a side note, maybe the slider should behave linearly for small totals of votes (instead of 1000 as it is now).


on handler causes process hang. Request does not time out.

Steps to reproduce
Tell us about your environment:

Puppeteer version: 5.5.0
Platform / OS version: Ubuntu <IP_ADDRESS> LTS
URLs (if applicable): https://53.com, https://securian.com

Both of these sites react similarly to the curl user agent.

Node.js version: 14.13.1

What steps will reproduce the problem?
Run the following code:
const puppeteer = require('puppeteer');

(async () => {
  let scripts = []
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  page.setUserAgent("curl/7.37.0");
  page.on("response", async function (response) {
    return new Promise((resolve, reject) => {
        if (response.url().match(/.+?\.js(?:\?.+)?/)) {
            scripts.push(response.url());
        }
        resolve();
    })
  });
  let response = await page.goto('https://53.com', {timeout: 15000});
  let content = page.content();
  await page.screenshot({path: 'example.png'});

  await browser.close();
})();

If the on handler is removed, the process does not hang.
What is the expected result?
The code properly loads the page or the request times out reasonably within the 15 seconds specified.
What happens instead?
The process hangs and must be stopped manually. Even when hitting ctrl+c, the process takes around a minute to time out.
Screenshot showing it takes 51 seconds to time out + warnings:

Discovered it was an issue with puppeteer treating "data:..." as "responses" and my regex was choking on it.


Upload: fix against non-primitive key warn in Vue 2.4

Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

#5868


[goctl api] Got a error when i use goctl api java

Describe the bug
Got a error when i use goctl api java
To Reproduce

The code is
goctl api java --api=./xx.api --dir=java

The error is
2023/02/15 17:56:50 Type UserProfile generate error, unsupported primitive type []string

Expected behavior
what you expected: generate the java api class files succeed
Screenshots

Environments (please complete the following information):

OS: windows
go-zero version v1.4.1
goctl version v1.4.4

More description

Please post the content of the key api file, thank you


istioctl x precheck yields Error

Bug description
The downloadIstio script was used to pull the 1.10-alpha.0 release. At the end of the script it says to:
Begin the Istio pre-installation check by running:
	 istioctl x precheck

which for me yields the error:
Error: Get "http://localhost:8080/version?timeout=32s": dial tcp [::1]:8080: connect: connection refused

[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
I should not receive an error when running the specified pre-installation check
Steps to reproduce the bug

curl -L https://istio.io/downloadIstio | ISTIO_VERSION=1.10.0-alpha.0 sh -
istio-1.10.0-alpha.0/bin/istioctl x precheck

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
1.10.0-alpha.0
How was Istio installed?
At this point, it isn't.
Environment where the bug was observed (cloud vendor, OS, etc)
MacOS
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

that means its not detecting kubeconfig correctly. Does istioctl version, kubectl version, and/or istioctl install work?

At the point I was running the commands, my cluster may have been still creating, so I suspect kubeconfig wasn't set yet. Should we have a better message in that case?
Going to a non specified kubeconfig, I see from kubectl a similar message, but agree it doesn't point at an incomplete kubeconfig:
> kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:16:14Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
The connection to the server localhost:8080 was refused - did you specify the right host or port?

also
>./bin/istioctl version
unable to retrieve Pods: Get "http://localhost:8080/api/v1/namespaces/istio-system/pods?fieldSelector=status.phase%3DRunning&labelSelector=app%3Distiod": dial tcp [::1]:8080: connect: connection refused
1.10.0-alpha.0

so similar message to recheck.
I'm fine closing this as user error.

Tried the same on the 1.8.4 client:
Checking the cluster to make sure it is ready for Istio installation...

#1. Kubernetes-api
-----------------------
Can initialize the Kubernetes client.
Failed to query the Kubernetes API Server: Get "http://localhost:8080/version?timeout=32s": dial tcp [::1]:8080: connect: connection refused.
Istio install NOT verified because the cluster is unreachable.
Error: 1 error occurred:
	* failed to query the Kubernetes API Server: Get "http://localhost:8080/version?timeout=32s": dial tcp [::1]:8080: connect: connection refused
	* ``

I've tested istioctl 1.10.0. Without kubeconfig correctly, it reports:
$ ./istioctl x precheck
Error: Get "http://localhost:8080/version?timeout=32s": dial tcp <IP_ADDRESS>:8080: connect: connection refused


Use 'motoko' NPM package for syntax highlighting

Defers to the node-motoko NPM package for Monaco editor configuration.
This fixes the ignore keyword, which was previously missing from the MP syntax highlighting.
Verified that the optimized build size is almost exactly the same (5.2 MB) before and after adding the motoko dependency.
Resolves #133.

Merged everything from #129 into the NPM package (dfinity/node-motoko#8).


[Python] Could we get a way to convert DMatrix back to ndarray or scipy csr?

I've often found myself wishing I could access the data inside the DMatrix after creating it. For example, after slicing up a DMatrix for cross validation folds, I want to look at some of the columns in "dtest" for post-processing (e.g., doing GROUP BY type operations on my metrics based on data column(s)).
Right now the only way to do this is to reimplement mknfold and cv myself... not end of the world but rather hacky.
Could we get a way to either:

extract columns from a DMatrix into a numpy array
or
construct a numpy array (recarray? 2d array? whatever) or scipy.sparse.csr_matrix from DMatrix?

The structure of Dmatrix is not built to make manipulation easy.
Old question, no answer. Closing

But the structure of DMatrix is exactly that of scipy.sparse.csr_matrix. I guess bad things could happen if scipy changes their format (why would they... it's csr), but that's what version pinning is for?
Yeah I realize that DMatrix is structured for internal use/performance.
However, forcing users to maintain 2 copies of data (one numpy/scipy/other, one DMatrix) is unnecessarily awkward.


add explicit check for ABI version

and use abi version for run_exports
this check will fail when the ABI version changes, which will prompt a manual change of run_exports, at which point we'll need to re-check https://ofiwg.github.io/libfabric/v1.22.0/man/fabric.7.html#abi-changes
alternative: track abi as its own package, which would better handle the fact that major libfabric releases don't necessarily break the ABI (2.0 will not, hence the upper bound of 3.0).

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


Deprecate prettier pre-commit hook

The prettier pre-commit hook has been deprecated and the repo has been archived since prettier made some breaking changes.

Sorry, I should have opened this in scientific-python/cookie.


Crash when closing second window

The following code crashes with the attached core dump when using the window's close button (the x in the corner) but not when closing from button's onClick.
@Composable
@Preview
fun First(isOpen: MutableState<Boolean>) {
    MaterialTheme {
        Button(onClick = {
            isOpen.value = true
        }) {
            Text("Open second window")
        }
    }
}

@Composable
@Preview
fun Second(isOpen: MutableState<Boolean>) {
    MaterialTheme {
        Button(onClick = {
            isOpen.value = false
        }) {
            Text("Dismiss")
        }
    }
}

fun main(args: Array<String>) {
    application {
        val isOpen = remember { mutableStateOf(false) }
        Window(title = "First", onCloseRequest = { exitProcess(0) }) {
            First(isOpen)
        }

        if (isOpen.value) {
            Window(title = "Second", onCloseRequest = { isOpen.value = false }) {
                Second(isOpen)
            }
        }
    }
}

Running on Ubuntu 20.04.
Kotlin version 1.5.31
Compose Desktop version 1.0.0-alpha4-build398
hs_err_pid388138.log

We have fixed crash during window closing on linux under some conditions in beta. Could you try if the crash still happens on your system on 1.0.0-beta5?

Not crashing anymore in my tests. (1.0.0-beta5)
Well done!

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Unable to list/delete sessions

Hello,
Only the backups seems to works.
If I try to delete/list/restore a particular session by example, I have this issue:
retmux -l 20200402_194711
Details of backup:20200402_194711
Traceback (most recent call last):
  File "/usr/local/bin/retmux", line 4, in <module>
    __import__('pkg_resources').run_script('retmux==1.0.0', 'retmux')
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 696, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1614, in run_script
    exec(code, namespace, namespace)
  File "/usr/local/lib/python2.7/dist-packages/retmux-1.0.0-py2.7.egg/EGG-INFO/scripts/retmux", line 92, in <module>
    func(sys.argv[2])
  File "/usr/local/lib/python2.7/dist-packages/retmux-1.0.0-py2.7.egg/tmuxbk/controller.py", line 89, in show_and_action
    print '\n'.join(tmux.long_info())
UnicodeEncodeError: 'ascii' codec can't encode characters in position 80-82: ordinal not in range(128)

If can help, you can find here my locale:
LANG=C
LANGUAGE=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"

Best regards,

@anthosz
It is not easy to precisely locate the problem based on the information in the comment.
Several things you may want to check:

please try to change your locale to one with utf-8 support, and try the same command again
if changing locale doesn't help, very likely you had some special characters in your tmux window name, or you were in a directory with special characters before you backup. You can find the backup in your ~/.retmux/backup  every screen/window was backup-ed there. Please double check the json file.
You can adjust the log-level in ~/.retmux/retmux.conf to have more detailed info. in ~/.retmux/retmux.log
please upgrade to the latest version, even if it may not resolve this problem, but it contains other fix.


Fixed caching of Kover report tasks

Resolves #68

It definitely would be nice to have a test on it

It definitely would be nice to have a test on it

Tests added


Update README

This fixes the type and improves the description for append and adds the entry for product.

This change is

Thanks!


Comments for changes

Makes sense to me. I'll make these changes and update this PR.

All requested changes were put in place. Clear to begin review process.


sudo sift update fails

I am using the ova version of the Sift Workstation and updated it already several times.
When I run "sudo sift update" now I receive these errors:
Command failed: apt-get update
W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file.
E: Failed to fetch 'https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
I assume it is caused by the move of the Docker repositories from apt.dockerproject.org to download.docker.com
-> https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages
My knowledge about Saltstack is not good enough to solve this.
Where can I find an easy and applicable howto?
Or is it something that can be changed centrally?

@Stoesi Are you using the latest version of the cli? Pretty sure I have an idea what's causing your issue, but to be on the safe side can you include your saltstack.log? It's located at /var/cache/sift/cli/<version_number>/saltstack.log

@digitalsleuth As mentioned I use the OVA as I have only base knowledge about Linux - and even less (better zero) about SaltStack. The installation run for a few months with some special handling at the beginning, but on my last try to update, I received the above errors.
In the meantime, I learnt more about SaltStack and was able to make it run again by this procedure:
import the OVA, start and reboot (easiest way for me to get around the error "Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)"
sudo apt-get remove salt-minion salt-common
sudo apt-get update
sudo apt-get install salt-minion salt-common
sudo sift update
In case you receive still errors, you should repeat this sequence (reason is that salt-common and salt-minion is still not installed - can be verified by sudo apt list salt* )
sudo apt-get install salt-minion salt-common
sudo sift update
It is not the smartest way and I cannot explain why sometimes I have to run the reinstall of salt-minion and salt-common twice, but at least it works.
If you still want to see the saltstack.log, just let me know - anyway, thanks for your efforts.

@Stoesi The reason you're seeing the '/var/lib/dpkg/lock' issue is because Ubuntu is attempting to do its auto updates at the same time you may be trying to do an apt update or upgrade. Thus, dpkg has a lock on the file to ensure that your apt update and the systems installation of packages do not conflict. When you have this lock, you can wait a few minutes for the system to complete its search for/installation of updates, and change the /etc/apt/apt.conf.d/20auto-upgrades config to read "0" vice the "1" that it's likely set it. Even without changing this, what you're seeing is normal Ubuntu behavior.
You should not need to re-install salt-minion or salt-common, only complete the apt update && apt upgrade to get the latest version of salt (if it's already installed). And then finally, you'll want to check out the sift-cli releases page to make sure you have the latest release of the cli, then do a sudo sift update and sudo sift upgrade (as necessary).
The reason for the salt re-installation working is because the newer releases of SIFT have some changes in them which are not supported in the older version of salt. What you're essentially doing is removing the old version of salt and installing the new version of salt, which is a roundabout way of just doing an upgrade.
In the end, were you finally able to install SIFT, or did you get errors from the actual sudo sift update command? If you received errors, then yes, please attach your saltstack.log. If not, and the installation completed fine, then the issues you mentioned should be resolved by the recommendations about.
Please try these and let me know how they work out for you.

Support for xenial is being dropped by a lot of tooling. SIFT supports 18.04 (bionic) and  we are currently working on 20.04 support for ubuntu right now.


No Docker image for ARM64

Hi,
I'm trying to install it on my RasPi 3 whose system is Ubuntu Server 64bit.
When I tried to start it,it reads:
Pulling management-center (cedalo/management-center:2)...
2: Pulling from cedalo/management-center
ERROR: no matching manifest for linux/arm64/v8 in the manifest list entries

Could you please help me?Thanks.

@Lucy2003 maybe use docker buildx kit to cross-compile the Docker image for armv8. See Docs for buildx by Docker

I've just tried to add the docker version on RPi5 - using BOOKWORK Pi OS 64 bit -  there is no image for arm8.   HELP....


Module Build Failed: Error: Plugin 1 specified in "base" provided an invalid property of "__wrapped"

Hey,
I've never seen this error message before and googling it is tough. I'm using the next branch, building it and seeing this. Has anyone had any issues?
ERROR in /Users/peter/Sites/temp/redux-api-middleware/lib/index.js
Module build failed: Error: Plugin 1 specified in "base" provided an invalid property of "__wrapped__"
    at Plugin.init (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/plugin.js:138:13)
    at Function.normalisePlugin (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:147:12)
    at /Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:181:30
    at Array.map (native)
    at Function.normalisePlugins (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:153:20)
    at OptionManager.mergeOptions (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:245:36)
    at OptionManager.init (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:383:12)
    at File.initOptions (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/index.js:223:65)
    at new File (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/file/index.js:140:24)
    at Pipeline.transform (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at transpile (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-loader/index.js:14:22)
    at /Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-loader/lib/fs-cache.js:145:18
    at ReadFileContext.callback (/Users/peter/Sites/test-labs/uc-frontend/node_modules/babel-loader/lib/fs-cache.js:28:23)
    at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:359:13)
 @ ./src/redux/configureStore.js 10:26-57

Probable solution: https://github.com/lodash/babel-plugin-lodash/issues/83#issuecomment-233941018

Not sure what this was -- but its been over a year so I'm going to close this out. Feel free to re-open if this is still an issue.


feat: support prefetch/preload modules

What problem does this feature solve?
Prefetch and preload chunk
What does the proposed API of configuration look like?
https://webpack.js.org/guides/code-splitting/#prefetchingpreloading-modules

I can try to support this

I can try to support this

My work depends on this feature, do you have any plans to implement it in the near future? If not, I will start working on this.

ok, currently I'm working on another pr, expecting your your nice work~

Supported in #5031


feat: Add spinner attribute to ui.progress #1747

Added Spinner Progress to progress.py

Implemented the necessary changes in progress.tsx.
Updated progress.py example.
Updated progress.md docs.

Closes #1747

Thanks @yashh-dev! Unfortunately, most of the people are currently OOO due to X-mas so this PR will get reviewed after New Year ( most probably after 9th of January) FYI.
Happy holidays!

Thanks for the heads up
btw the Spinner progress does not come with a description parameter but other progress components do so i have not included the description.
Should I make a custom Spinner component with a description in the mean time?
@mturoci

Should I make a custom Spinner component with a description in the mean time?

Seems like label attr is what you are looking for (<Spinner label="Wait, wait..." ariaLive="assertive" labelPosition="right" />).

type?: ' bar' | 'spinner'. Default should be bar

+1

I have
I have aligned the progress to the right
according to the below image should i position the label also to the right?
@mturoci

Thanks @yashh-dev! The PR looks mostly good, just needs a few small changes.

See my comment.
Do not center the spinner by default. Align it to the left as the the rest of the components.

I have did the requested changes @mturoci @lo5 https://github.com/h2oai/wave/pull/1771/commits/3137bfc1523b4a6efec53f6a36b9b1f215553e2e

Do you mean caption by description?

Do you mean caption by description?

Yes, my bad.

Is this the logic we are looking for @mturoci  https://github.com/h2oai/wave/pull/1771/commits/68e47330c72148526fd47812645973fee6f51d35

Yep, that's exactly what I wanted. Thanks!


More feedback types for impact and notification

Feedback guideline from Apple
Currently this module isn't supported all feedback types for impact and notification

impact - UIImpactFeedbackStyle
notification - UINotificationFeedbackType

Let me know if PR welcome. :)

Hey @jhen0409 . Wow, I am so sorry I didn't get back to you before, I totally missed the issue. PR's are more than welcome! Cute dog by the way :)

Second this. Thank you for this, definitely helpful!
Here is a full list of feedbacks:
Notifications:

[ ] Success
[ ] Warning
[ ] Failure

Impact:

[ ] Light
[ ] Medium
[ ] Heavy

Selection:

[ ] Selection

https://developer.apple.com/ios/human-interface-guidelines/user-interaction/feedback/
Look likes currently supported is:

[ ] Warning
[ ] Possibly light, or medium, or heavy
[ ] Selection

Any movement on this? Would be very much appreciated 🙏🏼

Hey @Spshulem and @Dexwell, thanks for your feedback. I will take some next week to add those. I'll get back to you then. Have a good weekend!

Don't mean to pressure you, but any ETA on this? 💝

Hey no pressure at all, I am so sorry for the wait @Dexwell we are busy these past couple of weeks haha. I'd really like to take some time 'soonish' to add those. I will ping back when it is, hopefully by the end of the month :)

@Dexwell Haha hey Doney, sorry about that, I was planning April 😬 but things are crazy at App & Flow so I had to postpone. It's still on my to do list. PR's welcomed !!

Working on a PR!

@bryanjclark Music to my ears! 💜


Ship theme as a gem

This is a nice theme!
Do you plan to provide ability for Jekyll's users to simply add theme: jekyll-type-theme and bundle install to use your theme?

Thanks for the suggestion. I've started converting the theme to a gem Jekyll theme.

@DirtyF I've finished a conversion in the gem branch (https://github.com/rohanchandra/type-theme/tree/gem), however I noticed some issues with gem themes, which could make it more inconvenient than the current installation:

SCSS variables aren't directly editable
_config.yml needs to match the Type Theme one for customization features to work
GitHub Pages users can't use the gem version

The gem is published at https://rubygems.org/gems/jekyll-theme-type.
For now, I've kept the regular theme as the default.


Update README.md and setup.py for Python modules [ECR-3992]

Overview
Python modules have been published with the following changes.

See: https://jira.bf.local/browse/ECR-3992
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 86.397% when pulling c325083875ec1dd7120814930dc0453da795f224 on vitvakatu:publish-python-modules into 0f5a506703f51bf2332c7e3625068ad1c78e54c1 on exonum:master.

@popzxc Would you please review the extension updates?

Why does it use a different version from the rest of the project?

Why does it use a different version from the rest of the project (on Pypi)?

A small oversight by me. PyPI doesn't like certain version formats, like 0.9.0-rc1, or 0.9.0-rc1.2 which are totally possible in semantic versioning. So I changed it to dev1 for testing purpose and forgot to change it back.
I published another release with version 0.9.0rc1, it is now available at PyPI.

PyPI doesn't like certain version formats

Does it forbid some version strings, allowed by semver?

Does it forbid some version strings, allowed by semver?

Even if it doesn't, it's not consistent with convention. Even the cpython project itself uses the following format:


Could you please confirm if this package can provide a license?

Could you please confirm if this package can provide a license?
I am currently developing a Metamask snap, and during a Black Duck scan before going live, I encountered a 'License Not Found' issue. I would greatly appreciate your assistance in resolving this matter.

Hey @JOHNBASS, this was fixed by #175


[Question] Issue with Generating V8 Coverage Report Using Modified v8-JSON

Hi,
I am trying to generate a V8 coverage report using monocart-coverage-reports. My goal is to modify the V8 JSON coverage data by grouping it and then generating a new V8 report from the modified JSON.
However, I am encountering an error during the report generation process:
Error generating the coverage report: Error: Invalid file coverage object, missing keys, found: bytes, statements, branches, functions, lines
I’m using the JSON format as described in the npm documentation, but it seems the structure of my modified JSON might not be fully compatible with what monocart-coverage-reports expects.
Could you provide some guidance on how to ensure my modified JSON is properly formatted for generating a valid V8 coverage report? Specifically, what key fields are required, and how should I structure the data to avoid the error above?
code:
const monocart = require('monocart-coverage-reports');
const path = require('path');

(async () => {
    try {
        const reportDir = path.resolve(__dirname, 'coverage-report');

        const mcr = await monocart({
            coverage: {
                cleanCache: true,
                name: 'Modified coverage',
                reportDir: reportDir,
                report: [['v8']],
            }
        });

        await mcr.add(<JSON FROM Docs>)
    );

        await mcr.generate();

        console.log('HTML coverage report generated successfully!');
    } catch (error) {
        console.error('Error generating the coverage report:', error);
    }
})();

Nope not working:
const monocart = require('monocart-coverage-reports');
const path = require('path');

(async () => {
    try {
        const reportDir = path.resolve(__dirname, 'coverage-report');
        const inputDir = path.resolve(__dirname, 'raw') // includes raw files;

        const mcr = await monocart({
            coverage: {
                cleanCache: true,
                inputDir,
                name: 'Modified coverage',
                reportDir: reportDir,
                report: [['v8'], ['raw']]
            }
        });

        await mcr.generate();

        console.log('HTML coverage report generated successfully!');
    } catch (error) {
        console.error('Error generating the coverage report:', error);
    }
})();

Error generating the coverage report: Error: Invalid file coverage object, missing keys, found:bytes,statements,branches,functions,lines

It is likely necessary to add a mapper in assertValidObject to convert key names like branch and function into shorter equivalents, such as b and f.
// asserts that a data object "looks like" a coverage object
function assertValidObject(obj) {
    const valid =
        obj &&
        obj.path &&
        obj.statementMap &&
        obj.fnMap &&
        obj.branchMap &&
        obj.s &&
        obj.f &&
        obj.b;

    if (!valid) {
        throw new Error(
            'Invalid file coverage object, missing keys, found:' +
                Object.keys(obj).join(',')
        );
    }
}

It seems that you have set wrong options, try remove coverage
const mcr = await monocart({
-            coverage: {
                cleanCache: true,
                inputDir,
                name: 'Modified coverage',
                reportDir: reportDir,
                report: [['v8'], ['raw']]
-            }
});

It worked, thanks for the fast response 🥳🥳🥳🥳🥳


[Enhancement] Please add NFS support

Hi,
wouldn't NFS support perfectly suit a linux-based media player? Please add.
(I have NFS shares up and running for xbmc and volumio and can't believe that I need to install and setup Samba to make another linux system work).
Cheers,
Michael

I second this feature request!

As to "code it into /etc/fstab yourself":
I don't think this is an argument. If I want to code, I don't go for a project like pimusicbox. I want to use.
And I really think this is a feature so basic while being so minor that it should be included.


source and sourceTransformer sdk use the same serverInfoPath

Describe the bug
In the SDKs, source and sourceTransformer use the same serverInfoPath, this will potentially cause problem.
We should use different path for different sdks maybe.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Kubernetes: [e.g. v1.18.6]
Numaflow: [e.g. v0.5.1]

Additional context
Add any other context about the problem here.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.

@a3hadi will pick up this issue.

@whynowy I just had a quick question. Is this a problem because two separate containers would write to the same location? I.e., would a container containing a python udf and a container containing a java udf both write to /var/run/numaflow/server-info and this could potentially cause a conflict? If this is the case, should we address this just for the sourcer service?

@whynowy I just had a quick question. Is this a problem because two separate containers would write to the same location? I.e., would a container containing a python udf and a container containing a java udf both write to /var/run/numaflow/server-info and this could potentially cause a conflict? If this is the case, should we address this just for the sourcer service?

Potentially there could be 2 containers write to the same location (e.g. udsource and source transformer).
What we should do is, for different type of UD container, use different path (instead of only addressing source and transformer).

steps to take:

Create new paths for all UD services, and use these new paths in all SDKs
Implement the same changes on the client side in numaflow
Update all images with new version number so that they use the new paths
Add note to documentation/readme that users using new SDK version also update numaflow to new version, otherwise there will be compatibility issues

Great job @a3hadi on closing this issue. 👍


[ListItem] href prop

Right now, when there is button prop, [ButtonBase] will be used. I think that it would be useful to extend this functionality to be at par with [Button], e.g. when there is href prop, root component will be by default set to a and button set to true.

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
<ListItem href="url" /> would be the same as <ListItem href="url" component="a" button />

@Mangatt Sure, why not. Feel free to work on it.