No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20211027.vhd

Hi,
We are trying to build a image base on official image, and using the official published image from page https://help.aliyun.com/document_detail/100410.html
But we got the error "no matching image found". Please help on this. thanks!

+ packer build base.json
alicloud-ecs: output will be in this color.

==> alicloud-ecs: Prevalidating source region and copied regions...
==> alicloud-ecs: Prevalidating image name...
==> alicloud-ecs: No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20211027.vhd
Build 'alicloud-ecs' errored after 855 milliseconds 521 microseconds: No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20211027.vhd

==> Wait completed after 855 milliseconds 711 microseconds

==> Some builds didn't complete successfully and had errors:
--> alicloud-ecs: No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20211027.vhd

centos_7_9_x64_20G_alibase_20211027.vhd is not online in zhangjiakou, it will publish soon.

@alexyueer
Thanks for your quickly response,
I tried change to another one, but latest 4 images are NOT working.
and the centos_7_9_x64_20G_alibase_20210623.vhd is worked in Sep 2021. now it is also not working.
please suggest how can i proceed this? thanks in advance!

Got same error. No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20230815.vhd

Got same error. No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20230815.vhd
image exists by call DescribeImages.
{
  "TotalCount": 1,
  "PageSize": 10,
  "RequestId": "C0FD71A1-40EA-55DB-B965-DB3B96808F79",
  "PageNumber": 1,
  "Images": {
    "Image": [
      {
        "ImageOwnerAlias": "system",
        "Description": "Kernel version is 3.10.0-1160.92.1.el7.x86_64, 2023.8.17",
        "IsSelfShared": "",
        "Platform": "CentOS",
        "ResourceGroupId": "",
        "Size": 20,
        "IsSubscribed": false,
        "BootMode": "BIOS",
        "OSName": "CentOS  7.9 64位",
        "IsPublic": true,
        "ImageId": "centos_7_9_x64_20G_alibase_20230815.vhd",
        "DetectionOptions": {},
        "Features": {
          "NvmeSupport": "supported"
        },
        "OSNameEn": "CentOS  7.9 64 bit",
        "Tags": {
          "Tag": []
        },
        "LoginAsNonRootSupported": true,
        "Status": "Available",
        "Progress": "100%",
        "Usage": "instance",
        "Architecture": "x86_64",
        "ProductCode": "",
        "IsCopied": false,
        "ImageFamily": "acs:centos_7_9_x64",
        "IsSupportIoOptimized": true,
        "IsSupportCloudinit": true,
        "ImageName": "centos_7_9_x64_20G_alibase_20230815.vhd",
        "DiskDeviceMappings": {
          "DiskDeviceMapping": []
        },
        "ImageVersion": "v2023.8.17",
        "OSType": "linux",
        "CreationTime": "2023-08-24T07:09:57Z"
      }
    ]
  },
  "RegionId": "cn-shenzhen"
}

centos_7_9_x64_20G_alibase_20230919.vhd

Got same error. No alicloud image was found matching filters: centos_7_9_x64_20G_alibase_20230815.vhd
image exists by call DescribeImages.
{
  "TotalCount": 1,
  "PageSize": 10,
  "RequestId": "C0FD71A1-40EA-55DB-B965-DB3B96808F79",
  "PageNumber": 1,
  "Images": {
    "Image": [
      {
        "ImageOwnerAlias": "system",
        "Description": "Kernel version is 3.10.0-1160.92.1.el7.x86_64, 2023.8.17",
        "IsSelfShared": "",
        "Platform": "CentOS",
        "ResourceGroupId": "",
        "Size": 20,
        "IsSubscribed": false,
        "BootMode": "BIOS",
        "OSName": "CentOS  7.9 64位",
        "IsPublic": true,
        "ImageId": "centos_7_9_x64_20G_alibase_20230815.vhd",
        "DetectionOptions": {},
        "Features": {
          "NvmeSupport": "supported"
        },
        "OSNameEn": "CentOS  7.9 64 bit",
        "Tags": {
          "Tag": []
        },
        "LoginAsNonRootSupported": true,
        "Status": "Available",
        "Progress": "100%",
        "Usage": "instance",
        "Architecture": "x86_64",
        "ProductCode": "",
        "IsCopied": false,
        "ImageFamily": "acs:centos_7_9_x64",
        "IsSupportIoOptimized": true,
        "IsSupportCloudinit": true,
        "ImageName": "centos_7_9_x64_20G_alibase_20230815.vhd",
        "DiskDeviceMappings": {
          "DiskDeviceMapping": []
        },
        "ImageVersion": "v2023.8.17",
        "OSType": "linux",
        "CreationTime": "2023-08-24T07:09:57Z"
      }
    ]
  },
  "RegionId": "cn-shenzhen"
}

for shenzhen, centos_7_9_x64_20G_alibase_20230815.vhd is the lastest image and centos_7_9_x64_20G_alibase_20230919.vhd will be online soon.
for hangzhou, centos_7_9_x64_20G_alibase_20230815.vhd  is deprecated and centos_7_9_x64_20G_alibase_20230919.vhd is the lastest image.

I tried both image. but failed. I wonder if I can use aliyun public image to packer new image?
my packer version
root@wwhvw:/home/wwhvw# packer version
Packer v1.9.4

plugin installed
root@wwhvw:/home/wwhvw/packer-demo/aliyun# packer plugins installed
/root/.config/packer/plugins/github.com/hashicorp/alicloud/packer-plugin-alicloud_v1.1.0_x5.0_linux_amd64

hcl template
variable "access_key" {
  type    = string
  default = "${env("ALICLOUD_ACCESS_KEY")}"
}

variable "secret_key" {
  type    = string
  default = "${env("ALICLOUD_SECRET_KEY")}"
}

source "alicloud-ecs" "aliyun-test" {
  access_key           = "${var.access_key}"
  image_name           = "packer_basic{{timestamp}}"
  instance_type        = "ecs.t5-lc1m1.small"
  internet_charge_type = "PayByTraffic"
  io_optimized         = "true"
  region               = "cn-shenzhen"
  secret_key           = "${var.secret_key}"
  #source_image         = "centos_7_9_x64_20G_alibase_20230815.vhd"
  source_image         = "centos_7_9_x64_20G_alibase_20230919.vhd"
  ssh_username         = "root"
  run_tags = {
    "Built by"   = "Packer"
    "Managed by" = "Packer"
  }
}

build {
  sources = ["source.alicloud-ecs.aliyun-test"]

  provisioner "shell" {
    inline = ["sleep 30", "yum install redis.x86_64 -y"]
  }

}

Try to use image_family, and you can find os related image_family.
Any error, please copy the execution detail.

still fail.
source "alicloud-ecs" "aliyun-test" {
  access_key           = "${var.access_key}"
  image_name           = "packer_basic{{timestamp}}"
  instance_type        = "ecs.t5-lc1m1.small"
  internet_charge_type = "PayByTraffic"
  io_optimized         = "true"
  region               = "cn-shenzhen"
  secret_key           = "${var.secret_key}"
  #source_image         = "centos_7_9_x64_20G_alibase_20230815.vhd"
  #source_image         = "centos_7_9_x64_20G_alibase_20230919.vhd"
  image_family          = "acs:centos_7_9_x64"
  ssh_username         = "root"
  run_tags = {
    "Built by"   = "Packer"
    "Managed by" = "Packer"
  }
}

2023/10/12 08:13:02 Starting build run: alicloud-ecs.aliyun-test
2023/10/12 08:13:02 Running builder:
2023/10/12 08:13:02 [INFO] (telemetry) Starting builder alicloud-ecs.aliyun-test
==> alicloud-ecs.aliyun-test: Prevalidating source region and copied regions...
==> alicloud-ecs.aliyun-test: Prevalidating image name...
==> alicloud-ecs.aliyun-test: No alicloud image was found matching image family: acs:centos_7_9_x64
2023/10/12 08:13:07 [INFO] (telemetry) ending alicloud-ecs.aliyun-test
==> Wait completed after 4 seconds 496 milliseconds
2023/10/12 08:13:07 machine readable: error-count []string{"1"}
==> Some builds didn't complete successfully and had errors:
2023/10/12 08:13:07 machine readable: alicloud-ecs.aliyun-test,error []string{"No alicloud image was found matching image family: acs:centos_7_9_x64"}
==> Builds finished but no artifacts were created.
2023/10/12 08:13:07 [INFO] (telemetry) Finalizing.
Build 'alicloud-ecs.aliyun-test' errored after 4 seconds 495 milliseconds: No alicloud image was found matching image family: acs:centos_7_9_x64

==> Wait completed after 4 seconds 496 milliseconds

==> Some builds didn't complete successfully and had errors:
--> alicloud-ecs.aliyun-test: No alicloud image was found matching image family: acs:centos_7_9_x64

==> Builds finished but no artifacts were created.
2023/10/12 08:13:09 [WARN] (telemetry) Error finalizing report. This is safe to ignore. Post "https://checkpoint-api.hashicorp.com/v1/telemetry/packer": context deadline exceeded
2023/10/12 08:13:09 waiting for all plugin processes to complete...
2023/10/12 08:13:09 /root/.config/packer/plugins/github.com/hashicorp/alicloud/packer-plugin-alicloud_v1.1.0_x5.0_linux_amd64: plugin process exited
2023/10/12 08:13:09 /usr/bin/packer: plugin process exited

The specified sub account used in packer is not authorized.

@alexyueer OMG. Thanks a lot!


fix replication role check on RDS Postgres

According to Debezium documentation[1], on AWS RDS, the rds_replication role
is enough to read the wal_log. However, on the connection validation step,
this case is ommited and the connector cannot start. The issue is pressent
starting at least v1.4.x.Final.
[1] https://debezium.io/documentation/reference/1.8/connectors/postgresql.html#postgresql-on-amazon-rds

Hi @isacandrei you can prefix this commit message with [docs] and that will satisfy the check.

