feature request: allow deployments from mainnet on hardhat in forking mode

It would be cool if await ethers.getContract("Bar") when run in hardhat forking mode would let hardhat-deploy know that --network hardhat can actually also take into consideration the deployments/ from whatever network is configured in forking
Referencing this issue https://github.com/wighawag/hardhat-deploy-ethers/issues/6

implemented in 0.7.0-beta.29

Copying from our chat for reference:
Is it exclusive to the network you pass with --fork-deployments ? Ideally for me it would do this:

Look into —fork-deployments deployments folder first - if contract not in there
Look into —network deployments folder second

This way tests can mix forked contract instances from mainnet + mocked ones that you might only wanna deploy to hardhat network

it works by copying the deployments from the chain into localhost
so then your deploy script can decide to override the deployment if they wish

I am using hardhat network in-memory forking and I don't have an instance of hardhat node running during my tests. Does this also work for tests using forking on in-memory hardhat network?

ha no, good point, this is only a param for the node task.
I should be able to add it to the test task. reopenning

re 1. : the argument to the param is the name of the network

Actually @gitpusha do you have a repo example on how this is setup because thinking of it might need some changes on how things are handled.
currently with in memory network, there is no facility to have pre-deployed contract info
I might be able to add a similar param but need to think more

actually you should be able to use the external deployments config :
something like :
hardhat.config.js
module.exports = {
 ...
  external: {
    deployments: {
      hardhat: ['deployments/mainnet'],
    },
  },
}

actually you should be able to use the external deployments config

That would be sweet.
Here is an example repo.
I am not sure how useful this feature is though, since you can always just use
await hre.ethers.getContractAt(abi, address)

in forkmode instead to access deployed instances from a specific network.
So it's really just a nice-to-have.

I tried the suggestion I posted above and it seems to work fine.
The deployments specified in external will not take precedence but that should not be an issue as node by default reset contract in deployments/hardhat and so unless you force redeployment of already deployed contract, you ll get the one from deployments/mainnet
I ll close the issue but if you have issue feel free to reopen

I tried the suggestion I posted above and it seems to work fine.
The deployments specified in external will not take precedence but that should not be an issue as node by default reset contract in deployments/hardhat and so unless you force redeployment of already deployed contract, you ll get the one from deployments/mainnet
I ll close the issue but if you have issue feel free to reopen


Async delete_blobs method raises an exception when using Azurite

Which service(blob, file, queue, table) does this issue concern?
Blob
Which version of the Azurite was used?
3.20.1
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Installed using VS Code extension
What's the Node.js version?
NA
What problem was encountered?
Calling await delete_blobs(*blobs) results in an exception. This only seems to occur against Azurite, using this method against a standard storage account seems to work as expected. Using the singular await delete_blob(blob) works as expected against Azurite.
Steps to reproduce the issue?
import asyncio
from azure.storage.blob.aio import ContainerClient
from typing import List

CONN_STR = "DefaultEndpointsProtocol=https;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=https://<IP_ADDRESS>:10000/devstoreaccount1;QueueEndpoint=https://<IP_ADDRESS>:10001/devstoreaccount1;TableEndpoint=https://<IP_ADDRESS>:10002/devstoreaccount1;"

async def main():
    client = ContainerClient.from_connection_string(CONN_STR, "test-container")
    blob_path = "test_name"
    blob_path_2 = "test_name2"
    await upload_schedule_blob(client, blob_path, {"key": "value"})
    await upload_schedule_blob(client, blob_path_2, {"key": "value"})
    print("Blob uploaded.")
    await delete_blobs(client, [blob_path, blob_path_2])
    print("Blob deleted")

async def delete_blobs(client, blob_list: List[str]):
    # Max deletes per request=256
    await client.delete_blobs(*blob_list)

async def upload_schedule_blob(
    client: ContainerClient,
    path: str,
    metadata: dict = {},
) -> None:

    await client.upload_blob(path, "".encode(), metadata=metadata)

if __name__ == "__main__":
    asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())
    asyncio.run(main())

Stack Trace
Exception has occurred: PartialBatchErrorException       (note: full exception trace is shown but execution is paused at: _run_module_as_main)
There is a partial failure in the batch operation.
ErrorCode:None
Content: --
Content-Type: application/http

HTTP/1.1 400 One of the request inputs is not valid.
x-ms-error-code: InvalidInput
x-ms-request-id: f3c21471-569e-4afa-961a-2312bbe4ebbf
content-type: application/xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
  InvalidInput
  <Message>One of the request inputs is not valid.
