Export to Image

Some tips how can I export images to static files? It's nice to use the same library in HTML interactive reports and in PDF version, but in PDF I need static images (e.g. SVG, PNG).

I've been looking at using pdfkit with wkhtmltopdf but haven't had success yet getting the javascript to render correctly.  I've done screenshots or print-to-pdf,  but so far haven't found a good solution for  programmatically saving a non-HTML version.  I'll keep looking into it.


Branch fix bugs

Previous Merge failed CI Checks due to issues such as no newline at EOF. This PR rectifies those issues.

Currently, checks fail due to failing testcases. I think we should go ahead and merge this so we can continue on our work for v1.2, then rewrite our testcases according to v1.2

I have fixed previously failing testcases in AddCommandParserTest. Although new mandatory fields "NRIC" and "Gender" were introduced, the tests in AddCommandParserTest (and other related classes such as PersonBuilder) were not modified to accomodate the new changes. Although bugs have been fixed, we still have to include new tests to test the new changes (such as testing for invalid gender input, etc.)


Quick Fix for pkg import path

This is caused by the lastest two merged PR 1) import path change 2) registry list (new added files but use old path)

/lgtm
Tring to merge it as this is urgent and is blocking others.

@maximilien @rhuss would you please help to review and merge it, thanks!


Relicense under dual MIT/Apache

This would make this library suitable for including in the Rust standard distribution. (Note that Rust is primarily Apache licensed - it uses the MIT only for GPLv2 compatability)

Sounds good to me. @llogiq, @rayglover agreed?

Agreed.

:+1:


Adhoc handling of custom entries for notations and improvements on plugins (VernacExtend)

To handle InCustomEntry from the AST, only consider notations with a non-empty pattern for the step context.
A single notation might yield multiple Locate results. We now iterate over all, instead of just trying the first one.
AST nodes with GenArg now (partially) support ListArg, besides ExtraArg.
Plugin for Coq-Equations is now recognized by FileContext.

Are there any simple examples to test what was changed? At least the second and third point. I believe the last one would require adding Coq-Equations to our test setup.


Add changes to prepate for moving flang to aocc3.0 sources

pgmath needs to be built with gcc 7 due to dependence on quadmath
need to add these include paths to find quadmath support in headers , for pgmath, flang, and flang_runtime
-DCMAKE_C_FLAGS=-I/usr/lib/gcc/x86_64-linux-gnu/7/include
-DCMAKE_CXX_FLAGS=-I/usr/lib/gcc/x86_64-linux-gnu/7/include"

LGTM

Can we therefore assume gcc-7 or higher across the board? That would let us remove a gcc version check in build_openmp which repeatedly breaks my local build on gcc-10.

[AMD Official Use Only - Internal Distribution Only]
I think you may have to assume gcc-7, try a later and tell me if you see issues
From: Jon Chesterfield<EMAIL_ADDRESS>Sent: Tuesday, February 23, 2021 1:51 PM
To: ROCm-Developer-Tools/aomp<EMAIL_ADDRESS>Cc: Lieberman, Ron<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [ROCm-Developer-Tools/aomp] Add changes to prepate for moving flang to aocc3.0 sources (#188)
[CAUTION: External Email]
Can we therefore assume gcc-7 or higher across the board? That would let us remove a gcc version check in build_openmp which repeatedly breaks my local build on gcc-10.

You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FROCm-Developer-Tools%2Faomp%2Fpull%2F188%23issuecomment-784429992&data=04|01|ron.lieberman%40amd.com|c4ccf4a3cff54ea4445308d8d82c06f1|3dd8961fe4884e608e11a82d994e183d|0|0|637497030896458694|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ifVNdeSsZD6da8YRQGZmb9qhJA27uC1l1Qaq2eSR5%2B4%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD3EYZ3KS77QCCEHGSAVAHLTAP2K7ANCNFSM4YBOIB3Q&data=04|01|ron.lieberman%40amd.com|c4ccf4a3cff54ea4445308d8d82c06f1|3dd8961fe4884e608e11a82d994e183d|0|0|637497030896458694|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Y%2F%2F4xzcvvddrVDucDee%2BqZp%2BzLWjHdvTzPDn%2FdIAtf8%3D&reserved=0.


Any way to specify the number of executors for the master?

Hullo :)
I can tell jenkins::slave how many executors I want, but is there any way to specify this for the master?
Cheers,
Gavin.

I've opened PR #260 that adds this feature.

#260 has been merged.


Prototype status

What's left before this loses the prototype status and is considered production ready?

I had a brief writeup recently, here it is:
couple urgent ones are:

Redesign Scan Api, there are some features missing there as well it's not really doing what it supposed to.
MultiAction batching before sending to regionserver (probably will increase performance).
Unit tests for AdminClient logic.
Merge unit test coverage with integration tests coverage (and add unit tests for the Client methods) because it currently only reports unit test coverage.
Improve documenation

Some probably needed for production:

Authentication

That's just features and doesn't account for the possible race conditions we know and don't know about. For that, I was planning to improve logic in some parts by coming up with some transactional "truths" (i.e. region is always unavailable if it has no client, region shouldn't be in region cache first and then in client cache, etc) to eliminate the possibility of races.

Thanks for the info! When you redesign the scan api, there are a couple things I would like to see:

Currently, I need to scan in "batches" and manually handle the batching myself. This is not too bad, but is sort of annoying that I have to do. Would be nice if scan handled the batching for me.
Channels! -- Currently, each scan request returns a list of results. Would be nice if I just got a channel back and then a goroutine pushed rows to that channel for me. =)

Other than that, the scan api isn't too bad.

I originally started designing the scanner using a channel, but that turned out to be annoying as I can't really pass an error back and also harder to test. I ended up with something like this instead:
// Scanner is used to read data sequentially from HBase.
// Scanner will be automatically closed if there's no more data to read,
// otherwise Close method should be called.
type Scanner interface {
	// Next returns a row at a time.
	// This method is thread safe. In case of an error, only the first call to Next()
	// will return the actual error, the subsequent calls will return io.EOF.
	// In case a scan rpc has an expired context, either io.EOF or gohbase.ErrDeadline
	// error will be returned. In such a case, clients should check the error of the
	// context they passed if they want to know why the scanner was actually closed.
	Next() (*Result, error)

	// Close closes the scanner if it is desired to stop scanning before getting all results.
	// In case all results has been delivered or in case of an error, the Scanner will be
	// closed automatically.
	Close()
}