Hi @Naros! I created an issue and a different PR according to the contribution guide. I could have probably reused this PR, but it's already done.
https://issues.redhat.com/browse/DBZ-4710
https://github.com/debezium/debezium/pull/3206


Evaluation failed: TypeError: Cannot read property 'click' of undefined

They must have changed something on the sight again. I downloaded the 1.1.6 version of glitch-deploy and this is what happened when I tried to deploy
[StJohnSales] npm i glitch-deploy -g                                                                                8:09:34  ☁  master ☀
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
/home/innocent/.nvm/versions/node/v10.15.3/bin/glitch-deploy -> /home/innocent/.nvm/versions/node/v10.15.3/lib/node_modules/glitch-deploy/bin/glitch-deploy.js

<EMAIL_ADDRESS>install /home/innocent/.nvm/versions/node/v10.15.3/lib/node_modules/glitch-deploy/node_modules/keytar
prebuild-install || node-gyp rebuild

<EMAIL_ADDRESS>install /home/innocent/.nvm/versions/node/v10.15.3/lib/node_modules/glitch-deploy/node_modules/puppeteer
node install.js

Downloading Chromium r515411 - 95.4 Mb [====================] 100% 0.0s
Chromium downloaded to /home/innocent/.nvm/versions/node/v10.15.3/lib/node_modules/glitch-deploy/node_modules/puppeteer/.local-chromium/linux-515411

<EMAIL_ADDRESS>added 140 packages from 91 contributors in 52.377s
[StJohnSales] DEBUG=glitch-deploy* glitch-deploy                                                                                8:10:54  ☁  master ☀
glitch-deploy glitch.com loaded +0ms
Error: Evaluation failed: TypeError: Cannot read property 'click' of undefined
at :3:63
at ExecutionContext.evaluateHandle (/home/innocent/.nvm/versions/node/v10.15.3/lib/node_modules/glitch-deploy/node_modules/puppeteer/lib/ExecutionContext.js:66:13)
at process._tickCallback (internal/process/next_tick.js:68:7)

me too


Adding returns to the service contracts methods in client.ts

Description
Adding returns to the service contracts methods in client.ts
Related Issues
https://github.com/threefoldtech/grid3_client_ts/issues/478

@maayarosama please resolve conflicts


Is it possible to wrap easylogging into a custom logger?

hi, I'm trying to use easylogging as internal implement of my logger.  E.g., I have a logger class:
#include "easylogging++.h"
INITIALIZE_EASYLOGGINGPP
class logger {
public:
logger() {
el::Configurations defaultConf;
defaultConf.setToDefault();
// configure logger ...
el::Loggers::reconfigureLogger("default", defaultConf);
}
~logger();
void debug(const char* _msg) {
LOG(DEBUG) << _msg;
}
};
Then this logger class is used by other part of the program, for example:
#include
#include "logger.h"
int main ()
{
logger log;
log.debug("a message");
getchar();
return 0;
}
However, I got link error saying that some symbols from el namespace are defined multiple times.  Is it possible to get around this?

Because you have to use INITIALIZE_EASYLOGGINGPP in main instead of header otherwise u r redefining symbols def everytime u including header

Thanks!   my next question is, is it possible to wrap easylogging into a dynamic lib? For example, the logger is one object in the lib, which provides logging service to other objects in the lib, and other projects which uses this lib.  So far all I've got is link errors.

Have a look at this sample project https://github.com/mkhan3189/project-islam it uses Qt extensions and uses log their. What you need is SHARE_EASYLOGGINGPP
Specifically https://github.com/mkhan3189/project-islam/blob/master/core/extension/extension_loader.cc#L83 (to pass on the pointer to library)
and https://github.com/mkhan3189/project-islam/blob/master/extensions/al-quran/al_quran.cc#L12 to get shared repository
You may also have a look at this sample from elpp https://github.com/easylogging/easyloggingpp/tree/master/samples/STL/shared-static-libs


Add ROS 2 support

This is a meta-ticket that I'll use to track progress for multiple smaller items. Notably:

trac_ik_lib:

[x] Migrate parameters business to be rclcpp compliant.

[x] API break: As a fallout of this directive, I've changed a TracIK constructor to accept a std::string of the URDF XML robot description file, rather than a std::string of the parameter housing the robot description XML. This was necessary because parameters are not global in ROS 2, and because I didn't want to publish the XML on a robot_description topic (although that's how it's done in robot_state_publisher).

[x] Convert roscpp logging macros to rclcpp logging macros.
[x] Move from boost::posix_time::ptime to std::chrono::time_point.

This is not exactly needed, but I'd like to remove superfluous boost dependencies.

trac_ik_kinematics_plugin:

[ ] Write the plugin for moveit2.
[ ] Update moveit documentation about the trac_ik library and about writing said plugins.

trac_ik_python:

[ ] Move from rospy to rclpy.

trac_ik_examples:

[x] Convert ROS 1 examples to ROS 2 equivalents.
[x] Migrate launch file to be ROS 2 compliant.
[x] Import a pr2.urdf file into the package launch tree.

This can be achieved by manually calling xacro on the pr2.urdf.xacro from the pr2_description package.
This is necessary because pr2_common is not published as a ROS 2 package.

[x] Migrate parameters business to be rclcpp compliant.
[x] Move from boost::posix_time::ptime to std::chrono::time_point.

This is not exactly needed, but I'd like to remove superfluous boost dependencies.

Miscellaneous:

[ ] Tests?
[ ] Update documentation to reflect changes.
[x] Move all packages from catkin to ament.
[ ] Change name to trac_ik2?

Notes:

nlopt does not exist as a ROS package on Galactic/Rolling - it is only available through apt as libnlopt-cxx-dev. Should this be released?

Release process.

Hi, I'm trying to get trac_ik_python compiling for ros2 but without success...
I made the changes from rospy to rclpy and the like, but I mostly have problems with ament and swig right now.
Do you have any clue on how to properly do that by any chance?

Hi @SteveNguyen, unfortunately I haven't had the time to look at trac_ik_python yet. The "Move from rospy to rclpy" directive I've noted was only an initial hunch, and as you've seen already, there is probably a bunch more to do on top of that. I think you're on the right track because the rospy -> rclpy migration should be a big part of the port, but I'm not sure what to do after that.
TLDR: Give me a few hours to investigate, and I will report back here with any details I find. If you don't mind, can you open a draft PR for the ROS 2 port of trac_ik_python? It'd be easier to track progress that way.


{Packaging} Change default debian repo to bullseye

Description
This is the stable release for almost 3 months by now.

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR title and description has followed the guideline in Submitting Pull Requests.

[X] I adhere to the Command Guidelines.

[X] I adhere to the Error Handling Guidelines.

Packaging

We still need to sync this file to https://azurecliprod.blob.core.windows.net/$root/deb_install.sh


typescript compatibility issue

When using it with typescript, it is giving error mentioned below:
Expected 2 arguments, but got 1.ts(2554) index.d.ts(60, 3): An argument for 'action' was not provided. (alias) connectRouter(history: History): Reducer<RouterState, LocationChangeAction> import connectRouter
for this code:
export default createStore( connectRouter(history)(rootReducer), initialState, composedEnhancers );

This looks wrong - connectRouter produces a reducer function which should be combined with other reducers to become part of the rootReducer. Here you are trying to call it - since it’s a reducer, it is complaining about a missing action

Confirmed, I am also running into this issue.

I ended up just ditching this and wrapping my App with <BrowserRouter>

I am having this issue, were any of you able to solve it?


Missing step

This article makes no mention of creating a connection request policy on the remote NPS server. If there is no CRP on the server matching the request from the RDP server, the request will fail. It is not sufficient to merely create a network policy.

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

ID: 61df48bb-a963-b1f0-8f64-b55d0bd6904c
Version Independent ID: 677de59f-a222-8905-11c0-a3ac619d8b56
Content: Remote Desktop Gateway integration with Azure MFA NPS extension - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-nps-extension-rdg.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@ianc911 Thanks for the feedback! We will review and update accordingly.

@ianc911 Thank you for requesting the CRP related information to be added to the article. We talk about the default connection request policy however we have added a note in the article pointing towards the original NPS server documentation which discusses how to create a connection request policy in detail. A pull request is initiated and the document will get updated after its reviewed and committed to the repository in the next release cycle. We will close this issue now. Should you have any further queries or concerns , please do let us know.
Thank you.

So do I need a Connection Request Policy setup on the server that is running the Azure NPS Extension? At the moment all I have is the default on in there that is the "Use Windows Authentication for all users".

Yes, whatever server has the NPS extension installed and will be processing the authentication request from the remote NPS server will need a CRP to match that request...


proposal: x/sys/windows: fix Accept implementation

Currently windows.Accept (like syscall.Accept for GOOS=windows) contains a stub function which does nothing.
Looks like this function was introduced to mimic unix.Sockaddr.Accept method but it's just a useless stub.
I propose to fix it's signature and re-implement it as winsock's accept function.
In the end it will look something like this:
package windows

func Accept(fd windows.Handle, sockaddr, sockaddrLen uintptr)

Winsock accept function signature (see MSDN)
SOCKET WSAAPI accept(
  [in]      SOCKET   s,
  [out]     sockaddr *addr,
  [in, out] int      *addrlen
);

Instead of passing sockaddr raw pointer and it's size it's possible to also use Sockaddr interface and the same approach like in windows.Bind but it will limit method's potential use cases (it can't be used for custom sockets). See #54209.

Windows programs mostly use windows.AcceptEx.  If Accept can work I don't see a problem implementing it.  But the only reason to implement it in x/sys/windows would be to match x/sys/unix, meaning that the function should be
func Accept(fd Handle) (nfd Handle, sa Sockaddr, err error)