RequestId:f3c21471-569e-4afa-961a-2312bbe4ebbf
Time:2022-11-17T05:28:01.429Z</Message>
</Error>
----
  File "C:\_DEV\prototyping\Lib\site-packages\azure\storage\blob\_shared\base_client_async.py", line 167, in _batch_send
    process_storage_error(error)
  File "<string>", line 1, in <module>
  File "C:\_DEV\prototyping\Lib\site-packages\azure\storage\blob\_shared\response_handlers.py", line 181, in process_storage_error
    exec("raise error from None")   # pylint: disable=exec-used # nosec
  File "C:\_DEV\prototyping\Lib\site-packages\azure\storage\blob\_shared\base_client_async.py", line 167, in _batch_send
    process_storage_error(error)
  File "C:\_DEV\prototyping\Lib\site-packages\azure\storage\blob\aio\_container_client_async.py", line 1110, in delete_blobs
    return await self._batch_send(*reqs, **options)
  File "C:\_DEV\prototyping\Lib\site-packages\azure\core\tracing\decorator_async.py", line 79, in wrapper_use_tracer
    return await func(*args, **kwargs)
  File "C:\_DEV\prototyping\azurite_delete_blobs_bug.py", line 22, in delete_blobs
    await client.delete_blobs(*blob_list)
  File "C:\_DEV\prototyping\azurite_delete_blobs_bug.py", line 16, in main
    await delete_blobs(client, [blob_path])
  File "C:\Users\JMONKHOUSE\AppData\Local\Programs\Python\Python38\Lib\asyncio\base_events.py", line 616, in run_until_complete
    return future.result()
  File "C:\Users\JMONKHOUSE\AppData\Local\Programs\Python\Python38\Lib\asyncio\runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "C:\_DEV\prototyping\azurite_delete_blobs_bug.py", line 77, in <module>
    asyncio.run(main())
  File "C:\Users\JMONKHOUSE\AppData\Local\Programs\Python\Python38\Lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\JMONKHOUSE\AppData\Local\Programs\Python\Python38\Lib\runpy.py", line 194, in _run_module_as_main (Current frame)
    return _run_code(code, main_globals, None,

Have you found a mitigation/solution?
Looping over the singular blob delete method works, but requires patching my code while testing which is not ideal.

@wallflower762
Would you please share the debug log of Azurite?
We need it to do further investigation.

I am not certain how to get the debug logs for the VS Code extension, but I enabled the debug channel in VS Code and these are the 2 outputs windows:

It doesn't show anything very interesting, just the PUT of the testing object. Please let me know if you need me to locate other debug logs (and how).

@wallflower762
You can enable debug log for Azurite VC extension like following picture, and restart Azurite:

Or you can just install Azurite with npm, and then start Azurite with command line like, and share the debug log file :
azurite --location c:\azurite --debug c:\azurite\debug.log

Ok, the screenshots posted earlier were with the debug setting enabled in VS Code.

@wallflower762
It looks too less log in the "Azurite Blob Debug" output.
We will need at least the debug log for the orignal error InvalidInput(400).
If you still can't get enough debug log in "Azurite Blob Debug" output (even by restart VS code), would you like try to install Azurite with npm, and run Azurite with above command line?

@wallflower762
I will close this issue as not hear from you for a long time.
Feel free to contact us again if need any further assistance on Azurite.

@blueww I've got the same issue as  was discribed above by @wallflower762. Azurite returning an error when calling delete_blobs() except I do not use async here.
I've got azurite 3.22.0 from docker hub
I attached file with debug logs.
debug.log
As a workaround I do the same think as @wallflower762 and patch it globally
    def delete_azure_blobs(self, *blobs, **kwargs):
        for blob in blobs:
            with suppress(ResourceNotFoundError):
                self.delete_blob(blob)

    @patch(
        "azure.storage.blob._container_client.ContainerClient.delete_blobs",
        side_effect=delete_azure_blobs,
        autospec=True,
    )
    def run_tests(self, test_labels, mock, **kwargs):
         return super().run_tests(test_labels, **kwargs)

I used the script below to check it. With Azurite I've got an error (full stack trace below) azure.storage.blob._shared.response_handlers.PartialBatchErrorException: There is a partial failure in the batch operation.
but when I pass connection string to my storage account everything works fine.
from azure.core.exceptions import ResourceExistsError

from azure.storage.blob import BlobServiceClient

blob_service_client = BlobServiceClient.from_connection_string((
    "DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;"
    "AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/"
    "K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://<IP_ADDRESS>:10000/devstoreaccount1;"
))

container_client = blob_service_client.get_container_client("container")

try:
    container_client.create_container()
except ResourceExistsError:
    pass

blob_list = [b.name for b in list(container_client.list_blobs())]
# empty list
print(blob_list)

upload_data = b"Hello World"
for index in range(10):
    container_client.upload_blob(name=f"my_blob{index}", data=upload_data, overwrite=True)

# uploaded blobs
blob_list = [b.name for b in list(container_client.list_blobs())]
print(blob_list)

container_client.delete_blobs(*blob_list)

# empty again
blob_list = [b.name for b in list(container_client.list_blobs())]
print(blob_list)

Stack trace
Traceback (most recent call last):
  File "/home/myLocalPath/.config/JetBrains/PyCharm2022.3/scratches/azurite.py", line 30, in <module>
    container_client.delete_blobs(*blob_list)
  File "/home/myLocalPath/.virtualenvs/py310/lib/python3.10/site-packages/azure/core/tracing/decorator.py", line 78, in wrapper_use_tracer
    return func(*args, **kwargs)
  File "/home/myLocalPath/.virtualenvs/py310/lib/python3.10/site-packages/azure/storage/blob/_container_client.py", line 1360, in delete_blobs
    return self._batch_send(*reqs, **options)
  File "/home/myLocalPath/.virtualenvs/py310/lib/python3.10/site-packages/azure/storage/blob/_shared/base_client.py", line 319, in _batch_send
    process_storage_error(error)
  File "/home/myLocalPath/.virtualenvs/py310/lib/python3.10/site-packages/azure/storage/blob/_shared/response_handlers.py", line 181, in process_storage_error
    exec("raise error from None")   # pylint: disable=exec-used # nosec
  File "<string>", line 1, in <module>
  File "/home/myLocalPath/.virtualenvs/py310/lib/python3.10/site-packages/azure/storage/blob/_shared/base_client.py", line 315, in _batch_send
    raise error
azure.storage.blob._shared.response_handlers.PartialBatchErrorException: There is a partial failure in the batch operation.
ErrorCode:None
Content: --batch_7240c4fb-b11c-11ed-ac16-d39098213827
Content-Type: application/http

HTTP/1.1 400 One of the request inputs is not valid.
x-ms-error-code: InvalidInput
x-ms-request-id: 89d6790c-18d2-4a2c-88b3-80c73e5614ab
content-type: application/xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
  InvalidInput
  <Message>One of the request inputs is not valid.

Would you please help to look why it fails?
@RobertM15
Would you like to open a new issue to track this?
The before issue has not enough information to investigate, and the behavior is also a little different (yous failed in both sync and async, but the original issue only fails in async), so we can't make sure they are same issue.

https://github.com/Azure/Azurite/issues/1809


add GET for /v1/users/{self.user_id}/temperature to pyEight

When calling /v1/users/{self.user_id}/temperature via a GET call it returns the current smart state of the mattress.
{
  "currentLevel": 0,
  "currentDeviceLevel": -51,
  "currentState": {
    "type": "off",
    "instance": {
      "timestamp": "2023-11-27T13:37:55Z"
    }
  },
  "scheduleType": "smart",
  "smart": {
    "bedTimeLevel": 0,
    "initialSleepLevel": 0,
    "finalSleepLevel": 0
  },
  "timeBased": {
    "level": -10,
    "durationSeconds": 28800
  }
}

['currentState']['type'] represents the state of the mattress as seen in the 8-sleep app for the schedule. With the following options:
off = when the mattress side is completely off
smart:bedtime = when the mattress is precooling or preheating for the selected bedtime (begins one hour before bedtime)
smart:initial = when the mattress has detected the person on this bedside has fallen asleep (lasts for 4 hrs)
smart:final = after the 4 hr window the mattress goes into the temperature set in the "final" stage in the app (stays in this stage until alarm or off)
alarm = 1 hr prior to the alarm time the app to begin heating and cooling the bed to the alarm temp.
Integrating this into the attributes for the mattress side state would allow automations to key off of the 4 phases that can be set in the 8-sleep app. Such as setting the lights to a lower brightness when the smart:bedtime state is detected, or opening the blinds after 30 mins when the alarm state is detected.

Not sure what you mean by your question currentState should ask be away?
However, for the second question as far as I can tell the bed presence is not reported directly in the API and I do not see any values that would help determine if the bed actually has someone in it besides getting sleep data (light, rem, deep) from the trends.

Edited my comment for clarity: * "also be away"

Ah not 100% sure, I think when you put the mattress side into away mode if say you're on vacation it does not return any values for the user ID calls.

Addressed in latest release.


I just can't play without 21:9... not anymore!! Please can you update the fix?, promise ill buy (donate) more than a coffee!

I just can't play without 21:9... not anymore!! Please can you update the fix?, promise ill buy (donate) more than a coffee!

You don't need to promise anything haha. I'll get the fix updated once my game is downloaded. It's going to take a bit so I would expect to see an update tomorrow.

Can I let you borrow my internet to help? Haha
On Tue, Sep 17, 2024 at 11:37 AM Lyall @.***> wrote:

You don't need to promise anything haha. I'll get the fix updated once my
game is downloaded. It's going to take a bit so I would expect to see an
update tomorrow.
—
Reply to this email directly, view it on GitHub
https://github.com/Lyall/FFXVIFix/issues/18#issuecomment-2356274900, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BLKX6S4WU6ZNBEYXZCDHYQTZXBED3AVCNFSM6AAAAABOLXIXHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGI3TIOJQGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

You don't need to promise anything haha. I'll get the fix updated once my game is downloaded. It's going to take a bit so I would expect to see an update tomorrow.

sorry but i insist! ppl who spend time helping others should be reward time to time.

Give v0.7.5 a try. Should work on the full game for now until I can get the game installed and look at it closer.

Works 100% thank you so much!

Give v0.7.5 a try. Should work on the full game for now until I can get the game installed and look at it closer.

Thank you so much! It was so fast from the very release of the game to help all people get the max of the game! <3

ty dev


[RFC] Overlayfs mounts

This is a RFC/POC of overlayfs volumes. By overlayfs volumes I mean mounts inside a container by using overlayfs to mount the resulting directory.
The code is by any mean ready to be reviewed or fully working. It just shows a working example of mounting something readonly in a container using overlayfs. This works by setting overlay's multiple lowers, specifically from the host and from the container rootfs.
The CLI is not perfect, but it works like this:
$ docker run -ti -v /etc/pki:/etc/pki:overlay fedora bash

The above command creates a mount by overlaying the host's /etc/pki and the container rootfs /etc/pki. The resulting mounts contains a merge of the two dirs.
It's not perfect, but I wouldn't allow complex overlay mounts at command line.
Another way of doing this could have been volume plugins, but unfortunately the Mount API isn't providing the container's rootfs path (otherwise it could be possible I guess?). The volume plugin would be in charge of mounting the overlay and docker will bind mount that afterwards.
I've opened this just to gather feedback and maybe find a saner way of specifying overlay mounts in the CLI.
/cc @cpuguy83 @rhatdan @rhvgoyal @mrunalp

@runcom :angel:
12:10:13 container/container_unix.go:411:1: exported method Container.OverlayMounts should have comment or be unexported

/cc @tonistiigi @cpuguy83 for design review :angel:

Thanks @vdemeester - I won't bother on tests failures for now, code is just a POC which works just to show this functionality. I'll move forward once we agree on design.

A couple of issues/discussion points would be if we want to support writable overlays?  Readonly use case works pretty good.   Using a writable overlay requires a "workdir" on the same file system as the "upper" directory, which could cause issues with the image structure.
Current patch does not work with SELinux, but it would be simple to fix I belive by adding the mount label when creating the mount options.

A couple of issues/discussion points would be if we want to support writable overlays? Readonly use case works pretty good. Using a writable overlay requires a "workdir" on the same file system as the "upper" directory, which could cause issues with the image structure.
Current patch does not work with SELinux, but it would be simple to fix I belive by adding the mount label when creating the mount options.

@rhatdan, alright, current patch is for now just POC, writable overlayfs can work using workdir(s) under docker root I guess.

Another way of doing this could have been volume plugins, but unfortunately the Mount API isn't providing the container's rootfs path (otherwise it could be possible I guess?).

I wonder a plugin could locate the mountpoint outside the rootfs, and just return the path of the mountpoint as the result of Mount API? Then IIUC it doesn't require rootfs path inside the Mount API.

I wonder a plugin could locate the mountpoint outside the rootfs, and just return the path of the mountpoint as the result of Mount API? Then IIUC it doesn't require rootfs path inside the Mount API.

one of the lower dir for an overlay needs to be relative to the rootfs and the Mount API (nor Create) is providing that. Not sure I follow what mean though.

$ docker run -ti -v /etc/pki:/etc/pki:overlay fedora bash
The above command creates a mount by overlaying the host's /etc/pki and the container rootfs /etc/pki. The resulting mounts contains a merge of the two dirs.

Uh, sorry, I was misthinking that this command results in a merge of the host's /etc/pki and a newly created writable directory, and not involved in the rootfs's /etc/pki. :sweat_smile: (Maybe the UX is not straightforward, but it is just my feeling)
So, I agree rootfs info is needed for this proposal if it comes with RW support (for RO, rootfs is not needed, because you could put the image info in VolumeDriver.Create())
If we extend the plugin API to support putting container info, can it be implemented as a plugin?
(I know it was once considered in 2015 https://github.com/docker/docker/issues/13420#issuecomment-106854433 https://github.com/docker/docker/issues/15588)

ping @dmcgowan @tonistiigi @stevvooe as well

So, I agree rootfs info is needed for this proposal if it comes with RW support (for RO, rootfs is not needed, because you could put the image info in VolumeDriver.Create())

I don't think I understand....even with RO you still need the container rootfs for lowerdir...

I don't think I understand....even with RO you still need the container rootfs for lowerdir...

Since the image's rootfs is identical to the container's rootfs with RO, the plugin would just require the image's information. (For mounting image's rootfs, the plugin would need to call Docker API)

We are talking about a readonly volume mount not a readonly image underneath.

I think you mean overlay "mounts". This is not adding a new volume type.

I think you mean overlay "mounts". This is not adding a new volume type.

I wrote that in my first comment... Here:

This is a RFC/POC of overlayfs volumes. By overlayfs volumes I mean mounts inside a container by using overlayfs to mount the resulting directory.

@runcom I just changed the title accordingly.

@runcom I would like to better understand how you expect this to be used. Overlaying the host and container's directories together to get a combined directory doesn't seem like an understandable pattern (which layer is on top, making a writable directory in the container now read only, mounting parts of a merged overlay directory back onto itself as a lower).
I do a see a very obvious benefit of just overlay mounting instead of bind mounting a local directory. The upper directories could be managed with the container life cycle, but wonder if that means the upper directory is just another form of a volume. Is the purpose of this change more focused on isolating changes in mount or combining host and container directories?

The customer that wanted this was looking at being able to merge directories like /etc/pki and /etc/yum.repos.d, They could do this with lots of bind mounts but it would be much easier to just merge two directory trees together.
Currently we would expect the external content to override the content inside the container image when they conflict.  In a perfect world we would be able to specify multiple sources and their order as well as support for write to an upper directory, but this becomes difficult with the volume CLI.

IIUC, this is a "non-opaque" volume thats mounted in the container? So I can have a single volume;
├── etc
│   └── nginx
│       └── nginx.conf
└── usr
    └── share
        └── nginx
            └── html
                └── wp-config.php

Mount that, and have all the configuration in place.
docker run -d -v myconfig:/ nginx

Would this volume be writable, or would it be "underneath" the container's writable layer?
-------------------------
writable layer
-------------------------
myconfig layer
-------------------------
nginx:latest
-------------------------

FWIW, I'm strongly against adding another option to the -v short syntax (i.e., no :overlay option), but (option-wise) this would go in the "advanced" syntax, once implemented (similar/same as the --mount syntax used on docker service create)

@runcom I would like to better understand how you expect this to be used. Overlaying the host and container's directories together to get a combined directory doesn't seem like an understandable pattern (which layer is on top, making a writable directory in the container now read only, mounting parts of a merged overlay directory back onto itself as a lower).
I do a see a very obvious benefit of just overlay mounting instead of bind mounting a local directory. The upper directories could be managed with the container life cycle, but wonder if that means the upper directory is just another form of a volume. Is the purpose of this change more focused on isolating changes in mount or combining host and container directories?

@dmcgowan the main purpose right now is combining host and container directories as @rhatdan explained in https://github.com/docker/docker/pull/30786#issuecomment-279091743.
@dmcgowan it could be just another form of volume, but I found there are no ways to do this as a volume plugin. Also note, the code I put up here is by any means the right approach I think, just something to show.
Right now, as @thaJeztah pointed out, the -v and :overlay options aren't right and IMO ugly as well.

Would this volume be writable, or would it be "underneath" the container's writable layer?

@thaJeztah this overlay stuff will be mounted on top of the container's writable layer (I guess).

I believe we start with requiring it to be read/only, Making it writable should be carefully thought about and worked on.  A writable overlay requires an additional work directory on the same file system with the upper directory.  Doing this in an image would leave content that we might not want committed to a container.   Also not sure what we do when we commit, changes.

I see the benefit here, wondering a sane way to specify which is upper/lower (which will be the first thing ppl ask for once this is added).

It's tricky, but overall I'd expect changes to be saved in the container's filesystem, not in a volume. Otherwise if e.g. -v foo:/ would be used (currently we don't support / as target inside the container), everything ends up in the volume, so effectively it means we're providing a "custom" writable layer, not a volume.
Note that there's an existing proposal, which looks a bit similar; see https://github.com/docker/docker/issues/9382

