Document and Banking application modified with scalardl-java-client-sdk 2.0.4

A simple bank account application document updated with scalardl-java-client-sdk 2.0.4
A simple bank account application source code updated with scalardl-java-client-sdk 2.0.4

@scalar-boney Did you check if it works properly ?

@scalar-boney Also please apply google-java-format if not.

@scalar-boney Did you check if it works properly ?

I have already verified it with docker.

@scalar-boney Also please apply google-java-format if not.

google-java-format applied.


Decision Forest prediciton works with any number of features

Describe the bug
If I train my Decision Forest with two features and use the model for predictions with more or less features checkComputeParams() returns true and compute() does not throw an exception.
To Reproduce
#include <daal.h>
#include <service.h>

int main() {
    const size_t nClasses = 2;
    const size_t vPCAFeatures = 2;

    /* creating arrays for shallow data access */
    float vData[8] = { 0, 0, 0, 1, 1, 0, 1, 1 };
    float vLabels[4] = { 0, 1, 1, 0 };

    float vTestData[6] = { 0, 1, 0, 1, 0, 1 };

    using namespace daal;
    using namespace daal::algorithms;
    using namespace daal::data_management;
    using namespace daal::algorithms::decision_forest::classification;

    /* Create Numeric Tables for training data and labels with the data pointer of xtensor */
    NumericTablePtr vTrainData(HomogenNumericTable<>::create(vData, 2, 4));
    NumericTablePtr vTrainGroundTruth(HomogenNumericTable<>::create(vLabels, 1, 4));

    /* Create an algorithm object to train the decision forest classification model */
    training::Batch<> vTrainingBatch(nClasses);

    /* Pass a training data set and dependent values to the algorithm */
    vTrainingBatch.input.set(classifier::training::data, vTrainData);
    vTrainingBatch.input.set(classifier::training::labels, vTrainGroundTruth);

    /* Build the model */
    vTrainingBatch.compute();

    /**
     * Predict using the trained model
     */
    for (size_t i = 1; i < 4; i++) {
        prediction::Batch<> vPredictorBatch(nClasses);

        std::cout << "Before assigning model and data: " << vPredictorBatch.checkComputeParams() << std::endl;

        vPredictorBatch.input.set(classifier::prediction::model, vTrainingBatch.getResult()->get(classifier::training::model));
        /* Pass a testing data set and the trained model to the algorithm */

        NumericTablePtr vNumTestData(HomogenNumericTable<>::create(vTestData, i, 6 / i));
        vPredictorBatch.input.set(classifier::prediction::data, vNumTestData);
        std::cout << i << " features: " << vPredictorBatch.checkComputeParams() << std::endl;

        vPredictorBatch.compute();
        printNumericTable(vPredictorBatch.getResult()->get(daal::algorithms::classifier::prediction::prediction), "Result");
    }
}

Output
Before assigning model and data: 0
1 features: 1
Result
0.000
1.000
0.000
1.000
0.000
0.000

Before assigning model and data: 0
2 features: 1
Result
0.000
0.000
0.000

Before assigning model and data: 0
3 features: 1
Result
0.000
1.000

Expected behavior
I would expect checkComputeParams() to return false and compute() to throw an exception for mismatching number of features. If I do the same with a SVM it results in an exception.
Environment:

OS: [Ubuntu 18.04]
Compiler: [GCC7.4]
Version: [2019 Update 5]

Hello @Mightrider
Fix is already uploaded to master branch.
Thanks again for pointing out this issue. I was glad to help. Please contact if you have additional questions or problems.


added files for new science blog

@HannaHei / @dsarkar
Is the some reason there was no link in the text "They can be accessed under the "Analysis" tab ..." to the actual Analysis tab on https://www.coronawarn.app/en/analysis/?
Would it make sense to add the link now?

@MikeMcC399 Nice suggestion. Will you offer a PR (I will merge) or shall we fix that one? Thanks!

@dsarkar
@HannaHei has fixed this with PR https://github.com/corona-warn-app/cwa-website/pull/1809, which is already merged, so I have no further questions 🙂 !

@MikeMcC399 Alright, thanks!


withCount and BelongsToMany: Maximum function nesting level of 'xxx' reached

Laravel Version: 5.5.21
PHP Version: 7.1
Database Driver & Version: MySQL 5.7

Description:
When you add $withCount on two models that are linked with a BelongsToMany and you want to retrieve one it stops because of "infinite loop".
If you comment any $withCount there is no error.
Steps To Reproduce:
Exam.php
protected $withCount = ['blogPosts'];

public function blogPosts(): BelongsToMany
{
    return $this
        ->belongsToMany(BlogPost::class, 'blog_post_exam_pivot', 'exam_id', 'blog_post_id')
        ->withTimestamps();
}

BlogPost.php
protected $withCount = ['exams'];

public function exams(): BelongsToMany
{
    return $this
        ->belongsToMany(Exam::class, 'blog_post_exam_pivot', 'blog_post_id', 'exam_id')
        ->withTimestamps();
}

This is a known issue. Since there is a cyclic relationship there is no where at this point Laravel will know not to fetch the count/relationship again

@Dylan-DPC Any tips or workaround?
Best

@sylouuu Do separate queries for the numbers.


proposal: methods with default implementations for interfaces

Proposal Details
Add possibility of implementation method for interface.
It make able to:

Extend interface without break compatibility by implement default behaviour.
Implement functional around interface. For example interface iterator with default implementation methods Skip, Limit, etc:

Example of default implementation:
type Task interface {
	Execute()
}

func (t Task) ExecuteMeasure() time.Duration {
	start := time.Now()
	t.Execute()
	return time.Since(start)
}

type Impl struct{}

func (_ Impl) Execute() {
	time.Sleep(time.Second)
}

It mean: Impl is implemented interface Task. I can call Execute from both types: Impl and Task. But I can call ExecuteMeasure only for Task only:
	var a Impl
	var b Task = a
	b.ExecuteMeasure()

Example of functional implementation around interface
type Iterator[T any] interface {
	Next() (T, error)
}

func (i Iterator[T]) Skip(count int) (int, error) {
	for i := 0; i < count; i++ {
		if _, err := i.Next(); err != nil {
			return i, err
		}
	}
	return count, nil
}

func (i Iterator[T]) Limit() Iterator[T] {
	...
}

#16254

Duplicate of #16254


New version: GridInterpolations v1.1.1

Registering package: GridInterpolations
Repository: https://github.com/sisl/GridInterpolations.jl
Created by: @MaximeBouton
Version: v1.1.1
Commit: 934bcdc4961353d8e80d590a1409a0e7d4d964b6
Reviewed by: @MaximeBouton
Reference: https://github.com/sisl/GridInterpolations.jl/commit/934bcdc4961353d8e80d590a1409a0e7d4d964b6#commitcomment-35417164
Release notes:

add iterator over the grid
add Cartesian indexing

TagBot tag


add pthread_getattr_np() and pthread_attr_getstack() for Solaris

r? @JohnTitor
(rust_highfive has picked a reviewer for you, use r? to override)


Document missing steps in remote attestation

The current implementation of remote attestation verifies that the enclave is genuine, but it does not verify that (1) it is running the correct code, and (2) it is in release mode. (Launching enclaves in release mode requires a Launch Enclave or a license from Intel.)
In addition, the enclave is currently not signed using the user's private key, but rather a sample key. This will need to change once we start validating the enclave's identity.
This PR adds TODOs to document these missing steps.

Thanks!


Upgrade pyright to a newer version

Problem
VSCode uses a newer version of Pyright than what we do in linting. We are frozen on a earlier version because of a huge number of updates we would need to do to fix linting errors.
Impact
We are seeing warnings in the editor that we do not see in CI, which is annoying, and gets people used to ignoring warnings in the editor rather than fixing them.
See earlier attempt

https://github.com/owid/etl/issues/1113

We know this is large and annoying to fix. Eventually we will want to, but we can also live with the status quo for a while longer.

I tried upgrading pyright to 1.1.373 which is the version used by Pylance in VSCode. There are ~2700 errors that need to be deat with. In summary, newer pyright version can detect more typing issues, but most of them are not very useful, e.g.

Argument of type "FrameOrSeries" cannot be assigned to parameter "df" of type "DataFrame"
Argument of type "DataFrame | None" cannot be assigned to parameter "df" of type "DataFrame"
Import "shared" could not be resolved
Argument of type "str | None" cannot be assigned to parameter "url"

They are often pandas-related typing issues that are mostly cosmetic and don't improve quality of code.
Upgrade plan
Parse errors from pyright --outputjson and use # type: ignore to silence the following types of errors:

All recipes in etl/steps/
All tests
Errors in core etl code that cannot be easily fixed

Done. Note that we've decided to relax type checks for recipes, and CI now passes even with failing type check. Users still see issues underlined red in VSCode which should be enough.


Update swedish language files

Here's a new updated version of the swedish language files

Closing, since re-opened in #1417


microk8s enable gpu -- daemonset fails to initialize

I have a cluster with 6 nodes, two of them have GPUs. I want to be able to eventually schedule some GPU applications to those specific nodes. After running microk8s enable gpu I notice all of the pods in the gpu-operator-resources namespace are stuck in the Init phase and have the following error when running kubectl -n gpu-operator-resources describe po <pod name>
All nodes are running Ubuntu Server 20.04
Events:
  Type     Reason                  Age               From               Message
  ----     ------                  ----              ----               -------
  Normal   Scheduled               65s               default-scheduler  Successfully assigned gpu-operator-resources/nvidia-device-plugin-daemonset-k8mrg to <host>
  Warning  FailedCreatePodSandBox  3s (x6 over 65s)  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox runtime: no runtime for "nvidia" is configured

I couldn't find any information about this particular error in the microk8s documentation. Based on some threads a while ago (here, and here) it seems like it shouldn't be necessary to update the docker daemon runtimes with the "nvidia" one because microk8s is supposed to be using containerd?
I'm just looking for some guidance to solve this issue and also help update the documentation if necessary.
inspection-report-20220204_183201.tar.gz
P.S.: microk8s is great! Thanks for making such a great piece of software :smile:

@ZacBlanco I'm in the same boat.  It isn't a straight forward process, but CUDA never is.   This document has some tidbits that I'm trying right now:
https://discuss.kubernetes.io/t/my-adventures-with-microk8s-to-enable-gpu-and-use-mig-on-a-dgx-a100/15366
One key piece I didn't realize is that you don't want the nvidia drivers loaded before the gpu addon runs.  I guess it needs to do that part for you?

@ZacBlanco but if you read the add on source code, you see that it seems try to handle the case that the drivers are already loaded:  https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/actions/enable.gpu.sh
anyways, not much help but wanted to share the threads i'm pulling on since we are in the same situation
may the CUDA gods be with you

@ZacBlanco i just spent a few hours debugging my gpu add-on enable, and this was my issue:
https://github.com/ubuntu/microk8s/issues/2662
cgroups2 needed to be disabled