It should address your point 1 (you don't need to worry about passing NumberOfRows and recreating the scan every time) and 2 (Next() returns a row at a time), and once I move to requesting batches from regionserver for rows that are too long, it should also address this issue: https://github.com/tsuna/gohbase/issues/40
What do you think?

@Timoha I think that's fair, though to make it more "conventional," you could do something like this:
type Scanner interface {
    // Results returns a channel of scanned rows. This channel will only receive rows that
    // are successfully scanned. Errors that occur during a scan can be accessed using the Errors channel.
    Results() <-chan *Result
    // Errors returns a channel of errors that occur during a scan.
    Errors() <-chan error
    // Done returns a channel that signals the scan's completion.
    Done() <-chan struct{}
    Close()
}

In this case, you would just use select like:
for {
    select {
    case row := <-scanner.Results():
        // Do something with the row
    case err := <-scanner.Errors():
        // Do something with the errors. It might be worthwhile to make the error that is returned a
        // custom error type that provides more info if needed. The user could then just cast the error
        // to access this info.
    case <-scanner.Done():
        break
    }
}

This is the approach taken by the context package, as well as the sarama Kafka library, so it should be fairly familiar to Go devs already.

So I don't know if that would work because we only have one error that stops the whole Scanner. There's no need to proceed the scan after the first error (as apposed to Kafka's case were you can handle that particular error and continue getting results). Maybe something like this could work instead:
type Scanner interface {
    // Results returns a channel of scanned rows. This channel will only receive rows that
    // are successfully scanned. Errors that occur during a scan can be accessed using the Errors channel.
    Results() <-chan *Result
    // Error returns error that caused the scanner to stop
    Error() error
    Close()
}

for row := range scanner.Results() {
    // Do something with the row
}
If err := scanner.Error(); err != io.EOF {
     // handle your error
}

But that might be a trickier implementation since now I need to make Error() method thread-safe. What do you think?

So channels in go don't necessarily need to be continuously scanned. They can also be used for signaling (i.e. the os.Signal func). With this in mind, you could have something like:
type Scanner interface {
    Results() <-chan *Result
    // Error returns a channel that can be used to recieve an error signal. If an error is recieved via
    // this channel, the scanner should be considered dead and no more results should be processed.
    Error() <-chan error
    Close()
}

So then you would do something like:
for {
    select {
    case row := <- scanner.Results():
        // Do something with row
    case err := <-scanner.Error():
        fmt.Println(err)
        break
    }
}

What do you think of something like that?

what's the point of that break though? If Results() channel is closed, you can assume the scanner has stopped.
having err := <-scanner.Error() also will only work if only one go routine is doing the reading of results, unless you make the read from scanner.Error() "sticky" (if error happened, every time you read it, you get the same error).

That's a fair point. If there is only ever going to be exactly one error, you could certainly get away with your above suggestion. Will you have more than one goroutine doing the scanning? If so, will each goroutine possibly throw an error?

I presume that it should return err in
func newClient(zkquorum string, options ...Option) *client{}

so users can handle the errs themself

@wanderself you can just pass context.WithTimeout() to any of the queries you are making to get gohbase.ErrDeadline error if the request is taking longer than you asked.


Error getting zone while creating subnet: cannot determine zone: please set 'zone' key in this resource or at provider level

Terraform 1.0
Terraform code
# Variables

variable "yc_token" {
  type = string
  description = "Yandex Cloud API key"
}

variable "yc_cloud_id" {
  type = string
  description = "Yandex Cloud id"
}

variable "yc_folder_id" {
  type = string
  description = "Yandex Cloud folder id"
}

# Provider

terraform {
  required_providers {
    yandex = {
      source  = "yandex-cloud/yandex"
      version = "0.61.0"
    }
  }
}

provider "yandex" {
  token     = var.yc_token
  cloud_id  = var.yc_cloud_id
  folder_id = var.yc_folder_id
}

resource "yandex_kubernetes_cluster" "zonal_cluster_resource_name" {
  name        = "MyCluster"
  description = "MyCluster description"
  network_id = "${yandex_vpc_network.this.id}"

  master {
    version = "1.17"
    zonal {
      zone      = "${yandex_vpc_subnet.subnet_resource_name.zone}"
      subnet_id = "${yandex_vpc_subnet.subnet_resource_name.id}"
    }
    public_ip = true
  }

  service_account_id      = "${yandex_iam_service_account.this.id}"
  node_service_account_id = "${yandex_iam_service_account.this.id}"
  release_channel = "STABLE"
  depends_on = ["yandex_resourcemanager_folder_iam_member.this"]
}

resource "yandex_vpc_network" "this" {}

resource "yandex_vpc_subnet" "subnet_resource_name" {
  network_id     = yandex_vpc_network.this.id
  v4_cidr_blocks = ["<IP_ADDRESS>/24"]
}

resource "yandex_iam_service_account" "this" {
  name = "k8-sa"
}

resource "yandex_resourcemanager_folder_iam_member" "this" {
  folder_id = var.yc_folder_id

  member = "serviceAccount:${yandex_iam_service_account.this.id}"
  role   = "editor"
}

Error:
yandex_iam_service_account_static_access_key.static-access-key: Destroying... [id=aje0njkb43lc1k5qkprm]
yandex_vpc_subnet.k8s-subnet-1: Destroying... [id=e9btlga2uok844valsfe]
yandex_resourcemanager_folder_iam_binding.editor: Destroying... [id=b1g972v94kscfi3qmfmh/editor]
yandex_vpc_network.this: Creating...
yandex_iam_service_account.this: Creating...
yandex_iam_service_account_static_access_key.static-access-key: Destruction complete after 8s
yandex_vpc_network.this: Creation complete after 9s [id=enpt6abuoluu82508abe]
yandex_iam_service_account.this: Creation complete after 9s [id=aje18tgata1cfe5o629v]
yandex_vpc_subnet.subnet_resource_name: Creating...
yandex_resourcemanager_folder_iam_member.this: Creating...
yandex_resourcemanager_folder_iam_binding.editor: Destruction complete after 10s
yandex_iam_service_account.admin: Destroying... [id=ajeouh8mqmntrut7gstv]
yandex_vpc_subnet.k8s-subnet-1: Still destroying... [id=e9btlga2uok844valsfe, 10s elapsed]
yandex_resourcemanager_folder_iam_member.this: Creation complete after 3s [id=b1g972v94kscfi3qmfmh/editor/serviceAccount:aje18tgata1cfe5o629v]
yandex_iam_service_account.admin: Destruction complete after 2s
yandex_vpc_subnet.k8s-subnet-1: Destruction complete after 12s
yandex_vpc_network.k8s-network: Destroying... [id=enpudqkok9vidlrva5me]
yandex_vpc_network.k8s-network: Destruction complete after 1s
╷
│ Error: Error getting zone while creating subnet: cannot determine zone: please set 'zone' key in this resource or at provider level
│
│   with yandex_vpc_subnet.subnet_resource_name,
│   on k8s.tf line 23, in resource "yandex_vpc_subnet" "subnet_resource_name":
│   23: resource "yandex_vpc_subnet" "subnet_resource_name" {
│
╵

Fix by https://github.com/yandex-cloud/docs/pull/180


⚠ AZ-Launcher has degraded performance

In 9d58a44, AZ-Launcher (https://az-launcher.nz/) experienced degraded performance:

HTTP code: 200
Response time: 2322 ms

Resolved: AZ-Launcher performance has improved in eb7072d.


feat(overlay): add connected position strategy

R: @hansl @robertmesserle @kara
I'm still missing tests for ViewportRuler, but I wanted to get the review started while I work on those.
(and also see if this passes on CI)

Added tests for ViewportRuler.

Tests are green now. Swapped the browser setup to use iOS8 instead of iOS7

Done reviewing. Just a few typos and questions, but looks good to me. @hansl, @robertmesserle ?


Add support to move NetBox Data Flows to plugins submenu

With default to False let user to reincarnate the current menu placement with:
PLUGINS_CONFIG = {
    'netbox_data_flows': {
        'top_level_menu': True,
    },
}

Plugin supporting this is for example netbox-acls (for inspiration).

Thanks for your suggestion. I'll add that option, but default to True as that seems to me more in line with the direction of NetBox's design to have many specialized sections.


Vendor Status Code Mismatch

Where are the VendorStatus codes coming from. There are a handful of codes that don't match anything that I can find. For example, VendorStatus::InvalidParameters is defined as 0x42. But based on the BLE spec, 0x42 should be UnknownAdvertisingIdentifier and based on the STM32 documentation (https://github.com/STMicroelectronics/STM32CubeWB/blob/master/Middlewares/ST/STM32_WPAN/ble/core/doc/STM32WB_BLE_Wireless_Interface.html), InvalidParameters should be 0x92.

I want to make sure I am not missing some data source that was used to generate these. If it is just mistakes, I will cross-reference the documents and make the appropriate changes.

hello @TaylorCarpenter
this repo is originally a fork of bluetooth-hci with the vendor-specific commands and events found in eupn's stm32wb55 and async support applied on top.
As for references, I mainly use the ST repo, but I have not double-checked everything.
I appreciate you pointing that out, and you seem to be correct, so feel free to open a PR


Feature Request:  conditions should be classed

Feature Idea
If the function signals a condition I want to know its class, so I can tell it apart from other conditions, and selectively handle them from a higher level.
Relevant Input
N/A
Relevant Output
N/A
Reproducible Example/Pseudo Code
e.g.
warn_if_something_bad()  should throw a condition that has classes warning, admiral.warning and admiral.warning.something_bad.
I want to be able to do:
withCallingHandlers({
    doing_a_task()
},
`admiral.warning.something_bad` = \(w){
    log_this(w)
}
`admiral.warning.something_else_bad` = \(w){
    # ignore... try restart... etc.
})

This would be a great enhamcement @sadchla-codes @zdz2101.

[ ] First step is identifying the functions that need to be updated


Add bytes <> string conversion

Add a way to convert  StaticArray to string and vice-versa

One on the function you want already exists in mass-as-sdk https://github.com/massalabs/massa-as-sdk/blob/4a8be29e13952096a117e4a21a272fe0b45d55f8/assembly/std/index.ts#L327

And the second one is just below: https://github.com/massalabs/massa-as-sdk/blob/4a8be29e13952096a117e4a21a272fe0b45d55f8/assembly/std/index.ts#L338


Provide warnings for toc.yml files where displayName nodes are invalid

Suggestion, provide warnings for toc.yml files where displayName nodes are invalid:
In toc.yml files, if a displayName node exists where the node it is decorating only contains items, the displayName is not
actually used. In other words, the displayName is only valid on nodes that have an href.
Example
These are two examples of valid displayName nodes.
- name: Top level section
  items:
  - name: Overview
    displayName: values,in the,display name here, are actually, valid,since they are directly,tied to an,href
    href: overview.md
  - name: Secondary node
    items:
    - name: Overview
      displayName: these,values,are,valid too
      href: ../core/sdk.md
    - name: Some section
      items:
      - name: Another file
        href: ../core/tools/dir/another--file.md
      - name: Some file
        href: ../core/tools/dir/some-file.md

However, if someone was to add a displayName to the "Top level section" we should warn the author that their displayName is invalid, and will have no effect. It is completely useless.
- name: Top level section
  displayName: this,is pointless,warn me about, it please # This will not work, no HREF
  items:
  - name: Overview
    displayName: values,in the,display name here, are actually, valid,since they are directly,tied to an,href
    href: overview.md
  - name: Secondary node
    items:
    - name: Overview
      displayName: these,values,are,valid too
      href: ../core/sdk.md
    - name: Some section
      items:
      - name: Another file
        href: ../core/tools/dir/another--file.md
      - name: Some file
        href: ../core/tools/dir/some-file.md

AB#325494

Going forward, validation should be done in build, not directly in the authoring pack. We'll consider this when/if we prioritize TOC validation, but low priority for now.


CMAKE failed because it is missing:  TCMALLOC_LIBRARY TCMALLOC_INCLUDE_DIR

I am trying to build hpx with the following command it cause an error as follow:
cmake .. -DBOOST_ROOT=/usr/lib/x86_64-linux-gnu/  -DHWLOC_ROOT=/home/runtime_systems/hwloc-1.10.1/install/lib -DCMAKE_INSTALL_PREFIX=/home/runtime_systems/hpx/install
build failed as follow:
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26")
-- Could NOT find TCMalloc (missing:  TCMALLOC_LIBRARY TCMALLOC_INCLUDE_DIR)
CMake Error at cmake/HPX_Message.cmake:43 (message):
ERROR: HPX_WITH_MALLOC was set to tcmalloc, but tcmalloc could not be
found.  Valid options for HPX_WITH_MALLOC are: system, tcmalloc, jemalloc,
tbbmalloc, and custom
Call Stack (most recent call first):
cmake/HPX_SetupAllocator.cmake:29 (hpx_error)
CMakeLists.txt:1308 (include)
-- Configuring incomplete, errors occurred!
See also "/home/runtime_systems/hpx/my_hpx_build/CMakeFiles/CMakeOutput.log".
See also "/home/runtime_systems/hpx/my_hpx_build/CMakeFiles/CMakeError.log"
Any advice on how to solve it?
Thanks,
Rabab

Hi Rabab,
The error message says:
ERROR: HPX_WITH_MALLOC was set to tcmalloc, but tcmalloc could not be
found.  Valid options for HPX_WITH_MALLOC are: system, tcmalloc, jemalloc,
tbbmalloc, and custom
The resolution is as as simple as either switching the allocator (system does
not have any additional dependencies) or install the necessary packages.
Either by hand or from your linux distribution. tcmalloc is often found as
part of gpertools, based on the distribution, you might need to install the -
dev packages as well.
On Montag, 27. Februar 2017 11:58:58 CET Rabab53 wrote:

I am trying to build hpx with the following command it cause an error as
follow: cmake .. -DBOOST_ROOT=/usr/lib/x86_64-linux-gnu/
-DHWLOC_ROOT=/home/runtime_systems/hwloc-1.10.1/install/lib
-DCMAKE_INSTALL_PREFIX=/home/runtime_systems/hpx/install
build failed as follow:
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26")
-- Could NOT find TCMalloc (missing:  TCMALLOC_LIBRARY TCMALLOC_INCLUDE_DIR)
CMake Error at cmake/HPX_Message.cmake:43 (message):
ERROR: HPX_WITH_MALLOC was set to tcmalloc, but tcmalloc could not be
found.  Valid options for HPX_WITH_MALLOC are: system, tcmalloc, jemalloc,
tbbmalloc, and custom
Call Stack (most recent call first):
cmake/HPX_SetupAllocator.cmake:29 (hpx_error)
CMakeLists.txt:1308 (include)
-- Configuring incomplete, errors occurred!
See also
"/home/runtime_systems/hpx/my_hpx_build/CMakeFiles/CMakeOutput.log". See
also "/home/runtime_systems/hpx/my_hpx_build/CMakeFiles/CMakeError.log"
Any advice on how to solve it?
Thanks,
Rabab

@Rabab53 to clarify: try using cmake -DHPX_WITH_MALLOC=system ...

@sithhell we should probably change our build system to fall back to system if tcmalloc is not available.

On Montag, 27. Februar 2017 12:52:53 CET Hartmut Kaiser wrote:

@sithhell we should probably change our build system to fall back to
system if tcmalloc is not available.

I am opposing that. I played with that thought for a long time but dismissed
it. The rationale is that we shouldn't silently fall back to a suboptimal
solution, I was hoping that the error message is clear enough.
While I agree that defaulting to tcmalloc is arbitrary, the need for a high
performance malloc implementation is absolutely there so I chose to have a
hard failure to make the user aware of the implications instead of silently
falling back to a solution which might lead to bad performance.
We might need to document it more prominently here:
http://stellar-group.github.io/hpx/docs/html/hpx/manual/build_system/
prerequisites.html

Ok, fair enough.

Since it is very easy to install jemalloc, and it gives as good, or better performance as tcmalloc, we could simply extend the error message to output the following
You have requested a non system malloc, but it was not found, you may install jemalloc as follows
JEMALLOC_VER=4.4.0
wget https://github.com/jemalloc/jemalloc/releases/download/$JEMALLOC_VER/jemalloc-$JEMALLOC_VER.tar.bz2
tar -xjf jemalloc-$JEMALLOC_VER.tar.bz2
cd jemalloc-$JEMALLOC_VER
./autogen.sh --prefix=$HOME/local/jemalloc/$JEMALLOC_VER
make -j -k install

and invoke cmake with the extra options
cmake -DHPX_WITH_MALLOC=JEMALLOC -DJEMALLOC_ROOT=$HOME/local/jemalloc/$JEMALLOC_VER

and update the error message from time to time when a newer jemalloc is available

I'd rather put a (stable) link to our documentation into the error message where this is described in detail.

Thanks all

@Rabab53 Can we close this issue now? Has it been resolved for you?

I see where @ZiCog is coming from... on Ubuntu 18.04.2:
$ sudo apt search tcmalloc
Sorting... Done
Full Text Search... Done
libtcmalloc-minimal4/bionic,now 2.5-2.2ubuntu3 amd64 [installed]
  efficient thread-caching malloc
$

(and cmake fails to find TCMalloc)
There are no -dev packages.
$ sudo apt search jemalloc
Sorting... Done
Full Text Search... Done
libjemalloc-dev/bionic 3.6.0-11 amd64
  development files and documentation for jemalloc

libjemalloc1/bionic 3.6.0-11 amd64
  general-purpose scalable concurrent malloc(3) implementation

and
$ sudo apt install libjemalloc-dev
...
$ cmake -DHPX_WITH_MALLOC=jemalloc ...

does the trick.

A simple google search would have revealed that the corresponding -dev package on Ubuntu is named libgoogle-perftools-dev.

@ZiCog  I'm using Arch destro [manjaro]. Here I installed gperftools package to satisfies the tcmalloc dependencies.
sudo pacman -S gperftools .


Coveralls should ignore test folder

Coveralls should ignore the test folder. The goal of this PR is to solve this issue.

This PR is related to a discussion: https://github.com/stympy/faker/pull/1209


DBZ-4710: 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 omitted 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
[2] https://issues.redhat.com/browse/DBZ-4710

Applied, thx!

Thanks for taking this up so quickly @gunnarmorling.


Question about self.accelerator.backward(loss)

I think what you want to do is to accumulate the gradient here. However, the loss back-propagated seems not the one accumulated.

I mean, is there anything wrong with the line 1016?
Using self.accelerator.backward(total_loss) seems better.

oh in this way, it seems like "gradient_accumulate_every " not work

yea, total loss is just for logging

yea, total loss is just for logging

I got your point. loss.backward() will automatically accumulate the gradients if there is no opt.zero_grad(). I misunderstood it at that time.


Feature flag implementation to delegate to IMPROVED_POM_SUPPORT

If the nebula.features.coreBomSupport feature flag is enabled, the user is expected to add enableFeaturePreview('IMPROVED_POM_SUPPORT') to settings.gradle. The nebulaRecommenderBom configuration will have almost every configuration extend from it (exceptions: provided, nebulaRecommenderBom, archives) so bom dependency versions are available in all the usual places users define dependencies.
For subprojects, the nebulaRecommenderBom configuration will be copied to that project and almost every configuration will extendFrom the copied configuration.

Coverage decreased (-4.9%) to 81.071% when pulling 54d55b0148199b23f43f1a1f01b78d7bfa1df13f on sghill:core-bom-support into fa19ad840fa68a4a0bde6699d9eefe30b45a2a11 on nebula-plugins:master.


github pages example for sys.dict modules

Add an example into python_from_rust.md for creating a module and inserting it into the sys.modules dictionary.
As discussed here:
GH-2649 example for inserting moulde in sys.dict

I've force-pushed to update this & address feedback, will now merge. Thanks again!

bors r+


want to add route and controller for setting shareable link in Product

@Trisha-tech , can i create the route and controller for the shareable link. This enhancement will empower users to efficiently manage and share product links, enhancing the accessibility and visibility of products.

@Trisha-tech , can i create the route and controller for the shareable link. This enhancement will empower users to efficiently manage and share product links, enhancing the accessibility and visibility of products.

Hello @Naman197 , Go for it
All the Best


Can't activate the extension

I'm in Windows 7 with Chrome and chrome as it disabled as it is not from their won store and it is not possible to activate it.
https://support.google.com/chrome_webstore/answer/2811969?visit_id=637067312512468782-2204705331&p=ui_remove_non_cws_extensions&hl=en&rd=2

Is your developer option 'ON' ?

Yes developer mode is on.

I use chrome in Ubuntu. It got no issues like this. I believe chrome has made some upgrades to block apps that are not downloaded from chrome store. I'll check the issue with Windows PC and will definitely give you an update on this issue itself. Meantime we can keep the issue open

Just an update. The issue is the same on Win 10

Noted

I've released a new version with a zip version tagged as v0.0.2 and updated the installation instructions. Please check.


[INTEL MKL] MKL DNN 0.x code cleanup - FusedBatchNorm op

DNN 0.x cleanup of MKL FusedBatchNorm op:
(1) Remove all DNN 0.x related code;
(2) Replace all DNN 1.x macro usages

@gzmkl Can you please resolve conflicts? Thanks!

@gbaned.  There was a recent commit (by my teammate at Intel) on the same source file. That commit had changes which
did not clean up DNN 0.x code block (also DNN 1.x macros are still used).  I will rebase and then re-do the clean-up.
Thanks!

@gbaned Also, the following PR has to go first as part of Tensorflow 2.4 release.
https://github.com/tensorflow/tensorflow/pull/43504
The above PR does a lot of change in the same source file tensorflow/core/kernels/mkl/mkl_fused_batch_norm_op.cc.
So I may need to wait a couple of weeks before I can rebase and do cleanup. I will notify you once it is ready.

@gzmkl Thank you for the note! I just approved #43504. It should be merged in a day or two if there's no problem.

@penpornk Thank you for letting me know!

@gzmkl  FYI, #43504 is merged.

@gzmkl Can you please resolve conflicts? Thanks!

@gbaned  Because there are a lot of changes in a recent merged PR (related to MKL native format support) on the same source file mkl_fused_batch_norm_op.cc, I am in the process of getting approval of an INTERNAL PR. Once it is done, I will submit a new PR to replace this one.  Thanks!

@penpornk @gbaned  Hi, I have done any round of cleanup after rebase with PR #43504 changes. So this one shall be fine and there is no need to submit a new PR.  Thanks!


what's the differences between aliyun ecs CreateInstance and aliyun ecs RunInstances ?

what's the differences between aliyun ecs CreateInstance and aliyun ecs RunInstances ?

We don’t know. For API issues, please ask ECS customer service staff.


Webpack -p [WDS] Disconnected! Safari

Hello, thank you for the boilerplate! I am using it for a proof of concept.
Using Webpack -p I FTP'd index.html / bundle.js (it's a simple app)
I loaded my project on several iOS devices (android / windows seem to be working) and the page is blank white, using Ghostlab I inspected and the console spits out [WDS] Disconnected! seveal times (once every 10 seconds)
Can you advise? Thanks!
package.json

{
  "name": "react-hot-boilerplate",
  "version": "1.0.0",
  "description": "Boilerplate for ReactJS project with hot code reloading",
  "scripts": {
    "start": "node server.js",
    "lint": "eslint src"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/gaearon/react-hot-boilerplate.git"
  },
  "keywords": [
    "react",
    "reactjs",
    "boilerplate",
    "hot",
    "reload",
    "hmr",
    "live",
    "edit",
    "webpack"
  ],
  "author": "Dan Abramov<EMAIL_ADDRESS>(http://github.com/gaearon)",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/gaearon/react-hot-boilerplate/issues"
  },
  "homepage": "https://github.com/gaearon/react-hot-boilerplate",
  "devDependencies": {
    "babel-core": "^6.0.20",
    "babel-eslint": "^4.1.3",
    "babel-loader": "^6.0.1",
    "babel-preset-es2015": "^6.0.15",
    "babel-preset-react": "^6.0.15",
    "babel-preset-stage-0": "^6.0.15",
    "eslint-plugin-react": "^3.6.2",
    "react-hot-loader": "^1.3.0",
    "webpack": "^1.12.2",
    "webpack-dev-server": "^1.12.1"
  },
  "dependencies": {
    "css-loader": "^0.23.0",
    "flux": "^2.1.1",
    "jquery": "^2.1.4",
    "moment": "^2.10.6",
    "radium": "^0.15.3",
    "react": "^0.14.0",
    "react-dom": "^0.14.0",
    "react-widgets": "^3.1.3",
    "style-loader": "^0.13.0"
  }
}

webpack.config.js

var path = require('path');
var webpack = require('webpack');

module.exports = {
  devtool: 'eval',
  entry: [
    'webpack-dev-server/client?http://localhost:3000',
    'webpack/hot/only-dev-server',
    './src/index'
  ],

  output: {
    path: path.join(__dirname, 'dist'),
    filename: 'bundle.js',
    publicPath: '/static/'
  },
  plugins: [
    new webpack.HotModuleReplacementPlugin()
  ],
  module: {
    loaders: [{
      test: /\.js$/,
      loaders: ['react-hot', 'babel'],
      include: path.join(__dirname, 'src')
    }, {
      test: /\.css$/,
      loader: "style-loader!css-loader"
    }, {
      test: /\.gif$/,
      loader: "url-loader?mimetype=image/png"
    }, {
      test: /\.woff(2)?(\?v=[0-9].[0-9].[0-9])?$/,
      loader: "url-loader?mimetype=application/font-woff"
    }, {
      test: /\.(ttf|eot|svg)(\?v=[0-9].[0-9].[0-9])?$/,
      loader: "file-loader?name=[name].[ext]"
    }, ]
  }
};

You might have better luck asking this on Webpack repos.
This repo is just for hot reloading but it relies on Webpack for transport (such as the actual connection logic).


nixos/i2c: add module to set up i2c permissions

Motivation for this change
This is a very simple module that installs a single udev.
The rule set the ownership of all /dev/i2c-* devices to a
group, "i2c" by default but can be changed.
Fix issue #91771
Things done

[x] Tested on NixOS via hardware.i2c.enable = true
[x] Built NixOS manual
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Was using "TAG+=uaccess" considered? Thoughts?

Was using "TAG+=uaccess" considered? Thoughts?

No, but it's a good idea to add it, thanks. I wouldn't rely entirely on it, though: it's still not a documented feature of logind and a group is necessary for daemons.

@bjornfor I added the uaccess tag.

@rnhmjoj: In that case, maybe update the docs to reflect the fact that any logged in user will have access?

Done. Thank you, again.


robot-name: Require uppercase letters

Update robot-name to allow only uppercase letters. This keeps the xcpp
track updated with the current instructions. See exercism/x-common#283

Sweet, thanks!
@LegalizeAdulthood Would you mind having a look at this one when you have time?

Looks good, thanks for the fix!


Update userdata.sh.tpl with node_labels based on ondemand/spot detection

PR o'clock
Description
In order to detect wheter an instance is running ondemand or spot I integrated a small detection logic from @pahud.
This is a change based on this template:
https://github.com/pahud/eks-templates/blob/master/cloudformation/nodegroup.yaml
This will allow us to use his eks lambda drainer in the future:
https://github.com/pahud/eks-lambda-drainer
This change is also relevant for the mixed instances pull request because once you have a mixed fleet you want to know which instances are ondemand or spot:
https://github.com/terraform-aws-modules/terraform-aws-eks/pull/222
Checklist

[ ] terraform fmt and terraform validate both work from the root and examples/eks_test_fixture directories (look in CI for an example)
[ ] Tests for the changes have been added and passing (for bug fixes/features)
[ ] Test results are pasted in this PR (in lieu of CI)
[ ] I've added my change to CHANGELOG.md
[ ] Any breaking changes are highlighted above

Hi @runningman84
Thanks for the PR!
There's nothing preventing these being added in kubelet_extra_args on a per worker group basis right now. Do you think every user will want these labels and taints applied to their clusters by default?
I'm open for opinions!

Hi @runningman84
Thanks for the PR!
There's nothing preventing these being added in kubelet_extra_args on a per worker group basis right now. Do you think every user will want these labels and taints applied to their clusters by default?
I'm open for opinions!

I think once https://github.com/terraform-aws-modules/terraform-aws-eks/pull/222 is merged you will see a lot of setups where you have a mixed fleet of instances. Therefore it is important to know which instance is ondemand and which instance is spot. An extra arg per worker group would not work because it would use the same arg for spot and on demand.
The question is what is the best name for the label?
https://github.com/pusher/k8s-spot-rescheduler uses:
--on-demand-node-label (default: node-role.kubernetes.io/worker) Name of label on nodes to be considered for draining.
--spot-node-label (default: node-role.kubernetes.io/spot-worker) Name of label on nodes to be considered as targets for pods.
Maybe we should make the label configurable...

Maybe we should make the label configurable...

Definitely.

it is important to know which instance is ondemand and which instance is spot. An extra arg per worker group would not work because it would use the same arg for spot and on demand.

Understood.
I'm hoping either AWS themselves or one of the k8s projects will provide some direction here. Either by adding labels/taints by default, e.g. like beta.kubernetes.io/instance-type and failure-domain.beta.kubernetes.io/zone etc, or something from AWS in their bootstrap or at least in their own CFN templates.

I will comment here, feel free to add your input too! https://github.com/awslabs/amazon-eks-ami/issues/85

I would recommend not to merge this PR

Agreed. I don't think we want to force some taints on everyone using spot instances.
For future reference, this can be achieved with something like this for additional_userdata:
iid=$(curl -s http://<IP_ADDRESS>/latest/meta-data/instance-id)
export AWS_DEFAULT_REGION=${AWS::Region}
ilc=`aws ec2 describe-instances --instance-ids  $iid  --query 'Reservations[0].Instances[0].InstanceLifecycle' --output text`
...
echo "--node-labels=spotfleet=xxx --register-with-taints=spotInstance=true:PreferNoSchedule" > /etc/systemd/system/kubelet.service.d/30-kubelet-extra-args.conf
systemctl start kubelet


dashboards: Add dashboard to grafana.com

[x] Make dashboard easily importable with minimal changes (e.g. data source)
[x] Add/Upload it to https://grafana.com/grafana/dashboards/
with screenshots, explanation and link to this repo

Added links in https://github.com/Kuadrant/gateway-api-state-metrics/commit/9a87069dc05fd8f2f7bb98d0980f7fce48422a90


Don't support thai langulage

Don't support thai langulage
Tell us about your environment:

Puppeteer version: 1.11.0
Platform / OS version: CentOS7
URLs (if applicable):
Node.js version: 8.4.0

** What steps will reproduce the problem? **
I already checked Troubleshooting.
And install many fonts package, just like "fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst ttf-freefont" and "https://www.ezylinux.com/add-fonts-thai-ใน-linux-กัน/".
When I screenshot some html, the thai langulage show not good :(

What is the expected result?

@3fuyu Generally, all font problems should be resolvable by installing the right font package. What's your page URL?

@aslushnikov My page is normal which include thai langulage, I also think it's a font problem. But I already install packages from Troubleshooting and yum groupinstall thai-support also useless. Can you give me some ideas for solve this problem? Thanks very much :)

My page is normal which include thai langulage

@3fuyu Would you mind sharing the page? I might be able to try something myself and see what works.

Can you give me some ideas for solve this problem?

Not really - I haven't had any experience with Thai fonts.

@aslushnikov Any include thai langulage page was failed. Just like
http://www.thai-language.com/default.aspx?nav=control
My engine result

The Troubleshooting's dependents is not enough. I install many ttf fonts and solve this problem. It's close, thanks.

Just install the following fonts and it should fix it
sudo apt-get install -y fonts-thai-tlwg-ttf


Timex.from_unix inconsistent behavior

Steps to reproduce
iex> Timex.from_unix<PHONE_NUMBER>000
%Inspect.Error{message: "got ArgumentError with message \"argument error\" while inspecting \e[39m%{\e[0m\e[33m\e[36m__struct__: \e[0m\e[33m\e[36mDateTime\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mcalendar: \e[0m\e[33m\e[36mCalendar.ISO\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mday: \e[0m\e[33m27\e[39m,\e[0m\e[33m \e[36mhour: \e[0m\e[33m1\e[39m,\e[0m\e[33m \e[36mmicrosecond: \e[0m\e[33m\e[39m{\e[0m\e[33m0\e[39m,\e[0m\e[33m 0\e[39m}\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mminute: \e[0m\e[33m46\e[39m,\e[0m\e[33m \e[36mmonth: \e[0m\e[33m9\e[39m,\e[0m\e[33m \e[36msecond: \e[0m\e[33m40\e[39m,\e[0m\e[33m \e[36mstd_offset: \e[0m\e[33m0\e[39m,\e[0m\e[33m \e[36mtime_zone: \e[0m\e[33m\e[32m\"Etc/UTC\"\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mutc_offset: \e[0m\e[33m0\e[39m,\e[0m\e[33m \e[36myear: \e[0m\e[33m33658\e[39m,\e[0m\e[33m \e[36mzone_abbr: \e[0m\e[33m\e[32m\"UTC\"\e[0m\e[33m\e[39m}\e[0m\e[33m"}
iex> Timex.from_unix -1000000000000
** (ArgumentError) invalid Unix time -1000000000000
    (elixir) lib/calendar.ex:1459: DateTime.from_unix!/2

Description of issue
I think the behavior in these two different out of bound situation should be consistent (i.e. raise an error).

Ah, after more experiments, I realized these inconsistent is from Elixir's DateTime module.
iex> DateTime.from_unix -1000000000000
{:error, :invalid_unix_time}
iex> DateTime.from_unix<PHONE_NUMBER>000
{:ok,
 %Inspect.Error{message: "got ArgumentError with message \"argument error\" while inspecting \e[39m%{\e[0m\e[33m\e[36m__struct__: \e[0m\e[33m\e[36mDateTime\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mcalendar: \e[0m\e[33m\e[36mCalendar.ISO\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mday: \e[0m\e[33m27\e[39m,\e[0m\e[33m \e[36mhour: \e[0m\e[33m1\e[39m,\e[0m\e[33m \e[36mmicrosecond: \e[0m\e[33m\e[39m{\e[0m\e[33m0\e[39m,\e[0m\e[33m 0\e[39m}\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mminute: \e[0m\e[33m46\e[39m,\e[0m\e[33m \e[36mmonth: \e[0m\e[33m9\e[39m,\e[0m\e[33m \e[36msecond: \e[0m\e[33m40\e[39m,\e[0m\e[33m \e[36mstd_offset: \e[0m\e[33m0\e[39m,\e[0m\e[33m \e[36mtime_zone: \e[0m\e[33m\e[32m\"Etc/UTC\"\e[0m\e[33m\e[39m,\e[0m\e[33m \e[36mutc_offset: \e[0m\e[33m0\e[39m,\e[0m\e[33m \e[36myear: \e[0m\e[33m33658\e[39m,\e[0m\e[33m \e[36mzone_abbr: \e[0m\e[33m\e[32m\"UTC\"\e[0m\e[33m\e[39m}\e[0m\e[33m"}}

I probably should report this issue to elixir-lang/elixir. Sorry for bothering you.


Prepare and deploy 4.15.1 release

[x] update version in setup.py and hxl/__init__.py
[x] check CHANGELOG
[x] test in clean virtualenv
[x] merge to test and push
[x] update in beta Proxy and run unittests
[x] merge to master and push
[x] create libhxl PyPi release
[x] wait until the new release is visible on PyPi
[ ] add git tag
[ ] create GitHub release

PyPi release: https://pypi.org/project/libhxl/4.15.1/

GitHub release: https://github.com/HXLStandard/libhxl-python/releases/tag/4.15.1


JS bugs

verify the field population when you hit "edit" from the posts page
search pre-pop stopped working this was only because I tried using hash tags instead of regular tags

enable hash tags by encoding/decoding the hash before dumping it into the URL

Fixed


SCAN command returns keys of expired objects

After setting an object and letting it expire, when running the SCAN command, Garnet still lists the key, while Redis does not.
This causes issues with RedisInsight and Another Redis Desktop Manager as they will run the TYPE command on each returned item from the SCAN command. The TYPE command bug is addressed in #150, however, even with this fix, in RedisInsight, the expired keys will show as having "No limit", and it'll show an error saying that the key with that name does not exist.
Using version 1.0.1, compiled in VS2022 in Release/Any CPU mode and using the .NET 8 version.
Garnet:

Redis:

RedisInsight error:

My original tests were on Windows 11, using .NET 8.0.3 and VS 2022 Preview 17.10 Preview 1. I'm also able to replicate this using redis-cli with Garnet running on Ubuntu 22.04.3 LTS with .NET 8.0.3 in Release mode.

Encountered the same issue, any progress?
is it fixed by https://github.com/microsoft/garnet/pull/150 ?

Hi @ClericPy this issue isn't fixed by #150, this is a different issue related to the SCAN command.

Hi @ClericPy this issue isn't fixed by #150, this is a different issue related to the SCAN command.

So sorry I got a mistake, I used garnet 1.0 and expire not work. Used redispy & redis long time ago, and the code didn't changed. These days I noticed that the keys were not automatically purged according to their expire time when using db0

Hi @ClericPy this issue isn't fixed by #150, this is a different issue related to the SCAN command.

So sorry I got a mistake, I used garnet 1.0 and expire not work. Used redispy & redis long time ago, and the code didn't changed. These days I noticed that the keys were not automatically purged according to their expire time when using db0

Yes, this is the same issue, keys aren't automatically purged in the list after their expiry time.

Hi @ClericPy this issue isn't fixed by #150, this is a different issue related to the SCAN command.

So sorry I got a mistake, I used garnet 1.0 and expire not work. Used redispy & redis long time ago, and the code didn't changed. These days I noticed that the keys were not automatically purged according to their expire time when using db0

Yes, this is the same issue, keys aren't automatically purged in the list after their expiry time.

I don't know why this issue hasn't received much attention. Logically, there shouldn't be a shortage of users for this database, and the usage of TTL caching should be quite frequent.

Hi @ClericPy this issue isn't fixed by #150, this is a different issue related to the SCAN command.

So sorry I got a mistake, I used garnet 1.0 and expire not work. Used redispy & redis long time ago, and the code didn't changed. These days I noticed that the keys were not automatically purged according to their expire time when using db0

Yes, this is the same issue, keys aren't automatically purged in the list after their expiry time.

I don't know why this issue hasn't received much attention. Logically, there shouldn't be a shortage of users for this database, and the usage of TTL caching should be quite frequent.

By the way, is there a temporary solution without experimentation that can solve the problem of having 30 million expired keys stored now:
scan all keys and manually determine expire and then manually clear them

Hi @TedHardMs,
The issue has been fixed for strings, but it's still showing expired data structures (please refer to screenshost)

This has been resolved for strings. Thank you @TedHartMs


chore(deps): update dependency eslint-plugin-react to v7.18.3

This PR contains the following updates:

Package
Type
Update
Change

eslint-plugin-react
devDependencies
minor
7.17.0 -> 7.18.3

Release Notes

yannickcr/eslint-plugin-react
v7.18.3
Compare Source
Fixed

[jsx-indent][]: don't check literals not within JSX (#2564 @toshi-toma)

v7.18.2
Compare Source
Fixed

[jsx-indent][]: avoid a crash on non-string literals (#2561 @ljharb)

v7.18.1
Compare Source
Fixed

[jsx-indent][]: Does not check indents for JSXText (#2542 @toshi-toma)
[jsx-props-no-spreading][]: add support for namespaced jsx components (#2534 @jonathanpalma)
[jsx-no-target-blank][]: allow rel to be an expression (#2544 @odinho)
[sort-comp][]: | isn’t a valid regex flag; u and s are (@ljharb)

Changed

[Docs] use markdown-magic to automatically sort all rules alphabetically (#1742 @ybiquitous)
[Docs][jsx-props-no-spreading][]: fix typo to use correct rule (#2547 @jonggyun))

v7.18.0
Compare Source
Added

[require-default-props][]: add option to ignore functional components (#2532 @RedTn)
[function-component-definition][]: Enforce a specific function type for function components (#2414 @Stefanwullems)
[no-adjacent-inline-elements][]: Prevent adjacent inline elements not separated by whitespace (#1155 @SeanHayes)
[jsx-no-script-url][]: prevent usage of javascript: URLs (#2419 @sergei-startsev)

Fixed

[jsx-pascal-case][]: false negative with namespacing (#1337 @mfyuce)
[jsx-curly-brace-presence][]: Fix curly-brace-presence edge cases (#2523 @rafbgarcia)
[prop-types][]: Does not validate missing propTypes for LogicalExpression (#2533 @toshi-toma)
[no-unknown-property][]: allowTransparency does not exist in React >= v16.1 (#1538 @dawidvdh)
[jsx-curly-brace-presence][]: Fix error related to tags line break (#2521 @rafbgarcia)
[no-typos][]: Compilation error when method name is string instead of identifier (#2514 @shijistar)
[jsx-curly-brace-presence][]: allow trailing spaces in TemplateLiteral (#2507 @doochik)
[no-unused-prop-types], [no-unused-state]: fix false positives when using TS type assertions (#2536 @kdmadej)

Changed

[Docs][no-render-return-value][]: Fix title (#2540 @micnic)
[Refactor]: remove unused codes in util/propTypes (#2288 @golopot)
[no-typos]: check static lifecycle methods (#2006 @bsonntag)
[Docs][jsx-first-prop-new-line][]: Fix rule name in "Rule Options" section (#2535 @barreira)
[Tests][no-unused-prop-types][]: Added test cases (#977 @dozoisch)
[Tests] avoid running tests on pretest job
[meta] Move eslint-plugin-eslint-plugin to devDeps (#2510 @nstepien)
[Deps] update array-includes, object.entries, object.fromentries, object.values, resolve

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 2.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix NetApp

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.NetApp


Automatically create an Issue on failed scheduled builds

This should add an issue like this when the ICI fails in a scheduled build.
See workflow run here, where I artificially introduced a build error.
The issues data could be modified (title, labels, description...) but I would need input for that.

What I'm wondering about: If a downstream test is flaky, we will get a new issue every day?

can we parse from ICI, which package failed in which state?
can we check if an issue exists already, for example "Test failure for webots"? Like dependabot is not posting duplicates.

Maybe we can additionally look for bots (or program one), which can be activated from every PR (@ros2controlbot test downstream), as one can trigger mergify.

What I'm wondering about: If a downstream test is flaky, we will get a new issue every day?

No, it shouldn't. With the update_existing: true flag I set there should only be one (open) issue with the same title that will get updated. In my point of view downstream packages with flaky tests would disqualify as being run inside ros2_control's CI.

* can we parse from ICI, which package failed in which state?

Not that I know of. This would be nice but I'm afraid one would have to inspect the build which is why I added the job link to the issue.

* can we check if an issue exists already, for example "Test failure for webots"? Like dependabot is not posting duplicates.

As stated above that should work already, however it will check for example for "CI build job rolling/main failed!" and update that.

Maybe we can additionally look for bots (or program one), which can be activated from every PR (@ros2controlbot test downstream), as one can trigger mergify.

That sounds nice. One possibility might be https://github.com/GregaVrbancic/gh-workflow-bot but that looks rather unmaintained. I think in the scope of this PR that might be over the top, we could keep that in mind for later, would you agree?

I agree to all of your points.
ICI has exit codes which can be parsed: https://github.com/ros-industrial/industrial_ci/pull/755
But it is not documented and not 100% clear for me how to use them
at least the test step can be parsed as
      test "${{ steps.ici.outputs.target_test_results}}" = "0" || exit 1

see their CI
otherwise we would have to write an own js wrapper around their script and parse the text output..


No error but nothing pushed

I have recently installed this plugin in a TFS 2015 project and configured it on one build. The build runs without error but nothing is pushed to the second repository.
Here is the log of the latest job:
    2018-08-07T15:24:48.8153693Z Checking if artifacts directory exists: E:\agent\_work\1\a

    2018-08-07T15:24:48.8153693Z Deleting artifacts directory.

    2018-08-07T15:24:48.8309919Z Creating artifacts directory.

    2018-08-07T15:24:48.8309919Z Checking if test results directory exists: E:\agent\_work\1\TestResults

    2018-08-07T15:24:48.8309919Z Deleting test results directory.

    2018-08-07T15:24:48.8309919Z Creating test results directory.

    2018-08-07T15:24:48.8466177Z Starting: Get sources

    2018-08-07T15:24:48.8622429Z Entering TfsGitSourceProvider.PrepareRepositoryAsync

    2018-08-07T15:24:48.8622429Z localPath=E:\agent\_work\1\s

    2018-08-07T15:24:48.8622429Z clean=False

    2018-08-07T15:24:48.8622429Z sourceBranch=refs/heads/develop

    2018-08-07T15:24:48.8622429Z sourceVersion=6ab0219711b1f7a0523b604275951e9bbdeb9fe0

    2018-08-07T15:24:48.8622429Z Syncing repository: junior-cie-client-mobile-app (Git)

    2018-08-07T15:24:48.8622429Z repository url=LOCAL_REPOS

    2018-08-07T15:24:48.8622429Z checkoutSubmodules=False

    2018-08-07T15:24:48.9247551Z Starting fetch...

    2018-08-07T15:24:49.1434932Z Checking out 6ab0219711b1f7a0523b604275951e9bbdeb9fe0 to E:\agent\_work\1\s

    2018-08-07T15:24:49.2626323Z Checked out branch refs/heads/develop for repository junior-cie-client-mobile-app at commit 6ab0219711b1f7a0523b604275951e9bbdeb9fe0

    2018-08-07T15:24:49.2626323Z commit=6ab0219711b1f7a0523b604275951e9bbdeb9fe0

    2018-08-07T15:24:49.2626323Z Leaving TfsGitSourceProvider.PrepareRepositoryAsync

    2018-08-07T15:24:49.3563826Z Running tasks

    2018-08-07T15:24:49.3720127Z Starting task: Mirror Git Repository to https://REMOTE_MIRROR

    2018-08-07T15:24:49.4032562Z Set workingFolder to default: E:\agent\tasks\mirror-git-repository-vsts-task\1.1.6

    2018-08-07T15:24:49.5595064Z ##[debug]agent.TempDirectory=undefined

    2018-08-07T15:24:49.5595064Z ##[debug]agent.workFolder=E:\agent\_work

    2018-08-07T15:24:49.5595064Z ##[debug]loading inputs and endpoints

    2018-08-07T15:24:49.5595064Z ##[debug]loading ENDPOINT_AUTH_C7272F41-432D-488A-9859-02677707766D

    2018-08-07T15:24:49.5595064Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION

    2018-08-07T15:24:49.5595064Z ##[debug]loading INPUT_DESTINATIONGITREPOSITORYPERSONALACCESSTOKEN

    2018-08-07T15:24:49.5595064Z ##[debug]loading INPUT_DESTINATIONGITREPOSITORYURI

    2018-08-07T15:24:49.5595064Z ##[debug]loading INPUT_DESTINATIONVERIFYSSLCERTIFICATE

    2018-08-07T15:24:49.5595064Z ##[debug]loading INPUT_SOURCEGITREPOSITORYURI

    2018-08-07T15:24:49.5595064Z ##[debug]loading INPUT_SOURCEVERIFYSSLCERTIFICATE

    2018-08-07T15:24:49.5595064Z ##[debug]loaded 7

    2018-08-07T15:24:49.5595064Z ##[debug]Agent.ProxyUrl=undefined

    2018-08-07T15:24:49.5595064Z ##[debug]Agent.CAInfo=undefined

    2018-08-07T15:24:49.5595064Z ##[debug]Agent.ClientCert=undefined

    2018-08-07T15:24:49.5595064Z ##[debug]Agent.SkipCertValidation=undefined

    2018-08-07T15:24:49.5751327Z Finishing task: mirror-git-repository-vsts-task

Hi @mikaoelitiana - we don't have access to a TFS instance to validate, so if you could provide some more info that would really help us out! Specifically, would you include/validate the below info (if you'd prefer to share any of this info offline you can email us at opensource@swellaby.com):

Node.js version:
npm version:
Operating System:  Windows
Mirror Git Repository Task version: 1.1.6
Tool for Mirror Source Repo (TFS, VSTS, GitHub, Bitbucket, etc.):
Tool for Mirror Destination/Target Repo (TFS, VSTS, GitHub, Bitbucket Cloud, Bitbucket Server, etc.):
Is your TFS Agent running in a private network/behind a firewall (y/n)?:
Does your Mirror Destination/Target Repo reside outside the network where your Agent is running (y/n)?

@mikaoelitiana - we are going to go ahead and close this as we've not heard back for while. Please feel free to re-open if you are still having issues and can share the requested information.
Thanks!


Fix command with complete but no nargs (#724)

This PR fixes #724.

Thank you for your review! Your suggestion looks better than my changes, so I've incorporated them.
(Actually, I modified it as you suggested at first, but since the default value of : command-nargs of nvim is -nargs = 0 and does not accept arguments, I committed it so that the behavior does not change.)

Would be really nice if someone could approve this

Would be really nice if someone could approve this

Yep, also waiting on this to be approved. My :w does not work and also getting same E1208 output messages.

Tested this, seems to work fine, would someone please commit it ?, so that i don't have to patch it every time reinstall vscode :-)

Sorry @asvetliakov but any chance of reviewing this?

Also getting this error, looking forward to a merge of this 👍

is there some update on this?

For the impatient , I applied the patch manually by directly editing the files works quite ok ( you find the files in your /.vscode/extenstions/asvetliakov.vscode-neovim-0.0.82/vim

Thank you for the fix!

@asvetliakov can we get a new version publish for this update? that would be great, thanks!

Published v0.0.83


kafkactl: 1.23.1 -> 2.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/deviceinsight/kafkactl/releases.
meta.description for kafkactl is: "Command Line Tool for managing Apache Kafka"
meta.homepage for kafkactl is: "https://github.com/deviceinsight/kafkactl"
meta.changelog for kafkactl is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.5.0 with grep in /nix/store/k9v4zzwg2n4yb9mxjkfpwxpq7s0fh8ka-kafkactl-2.5.0
found 2.5.0 in filename of file in /nix/store/k9v4zzwg2n4yb9mxjkfpwxpq7s0fh8ka-kafkactl-2.5.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kafkactl

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

kafkactl

Maintainer pings
cc @GRBurst for testing.

Result of nixpkgs-review pr 188860 run on x86_64-linux 1

1 package built:

kafkactl


[FP]: CVE-2010-1621 False positive against AWS Aurora MySQL v1.1.2 library

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:mysql:mysql:*:*:*:*:*:*:*:*
CVE
CVE-2010-1621
ODC Integration
No response
ODC Version
7.3.0
Description
Seems to be looking for a different library, entirely

duplicate #5097


81-update-promises-fails

#81
It seems that wasm-pack uses its own panic hook, so we can fix it with console_error_panic_hook::set_once();. This call doesn't try to change panic hook while the thread is panicking, because wasm-pack already hooked panics.
I've also moved it from run method into build so it's hooked sooner.
If you think it's possible to init Application without call build(..), we can add console_error_panic_hook::set_once() to other places.

Nice!


Test PrimeQA compatibility with python 3.10

Changing the requirements in setup.py to allow python 3.10 and the python version in primeqa-ci.yml  ( https://github.com/primeqa/primeqa/pull/426) passes the test.


page wont load after running trunk build

i would like to host my wasm app using my own server instead of proxying it through trunk. im running a static server at /dist/, and whenever i load / on my server i see index.html js_xxxx.js and wasm_xxxx.js all get loaded, but the app never loads. all i get is a blank page and a repeted request to /_trunk/ws.
how do i build a trunk app in a way that can be run independent from the build in trunk server?

Trunk build --release
Then serve the /dist with an HTTP server such as nginx.

i did that too. still diddent work.

Firefox can’t establish a connection to the server at ws://<IP_ADDRESS>:8080/_trunk/ws.

what websocket server did you expected?

none? im runing a warp server and hosting the /dist folder, i expect it to just work, i dont see why trunk is a runtime dependency

trunk build only emits static files as assets, and it exits. I don't see why there is a ws server. trunk serve has a websocket server for reloading(forgot its url path), but it's not in the case of trunk build. I'm still confused.

nevermind. looks like i was hosting / not /dist


Error running config for copilot:lua... Attempt to to index upvalue ''

Was avid copilot user in the past months, so it was working correctly.
I uninstalled the vim version and installed yours, but I'm experiecing this error as soon as I insert any char as I am using event Insert as you specified in the docs.

What I'm doing wrong?

Hi, can you show me the config you have for copilot.lua in your use code? This looks like an issue with the config you have set up.

exactly same code in your README.MD
		use({
			"zbirenbaum/copilot.lua",
			event = "InsertEnter",
			config = function()
				vim.schedule(function()
					require("copilot").setup()
				end)
			end,
		})

exactly same code in your README.MD

		use({

			"zbirenbaum/copilot.lua",

			event = "InsertEnter",

			config = function()

				vim.schedule(function()

					require("copilot").setup()

				end)

			end,

		})

This is very strange. What version of neovim are you using?

Nightly. yeah. I don't understant that.

Nightly. yeah. I don't understant that.

There definitely shouldn't be any issues then. Have you tried updating with packer sync? Worst case you might try nuking the plugin dir and reinstalling with a packer sync in case I commit --amend'd and it's not pulling an update

Yes, I even tried removing  ~/local/.share/nvim/site and ~/.cache/nvim/packer but nah, nothing fixes the issue, that's so weird.
Maybe I need to del some other folder?
https://github.com/lucax88x/configs/tree/master/dotfiles/.config/nvim
that's my dotfiles ..

I looked through your dot files. The copilot config seems to require something called lt.plugins.copilot-lua
I didn't see such a file there, and if that's where packer is set to install plugins, it should be require("copilot").setup()

Ops, I forgot to push, check it now.

Something I just thought of, do you install plugins to a non-standard location?

Removing the vim.schedule function fixed the problem.... Dunno why. I never used it anyway.


KAFKA-14214: Convert StandardAuthorizer to copy-on-write

Convert StandardAuthorizer to use a copy-on-write sorted array rather than a ConcurrentSkipList. The issue with the skiplist was that because it was modified while in use by StandardAuthorizer#authorize, we could sometimes expose an inconsistent state. For example, if we added a "deny principal foo", followed by "allow all", a request for principal foo might happen to see the second one, without seeing the first one, even though the first one was added first.
The sorted array data structure is more compact than the tree, although it has the disadvantage of needing to be copied every time it's modified. On the broker side, we can apply a batch of updates atomically now. On the controller side, we still apply updates one-by-one, for now.
This PR renames AclAuthorizerBenchmark to AuthorizerBenchmark and extends it to report information about StandardAuthorizer as well as AclAuthorizer.
Co-authored-by: Akhilesh Chaganti<EMAIL_ADDRESS>

Jenkins went down again. :(
java.nio.file.FileSystemException: /home/jenkins/workspace/Kafka_kafka-pr_PR-12636: No space left on device

Thanks for the PR. @cmccabe can you please include the benchmark results before/after this change?

I uploaded a new version at https://github.com/apache/kafka/pull/12662


Endorsing rights support

Added Delegate to the Contents.Metadata
Pulling endorsing rights from head at a specific level does not need to mess with snapshot blocks.
{
  "protocol": "Pt24m4xiPbLDhVgVfABUjirbmda3yohdN82Sp9FeuAXJ4eV9otd",
  "chain_id": "NetXwhYbWGa82xo",
  "hash": "oovKAGF2f7rciRmuu2K5NgCN8xukvLmAKGjQx4wR4gfmNQCP7QR",
  "branch": "BMH5F4K6A2eiYzin8sRP4aTTVfoGbmC1GMscckp5JsFdC77tJ7H",
  "contents": [
    {
      "kind": "endorsement",
      "level": 42308,
      "metadata": {
        "balance_updates": [ ... ],
        "delegate": "dn1aUVnffhj4RZ89wQ8NSWwTZYay9PFZSTCx",
        "slots": [ 7 ]
      }
    }
  ],
  "signature": "sigPPZmAsKD7gkpbSw5ERkZ83c4Ezo1QmJ4fDbav8TdCddhw3tz5E82j8rPweoEjoNk65zQ8FzFvM76WtVDL2CjDvTvUijMz"
}

Just updated PR to include baking rights at level via Head and refactored baking rights code

Added support for capturing double baking evidence


Assets/MRTK folder empty after initializing new project

Hello,
I just started a new project for Hololens 2 using Unity 2020/OpenXR/MRTK 2.8.2, and after following the instructions to set up a new project, I don't see anything in the Assets/MRTK folder, it is just empty.  How do I get the Hand Menu?

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

ID: 91cdafae-141d-704d-3a0b-35be1b3b4cf7
Version Independent ID: 91cdafae-141d-704d-3a0b-35be1b3b4cf7
Content: Hand menu - MRTK 2
Content Source: mrtk-unity/mrtk2/features/ux-building-blocks/hand-menu.md
Product: mixed-reality
GitHub Login: @cre8ivepark
Microsoft Alias: dongpark

It seems that you imported MRTK using the Mixed Reality Feature Tool, where MRTK is imported as UPM packages. You can locate imported UPM packages under the Project window -> Packages. Also make sure you go through our docs on Unity packages


Week 27 Ticket

Team Score
Lesson ideas: Our advanced lessons while adventure deeper into important college board topics
     -Binary search
     -Image differentiation
     -More if we have time

NATM: Our binary games will be better suited for NATM because people will venture quickly and games are perfect for a quick pop in and go

Suggested division of work using Scrum Board:

Pair Score
Theo and Haseeb's Project Board:

Examples of code/things done so far:

Individual Score
Commits since Ski Week:

AP Classroom Quiz Score + Blogging
CPT
Space Time Complexity

Grading for Theo
Duo/Trio Grading
0.9/0.9
Theo made good progress on his quiz, so he obviously has code. He also has all of his Issues up.
Team Score
0.9/0.9
Theo helped with ideation and the scrum/project board, and he has plans for the two big events/cleaning up the CPT.
Individual Score
0.9/0.9
Theo has sufficient corrections for his CB quiz, his commits are good as well. As I stated above he has his plans for finishing up the CPT and big events.


WORLDPATH command doesn't work

Hello,
I have followed your tutorial on how to have the Terraria server running and I am facing a problem.
When I remove the FILENAME_WORLD command I can create a new world without any issues.
However when I want to import a previous world, the FILENAME_WORLD command with WORLDPATH don't seem to work.
The container crashes on startup and tells me that there is no world file in -v <path_to_world_file>:/root/.local/share/Terraria/Worlds
The journal logs show that the WORLDPATH environment is not taken into account.
Am I missing something?
Thank you

Are you using my terraria docker version? I don't have this variable. I am using
DOWNLOAD_VERSION=1449
FILENAME_CONFIG=serverconfig.txt
FILENAME_WORLD=world.wld
FILENAME_BANLIST=banlist.txt

Out of all dockerized solutions I do recommend you this one. It is frustrating to work with the others, especially for a user not familiar with docker and related stuff.


@4.5.2 - provenance build/publish

coverage: 99.245%. remained the same
when pulling 3f1518959f21bd0e4f84605dc86ac6b5182ce1b2 on rc-4.5.2
into 184971856ee618ae7003e65e5c184ac9c9f6eace on master.


Data for next 24 hrs

Hi!
Thanks for creating this module.
I'm currently pulling the data via Awattar API using Node-Red but am not able to get the prices for all upcoming next 24 hours.
From my knowledge, Awattar only publishes the data something about 14:00 UTC+1.
Did you find a way to receive the prices for the upcoming 24hrs, no matter at which time you pull them?
In the sensor data, I can only see the prices for today.
Thanks

Hi, I'm not sure if I understand your question correctly. This module fetches all available data, which contains the prices to today and after 14:oo also the prices for tomorrow:
unit_of_measurement: EUR/MWh
icon: mdi:currency-eur
friendly_name: EPEX Spot de Price
data:
  - start_time: '2023-01-02T00:00:00+00:00'
    end_time: '2023-01-02T01:00:00+00:00'
    price_eur_per_mwh: 51.67
  - start_time: '2023-01-02T01:00:00+00:00'
    end_time: '2023-01-02T02:00:00+00:00'
    price_eur_per_mwh: 52.93
  - start_time: '2023-01-02T02:00:00+00:00'
    end_time: '2023-01-02T03:00:00+00:00'
    price_eur_per_mwh: 44.09
  - start_time: '2023-01-02T03:00:00+00:00'
    end_time: '2023-01-02T04:00:00+00:00'
    price_eur_per_mwh: 50.08
  - start_time: '2023-01-02T04:00:00+00:00'
    end_time: '2023-01-02T05:00:00+00:00'
    price_eur_per_mwh: 69.72
  - start_time: '2023-01-02T05:00:00+00:00'
    end_time: '2023-01-02T06:00:00+00:00'
    price_eur_per_mwh: 105.08
  - start_time: '2023-01-02T06:00:00+00:00'
    end_time: '2023-01-02T07:00:00+00:00'
    price_eur_per_mwh: 140.64
  - start_time: '2023-01-02T07:00:00+00:00'
    end_time: '2023-01-02T08:00:00+00:00'
    price_eur_per_mwh: 145.98
  - start_time: '2023-01-02T08:00:00+00:00'
    end_time: '2023-01-02T09:00:00+00:00'
    price_eur_per_mwh: 147.05
  - start_time: '2023-01-02T09:00:00+00:00'
    end_time: '2023-01-02T10:00:00+00:00'
    price_eur_per_mwh: 145.61
  - start_time: '2023-01-02T10:00:00+00:00'
    end_time: '2023-01-02T11:00:00+00:00'
    price_eur_per_mwh: 143.35
  - start_time: '2023-01-02T11:00:00+00:00'
    end_time: '2023-01-02T12:00:00+00:00'
    price_eur_per_mwh: 144.38
  - start_time: '2023-01-02T12:00:00+00:00'
    end_time: '2023-01-02T13:00:00+00:00'
    price_eur_per_mwh: 143.76
  - start_time: '2023-01-02T13:00:00+00:00'
    end_time: '2023-01-02T14:00:00+00:00'
    price_eur_per_mwh: 148.2
  - start_time: '2023-01-02T14:00:00+00:00'
    end_time: '2023-01-02T15:00:00+00:00'
    price_eur_per_mwh: 155.34
  - start_time: '2023-01-02T15:00:00+00:00'
    end_time: '2023-01-02T16:00:00+00:00'
    price_eur_per_mwh: 162.89
  - start_time: '2023-01-02T16:00:00+00:00'
    end_time: '2023-01-02T17:00:00+00:00'
    price_eur_per_mwh: 170
  - start_time: '2023-01-02T17:00:00+00:00'
    end_time: '2023-01-02T18:00:00+00:00'
    price_eur_per_mwh: 174.74
  - start_time: '2023-01-02T18:00:00+00:00'
    end_time: '2023-01-02T19:00:00+00:00'
    price_eur_per_mwh: 164.46
  - start_time: '2023-01-02T19:00:00+00:00'
    end_time: '2023-01-02T20:00:00+00:00'
    price_eur_per_mwh: 153
  - start_time: '2023-01-02T20:00:00+00:00'
    end_time: '2023-01-02T21:00:00+00:00'
    price_eur_per_mwh: 141.67
  - start_time: '2023-01-02T21:00:00+00:00'
    end_time: '2023-01-02T22:00:00+00:00'
    price_eur_per_mwh: 134.91
  - start_time: '2023-01-02T22:00:00+00:00'
    end_time: '2023-01-02T23:00:00+00:00'
    price_eur_per_mwh: 124.22
  - start_time: '2023-01-02T23:00:00+00:00'
    end_time: '2023-01-03T00:00:00+00:00'
    price_eur_per_mwh: 130.01
  - start_time: '2023-01-03T00:00:00+00:00'
    end_time: '2023-01-03T01:00:00+00:00'
    price_eur_per_mwh: 120
  - start_time: '2023-01-03T01:00:00+00:00'
    end_time: '2023-01-03T02:00:00+00:00'
    price_eur_per_mwh: 118.76
  - start_time: '2023-01-03T02:00:00+00:00'
    end_time: '2023-01-03T03:00:00+00:00'
    price_eur_per_mwh: 115
  - start_time: '2023-01-03T03:00:00+00:00'
    end_time: '2023-01-03T04:00:00+00:00'
    price_eur_per_mwh: 113.63
  - start_time: '2023-01-03T04:00:00+00:00'
    end_time: '2023-01-03T05:00:00+00:00'
    price_eur_per_mwh: 116.27
  - start_time: '2023-01-03T05:00:00+00:00'
    end_time: '2023-01-03T06:00:00+00:00'
    price_eur_per_mwh: 138.92
  - start_time: '2023-01-03T06:00:00+00:00'
    end_time: '2023-01-03T07:00:00+00:00'
    price_eur_per_mwh: 159.92
  - start_time: '2023-01-03T07:00:00+00:00'
    end_time: '2023-01-03T08:00:00+00:00'
    price_eur_per_mwh: 169.17
  - start_time: '2023-01-03T08:00:00+00:00'
    end_time: '2023-01-03T09:00:00+00:00'
    price_eur_per_mwh: 171.18
  - start_time: '2023-01-03T09:00:00+00:00'
    end_time: '2023-01-03T10:00:00+00:00'
    price_eur_per_mwh: 168.57
  - start_time: '2023-01-03T10:00:00+00:00'
    end_time: '2023-01-03T11:00:00+00:00'
    price_eur_per_mwh: 169.49
  - start_time: '2023-01-03T11:00:00+00:00'
    end_time: '2023-01-03T12:00:00+00:00'
    price_eur_per_mwh: 164.5
  - start_time: '2023-01-03T12:00:00+00:00'
    end_time: '2023-01-03T13:00:00+00:00'
    price_eur_per_mwh: 160.91
  - start_time: '2023-01-03T13:00:00+00:00'
    end_time: '2023-01-03T14:00:00+00:00'
    price_eur_per_mwh: 163.06
  - start_time: '2023-01-03T14:00:00+00:00'
    end_time: '2023-01-03T15:00:00+00:00'
    price_eur_per_mwh: 167.73
  - start_time: '2023-01-03T15:00:00+00:00'
    end_time: '2023-01-03T16:00:00+00:00'
    price_eur_per_mwh: 166.61
  - start_time: '2023-01-03T16:00:00+00:00'
    end_time: '2023-01-03T17:00:00+00:00'
    price_eur_per_mwh: 170.72
  - start_time: '2023-01-03T17:00:00+00:00'
    end_time: '2023-01-03T18:00:00+00:00'
    price_eur_per_mwh: 168.93
  - start_time: '2023-01-03T18:00:00+00:00'
    end_time: '2023-01-03T19:00:00+00:00'
    price_eur_per_mwh: 160.99
  - start_time: '2023-01-03T19:00:00+00:00'
    end_time: '2023-01-03T20:00:00+00:00'
    price_eur_per_mwh: 149.62
  - start_time: '2023-01-03T20:00:00+00:00'
    end_time: '2023-01-03T21:00:00+00:00'
    price_eur_per_mwh: 130.99
  - start_time: '2023-01-03T21:00:00+00:00'
    end_time: '2023-01-03T22:00:00+00:00'
    price_eur_per_mwh: 114.27
  - start_time: '2023-01-03T22:00:00+00:00'
    end_time: '2023-01-03T23:00:00+00:00'
    price_eur_per_mwh: 93.66

Hi @mampfes
it is about the timeframe from 01:00 to 13:00 where I can not get the EPEX Spot data for all upcoming 24 hrs as I need them for EMHASS (all 24hrs).
I hoped that your solution might provide them but it seems that this is not provided from EPEX Spot side.
Thanks anyway!

Ah, ok - now I see. From my understand, the new prices are determined at 14:oo for the following day. So the max forecast period is 32h (right after 14:oo) and the min forecast period 8h (just before 14:oo). There is no way to bypass this.


Added simple permission checks to views.

I think we (I) made a mistake. We should leave those big juicy "Contribute" buttons there regardless of whether a user is signed in. So long as the controller redirects unauthorized users to the sign in / sign up pages, we can and should leave those buttons in as calls to action.
Sorry for not realizing that sooner.


if the repo we are pushing has a CHECKS file...

the  check will fail because curl is not installed.
Making sure that curl is indeed installed on the VM.

Are you certain this is necessary? I have not run into this and have not heard of anyone having this issue either.

@michaelshobbs I'm afraid it is. This is what I got when I tried to deploy to the VM:
---> Attempt 1/5 Waiting for 5 seconds ...
       CHECKS expected result:
       http://localhost/_internal_/ok => ""
 !     /var/lib/dokku/plugins/enabled/checks/check-deploy: line 187: curl: command not found
 !     Check attempt 1/5 failed.
-----> Attempt 2/5 Waiting for 5 seconds ...
       CHECKS expected result:
       http://localhost/_internal_/ok => ""
 !     /var/lib/dokku/plugins/enabled/checks/check-deploy: line 187: curl: command not found
 !     Check attempt 2/5 failed.
-----> Attempt 3/5 Waiting for 5 seconds ...
       CHECKS expected result:
       http://localhost/_internal_/ok => ""
 !     /var/lib/dokku/plugins/enabled/checks/check-deploy: line 187: curl: command not found
 !     Check attempt 3/5 failed.
-----> Attempt 4/5 Waiting for 5 seconds ...
       CHECKS expected result:
       http://localhost/_internal_/ok => ""
 !     /var/lib/dokku/plugins/enabled/checks/check-deploy: line 187: curl: command not found
 !     Check attempt 4/5 failed.
-----> Attempt 5/5 Waiting for 5 seconds ...
       CHECKS expected result:
       http://localhost/_internal_/ok => ""
remote: Could not start due to 1 failed checks.
 !     /var/lib/dokku/plugins/enabled/checks/check-deploy: line 187: curl: command not found
 !     Check attempt 5/5 failed.

This can be easily reproduced by doing vagrant up and then vagrant ssh followed by any curl command. The result should be:
vagrant@dokku:~$ curl
The program 'curl' is currently not installed. You can install it by typing:
sudo apt-get install curl

I agree with you.. it's strange that no one noticed this... maybe I am doing something silly. But the steps I gave you are the exact ones I used.

This is on master?

Yes, this happened while on the master branch.

On 18 Nov 2015, at 18:17, Michael Hobbs<EMAIL_ADDRESS>wrote:
This is on master?
—
Reply to this email directly or view it on GitHub.

I'm thinking your vagrant up failed or maybe you have a really old version of the base box? You might try a vagrant destroy & vagrant up again and post that output in a gist? I can confirm a fresh vagrant up in my env includes curl.

 My bad. You are correct this is indeed a bug. I don't think this is the correct place to do this however. Perhaps here would make more sense: https://github.com/progrium/dokku/blob/master/Makefile#L80-L81

Not sure what changed to cause this though....maybe it was our move to bento? /cc @josegonzalez

https://github.com/progrium/dokku/pull/1665

Except that #1665 didn't actually remove curl from this PR's vagrant setup; just the deb version.

Also, the dokku deb package depends on curl. So in that version you end up with curl anyway.

Oh nevermind about #1665 I see it now in the top-level Makefile line 102 was removed. That should be added back.

@pmvieira let me know if you're cool updating this PR to revert that regression

@michaelshobbs Sure, not a problem, will do and update the PR

gracias!

That's that line added back @michaelshobbs  :)

@pmvieira mind squashing?

That's the opposite of squashing :smile:

Sorry @michaelshobbs ... :blush: Should know better not to commit while sleepy

No worries. Thanks for the PR.


3.2 ROM Kickstart 47.96 not recognized

the main splash screen reports ROM: unknown
it is a minor issue since all tests work normally

Please test this version:
AmigaTestKit-5d15759.zip

Reported working and folded into new v1.17 release.


Always validate the array data when creating array in IPC reader

IMO we should probably be validating all of them, I'm not sure why we aren't validating some of them... IPC is inherently not trusted
Originally posted by @tustvold in https://github.com/apache/arrow-rs/pull/2525#discussion_r950697745

After replacing build_unchecked with build().unwrap() in create_primitive_array in the ipc reader, 5 tests fail:
failures:
    ipc::reader::tests::read_generated_files_014
    ipc::reader::tests::read_generated_streams_014
    ipc::writer::tests::read_and_rewrite_generated_files_014
    ipc::writer::tests::read_and_rewrite_generated_streams_014
    json::reader::tests::test_row_type_validation

@tustvold @viirya Any idea about these?


Do not load the flatpak_create_plugin if we are not building a flatpak

Without this we are trying to run the pre_flatpak_create_dockerfile plugin when trying to build normal containers.
Maybe @mlangsdorf could review this and make sure this is a sane change.
I ll be happy to work on some tests if I could get some pointers on which test to modify.
cc'ing @owtaylor
Signed-off-by: Clement Verna<EMAIL_ADDRESS>

Thanks for the pointers, I ll work on modifying the tests.
Following is the log of the failing build if you are interested https://kojipkgs.stg.fedoraproject.org//work/tasks/1014/90001014/orchestrator.log

On Fri, Jun 15, 2018, 7:26 AM Mark Langsdorf<EMAIL_ADDRESS>wrote:

I'm curious why your buildconfig is passing a flatpak_base_image value
when not building a flatpak, but this is still a bug.

In Fedora a single Koji instance and hence osbs.conf is used to build both
docker containers and flatpaks.

Could you add a test for this?
Yes working on it :monkey_face:

@mlangsdorf currently flatpak = True and flatpak_base_image = Flase is loading the resolve_module_compose.
I am not 100% if this is correct or not, based on the flatpak_create_dockerfile plugin should we check if we have a flatpak_base_image before loading the plugin.

I think it doesn't make sense to enable resolve_composes unless we've got a valid flatpak_base_image and we're doing a flatpak build.
Would you please remove the test_render_not_flatpak and move all the logic into test_render_flatpak? I'd like to see one test function, something like:
@pytest.mark.parametrize('build_type', (BUILD_TYPE_ORCHESTRATOR, BUILD_TYPE_WORKER)) @pytest.mark.parametrize('compose_ids', (None, [], [42], [42, 2])) @pytest.mark.parametrize('flatpak_base_image', (TEST_FLATPAK_BASE_IMAGE, None)) @pytest.mark.parametrize('flatpak', (True, False)) def test_render_flatpak(self, compose_ids, build_type, flatpak, flatpak_base_image):
It confirms the plugins are set up if and only if both flatpak and flatpak_base_image are true/have values, and confirms that the plugins are disabled if either flatpak is false or flatpak_base_image is None.
It should be pretty easy - all the logic is there.

If flatpak is specified, then it doesn't make any sense to proceed if
flatpak_base_image is not configured. You can't fall back to a docker build
if you just remove the plugins and submit the build: that's just asking
atomic reactor to haul in a confusing way. osbs-client needs to fail with
that combination.

@mlangsdorf, I think I kind of agree with @owtaylor here, if flatpak = True and flatpak_base_image is None should raise an exception in osbs-client for flatpak_create_dockerfile, flatpak_create_oci and resolve_module_compose.
I ll modify this PR in that direction if this is ok with you.

@mlangsdorf, I think I kind of agree with @owtaylor here, if flatpak = True and flatpak_base_image is None should raise an exception in osbs-client for flatpak_create_dockerfile, flatpak_create_oci and resolve_module_compose.

I think it's a bit better to check up front - you are going to have trouble getting complete test coverage if you do it in the render_ because the first plugin will fail and you never will get to the second. Perhaps it could be done in user_params.py - though if you put it in set_params(), that doesn't look like it gets run in actual use through the api - only from the test code? the api seems to only use from_json which doesn't validate anything?

set_params is called in osbs/api.py line 610, as part of _do_create_prod_build, after retrieving either a BuildRequest or BuildRequestV2 depending on the arrangement version. So user_params.set_params is the right place do raise the error - there's currently an if not flatpack: test around line 133, which should be replaced by
if flatpak:
    if not flatpak_base_image:
        raise OsbsValidationException("flatpak_base_image must be provided)
else:
    # existing checks go here

I think I'm failing to follow some code path - the code that is being patched here - and that was apparently triggering a problem in Fedora staging - is the code in plugin_configurations.py. But outside of testing/ PluginsConfiguration is referenced only by osbs.render_plugins_configuration() which as far as I can tell is not used in osbs-client, koji-containerbuild, or atomic_reactor. So clearly I'm missing something :-)

The way it works is:
someone calls _do_create_prod_build in osbs_client.api
_do_create_prod_build gets a BuildRequestV2 object for arrangement 6 and later via get_build_request
_do_create_prod_build sets the user params via build_request.set_params()
_do_create_prod_build spawns atomic_reactor, passing the json of the build configuration via the USER_PARAMS environment variable
atomic reactor calls the input_osv3 plugin
the input_osv3 plugin retrieves the build json from USER_PARAMS
the input_osv3 plugin creates an an osbs instance and calls osbs.render_plugins_configuration
the input_osv3 plugin finishes removing plugins based on the reactor config - including removing resolve_composes if there isn't an odcs value in the reactor_config
at some point, I'd like to re-engineer some of this to be a little less confusing.

But doesn't all that mean that BuildUserParams.set_params() is never called?

in step 2oc, build_request is a BuildRequestV2, so build_request.set_params() is BuildRequestV2.set_params(), which calls self.user_params.set_params().

I restarted the failed Travis CI test runs and they succeeded.

Updated release notes draft:

flatpak_create_dockerfile is only enabled for flatpak builds


request.del(url) with params

I'm working with an API where I need to send parameters across with a DELETE request, however looking at https://github.com/visionmedia/superagent/blob/master/lib/client.js#L1093, none of the .send(data) methods are called before .end() like on the other verbs.
Is this deliberately not supported for a reason or a bug?

Fixed this using .query(params), closing.


ci(release_workspace): add optional branch to workflow

Hey, I just made a Pull Request!
Testing whether we can add a UI-based workflow to release from a branch.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] 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)

Hi @BethGriggs, any chance we can follow up on this with some documentation? Like how to use and when to use as well as some examples? This could just go in the /docs folder. 👍


Stepwise guidance in implementing in ESP32/Ubuntu?

Hi @matth-x  @all,
Is there anyone has successfully incorporated this library into ESP32 and if so kindly aid the knowledge that has been acquired during the process. There are some you could aid me/newbie like me attain the same too.
The stepwise guidance for ESP32 / any Linux based OS is very welcomed.
PS : As @matth-x being very busy, I'm raising this concern more to the community. Setup of ocpp-server Steve is attained. Hence aid us in implementing the client side part alone. Thanks in advance.

Hi @GanesanGuru,
Yes, I must admit that the documentation of this open source project is by far not as extensive as it should be. However, there is some material. A technical introduction explains the basic principles of this library. The API documentation can be found in MicroOcpp.h.
I think that most people get started with this library by creating an example project in PlatformIO based on the ESP example. When you manage to build this project successfully in PlatformIO, then you have a good reference project and the perfect resource to learn how including MicroOcpp generally works. The corresponding starting point on Ubuntu would be to clone and build the Simulator.

Hi @matth-x ,
The corresponding starting point on Ubuntu would be to clone and build the Simulator.
This line has saved me from all that uncertain EVSE charging environment. Yes, I was able to successfully integrate the SteVe with MicroOCPP Simulator and able to perform transactions,etc and all. I've few queries relate to OCPP 1.6J spec & MicroOCPP Simulator implementation, as listed below:

I was able to re-create 6/9 states of EV Charger - while I'm unable to recreate - Reserved,Unavailable ,Faulted states
I was able to re-create 7/10 of ChargePoint Transactions - while I'm unable to recreate - Data Transfer,Diagnostics & Firmware Status Notification
I was not able to recreate any of total 19 - Operations Initiated by Central System - like reservation,stop/start transactions using SteVe...
Whether microocpp has impleted all those leftout operations &whether because of SteVe I'm not able to visualize it? If so, recommended any OCPP server that you have used to develop the simulator...


How to get sub categorie name in home.php (redlabel)

I am trying to display sub categorie like this

How to get sub categorie from home.php? Many thanks

In the templates you have option for subcategories. You can change listing design in the html structure.