It's tricky, but overall I'd expect changes to be saved in the container's filesystem

That would be tricky and I don't think we want to go down a direction of supporting overlay in overlay. This gets us into the realm of undefined behavior as any whiteouts written to the saved overlay mount would end up in the containers upper directory. It really shouldn't matter if the changes are persisted in a separate directory, it is already the expectation to user's that changes made in mounts will not be reflect on save/commit.

I see the benefit here, wondering a sane way to specify which is upper/lower (which will be the first thing ppl ask for once this is added).

@cpuguy83 right, what about something like:
docker run -ti -v /etc/pki:overlay,lower=/etc/host-pki,upper=/etc/image-pki fedora bash

The tricky part comes when people wants multiple lowers maybe:
docker run -ti -v /etc/pki:overlay,lower=/etc/host-pki:/etc/host-yum.repos.d/,upper=/etc/image-pki fedora bash

which separates each lower with a colon.
That said, starting with RO overlay mounts should remove this complexity as there won't be any real upper I guess.

@thaJeztah I see what you meant, I don't have a good answer for that other than what @dmcgowan already wrote.

Just to throw more wrinkles in this, even in the read/only mode, you might have more then two lowers.
But the syntax should follow the mount command syntax.

I cannot see how we can support all this with the -v syntax.

I cannot see how we can support all this with the -v syntax.