@ianlancetaylor the problem is that in x/sys/unix, Accept is a method of Sockaddr interface but in windows package it's a dedicated function which just accepts some kind of handle (which makes it useless).
Winsock supports a classic accept function and accepts socket, sockaddr pointer and sockaddr struct length.
I would recommend to implement Sockaddr interface in the same way as it's done in x/sys/unix but to make it open for custom implementation so it can be reused for custom sockets.

For Unix, Accept shows up next to Sockaddr in pkg.go.dev because it is a constructor, not a method.
The Accept signature in x/sys/windows can't be changed, but it would be fine to implement.
If the signature is not changing and the behavior is changing from a stub to an actual implementation, that sounds perfectly fine and doesn't need more discussion.
Do I have that right?

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

@rsc I'm not really sure that it's possible to implement Accept method for windows with only 1 argument, because in winsocks signature is the same as for regular POSIX accept method.
That means that it requires also sockaddr pointer and a size:
SOCKET WSAAPI accept(
  [in]      SOCKET   s,
  [out]     sockaddr *addr,
  [in, out] int      *addrlen
);

Do you know why it was initially designed with only 1 argument? And how it was supposed to be used?
Thank you.

The Windows accept function is the same as the Unix accept function.  But the addr and addrlen parameters are just output parameters.  There is no need to pass them in.  So the Go version just passes down the address of local variables, and returns those variables.  See, for example, https://go.googlesource.com/sys/+/refs/heads/master/unix/syscall_bsd.go#272.

@ianlancetaylor thank you for clarification :)

The Windows accept function is the same as the Unix accept function. But the addr and addrlen parameters are just output parameters. There is no need to pass them in. So the Go version just passes down the address of local variables, and returns those variables. See, for example, https://go.googlesource.com/sys/+/refs/heads/master/unix/syscall_bsd.go#272.

One quick clarification, the addrlen is an [in, out] parameter, which means that it receives a value and based on that value it will refresh the value on the same memory address. I don't have experience with Accept specifically, but in some cases it's mandatory to pass the value into the syscall, and used the refreshed one. One specific example: WSALookupServiceNext also accepts a size, which value is 120 in the first syscall (the length of WSAQUERYSET), and updates to 1024. The next syscall supposed to used the same memory address and the refreshed value.
This doesn't mean that you need to update the function signature, but something to keep in mind.

@rsc can I contribute somehow to the implementation if this proposal will be accepted?

@x1unix Sure.  Thanks.

It sounds like everyone agrees this is about implementing a stub function, keeping the API exactly the same. Assuming that's true, there's no need for a proposal.

Removing from the proposal process now that the issue is simply to implement the existing stub API with no API signature changes or new APIs.

Removed from the proposal process.
This was determined not to be a “significant change to the language, libraries, or tools”
or otherwise of significant importance or interest to the broader Go community.
— rsc for the proposal review group


Publish download link for JDBC Driver

Publish download link for the JDBC driver independently from ODBC

Isn't it a duplicate of #244?

Not quite, the releases for JDBC and ODBC are being tracked separately and will be released independently of each other, so I created a separate issue for JDBC since that one is on track to be released first

closed by https://github.com/opensearch-project/project-website/pull/635, links are available on https://opensearch.org/artifacts


Replaced @react/auto-id with nanoid

@react/auto-id doesn't support React versions higher than 17.
Replacing it with nanoid give us the same functionality with a lighter and faster package.

Thanks for the PR. However, this would generate a new id on every render. Looks like the issue with React 18 was fixed in this commit https://github.com/reach/reach-ui/commit/f50908c6203b44032b601307cb5e7b9aece8f4c6. Can you try bumping @react/auto-id to the latest version instead?

Hi @phamfoo, you are right I didn't account for the id changing on every render. I just pushed a new commit persisting the id between renders. I looked at the last commits for @reach/auto-id; they still don't support React 18 directly, just through a react-18 alias.