Hello @ZacBlanco, I have a similar issue with my cluster (mk8s v1.23, gpu-operator v1.8.2) where the master node does not have a GPU. I've noticed that if I enable the add-on from a node that has a GPUs the daemonset eventually succeeds. For this to work you cannot use the --worker flag while joining new nodes since this will disable the control plane on that node and force you to enable the add-on from (in my case) the master node. I hope this will help you. Nevertheless, this seems to be a bug because I can not use the --worker flag within a cluster where the master node does not contain any GPU.

I also encountered the same error. I resolved the error by modifying the /var/snap/microk8s/current/args/containered-template.toml on the newly added node. I copied default_runtime_name and other missing nvidia related configs by referencing the  previously added node. After modification, reboot the newly added node, I found out that the initialization step passed!! (Tested under microk8s 1.23.3, Ubuntu 18.04.5 and 20.04.2)


next gen

@juancarlospaco this PR is all yours for review!

Thanks for the review @acamino! Please see my changes in the last commit. The version for twilio-node stayed as "3.0.0-rc.13" because it seems it's the only way to strictly callout for a strict version number.
Cheers

LGTM!


fix(android): Use cdvPluginPostBuildExtras instead of ext.postBuildExtras (CB-14163)

Use cdvPluginPostBuildExtras instead of ext.postBuildExtras
Platforms affected
Android
What does this PR do?

Adds a reference to the build-extras.gradle file in plugin.xml so that the code in build-extras.gradle will run with the main Cordova build.gradle.
Replaces incorrect usage of ext.postBuildExtras with usage of cdvPluginPostBuildExtras.

What testing has been done on this change?
Added the modified cordova-plugin-file to a Cordova project and verified that the code in build-extras.gradle ran during the execution of the command cordova build android.
Checklist

[x] Reported an issue in the JIRA database
[x] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[ ] Added automated test coverage as appropriate for this change.

Run current tests

CI: Once more please.

is this change needed? I am curious if I should be running the code
defined in the build-extras.gradle file

For context, the original issue this PR addresses is on jira at https://issues.apache.org/jira/browse/CB-14163
The motivation appears to be a bug if multiple plugins are trying to use ext.postBuildExtras where one will overwrite the other (as claimed in the bug report).

if the plugin.xml doesnt have the change in this pull request the build-extras.gradle wont exist in the build output. So I am really wondering if the contents of the build-extras.gradle needs to be run at all. Cause if it does then i think this change is important


[BUG] Image schema raises error in new version

🐛🐛 Bug Report
The new version of hub v.1.3.7 raises the  following error: hub.exceptions.NotFoundException: Not supported dtype for Image
with the schema:
schema = {
   'image': Image(shape=(60, 160, 3), dtype='uint8'),
   'label': Text(max_shape=(max_shape,))
}

when I try to run the following line: ds = hub.Dataset(f"debadityapal/{ds_tag}", schema=schema, shape=(5000,), mode="w")
Error is not raised in v1.3.5