@cpuguy83 do you have anything in mind (other than what I've proposed in my last comment)? :disappointed:

It's not supported on the run CLI, but adding a new mount type for overlay. See https://github.com/docker/docker/blob/master/api/types/mount/mount.go#L21

We discussed this in the maintainers meeting, and we would like to discuss more in depth what the use case is, and if there are other solutions than this implementation.
@runcom could you open an issue with more details for the use case we're trying to solve here?

@runcom could you open an issue with more details for the use case we're trying to solve here?

can we discuss that here? :angel: I mean, this is not a ready PR, we started talking here about design and such, this wasn't mean as the implementation, just showing off what we mean

I think we're already going too deep into discussing the implementation that's proposed here and should take a step back and start with the use case, requirements, expectations, and go from there. From that PoV, having an issue describing that would be better.


Use conan version of Boost.LEAF

Remove internal/third_party directory
Make boost-leaf a requirement for libhal
Add boost-leaf to test requirements

This will not work until conan is actually on CCI.


Directory vs Folder

I think we should consider using the term "Folder" instead of "Directory".  This is for the UI, of course, because folder icons are used everywhere.  But, I don't think it would kill the UX of the cmd line.  It is 3 characters shorter and would avoid extra processing.

resolved.


Update tutorial-using-rest-apis.md

Fix the code sample related to tenant id.

@summerjune0730 : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hophan

#sign-off


Dungeon Generator class

TODO for DG as a class:

[x] Place rooms in the level, having them connected through connections and rotated to face one another
[x] Detect rooms being placed into each other, change rooms, and if none available - place it in another place
[ ] Put walls if connection is open
[ ] Have a static starting room and the ending room randomly placed

TODO for DG for a game:

[ ] Build some test rooms for a game
[ ] Make rooms have an enemy spawner, maybe changable props and materials

Second point added here.

To add 3rd point, need to make new rooms!


[opendistro-1.6][backport] Add validation for null elements in JSON array (#1157)

(cherry picked from commit 960d4209282027adedc0b37b28d74df8913dfafe)
opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1354 (ca9da85) into opendistro-1.6 (f4a82d6) will increase coverage by 0.16%.
The diff coverage is 79.06%.

@@                 Coverage Diff                  @@
##             opendistro-1.6    #1354      +/-   ##
====================================================
+ Coverage             62.72%   62.88%   +0.16%
- Complexity             2950     2975      +25
====================================================
  Files                   229      231       +2
  Lines                 16326    16397      +71
  Branches               3057     3069      +12
====================================================
+ Hits                  10240    10311      +71
+ Misses                 4507     4499       -8
- Partials               1579     1587       +8

Impacted Files
Coverage Δ

...arch/security/ssl/OpenDistroSecuritySSLPlugin.java
82.05% <0.00%> (ø)

...ort/OpenDistroSecuritySSLTransportInterceptor.java
0.00% <0.00%> (ø)

...lasticsearch/security/support/ConfigConstants.java
90.00% <ø> (ø)

...rch/security/setting/OpenDistroDynamicSetting.java
60.00% <60.00%> (ø)

...ticsearch/security/configuration/CompatConfig.java
38.23% <66.66%> (+10.64%)
:arrow_up:

.../security/setting/TransportPassiveAuthSetting.java
80.00% <80.00%> (ø)

...ecurity/configuration/ConfigurationRepository.java
74.54% <80.39%> (+4.84%)
:arrow_up:

...transport/OpenDistroSecuritySSLRequestHandler.java
53.57% <83.33%> (-2.84%)
:arrow_down:

...ty/transport/OpenDistroSecurityRequestHandler.java
71.64% <83.33%> (+0.91%)
:arrow_up:

...arch/security/filter/OpenDistroSecurityFilter.java
64.33% <88.88%> (+3.14%)
:arrow_up:

... and 15 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a661551...ca9da85. Read the comment docs.


Add recent news articles

Is your feature request related to a problem? Please describe.
Add recent news articles

Pricing options (free tiers)
https://newsdata.io
20 articles/requests a day
https://worldnewsapi.com/console/#Dashboard
1 request per second
https://newsapi.org/pricing
100 requests per day

Easy fix
Use iframe component in Streamlit to pull some news site panel.
Some websites like Google and Yahoo do not allow iframe embedding.

Stock API options
https://www.alphavantage.co/documentation/#news-sentiment
Limit: 5 / min; 500 / day

Design
Option #1: News carousel with panels scrolling on a horizontal axis.
https://stackoverflow.com/questions/77634432/dynamically-create-panels-in-streamlit


rn-nodeify vs node-libs-browser

I just came across module node-libs-browser (deprecated though because webpack5 did not include it) and it seems has very similar idea by provide wrapper of nodejs core to application. Can someone shed light on what is the difference between those 2 modules? Are they exchangeable in react native app?

similar purpose, but the browser and react-native environments are pretty different and require a different set of shims

I need integrate web3.js into a react native app. I have tried to install ipfs modules in react native app with the help of rn-nodeify and there were a few bundle issues which I could not solve. I am wondering if web3 has better chance with rn-nodeify. Any insight/experience is appreciated.


Support vacation mode for WG4-series thermostats

I mistakenly believed that vacation mode was not actually used for WG4-series thermostats. It is!
This PR correctly parses vacation fields. It still does not support scheduling vacation mode (just like WD5-series thermostats).

Tagged as v3.1.0!


Feat: Feast go support with HTTP Registry

What this PR does / why we need it:

Adds support for HTTP Registry in GO
Added support for redis with cluster mode

Which issue(s) this PR fixes:

Fixes #

Reverted the deleted GO specific changes
Fixed the Segmentation fault error during the feast apply process
HTTP Registry will retrieve/ cache only the project specific feast objects instead of all projects information
feast version is erroring out. Fixed it.
Fixed minor issues observed in GO code during the tests
Apache arrow is downgraded to 11.0.1 version due to open issue https://github.com/apache/arrow/issues/37442
Redis go version upgrade
Enabled datadog tracing for GO feature server
Fixed the issue with Response content-type for GO feature server from text to json
Using importlib instead of pkg_resources to avoid the deprecation warnings

A quick question: Why are we making this compatible with HTTP registry and not SQL registry? Seems that HTTP registry updates SQL tables and we can just pull feature metadata directly from the SQL server. If we depend on HTTP registry for this change, won't it be much harder to contribute this change back?

We need to contribute HTTP registry back to Feast.


How to create discrete inputs for credit card information (like in screenshot)

This screenshot displays a credit card input form with individual inputs for the card information (CC#, expiration, CVV) and also the name, country, and email:

Based on the Vue Stripe Elements example shown in the GitHub README.md, my single-file Vue component currently creates a single input for all the credit card information. It looks like this:

And this is the code that created it:
<template>
  <div>
    <StripeElements
      ref="elementsRef"
      :pk="publishableKey"
      :amount="amount"
      @token="tokenCreated"
      @loading="loading = $event"
    >
    </StripeElements>
    <button @click="submit">Pay ${{ amount / 100 }}</button>
  </div>
</template>

<script>
import { StripeElements } from "vue-stripe-checkout";

export default {
  components: {
    StripeElements
  },
  data: () => ({
    loading: false,
    amount: 1000,
    publishableKey: process.env.VUE_APP_PUBLISHABLE_KEY,
    token: null,
    charge: null
  }),
  methods: {
    submit() {
      this.$refs.elementsRef.submit();
    },
    tokenCreated(token) {
      this.token = token;
      // for additional charge objects go to https://stripe.com/docs/api/charges/object
      this.charge = {
        source: token.id,
        amount: this.amount, // the amount you want to charge the customer in cents. $100 is 1000 (it is strongly recommended you use a product id and quantity and get calculate this on the backend to avoid people manipulating the cost)
        description: this.description // optional description that will show up on stripe when looking at payments
      }
      this.sendTokenToServer(this.charge);
    },
    sendTokenToServer(charge) {
      // Send to charge to your backend server to be processed
      // Documentation here: https://stripe.com/docs/api/charges/create
      console.log(charge)
    }
  }
};
</script>

<style lang="scss" scoped></style>

However, after scouring its documentation, limited examples (here and its source code), and Issues section, I am unclear on how a credit card input form with individual inputs for the card information (CC#, expiration, CVV) and also the name, country, and email can be created.
I am hoping someone with experience with Stripe might be able to shed some light. Thank you.

Hello @rajsinghUSA thanks for this. You're probably looking for something like this right? The stripe element instance has a method called .create(name?, options?) that lets you create an element and mount it using the .mount(id) method. Creating dynamic elements  is not yet supported in this project. I can do this but I can't promise anything, as I am so busy right now, I hope you understand.
You can still achieve it by modifying the code of the Element.vue component.
Around line 84, you can create and mount separate elements such as cc number, expiry date, cvc, etc. instead of just the card element.

See #124


docs: update create-pages docs for root

Update create-pages.mdx for documenting the createRoot function for supporting customization of the top level tags.

Naming is hard. (I notice createRoot is also the name of a function from react-dom/client.)
It's up to you, but top-level layout or root-level layout sounds fine.


Fix FreeBSD SbrkRegion alignment issue

Please see discussion at #5806
@andralex @jmdavis

Not being particularly familiar with std.experimental.allocator, I can't really properly review these changes, but I can confirm that with these changes, the unit tests now pass again on my local FreeBSD system (which is TrueOS stable, so it's a 64-bit version of FreeBSD 12-to-be). And if you tested them on the 4 VMs like you said you were going to in the other PR, then presumably, it works for 10.3 and 11 for both 32-bit and 64-bit, but the autotesters with the newer versions of FreeBSD don't run for PRs.


Added message integrity check

Currently the endpoint is exposed to anyone and is vulnerable to message spoofing. While the recipient ID is probably unique (I have not tested if works across page tokens tho) it's still a good practice to verify that the message comes from the safe source.
I'm not happy with the commit and it's quite a draft. We should probably send a proper header code denying spoofed request.
Facebook reference which this PR is based on is available here: https://developers.facebook.com/docs/graph-api/webhooks#receiveupdates (one needs to scroll down a bit).

You are correct that the recipient's ID is unique, and it is scoped to the page as well, so someone couldn't hijack the endpoint to spam people, since they wouldn't have the correct user ID's. However, this is definitely something we should have! :smile: Definitely better safe than sorry when it comes to open endpoints like this.
The code looks good to me, though yeah, maybe we should send a different response if it's being denied. As well, we should have some tests of our signature algorithm to make sure it handles the edge cases Facebook mentioned with Unicode characters.
Also, do you think having an error event on the bot would be helpful? It would fire when things like this happen, so a developer can choose to track these errors, and be proactive about it. (maybe block the IP it's coming from or something, if it's spamming bad requests)
Overall, super awesome! Thanks for doing this. :tada:

@remixz
Thanks. I've tested it with a few messages with unicode characters and the signature matches.
When I added the aforementioned escaping, the check started to fail. I had no time to do more testing at the time so I don't know how it handles extreme edge cases. The event seems like a good idea, I'm nowhere close to being a javascript backend developer, therefore I don't know what design is commonly adapted by community under similar circumstances.
Have a great day, I'll write some tests tomorrow and test edge cases.

I just took a look, and Node should be automatically escaping when you update the digest, since it's internally turning the string into a Buffer with UTF-8 encoding. So, it should be all good there!
Once you add the tests tomorrow, then this should be good to go, aside from adding the error event, which I can do if you want. I can also add the documentation for this if you want me to. :smile:

I tried adding some tests, unsuccessfully. I can't find a way to properly encode body I think.
http://pastebin.com/b4BeUPAa
I used the exact same data facebook provided me with. The statusCode returned was 400 meaning the integrity check failed.

It looks like in your test's body, you didn't escape the Unicode characters. In https://github.com/remixz/messenger-bot/commit/ba128b9f5d1bdd45fac108b0851364d490c45392, I managed to get the tests to work, just had to escape the characters. I also simplified the signature generation code to use the digest and update functions, which makes it a bit smaller.
I did have to revert the change to send a 400 status code, since if Facebook gets a non-200 status code, it just keeps repeating the request until it gets a 200. I did add the error event though, so that should be good enough for developers to detect when something goes wrong.
Thanks again for your great work! :tada: I've added you as a collaborator to this repository. You can see the contribution guidelines here, if you haven't already. :smile:

Hello,
regarding the 400: If the message originates from the facebook platform the integrity check should never fail. Great work and thanks for spotting the issue.

I've released this as part of 2.0.0, along with some other changes: https://github.com/remixz/messenger-bot/blob/master/CHANGELOG.md The other big thing, in my opinion, is the 100% test coverage, so now everything definitely works! 😄


Error when running Tacotron GST with interactive_inference

It seems that the Tacotron GST doesn't support interactive inference.
Here model.py:395, when we do interactive mode, the code will call the create_interactive_placeholders() instead of the build_graph().
However, Tacotron GST requires "mel_spec" and "spec_length" input_tensors['source_tensors'] list, which were built here data/text2speech.py:366 in the build_graph() function.
So when running in interactive mode, the code will prompt an error when it runs this line
  File "t2s_interactive_run.py", line 36, in <module>     model_T2S, checkpoint_T2S = get_model(args_T2S, "T2S")   File "t2s_interactive_run.py", line 33, in get_model     args, base_config, config_module, base_model, None)   File "/xxxx/OpenSeq2Seq/open_seq2seq/utils/utils.py", line 790, in create_model     model.compile(checkpoint=checkpoint)   File "/xxxx/OpenSeq2Seq/open_seq2seq/models/model.py", line 411, in compile     gpu_id=gpu_cnt   File "/xxxx/OpenSeq2Seq/open_seq2seq/models/encoder_decoder.py", line 157, in _build_forward_pass_graph     encoder_output = self.encoder.encode(input_dict=encoder_input)   File "/xxxx/OpenSeq2Seq/open_seq2seq/encoders/encoder.py", line 138, in encode     return self._encode(self._cast_types(input_dict))   File "/xxxx/OpenSeq2Seq/open_seq2seq/encoders/tacotron2_encoder.py", line 163, in _encode     style_spec = input_dict['source_tensors'][2]

It does not support interactive inference.
The tacotron gst config does not have interactive_infer_params. But it will be fairly easy for you to add such functionality if you want.


Create automatic deployment for maven central

Create workflows

nexus staging plugin
Skip deployment of fat jars

Is done automatically by Deploy (Dev) if Version is no snapshot


CB-13260 Datalake cloud storage validation error on Azure in case of …

…non-subscription wide policies of the credential's service principal
In case of Azure single resourcegroup the roleassignment are queried from the resourcegroup instead of the subscription.

retest this please


HSEARCH-3540 The NONE Elasticsearch index lifecycle strategy throws an AssertionFailure

https://hibernate.atlassian.net//browse/HSEARCH-3540

Jenkins, retest this please

Pull Request Test Coverage Report for Build 1

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0006%) to 88.724%

Totals

Change from base Build 187:
0.0006%

Covered Lines:
16650

Relevant Lines:
18766

💛  - Coveralls

Merged, thanks.


if my dataset is csv file, how could I do to load my dataset as input to the mindspore

if my dataset is csv file, how could I load my dataset as input to hte mindspore

it seems that pass an obj as input to the mindspore model,how could i define my data obj?

Yes, MindSpore model needs an object of MindSpore Dataset. For csv files, now (0.3.0 release version), there are 2 ways:
1. Define a GeneratorDataset (API doc:
https://www.mindspore.cn/api/zh-CN/master/api/python/mindspore/mindspore.dataset.html#mindspore.dataset.GeneratorDataset).  You need to define a function to parse your csv files as input of 'source' parameter of GeneratorDataset. In your parsing function, you could use whatever third-party packages to process your csv files, e.g., pandas, numpy.
2. Convert csv files into mindrecord format, and then define a MindDataset.
This is a high-performance way to deal with various datasets. In general scenario, MindDataset costs less time than GeneratorDataset. Please check the following reference:
https://www.mindspore.cn/tutorial/en/master/use/data_preparation/converting_datasets.html
https://www.mindspore.cn/api/en/0.3.0-alpha/api/python/mindspore/mindspore.dataset.html#mindspore.dataset.MindDataset
Actually, both GeneratorDataset and mindrecord are very flexible ways to load dataset. They can almost deal with any dataset.


murmur.js: inspect block events by block number

@driemworks do we still want this feature? as well as #11 this can be achieved by querying polkadotjs or etf.js
This way we keep murmur.js only as an interface to the API

No, we don't really need this anymore

not needed anymore


unify setFrom and getFor methods in schema

reduce setFrom* to one function:
 setPrimaryKey(source: constants.SOURCE, item: Object, data: Object)
 setFrom(source: constants.SOURCE, item: Object, data: Object, options: Object)

reduce getFor* to one function:
 getPrimaryKey(source: constants.TARGET, item: Object)
 getFor(source: constants.TARGET, item: Object)

Current status:

[] setPrimaryKey
[x] setFrom
[] getPrimaryKey
[] getFor


Support for k,v in d.items

https://github.com/pikasTech/pikascript/commit/2884d51c7269d7e3de1a54024f37ae705c3a3dee


Update sprayproxy production

Included PRs:

https://github.com/redhat-appstudio/sprayproxy/pull/59
https://github.com/redhat-appstudio/sprayproxy/pull/60

/retest-required

/lgtm


Do we want to permit typed senders to advertise that they don't call set_value by setting value_types to Variant<>?

Same Q about error_types. See #228 for the sorts of trouble this causes.

Is this moot with the receiver requirement changes?


Repository reorganization

Codecov Report
Base: 96.18% // Head: 95.31% // Decreases project coverage by -0.86% :warning:

Coverage data is based on head (3b35d7e) compared to base (98b3315).
Patch coverage: 76.08% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
- Coverage   96.18%   95.31%   -0.87%
==========================================
  Files          14       15       +1
  Lines        1022     1068      +46
==========================================
+ Hits          983     1018      +35
- Misses         39       50      +11

Impacted Files
Coverage Δ

gvdb/src/gresource/builder.rs
98.00% <ø> (ø)

gvdb/src/gresource/error.rs
100.00% <ø> (ø)

gvdb/src/gresource/xml.rs
100.00% <ø> (ø)

gvdb/src/read/error.rs
95.65% <ø> (ø)

gvdb/src/read/file.rs
100.00% <ø> (ø)

gvdb/src/read/hash.rs
87.30% <ø> (ø)

gvdb/src/read/hash_item.rs
100.00% <ø> (ø)

gvdb/src/read/header.rs
100.00% <ø> (ø)

gvdb/src/read/pointer.rs
100.00% <ø> (ø)

gvdb/src/util.rs
100.00% <ø> (ø)

... and 5 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Can't confirm font size

Hi, I use Manjaro-i3. After few days I'm trying to configure fonts but when I run bmenu -> 3 Set font then choose a font and type in the size, I cannot confirm it. Tried enter - does nothing, escape - same, even tried insert - it's the only one that gives an output:
Wrong. Press any key and try again

How do I confirm the font size?

This is the problem:
# /usr/bin/appearance-menu
273 function numberinput {
           [...]
277     while true; do
278         read -s -n 1 schar
           [...]
284         $'\n')   #Enter
285             break
286             ;;

You have to check for empty character instead to be compatible with all terminals:
'')   #Enter
    break;;


fix: grafana exclusion

I previously used the json's additionalEventData.action instead of eventName. This change fixes it.
We may want to exclude these too

grafana.amazonaws.com:create_update
ssm.amazonaws.com:StartSession

@nitrocode thanks for the contribution!


CS: fix compliance with PSR12

Proposed Changes
PHPCS 3.5.0+ contains a far more complete PSR12 ruleset.

The current code didn't fully comply with that ruleset. Some minor code tweaks fix that.
PSR12 demands constant visibility to be declared, but as this project still supports PHP 5.3 and constant visibility wasn't introduced until PHP 7.1, this is not desirable. Excluding that particular rule from within the ruleset fixes that.

Related Issues

https://github.com/squizlabs/php_codesniffer/releases

@mjrider Thanks. Now we have a passing build again, I'll be sending in some more PRs to further improve the testing of the plugin. I'm sending them in staged as otherwise we'd have to fix conflicts all the time.


setExternalSubset() not working as documented

Consider the following, slightly adapted from setExternalSubset doco:
use LibXML::Document;
use LibXML::Dtd;

my LibXML::Document $doc .= parse: string => '<foo/>';
my LibXML::Document $other-doc .= parse: :file<test/dtd/note-external.xml>, :dtd;

my LibXML::Dtd:D $dtd = $other-doc.getExternalSubset;
$doc.setExternalSubset: $dtd.clone();
note $doc.Str;

Output is:
<?xml version="1.0" encoding="UTF-8"?>
<foo/>

I.e. is being ignored and no affect on the output.

setExternalSubset() sets a Dtd for validation only.
setInternalSubset() has been amended, along with doco. It now calls xmlCreateInSubset() to create a new Dtd, correctly inserted into the document's tree.
Further work needed to copy or construct validation rules.

Redoing fix to bring it into line with Perl XML::LibXML.
Amending domSetInternalSubset to call xmlAddChildren xmlAddPrevSibling to link the node into document root. Somehow lost these lines during migration.

domSetInternalSubset() now inserts the DtD into the document root, similar function in Perl XML::LibXML.
Also automatically make a copy of an imported DtD.


The Yeaoman<EMAIL_ADDRESS>comes with no scaffold support for tests files

Category

[X] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

The Yeaoman<EMAIL_ADDRESS>comes with no scaffold support for tests files for React and JavaScript client side solution templates. That feature was present in older versions and was useful to 3 teams within my organization.
What might be the reason for removing that from a newly created web part scaffolded by the Yeaoman generator?
Maybe option for including the test folder and test file in the solution upon creation could be beneficial. Something similar to Visual Studio that has check box allowing to include Tests project in your C# solution upon solution creation.

Thx @VelinGeorgiev  for reporting, let me follow up on this internally. We should definitely not remove anything without proper documentation in release notes.

@VesaJuvonen , @patmill do you know what would be the future of the SharePoint testing framework and packages so we can eventually plan migration if that would be deprecated.

Ideally, wouldn't it be the best if the SharePoint Framework allowed us to use any testing framework we want?  As long as things just work and developers can use the testing framework of their choice, I'd say it's not necessary for Yeoman to scaffold tests by default.

I agree with that. It is just we had one setup provided OOTB and we decided to use it in the past. If this is going to be deprecated, it would require technological time for us to migrate and that has to be communicated.

@waldekmastykarz - Will you create a user voice entry for your recommendation?  Myself and my colleagues will up vote it.

stumbled on this issue recently trying to debug unit tests with 1.4.1 and see what's missing. Agree with the fact that spfx should be "test framework agnostic" and let the community provide samples for different options. My original post from almost a year ago https://github.com/SharePoint/sp-dev-docs/issues/736


test: simplify minitest inclusion.

The previous version seems needlessly complicated given we only support a single Ruby version. It was also blowing up on Bundler 1.15.X.

I think this broke assert_predicate. I can't immediately see what else would've done so.
Error: makeicns: failed
undefined method `assertions' for #<Formulary::FormulaNamespacea1183c3e8b2cd1078c485d8b562c8009::Makeicns:0x007fdb712d6e60>
/Library/Ruby/Gems/2.0.0/gems/minitest-5.10.1/lib/minitest/assertions.rb:135:in `assert'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/test/unit/assertions.rb:38:in `assert'
/Library/Ruby/Gems/2.0.0/gems/minitest-5.10.1/lib/minitest/assertions.rb:307:in `assert_predicate'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/makeicns.rb:30:in `block in <class:Makeicns>'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1639:in `block (2 levels) in run_test'
/usr/local/Homebrew/Library/Homebrew/formula.rb:832:in `with_logging'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1638:in `block in run_test'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:14:in `block in mktemp'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:74:in `block in run'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:74:in `chdir'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:74:in `run'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:13:in `mktemp'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1632:in `run_test'
/usr/local/Homebrew/Library/Homebrew/test.rb:28:in `block in <main>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
/usr/local/Homebrew/Library/Homebrew/test.rb:27:in `<main>'

Error: domt4/crypto/curl-max: failed
undefined method `assertions' for #<Formulary::FormulaNamespace18a84273f2db472a3ba2f823ee83f1df::CurlMax:0x007fa9ab9010f8>
/Library/Ruby/Gems/2.0.0/gems/minitest-5.10.1/lib/minitest/assertions.rb:135:in `assert'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/test/unit/assertions.rb:38:in `assert'
/Library/Ruby/Gems/2.0.0/gems/minitest-5.10.1/lib/minitest/assertions.rb:307:in `assert_predicate'
/usr/local/Homebrew/Library/Taps/domt4/homebrew-crypto/Formula/curl-max.rb:181:in `block in <class:CurlMax>'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1639:in `block (2 levels) in run_test'
/usr/local/Homebrew/Library/Homebrew/formula.rb:832:in `with_logging'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1638:in `block in run_test'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:14:in `block in mktemp'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:74:in `block in run'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:74:in `chdir'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:74:in `run'
/usr/local/Homebrew/Library/Homebrew/extend/fileutils.rb:13:in `mktemp'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1632:in `run_test'
/usr/local/Homebrew/Library/Homebrew/test.rb:28:in `block in <main>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
/usr/local/Homebrew/Library/Homebrew/test.rb:27:in `<main>'

iMac-TMP:~ joe$ brew test makeicns
Testing makeicns
==> Using the sandbox
==> /usr/local/Cellar/makeicns/1.4.10a/bin/makeicns -in /usr/local/Homebrew/Library/Homebrew/test/sup
iMac-TMP:~ joe$ unset HOMEBREW_FORCE_VENDOR_RUBY
iMac-TMP:~ joe$ brew test makeicns
Testing makeicns
==> Using the sandbox
==> /usr/local/Cellar/makeicns/1.4.10a/bin/makeicns -in /usr/local/Homebrew/Library/Homebrew/test/sup
iMac-TMP:~ joe$

HOMEBREW_CACHE=/usr/local/var/homebrewcache
HOMEBREW_LOGS=/usr/local/var/homebrewcache/logs
HOMEBREW_DEVELOPER=1
HOMEBREW_SANDBOX=1
HOMEBREW_NO_AUTO_UPDATE=1
HOMEBREW_NO_ANALYTICS=1
HOMEBREW_ENV_FILTERING=1
HOMEBREW_EDITOR=code-insiders
HOMEBREW_GIT=/usr/local/opt/git/bin/git
HOMEBREW_GITHUB_API_TOKEN=blah

HOMEBREW_VERSION: 1.2.3-121-gb55290849
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: b5529084906af89827f6d9befd613457a1615918
Last commit: 2 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 71083d172d5786aeabf6c606f56e00f8cdb2c6af
Core tap last commit: 2 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.0.0-p648
Clang: 8.1 build 802
Git: 2.13.2 => /usr/local/opt/git/bin/git
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
Java: 1.8.0_131
macOS: 10.12.6-x86_64
Xcode: 8.3.3
CLT: <IP_ADDRESS>.1.1492020469
X11: N/A

That config readout is technically incorrect FWIW, but doesn't seem to make a difference even when I unset HOMEBREW_ENV_FILTERING.

This is the additional debug output:
Error: makeicns: failed
undefined class/module Debrew::
/usr/local/Homebrew/Library/Homebrew/utils/fork.rb:39:in `load'
/usr/local/Homebrew/Library/Homebrew/utils/fork.rb:39:in `block (3 levels) in safe_fork'
/usr/local/Homebrew/Library/Homebrew/utils.rb:396:in `ignore_interrupts'
/usr/local/Homebrew/Library/Homebrew/utils/fork.rb:26:in `block (2 levels) in safe_fork'
/usr/local/Homebrew/Library/Homebrew/utils/fork.rb:7:in `open'
/usr/local/Homebrew/Library/Homebrew/utils/fork.rb:7:in `block in safe_fork'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/tmpdir.rb:88:in `mktmpdir'
/usr/local/Homebrew/Library/Homebrew/utils/fork.rb:6:in `safe_fork'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/test.rb:70:in `block in test'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/test.rb:29:in `each'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/test.rb:29:in `test'
/usr/local/Homebrew/Library/Homebrew/brew.rb:93:in `<main>'

Yep it crashes if I first run sudo /usr/bin/gem install minitest

sudo /usr/bin/gem uninstall minitest

and it's back to normal.

And indeed if I revert this PR, it works either way.

Aye, sudo /usr/bin/gem uninstall minitest resolved the problem for me locally, thanks.

I'm 👍 on changing this behaviour (perhaps as part of https://github.com/Homebrew/brew/pull/2841?) and 👎 on reverting as-is as the lack of comments meant I had no idea why this code did what it does and it was breaking on our test-bot CI with Bundler 1.15.X (and Homebrew/brew CI when the cache was invalidated).


Add webpack example

Comes from https://github.com/VictorBjelkholm/webpack-node-ipfs-api-demo which I'll deprecate if we decide to merge this.

@dignifiedquire thanks for the review. The example comes from a quick setup I did, coming from Dan's react hot boilerplate. I'll address the things you've mentioned, and also remove the findprovs part (since it's out of scope of the example). Thanks!