Sorry for the delayed response. I decided to go with a different approach (https://github.com/phamfoo/react-native-figma-squircle/commit/d3ee298687f9c2c94ebb423632571a54cb1986bd) that doesn't require using ClipPath. This also removes the need of generating a unique id for each clip path.


If the shot target is dead, the shot still is there and goes to the target

shot should follow new target or shot should disappear

shot gets removed after target is dead


M3-3416 [Longview] Plan Details page

Description
This PR contains the new Longview "Plan Details" page.
In this PR:

New [SDK] method: GET /longview/subscriptions
New LongviewSubscription interface
New longviewSubscription factory for generating test data (via factory.ts)
Updates to accountSettings.container.tsto include the updateAccountSettings request.
<LongviewPlans /> component (with sub components in the same file)
Tests ~(still in progress)~ done for now

Mobile styling is... fine. I made the table non-responsive, so you'll need to horizontally scroll on smaller viewports to see the entire table.
Type of Change

Non breaking change ('update', 'change')

Note to Reviewers
To run new unit tests: yarn test packages/manager/src/features/Longview/LongviewLanding/LongviewPlans.test.tsx ~(still in progress)~ done for now
To test functionality, go to http://localhost:3000/longview/plan-details and change your subscription. Simulate error state by request-blocking *longview* and *settings*.

agreed with all of Jared's points - otherwise LGTM

@johnwcallahan one more request: we're going to need the longview/subscriptions data (as well as the accountSettings) in the longview/clients page. Would it make sense to move your requests up to LongviewLanding and pass that data down to both tabs?

Thanks for the feedback. @Jskobos addressing your points:

We should handle for Managed customers more explicitly. We could disable the form for them with a message, for example.

cc @alioso
I chatted with Jay about this. We're going to hide the table and show a message:

Pressing the submit button with the current plan selected doesn't do anything & there's no feedback. Should disable that one somehow, like we do for the Linode resize flow

Also chatted with Jay about this. The submit button has been disabled if you've selected the plan that is already on your account.

Weird bug: generate a few errors then navigate to /account/settings...you get toasts for the errors you've just seen inline in the form

This is super interesting. This is happening because upon failure to update your account settings, we get an error in Redux under accountSettings.error.update. <GlobalSettings /> blindly shows toasts for update errors upon every render: https://github.com/linode/manager/blob/2150815ecf8aec6e3743e42186ab2391ccecb4bd/packages/manager/src/features/Account/GlobalSettings.tsx#L130
My feeling is that this should be fixed separately, in that component. Let me know your thoughts.
Another solution is that <LongviewPlans /> could clear out accountSettings Redux errors on unmount, but that feels wrong to me.

Would it make sense to move your requests up to LongviewLanding and pass that data down to both tabs?
Yep, done. Though I kept the accountSettings container where it is, because I also needed isManaged. We can hook up the parent to accountSettings as well.


Limit python version installation

Please add python version checks before installation.
See https://packaging.python.org/guides/distributing-packages-using-setuptools/#id55
Maybe it would be a good idea considering relaying on typing extensions:
https://github.com/python/typing/tree/master/typing_extensions
Thank you!

Thanks for reporting.
I added support for 3.6 and 3.7 with typing-extensions; and also configured Travis CI to runs tests on 3.6, 3.7 and 3.8.

Awesome!


Telemetry

telemetry merge 2.0

Sweet. Ok, first thing's first. Your'e gonna have to get all these files building. Whag I recommend you do is treat the mavlink library as a cmake library. That means you'l have to stick a cmakelists.txt file inside the mavlink directory and tell the cmakelists.txt file in the autopilot directory about it. You'l def have to do some research but one good example is our HAL drivers. Take a look at Autopilot\boardfiles\Drivers\STM32F7xx_HAL_Driver\Cmakelists.txt and then checkout how the top level cmakelists (in AutoPilot) pulls it in as a library.

Sweet. Ok, first thing's first. Your'e gonna have to get all these files building. Whag I recommend you do is treat the mavlink library as a cmake library. That means you'l have to stick a cmakelists.txt file inside the mavlink directory and tell the cmakelists.txt file in the autopilot directory about it. You'l def have to do some research but one good example is our HAL drivers. Take a look at Autopilot\boardfiles\Drivers\STM32F7xx_HAL_Driver\Cmakelists.txt and then checkout how the top level cmakelists (in AutoPilot) pulls it in as a library.


Add response attribute for WebSocketSession

Close: discussions/53

I have an idea, what about using response instead of subprotocol as the parameter?
class AsyncWebSocketSession:
    response: httpx.Response
    subprotocol: typing.Optional[str]

    def __init__(
        self,
        stream: AsyncNetworkStream,
        *,
        response: httpx.Response,
        max_message_size_bytes: int = DEFAULT_MAX_MESSAGE_SIZE_BYTES,
        queue_size: int = DEFAULT_QUEUE_SIZE,
        keepalive_ping_interval_seconds: typing.Optional[
            float
        ] = DEFAULT_KEEPALIVE_PING_INTERVAL_SECONDS,
        keepalive_ping_timeout_seconds: typing.Optional[
            float
        ] = DEFAULT_KEEPALIVE_PING_TIMEOUT_SECONDS,
        # subprotocol: typing.Optional[str] = None,  # delete
    ) -> None:
        self.stream = stream
        self.connection = wsproto.connection.Connection(wsproto.ConnectionType.CLIENT)
        self.response = response
        self.subprotocol = response.headers.get("sec-websocket-protocol")  # instead

Explicitly annotating httpx.Response instead of typing.Optional[httpx.Response] can provide type checking benefits to prevent type checking complaints about ws.Response being None.

Hi @frankie567
Can you review this PR? I'm maintaining fastapi-proxy-lib, which uses httpx-ws as the underlying library to implement reverse proxy functionality. I'm hoping to be able to retrieve response headers through httpx-ws, so that I can achieve transparent proxying.
https://github.com/WSH032/fastapi-proxy-lib/blob/977d9c10c102c4dd34101f0f9eb51de6cba72a70/src/fastapi_proxy_lib/core/websocket.py#L571-L573

Hey @WSH032 👋
Sorry, this got out of my mind 😊
Looks good overall! I would be indeed interested in having the subprotocol pulled from the response parameter, if available.
However, let's keep response typed as Optional, as it would be painful for testing.

For the current PR, the type of response is indeed Optional. Is there anything you would like me to change? Or do we need to wait for something?

Just the way we set self.subprotocol: let's use the response object if available instead of explicitly passing it in argument.

Sorry, please forgive me. Could you clarify further? I'm not quite understanding.
We're only passing response in aconnect_ws. Wouldn't this cause a WebSocketUpgradeError if response isn't available?

Yes, sorry, I'm not being clear here. What I mean is, I would like to do this:
class AsyncWebSocketSession:
    subprotocol: typing.Optional[str]

    def __init__(
        self,
        stream: AsyncNetworkStream,
        *,
        max_message_size_bytes: int = DEFAULT_MAX_MESSAGE_SIZE_BYTES,
        queue_size: int = DEFAULT_QUEUE_SIZE,
        keepalive_ping_interval_seconds: typing.Optional[
            float
        ] = DEFAULT_KEEPALIVE_PING_INTERVAL_SECONDS,
        keepalive_ping_timeout_seconds: typing.Optional[
            float
        ] = DEFAULT_KEEPALIVE_PING_TIMEOUT_SECONDS,
        response: typing.Optional[httpx.Response] = None,
    ) -> None:
        self.stream = stream
        self.connection = wsproto.connection.Connection(wsproto.ConnectionType.CLIENT)
        self.response = response
        if self.response is not None:
            self.subprotocol = response.headers.get("sec-websocket-protocol")
        else:
            self.subprotocol = None

And so _aconnect_ws (and _connect_ws) would look like this:
@contextlib.asynccontextmanager
async def _aconnect_ws(
    url: str,
    client: httpx.AsyncClient,
    *,
    max_message_size_bytes: int = DEFAULT_MAX_MESSAGE_SIZE_BYTES,
    queue_size: int = DEFAULT_QUEUE_SIZE,
    keepalive_ping_interval_seconds: typing.Optional[
        float
    ] = DEFAULT_KEEPALIVE_PING_INTERVAL_SECONDS,
    keepalive_ping_timeout_seconds: typing.Optional[
        float
    ] = DEFAULT_KEEPALIVE_PING_TIMEOUT_SECONDS,
    subprotocols: typing.Optional[typing.List[str]] = None,
    **kwargs: typing.Any,
) -> typing.AsyncGenerator[AsyncWebSocketSession, None]:
    headers = kwargs.pop("headers", {})
    headers.update(_get_headers(subprotocols))

    async with client.stream("GET", url, headers=headers, **kwargs) as response:
        if response.status_code != 101:
            raise WebSocketUpgradeError(response)

        async with AsyncWebSocketSession(
            response.extensions["network_stream"],
            max_message_size_bytes=max_message_size_bytes,
            queue_size=queue_size,
            keepalive_ping_interval_seconds=keepalive_ping_interval_seconds,
            keepalive_ping_timeout_seconds=keepalive_ping_timeout_seconds,
            response=response,
        ) as session:
            yield session

Said another way, the "parsing" of the subprotocol is done by the main class instead of the context manager function.

Oh, I see what you mean now. I've made the changes accordingly. But this seems like a BREAKING CHANGE, doesn't it?

Indeed, but I don't expect much people to use the class directly; so that's acceptable if clearly stated in the changelog 😄

@all-contributors add @WSH032 for code


[WIP] [ALLUXIO-1739] Implement ufs data path delegation on the client

Adds client side logic for ufs data path delegation. This PR is still WIP
TODOs:

Resolve integration test failures when delegation is enabled
Propagate user group info
Documentation for this feature
Additional integration/unit tests for the feature

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9862/
Test PASSed.

Thanks @calvinjia for the awesome PR! I left some comments.
Looking forward to seeing the documentation for this feature, and test coverages.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9878/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.block.BlockMasterClientRestApiTest.serviceNameTest
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9888/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9891/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9894/Build result: ABORTED[...truncated 3367 lines...]	at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:606)	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)	at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:606)	at hudson.maven.Maven3Builder.call(Maven3Builder.java:136)	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)	at hudson.remoting.UserRequest.perform(UserRequest.java:120)	at hudson.remoting.UserRequest.perform(UserRequest.java:48)	at hudson.remoting.Request$2.run(Request.java:326)	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:745)[INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alluxio-tests ---
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9896/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9895/
Test PASSed.

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9899/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9900/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9902/Build result: FAILURE[...truncated 1638 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3/target/alluxio-underfs-s3-1.1.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-s3/1.1.0-SNAPSHOT/alluxio-underfs-s3-1.1.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3/target/alluxio-underfs-s3-1.1.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-s3/1.1.0-SNAPSHOT/alluxio-underfs-s3-1.1.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/assembly/pom.xml to org.alluxio/alluxio-assemblies/1.1.0-SNAPSHOT/alluxio-assemblies-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.1.0-SNAPSHOT/alluxio-shell-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/oss/pom.xml to org.alluxio/alluxio-underfs-oss/1.1.0-SNAPSHOT/alluxio-underfs-oss-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/oss/target/alluxio-underfs-oss-1.1.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-oss/1.1.0-SNAPSHOT/alluxio-underfs-oss-1.1.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/oss/target/alluxio-underfs-oss-1.1.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-oss/1.1.0-SNAPSHOT/alluxio-underfs-oss-1.1.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/client/pom.xml to org.alluxio/alluxio-keyvalue-client/1.1.0-SNAPSHOT/alluxio-keyvalue-client-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/pom.xml to org.alluxio/alluxio-underfs-hdfs/1.1.0-SNAPSHOT/alluxio-underfs-hdfs-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.1.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-hdfs/1.1.0-SNAPSHOT/alluxio-underfs-hdfs-1.1.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.1.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-hdfs/1.1.0-SNAPSHOT/alluxio-underfs-hdfs-1.1.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/pom.xml to org.alluxio/alluxio-underfs-swift/1.1.0-SNAPSHOT/alluxio-underfs-swift-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.1.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-swift/1.1.0-SNAPSHOT/alluxio-underfs-swift-1.1.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.1.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-swift/1.1.0-SNAPSHOT/alluxio-underfs-swift-1.1.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.1.0-SNAPSHOT/alluxio-examples-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/pom.xml to org.alluxio/alluxio-core-server/1.1.0-SNAPSHOT/alluxio-core-server-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.1.0-SNAPSHOT/alluxio-keyvalue-common-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/pom.xml to org.alluxio/alluxio-underfs/1.1.0-SNAPSHOT/alluxio-underfs-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.1.0-SNAPSHOT/alluxio-underfs-glusterfs-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.1.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.1.0-SNAPSHOT/alluxio-underfs-glusterfs-1.1.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.1.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.1.0-SNAPSHOT/alluxio-underfs-glusterfs-1.1.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/integration/pom.xml to org.alluxio/alluxio-integration/1.1.0-SNAPSHOT/alluxio-integration-1.1.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/pom.xml to org.alluxio/alluxio-keyvalue/1.1.0-SNAPSHOT/alluxio-keyvalue-1.1.0-SNAPSHOT.pomchannel stopped
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9906/
Test PASSed.

Merged build finished. Test PASSed.

Mostly LGTM, just a few minor comments.

@ifcharming Thanks for doing a second pass, I've addressed your comments.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9922/
Test PASSed.

Thanks @calvinjia, I have one more comment, otherwise LGTM

LGTM

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9925/Build result: ABORTED[...truncated 2749 lines...]	at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:606)	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)	at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:606)	at hudson.maven.Maven3Builder.call(Maven3Builder.java:136)	at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)	at hudson.remoting.UserRequest.perform(UserRequest.java:120)	at hudson.remoting.UserRequest.perform(UserRequest.java:48)	at hudson.remoting.Request$2.run(Request.java:326)	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:745)[INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alluxio-tests ---
Test FAILed.


Exception: Class auth does not exist

composer.json:
"barryvdh/laravel-ide-helper": "1.*"

and got this message below:
➜  src  php artisan ide-helper:generate
Exception: Class auth does not exist
Skipping Illuminate\Support\Facades\Auth.
Exception: Class auth does not exist
Skipping Illuminate\Support\Facades\Password.
A new helper file was written to _ide_helper.php

@barryvdh : I have this same issue after upgrading to L5.1... Any ideas?

Yes, see above

Uhm... Sorry, what you mean? All the posts above are related to L4.1. In L5.1 we have only one config file and mine is similar to official file, nothing wrong there. Am I missing something?

Then please create a new issue.

Most of the times the issue of 'class ****(in lower case) does not exist' are caused by something different entirely. If you open bootstrap/cache/services.php you will see the **** that is being complained about.
...
...
     'hash' => 'Illuminate\\Hashing\\HashServiceProvider',
...
...

In my own case but Laravel complained  class hash does not exist. With this, I deduced that the problem was not hash, it was something that was thrown before services.php file could be loaded.
It turned out that I was right I simply dumped $e on the first line of report() function in app/Exceptions/Handler.php to see the real error which happened to be database connection issues in my case

i am experiencing a similar problem in laravel 8 how can is solve this after updating it


Correct the default archetype

Resolves #48, which iirc was an error I introduced at some point in the past. To observe the change, create a new post/content item and run hugo server without updating any of its fields.

No problem with that, I didn't see it either.


update announcements plugin ownership

Hey, I just made a Pull Request!
For several months, I have attempted to communicate with the owner of the announcement plugins. I have tried emailing, opening an issue, messaging them on Discord, and posting in the Backstage Discord.
I don't know what else to do, but I see a backlog of issues and feature requests not receiving adequate attention. We started our own version based on the recommendation of the maintainer and are now at a point where we would receive more traction if the marketplace pointed to our maintained version. A lof the open issues have been resolved in our version, and we are excited about the opportunity for community contributions.
I elected not to open a PR to include these plugins here based on the recent RFC.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hej Kurt - thanks for the effort & taking ownership here! I will bring it up with the team & we will discuss it. Good to mention #20266 here as this might be the perfect example for a community plugin.

Ok, let's try one last time to see if this is in his intention.
Can you just give a quick thumbs up / lgtm, such that we can ship this, @K-Phoen? :)