having the same problem with both `uint8' and 'uint16'

Hey guys! This issue will get resolved soon in Hub 2.0. We're releasing an alpha version next week, so stay tuned!

Closing this issue, as there is no schema in 2.0.
@DebadityaPal, @pablovela5620 - I'm also excited to announce we’ve released the 2.0 community beta - you can try it out using pip (pip install hub). You can access the docs here, and access some small tutorials to get started with 2.0 here! You can also let me know if you run into any issues, I'll be happy to help! If you haven't, please consider joining our Community Slack to receive further updates.


Pull in data from YNAB API

The dashboard currently just pulls in data from some finance package. Instead, it should pull in data from a user's ynab account/budget


Client Verbosity Settings

Description of the new feature/enhancement
As a power user I would like to be able to get additional data about what the client is doing so I can be informed.

Proposed technical implementation details (optional)
Note:
The verbosity levels might be "silent", "default", and "verbose".
There should also be a setting or mechanism to support screen readers
Progress bars don't work well for screen reader applications

Hi,
Regarding screen readers and progress bars: if we're talking about progress messages when an app is being downloaded/installed/updated/uninstalled, providing a textual output would work, something to the effect of:
winget install notepad++
Downloading 10%
Downloading 20%
...
Downloading 100%
Installing 0%
...
Installing 100%
For a practical example as to how screen readers can react to console output changes, take a look at how Git command-line for Windows does it when fetching commits while Narrator or NVDA is running.
Thanks.

@denelon I guess this is completed. https://github.com/microsoft/winget-cli/blob/master/schemas/JSON/settings/settings.schema.0.2.json#L34

@denelon I guess this is completed. master/schemas/JSON/settings/settings.schema.0.2.json#L34

I disagree. This is about verbosity during the install process, not post-install looking at a log.

This may also be part of the mechanism to support different UX (User Experience) modes. The default is the way the client operates today where users must type the correct command to get the desired behavior. The other is more of an "interactive" mode where the user sees more prompts and WinGet tries to help them be more successful.
As I've been thinking a bit more about it maybe it's a "prompt" mode where the user sees more prompts or hints when the client can make intelligent suggestions or provide options. This shouldn't be confused with:
Are you sure [Yes | No] ?_

It's more like a command was run like "winget upgrade " and the installer type changes. Rather than telling the user they need to uninstall the previous version "manually", the client could prompt:
Would you like to remove the previous version and continue [Yes | No]?_

We will clearly have some discoverability concerns with this setting, so maybe there should be a first run experience (if no explicit setting is in place) where the first time the user runs "winget" we can provide an informational message about this mode so it's not breaking for automated scenarios.


Error: The module was compiled against a different Node.js version using NODE_MODULE_VERSION 48.

Hi, I'm getting the following error after trying to use mpris-service and running my program:
Error: The module '<project>/node_modules/dbus/build/Release/dbus.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 48. This version of Node.js requires
NODE_MODULE_VERSION 54. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or`npm install`).
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:173:20)
    at Object.Module._extensions..node (module.js:598:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:173:20)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (<project>/node_modules/dbus/lib/dbus.js:3:13)
    at Object.<anonymous> (<project>/node_modules/dbus/lib/dbus.js:148:3)

I'm trying to use it in an Electron program. Would you happen to know how to recompile dbus.node to work with my version of node (6.10.1)? Or maybe there's a different fix for this issue?

Maybe npm rebuild dbus?

Nope, the problem still occurs. Reinstalling dbus manually doesn't help either.

Okay, maybe a dbus upgrade to v1 can fix it.

The package electron-rebuild can fix this issue. You can run ./node_modules/.bin/electron-rebuild or if you have it installed globally, just electron-rebuild and it will recompile the module for your current version of node.js
It's weird that the published version of dbus is compiled against NODE_MODULE_VERSION 54 which is not an LTS release and it's not even in the list of previous releases.
The dbus package should be updated to compile either with v6, the current LTS, or v8 which will become LTS on October 2018 (less than two months from now)

I can confirm that this fixes the above problem.
However, I still can't see the program being registered and it doesn't show up with the rest of mpris-supporting programs, but that's probably another issue altogether.

@nukeop the developers seem busy at the moment, but since you created this issue, you could close it yourself.


Handle user:group specification in Dockerfile

When checking whether a user is in the allowed range, a USER directive with uid:group is now allowed.

@bparees ptal

lgtm.

LGTM, pending fixing @GrahamDumpleton check

Hold off merging this. As per comments on original issue, this may be pointless as deployer may not use the group anyway. If that is the case, need to work if deployer should honour the group in Docker image data.

@GrahamDumpleton I believe we still need the fix for s2i not to reject images unnecessarily. We're simply not interpreting the user spec in a Dockerfile correctly right now.

@csrwng +1, i think this fix is as good as it can get from an s2i perspective.  lgtm.

I have created https://github.com/openshift/origin/issues/8618 for wider issue of changing Kubernetes/OpenShift to honour the group. This change in this patch is still useful in context of standalone S2I usage, but images produced still aren't going to necessarily run properly on OpenShift.

@csrwng @GrahamDumpleton are we in agreement that this PR is as complete as it's going to get?

yes

[merge]


Depth sensor readings, depth sensor range, and point cloud

Hi there, I have a few questions regarding the depth camera in Habitat-lab:
1, I am using depth images and open3d's interfaces as following to create point cloud objects:
depth_img = o3d.geometry.Image(depth_as_np) fx = camera_info_k[0][0] fy = camera_info_k[1][1] cx = camera_info_k[0][2] cy = camera_info_k[1][2] camera_intrinsic = o3d.camera.PinholeCameraIntrinsic(      camera_info.width, camera_info.height, fx, fy, cx, cy ) pcd = o3d.geometry.PointCloud().create_from_depth_image(      depth=depth_img,      intrinsic=camera_intrinsic,      extrinsic=np.identity(4),      depth_scale=1000.0,      depth_trunc=1000.0,       stride=1, )
However, the point cloud generated looks too deterministic and different from what we normally expect. See the images linked below:

The first image is a point cloud generated in Habitat's test scene and the second is a Matlab point cloud example.
As you can see, the Matlab example has a lot more randomness in terms of point coordinates. I wonder why the point cloud generated using Habitat's depth image looks different.
2, I also wonder there's a way to limit the depth camera's FOV in its depth range and vertical axis. Since I am not interested in objects that are located on the ceiling or are far away from the robot itself.

I'm not familiar with Open3D, but depth_scale=1000.0 seems odd. Habitat-lab outputs depth in [0,1] by default where a value of 1 represents something 10m away, so maybe depth_scale=10.0?

Not sure where that source image is from, but it looks like it's from a real camera. A simulate camera (without a noise model) will be perfect and things will be very regular.

@yhymason Feel free to re-open the issue, if you still have questions.


V-71947 Does not Consider Authentication Other Than Passwords

The check text for V-71947 states that "If passwords are not being used for authentication, this is Not
Applicable." This check does not perform a check to see if passwords are being used for authentication.
This test could either check the system to confirm that password authentication is enabled and continue, or create a new attribute similar to smart_card_status which will reduce the impact if disabled.

Honestly, I have no idea how to do this effectively across all of the PAM subsystems considering all the ways that passwords can be hooked in and how easy it is to simply jump parts of the stack.
I guess that you could try logging in as the user and see if there is a password prompt but that's still not really authoritative for all potential methods.


Remove the duplicate starting and ending points

The starting point and the first left segment's A point are the same. The ending point and the original spline's D point are the same.

Thank @weihsinyeh for contributing.


AreDefaultContextMenusEnabled don't work during first load

I have set WebView2CreationOptions.AreDefaultContextMenusEnabled = false; in SampleEdgeSharpConfig.cs to disable the right click.  I am based on the Win32 sample. The problem is between the window creation and the render of the webview. During this interval the right click (so the context menu) can be trigger. But when the page is loaded and displayed by the web view, the context menu no longer works as expected.

@Brouilles sorry, I have not really had bandwidth to revisit some of the flow here. When you say it no longer work as expected, you mean the context menu is not expected to show?
Does it seem related to this?
https://stackoverflow.com/questions/63322779/wpf-webview2-not-able-to-disable-context-menu?
I will find sometime over the weekend to reproduce.

@Brouilles
I made a change in SampleConfig.cs and works for me:
    internal class SampleConfig : Configuration
    {
        public SampleConfig() : base()
        {
	    // ------
            WebView2CreationOptions.AreDefaultContextMenusEnabled = false;
        }
    }

EdgeSharp_win-32_Sample.zip

It is during the initialization of the webview, before the html render. I can open the context menu. During some ms/s.

I am not quite sure what you are trying to do really. But my guess is it may be a threading issue.  Some functions will not work if not executed on the browser thread.
Please can you see how the dispatcher is used here:
https://github.com/webview2/EdgeSharp/blob/f4c7eafdb21f356169dec6e380459a66a2b56d2a/src/EdgeSharp.Core/Defaults/ResourceRequestSchemeHandler.cs#L95
More samples here - https://github.com/webview2/EdgeSharp/search?q=Dispatcher.Browser
If that does not work, you may need to attach a skeletal sample.


update jenkinsfile forecasting stash

Update to jenkinsfile for forecasting that cannot be made from forecasting PR

Job PR-1259-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1259/3/index.html

Job PR-1259-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1259/4/index.html


Denying item usage in region.

I think it will be awesome if you'll add the flag that prevents the players from using specific item in your region (but you and allowed players can). For example i have a carrot on a stick which functions like a magic wand (via scoreboard useItem thing), and i want to deny using it in region if the player is not allowed to do that. :)

This is a nice idea, but it needs to be able to prevent the use of blocks too, like trapdoors, doors, buttons, etc... not just items 👍


[Discussion] Integrating port specific syscall proxies

With the risc-v/litex port, we're able to access the TIME and TIMEH CSRs in usermode. I would like take advantage of this feature to replace the proxies for syscalls, such as timer_gettime, with an equivalent implementation that avoids a context switch, where appropriate.
I understand that the syscall.csv database is used to generate the syscall proxies and stubs, but there doesn't seem to be any facility to provide a different implementation. Potentially, I could remove the desired syscalls from syscall.csv and provide my own proxy which is linked into libproxies, but it would be nice if this was more generally supported, rather than patching the kernel locally.
I'd be interested to know if anyone has had a similar idea, or potentially there is a method to achieve this in NuttX which I have overlooked.

@g2gps I suggest you to send thing discussion to mailing list as well.


[JOSS REVIEW] Elaborate on applications

In your paper you mention some relevant applications. I think it would be good to give some more details about the applications and perhaps also add some figures showing the results of the simualtions using your software.
This issue is related to the review here: https://github.com/openjournals/joss-reviews/issues/7307

The changes have been committed and are now reflected in the updated version of the paper.
https://github.com/CastillonMiguel/phasefieldx/commit/487b67af6c257d0bf032dd8f01234dbc184ac4e1


UI-Shapes show Halo error in addPointHandle:

Using the latest Cuis-Smalltalk-Dev image Cuis6.0-5542.image with the latest Core Update (5588-Symbol-value) as of today, 2022-12-18 with ,  when trying to get the Halo of a RectangleShapeMorph,  I get the error shown in the image.
Seems to me that the command: self class haloPointIcon is returning nil, therefore it does not recognize the extents message.

The same happens with at least with the BezierCubicMorph, BezierQuadraticMorph, CircleShapeMorph and the LineShapeMorph.

On 2022-12-08 10:11, Ricardo Pacheco wrote:

Using the latest Cuis-Smalltalk-Dev image Cuis6.0-5542.image with the
latest Core Update (5588-Symbol-value) as of today, 2022-12-18 with ,
when trying to get the Halo of a RectangleShapeMorph, I get the error
shown in the image.

I could not reproduce this, but found uses of Utf8{String|Symbol} in
Cuis-Smalltalk-UI
Now updated are:
tools/Morphic-MetaProperties.pck.st
lib/UI-Panel.pck.st
Please pull and try again.
-KenD

Thanks a lot! I reinstalled Cuis again and both UI-Components and UI-Tools and now the Halo is properly displayes for all the Morphs.

As a side effect now I'm able to see properly the MetaProperties also, thanks !!


Update README.md

Grammar

Thanks for your contribution , closing this issue as this change no longer needed.


Fix OB detector not getting correct shared value on demo playback

cg_pmove.shared is always 0 on demo playback, whereas cgs.shared has the correct value.

refs c8d4ee3845f426a58b1a2968d7ab2367bde48bec


Add theme check and get repo from context

Adding this step will enable the theme check plugin in the Playground instance, enabling us to check whether the theme is fit to be published in the WordPress.org theme directory.
I'm also fixing an oversight where the repo where this could run was hardcoded.

We'll need to update any existing integrations by adding the repo to any createBlueprint calls, right?

They are taken from the context here, so it's not necessary to alter the current integrations.


Lighten up / Blur images for readability

Hi @sasha-astiadi can you help me out with these? I saw you did some lightening / effects for other websites for readability.
Home Page

[x] All images

Other Pages

[x] Header Image

done https://zanzibar.ourworld.tf/


Adjust kubelet bootstrap option for Windows

v1.12

Drop cadvisor-port
Drop MountPropagation from feature-gates

v1.13

Drop MountPropagation from feature-gates

v1.14

Support
Remove nanoserver-1803 suffix

Issues:
rancher/rancher#17341

You need to update the PR once 2.2.0 released.
v1.13.4-rancher1-3

Marked related documents for the changes:

For mountPropagation https://kubernetes.io/docs/setup/windows/intro-windows-in-kubernetes/#v1-pod.
For cadviser-port https://kubernetes.io/docs/tasks/debug-application-cluster/resource-usage-monitoring/#cadvisor

LGTM, add support for 1.14

LGTM

Updated for version 1.14.1-rancher1-2, LGTM

@thxCode can we organize the commits in the following way:

2 commits
the first commit is the base copy of 1.14
the second commit with the actual changes.

LGTM


"Select a predefined carrier" does not work on main branch

Selecting a predefined carrier from the dropdown when creating a carrier does not populate the sip gateways for that carrier.

If we look on legacy branch, where it does work, we can see that when the user selects a predefined carrier from the list we execute this api.
That sends a POST to /ServiceProviders/${currentServiceProvider}/PredefinedCarriers/:predefined_carrier_sid, which creates a new voip_carrier based on the template data in the predefined_carriers table.  It creates also the sip_gateways.  At that point all the webapp needs to do is retrieve the carrier by the sid that is passed back from the POST.
Somehow this is not happening on the main branch, and I suspect the api above is not being called.


Add openvino-nightly to automated tests

Add openvino-nightly to automated tests (in addition to the openvino that is installed by setup.py).
We may not want to keep this for all the tests forever since it doubles the amount of tests on every PR - but for now it would be useful to check PRs with openvino-nightly before the OpenVINO 2023.0 release, and to catch any issues with openvino-nightly in existing code.
Also changed Python versions to test to 3.8 and 3.11.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


6 users can view holon scenarios

Please keep in mind: I also did #5 within this branch
Code is completed except for the following:

texts
maxvalues for the indicators (I need them to determine the color of the circles)
api-call has not been made

I am working hard on getting those numbers right now. I've pushed on the bouwteam to finalize the inputs and outputs decisions and formalized those this morning. Directly after, I updated the mockup (which I'll send via mail). For this PR specifically this slide applies:


Remove nic allocation txn during Vm deploy

During deploy Vm failure, entries for nics will remain in DB. This will allow cleanup of any allocated nics.
Steps to reproduce:
Create 2 networks. One of the with a small IP range (/29 or /30)
Deploy Vms with both networks until IPs in smaller network are exhausted
Without fix, there won't be any nic entries for failed VM. UserVm Scavenger will not find any nics to cleanup.
With the fix nic will be removed during Vm cleanup
DEBUG [o.a.c.e.o.NetworkOrchestrator] (UserVm-Scavenger-2:ctx-ddff4ea8) (logid:48d79c3c) Removed nic id=27
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[X] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@kishankavala a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_multiplication_x: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_multiplication_x: debian :heavy_check_mark: suse15. SL-JID 6643

@blueorangutan package

@harikrishna-patnala a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@kiranchavala a [SF] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian Build Failed (tid-7246)

@blueorangutan test rocky8 kvm-rocky8

@kiranchavala a [SF] Trillian-Jenkins test job (rocky8 mgmt + kvm-rocky8) has been kicked to run smoke tests

[SF] Trillian test result (tid-7247)
Environment: kvm-rocky8 (x2), Advanced Networking with Mgmt server r8
Total time taken: 48647 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7809-t7247-kvm-rocky8.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File


Failed to upload sourcemap to New Relic in a nextjs project.

Description
Hi! I am not sure if this is the right place to ask this question, I am sorry if it isn't.
We are using New relic in our Nextjs project and have installed the browser agent. The setup is working as expected with the help of this guide, however, I am trying to upload the sourcemap of my application using this plugin and it's giving me this error: javascriptUrl must be a valid uri. error in the console.
According to this newrelic post, it sounds like it was due to the fact that Nextjs generates these dynamic routes in the sourcemap folder and New Relic API rejects these patterns. I am wondering if the NR team is aware of this and if there's a recommended setup where I can just upload sourcemaps in the next.config.js file as part of the webpack config (or other setups)?
Expected Behavior
I should be able to upload sourcemap in a nextjs project
Troubleshooting or NR Diag results
Steps to Reproduce
  new NewRelicSourceMapPlugin({
          applicationId: APP_ID,
          apiKey: NEW_RELIC_API_KEY,
          staticAssetUrl: "https://example.com",
          releaseName: "unique-name",
          released: "unique-id",
          errorCallback: e => {
            console.log(e);
          },
          noop: typeof NEW_RELIC_API_KEY === "undefined", // upload source maps in prod builds only
   });

Your Environment

ex: Browser name and version:
ex: Node version:
ex: Operating System and version:

Additional context

@Toxiapo this repository is maintained by the Node.js agent team.  That plugin you're referencing isn't maintained by New Relic at all.  Have you tried reaching out in their repository?  Also for more context here is the New Relic Browser Agent repo.
If you've tried all those avenues may I suggest leveraging our support team over at support.newrelic.com which can help deep-dive into solving the problem. They will also ask to collect the necessary information which may or may not be sensitive (such as logs).
I'm going to close this issue as it is not relevant for this project.


config: ensure correct labelname in JSON target group.

:+1:

Does that play well with Godeps? It looks like you changed the dependencies in the Godops workspace but not Godeps.json.

The author of Godeps described this as the way to do it. If you are waiting for a patch in a dependency, you know will be merged, just apply the patch to the dep folder and it will be overwritten with the next vendor upgrade.
Makes way more sense to me then merging tests that fail until the next vendoring upgrade or leaving a bug unfixed until the next vendoring upgrade.
We/I did this for the last few patches to client_golang as well. Worked well.

I see... One day, I'll know to handle Godeps correctly... :)
:+1:


documentation for calibration

after testing the examples, it looks like the joystick I'm using needs to be calibrated because I see vrx=506 and vry=510 in neutral position.
After checking the CalibrateJoystick example, it's not clear how this calibrate actually works. Should these vrx and vry be 'calibrated'?

Calibration is the setting of the axis response range.
For example, for Arduino, the joystick axis (vrx or vry), when pressed in different directions,
can return a value in the range [10, 980] (for different joysticks, these values can be different, ideally [0, 1023]).
Then we can set the lower bound of the range to 100 (must by great than the minimum axis value),
and the upper bound to 900 (must by less than the maximum axis value).
[0, 100] - the axis is pressed down,
[900, 1023] - the axis is pressed up,
(100, 900) - the axis is not pressed.
By default, this range is [100, 923].
For calibration, we can use 2 methods:

calibrate (int low, int high)
low - the lower bound of the values range,
high - the upper bound of the values range.
In the example above: low = 100, high = 900.

Or calibrate(int adcMin, int adcMax, int deviation)
adcMin - min value of the board ADC (for Arduino, 0);
adcMax - max value of the board ADC (for Arduino, 1023);
deviation - deviation from the value’s axis range (default, 100),
when the axis is considered pressed.
low = (adcMin + deviation)
high = (adcMax - deviation).
For Arduino: adcMin = 0, adcMax = 1023, deviation = 100
=> low = 0 + 100 = 100, high = 1023 - 100 = 923.

Test results
Neutral position:
| SingleRead: NOT | MultipleRead: UP | Press: 0 | Up: 1 | Down: 0 | Right: 1 | Left: 0 |
VRx: 1861 | VRy: 1840 | SW: 1 |

Down:
| SingleRead: NOT | MultipleRead: DOWN | Press: 0 | Up: 0 | Down: 1 | Right: 1 | Left: 0 |
VRx: 1863 | VRy: 0 | SW: 1 |

Up:
| SingleRead: NOT | MultipleRead: UP | Press: 0 | Up: 1 | Down: 0 | Right: 1 | Left: 0 |
VRx: 1863 | VRy: 4095 | SW: 1 |

Left:
| SingleRead: NOT | MultipleRead: UP | Press: 0 | Up: 1 | Down: 0 | Right: 0 | Left: 1 |
VRx: 0 | VRy: 1840 | SW: 1 |

Right:
| SingleRead: NOT | MultipleRead: UP | Press: 0 | Up: 1 | Down: 0 | Right: 1 | Left: 0 |
VRx: 4095 | VRy: 1843 | SW: 1 |

So basically it only seems to detect UP and DOWN. Leaving it in neutral position reads UP, and LEFT and RIGHT are not detected.
I'm using:
#define SW_PIN 27
#define VRX_PIN 26
#define VRY_PIN 25
#define ARDUINO_ADC_MIN 0
#define ARDUINO_ADC_MAX 1023
#define AXES_DEVIATION 100

joystic = new AxisJoystick(SW_PIN, VRX_PIN, VRY_PIN);
joystic->calibrate(ARDUINO_ADC_MIN, ARDUINO_ADC_MAX, AXES_DEVIATION);

How would I properly calibrate this @YuriiSalimov?

ah, because I'm using ESP32 the values are between 0 and 4095. So:
#define ARDUINO_ADC_MIN 0
#define ARDUINO_ADC_MAX 4095


Error: looks like "https://osiris.azurecr.io/helm/v1/repo" is not a valid chart repository or cannot be reached: error unmarshaling JSON: while decoding JSON: json: unknown field "acrMetadata"

I couldn't  add the repo to helm chart. I have an AKS cluster and my helm version 3.3.4.
Kindly help with this

Same issue

I have the same issue. Is there any workaround to get osiris?


Add Redux toolkit and Fix Nifty

Use redux tool kit for identitySlice with tests. Reorganize folder structure
Update helpers file to use ether-query to get accounts and chainId. This package adds support for legacy wallets.

And about helpers name. That is not a helper module imho. I would call it eth rpc or something related. Helpers stand for methods that help other core methods. This are core methods


[Blog] Prepare for 2024 + blog navigation enhancements

Fixes #3782
Adds breadcrumbs to the blog section and post pages
Adds last-modified info to the bottom of posts.

Related Docsy issues (FYI):

https://github.com/google/docsy/issues/1789
https://github.com/google/docsy/issues/1196
https://github.com/google/docsy/pull/1791

Preview & Redirect test: https://deploy-preview-3784--opentelemetry.netlify.app/blog/
Screenshots
2024 - posts coming soon

Illustrating breadcrumbs

Illustrating page last-mod info

Putting this on hold because I don't really want an empty 2024 page.
(I'll also split out the NPM script followup change.)
Setting to DRAFT

@svrnm et al. - this is ready for review.

@svrnm - I've dropped the Blog landing page redirect, so this is what it looks like now:

And it will populate with 2024 blog posts as they arise.
So, I'd suggest that this can be merged now. WDYT?

yeah, I guess that works, TY


Clean up imports and lack of typing.

Remove a confusing star import and cleanup the typing on encoder.py
Side question for @davidplowman:  Is there a reason that the _ prefix is being used on methods on this class that are clearly not private? AFAICT, everything with an underscore prefix is called outside of this file...

@chrisruk Hi Chris, are you happy to merge this one? I think the style checker complaint is one that we can ignore.
As regards the use of _, I think many of them have actually been resolved in this file. I'm always happy to review them, however, I know there are many places where they are/aren't used appropriately for all kind of reasons, and we haven't got round to tidying them. Thanks!

Thanks! Just noticed a small typo in the signature

@chrisruk and @davidplowman


Expose replication latency via FUSE

Similar to the -pos file, it would be useful for applications to be able to track the current latency. We expose latency via the Prometheus metrics so it's just a matter of wiring it up to FUSE.
This was originally spurred by a discussion on HN: https://news.ycombinator.com/item?id=34251743

Should we close this since https://github.com/superfly/litefs/pull/340 merged?


Error when trying to use cloudflare tunnel with firezone

Describe the bug
Client sent an HTTP request to an HTTPS server. is displayed when trying to go to webpage forwarded with cloudflare tunnel on port 443
To Reproduce
Port forward port 443 to a subdomain using cloudflare tunnel and then go to that subdomain
Expected behavior
I should be able to see the webpage
Platform (please complete the following information):

Firezone Version [latest - 0.7.30]
OS: [Linux]
Distro: [Debian GNU/Linux 11 (bullseye)]
Kernel version: [5.15.84-v8+]
Deployment method: [Docker]

Additional context
N/A

Does it work fine without Cloudflare Tunnel? If so, I'm not sure this is a Firezone bug.
See if this is helpful: https://www.firezone.dev/docs/deploy/advanced/reverse-proxy/
The bundled caddy should automatically redirect http to https, but not sure about Cloudflare Tunnel; there may be a similar configuration option.


How to prevent regeneration of modelassembly?

Hello,I am new to expand framework.
I created a new project added expand win all nugets.Then removed world creator modules from required module list.
Application runs but I noticed that modelassembly.DLL is always created even on subsequent runs in release mode.
Is this the expected behavior of expand or there is something wrong on my side?

check the front end project once u use designers by default they register modules to the front end application, i recomend u never touch designers, they take initiatives that are hidden

I  manually registered the expand assemblies to my module project. They don't exist in the frontend project.
You labeled it world creator but I removed world creator modules and am not using them anywhere.
Just create a new project. Add expandWin nugets.I removed world creator because I don't plan to use it.

hmm no expand does/should not mess up the default XAF behaviour, please provide a sample to be examined

Sample.zip

prioritizing as:

ReproSample

note: researching this can take a while to users without active subscription

We will try to answer all questions that do not require research within 24hr.
To prioritize cases that require research we use the following labels in order. For all other issues the posting time is respected.

❇ Exclusive-Services
❤ Bronze Sponsor
❤ Sponsor
❤ Backer
Installation
ShowStopper
Nuget
Contribution
BreakingChange
ReproSample
Deployment
must-have

This case is prioritized.

Researched this issue and traced it to
Expand masterdetailmodule.
Checked the implementation and there is nothing wrong.The issue exists in earlier versions of expand.(went as far back as 18.2.7) they are just a little bit faster.avoiding the module prevents regeneration.With today's PCs apps will still start in less than 50 seconds with regeneration of the assembly. So I am closing the issue


PromiseConstructor - Promise is default in .toPromise()

Please see the first part of https://github.com/caolan/highland/pull/628#issuecomment-306671817.


using libfranka in own cpp file

i installed the libfranka and franka_ros using command sudo apt install ros-kinetic-libfranka ros-kinetic-franka-ros now i have created own catkin workspace and own package. i created a cpp file incluing libfranka and franka_ros to control robot. but at making my package i met error like following
In file included from /opt/ros/kinetic/include/libfranka/franka/robot_state.h:8:0,
from /opt/ros/kinetic/include/franka_hw/franka_state_interface.h:7,
from /opt/ros/kinetic/include/franka_hw/franka_cartesian_command_interface.h:7,
from /home/yin/test_ws/src/image_proc/src/franka_myController.cpp:1:
/opt/ros/kinetic/include/libfranka/franka/duration.h:24:12: error: expected ‘;’ at end of member declaration
Duration() noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:24:14: error: ‘noexcept’ does not name a type
Duration() noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:24:14: note: C++11 ‘noexcept’ only available with -std=c++11 or -std=gnu++11
/opt/ros/kinetic/include/libfranka/franka/duration.h:31:30: error: expected ‘)’ before ‘milliseconds’
explicit Duration(uint64_t milliseconds) noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:38:17: error: ‘std::chrono’ has not been declared
Duration(std::chrono::duration<uint64_t, std::milli> duration) noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:38:33: error: expected ‘)’ before ‘<’ token
Duration(std::chrono::duration<uint64_t, std::milli> duration) noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:43:31: warning: defaulted and deleted functions only available with -std=c++11 or -std=gnu++11
Duration(const Duration&) = default;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:48:42: warning: defaulted and deleted functions only available with -std=c++11 or -std=gnu++11
Duration& operator=(const Duration&) = default;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:55:17: error: ‘chrono’ in namespace ‘std’ does not name a type
operator std::chrono::duration<uint64_t, std::milli>() const noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:62:18: error: expected ‘;’ at end of member declaration
double toSec() const noexcept;
^
/opt/ros/kinetic/include/libfranka/franka/duration.h:62:24: error: ‘noexcept’ does not name a type
double toSec() const noexcept;
^
it seems that some erros in head files in libfranka, but i don't know how to solve this error. can anyone give me a hand? thank you in advance.

Solved in community: https://www.franka-community.de/t/problem-at-catkin-make-of-my-cpp-file-with-franka-ros-and-libfranka/1159/3


MAINT: Pin our github actions to minor versions

This pins our github actions to minor versions, rather than patch versions, simulating the ~= syntax we follow for Python dependencies.

not sure why some actions don't let you pin just to minor versions, but github actions is unhappy and I don't have time to debug this since it's not easy, so just gonna close this


Attachments can now be downloaded

resolve #331

@wongband Yes, please make it so it saves the attachment instead of opening it on the page.

I will change that right away

I believe you can just add download to the <a> tag and that'll do it

@wongband while @sprucely would work, I specifically didn't want to make the blob storage hardcoded to an attachment -- we don't know if that's how it should be used in all cases.  Try the download attribute first, and if that works it'll be the most flexible option.  If not then we can go with the other one.

@srkirkland download attribute does not work. Do i just changed blobContentDisposition: filename=${file.fileName}`` to  blobContentDisposition: attachment; filename=${file.fileName},

Thanks for checking, not sure why it doesn't work but yea just add that attachment; like you put there

If we don't go as a download, then at least open it up in a new tab in the browser.

When I change it to attachment; filename=${file.fileName} and I click on the file it does not download it still opens the attachment

Did you try uploading a new file? It's metadata that gets saved with the blob, so previous uploads will not have it.

Or just add this to the a tag target="_blank" rel="noreferrer"

@sprucely I think we want all the attachments to be downloadable and not just the the uploaded ones

@wongband It's not in production yet, so with that attachment; disposition being applied from the beginning, they would all be downloadable.

Yeah, adding that to the fileupload.tsx worked for me.

@sprucely ohh okay I see. Should I keep the attachment there or do what @jSylvestre with the blank? That method works as well

@wongband I'd say just go with the blank for now to it opens in a new tab. If we decide we want to force a download for some of these in the future we can modify the upload for those cases.

Adding the blank to the a tag allows the document to be downloaded. Is this fine as well?

@jSylvestre check it again. It should be fixed with that last push


Update web3.py examples across documentation

I noticed some examples for web3.py were not up-to-date. I tried to check against all examples and did my best to update them as per web3.py >= v6.0.0.

@lucemans I re-structured my original PR to reflect against the docs refactor. Should be ready for a review. Not sure how your svg / icon management works but we can submit one as well where appropriate.


Welcome page - accidental signup message

Need to implement a delete feature as per the request here:

... such a message upon creating a new account would be extremely helpful. IMHO the copy should be:
"Welcome to your brand new freeCodeCamp account. Let's get started. (If you meant to sign into an existing account instead of creating this account, click here to delete this account and try another email address.)"
Desired functionality upon clicking that link: delete the account, and redirect people back to the signin page.

Main Goals:

[ ] Update the copy on the welcome page for new user sign-ups.
[ ] Implement a delete and redirect to the sign-in page.

Originally posted by @QuincyLarson in https://github.com/freeCodeCamp/auth0-config/issues/41#issuecomment-1540553639

I am happy for this feature to be implemented.
However, do we have a reason (link to discussion) for not going with:

Two buttons

Sign-in and Sign-up

Click Sign-in

If account exists, no problem
If account not found, show error (ENOENT)

Click Sign-up

If account exists, no problem
If account not found, create account

See: https://chat.freecodecamp.org/group/staff?msg=2tbXD4dX5NuMFC6wG


CRAYSAT-1512: cf-gitea-import enhancements

Summary and Scope

Fix a bug that was preventing cf-gitea-import from working when the value of CF_IMPORT_GITEA_URL had trailing components, e.g. "https://api-gw-service-nmn.local/vcs", caused by a slightly incorrect use of urljoin.
Add an alternate entrypoint that does not wait on the Envoy sidecar proxy to be available, which allows cf-gitea-import to be run directly via podman, if a product install mounts the ansible content to import.
This change does not change the default entrypoint and the image continues to work in the "old" way, in which a product-specific image is derived from cf-gitea-import.

Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CRAYSAT-1512

Testing
Tested on:

groot

Test description:

Built the image.
Built a version of sat-cfs-install derived from this image, and used
a loftsman manifest and helm chart to import a version of SAT
configuration.
Built a version of the product stream with this image, Ran cf-gitea-import
directly using podman, mounting in a version of SAT configuration
over /content.

Risks and Mitigations
N/A
Pull Request Checklist

[X] Target branch correct
[X] Testing is appropriate and complete, if applicable
[X] Is a new version being released? Update https://github.com/Cray-HPE/cf-gitea-import/wiki/CSM-Compatibility-Matrix
[X] HPC Product Announcement prepared, if applicable

It would be ideal if we could merge these couple first:
https://github.com/Cray-HPE/cf-gitea-import/pull/45
https://github.com/Cray-HPE/cf-gitea-import/pull/39

https://github.com/Cray-HPE/cf-gitea-import/pull/46#pullrequestreview-1065690024 - I reworded the commit message to describe both cases, i.e. both urljoin('https://foo.com/bar', '/baz') and urljoin('https://foo.com/bar', 'baz') returning 'https://foo.com/baz'.


build: bump docker-compose to v2.24.5

The Issue
It's time to update docker-compose.
The most significant change in v2.24.0:
Breaking change ⚠
service hash computation logic has been updated to fully ignore replicas/scale. Due to this change, after upgrade all services will be recreated.

The new docker-compose has new aggressive checks, tests are failing:
can't set healthcheck.start_interval as feature require Docker Engine v25 or later

Related issue:

https://github.com/docker-library/docker/issues/473

Pretty weird! Nice job chasing it. But it needs to be fixed somewhere or we're stuck with old compose. Seems like compose bug.

Yes, I will see what can be changed.

I'd sure rather it be fixed in docker-compose.

I think they made a reasonable change with error, because healthcheck.start_interval didn't work before Docker v25 and should be considered an invalid option.

it does look fragile for the future

Agree, and for this reason I added a check specifically for the Docker API version https://docs.docker.com/engine/api/#api-version-matrix
This API version (e.g. 1.44) is much more stable than the Docker version (e.g. 25.0.1). The same comparison is used inside docker-compose.

Looking deeper into the code base, there is a check for the minimum version of Docker to use with DDEV:
https://github.com/ddev/ddev/blob/2defedb31dd103d945fac90f260909796a0a5dc0/pkg/dockerutil/dockerutils.go#L1733-L1739
And it does some exotic things in comparison, like removing _ce for OpenSUSE (they add this suffix to the version):
https://github.com/ddev/ddev/blob/2defedb31dd103d945fac90f260909796a0a5dc0/pkg/dockerutil/dockerutils.go#L772-L783
From what I can see, people who build Docker can override the Docker version as they wish, for example from the Arch package (people can set any VERSION env they want when building):
https://gitlab.archlinux.org/archlinux/packaging/packages/docker/-/blob/381210628f4f895b2cee908ffa1179f7ff1150d4/PKGBUILD#L87-94
I would rather set the minimum API version to use with DDEV - this value is set and controlled only by Docker.
@rfay, what do you think about this? (Of course, this is beyond the scope of this PR, and can be done in a new PR).

API version sounds like a fine thing to me.
In general, we've been trying to support as much as we can all the time, and been pretty successful with it over the long term.

I've updated the PR description with more information about the changes made, it should be fine to merge.

I'll try to manually test. Looks good to me also.

I guess my major worry would be that since healthcheck.start_interval was previously ignored, it not being ignored when using Docker v25 might cause some new issues.


dd: does not handle lots of rapid SIGUSR1 signals with large block writes

In the GNU test suite tests/dd/stats.sh checks that dd reports transfer statistics correctly when it receives the signal SIGUSR1. This is tested by starting a dd process that writes a lot of zeros to a named pipe, starting another process that reads from that named pipe, and then sending a bunch of SIGUSR1 signals to the dd process to force it to report progress. Unfortunately, uutils dd fails to write all the bytes to the named pipe.
In summary, the dd process is invoked as
dd iflag=fullblock if=/dev/zero of=fifo count=50 bs=5000000 2>err & pid=$!

and the SIGUSR1 signals are produced via
  until ! kill -s USR1 $pid 2>/dev/null; do
    sleep .01
  done

When using coreutils dd, this results in a predictable sequence of progress reports, one for each signal:
# ...
6+0 records in
5+0 records out
25000000 bytes (25 MB, 24 MiB) copied, 0.0387354 s, 645 MB/s
8+0 records in
7+0 records out
35000000 bytes (35 MB, 33 MiB) copied, 0.0535897 s, 653 MB/s
11+0 records in
10+0 records out
50000000 bytes (50 MB, 48 MiB) copied, 0.0688566 s, 726 MB/s
# ...

But for uutils dd (on my machine anyway), the signals do not result in a progress report (or they are not handled quickly enough? I'm not sure).
Additionally, the final progress report indicates that some blocks were only partially written to the named pipe:
50+0 records in
42+8 records out
224286848 bytes (224 MB, 214 MiB) copied, 0.0989137 s, 2.3 GB/s

but we expected
50+0 records in
50+0 records out
250000000 bytes (250 MB, 238 MiB) copied, 0.314097 s, 796 MB/s

Maybe the same underlying issue as #3042?

I worked on the topic in  #6025. Sadly the menioned GNU test is still not green. There seems to be more than just this.

Update: I added an additional fix there. The relevant GNU test is green now.

I think this was fixed by #6025?


tox config is broken

Failures noticed in #336 and #337.
From http://tox.readthedocs.org/en/latest/changelog.html it looks like the 2.2.1 release notes explain the failure

fix bug where {envdir} substitution could not be used in setenv if that env value is then used in {basepython}. Thanks Florian Bruhin.

Seems https://bitbucket.org/hpk42/tox/pull-requests/169/tries-to-fix-99/diff is the PR that fixed something but broke us

I should add that the offending line is
https://github.com/google/oauth2client/blob/311a53fbcae550526a74057f27cb9df73a0af009/tox.ini#L86-L87
and the issue is a circular reference between setenv and the use of env:KEY:DEFAULT.

@jonparrott Any idea on how to fix this? (I did the "cowardly" thing and downgraded tox temporarily.)

I accidentally stumbled on something which I think/hope will solve this:
https://github.com/GoogleCloudPlatform/gcloud-python/pull/1237

All I've got is to just wait. We ended up pinning tox in python-docs-samples as well.
Consider tox isn't a direct dependency of library, pinning it for a while doesn't seem too offensive.

I don't think waiting will work. I think we are permanently broken. I tried making the change suggested by my other PR and get a circular dependency sort of error:
...
  File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 959, in _replace_substitution
    val = self._substitute_from_other_section(sub_key)
  File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 944, in _substitute_from_other_section
    (section, item), self._subststack))
ValueError: ('testenv', 'gae_pythonpath') already in [('testenv:gae', 'setenv'), ('testenv', 'gae_pythonpath'), ('testenv:gae', 'setenv')]

It seems like it is getting a self-reference and it will "always" be impossible for setenv and env to coexist.

@waprin who's more involved in the testing side than me.

@jonparrott By forcing me to articulate that

it will "always" be impossible for setenv and env to coexist.

I realized we could just ditch setenv in testenv:gae. w00t!

Haha JK:
gae runtests: commands[0] | PYTHONPATH= nosetests --with-gae --gae-application=tests/data --logging-level=INFO tests/test_appengine.py
ERROR: InvocationError: could not find executable 'PYTHONPATH='

It's a bug a lot of people are experiencing, people already have PRs to fix it, they are just in the process of getting vetted/merged:
https://bitbucket.org/hpk42/tox/issues/285/tox-220-breaks-some-toxini-config-files

w00t. Thanks @waprin

This is no longer broken right?


Prepare for scpca-docs release: New age columns

Steps for a new release of scpca-docs

This should include updates for the age columns - age and age_timing.
Preparing for the release

[x] Does this release require an update to the CHANGELOG because there will be changes to downloadable files? If so, please create an issue tracking the CHANGELOG update and mark it as blocking this issue.
[x] Are all other issues planned for this release resolved? If any issues are unresolved, mark this issue as blocked by those on ZenHub.
[x] Optional: If not all changes in development are ready to be released, create a feature branch off main and cherry pick commits from development to that feature branch.
[x] File a PR from the development branch (or the new feature branch) to the main branch. This should include all of the changes that will be associated with the next release.

[x] If a CHANGELOG entry was required, add the date to the entry's header as part of this PR.

Creating a release

[x] On the releases page, choose Draft a new release.
[x] In Choose a tag, use the current date as the release tag (YYYY.MM.DD), then click Create a new tag: YYYY.MM.DD on publish.
[x] Write a description of the major changes in this release. You may want to start with the auto-generated release notes to save time.
[ ] Optional: If not all issues have been addressed, save a draft to return to later.
[x] Publish the release!

Done: https://github.com/AlexsLemonade/scpca-docs/releases/tag/2024.08.13


[FLINK-4197] Allow Kinesis endpoint to be overridden via config

I perform local testing of my application stack with Flink configured as a consumer on a Kinesis stream provided by Kinesalite, an implementation of Kinesis built on LevelDB. This requires me to override the AWS endpoint to refer to my local Kinesalite server rather than reference the real AWS endpoint. I'd like to add a configuration property to the Kinesis streaming connector that allows the AWS endpoint to be specified explicitly.
This should be a fairly small change and provide a lot of flexibility to people looking to integrate Flink with Kinesis in a non-production setup.

Thank you for opening a PR for this @skidder ! I'll review the changes soon.

Hi @skidder, I like the add, I think serious users will definitely need this.
One thing I'm concerned about is how CONFIG_AWS_REGION and CONFIG_AWS_ENDPOINT should co-exist in the configuration properties, especially when we validate the configuration with KinesisConfigUtil#validateConfiguration().
The Kinesis consumer requires the user to specify CONFIG_AWS_REGION.
I wonder if we need to check for conflicting CONFIG_AWS_REGION and CONFIG_AWS_ENDPOINT values, i.e.region is set to "us-east-1", but endpoint is set to "ap-northeast-1.amazonaws.com".
Also,
What do you think?

Thanks for the comment, @tzulitai !
I have not had any problems with testing Flink against a local Kinesalite instance where the Region (required by Flink) is set to us-east-1 and the endpoint is set to an address on localhost. The setRegion function on the AWS Kinesis client calculates the endpoint URL from the region name and sets it on the client. The setEndpoint function is meant to allow for testing against non-AWS endpoints, or even new AWS endpoints in Regions unrecognized by an older version of the library.
I think that requiring the AWS region, and optionally using the AWS endpoint if provided, will work well; this is consistent with the AWS client's own behavior.

@skidder I see, thank you for your explanation. If it's a familiar behavior (with respect to AWS / Kinesis users) to completely override the region when setting the endpoint regardless of the original value, then I think it's ok.
Can you also add information about the overriding behaviour in the Kinesis connector documentation (can be found at flink/docs/api/streaming/connectors/kinesis.md)? I think it'll be good to have this explained.

@tzulitai definitely, I'll add an explanation of the config setting in the docs shortly.

@skidder Thank you for the quick responses & fixes!
@rmetzger Can you also have a look through the changes & the comment on the Kinesalite referencing? Will also need help on the final merging, the changes LGTM, after comments are addressed. Thank you!

Looks good to merge.
Waiting for the tests to pass, then merging (probably tomorrow).


PUT dont set "Transfer-Encoding" but send chucked data

Hi,
I testing our new s3 compatible storadge.
The PUT test passes, but the GET does not.
I checked what Wasp was sending. It sends data in chunks, but does not set the appropriate header, so the data size does not match the expected one.
PUT /warp-benchmark-bucket/OdrYKa9t/1.aXrdRlomKVEntzRL.rnd HTTP/1.1
Host: 10.197.XX.XX:8084
User-Agent: MinIO (linux; amd64) minio-go/v7.0.49 warp/0.6.7
Content-Length: 128265
Authorization: AWS4-HMAC-SHA256 Credential=FhS8yEmUkfyX2q8qG1CWo1V996h8PxySc3vjUe2xcMm805NZL3twBNLRkU64jXrJkgZhSMjGSprL5AvYjSTY86asr/20230407/default/s3/aws4_request,SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-decoded-content-length,Signature=8e2b4193e420fd03adf0278693e4916f329e796038eca3cebc533f8b6ae54453
Content-Type: application/octet-stream
X-Amz-Content-Sha256: STREAMING-AWS4-HMAC-SHA256-PAYLOAD
X-Amz-Date: 20230407T110527Z
X-Amz-Decoded-Content-Length: 128000

14:05:27.740648 IP 10.XX.XX.XX.49366 > 10.197.XX.XX.8084: Flags [.], seq 2268:3716, ack 904, win 254, options [nop,nop,TS val 89444189 ecr<PHONE_NUMBER>], length 1448
E...j<EMAIL_ADDRESS>L.!
.......Wy.2...|...........
.T.]W...10000;chunk-signature=b523a26f4b1f0a06357475c8d3defe3707178e7aa5a16719fc821c9452ec76b5

Seems like AWS doesn't care. But adding it, since it should be there. See #1803

Hi,
It didn't help.
I rebuild WARP with monio-go/v7.0.51
But "PUT" sends data in chunks and does not set the header "Transfer-Encoding:".

@greenx Are you sure this isn't just because it isn't printed? Did you confirm this on the sever side?

@klauspost Go removes tranfer-encoding in the http dump of the request.
I think the server implementation is wrong here.

There is a "content-length" in the headers, but the message body is transmitted in chunks, without the "transfer-encoding" header.
https://www.rfc-editor.org/rfc/rfc9112#section-6.2

@greenx this is actually normal for this operation. The main reason is that content-length is automatically added via Go's net/http. Which looks at our input buffer to see what is the size and then automatically sets it.
That seems to invalidate the value set at req.TransferEncoding - it requires a bit of a refactor and touching some old code.
I would carefully do it if we must fix this. Since this works with MinIO and AWS our current priorities are really kind of met - it would seem like no other S3 vendor has complained either.
Unless I am mistaken at this point server should honor what AWS S3 honors, i.e allow chunked transfer via Content-Length being set.
Just treat it as chunked via x-amz-signature-algorithm - that calls it as Streaming!

Hmmm, Judging by this,
https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html
AWS just scored on the RFC.

 I will look a bit deeper into it.

Observed against storage.googleapis.com
v7.0.57 works fine, but v7.0.70 on getting file returns something like
10000;chunk-signature=fce2a10afb7ceaecfcb0010dbc5eb2dd02d4221228c3a555faf686d49f1274d8\r\n...original_data

It's funny - on our project we replaced github.com/minio/minio-go/v7 with github.com/aws/aws-sdk-go-v2 to continue working with GCP storage which doesn't support proper AWS S3 semantics.

BTW GCP is working for us with v7.0.61 (even with SignatureV2) but not with v7.0.62,
where SignatureV2 was replaced with SignatureV4 for GCP (which uses StreamingSignV4) in the PR #1870.
But with latest minio-go (48517d8) finally I got it working with change our code
like this (added TrailingHeaders: false and DisableContentSha256: true)
func NewBucket(cfg *BucketCfg) (*bucket, error) {
	client, err := minio.New(cfg.Endpoint, &minio.Options{
		Creds:  credentials.NewStaticV4(cfg.AccessKeyID, cfg.SecretAccessKey, ""),
		Secure: false, TrailingHeaders: false,
	})
	return &bucket{client: client, bucketName: cfg.BucketName}, err
}

func (b *bucket) PutData(ctx context.Context, data []byte, path, mime string) error {
	size := len(data)
	_, err := b.client.PutObject(ctx, b.bucketName, path, bytes.NewReader(data),
		int64(size), minio.PutObjectOptions{ContentType: mime, DisableContentSha256: true})
	return err
}


Missing documentation

I found that the following methods were not documented:

docma.utils.listType
docma.utils.listTypeDesc

Since there are used in the default template's filters ($returns, $extends, $exceptions) I think it would be a good idea to add them.

Those are left out on purpose. I'll check if they're ok for general use and add if ok.

These are now included but for semantics, they are refactored in v2 as below:

docma.utils.listType() refactored to docma.utils.getCodeTags()
docma.utils.listTypeDesc refactored to docma.utils.getFormattedTypeList()

Each now has additional arguments for format options.


[SLM] Introduce microsoft/Phi-3

Introduce microsoft/Phi-3 from https://huggingface.co/microsoft/Phi-3-mini-4k-instruct
cc. @CharlieFRuan @MasterJH5574  @tqchen

Why did this pull request fail?

waiting

waiting

How will existing Android users be able to use it? Reinstall existing Android app or can we refresh the list of existing models?

Hi @moondiy @sebastienbo, our prebuilt package should be able to contain this commit tomorrow. We will work on uploading prebuilt model weights to our huggingface and also the android app update. Will report back regarding the progress.

I see there are chunks available for Phi 3:
https://huggingface.co/mlc-ai/Phi-3-mini-4k-instruct-q4f16_2-MLC/tree/main
.. but I couldn't find a corresponding .wasm file (yet)?
https://github.com/mlc-ai/binary-mlc-llm-libs

Thanks. So we just download a new APK?
On Wed, 8 May 2024, 01:37 Ruihang Lai, @.***> wrote:

Hi @moondiy https://github.com/moondiy @sebastienbo
https://github.com/sebastienbo, our prebuilt package should be able to
contain this commit tomorrow. We will work on uploading prebuilt model
weights to our huggingface and also the android app update. Will report
back regarding the progress.
—
Reply to this email directly, view it on GitHub
https://github.com/mlc-ai/mlc-llm/pull/2222#issuecomment-2099476972, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7MPQSRE3CQD4ZR7OX5SXLZBFQSFAVCNFSM6AAAAABGZM7V4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZGQ3TMOJXGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Settings File

The Settings file is stored internally in .exe
relocate that!

Settings are stored at
%appdata%\porphystruct\settings.json
in upcoming 1.0.0 release


Terraform changes to get access token via client credentials

pls also run, go generate ./... in project root dir, documentation files need update


⚠ BeyondHD has degraded performance

In 14eebe0, BeyondHD ($BHD) experienced degraded performance:

HTTP code: 200
Response time: 2144 ms

Resolved: BeyondHD performance has improved in 0fadaf6.


feat: add mutating FunctionDefinition functions

Description
Problem
Part of #5668
Summary
Additional Context
I think we are missing a FunctionDefinition::body, but that could come later.
I had to get a FuncMeta many times in some functions because Rust wouldn't let me get two mutable borrows of interner.
Generics handling is missing... but I think right now generics can't appear in these functions, as attributes only run on top-level functions, not on impl or trait impl functions, but let me know if this is not the case.
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Generics handling is missing... but I think right now generics can't appear in these functions, as attributes only run on top-level functions, not on impl or trait impl functions, but let me know if this is not the case.

Top-level functions can still have generics:
fn length_times_two<T, let N: u32>(array: [T; N]) -> u32 {
    array.len() * 2
}

Regarding generics, I wanted to add a test to prove that it works with generics, something like:
#[mutate_generic]
fn identity<T>() {}

comptime fn mutate_generic(f: FunctionDefinition) {
  // I want to change f to be `fn identity<T>(x: T) -> T { x }`
  f.set_parameters(&[quote { x }, ???]); // what type can I pass here?

Is this PR ready for review again? It is hard for me to tell because of the force push but I see all the comments are resolved

Oh, yes, it is, sorry! Next time I'll ask for a re-review after pushing several commits.
I'll fix the conflicts now.

Can you avoid force pushes after a review has been done in the future? It makes it a bit more difficult to review since I can't see changes since the last review any more and need to start over.

Sounds good!
I did a force push because we use squash-merge and this PR was on top of another PR. When the first PR merged, doing git merge gives conflicts. I found a simpler way to do that by using git rebase --onto to remove the extra commits. Is there another way to do this merge in a simpler way?

(the conflicts are easy to solve, just always "keep mine", but it's a bit annoying to do it all the time for every stacked PR, so I wonder how you all deal with this)

@asterite usually when this happens I just go through the conflicts and "keep mine" or fix them in the case there are changes (e.g. changes requested from the previous PR).


🍒 Cherry pick PR #5330 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/5330 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.0.99-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.


Add **kwargs to functions that return a builder + remove shebang

Adding **kwargs is useful when a build script needs to pass non-standard arguments to the constructor of ConanMultiPackager.
For example: https://github.com/bincrafters/conan-flex/pull/4#issuecomment-465173462

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #19   +/-   ##
=======================================
  Coverage   98.63%   98.63%
=======================================
  Files           8        8
  Lines         146      146
=======================================
  Hits          144      144
  Misses          2        2

Impacted Files
Coverage Δ

bincrafters/build_template_boost_default.py
100% <ø> (ø)
:arrow_up:

bincrafters/build_template_boost_header_only.py
100% <ø> (ø)
:arrow_up:

bincrafters/build_template_default.py
100% <ø> (ø)
:arrow_up:

bincrafters/build_template_header_only.py
100% <ø> (ø)
:arrow_up:

bincrafters/build_shared.py
98.13% <ø> (ø)
:arrow_up:

bincrafters/__init__.py
100% <ø> (ø)
:arrow_up:

bincrafters/build_paths.py
100% <ø> (ø)
:arrow_up:

bincrafters/build_template_installer.py
100% <ø> (ø)
: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 e50bb7f...b9678db. Read the comment docs.

@uilianries any ideas on this error?
3.7 is not installed; attempting download
Downloading archive: https://travis-ci-python-archives.global.ssl.fastly.net/binaries/ubuntu/14.04/x86_64/python-3.7.tar.bz2
0.21s$ curl -sSf -o python-3.7.tar.bz2 ${archive_url}
curl: (22) The requested URL returned error: 403 Forbidden
Unable to download 3.7 archive. The archive may not exist. Please consider a different version.

@uilianries ping :)

@SSE4 I can't download python 2.7 too
wget https://travis-ci-python-archives.global.ssl.fastly.net/binaries/ubuntu/14.04/x86_64/python-3.7.tar.bz2
--2019-03-14 08:20:03--  https://travis-ci-python-archives.global.ssl.fastly.net/binaries/ubuntu/14.04/x86_64/python-3.7.tar.bz2
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving travis-ci-python-archives.global.ssl.fastly.net (travis-ci-python-archives.global.ssl.fastly.net)... <IP_ADDRESS>
Connecting to travis-ci-python-archives.global.ssl.fastly.net (travis-ci-python-archives.global.ssl.fastly.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2019-03-14 08:20:04 ERROR 403: Forbidden.

I think Travis is not totally recovered from yesterday. But there is no error message on https://www.traviscistatus.com/
I'll send an email relating this error.

I sent the email. Let's wait for an answer.

That's weird, Python 3.7 is listed in the documentation. Also, I can download both python-3.6 and python-3.7-dev

Maybe the missing dist option?

@madebr Yes, it makes sense.

done! I just included the linux distro. Let's wait for the CI result.

Is this a go then?

@madebr merged! Thanks! I gonna release a new version soon

Done: https://github.com/bincrafters/bincrafters-package-tools/releases/tag/0.17.10
Let's wait the new release on Pypi

@uilianries pypi is still at 0.17.9
See https://pypi.org/project/bincrafters-package-tools/

lemme check what happened

@madebr Fixed, but need to wait for CI job:
https://travis-ci.com/bincrafters/bincrafters-package-tools/jobs/186758624
Thanks for reporting!

Done!
https://pypi.org/project/bincrafters-package-tools/0.17.10/


plotly 3.0 causes warnings

When using the plotly 3.0, the below warnings show up after importing cufflinks.
Would be good to update the code by avoiding the deprecated methods.
/Users/gshalev/.pyenv/versions/3.6.2/lib/python3.6/site-packages/plotly/graph_objs/_deprecations.py:558: DeprecationWarning:

plotly.graph_objs.YAxis is deprecated.
Please replace it with one of the following more specific types
  - plotly.graph_objs.layout.YAxis
  - plotly.graph_objs.layout.scene.YAxis

/Users/gshalev/.pyenv/versions/3.6.2/lib/python3.6/site-packages/plotly/graph_objs/_deprecations.py:531: DeprecationWarning:

plotly.graph_objs.XAxis is deprecated.
Please replace it with one of the following more specific types
  - plotly.graph_objs.layout.XAxis
  - plotly.graph_objs.layout.scene.XAxis

Hello,
A quick search into the cufflinks repo yield only two files:

cufflinks/themes.py
cufflinks/tools.py

I'm working on a quick PR.

Haven't looked into detail, but there might be more fixes required, getting this after a df.iplot():
ValueError:
    Invalid value of type 'builtins.str' received for the 'bgcolor' property of layout.legend
        Received value: 'pearl02'

Just to give more feedback:
When I run
df.iplot(kind='area',fill=True)
I get also an ValueError:
ValueError:      Invalid value of type 'builtins.str' received for the 'color' property of layout.legend.font         Received value: 'grey10'

I've had similar issues too with plotly 3.0.0 and cufflinks (fails when I do import cufflinks)

@ah- you might be right
After replacing by the go.layout.XAxis and go.layout.YAxis and testing the errors are due to color naming.
Instead of passing the corresponding hex string from the cnames dict from cufflinks/cufflinks/colors.py, cufflinks passes the color name directly to plotly.graph_objs.layout.YAxis, resulting in ValueError
Usually cufflinks.tools will convert to RGBA/hex string using the to_rgba function, but since it imports THEMES first, it passes the YAxis/XAxis with invalid colors.
A clunky fix would to convert all the colors in THEMES to its hex string equivalent, but I still don't really know why there is suddenly this problem with colors... 🤔

I think it's a new feature, read about it in https://medium.com/@plotlygraphs/introducing-plotly-py-3-0-0-7bb1333f69c6, see "Deep Validation and Helpful Error Messages".

Same ValueError, cufflinks (<=git:master) not usable with plotly 3.0+
Maybe we should open a new issue as this is different from the OP Warning?

Hello everyone, I think that this change causes the issue:
https://github.com/plotly/plotly.py/blob/master/migration-guide.md#object-array-classes-deprecated

my quick fix was to downgrade to plotly 2.0.0 for the time being
pip uninstall plotly
pip install plotly==2.0.0

@DiegoAgher , Plotly==2.7.0 is working just fine since Plotly uses the  Semantic Versioning 🙂 (and I tested it)

Looking a little closer, this is going to be a fairly painful migration.

getting started on #122

Yikes. This looks like a painful one. Thank you @timkpaine. Let’s get on it.

Uninstall version 3.0 and install version 2.7.0. Worked for me.
in anaconda prompt:>  pip install plotly==2.7.0

Hi all, I just came across this thread. Let me know if you have any questions about migration.
Also, one option that may (or may not) be easier for you would be to replace all of the former graph objects (go.Scatter, etc.) with raw dictionaries\lists and then only build a go.Figure object at the very end of the construction process. This would delay validation until the end of the process (after you've replaced the colors etc.) and would be backwards compatible with version 2.7.

This warning seems to have been resolved in Plotly 3.1.0. Try upgrading to this version and verify.

Just came across this thread.
Using Plotly 3.1.0, I had the same value error as ah- commented, however, after upgrading to 3.1.1 I no longer get it.
In both versions, I still get the original warnings described by OP.

Unfortunately, cufflinks 0.13.0 with Plotly 3.1.1 throws the same error:

/opt/conda/lib/python3.6/site-packages/plotly/graph_objs/_deprecations.py:558: DeprecationWarning:
plotly.graph_objs.YAxis is deprecated.
Please replace it with one of the following more specific types

plotly.graph_objs.layout.YAxis
plotly.graph_objs.layout.scene.YAxis

/opt/conda/lib/python3.6/site-packages/plotly/graph_objs/_deprecations.py:531: DeprecationWarning:
plotly.graph_objs.XAxis is deprecated.
Please replace it with one of the following more specific types

plotly.graph_objs.layout.XAxis
plotly.graph_objs.layout.scene.XAxis

I'm having the same issue, although I also get the following error following the warnings when I import cufflinks:
  File "/opt/custard/git/adhoc/adhoc/air_metrics.py", line 5, in <module>
    import cufflinks as cf
  File "/home/custard/.local/lib/python2.7/site-packages/cufflinks/__init__.py", line 15, in <module>
    from . import tools
  File "/home/custard/.local/lib/python2.7/site-packages/cufflinks/tools.py", line 37, in <module>
    __LAYOUT_AXIS_X=['xaxis_'+_ for _ in go.XAxis().__dir__()]
AttributeError: 'XAxis' object has no attribute '__dir__'

I've created a plotly3 branch to start testing all the fixes (lot of changes).

Done.
**Thank you @timkpaine ** for the help.

Hi All,  did this issues solved?  I updated the latest plotly and got the same error again.  What should I do?
Thanks,
Tim

I am also on latest plotly and it works fine. Can you send a repro and info about your environment (python and plotly/cufflinks versions)

Sorry I forget to post the errors which is as follows:
ValueError                                Traceback (most recent call last)
 in ()
21             color = 'colors[i-6]',
22             opacity = .4,
---> 23             line = dict(width = 0)
24         ),
25     ) )
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\graph_objs_scattergeo.py in init(self, arg, connectgaps, customdata, customdatasrc, fill, fillcolor, geo, hoverinfo, hoverinfosrc, hoverlabel, hovertext, hovertextsrc, ids, idssrc, lat, latsrc, legendgroup, line, locationmode, locations, locationssrc, lon, lonsrc, marker, mode, name, opacity, selected, selectedpoints, showlegend, stream, text, textfont, textposition, textpositionsrc, textsrc, uid, unselected, visible, **kwargs)
1553         self.lonsrc = lonsrc if lonsrc is not None else _v
1554         _v = arg.pop('marker', None)
-> 1555         self.marker = marker if marker is not None else _v
1556         _v = arg.pop('mode', None)
1557         self.mode = mode if mode is not None else _v
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\basedatatypes.py in setattr(self, prop, value)
2702                 prop in self._validators):
2703             # Let known properties and private properties through
-> 2704             super(BasePlotlyType, self).setattr(prop, value)
2705         else:
2706             # Raise error on unknown public properties
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\graph_objs_scattergeo.py in marker(self, val)
693     @marker.setter
694     def marker(self, val):
--> 695         self['marker'] = val
696
697     # mode
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\basedatatypes.py in setitem(self, prop, value)
2665             # ### Handle compound property ###
2666             if isinstance(validator, CompoundValidator):
-> 2667                 self._set_compound_prop(prop, value)
2668
2669             # ### Handle compound array property ###
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\basedatatypes.py in _set_compound_prop(self, prop, val)
2963         validator = self._validators.get(prop)
2964         # type: BasePlotlyType
-> 2965         val = validator.validate_coerce(val)
2966
2967         # Save deep copies of current and new states
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages_plotly_utils\basevalidators.py in validate_coerce(self, v)
1875
1876         elif isinstance(v, dict):
-> 1877             v = self.data_class(**v)
1878
1879         elif isinstance(v, self.data_class):
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\graph_objs\scattergeo_marker.py in init(self, arg, autocolorscale, cauto, cmax, cmin, color, colorbar, colorscale, colorsrc, gradient, line, opacity, opacitysrc, reversescale, showscale, size, sizemin, sizemode, sizeref, sizesrc, symbol, symbolsrc, **kwargs)
1175         self.cmin = cmin if cmin is not None else _v
1176         _v = arg.pop('color', None)
-> 1177         self.color = color if color is not None else _v
1178         _v = arg.pop('colorbar', None)
1179         self.colorbar = colorbar if colorbar is not None else _v
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\basedatatypes.py in setattr(self, prop, value)
2702                 prop in self._validators):
2703             # Let known properties and private properties through
-> 2704             super(BasePlotlyType, self).setattr(prop, value)
2705         else:
2706             # Raise error on unknown public properties
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\graph_objs\scattergeo_marker.py in color(self, val)
165     @color.setter
166     def color(self, val):
--> 167         self['color'] = val
168
169     # colorbar
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\basedatatypes.py in setitem(self, prop, value)
2674             # ### Handle simple property ###
2675             else:
-> 2676                 self._set_prop(prop, value)
2677
2678         # Handle non-scalar case
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages\plotly\basedatatypes.py in _set_prop(self, prop, val)
2904         # ------------
2905         validator = self._validators.get(prop)
-> 2906         val = validator.validate_coerce(val)
2907
2908         # val is None
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages_plotly_utils\basevalidators.py in validate_coerce(self, v, should_raise)
1077             validated_v = self.vc_scalar(v)
1078             if validated_v is None and should_raise:
-> 1079                 self.raise_invalid_val(v)
1080
1081             v = validated_v
c:\users\leirhyh\appdata\local\programs\python\python37-32\lib\site-packages_plotly_utils\basevalidators.py in raise_invalid_val(self, v)
223             typ=type_str(v),
224             v=repr(v),
--> 225             valid_clr_desc=self.description()))
226
227     def raise_invalid_elements(self, invalid_els):
ValueError:
Invalid value of type 'builtins.str' received for the 'color' property of scattergeo.marker
Received value: 'colors[i-6]'
The 'color' property is a color and may be specified as:
  - A hex string (e.g. '#ff0000')
  - An rgb/rgba string (e.g. 'rgb(255,0,0)')
  - An hsl/hsla string (e.g. 'hsl(0,100%,50%)')
  - An hsv/hsva string (e.g. 'hsv(0,100%,100%)')
  - A named CSS color:
        aliceblue, antiquewhite, aqua, aquamarine, azure,
        beige, bisque, black, blanchedalmond, blue,
        blueviolet, brown, burlywood, cadetblue,
        chartreuse, chocolate, coral, cornflowerblue,
        cornsilk, crimson, cyan, darkblue, darkcyan,
        darkgoldenrod, darkgray, darkgrey, darkgreen,
        darkkhaki, darkmagenta, darkolivegreen, darkorange,
        darkorchid, darkred, darksalmon, darkseagreen,
        darkslateblue, darkslategray, darkslategrey,
        darkturquoise, darkviolet, deeppink, deepskyblue,
        dimgray, dimgrey, dodgerblue, firebrick,
        floralwhite, forestgreen, fuchsia, gainsboro,
        ghostwhite, gold, goldenrod, gray, grey, green,
        greenyellow, honeydew, hotpink, indianred, indigo,
        ivory, khaki, lavender, lavenderblush, lawngreen,
        lemonchiffon, lightblue, lightcoral, lightcyan,
        lightgoldenrodyellow, lightgray, lightgrey,
        lightgreen, lightpink, lightsalmon, lightseagreen,
        lightskyblue, lightslategray, lightslategrey,
        lightsteelblue, lightyellow, lime, limegreen,
        linen, magenta, maroon, mediumaquamarine,
        mediumblue, mediumorchid, mediumpurple,
        mediumseagreen, mediumslateblue, mediumspringgreen,
        mediumturquoise, mediumvioletred, midnightblue,
        mintcream, mistyrose, moccasin, navajowhite, navy,
        oldlace, olive, olivedrab, orange, orangered,
        orchid, palegoldenrod, palegreen, paleturquoise,
        palevioletred, papayawhip, peachpuff, peru, pink,
        plum, powderblue, purple, red, rosybrown,
        royalblue, saddlebrown, salmon, sandybrown,
        seagreen, seashell, sienna, silver, skyblue,
        slateblue, slategray, slategrey, snow, springgreen,
        steelblue, tan, teal, thistle, tomato, turquoise,
        violet, wheat, white, whitesmoke, yellow,
        yellowgreen
  - A number that will be interpreted as a color
    according to scattergeo.marker.colorscale
  - A list or array of any of the above

Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:06:47) [MSC v.1914 32 bit (Intel)] on win32
import plotly
plotly.version
'3.2.0'
import cufflinks
cufflinks.version
'0.13.0'

Thanks and I appreciate your time.
Tim

I get the same error with the same versions as @timkpaine .
Error :
ValueError:  Invalid value of type 'builtins.str' received for the 'bgcolor' property of layout.legend
Received value: 'pearl02'
O/S : Ubuntu 18.04
Python Version: 3.7.0 (default, Jun 28 2018, 19:31:47)
[GCC 7.3.0]
Plotly Version: 3.2.0
Cufflinks Version: 0.13.0
Repro (taken from the online example:)
import plotly
import cufflinks as cf
import sys
cf.set_config_file(offline=True)
print("Python Version: %s" % sys.version)
print("Plotly Version: %s" % plotly.version)
print("Cufflinks Version: %s" % cf.version)
iplot(cf.datagen.lines().iplot(asFigure=True,kind='scatter',xTitle='Dates',yTitle='Returns',title='Returns'))
Many thanks & appreciate your great efforts.
Andy

I can repro against pypi disted cufflinks, but not my source repo (which matches this repo). Can you try to pip install this git repo directly and see if it still happens?

yeah, what got disted is not whats on master, for sure

my code is ad following:
import plotly
import plotly.plotly as py
import plotly.graph_objs as go
plotly.offline.init_notebook_mode()
import pandas as pd
coords = pd.concat([housing['latitude'], housing['longitude'], housing['population']], axis=1)
coords = coords.sample(frac=0.1, replace=True)
cases = []
colors = ['rgb(239,243,255)','rgb(189,215,231)','rgb(107,174,214)','rgb(33,113,181)']
months = {6:'June',7:'July',8:'Aug',9:'Sept'}
for i in range(6,10)[::-1]:
cases.append(go.Scattergeo(
lon = coords['longitude'],
lat = coords['latitude'],
marker = dict(
size = coords['population']/1000,
color = 'colors[i-6]',
opacity = .4,
line = dict(width = 0)
),
) )
cases[0]['mode'] = 'markers'
layout = go.Layout(
title = 'Hey look! It's a scatter plot on a map!',
geo = dict(
resolution = 100,
scope = 'usa',
showframe = False,
showcoastlines = True,
showland = True,
landcolor = "rgb(229, 229, 229)",
countrycolor = "rgb(255, 255, 255)" ,
coastlinecolor = "rgb(255, 255, 255)",
projection = dict(
type = 'Mercator'
),
lonaxis = dict( range= [ -124.0, -113.0 ] ),
lataxis = dict( range= [ 32.0, 43.0 ] ),
),
legend = dict(
       traceorder = 'reversed'
)

)
fig = go.Figure(layout=layout, data=cases)
plotly.offline.iplot(fig, validate=False, filename='iantest')

@leirhyh72 please install 0.14

when I use pip install, it is 0.14,  do I need  to install from the source??

I mean 0.13, sorry

0.14 isn't disted to pypi yet:
pip install git+git://github.com/santosjorge/cufflinks.git#egg=cufflinks

Do I need to uninstall the 0.13 and try to install from source?  Thanks

read above

I did use "pip install git+git://github.com/santosjorge/cufflinks.git#egg=cufflinks"
but the version is still 0.13.  Don't know why.  I may uninstall all cufflinks if possible and reinstall it again.  What do you think?  Thanks, Tim

did it actually install? if you have an install you probably need -U

Hi Tim, after I add -U, 0.14 was successfully installed.  However, the same error appeared.  Don't know why.  Any input?  Thanks,  Tim

@leirhyh72 Are you using cufflinks within an iPython session or a Jupyter Notebook? You may need to restart your kernel to get it to work. I continued having the same error as you after install until I restarted my Jupyter notebook kernel.

Upgrading to 0.14.0 with
pip install git+git://github.com/santosjorge/cufflinks.git#egg=cufflinks -U
works. I am running Jupyter notebook on OSX.
I have struggled with this for the last couple of week. Thank you so much guys
import plotly
plotly.version
'3.2.0'
import cufflinks
cufflinks.version
'0.14.1'

I can confirm that this is now working properly for me with Plotly 3.2.1 and cufflinks 0.14.4. Thanks for all the hard work @santosjorge!  Not to bug you too much about it, but do you have plans to push this to PyPi soon?

@DavidJBianco when did you check for cufflinks 0.14.4?
It is listed at PyPi: https://pypi.org/project/cufflinks/

Sorry, you're correct. I had it installed from conda-forge, which isn't up-to-date.  Switching to the PyPi version was pretty simple.

Can confirm this error still is thrown under Plotly version 3.9.0   and cufflinks version 0.15.
How do we resolve this? (aside from downgrading from Plotly 3.9.0)

@cpoptic did you install from conda? the cufflinks version there is 0.13, where the current version is 0.15. Support for plotly 3.0 was added in version 0.14
check your version (cf.version)
upgrade using pip: pip install cufflinks --upgrade

@cpoptic are you certain you're running 0.15? I was running 0.13 when I hit it and upgrading certainly solved it for me..

Same error with plotly 3.9, but downgrading it to 3.7 does help.

3.9 with 0.13 was problematic for me. Upgrading cufflinks to 0.15 fixed the issue. FYI, the latest version on Conda is 0.13.

At the moment there is no official Conda repo. I think someone created one but not sure if it is being kept up to date. Better to always use PyPi.