Sweeeet! :D
Can we call the folder bundle-webpack so that then we also have bundle-browserify?
Also, can you add a README just explaining what people are doing with all of this pieces? Or even just say?  Also update the readme section https://github.com/ipfs/js-ipfs-api#in-a-web-browser-through-browserify to point to both examples :)

Thanks for the feedback, everything have been addressed now!
@diasdavid @dignifiedquire please take a look again and merge if :+1:

@diasdavid linting should pass now, yes.


Add example of go-zero

Codecov Report

Merging #79 (34e5eca) into main (817dea3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #79   +/-   ##
=======================================
  Coverage   89.53%   89.53%
=======================================
  Files           1        1
  Lines          86       86
=======================================
  Hits           77       77
  Misses          5        5
  Partials        4        4

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 817dea3...34e5eca. Read the comment docs.


BIT operators

Relates to https://github.com/crate/crate/issues/5463

Found out an issue with printing statements via a new test case (not yet pushed), will resolve it

Found out an issue with printing statements via a new test case (not yet pushed), will resolve it

Resolved in https://github.com/crate/crate/pull/13278/commits/6cab3d2c44ce2f4166f69464c2aa299e6cdc13bd

unrelated failure Could not resolve com.github.jk1:gradle-license-report:2.1.
retest this please