Are you planning to address the issues in this plugin found with announcements  plugin wrt backstage v1.20.3 ?

Are you planning to address the issues in this plugin found with announcements plugin wrt backstage v1.20.3 ?

@sharadpattanshetti, our version of the plugin is on the latest release of Backstage. Here is the PR.
I'm learning how to best handle releases, and I've settled on every Monday / Tuesday until more governance is needed.

@sharadpattanshetti, I have also added some issues that would be valuable to contribute.
Here is a contribution I made based on an issue opened with the repo, and we have received two new contributors.
I am having a hard time getting the owners of issues and PRs to open them with us. I think part of that is that the "official" plugin on the marketplace does not point to us.

Hey, thanks for your patience. Given the lack of feedback, we'll ship this. ❤


Support build step listener

🚧

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

What
Enable BuildStepListener for the non-pipeline jobs in order to create spans.
Actions

[x] Support siblings steps rather than nested steps
[x] Support symbols
[x] Support plugin metadata
[ ] Support env variables with the trace/span id in the BuildStep itself to be able to correlate from the build step rather than the transaction itself?

Test
Test simple freestyle job
Given the freestyle job:
<?xml version="1.0" encoding="UTF-8"?>
<project>
   <description />
   <keepDependencies>false</keepDependencies>
   <properties />
   <scm class="hudson.scm.NullSCM" />
   <canRoam>true</canRoam>
   <disabled>false</disabled>
   <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
   <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
   <triggers />
   <concurrentBuild>false</concurrentBuild>
   <builders>
      <hudson.tasks.Shell>
         <command>echo 'I am your span'</command>
      </hudson.tasks.Shell>
   </builders>
   <publishers />
   <buildWrappers />
</project>

Then

Test complex freestyle job
<?xml version="1.0" encoding="UTF-8"?>
<project>
   <actions />
   <description />
   <keepDependencies>false</keepDependencies>
   <properties />
   <scm class="hudson.scm.NullSCM" />
   <canRoam>true</canRoam>
   <disabled>false</disabled>
   <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
   <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
   <triggers />
   <concurrentBuild>false</concurrentBuild>
   <builders>
      <hudson.tasks.Shell>
         <command>curl -s https://raw.githubusercontent.com/jenkinsci/ant-plugin/master/src/test/resources/hudson/tasks/_ant/simple-build.xml > file.xml</command>
      </hudson.tasks.Shell>
      <hudson.tasks.Ant<EMAIL_ADDRESS>         <targets>foo</targets>
         <antName>latest</antName>
         <buildFile>file.xml</buildFile>
      </hudson.tasks.Ant>
   </builders>
   <publishers>
      <hudson.tasks.ArtifactArchiver>
         <artifacts>file.xml</artifacts>
         <allowEmptyArchive>false</allowEmptyArchive>
         <onlyIfSuccessful>false</onlyIfSuccessful>
         <fingerprint>false</fingerprint>
         <defaultExcludes>true</defaultExcludes>
         <caseSensitive>true</caseSensitive>
         <followSymlinks>false</followSymlinks>
      </hudson.tasks.ArtifactArchiver>
   </publishers>
   <buildWrappers />
</project>

I love the fearture

I can say now that this is feature complete. It supports Freestyle jobs out of the box. For matrix or maven job types, in case we want to support them, it will require some further changes to enable every axes in the matrix job to be a span from the job, similar with the maven multimodules.


consistent component name and resolved failing numeric dir push

Changed the ordering of prefix and component type when creating a default component name.
Use of absolute path for source path when generating the default component name when source type is local

Was the change discussed in an issue?
fixes https://github.com/openshift/odo/issues/1825

How to test changes?
mkdir nodejs-test
odo create nodejs --context ./nodejs-test
cd nodejs-test
odo create nodejs --context .

should give the same component name
also
mkdir 1234
odo create nodejs --context ./1234
cd 1234
npm init --yes  #just so it doesn't fail on package.json not found error
odo push

shouldn't fail due to a DNS-1035 label must consist of lower case alphanumeric characters or '-'

/retest


net: Enable logging in more modules if CONFIG_NET_LOG_GLOBAL defined

This is useful to enable error/warning logging across the net
codebase (less useful for debug level logging, but that's true
for CONFIG_NET_LOG_GLOBAL already).
Implementation-wise, instead of keeping adding to long list of
"select"'s in CONFIG_NET_LOG_GLOBAL and thus introduce component
inter-dependencies, add "default y if NET_LOG_GLOBAL" to
individual components' logging options.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

This is rework of https://github.com/zephyrproject-rtos/zephyr/pull/1507 using @tbursztyka's suggestion.

For better consistency, I think you will need to do the same change for all the options currently listed in config NET_LOG_GLOBAL, and remove the select of those there.

How about doing it step by step, minimizing the amount on big changes on each?

Sure, either way. You can add another commit on this PR


Link to GitHub webhook event types

Why:
Closes #8295
What's being changed:
The GitHub Actions reference documentation for the github context's event field now benefits from a direct link to the documentation describing the different GitHub webhook event types. No longer must one wonder how to figure out which fields are supported.
Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@OldSneerJaw Thanks so much for opening a PR! I'll get this triaged for review :zap:


In pull request, can't add review with thumbup emoji

Gitea version (or commit ref): 1.14.2
Git version: <IP_ADDRESS>
Operating system: CentOS Linux release 7.9.2009 (Core)

I'm using the gitea binary from the 1.14.2 release (https://github.com/go-gitea/gitea/releases/tag/v1.14.2), and I'm running this with systemd.

Database (use [x]):

[ ] PostgreSQL
[ x ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ x ] No

Log gist:

2021/05/19 15:26:30 .../repo/pull_review.go:219:SubmitReview() [E] SubmitReview: Error 1366: Incorrect string value: '\xF0\x9F\x91\x8D ' for column gitea.review.content at row 1
Description

When I do a review within a pull request, and use the thumbup (+1) emoji in the review comment textarea, I get a 500 error with the below logged error:
2021/05/19 15:26:30 .../repo/pull_review.go:219:SubmitReview() [E] SubmitReview: Error 1366: Incorrect string value: '\xF0\x9F\x91\x8D ' for column gitea.review.content at row 1
Screenshots

Are you using MySQL? If so you probably need to convert the tables to utf8mb4, gitea convert can help with that but take a backup before doing it.

This is clearly YET ANOTHER mysql utf8 Vs utf8mb4 issue.
Please read the extensive number of issues relating to this and run: gitea convert and change your app.ini to use charset=utf8mb4.


Disable Cave Aging Inside Claims

My players would love to make their bases underground without the cave aging feature inside their claims. Is it possible to hook with GriefPrevention to stop cave aging inside claims?

I just tried to add GriefPreventionFlags support into the plugin in latest build. Honestly I'm not sure if it works and persists after restart, but would be awesome if you try it.
If you don't want to use another plugin - I'm planning to add flag-less mode, so it will just disable certain features inside of regions.

Thank you. I'll give it a try soon and will give feedback.

Added flagless mode, so you can choose it to disable some of features inside of claims.
worldguard-flagless for WorldGuard and griefprevention-flagless for GriefPrevention.

"[DangerousCaves] Can't find mode "griefprevention". Regions feature is disabled."

@LoneDev6 You have to use griefprevention-flagless for just GriefPrevention. Anyway, I will look into it.
I was already thinking about combined protections. It's actually quite to do simple with current system. Will try to implement it.

Thanks please let me know.
Anyway I triesd also to use griefprevention-flagless without success, as I said

@LoneDev6 GP region checker should work properly now. Also renamed griefprevention mode to griefprevention-flags and griefprevention-flagless to griefprevention (and same for WG).
Also you can now specify multiple modes, like mode: griefprevention,worldguard