Could not resolve com.github.jk1:gradle-license-report:2.1.
retest this please


Sync ballerina 1.0.x to next release

Purpose

$subject

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #20094 into next-release will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           next-release   #20094   +/-   ##
=============================================
  Coverage         20.51%   20.51%
=============================================
  Files                52       52
  Lines              1394     1394
  Branches            216      216
=============================================
  Hits                286      286
  Misses             1095     1095
  Partials             13       13

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3341f18...45323de. Read the comment docs.


Ruff does not signal E999 SyntaxError on literal assignment.

I'm using Ruff v0.0.286 in the following.
For the following Python code:
#!/usr/bin/env python
5 = 3

No output is generated from ruff when analyzed:
user@host $ ruff literal_assign.py

When run from Python:
user@host $ python literal_assign.py
  File "/home/user/literal_assign.py", line 2
    5 = 3
    ^
SyntaxError: cannot assign to literal here. Maybe you meant '==' instead of '='?

When analyzed with flake8:
user@host $ flake8 literal_assign.py
literal_assign.py:2:2: E999 SyntaxError: cannot assign to literal here. Maybe you meant '==' instead of '='?

Yeah the parser is more permissive than the Python interpreter -- this is better than being less permissive (i.e., rejecting valid code), but it'd be nice to error here.