It continues to happen with Dangerous-Caves-2 2.2.7 and GriefPrevention 16.14.0 :(

This continues to happen in griefprevention protections :(

@niqoar, can you show list of your modes from the config?

@niqoar, can you show list of your modes from the config?

Yes, this is my config: https://pastebin.com/vCEENGVm

@niqoar, as for now not sure what's wrong. Will look deeper into it a bit later.

There was some commits related to this issue. If anyone is interested - please test it.

My players confirm that the cave aging is mostly gone - except for one thing: the mushrooms.

@l3st4tPlugins are you sure that DC causes it and not vanilla mushrooms spreading?

Not sure. Didn't even know vanilla mushrooms can spread. I guess I could add debug and monitor it.

After testing, there were some hidden mushrooms in their lands, and removing them fixed it. So at least under the Lands protection, cave aging inside claims is disabled.

Will leave this issue open for one more month just in case.

Hi. I'm not sure if this is related to the problem above but I'm getting this  warning from the plugin:

[08:19:23 WARN]: [DangerousCaves] Can't find mode "griefprevention".

I also have the same problem as the person above.

@Kenaestic It tells that DC2 can't detect GriefPrevention plugin on your server, so mode can't be used - do you actually have GriefPrevention installed? Also, what's your exact second problem?

@Kenaestic It tells that DC2 can't detect GriefPrevention plugin on your server, so mode can't be used - do you actually have GriefPrevention installed? Also, what's your exact second problem?

Yes I'm positive. I also have other plugins hooking into griefprevention like dynmap. I'm on the newest version on both Dangerous Caves and Griefprevention. I tried downgrading versions with both plugins without succes. I suspect it may be a paper update that caused this but I'll have to test it out.
I left my server startup log in the spigot discussion thread but I'll send you an up-to-date one here:
https://pastebin.pl/view/0034cc76
DC settings:
https://pastebin.pl/view/bbb04e8f
Griefprevention settings:
https://pastebin.pl/view/4f2393d7
Let me know if you need anything else.

@Kenaestic Seems like somehow DC starts sooner than GP, and that's quite weird.

@Kenaestic Please try latest build, it should be fine now.

@Kenaestic Please try latest build, it should be fine now.

Do you have a link where I can download it?

@Kenaestic Please try latest build, it should be fine now.

I can confirm that I'm not getting any warnings now. I'll test the plugin further and will report back if there's any problems. Thanks for your help 👍

Please reopen the issue if something is still doesn't work.

Please reopen the issue if something is still doesn't work.


Coordinate Widget not working

The coordinate widget located at http://pscltcentos.eastus.cloudapp.azure.com/coordinatetool/ is not working.  When modifying the input value, none of the outputs are being updated.

Can you give me some of the values you were using and if you were typing them in or pasting. I'll try and reproduce here.

The tool is actually updating today, as opposed to the other day when nothing was updating.  We could probably close this issue and just open specific issues that I've found.  I want to talk with Lyle to see what he captured during the testing task, and to clarify that the issues I'm seeing are actually issues, although talking with Joe, it sounds like they are.

Please check to see if you can access the widget. @dhagens

I am able to access the widget and everything is updating fine.


Flake8 finds Python syntax errors and undefined names

flake8
These tests should pass ~once #997 is merged.~

Could you move the pip install flake8 into test/travis_setup.sh? Pip sometimes fails or times out. The retry helps to avoid false failures.

Tracks with https://devguide.python.org/#branchstatus


Added a shorter method

The proposed method is useful when the binding address/port don't matter.

Thanks, @maxime915 !
That's the best solution for my use case. And it is not the same as the others. Because the other solutions do listen on this port, too. This means that you are not able to use another client/netcat on the same machine to listen on this port (which is, at least for development purposes, very handy).
@aler9 You should definitely include this.


Prompt Tracking - Long Form

Currently when the user opts-in to prompt tracking, we send them to Google Analytics as a tag on an event. This has a character limit.
In order to overcome this character limit, we can build our own backend that stores the prompts in full.
NOTE: this should probably have user authentication as a pre-requisite so that we don't have unassociated events being stored in the DB, which could lead to abuse.

duplicate: https://github.com/polywrap/evo.ninja/issues/479


Update pre-commit hooks

Fixes issue on a macOS with pre-commit:
flake8...................................................................Failed
- hook id: flake8
- exit code: 1

multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/Users/albert/.pyenv/versions/3.8.0/lib/python3.8/multiprocessing/pool.py", line 125, in worker
    result = (True, func(*args, **kwds))
  File "/Users/albert/.pyenv/versions/3.8.0/lib/python3.8/multiprocessing/pool.py", line 48, in mapstar
    return list(map(*args))
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/checker.py", line 669, in _run_checks
    return checker.run_checks()
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/checker.py", line 608, in run_checks
    self.run_ast_checks()
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/checker.py", line 504, in run_ast_checks
    for (line_number, offset, text, check) in runner:
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8_plugin_utils/plugin.py", line 78, in run
    visitor = self._create_visitor(visitor_cls)
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8_plugin_utils/plugin.py", line 105, in _create_visitor
    if cls.config is None:
AttributeError: type object 'PytestStylePlugin' has no attribute 'config'
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/bin/flake8", line 8, in <module>
    sys.exit(main())
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/main/cli.py", line 18, in main
    app.run(argv)
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/main/application.py", line 394, in run
    self._run(argv)
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/main/application.py", line 382, in _run
    self.run_checks()
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/main/application.py", line 301, in run_checks
    self.file_checker_manager.run()
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/checker.py", line 328, in run
    self.run_parallel()
  File "/Users/albert/.cache/pre-commit/repo8iv7mhhh/py_env-python3/lib/python3.8/site-packages/flake8/checker.py", line 292, in run_parallel
    for ret in pool_map:
  File "/Users/albert/.pyenv/versions/3.8.0/lib/python3.8/multiprocessing/pool.py", line 448, in <genexpr>
    return (item for chunk in result for item in chunk)
  File "/Users/albert/.pyenv/versions/3.8.0/lib/python3.8/multiprocessing/pool.py", line 865, in next
    raise value
AttributeError: type object 'PytestStylePlugin' has no attribute 'config'

"tl;dr python 3.8 multiprocessing switch from fork to spawn on macOS and the plugin configuration approach flake8 uses is not spawn-safe. 3.7.9 has a fix for that." (at)asottile

Thanks @webknjaz!


[Rust] Remove blst to avoid double link issues, expose blst features

The big chunks of code are taken from blst without major modifications

@jtraglia again no idea why I can't use github's review request

Yeah idk either. It seems that I can only add a subset of people myself. Like I can't request a review from @ppopth even though he has write-access & is part of the organization. I'll make an issue with devops.

@jtraglia this code is copied from the blst build.rs (so what we currently use). I'm not really aware behind the decisions to use some or other compile flags on their side, tho I'm trying to dig in the blst history to understand where they come from

Ah, yeah I see that now. Maybe I should bring up my concerns with blst instead.
I think this PR looks fine, let me know when you're ready & I'll merge it.

all good on my side.  I should note tho, I think we could avoid having to maintain this code in sync if we weren't vendoring blst but declaring it as a depedency from crates.io and if the blst crate had a release. From the commit that upgraded the version to 0.3.10 there have been 65 commits to date in the blst main repository, which seem to include expansion of the headers. I'm not aware if using the submoduled one is something bindings MUST do, or simply there to facilitate this

yeah, just like we were doing before. The blst crate exposes the headers via environmental variables

Alright, sweet. Let's add this logic. I think it's a good idea.

What way are you suggesting we proceed ?

Maybe I misunderstood part of what you said, but I was referring to this:

To be clear, if the project is using blst >=0.3.11 use that instead of the submodule.

Where "project" is the project using these bindings.
To do that, somehow you'd falsely mark the submodule'd blst as 0.3.11.

Yes, I mean a project using these bindings. For that to work, there must be a blst release, since it's the only way to allow users to find a compatible version. I don't think we can mark the submodule's blst as 0.3.11and even if we did, these wouldn't be available to users given that the source is different

Okay haha, yeah I misunderstood. Sorry about that. When 0.3.11 comes out, let's see if it's possible to remove this manual blst compilation and let cargo do version resolution. Going to merge this PR now.


Get a list of open tabs from all devices

I love this project, great work! I read the docs, but it wasn't clear to me if this feature was available: is it possible to get a list of open tabs from all devices?
My mobile phone has 99+ tabs open, and I'd love to be able to grab them in a list or something, and maybe even "close" the tab (delete?) from my laptop.

If you run ffsclient collections you can see all available collections on your account:
NAME         LAST MODIFIED                COUNT
---------    -------------------------    -----
bookmarks    2022-09-24 00:42:06+02:00    61
clients      2022-09-23 23:28:15+02:00    0
crypto       2022-08-20 22:30:11+02:00    1
forms        2022-09-28 21:50:13+02:00    16
history      2022-09-29 00:15:40+02:00    0
meta         2022-08-20 22:30:16+02:00    1
passwords    2022-10-29 13:35:45+02:00    12
prefs        2022-09-23 10:53:58+02:00    1
tabs         2022-09-24 00:25:46+02:00    1              // <--  this is the one you want
test         2022-10-29 14:22:16+02:00    3

There is the tabs collection.
For some collections (bookmarks, password, forms, etc) exist special subcommands to work with them (eg ffsclient bookmarks list...).
Unfortunately there is currently no ffsclient tabs ... subcommand.
But you can still use the generic commands, for example:

ffsclient list "tabs" --decoded --pp to list the entries in the tabs collection (aka your open tabs) (use --format if you want them in a better format for future processing)
ffsclient delete "tabs" {id} to delete an entry (be careful, it seems that one entry in the tabs collection is an array of all tabs of one device..)
ffsclient update "tabs" {id} to delete an entry
ffsclient get "tabs" {id} --decoded --pp to get a single entry
etc (see ffsclient --help

If you want you can try to write a tabs subcommand, should not be too hard and be pretty similar to teh existing collection-specific subcommands.
But depending on your use-case ffsclient list tabs --decoded --pp could also be enough

Thanks! This answers my question and makes me excited to give this a try!


ruby/spec compliance tracking ticket

TODO: track the compliance of all core and stdlib functionality of mruby crate.

Closing now that there are milestones to track progress.


Where is react-bootstrap-table V3.0.0?

Where is react-bootstrap-table V3.0.0?
The current version in npm is 2.5.3. Since the 'milestone' achieved, where can I get the new version? @AllenFang

@hustshawn, it's on development. not yet release.. But I've no any schedule for it, cause I'm also busy on work.  Hope it can be done in near future.  If you want to contribute, just checkout to the branch of v3.0.0-dev


Map k8s storage classes on structures storage classes

Volume CR spec has storage class filed in which values like HDD, SSD etc are stored. Also during plugin installation k8s storage classes baremetal-csi-sc-hdd, baremetal-csi-sc-ssd etc are installed. Need to implement logic for switching between these storage classes. It is need to scheduler extender to make conversion between storage classes from pods volumes requests and storage classes in AC.

Not relevant anymore


Investigate Exif.mnote_data implementation

https://github.com/mamantoha/crystal-exif/blob/main/src/exif.cr#L65=
buf = uninitialized UInt8[64]

Investigate why changing the above line to this caused a memory error.
buf = uninitialized UInt8

https://github.com/mamantoha/crystal-exif/pull/11/commits/8a274256702ef2af2f219d88425339b282031373


"https" situation over Apache/Ngynx in proxy reverse configuration

Situation:

The kestrel server is running in localhost over simple "http". (http://<IP_ADDRESS>:5000)

Apache/Ngynx is configured using proxy-reverse to provide an endpoint secure to the end-user, example: https://app.domain.com -> proxy-reverse to -> http://<IP_ADDRESS>:5000

Well, lets take a look in "Unauthorized controllers".
When we put the decoration [Authorize] in some controller and try to access this controller without do the login proccess, the aspnet automatically will redirect you to the "login page", THE PROBLEM is that the THIS REDIRECT  is done using "http" unstead "https", obviously because the kestrel server is running in "http".
This wouldn't be a problem if in Apache/Ngynx we ALSO setup the endpoint http(80) making a permanent redirect to https(443), in browsers this is not noticeable BUT in PWA APP running in iOS this will cause the link opening out of the standalone browser, forcing a new browser instance of safari to be opened because http://app.domain.com has a different scope than https://app.domain.com
Another problem is if we do not setup the http(80) permanent redirection, to avoid any type of unsecure request, if we do this, the auto redirection will fail.
The aspnet core runtime uses the end-user address "app.domain.com" in your internally requests (this can be seen in /vsr/log/messages) but doesn't consider the http protocol, it is using the kestrel configuration unstead apache.
Hard to tell if this is a issue to be solved in aspnet core or just about the situation, to solve my problem I am running the kestrel facing directly de internet with certificate.

I'm moving this topic to the right repo. Sorry. :)


Mistral AI LLM Integration fixes

Description
The Mistral API key is revoked in the documentation and in the colab notebook. While working on the use case I could use the same key. I believe it needs to be revoked. Further change of the DEFAULT model for Mistral AI making it suitable for function calling.
Fixes # (issue)

API key of Mistral to be revoked

New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[x] No

Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

Thanks @lucifertrj. Please also bump the version number of the package in its pyproject.toml.

done


ws node module throws warnings when webpack'd

webpack step fails at ToT after a clean (rm node_modules, npm install, ./tools/sigh) today with error below. It's not immediately clear to me if this is due to a storageNG ramdisk dep, or devtools, or something else, see error detail below. Will seek thoughts from @piotrswigon but FYI @shans
><EMAIL_ADDRESS>build:webpack-tools /usr/local/google/home/wkorman/workspace/arcs
> webpack --config ./src/tools/webpack.config.js

Hash: e278cb663a1b8aa70f39
Version: webpack 4.41.2
Time: 11125ms
Built at: 11/22/2019 11:48:30 AM
        Asset     Size  Chunks             Chunk Names
bundle-cli.js  938 KiB       0  [emitted]  bundle-cli
Entrypoint bundle-cli = bundle-cli.js
 [13] external "crypto" 42 bytes {0} [built]
 [15] external "fs" 42 bytes {0} [built]
 [16] external "path" 42 bytes {0} [built]
 [18] external "util" 42 bytes {0} [built]
 [21] external "stream" 42 bytes {0} [built]
 [22] external "events" 42 bytes {0} [built]
 [28] external "os" 42 bytes {0} [built]
 [32] external "buffer" 42 bytes {0} [built]
 [54] external "assert" 42 bytes {0} [built]
 [56] external "http" 42 bytes {0} [built]
 [57] external "url" 42 bytes {0} [built]
 [96] external "https" 42 bytes {0} [built]
 [97] external "net" 42 bytes {0} [built]
[104] (webpack)/buildin/harmony-module.js 573 bytes {0} [built]
[105] ./build/tools/bundle-cli.js + 173 modules 1.65 MiB {0} [built]
      | ./build/tools/bundle-cli.js 1.34 KiB [built]
      | ./build/tools/bundle.js 3.85 KiB [built]
      | ./build/platform/loader.js 379 bytes [built]
      | ./build/runtime/manifest.js 54.5 KiB [built]
      | ./build/platform/assert-node.js 424 bytes [built]
      | ./build/runtime/flags.js 1.92 KiB [built]
      | ./build/runtime/interface-info.js 17.4 KiB [built]
      | ./build/runtime/schema.js 8.05 KiB [built]
      | ./build/runtime/id.js 4.18 KiB [built]
      | ./build/runtime/storageNG/drivers/driver-factory.js 2.04 KiB [built]
      | ./build/runtime/recipe/comparable.js 1.78 KiB [built]
      | ./build/runtime/storageNG/storage-key.js 804 bytes [built]
      | ./build/runtime/storageNG/store.js 2.88 KiB [built]
      | ./build/runtime/type.js 24 KiB [built]
      | ./build/runtime/recipe/type-checker.js 13.3 KiB [built]
      |     + 159 hidden modules
    + 91 hidden modules

WARNING in ./node_modules/ws/lib/buffer-util.js
Module not found: Error: Can't resolve 'bufferutil' in '/usr/local/google/home/wkorman/workspace/arcs/node_modules/ws/lib'
 @ ./node_modules/ws/lib/buffer-util.js
 @ ./node_modules/ws/lib/sender.js
 @ ./node_modules/ws/index.js
 @ ./build/platform/devtools-channel-node.js
 @ ./build/devtools-connector/devtools-connection.js
 @ ./build/devtools-connector/devtools-arc-inspector.js
 @ ./build/runtime/runtime.js
 @ ./build/runtime/storageNG/drivers/ramdisk.js
 @ ./build/runtime/manifest.js
 @ ./build/tools/bundle.js
 @ ./build/tools/bundle-cli.js

WARNING in ./node_modules/ws/lib/validation.js
Module not found: Error: Can't resolve 'utf-8-validate' in '/usr/local/google/home/wkorman/workspace/arcs/node_modules/ws/lib'
 @ ./node_modules/ws/lib/validation.js
 @ ./node_modules/ws/lib/sender.js
 @ ./node_modules/ws/index.js
 @ ./build/platform/devtools-channel-node.js
 @ ./build/devtools-connector/devtools-connection.js
 @ ./build/devtools-connector/devtools-arc-inspector.js
 @ ./build/runtime/runtime.js
 @ ./build/runtime/storageNG/drivers/ramdisk.js
 @ ./build/runtime/manifest.js
 @ ./build/tools/bundle.js
 @ ./build/tools/bundle-cli.js

I had this problem and it was fixed by npm i.
I notice your output is from webpack, so I wonder if the bug report should read _webpack failure related to ws`.
Is the idea that tools/sigh is suppose to take care of updating npm for you? I'm not clear on what the guarantees are.

Ok, so my last comment was wrong.
The error is from webpackTools section of tools/sigh I think that's why I made a bad deduction.
npm i didn't fix it at all.

Ok, these are warnings that ws causes to happen because they support optional binary packages.
https://github.com/websockets/ws/issues/1220
IIUC, we can ignore them, or we can install bufferutil and utf-8-validate for some performance gains under Node.

I'll write down what I understood:
WS library is used to connect to Arcs Explorer when running Arcs in Node (browser uses browser-provided WebSocket implementation). WS can be greatly sped up by including these 2 libraries. However both require a native component that can fail to compile depending on the developer's machine, so they are not required. @sjmiles change to the webpack config makes it explicit that we don't want webpack to include this libraries, which stops it from generating a warning. This is fine as we don't care so much about performance of the Runtime-Explorer on Node right now.

@piotrswigon what caused these errors to arise, when we hadn't seen them previously? Do you know whether an involved module was updated?

I was not able to correlate this warning with the version of webpack or ws. Are we confident these warnings just appeared now?
@shaper how did you discover them? Did you notice them in the command line, or are they blocking travis? I want to understand whether they only appeared now or whether they were there for months / days.

They appeared last week when I was building on my workstation. I don't think these blocked Travis as they were just warnings. I saw them on the command line and hadn't seen them previously, but had been building mainly on my Pixelbook for prior week or two.

I thought this was all figured out re: my comment from 3 days ago and my patch.
Why are we still talking about versions?

My understanding is that we know how to fix it, but we don't know why it surfaced only now. I presume @shaper would like to understand the relationship between this issue and the lack of package-lock.json.


GEODE-6629: Allow disk stores to be specified for region creation in V2 Management API

Co-authored-by: Jens Deppe<EMAIL_ADDRESS>Co-authored-by: Jinmei Liao<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@Petahhh For your review


Dialogue evaluation fails if entities are not tokenized in the target program

If one writes new Location("foo, bar") without a space before the comma, the contextual program will be generated correctly, but dialogue evaluation will fail with error "Program matches but slots do not", because one slot will not be tokenized.

Fixed by #464


Playlist: improve claim_search calls at bootup?

In addition to homepage categories making lots of claim_search calls (lazy-loading coming soon), playlists now calls them too.  If you have lots of playlists with lots of items each, the network load seems huge.  Given that we don't need them immediately (I think), can we postpone the call?
11s for a claim_search to load the categories is bad (not sure if it's just today's network hiccup, or due to too many calls, though).

I think that's related to your network / location in relation to the apis in the US. Hoping we can improve that soon.
Spoke with Jessop briefly and would require some redesign to make this work. Right now only non-published playlists are re-hydrated from the wallet data. At all times we need to know if something is in a playlist so the state reflects that.

This was done right?

On top of potentially stalling the important claim_searches for the homepages, it impacts the "Total Blocking Time" score for the amount of work that it does.  Also, it feels odd to load this much data for Embeds (when I have a logged in session).
Without knowing the full constraints, and probably already covered by the "redesign" remark above, here are some random suggestions:

We are currently setting collection_list to resolve only 1 claim. ,It looks like it can resolve all claims for all published collections. Can save some overhead in creating connections and doing the manual batching of promises?
Delay all of this until few seconds after bootup?

Judging from how the code only blocks the GUI until user/me is done, it doesn't seem like anything else is critical, so most likely we can delay this without significant impact.


refactor: getOraclePrivKey command

This PR is close now.
Because already apply another PR: https://github.com/medibloc/panacea-oracle/pull/27


Updated module for handling large datsets

Fixed Issue : #2
I initially started with chunking approach divided the dataset into chunks but due creation of chunks the class was becoming complex and slow
Therefore i used Dask.dataframes instead of pandas this increases memory efficiency and can handle any dataset without hindering with other functions
Darsh Agrawal , GSSoC 24 extd contributor

Actually i added this function in the original module , but since then significant changes have been made such as methods like .analyse which got inlcuded when i pulled origin before commiting , after changes were made to repo i think the module itself is not working , if you want can send you test.py to test my method , because currently the module itself is not working for me

yes @DarshAgrawal14, I can see merge conflicts. please do a git pull and have your code changes there

@ombhojane  i have resolved the issue , the PR is ready to merge

@ombhojane , If you require any changes please let me know..


Support writing large BAM files in dataflow

From @droazen on July 8, 2015 17:0
Currently tools like MarkDuplicatesDataflow use the SmallBamWriter to write their output, which makes them unable to handle large BAM outputs. We should switch to using a sharded/large BAM writer, when one materializes.
Copied from original issue: broadinstitute/hellbender#621

@iliat are you on this? (as we're assuming you are)

From @iliat on July 22, 2015 23:16
Yep, design thoughts here:
https://docs.google.com/document/d/1OHFnWD9yrWhrei-bwUHE2kLXahlcHiYryy4Qoii8PCc/edit#heading=h.6ftiho1vflb
Current state: have PoC code using HTSJDK, have DF skeleton with sharding,
etc
https://github.com/iliat/dataflow-java/blob/sharded-bam-writer/src/main/java/com/google/cloud/genomics/dataflow/pipelines/ShardedBAMWriting.java,
next step: combine the two.
Will likely ask you some questins about index merging from sharded writing
when we get to it :)
Ilia.
On Wed, Jul 22, 2015 at 6:54 PM, Adam Kiezun<EMAIL_ADDRESS>wrote:

@iliat https://github.com/iliat are you on this? (as we're assuming you
are)
—
Reply to this email directly or view it on GitHub
https://github.com/broadinstitute/hellbender/issues/621#issuecomment-123897049
.

From @iliat on August 18, 2015 17:51
Update: we have a PoC impl. working with sharded writing and simple indexing implementation in https://github.com/googlegenomics/dataflow-java/tree/sharded-bam-writer , need to do some more benchmarking and merge to main branch.

@akiezun
Current status: have this working, code here: https://github.com/googlegenomics/dataflow-java/blob/master/src/main/java/com/google/cloud/genomics/dataflow/pipelines/ShardedBAMWriting.java
Its now refactored for easier reuse in other pipelines if thats still interesting.


Fix travis ci testing

Pull Request check-list
Please make sure to review and check all of these items:

[X] Does npm test pass with this change (including linting)?
[n/a] Is the new or changed code fully tested?
[n/a] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

Description of change
Travis-CI has disabled IPv6 in their trusty images and thats why your tests failed since some time. because I rely on your work I thought it is a good idea to fix the testing. So I did :-)

@Apollon77 thanks a lot! :+1: about the changed error message: I am not sure why the message is different on Windows and on Linux. I am going to investigate that.


Adds the release announcement post for v7 of the CLI for Microsoft 365

Category

[ ] Content fix
[x] New article

Related issues
none
Contents of the Pull Request
Adds the release announcement post for v7 of the CLI for Microsoft 365

@martinlingstuyl do you need me to help here or would you like to publish this on your own?

@martinlingstuyl do you need me to help here or would you like to publish this on your own?

I'm still waiting on a review by the maintainers team...

I'll probably ask waldek to publish it, so never mind. Thanks for asking though!

[heart]         Luise Freese reacted to your message:

From: Martin Lingstuyl @.>
Sent: Thursday, September 28, 2023 10:48:42 AM
To: pnp/blog @.>
Cc: Luise Freese @.>; Comment @.>
Subject: Re: [pnp/blog] Adds the release announcement post for v7 of the CLI for Microsoft 365 (PR #1572)
I'll probably ask waldek to publish it, so never mind. Thanks for asking though!
—
Reply to this email directly, view it on GitHubhttps://github.com/pnp/blog/pull/1572#issuecomment-1738912413, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL5FMIQZQFQENXOFUMSBX4TX4VIYVANCNFSM6AAAAAA5J5LUGQ.
You are receiving this because you commented.Message ID: @.***>


Temporary anomaly - offline version created different addresses

v0.3.8
For the extent of a few random-generated mnemonics, for the same mnemonic on ETH 44/60/0/0 my offline instance generated a different set of addresses than the online page. I immediately checked and it was the offline version which diverged from the standard. I also immediately checked the HTML's SHA-256 and it matched with the one published on the site. I downloaded again, verified the signature and checked the hashes - all the same.
Maybe unfortunately, I didn't save the mnemonics because I tried 2-3 generated ones and the difference persisted, thus I didn't assign relevance to the mnemonics themselves. Again, probably unfortunately, I've overwritten the old local copy with the new one (which in theory shouldn't change anything since their hashes matched). I restarted the browser, loaded the local copy, and tried again. But the difference was gone and I couldn't reproduce the behavior since.
Any ideas what this could've been? As far as I know, my RAM and my hard drive are not corrupted.

I don't have any ideas but if you can provide steps to reproduce it I will definitely get on this as a top priority.
Can you please provide info about which browsers being used online vs offline?

I can confirm this issue.
Mnemonic: tourist oxygen junk alert ostrich stand enough kangaroo sort loop seven useless
Seed: ea2236a4af4b4c82f885330611d33434d21710c5e2f667294477850edc43376fa16e22e8ec0ed5d16ddd6dc0a1949b7bdba833c1bc1e57498343c5c90a97bace
Bip 32 Root Key: xprv9s21ZrQH143K3LR79LhQumgV1ZBzRGQmtmyzrLqkg1NWvStCRqi3KBVfdTRSDPmWsKT3dngN347nypT4YK3ocUf8wRgaFsXcLSbFQ6dYBnd
Account Extended Keys:
xprv9xkdsFeL5iATff1VCJGQ8XTyvzA4saaHfxEfLg4P7KuASRfAHZbeVmZGKBkKYyoT4boSDGaLKjTeaaxHVHuzPZGdiLwbDteWwNrinWdoG4q

xpub6BjzGmBDv5ikt95xJKoQVfQiV1zZH3J93BAG94TzffS9KDzJq6uu3ZskAVG225ptzkfNcghoHtYWZsSzXnkAtjmC7FooDsDaVjR6daLL52a

Derivation path: m/44'/0'/0'/0
BIP 32 Extended Keys:
xprv9zp75PfLV6dsCjgKHwM9gUtToDVEmF3wa4TA6CinEyABW2DFNT3Bj2R8KRH6CZY2A75bbJVgS4d4HnDHDBaiCVAuLnWDw2WEEAotjMsxpHo

xpub6DoTUuCEKUCARDknPxtA3cqCMFKjAhmnwHNktb8PoJhANpYPuzMSGpjcAgJReXcnwnMpG5Gka1TQwnG9SFJ1no1dwxpRqRCK9HF4SXmZ8iE

No changes to this point. However, the addresses generated online vs offline are different.
Online:
/0/0 1PnzwzDHSaZypfbRMN4yvwxcZMYVNt4e8g
/0/1 1AEXqJMLsjMpSYLwDKogmU22wqqv7c3cQp
/0/2 186D7Ws51EVBJpNbpmGwJiDDeiT6hedfcD
/0/3 1NxHRCeTpsZfzYNkkaCDwfUXs2MEg5Pj6d
/0/4 1357EAU2AZ1MWGGe2FLw8xA62ENYFr5yBs

Offline:
/0/0 13LrzyBEBFPmKRrQ3BvkUpqwsovDuTHUX1
/0/1 1FTVBnZoFuyJ2EvqJJSPHJGPsyNZvwhWnZ
/0/2 1EZdeYjuj14PPhvDswNLhMZ8NwbPnsfixS
/0/3 1E1cbwXrDjbCtemLKcwiwKx1RirPtsDX44
/0/4 16DxG5BBJot9Axa9RvkEqTjC4UwNmoU3ee

In Electrum, run offline, the mnemonic seed reconciles to the addresses generated in the online version of the tool.

Thanks for confirming this.
I've not been able to reproduce this under several different circumstances. They all matched the online version.

Online + chromium + bip39tool v0.3.8
Offline + firefox + bip39tool v0.3.8
Offline + chromium + bip39tool from early 2017 (commit 1e6a9f416244cf00fa41c1237973de3174fa656f)

Can you please let me know the offline browser, operating system and version of the bip39tool so I can reproduce and debug this issue.
Thanks again for confirming this.


fix(TDI-44393) : Support schema date pattern.

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-44393
Studio schema date pattern property were not used by tcompV0/Snowflake connector.
What is the new behavior?
If we receive a Date as data and DBType output is String/Text/Varchar, then we format the date to String using the given date pattern.
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: failure :x:


bug: It is possible to run compass-evm through submit_logic_call

What is happening?

Section description
Provide as much context as you can. Provide relevant software versions, screenshots, copy & paste error messages and so on.
Give as much context as you can to make it easier for the developers to figure what is happening.

compass-evm can call itself through the submit_logic_call. Right now I don't see a possible attack vector, but it's better to protect against this.
How to reproduce?

Section description
Please write detailed steps of what you were doing for this bug to appear.

Set https://github.com/palomachain/compass-evm/blob/master/contracts/Turnstone.vy#L36 to the address of the compass-evm that's actually running this submit_logic_call
What is the expected behaviour?

Section description
If you know, please write down what is the expected behaviour. If you don't know, that's ok. We can have a discussion in comments.

Providing arguments to submit_logic_call function in a way that would call itself should be prohibited and should return an error to the caller.

@webelf101 what do you need to do in order to delivery on this ticket?

@verabehr let's move this to Volume. We will need this one as well.


Added the option to return inputs + positional encodings

Hey,
I sometimes like to use layers sequentially so I added the option to add the positional encoding directly to the outputs. I wonder if you agree with the execution.
I also added a bit of typing.
Cheers

I think I got all your suggested changes.