Rename vertica node js package

I went ahead and made the changes to ensure the test results are the same.    I compared this branch to master and had identical results.  However, if we merge this PR we will also need to rename the git repo to vertica-node-js.   After browsing names on npmjs.com, I think vertica-node-js is a better name anyway.   As long as we think this is the right direction, I vote to do it.

I also bumped the version numbers of all four packages to 0.9.0-pre.3 because v-pool declares a peerDependency:
"peerDependencies": {
"vertica-node-js": "0.9.0-pre.3"
}
I'm curious why v-pool is the only one that does this.   My understanding of what this means is it will cause a warning if any other versions of vertica-node-js are used with v-pool other than 0.9.0-pre.3.   Why is this declared on v-pool but none of the other packages?

We decided not to do this.  We are staying with vertica-nodejs


Limit on number of end points

I need more than 16 endpoints.
I (3114) esp_matter_core: Dynamic endpoint 13 added
I (3114) esp_matter_attribute: ********** Endpoint 0x000E's Cluster 0x0003's Attribute 0x0001 is 0 **********
I (3114) esp_matter_attribute: ********** Endpoint 0x000E's Cluster 0x0004's Attribute 0x0000 is 128 **********
I (3124) esp_matter_attribute: ********** Endpoint 0x000E's Cluster 0x0004's Attribute 0xFFFC is <invalid type: 0> **********
I (3144) esp_matter_core: Dynamic endpoint 14 added
I (3144) esp_matter_attribute: ********** Endpoint 0x000F's Cluster 0x0003's Attribute 0x0001 is 0 **********
I (3154) esp_matter_core: Dynamic endpoint 15 added
E (3164) esp_matter_core: Error adding dynamic endpoint 16: 0x89
E (3174) esp_matter_core: Error adding dynamic endpoint 17: 0x89
E (3174) esp_matter_core: Error adding dynamic endpoint 18: 0x89
E (3184) esp_matter_core: Error adding dynamic endpoint 19: 0x89
E (3194) esp_matter_core: Error adding dynamic endpoint 20: 0x89
E (3194) esp_matter_core: Error adding dynamic endpoint 21: 0x89
E (3204) esp_matter_core: Error adding dynamic endpoint 22: 0x89
E (3214) esp_matter_core: Error adding dynamic endpoint 23: 0x89
E (3214) esp_matter_core: Error adding dynamic endpoint 24: 0x89
E (3224) esp_matter_core: Error adding dynamic endpoint 25: 0x89

32 at least, that gives room for seven bridged devices, 40 would be better.

Hello @jonsmirl

I recreated your issue by trying to add more than 16 endpoints  (on_off endpoints) in the light example.
Seems like there is a limit of 16 endpoints by default.  Maximum dynamic endpoint count is governed by a macro CHIP_DEVICE_CONFIG_DYNAMIC_ENDPOINT_COUNT

You can find and change this limit, <your_app>/main/zap_generated/endpoint_config.h - light/main/zap_generated/endpoint_config.h.

Logs for my setup - ( I created 20 endpoints in app_main)
After updating the number of maximum dynamic endpoints ( CHIP_DEVICE_CONFIG_DYNAMIC_ENDPOINT_COUNT = 20)

this works.


Download failed: Not Found

I've just installed the latest version of Web2Exe and every time I try to export I get this message as soon as the app tries to download the ZIP for any platform.

This is because you're trying to export to Mac OSX 32 bit, which doesn't exist for NW.js > 0.12.X. Switch to 64 bit and it should be good.


Document the code

Documentation can be easily generated from the Go code, but we need to add comments and consider what pieces that we actually want to be exported.
https://pkg.go.dev/github.com/cloudstruct/go-ouroboros-network
https://pkg.go.dev/about
https://go.dev/blog/godoc
https://tip.golang.org/doc/comment
https://mdaverde.com/posts/golang-local-docs/

This has been split into per-package tickets.

For my own reference, the in-progress docs can be viewed with:
$ ~/go/bin/pkgsite -http <IP_ADDRESS>:8080


Move heatmap button

The comparative heatmap button should be moved to the bottom of the "switch-datasets-card" (a ruler should divide the selected cards from actions that can be performed on the card).

Fixed in #05b6ceb287173dcd70dd5889970f161f603ae08d


As a User I want to be able to run GNdiff as a server with reference data cached.

I will move cached reference data into a separate issue


Scale up the pod number of bookie or broker cant improve the performance of throughput and my hardware resource is still free enough

Describe the bug
I deployed pulsar with k8s. We need 25w/s(1k size msg) throughput, however it can only provide 9w/s throughput with perf tool. By the way, its far away from the official test report. I tried to scale up the pod number of bookie and broker, but it worked nothing for me and I found my hardware is still free enough. What's wrong with my operation?
To Reproduce
See description
Expected behavior
Support horizontal expansion
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: k8s, pulsar version 2.8

Additional context
Add any other context about the problem here.

@kingboung
Could you provide more details like "broker.conf", "bookkeeper.conf", machine resources, etc.?
These are very useful for diagnosing your problem.

@mattisonchao
no problem, please see the zip file   pulsar.zip
pvc detail


Sync master with develop

Implementation notes
Add any additional information about the change that isn't captured in the ticket.
Checklist

[ ] Has the branch been rebased to develop?
[ ] Automated tests (Any of the following when applicable: Unit, Functional or Acceptance)
[ ] Manual compatibility testing (Browsers: Chrome, Firefox, IE11, Safari)

Yeah - me too. Somehow master was behind develop by 5 commits but zero file changes


Release Schedule

Hi,
Just curious how you determine when to put together new releases and push them to Docker Hub. I expect that I will be getting more involved with this project and it would be nice to have an idea of when things are expected to go from master into an official image.

Close this issue for now.
@crberube we have some security rules to workaround a github bot user, which is required from DockerHub. Therefore, right now the builds on https://hub.docker.com/r/checkr/flagr/tags are not automated and fully transparent with Dockerfile tagged. I will update here if I have some new solutions to share.


Write a generic kzip verification tool

When testing extraction, it can be useful to have a tool that opens a kzip and checks its contents against the repo you just tried to extract, to verify that you have good coverage.
kythe/go/extractors/config/smoke is an example of such a tool, but it's (a) hard-coded to live in Docker-in-Docker land, and (b) works on kindex files because it predates kzip's adoption in kythe.
So something that both supports kzip and is more isolated to checking a single archive&repo pair (or archive vs. previous archive maybe) would be more generally useful.

#3336 is a first pass at this.
Other thought: we should check for corpus and emit something if it isn't set.  Down the road, that should also compare against expected corpus for the repo and emit something if it doesn't match (unclear what the source of truth is there)/


'updated_at' in field list is ambiguous

Laravel Version: 5.4.24
PHP Version: 5.6.30
Database Driver & Version: MYSQL  5.5.54,

Description:
This happens to me when I execute the following line:
$usuarioE->roles()->update(['kaseya_rol_user.state'=>0]);
It is an update of a field in the PivotTable of a many to many relationship between two tables.
Error:
[Illuminate\Database\QueryException]
  SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'updated_at' i
  n field list is ambiguous (SQL: update `kaseya_roles` inner join `kaseya_ro
  l_user` on `kaseya_roles`.`id` = `kaseya_rol_user`.`rol_id` set `kaseya_rol
  _user`.`state` = 0, `updated_at` = 2017-06-21 22:03:59 where `kaseya_rol_us
  er`.`user_id` = 11)

The serious solution, specifying the name of the table but not how to do it with that field (updated_at)t

Please share the relationship definition.

Closing for lack of activity.


Fix state_lines in night-vision

@PetersonGIS any idea when this one will be addressed?

Two ways to fix this:

I can simply remove the state_lines reference in the style
We can fix the state_lines data by re-adding it to the toml and reimporting (it was commented out of the toml at one point because it wasn't loading properly, and now I believe it has been removed altogether)

Fixed via method 1 above. At some point we need to re-add state_lines to the data though.