Xiaomi Vacuum no longer works in 0.57

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.57.0
Python release (python3 --version):
3.6.1
Component/platform:
vacuum/xiaomi_miio
Description of problem:
With the upgrade to 0.57 (from 0.56.2), my vacuum's status is unavailable. I cannot control the vacuum at all, nor can I see any data coming into it. I can confirm that it is connected to my LAN (given that I can still connect through the MiHome app). I can also confirm that my token is the same as always.
Expected:
The opposite.
Problem-relevant configuration.yaml entries and steps to reproduce:
vacuum:
  platform: xiaomi_miio
  host: <IP_ADDRESS>
  token: xxxxxxxxxxxxxxxxxxxxxxxxxx

Launch HASS 0.57

Traceback (if applicable):
The logs are filled with these messages:
2017-11-04 11:31:44 ERROR (SyncWorker_18) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:32:05 ERROR (SyncWorker_2) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:32:25 ERROR (SyncWorker_12) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:32:45 ERROR (SyncWorker_17) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:33:06 ERROR (SyncWorker_10) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:33:27 ERROR (SyncWorker_18) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:33:48 ERROR (SyncWorker_7) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:34:09 ERROR (SyncWorker_18) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:34:30 ERROR (SyncWorker_3) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:34:51 ERROR (SyncWorker_8) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:35:12 ERROR (SyncWorker_18) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:35:33 ERROR (SyncWorker_3) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:35:54 ERROR (SyncWorker_7) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:36:15 ERROR (SyncWorker_7) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:36:36 ERROR (SyncWorker_3) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:36:57 ERROR (SyncWorker_19) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:37:18 ERROR (SyncWorker_0) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:37:39 ERROR (SyncWorker_17) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:38:00 ERROR (SyncWorker_17) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:38:21 ERROR (SyncWorker_12) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:38:42 ERROR (SyncWorker_9) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:39:03 ERROR (SyncWorker_9) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:39:24 ERROR (SyncWorker_13) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:39:44 ERROR (SyncWorker_12) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:40:05 ERROR (SyncWorker_12) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:40:26 ERROR (SyncWorker_5) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:40:47 ERROR (SyncWorker_0) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:41:08 ERROR (SyncWorker_8) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:41:29 ERROR (SyncWorker_0) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:41:50 ERROR (SyncWorker_13) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:42:11 ERROR (SyncWorker_19) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:42:32 ERROR (SyncWorker_14) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:42:53 ERROR (SyncWorker_9) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:43:14 ERROR (SyncWorker_3) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:43:35 ERROR (SyncWorker_8) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:43:56 ERROR (SyncWorker_9) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:44:17 ERROR (SyncWorker_10) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:44:38 ERROR (SyncWorker_14) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:44:59 ERROR (SyncWorker_12) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:45:20 ERROR (SyncWorker_5) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:45:41 ERROR (SyncWorker_15) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:46:02 ERROR (SyncWorker_9) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:46:23 ERROR (SyncWorker_14) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:46:44 ERROR (SyncWorker_19) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:47:05 ERROR (SyncWorker_2) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:47:26 ERROR (SyncWorker_10) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:47:47 ERROR (SyncWorker_13) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:48:08 ERROR (SyncWorker_5) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:48:29 ERROR (SyncWorker_15) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:48:50 ERROR (SyncWorker_10) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:49:11 ERROR (SyncWorker_8) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:49:32 ERROR (SyncWorker_0) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:49:53 ERROR (SyncWorker_3) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:50:14 ERROR (SyncWorker_11) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:50:35 ERROR (SyncWorker_18) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:50:56 ERROR (SyncWorker_14) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:51:17 ERROR (SyncWorker_17) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:51:38 ERROR (SyncWorker_13) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:51:59 ERROR (SyncWorker_0) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:52:20 ERROR (SyncWorker_8) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:52:41 ERROR (SyncWorker_1) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:53:02 ERROR (SyncWorker_3) [miio.device] Unable to discover a device at address <IP_ADDRESS>
2017-11-04 11:53:23 ERROR (SyncWorker_19) [miio.device] Unable to discover a device at address <IP_ADDRESS>

Additional info:
This may be related to https://github.com/home-assistant/home-assistant/issues/10210; however, unlike that ticket, in this case, I cannot control my vacuum from HASS whatsoever.
CC: @rytilahti, @syssi

I can not replicate this problem..
Are you able to discover it using https://github.com/rytilahti/python-miio ?

@olskar Unfortunately, no. The device is definitely connected to the LAN:

...but when I run this command:
$ mirobo --ip <IP_ADDRESS> --token xxxxxxxxxxxxxxxxxxxxxxxxxxxx

...I get this output:
ERROR:miio.vacuum_cli:Unable to read the stored msgid: [Errno 2] No such file or directory: '/tmp/python-mirobo.seq'
ERROR:miio.device:Unable to discover a device at address <IP_ADDRESS>
Traceback (most recent call last):
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/bin/mirobo", line 11, in <module>
    sys.exit(cli())
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 1043, in invoke
    return Command.invoke(self, ctx)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/vacuum_cli.py", line 86, in cli
    ctx.invoke(status)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/decorators.py", line 64, in new_func
    return ctx.invoke(f, obj, *args[1:], **kwargs)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/vacuum_cli.py", line 116, in status
    res = vac.status()
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/vacuum.py", line 99, in status
    return VacuumStatus(self.send("get_status")[0])
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 165, in send
    self.do_discover()
  File "/Users/abach/.local/share/virtualenvs/miio-Q_DY263b/lib/python3.6/site-packages/miio/device.py", line 118, in do_discover
    raise DeviceException("Unable to discover the device %s" % self.ip)
miio.device.DeviceException: Unable to discover the device <IP_ADDRESS>

I've hard reset the device, but that didn't seem to change anything.

Which FW version is running on the vacuum?

3.3.9_003307

im on <IP_ADDRESS>077, not sure if you are on higher version or its a typo (assuming the latter).
I'm on hass.io so I cant replicate your issue. With my setup there is (except the same discovery logs) no issue with actual function of the device.
Did you setup the battery/fan/etc sensors. Does any of them work at all ?

I too have this same issue, updated from 0.56.2 to 0.57.1 and get the same error messages as bachya. Running firmware <IP_ADDRESS>077, and on hass.io

Seems to be a bug in mirobo, not home assistant
https://github.com/rytilahti/python-miio/issues/92

@ferdydek I had several sensors pulling data from the vacuum; currently, no values appear:

Got it figured it. At some point, it looks like the token changed on me; rediscovered it (using the instructions on the website) and everything started working again. Going to close.


main-min build of front end throws Exception

comamitc@ubuntu:~/dev/pretty-print.net/frontend$ lein cljsbuild auto
Compiling ClojureScript.
Compiling "public/js/main.min.js" from ["src-cljs"]...
Jan 18, 2015 11:40:20 PM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: /home/comamitc/dev/pretty-print.net/frontend/target/cljsbuild-compiler-0/cljs/core.js:19519: ERROR - Parse error. '}' expected

Jan 18, 2015 11:40:20 PM com.google.javascript.jscomp.LoggerErrorManager printSummary
WARNING: 1 error(s), 0 warning(s)
ERROR: JSC_PARSE_ERROR. Parse error. '}' expected at /home/comamitc/dev/pretty-print.net/frontend/target/cljsbuild-compiler-0/cljs/core.js line 19519 : 0
Successfully compiled "public/js/main.min.js" in 4.267 seconds.
Compiling "public/js/main.js" from ["src-cljs"]...
Successfully compiled "public/js/main.js" in 3.399 seconds.

This prevents html page from loading.

oakmac@oakmac-desktop:~/pretty-print.net/frontend$ lein clean && lein cljsbuild auto
Compiling ClojureScript.
Compiling "public/js/main.min.js" from ["src-cljs"]...
Successfully compiled "public/js/main.min.js" in 10.565 seconds.
Compiling "public/js/main.js" from ["src-cljs"]...
Successfully compiled "public/js/main.js" in 6.723 seconds.

I added some lein clean targets; this might have been the problem. Try again?


feat(OperatorNorm/Prod): norm of first/second projection

Operator norm of the projection maps E × F → E and E × F → F for (semi)normed spaces

Thanks for the review, I have made the changes as requested.


Wrong Provider name is reported in airnode-client log metadata

Description
When there are multiple Providers specified for a chain, the Airnode logs report incorrect Provider names within the log metadata, see the example below.
Version
Airnode v0.9, v0.10, master.
Present Behaviour
In config.json there are two providers:
     "id": "5",
      "providers": {
        "goerliPublic": {
          "url": "https://rpc.ankr.com/eth_goerli"
        },
        "goerliTestnet1": {
          "url": "${GOERLI_PROVIDER_URL}"
        }

Yet in the logs (in multiple places, below is one example), the metadata Provider is incorrect for one (they both say Provider:goerliTestnet1 at the end of the line on the far right):
2023-04-01 21:29:04 [2023-04-02 04:29:04.067] INFO Initialized EVM provider:goerliPublic                                            Coordinator-ID:ca47f3d2387ced05, Chain-ID:5, Provider:goerliTestnet1
2023-04-01 21:29:04 [2023-04-02 04:29:04.068] INFO Initialized EVM provider:goerliTestnet1                                          Coordinator-ID:ca47f3d2387ced05, Chain-ID:5, Provider:goerliTestnet1

This makes troubleshooting confusing as it is not clear what provider the logs are attributable to.
Expected Behaviour
Log metadata should report the correct Provider names.
Steps to reproduce
Run Airnode with more than one Provider.

As a note, I'm pretty sure that this is a somewhat new issue because I went through a lot of multi-provider logs a few months ago. Makes me think that this may be related to that v0.10 issue.

It turns out both are true. The issue doesn't affect Airnode deployed to AWS (v0.9 or v0.10), but does affect airnode-client back to at least v0.9, and including v0.10 and master which I tested when creating the issue.
airnode-client:0.9.2
2023-04-02 11:45:03 [2023-04-02 18:45:03.880] INFO Initialized EVM provider:goerliPublic        Coordinator-ID:6af849d09ace5cb9, Chain-ID:5, Provider:goerliTestnet1
2023-04-02 11:45:03 [2023-04-02 18:45:03.880] INFO Initialized EVM provider:goerliTestnet1      Coordinator-ID:6af849d09ace5cb9, Chain-ID:5, Provider:goerliTestnet1

airnode-deployer:0.9.2 and airnode-deployer:0.10.0
AWS logs:
The startCoordinator logs don't have Provider as metadata
INFO [2023-04-02 19:29:11.671] INFO Initialized EVM provider:goerliPublic Coordinator-ID:538bad185ef80309
INFO [2023-04-02 19:29:11.671] INFO Initialized EVM provider:goerliTestnet1 Coordinator-ID:538bad185ef80309

And the run logs depict sets for each of the Providers with the appropriate Provider metadata.
I did notice that among the two run log streams, it seems arbitrary which provider is used for each stream for each cycle. I'm not sure if this is configurable, but it'd be nice if it was a single stream for each provider and rather than intermingled. For example, INFO Pending requests logs for 6 cycles in stream 1 had the following Providers:
Provider:goerliTestnet1
Provider:goerliTestnet1
Provider:goerliPublic
Provider:goerliPublic
Provider:goerliTestnet1
Provider:goerliPublic

And stream 2 had the opposite Providers:
Provider:goerliPublic
Provider:goerliPublic
Provider:goerliTestnet1
Provider:goerliTestnet1
Provider:goerliPublic
Provider:goerliTestnet1

For unclear reasons, when using the airnode-client the Provider in the log metadata is consistently the last one that is defined. For example, goerliPublic3 is the last one defined in chains[0].providers (where I intentionally use broken provider URLs so initialization fails):
[2023-04-03 05:59:03.146] INFO Forking to initialize providers  Coordinator-ID:c42cc52ca74b1794
[2023-04-03 05:59:06.949] ERROR Failed to initialize provider:goerliPublic0  Coordinator-ID:c42cc52ca74b1794, Chain-ID:5, Provider:goerliPublic3
[2023-04-03 05:59:06.950] ERROR Failed to initialize provider:goerliPublic1  Coordinator-ID:c42cc52ca74b1794, Chain-ID:5, Provider:goerliPublic3
[2023-04-03 05:59:06.950] ERROR Failed to initialize provider:goerliPublic2  Coordinator-ID:c42cc52ca74b1794, Chain-ID:5, Provider:goerliPublic3
[2023-04-03 05:59:06.951] ERROR Failed to initialize provider:goerliPublic3  Coordinator-ID:c42cc52ca74b1794, Chain-ID:5, Provider:goerliPublic3
[2023-04-03 05:59:06.954] INFO Forking to initialize providers complete     Coordinator-ID:c42cc52ca74b1794, Chain-ID:5, Provider:goerliPublic3

I presume this is because when running Airnode locally it doesn't really run as multiple processes (as the cloud version). So, when we call logger.addMetadata function to add info about the chain ID and provider, it sets it for one global logger singleton, each call overriding the previous one, resulting in only the last one being used.

That makes sense, which would imply we need to pass provider and chainId for each log.

After more work, I recommend pushing this issue to the Airnode release containing the single lambda Airnode.
As @amarthadan mentions above, log metadata e.g. Chain-ID, Provider, Sponsor-Address, etc. gets overwritten in a single-process environment, which is effectively what we'll have when switching from multiple lambdas to a single lambda. Consequently, our current approach to reporting these metadata will break (like how it is broken now for airnode-client) and require an overhaul to the very large proportion of logs that currently contain metadata. I've updated the issue title to reflect this broader scope.
CC @aTeoke, @Siegrift

This is an issue that needs to be solved when implementing https://github.com/api3dao/airnode/issues/1478


tour: no coding environment is available on the page

Context: /concurrency/7
The page is about an exercise. Meanwhile there's nothing on the left to write the code or run it.

The excercise is too big so it was split into two pages - /concurrency/7 and /concurrency/8
While this is working as intended, this might require some refactoring to make it more obvious.

CC @adg @campoy

Would adding a small clarification at the bottom of the page help?
https://go-review.googlesource.com/#/c/12179/1


Add option to show editor group index for each editor group

When you press ctrl+{n}, where {n} is a number from 1 to 8, the editor group with index {n} will be made active. However, it is not easy to quickly identify the index of an editor group. In other text editors, it is often possible to show the index for each editor group (or equivalent concept), and it would be useful if this was also possible in VSCode.
N.B. I quickly tried to write a hacky extension that uses the proposed editor/content menu contribution point to show a button with a number, but this would require VSCode to add a context key that gives the editor's editor group's index -- activeEditorGroupIndex exists but only shows the index of the active editor group rather than that of the editor's editor group. I would rather put the button in the editor/title menu but that only shows for the active editor rather than all the editors.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


STL codec: should use binary file format

I suggest to use the binary format for STL generation, or make it configurable

We'll need to figure out how to add this option. For formats like gltf you can determine whether a binary or ASCII version is desired based on the file extension, but with STL that is not possible since the same file extension is used for both. Maybe there could be an --encoding command line parameter that accepts binary, ASCII, utf-8 etc, which is then passed through to the codec, which can decide how to use that information.

I would opt for always saving binary STLs in a first step, as in most use cases this is what you would want

Arguments for keeping ASCII as the default, or at least giving the user the option to revert back to ASCII.

Defaulting to binary would change existing behavior and could break existing systems that integrate cq-cli if they upgrade.
When CQ changed from ASCII to binary as the default for STL, it broke some things downstream. Nothing major, but it did cause some confusion.
cq-cli is designed to be used in pipelines for text transformations as well, which would be broken if defaulting to binary without a way to revert to ASCII.


Unable to set StorageQuota

The Latest version of Microsoft.Online.SharePoint.PowerShell version 16.0.19404.12000 will not modify the size of the storageQuota no error is displayed and no changes are applied. We've used version 16.0.7521.0 and all worked fined.

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

ID: 5d1c6b2b-5af6-acce-b7e8-bf784bb0973e
Version Independent ID: 301586d3-ec04-c42d-4681-0bb59443d35c
Content: Set-SPOSite (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
Service: sharepoint-powershell
GitHub Login: @trent-green
Microsoft Alias: trgreen

Do you have Automatic or Manual storage allocation selected on your tenant?

@officedocsbot assign @yogkumgit

We are set to automatic behavior.

@stephane0smith I would assume that is going to override any manual changes you attempt to add.

@tseward  Thank you very much for the contribution and sharing this explanation. @stephane0smith
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

I am not willing to override the automatic behavior we had it working in an early verison 7019. with the automatic behavior set to true. If I am not mistaking setting the value to manual is a tenant default value that we don't want to be working with. Why is it that NO Errors is shown for a command that is not applying the correction to the site storageQuota. This issue has been wrongly closed. has no resolution seems to be proven to me.

There was an unfortunate regression with the previous versions, but that has been now addressed with a new version 19418 - https://www.powershellgallery.com/packages/Microsoft.Online.SharePoint.PowerShell/16.0.19418.12000
We do apologize the inconvenience caused by this. Issue is now luckily resolved.


please update code snippet ==> rm -rf .git  // non-Windows

I have followed the tutorial
and mistakenly copy-pasted this line:
rm -rf .git  // non-Windows
this cmd is actually same as rm -rf  /  which deleted all my localUser files.
please change to rm -rf .git # non-Windows

Fair point. Fix in https://github.com/angular/quickstart/pull/177.


fix: 🐛 add useArgs to handle state in default modal storybook

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we created for it here.


Loading model trained in H2O studio giving us error

We got this error when trying to load our finetuned model form h2o Studio, can you help please? :
python3 generate.py --base_model=/home/kocka/Data/model/model_unnatural-rat --langchain_mode=UserData --score_model=None --use_gpu_id=False --max_seq_len=4096 --share=False --gradio_offline_level=1 --h2ocolors=False --hf_embedding_model=BAAI/bge-large-en-v1.5 --enable-heap-analytics=False --cut_distance=1000000 --prompt_type=llama2 --top_k_docs=-1 --enable_pdf_ocr='on' --langchain_modes="['LLM','UserData','UserData2']" --do_sample=True --max_max_new_tokens=4096 --max_new_tokens=4096 --auth=auth.json    Using Model /home/kocka/data/model/model_unnatural-rat
Starting get_model: /home/kocka/Data/model/model_unnatural-rat
/home/kocka/.local/lib/python3.10/site-packages/transformers/models/auto/configuration_auto.py:1006: FutureWarning: The use_auth_token argument is deprecated and will be removed in v5 of Transformers.
warnings.warn(
Overriding max_seq_len -> 4096
/home/kocka/.local/lib/python3.10/site-packages/transformers/tokenization_utils_base.py:1727: FutureWarning: The use_auth_token argument is deprecated and will be removed in v5 of Transformers.
warnings.warn(
Traceback (most recent call last):
File "/home/kocka/h2ogpt/generate.py", line 16, in
entrypoint_main()
File "/home/kocka/h2ogpt/generate.py", line 12, in entrypoint_main
H2O_Fire(main)
File "/home/kocka/h2ogpt/src/utils.py", line 64, in H2O_Fire
fire.Fire(component=component, command=args)
File "/home/kocka/.local/lib/python3.10/site-packages/fire/core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "/home/kocka/.local/lib/python3.10/site-packages/fire/core.py", line 475, in _Fire
component, remaining_args = _CallAndUpdateTrace(
File "/home/kocka/.local/lib/python3.10/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "/home/kocka/h2ogpt/src/gen.py", line 1203, in main
model0, tokenizer0, device = get_model(reward_type=False,
File "/home/kocka/h2ogpt/src/gen.py", line 1633, in get_model
tokenizer = tokenizer_loader.from_pretrained(tokenizer_base_model, **tokenizer_kwargs)
File "/home/kocka/.local/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 1854, in from_pretrained
return cls._from_pretrained(
File "/home/kocka/.local/lib/python3.10/site-packages/transformers/tokenization_utils_base.py", line 2017, in _from_pretrained
tokenizer = cls(*init_inputs, **init_kwargs)
File "/home/kocka/.local/lib/python3.10/site-packages/transformers/models/llama/tokenization_llama.py", line 156, in init
self.sp_model = self.get_spm_processor()
File "/home/kocka/.local/lib/python3.10/site-packages/transformers/models/llama/tokenization_llama.py", line 169, in get_spm_processor
with open(self.vocab_file, "rb") as f:
TypeError: expected str, bytes or os.PathLike object, not NoneType
Thanks!

@psinger @pascal-pfeiffer Do you have any idea why a model from LLM Studio would have some issue like this?  Seems to be missing the vocab.json file.  Thanks!

Please show full contents of the path in question.

Thanks for reporting @Cansiano.
It seems that we missed to include tokenizer.model in the download zip. You can directly grab it from the LLM Studio experiment output folder and place it in the corresponding folder.
The issue should be fixed with this PR.


swagger api documentation

Document Service APIs.
The writer will use swagger so as to standardize the documentation across services

Is the API already there, from what I can tell from the code its not yet right.

Is the API already there, from what I can tell from the code its not yet right.

yes . some services are not fully ready, but their interfaces are predefined.
however for some services that are near ready, or already done, we can have them documented.

Hello - I’m a pro writer and editor transitioning to technical writing, and I’m looking to build my portfolio -  I could create an OpenAPI spec for you using Swagger - I'd probably have everything I need if you could give me the endpoints and authorization.  Or are you doing 'spec-first'?   I could also write write other docs, including marketing content, Readmes, user-facing content, etc.   Let me know if you'd like to talk.


Modal Drawer with SlideTransition issue

Hi,
I found a bug. When we have Horizontal Slide Transition between Screen A and Screen B and Screen B has Modal Drawer then you see the drawer during the navigation animation.
I will attach video with the issue
Screen_recording_20240116_221018.webm

Can you share a reproducible code for this bug?


Add get_video_id

I took what Carl did in pull #26 and tweaked it a bit so it's better api-wise plus I added tests.
Does this look ok?

Did a quick skim, looks ok to me.  Thanks.
On Mon, Aug 10, 2015 at 2:56 PM, Will Kahn-Greene<EMAIL_ADDRESS>wrote:

I took what Carl did in pull #26
https://github.com/pyvideo/steve/pull/26 and tweaked it a bit so it's
better api-wise plus I added tests.
Does this look ok?
You can view, comment on, or merge this pull request online at:
https://github.com/pyvideo/steve/pull/30
Commit Summary

Add get_video_id

File Changes

M steve/tests/test_utils.py
https://github.com/pyvideo/steve/pull/30/files#diff-0 (38)
M steve/util.py
https://github.com/pyvideo/steve/pull/30/files#diff-1 (28)

Patch Links:

https://github.com/pyvideo/steve/pull/30.patch
https://github.com/pyvideo/steve/pull/30.diff

—
Reply to this email directly or view it on GitHub
https://github.com/pyvideo/steve/pull/30.

--
Carl K

Sweet! I'll land it now. Thank you!


Release 0.3.7 with post-0.3.6 fixes?

Hi!
There seem to be a number of post-0.3.6 commits in Git that never got to PyPI. (The fix I'd need in a release is 12da9667deba432d8917129afab1daa86c20ec84 in particular.) I find these unreleased fixes in Git:

git cherry -v 668d11edbd62052cde1583be1e1d0512c930f16d | tac

0e1d9d5d461530724522d12d592cde9fc68264a9 Add support for Django 1.10
9a6e024e056964c3d860316d5b13b295ed80d379 Drop support for Django 1.3
a76b50ea257dc4aec0ad2610d8d5281ce478565d Updated travis install command.
1b5167054907b94a7c8dda7f95871661bbf285a2 Expanded Python test versions.
469ed83d11d62684e07798781014b4f2dde89b0d Added tox configuration for running tests across multiple Python versiosn. Fixed Python3 support.
acf095b78208edb59b5873662653e12773add3cc Fixed import to support Django>=1.9.
1c84627980c0b77f8f9005fdbcc916ca33d0e4d1 Leadership note.
13cd65e6e47fffe91a34f14b4030b14382de3963 Travis script fix
12da9667deba432d8917129afab1daa86c20ec84 Full Python 2+3 support

Is there a chance to get a new release tagged and uploaded to PyPI?
Thanks in advance!

If someone else has need for a temporary fix: I've put a version with these fixes up to PyPI now. It's named gevent-socketio-hartwork. The related repository can be found at https://github.com/hartwork/gevent-socketio.


LiveData is not reloaded when back is pressed and returned back to app

Reproduce steps:

Open app and browse themes are loaded
Data is loaded from network
Press back button
Open app again

Actual:
Data is presented without loading it from network
Expected:
Data should be loaded from network

Hi @eugeneroz
For that, you need to change the approach of initializing the live data in viewmodel from lazy to var or val,
   var example: () -> LiveData<Result<SampleResponse>> = { repository.sample(createRequest()) }

This logic sucks

use like this
`var liveData: LiveData<Result<List>> ? = null
private var mediatorLiveData: MediatorLiveData<Result<List>> = MediatorLiveData<Result<List>>()
fun refresh(): MediatorLiveData<Result<List<Product>>> {
    Log.d("info_refresh","refresh2")
    if(liveData!=null&&liveData?.hasObservers()!!){
      liveData?.removeObservers(lifecycleOwner!!)
    }
    liveData = repository.products()
    try{
        if(mediatorLiveData.hasObservers()){
            Log.d("info_refresh","removing observers")
            mediatorLiveData?.removeObservers(lifecycleOwner!!)
        }
    }catch (exc : Exception){
        Log.d("info_refresh","exception: "+exc.message)
        exc.printStackTrace()
    }
    mediatorLiveData.addSource(liveData!!, object : Observer<Result<List<Product>>> {
        override fun onChanged(@Nullable recipeListPojos: Result<List<Product>>) {
            mediatorLiveData.setValue(recipeListPojos)
        }
    })
    return mediatorLiveData
}`

in repository add this method
fun products (): LiveData<Result<List<Product>>> {         Log.d("info_refresh","products refresh info")         return resultLiveData(                 databaseQuery = { dao.getProductsLiveData() },                 networkCall = { ProductRemoteDataSource.fetchProductList("",0,20) },                 saveCallResult = { dao.insertAll(it.results!!) })     }

liveData?.removeObservers(lifecycleOwner!!)

How do you get lifecycleOwner inside viewmodel

@vignesh6 you can follow my approach, and let me know in case of any problem


Decompilation issue when converting Game.LedSprite back to blocks

Open Javascript Editor and type:
let item: game.LedSprite = null
input.onButtonPressed(Button.A, () => {
item = game.createSprite(2, 2)
})
This is the same as:

However when converting back to blocks, it fails to convert.

@microsoftsam - assign any issues with Blocks -> TS and TS -> BLocks to @riknoll - thanks.


502 to docker-gitlab w/ docker-compose

Attempting to configure nginx-proxy to handle docker-gitlab
I'm only getting 502's so I've posted the stdout and docker-compose here:
https://gist.github.com/minskmaz/4a741f733cc90ae63aad00220d9e646c
Obviously I'm not doing this right - suggestions welcomed.

Hi, can you post the generated nginx default.conf?
My guess is that VIRTUAL_PORT=10080 should be VIRTUAL_PORT=80, when i checked the docs it sounded like GITLAB_PORT is the "public" port used when generating URLs but the service will still listen to port 80. Give that a try.

Close?


Parquet without Hadoop dependencies

I have been trying for weeks to create a parquet file from avro and write to S3 in Java.  This has been incredibly frustrating and odd as Spark can do it easily (I'm told).
I have assembled the correct jars through luck and diligence, but now I find out that I have to have hadoop installed on my machine. I am currently developing in Windows and it seems a dll and exe can fix that up but am wondering about Linus as the code will eventually run in Fargate on AWS.
Why do I need external dependencies and not pure java?
The thing really is how utterly complex all this is.  I would like to create an avro file and convert it to Parquet and write it to S3, but I am trapped in "ParquetWriter" hell!
Why can't I get a normal OutputStream and write it wherever I want?
I have scoured the web for examples and there are a few but we really need some documentation on this stuff.  I understand that there may be reasons for all this but I can't find them on the web anywhere.  Any help?  Can't we get the "SimpleParquet" jar that does this:

ParquetWriter writer = AvroParquetWriter.<GenericData.Record>builder(outputStream)
.withSchema(avroSchema)
.withConf(conf)
.withCompressionCodec(CompressionCodecName.SNAPPY)
.withWriteMode(Mode.OVERWRITE)//probably not good for prod. (overwrites files).
.build();

Environment: Amazon Fargate (linux), Windows development box.
We are writing Parquet to be read by the Snowflake and Athena databases.
Reporter: mark juchems
Assignee: Atour Mousavi Gourabi / @amousavigourabi
Related issues:

Avoid Hadoop interfaces and classes in codecs (relates to)
Add interface layer between Parquet and Hadoop Configuration (relates to)
Use SeekableByteChannel instead of OutputFile/InputFile Classes (is related to)

PRs and other links:

GitHub Pull Request #1111
Dev Mailing List Discussion

Note: This issue was originally created as PARQUET-1822. Please see the migration documentation for further details.

Ben Watson:
I also had this problem and I hope I can help you. I maintain an IntelliJ plugin that lets people view Avro and Parquet files. I assumed that creating this plugin would be a trivially easy task, but I've been surprised at just how much effort it is and how many bugs people still keep finding.
I asked about this on Stack Overflow a while ago and got an answer that works. The solution I implemented does have some Hadoop dependencies, but the critical difference is that it uses org.apache.parquet.io.InputFile and does not require org.apache.hadoop.Path. This skips a lot of Hadoop libraries and helped me to avoid a lot of JAR Hell issues. This works on Windows without any additional setup or PATH changes.
Feel free to copy the relevant code from my repo:

https://github.com/benwatson528/intellij-avro-parquet-plugin/blob/master/src/main/java/uk/co/hadoopathome/intellij/viewer/fileformat/ParquetFileReader.java

https://github.com/benwatson528/intellij-avro-parquet-plugin/blob/master/src/main/java/uk/co/hadoopathome/intellij/viewer/fileformat/LocalInputFile.java
Disclaimer: this does not produce valid JSON if Logical Types are used as the date strings are not surrounded by quotes (see this open SO question).

David Mollitor / @belugabehr:
Parquet 2.0 anyone?

Gabor Szadovszky / @gszadovszky:
@belugabehr, based on the current community activity I wouldn't say parquet 2.0 is feasible any time soon. :(

Xinyu Zeng / @XinyuZeng:
Hi community, just wondering whether there is any update to this issue?

Johannes Müller:
We're having the exact same issue. We would like to write to parquet for the convenience and the obvious benefits of the format but it just seems impossible to do without a lot of overhead, including a Hadoop installed?

mark juchems:
Ben,
Thanks for you work on this!  We use your plugin all the time.  It is quite indespensible.
All,
Keep in mind that, at least for us, no haddop install was needed in Fargate on AWS.  So we just used these jars and it worked.  We of course used the AWS jar to write to S3.  We wanted an output stream but couldn't overcome that.

11
3.2.1

org.apache.avro
avro
1.9.2

org.apache.parquet
parquet-avro
1.11.0

org.apache.hadoop
hadoop-common
${hadoop.version}

org.apache.hadoop
hadoop-client
${hadoop.version}

org.apache.hadoop
hadoop-aws
${hadoop.version}

Here is our code:
/**

This saves it to the "parquet" folder at the base of this project.
*/
public void saveIt(List<Map<String, Object>> theData, String fileName) throws Exception {
Schema avroSchema = AvroSchemaBuilder.build("pojo", theData.get(0));
System.out.println(avroSchema);

Configuration conf = new Configuration();
Path path = new Path("parquet/" + StringUtils.substringBeforeLast(fileName, ".") + ".parquet");
ParquetWriter writer = AvroParquetWriter.<GenericData.Record>builder(path)
.withSchema(avroSchema)
.withConf(conf)
.withCompressionCodec(CompressionCodecName.SNAPPY)
.withWriteMode(Mode.OVERWRITE)//probably not good for prod. (overwrites files).
.build();
for (Map<String, Object> row : theData) {
StopWatch stopWatch = StopWatch.createStarted();
final GenericRecord record = new GenericData.Record(avroSchema);
row.forEach((k, v) -> {
record.put(k, v);
});
writer.write(record);
}
writer.close();
}

Gang Wu / @wgtmac:
@amousavigourabi Is this issue complete? Should we resolve it?

Ryan Rupp / @ryanrupp:
@wgtmac thanks, do you have any sample code by any chance? If I use hadoop-client-api as a dependency I can get further along (compiles etc.) but it does then result in an exception downstream when trying to go from ParquetConfiguration -> Configuration (Hadoop). It looks like because hadoop-client-api does some shading but it's failing to classload a woodstox class that it's expecting to be shaded but isn't:

java.lang.NoClassDefFoundError: org/apache/hadoop/shaded/com/ctc/wstx/io/InputBootstrapper
 at org.apache.parquet.hadoop.util.ConfigurationUtil.createHadoopConfiguration(ConfigurationUtil.java:60)
 at org.apache.parquet.hadoop.ParquetWriter$Builder.build(ParquetWriter.java:929)
 // test code
Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.shaded.com.ctc.wstx.io.InputBootstrapper
 at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
 ... 74 more

I'm guessing because this dependency is really just meant for API users and at runtime the "hadoop-client" with all relevant transitive dependencies would be in place? I'm actually not familiar when you would use hadoop-client-api vs hadoop-client.

Gang Wu / @wgtmac:
Hi @ryanrupp, I tried to reproduce the issue and can confirm that I have to add hadoop-client-api as the minimal dependency of hadoop: Maven Repository: org.apache.hadoop » hadoop-client-api (mvnrepository.com). Otherwise, my compiler complained about missing hadoop-related class file.

Ryan Rupp / @ryanrupp:
Is 1.14.0 to the point that parquet can be used without hadoop-client dependency? I was playing around with it and observed:

The compiler complains about the new method overloads for builder and withConf - even though I'm using the new Parquet interface overloads, the compiler will complain about the hadoop classes not being available. I can "trick" this though by adding hadoop as a provided scope dependency. This is on Java 11 FWIW.

Once past that, ParquetWriter if you're not using encryption the null code path goes down into path that hits Hadoop classes (I temporarily worked around by just removing the encryption settings as I don't use them in this case)

After that I hit I believe I hit PARQUET-2353 but didn't dig into it too far
There's some comments on the PR like this that sound like people are doing this to an extent, maybe dependency on hadoop-common (instead of hadoop-client) or does anyone have an example of minimal hadoop dependencies being pulled in? The tests like TestReadWrite already have Hadoop on the classpath for instance.
Thanks

Gang Wu / @wgtmac:
I marked this as resolved for 1.14.0 release. Feel free to reopen if this issue is considered incomplete.


[Docker] Add Docker support

Hello !
First, I wanted to thank you for this project, it's really awesome ! I am working on learning RUST and apply it to WASM and this project is awesome I I would be happy to start to contribute to it in the next future :)
My first humble contribution if you are okay with it will be to add Docker support to easily be able to deploy it (I am using Kubernetes).
I will push a PR to add this support, please let me know what you think ! :)
Cheers !

Hey @mtharrison, I was wondering if you had time to look at this one and if it makes sense to you?
Thanks :)

https://github.com/mtharrison/wasmbooth/pull/3


DETR config does not have auto_scale_lr.enable

I am trying to train DETR but if auto_scale_lr=True then I get the error:
RuntimeError('Can not find "auto_scale_lr" or '
                               '"auto_scale_lr.enable" or '
                               '"auto_scale_lr.base_batch_size" in your'
                               ' configuration file.')

cause raise here in tools/train.py
Is auto_scale_lr.enable missing from the config because auto-scaling the lr is not supported by DETR, or should the check for auto_scale_lr.enable be removed, or should it be added to the config, and other configs as needed.
Reproduction
Train with the detr_r50_8xb2-150e_coco.py config and with --auto-scale-lr set

I tried to add it to the config: auto_scale_lr = dict(enable=False, base_batch_size=32), and it finally worked.


Bad error message for type used as index

TypeScript Version: 3.1.0-dev.20180717
Code
type S = "a" | "b";
type O = { [S]: number };

Expected behavior:
Error message telling me to use K in S.
Actual behavior:
src/a.ts:2:13 - error TS2693: 'S' only refers to a type, but is being used as a value here.

@mhegazy @andy-ms @DanielRosenwasser which message will be acceptable to this case?

I'm thinking something like:
'S' is a type, not a symbol. To use 'S' as a key type of a mapped type, use K in S.
(Note that with const S = Symbol(); the code would compile as-is.)
Note that a mapped type will only work here if the type does not have any other properties; see #24286.
We could also add a codefix triggered by this diagnostic.


Please add support for the Team City Tray (and other tools)

Clicking the Log in using Azure Active Directory link doesn't appear to work.

Thanks

What other tools do you mean?

https://confluence.jetbrains.com/display/TCD9/Installing+Tools

Are there any plans for supporting the Tray Notifier? Thanks

I am also having a problem with the Windows Tray Notifier - I click the 'Log in using Azure Active Directory' but nothing happens

Log in using Azure Active Directory is not working for me either. (Version 10.0.1 (build 42078)

Hi, this issue has been open since 2015 but my team is unable to use the tray notifier without setting up alternate credentials (our Ops team is unwilling to do this as we're pushing heavily for everything to use AAD integration).
Are there any plans for fixing this, or should we look to alternative solutions?

(Note; we are now using Azure DevOps)

Just found this after getting a question from a user.  Can we get confirmation about the status of Azure AD support from the Tray Notifier?


Should np.sh default to using -s and -i flags?

Is your feature request related to a problem? Please describe.
An install of sshnp into a fresh environment is likely to fail unless keys have already been put in place
Describe the solution you'd like
Use the -s and -i flags in np.sh to ensure that keys on the client machine are transported to the target device.
Describe alternatives you've considered
These could be the default for sshnp itself, but I'm not persuaded that it's a secure default.
Additional context
Do we expect our users to know their way around ssh key management?

Now that npt is available, I'm even more inclined to say we shouldn't. I think the bar for entry is at least "knows / needs to know how to use ssh", otherwise why aren't they using npt.
Thus, I think -s and -i should not do these automatically, since the default behavior would then be the opposite of what people expect ssh to do.

Also, SSH No Ports Desktop we require that the user uploads a public key, since we can't pull from the .ssh directory due to app sandboxing. I think it might be reasonable here to have -s turned on by default.

Moving back to Triage so we can decide what to do next.

Don't expect to get to this in PR90, so bumping to PR91

On further reflection I'm inclined towards not having this as a default, particularly as -i would need to be pointed at the right key.


ContractCallQuery() inconsistently requires using .setQueryPayment() when function returns a string

Description
Using v2.13.1 of the JS SDK.
The zip attached includes the bytecode, the sol, and the js files needed to reproduce the issue.
Lines 107 and 117 show that  .setQueryPayment() has to be used in the ContractCallQuery() module,
even if the query payment is set to the default max payment amount (which should have worked in the first place without specifying a query payment amount).
Note that setting a query payment is not required for other types like numbers and addresses.
For clarity, the issue I'm reporting is that setting the query payment is only required for return values of type strings 1 HBAR is the default max payment amount, which means that the ContractCallQuery() should've worked without having to specify the query payment. I looks like the SDK is requiring specification of any amount (as long as it's greater that the actual payment needed)
Steps to reproduce

open the zip attached
run 5_1_HIP218_FungibleTok.js with and without commenting lines 107 and 117,
observe the error or INSUFFICIENT_TX_PAYMENT

Additional context
5_1_HIP218_FungibleTok_sol_ERC20Contract.zip
Hedera network
testnet
Version
v.0.25
Operating system
Windows

I was slightly aware of this issue (I thought it applied to ContractCallQuery as a whole rather than only when it returns certain responses), but it isn't an SDK issue. The reason I say this is because we query the cost of the query and use the resulting cost as the payment for the actual query if it's less than maxQueryPayment otherwise we use maxQueryPayment. The fact you're getting INSUFFICIENT_TX_PAYMENT despite us using the result of the CostQuery means the cost returned to us is incorrect when it should be correct as it is for all the other queries. I think this may be a bug within https://github.com/hashgraph/hedera-services

Thanks for the response. I opened this issue in the hedera services repo: https://github.com/hashgraph/hedera-services/issues/3288

Closing the issue here. If we end up determining we need to do extra work in the SDK we can reopen.


Boxplots widths too narrow if x == by

library(tinyplot)

tinyplot(
  Petal.Length ~ Species, iris,
  type = "boxplot"
)

tinyplot(
  Petal.Length ~ Species | Species, iris,
  type = "boxplot",
  legend = list("topleft", bty = "o")
)

The bottom boxplots should be the same width as the top ones. But they're too narrow.
I think I know why this is happening (related to a factor coercion) and should hopefully be a simple fix.

Oops, turning off the legend triggers a resizing error of its own.
tinyplot(
  Petal.Length ~ Species | Species, iris,
  type = "boxplot",
  legend = FALSE
)

This is a separate bug, but I'll try to address at the same time.

Note also that you try to detect x == by only based on their levels which is not general enough. As a simple example, consider a coordination game of two players, where you want to know whether the outcome of the experiment depends on the combination of the gender of player1 and player2. To visualize the boxplots of the four groups you can use outcome ~ player1 | player2. Thus x != by but levels(x) == levels(by).
When legend = FALSE this case is handled correctly but by default it is not:
d <- data.frame(
  outcome = sin(1:40 - 3),
  player1 = factor(rep(c("female", "male"), each = 20)),
  player2 = factor(rep(rep(c("female", "male"), each = 10), 2))
)
tinyplot(outcome ~ player1 | player2, data = d)
tinyplot(outcome ~ player1 | player2, data = d, legend = FALSE)

Good catch.
Hmmm. I'll probably have to move this logic higher up in the code and do something like x_by = identical(x, by).

Oh, and playing around with this some more: We currently cannot set any of the boxplot.default arguments, can we? For example, range, varwidth, width, notch, etc. seem to be ignored at the moment.
iris2 <- iris[c(1:30, 61:100, 101:150), ]
plot(Petal.Length ~ Species, data = iris2, varwidth = TRUE, range = 0.5, notch = TRUE)
tinyplot(Petal.Length ~ Species, data = iris2, varwidth = TRUE, range = 0.5, notch = TRUE)

But maybe this should be a separate issue?

Oh, and playing around with this some more: We currently cannot set any of the boxplot.default arguments, can we? For example, range, varwidth, width, notch, etc. seem to be ignored at the moment.

It's a bit hidden, but boxwex, staplewex, and outwex at least are supported through .... In this case, adjusting  boxwex would have had a similar effect.
tinyplot(Petal.Length ~ Species, data = iris2, boxwex = .75)

I didn't include support for notch because I personally don't like it (see also the warnings about weird behaviour in ?boxplot) But varwidth and range are oversights; I'll add those. (I can add notch too if you would like to advocate for it.)

I don't like notch either but I would still support it for compatibility with boxplot. And then maybe outline could be supported as well (even though I have never used it myself)?

Cool. I'll also add support for boxwidth as more direct argument alias that gets passed down to boxplot(..., width = boxwidth) internally (and so doesn't create a clash with our primary tinyplot(..., width) argument).


[build-script] Add a default-enabled "clean" step for swift-driver and swiftpm products

Along with options to disable the mandatory clean using: --skip-clean-swift-driver and --skip-clean-swiftpm.
This change will ensure that every invocation of build-script will, by default, clean up all build artifacts of these projects and re-build them from scratch.
This is needed for all builds because today arbitrary changes to the compiler can lead to being unable to incrementally build components that are themselves written in Swift (e.g. SwiftPM and swift-driver). This causes now-frequent failures in incremental build bots, and is a scenario that is encountered by developers (For example, see: rdar://65006593).
The proper long-term solution is to enable library evolution for these projects.
Until this is done, the only safe thing to do is to always rebuild them.
Resolves rdar://65006593

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - fc4ef192ae875d979365513a03c9f8312f9ba75e

@swift-ci please test

@swift-ci please smoke test

Build failed
Swift Test Linux Platform
Git Sha - fc4ef192ae875d979365513a03c9f8312f9ba75e

Build failed
Swift Test OS X Platform
Git Sha - fc4ef192ae875d979365513a03c9f8312f9ba75e

Are there any other products that should have this set? I imagine it is anything that uses a notion of a shared workspace. I have seen this same error before btw and it was on my list of things to fix. Thanks for taking the initiative here!

I imagine so. So far these are the only two projects that have caused a problem. I will look over the other products to see if they could potentially run into this.


HIVE-25793 Isolate metastore metrics related to a retrying handler

What changes were proposed in this pull request?

This change will make new metrics for a metastore retrying proxy handler.
Why are the changes needed?

We can see that metastore api count increments twice for one RPC. A metastore server makes two timers with same name for one RPC. one for retrying proxy handler and another for hms handler.  It will make api metrics more inaccurate, Especially during retrying.
Does this PR introduce any user-facing change?

This change will make new metrics for a metastore retrying proxy handler.
How was this patch tested?

A test was added

The #2441 also wants to solve the problem, but brings some backwards compatible problem. I am not sure it appropriate to introduces some more metrics about the apis.
Thanks,
Zhihua Deng

@dengzhhu653
I didn't know you are working on the same issue. thanks for sharing.

I am not sure if it appropriate to introduce more metrics about the apis.

I thought we may easily recognize retrying cases by comparing two api metrics, whether apis succeeds or not.
This approach doesn't break anything. It gives us more accurate metrics, and users can pick metrics which they wants to collect, if they don't want both.

I am not sure if it appropriate to introduce more metrics about the apis.

I thought we may easily recognize retrying cases by comparing two api metrics, whether apis succeeds or not. This approach doesn't break anything. It gives us more accurate metrics, and users can pick metrics which they want to collect, if they don't want both.

On a long running metastore instance, the two different metrics may be almost the same,  it may bring some ambiguities and memory pressure. Just my thought, Thank you!

It seems you are still working on #2441. I hope your work will be merged soon. Thanks! @dengzhhu653


remove the respository OTP publish token for NPM

This change is the final step to allow the publish action (completed in PR #22) to work.
From Chris Capell:

It appears that there is a repository-level secret for the NPM_TOKEN. This is overriding the Org token.
...Option 2 is to just delete the repository level token and use the Bitovi org token

Notes
https://docs.npmjs.com/configuring-two-factor-authentication#disabling-2fa-for-writes

The repository token has been deleted.


testing

Why:
Closes [issue link]
What's being changed:

Check off the following:

[ ] For workflow changes, I have verified the Actions workflows function as expected.
[ ] For content changes, I have reviewed the style guide.

Why:
Closes [issue link]
What's being changed:

Check off the following:

[ ] For workflow changes, I have verified the Actions workflows function as expected.
[ ] For content changes, I have reviewed the style guide.


BUG: Fixed ctkVTKDataSetArrayComboBox crashing and not updating

ctkVTKDataSetArrayComboBox caused application crash when it is used for a VTK data set that is generated by a pipeline and the combobox was used for setting active scalar.

When a data set is changed due to a pipeline change, the data set is first reset and then recomputed. During reset the scalars are removed therefore the selection in the combobox is changed to item (-1), which triggers a data update. During update all the scalars are removed (again, so there is no change) but then the scalars are re-added when the data is recomputed. Qt combobox automatically selects the first item if an item is added, therefore the selection changes to the first active scalar. This change triggers a data set update, which starts with a reset. During reste the scalars are removed, therefore the selection in the combobox is changed to item (-1), which triggers a data update... This is an infinite loop, which causes application crash due to stack overflow.
Solution was to add a NULL item (no active scalar). This is also useful because without a NULL item it is not possible to unselect scalars.
For backward compatibility reasons, by default NULL item is not added (it is not needed if the combobox is not used for setting the active scalar).

ctkVTKDataSetArrayComboBox did not contain any arrays that were added after the data set and attribute types are added.

vtkDataSet Modified event is not invoked if arrays are added/removed/renamed, only vtkDataSet.PointData and vtkDataset.CellData object Modified events are invoked. ctkVTKDataSetModel did not observe the point and cell data objects.
Solution was to add observers to the point and cell data objects.

All sounds like good fixes.
@jcfr is traveling so maybe @finetjul wants to have a look also.
I would be fine merging this unless there's an objection.

Looks fine to me too.


img tag attributes 'width, height' rendering with 0 value when 'null, undefined' specified

Version
3.0.3
Reproduction link
https://codesandbox.io/s/long-pond-gbdnl?file=/src/App.vue
Steps to reproduce
Insert an image via the img tag and specify width or height as null or undefined.
<img :width="null" :height="null" src="./assets/logo.png" />
<img :width="undefined" :height="undefined" src="./assets/logo.png" />

What is expected?
Attributes width and height have not been rendered according with the Vue 3 documentation - https://v3.vuejs.org/guide/template-syntax.html#attributes
What is actually happening?
Attributes width and height have been rendered with 0 value.

The attribute should be removed with nullish values. This would also make it consistent with Vue 2


Update docs/UsingPyRuntime.md to catch up PR #2629 (Support string type inputs from Python application code).

Update docs/UsingPyRuntime.md to catch up PR #2629 (Support string type inputs from Python application code).
Only document is updated.

Jenkins Linux ppc64le Build #13103 [push] Update docs/UsingPyRunti... started at 00:04

Jenkins Linux s390x Build #14106 [push] Update docs/UsingPyRunti... started at 23:54

Jenkins Linux amd64 Build #14079 [push] Update docs/UsingPyRunti... started at 22:54

Jenkins Linux s390x Build #14106 [push] Update docs/UsingPyRunti... passed after 1 hr 12 min

Jenkins Linux amd64 Build #14079 [push] Update docs/UsingPyRunti... failed after 1 hr 37 min

Jenkins Linux ppc64le Build #13103 [push] Update docs/UsingPyRunti... passed after 1 hr 54 min


Folded line is not collapsed to a single line

The above is folded into:

Notice the blank line in the  tag.

Hey
This explains the issue.
https://github.com/moalamri/vscode-inline-fold/discussions/69#discussioncomment-4150206

Thanks @moalamri !


Mining is broken

Whenever you mine, you get that the block hash is incorrect. I have done git pull and restarted all my miners to see if I had outdated code, however that didn't work.
Mining to this address: 2zRNlDy4PFHZe7TQAEwX7BbnN7DGC0QQKdVlCP5k+DM=
Approx hashrate: 72288.83. Have checked 131072 hashes.
Approx hashrate: 71045.51. Have checked 262144 hashes.
Approx hashrate: 66310.32. Have checked 393216 hashes.
Approx hashrate: 66062.97. Have checked 524288 hashes.
Approx hashrate: 66497.15. Have checked 655360 hashes.

Block made! It took 11.55s
{
   "Index": 189494,
   "Timestamp":<PHONE_NUMBER>419704,
   "Data": "Mined by the official Duckcoin CLI User: ",
   "Hash": "00000ffbe34bff75d98b142401df5b2011a4a5a2de06ed013052a47d09df4391",
   "PrevHash": "00000eaf24732c71e5ce05da3e6755813570205e8e1b2236f70512e6666e3c15",
   "Solution": "758738",
   "Solver": "2zRNlDy4PFHZe7TQAEwX7BbnN7DGC0QQKdVlCP5k+DM=",
   "Tx": {
      "Data": "",
      "Sender": "",
      "Receiver": "",
      "Amount": 0,
      "PubKey": "",
      "Signature": ""
   }
}
Sent block to server
Server returned "Invalid block. Block Hash is incorrect. This usually happens if your Difficulty is set incorrectly. Restart your miner."

I need to mine to become the richest quack holder :sob:
I have looked at the code to see if I could spot the issue, but haven't been able to so far. Will update you if I find anything.

Hm. I'll look at this!

helloooo

Ok, @TommyPujol06 are you running the latest the latest version of the client? You might have to rebuild the binary.

@quackduck pls review my pr

Send a sha256 hash of the binary (specify OS) so I can check whether it’s the latest.

Ok, @TommyPujol06 are you running the latest the latest version of the client? You might have to rebuild the binary.

Yes, I am running the latest version. Re-building worked. I can mine again now. Must have forgotten to rebuild after fetching the new code.

Glad it worked out

perfect!


Chromecast component does not detect media pausing

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.62.1
Python release (python3 --version):
Hassio
Component/platform:
Hassio / RPi3
Description of problem:
Chromecast component detects new media being started or stopped, but when using an external control to pause the media, the Chromecast component in Home Assistant does not detect the media being paused.
When using the controls in the Home Assistant web interface, the play/pause is correctly shown (also in the event list in the HA web interface).
Expected:
Pausing/resuming Netflix on my phone should be detected in Home Assistant.
Problem-relevant configuration.yaml entries and steps to reproduce:

Auto-detect Chromecast
Start playing something
Pause using your phone and observe that HomeAssistant never detects that the stream is paused

Additional info:

For me, this works correctly using a Chromecast and Google Home Mini with Netflix and the news feature, respectively. :/

Is it perhaps a firmware version thing?
My Chromecast has 1.29.104827; what version is yours running?

Google Home Mini: 1.30.111204
Chromecast: 1.29.104827

I can confirm that I'm having the OP's problem with Netflix casting. If I use the Netflix app on my phone to cast to the TV, and then either stop or pause from my phone, HA continues to detect Netflix as playing (under State). If I pause using the pause button in HA, HA correctly updates the state.
This behaviour does not occur if I cast Youtube or Google Play Music. Have not tested other casts yet.
Chromecast Version 1.30.109591
HA 0.61.1 (running via Ubuntu Server Python VENV)

Updated the ticket to reflect that this seems to focus on Netflix; Youtube also worked for me.

I randomly happened to test this last night, but I can not reproduce the bug. As far as I could tell it is working just fine for me: when I hit pauze/play on my TV remote (controlling Netflix on the Chromecast via CEC), the center button in the media player switches between play/pauze as expected.
Home Assistant 0.63.1 with Python 3.6.3
Chromecast with firmware 1.30.109591

So it's clear that the Chromecast shows different attributes depending on the app being shown.
My CC (described above) receiving Youtube (which I agree works fine and detects status correctly):

app_id: 233637DE
media_content_id: vcebekI9F7g
entity_picture: /api/media_player_proxy/media_player.media_room_tv?token=2b6061ec3beafa750a09a3a795abc65dbe1a45a4dfa9d906d61440431f4469e5&cache=71f0850f147993d9
media_position_updated_at: 2018-02-13T12:20:58.284064+00:00
volume_level: 1
media_title: Games Should Not Cost $60 Anymore (The Jimquisition)
supported_features: 21437
is_volume_muted: false
media_duration: 1368.261
app_name: YouTube
media_position: 9.009
friendly_name: Media Room TV

And my CC receiving Netflix

media_duration: 5206
supported_features: 21437
is_volume_muted: false
media_content_id: http://www.netflix.com
app_id: CA5E8412
media_position_updated_at: 2018-02-13T12:22:56.883779+00:00
app_name: Netflix
media_position: 5.267
friendly_name: Media Room TV
volume_level: 1

I wonder if this is an issue with pychromecast.
@fanaticDavid: Try to control Netflix using your phone rather than CEC to replicate. CEC must work around the problem (I'm guessing pychromecast specifically receives those signals?)

I can now confirm this issue - however, as far as I can see, the problem is on Netflix' side and we can't really do anything about it. All cast apps are supposed to send MediaStatus messages to send their current state. Netflix however doesn't send playerState: PAUSED when pausing through a mobile device - it always sends playerState: PLAYING even when nothing is playing.
https://github.com/balloob/pychromecast/blob/master/pychromecast/controllers/media.py#L224
Potentially creating a special Netflix controller could work around this - though their API is probably quite obscure and hard to reverse engineer. To keep the issue tracker clean, I believe this issue should therefore be closed.
@databoy2k There's no such thing as encrypted messages in the open cast API protocol. I believe @szczys was referring to protobuf messages, which look like a bunch of encrypted data in plaintext even though it's just a very sophisticated data structure + compression format.

Thanks for clarifying. Hopefully Netflix will update their end of it and we'll be able to use these functions.

Closing due to this not being because of Home Assistant.


JTACMonthView's calendarDelegate and calendarDataSource should be weak

JTAppleCalendar version ~8.0.1~ 8.0.0
Description
To avoid retain cycles, the JTACMonthView's calendarDelegate and calendarDataSource should be marked as weak, and the respective protocols should extend AnyObject to allow this.
Otherwise, anyone not using a dedicated instance as the dataSource/delegate will have to take extra care not to create a retain cycle. Since a common Cocoa pattern is for the parent view to also be the dataSource/delegate, this can become an easy mistake to make.
Steps To Reproduce

Add a JTACMonthView to a UIView, and set this UIView as the calendarDataSource and/or calendarDelegate of the JTACMonthView.

A retain cycle is created

Expected Behavior

No retain cycle is created

Yes, I have made them weak in version 8.0.1
are you still seeing them as strong?

Hi @patchthecode 🤝
Sorry, my bad 😅, I thought I had 8.0.1 since I had updated very recently. It's good to know you've fixed that on the latest version.
However, I've just tried to do a pod update, and I'm still getting 8.0.0. It appears you haven't pushed it yet to CocoaPods master repo, right?
Please let me know once you have done so.
Cheers! 🍻

ok i guess you're one of the developers who updated to 8.0.0 with cocoapods before i corrected the issue.
I have removed 8.0.0 from cocoapods because I do not want to support cocoapods from 8.0.0 and upwards. This is because Xcode 11 + now comes builtin with Swift Package Manager.
I want everyone using this lib version 8.0.0 and up to to start using SPM instead of cocoapods. SPM makes cocoapods obsolete.

Well, that was unexpected 😓
Xcode 11 is still in beta, and even though I agree that SPM is the future, many apps that are in production today still don't use it because it's beta, and may take a while to migrate because it's not trivial in some cases, and in others is not even possible because SPM still doesn't support things like additional resources bundled with the packages (i.e. it's just code for now) which some projects/frameworks depend on.
We are using your framework in production and integrate via CocoaPods, and I think other projects will be under the similar scenarios. Since you're the code owner you obviously have the decision power here, but I honestly think that you are leaving out some users of your framework because it seems a bit soon to me to force this on your users.
Anyway, we'll work around this issue some other way...

Sorry if i sound like i am making a definitive conclusion.
I am very open to hear the thoughts of every one on this.
Xcode 11 will be out of beta around ~ September or so.
My thoughts on the removal of Pods were this:

Version 8.0 has a new feature (yearView mode) which I am still working out the kinks on.
Version 7.1.7 is very stable.
So my thoughts were to get version 8.0+ up to speed so that it will be mature by Xcode 11 public release date.

Now as to why i am dropping cocoa pod support.
I was considering removing it because I do not have an answer to this question
--> Why continue to support cocopod for this library, when developers can use SPM that comes built-in into Xcode 11?
A developer can have in his Xcode 11 project (for example)

Alamofire/Afnetworking cocoaPod
Kingfisher cocoapod
JTAppleCalendar SPM

They work well together within the same project. And SPM has all the advantages of cocoapods and Carthage combined. The only people that will be affected by this will be developers who want to go to 8.0+ but refuse to update to Xcode 11.
What are you thoughts?

My thoughts is that even though SPM is the way forward, I don't think the best approach is to "force" adoption of it by deprecating the support of still-industry-standard Carthage and CocoaPods for the new version of your framework.
I know that you can have N dependency managers at the same time (even though I think that can be messy), but why force one onto your users? That's where I'm getting at.
As for your question:

Why continue to support cocopod for this library, when developers can use SPM that comes built-in into Xcode 11?

A possible answer is that making these kind of migrations in some projects is sometimes not an easy undertaking, and there's quite some risk to it. Not all projects can or want to jump to the shiny new stuff as soon as it becomes available. And you're not even waiting for these shiny things to leave beta before deprecating currently used and battle tested tools. Isn't 8.0+ a stable release? Then why only allow its integration via a beta package manager and tooling?
Since I don't need any new feature from 8.0+, I think I'll simply downgrade and lock the version as I updated your pod because I saw there was a new version and upgraded it as a part of regular project maintenance.

Your points are valid.
Cocoapods/carthage will be re-implemented.
In the mean time stay on version 7.1.7
My understanding was that major version changes like 7 to 8 meant breaking changes. I thought it would be ok to get away with the deprecation under these breaking changes. But now I am re-considering.
Will get back to this once i get some free time this week.
Setting the upgrade flag.

Ive decided to main 2 versions.
I've just released version 7.1.8 which contains all of the fixes of version 8.0
reason? I am not good at configuring cocoapods.
Ive taken much time to try and re-implement cocoapods and SPM in the same repository. I could not get the cocoapods configured properly. If someone can help with that it would be appreciated.
So i've opted for the next best thing. I'll maintain Version 7 and version 8.
New features will go into version 8, but i'll continue to do bug fixes on version 7.
I think this is a good middle ground for me given my time constraints.

Ok. As stated in wiki, this will be done once Xcode 11 fully released.
It has been release.
So Cocoapods has been re-implemented.
Latest version = 8.0.2
Closing this issue


Swift 4.0 Support.

Upgraded all the things to Swift 4.0, not more than that.

You're welcome, it's fixed 👍

@DagAgren @DmitryBespalov I've checked the changes and I think they're fine. I we merge this branch and therefore migrate SwiftMonkey to Swift 4 we'll have to make sure that the next release of both Monkey and MonkeyPaws does not break any existing Swift 3 code.
To ensure this I would suggest to release both libraries with a major version bump. This will indicate the breaking changes and hopefully will prevent people from automatically updating SwiftMonkey to this source-incompatible version.

I will merge this PR regardless of the suggested changes (consulted this with @DmitryBespalov). The mentioned code comments will be addressed in a separate PR.


Adding packages, moving ast-tools to its package

Packages will be published along with the CLI, in their different npm packages.
The goal is to streamline the dependencies so they become smaller, and each package can be used without using the cli.

Please note that before the next release, we will have to make a new package.json for the CLI itself.


Get current year automaticly

For the moment I have
defaultYear :: Text
defaultYear = "2017"

I guess it's not a good idea to change defaultYear manually on Jan, 1 each year instead of having the party :champagne:
So the plan is to use time package to get current year on fly.

Implemented in PR #25


Revert " [CastOptimizer] Set the correct debug scope for the SILBuilder. "

Reverts apple/swift#25490
Failed in CI: https://ci.swift.org/job/oss-swift_tools-RA_stdlib-DA_test-simulator/687/

@swift-ci please smoke test


fix ingress SDS not getting secret updates issue

fix issue: https://github.com/istio/istio/issues/23715
high level context:
basic network variable:

sdsclients map : store all the current connection network with a  key (connection id + resource name)

cache.secrets map: store all the secrets with the same key connection id as sdsclients

when the gateway and secret are deleted, the sdsservice will detect that and build a new connection with id (connection.local-5) trying to reconnect. The secrets and connections are stored in the cache.secrets and sdsclients seperately.

when the user recreated the gateway, the sdsservice detects that and close the former connection(connection.local-5, remove this connection from the sdsclients), but somewhat the secrets are not removed from the cache.secrets

when the secret are created, the sdsservice use the not deleted connection-id to fetch connection from the sdsclients, which causes error in NotifyProxy which sends notification to proxy about secret update

The root cause : https://github.com/istio/istio/blob/master/security/pkg/nodeagent/sds/sdsservice.go#L482
There is a cache id problem when gateway are deleted and recreated: The old connection cache id are not clean up when the gateway are deleted
we need to delete the secret from the cache
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @williamaronli. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Thanks for working on this. Please add unit tests in sdsservice_test.go to cover the connection and cache cleanup flow.

We should also revisit this process and figure out whether this is needed.
https://github.com/istio/istio/blob/65bd2ac632cbd6ec8e3fd85bb9874f685aea0cfd/security/pkg/nodeagent/cache/secretcache.go#L621
What if cache is deleted but connection is still alive, and Envoy is waiting for secret, it looks like in that case SDS push never happens and SDS flow hangs on that connection.

@williamaronli: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test lint_istio

gencheck_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test lint_istio

gencheck_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test gencheck_istio

unit-tests_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Close this one and create another CR(https://github.com/istio/istio/pull/24817) here because of there are lots of commit on master branch since this CR are created

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test gencheck_istio

unit-tests_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test unit-tests_istio

lint_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test unit-tests_istio

lint_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test lint_istio

gencheck_istio
23eadc1d00a8071b38f58232cf86bbcf141ea05f
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Dependencies can't use URL.parse

Describe the bug
Dependencies can't use URL.parse
Steps:

New vite app
Install postlight parser https://github.com/postlight/parser/
Add this code to main:

import Parser from '@postlight/parser';

Parser.parse("http://example.com").then(result => console.log(result));

Open the browser and look at the console

Expected:
Dependencies can use URL.parse
Actual:
Get this error:
Module "url" has been externalized for browser compatibility. Cannot access "url.parse" in client code. See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
Reproduction
https://github.com/ibash/vite-url-bug
Steps to reproduce
npm install
npm run dev
open the app and look at the console
System Info
System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M1
    Memory: 77.27 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.1.0 - ~/.nodenv/versions/21.1.0/bin/node
    Yarn: 1.22.17 - ~/.yarn/bin/yarn
    npm: 10.2.0 - ~/.nodenv/versions/21.1.0/bin/npm
    bun: 1.1.34 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 131.0.6778.86
    Safari: 18.0
  npmPackages:
    vite: ^6.0.1 => 6.0.1

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

url.parse is different from URL.parse. url.parse does not exist in browsers.

The library is calling URL.parse.

Oh I see, they import it. Have any suggestions on how to get vite to use the in browser URL for that module?

I'd recommend avoiding the use of that dependency. But if you need to, you can install a polyfill.


Added transform 2d header and sample

I've made a sample project to illustrate the added functionality. Please let me know if I need to make any changes!

Thanks for the feedback, I'll take a look at the matrix stack in the context of 2d and run my proposed implementation by you.


fix(region): allow contailer host update numa cpu allocate with guests running

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:
master

/lgtm


Selector changes required by Atom v1.13+

Fix for issue #2

Hi, could you merge this?
In case you're no longer maintaining this repo, I could take over.


Delete old command workflows and dead code

Description of changes:
There is probably more if we dig deeper, but I think this is good enough for a first pass.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/lgtm

/approve


Memory leak whist producing messages when broker(s) down

from #180, @chiru1205 notes:
I have noticed another memory leak issue this morning while testing a disconnect scenario.
Steps to recreate the issue

Shut down Kafka Broker(in my case local).
Use a non-serializing producer with a Delivery Handler.
Send thousands of messages to see if Delivery Handler can handle the error logging. I received error messages as expected. But memory was pushed to the limit and finally got the Access violation exception. Here is a screenshot of the memory leak.
image
I think there should be some kind of mechanism to halt message send requests if broker is not connected or down.

Well, it's not a memory leak here (memory not freed which would end up using all memory and end in OutOfMemory exception) but an AccessViolation (much worse - we are writing in an invalid space - I think we have raither release memory we shouldn't have because used in librdkafka)
Memory usage would be normal - as long as message don't timeout (default: 5 min), we won't release any memory, as it's possible the broker switch on again so we can send message. The default is very high, reducing it might be better in prod to avoid huge memory usage in this case.

@treziac  you are correct. I don't think its memory leak. ,Here is some more information, I noticed that this issue  happens(at least in my case) when queue.buffering.max.messages is increased to 2 Million messages and each of my message size is 2398 bytes. That's a lot of data. There is not enough memory to accommodate queue requirements.
Here are some configuration parameters I'm using
{"bootstrap.servers", "test"},
        {"delivery.report.only.error",true },
       {"queue.buffering.max.messages", 2000000 },
        {"queue.buffering.max.ms",100 },
        {"message.send.max.retries", 3 },
        { "debug", "all" },
        {"client.id", Dns.GetHostName()},
        {
            "default.topic.config", new Dictionary<string, object>
            {
                {"acks", "all"}, //updated to support leader & follower acknowledgments
                {"message.timeout.ms", 3000}
            }
        }

Changing the setting back to default values(100000 for queue buffer max messages) did work with any exceptions. I did a test for 6 millions messages and all 6 Million error messages came through. I may have to play with queue.buffering.max.ms to keep up with send requests.

Well, didn't see your message while editing :) Thanks for feedback!

But there is effectively problems with delivery.report.only.error and the Task ProduceAsync method.

But there is effectively problems with delivery.report.only.error and the Task ProduceAsync method.

I have removed that setting completely from the configuration and using a non serializing producer.

The growth in memory usage was initially worrying, but with the numbers mentioned above I don't think there is a problem.
The access violation seems likely caused by an OOM error which isn't being checked for in librdkafka ( and arguably shouldn't be: https://stackoverflow.com/questions/763159/should-i-bother-detecting-oom-out-of-memory-errors-in-my-c-code )

I have increased my message set size to send more messages. Changed it to 5MB and achieved more through put. I think this issue can be closed at this point.


floatingdockfixworkaround

Added support with a workaround to FloatingDock

id like to help with this tweak. I've started also but you made more progress than me, so.. i will keep in track with your changes and add my own code to fix things also, lets collaborate

id like to help with this tweak. I've started also but you made more progress than me, so.. i will keep in track with your changes and add my own code to fix things also, lets collaborate

Thanks, I've added your corrections. Any contribution is welcome.

Thanks, I'm trying to fix the upside down bug when you open a folder after unlocking the device.

I've found a partial fix for the upside down folder bug, but need to work on it
With the fix the folder is overlapping the icons below, so maybe you'll have an idea to continue the fix
I'll upload it later today

I've found a partial fix for the upside down folder bug, but need to work on it
With the fix the folder is overlapping the icons below, so maybe you'll have an idea to continue the fix
I'll upload it later today

I didn’t even understand what were talking about until I accidentally saw an open folder at the top when I tried to go into it with the tweak installed FloatingDockXVI.

Yeah, seems like there's no easy fix. Everything I did introduced another problem

So it's something with floatingdock, as I don't use regular dock I didn't tested it with it

Так что это что-то с плавающей док-станцией, так как я не использую обычную док-станцию, я с ней не проверял

I also not use a floating dock, users with ipad will have certain difficulties, they will have to wait until solution falls from heaven 😁


Fix pep8 errors

Since pep8 1.6.0 (2015-02-06) the lambda assignment throws an error:
E731 do not assign a lambda expression, use a def

This commit provides changes that are ok for latest pep8.

Coverage remained the same at 70.33% when pulling 0c78d7a416876d7c8e3dfe5d8bad85b4ca9b7dab on fix-pep8 into d0c7bccb46e15a478b31524600d7f82d238ac110 on master.


Added new resource : Learning react book

Book is added under the books section as a new resource.
name - learning react
closes the issue #183 please check @jayk-gupta

Please check the PR @jayk-gupta  I have added the resource

Can you please merge it @jayk-gupta

@jayk-gupta ??

Will it be merged @jayk-gupta

Please read this:
Important Update


in full screen

It is failing to show subtitles in full screen.Your jquery is only working solution i found so i hope you can fix for full screen:)

Also 2. lines are not showing.


[CLOSED] Bug/published dates

 Issue by Themitchell
Monday 08 December 2014 at 10:06 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/351

As the repository only pulls out the last 2 document editions there is no
garauntee that we will always have pulled out a document edition that is a
major update. Instead all documents that have been published should have
a PublicationLog entry from this point on. For any that do not have a
PublicationLog entry just fall back to the documents updated_at as before.
There is some discussion about pulling more documents from the repository
however we are worried about taking a huge hit on performance which is already an issue here.
Without a migration to create a PublicationLog for each document that doesn't currently have one, documents that are already published will continue to have their last_update touched each time they're edited, until such time as they have a major edit performed on them.

Themitchell included the following code: https://github.com/alphagov/specialist-publisher/pull/351/commits

 Comment by tommyp
Monday 08 December 2014 at 13:13 GMT

This is mostly fine, but I've just found another issue with updates in general. When a document exists in a draft state and the Editor publishes it., we generate a change note from the Publication Log, but the change note is empty. So we get:
"change_history": [
   {
      "note": null,
      "published_timestamp": "2014-12-08T13:08:39Z"
   },
]

 Comment by tommyp
Monday 08 December 2014 at 13:13 GMT

What do we want to do about this? /cc @james

 Comment by tommyp
Monday 08 December 2014 at 13:22 GMT

After chatting with Holly we think that the first change note should say "First published".

 Comment by Themitchell
Monday 08 December 2014 at 13:33 GMT

I wonder if this is a separate issue. Im not sure if this is something that should block this story. It would mean that if we want to remove any existing PublicationLogs that don't have a change note (i.e. one we previously assumed were related to minor updates) these will disappear. Which may cause us data issues.

 Comment by Themitchell
Monday 08 December 2014 at 14:25 GMT

Ok working on an alternative solution for this. Lets see if we can get that looked at and we can go live with that.

 Comment by tommyp
Monday 08 December 2014 at 13:43 GMT

We could make it a separate story, but it still blocks updates going live in general.

 Comment by Themitchell
Monday 08 December 2014 at 15:52 GMT

Closing in favour of new mechanism!


Add nicer stack traces in -c mode.

A "nice to have", but does help when debugging quite a bit.
Only enabled by default when assertions are enabled.

Why not always use Chain.track? Seems like a lot of overhead to make it optional...
This is not super perf critical. Not compiling to JS, etc...

Going to add it everywhere?


Fix Student Assessment results that appear off by 1 day in the UI

# Find most recently taken DIBELS student assessment:
dibels = Assessment.find_by_family('DIBELS').student_assessments.order(:date_taken).last

# Check date taken
dibels.date_taken
=> Fri, 01 Jan 2016

# Look up student
dibels.student

# 2016 DIBELS result not appearing on student profile! #

The record is in the database, just not making it to the UI. Going to throw it in a bunch of debugging statements and see why this isn't showing up.

puts student.dibels.order(:date_taken).pluck(:date_taken).reverse

=>
2016-01-01 00:00:00 UTC
2015-10-01 00:00:00 UTC
2015-05-01 00:00:00 UTC
2015-01-01 00:00:00 UTC
2014-10-01 00:00:00 UTC

Dates are showing up in the UI off by 1 day.
For example:
# db
2016-01-01 00:00:00 UTC

# UI
December 31st, 2015

The Problem
# js

moment("2016-01-01T00:00:00.000Z").toDate()
=> Thu Dec 31 2015 18:00:00 GMT-0600 (CST)

moment("2016-01-01").toDate()
=> Fri Jan 01 2016 00:00:00 GMT-0600 (CST)

This commit fixes the issue for DIBELS: 3e9442b88f25af2115158558a0fd782730fcdff4
Next steps are:
(A) See if this issue is affecting other types of assessments
and
(B) Plan out a more generalized solution if needed.
Not sure right now if it's best to handle this client-side or server-side.

This issue exists for STAR assessments in the student Full Case History (but interestingly not the line graphs).

This issue exists for MCAS assessments in the student Full Case History (but also not in the line graphs.)

Checking to see how JS date is computed for the line graphs as opposed to the Full Case History on the Student Profile . . .

The dates that look right are coming from serialized_data/chart_data.

Profile dates STAR, MCAS, etc are being computed using the QuadConverter; this is improperly returning dates that are one day early.
// js

QuadConverter.toMoment([2015, 2, 5, 0]);
> Moment {_isAMomentObject: true, _i: "2015-2-5", _f: "YYYY-M-D", _isUTC: true, _pf: Object…}

// js

QuadConverter.toMoment([2015, 2, 5, 0]).toDate();
> Wed Feb 04 2015 18:00:00 GMT-0600 (CST)

Looks like a timezone issue. Moment.js is subtracting 6 hours from the date in order to return a time in CST. We need to stop it from subtracting those six hours.

Fixed by #635.


Update review-database to 0.7.1

Codecov Report
Patch and project coverage have no change.

Comparison is base (e52d99c) 55.24% compared to head (36a9e12) 55.24%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   55.24%   55.24%
=======================================
  Files          45       45
  Lines        8244     8244
=======================================
  Hits         4554     4554
  Misses       3690     3690

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


Feat/update with upstream repo

Update this role with geerlingguy/ansible-role-nginx

@mtulio I see some change that you made. Can you check if this merge not brake you changes, pls?
The last 2 commits specifics.

Agreed, if it breaks something later its an incentive to upgrade there aswell :P


[FR] Option to replace new lines with spaces

Example
Input:
Both Initiator and Target
device communicate by
alternately generating their
own field

Result:
Both Initiator and Target device communicate by alternately generating their own field

Ah, it's called "merge broken paragraph"


Don't fail if bin directory exists.

CI is now green.
Not clear why the dir exists already on macos-arm. @ostera could it be that the runner does not clean between runs?


TS: global symbols search only works when TS file is opened once

I often end up in a situation where I reload the editor and fire up Cmd+T for symbol search but no symbols are found because I first have to open the typescript file to load it's extension.
I wonder if a better approach would be to simply activate each extension that is opened as editor in the workbench when doing the symbol search because the opened editor is a good sign that this is the thing I am interested in for the search.

Actually it seems to also stop working when all files are closed, which seems like a bug to me. Reported as https://github.com/microsoft/vscode/issues/92764

The TS extension does activate when it sees a tsconfig.json file, but for workspace symbol search we also needs to load a TS project. That only happens when you actually open a JS/TS file
I'm not sure we'd want to try doing this eagerly

Closing this as by-design. Starting the TS Server and loading project symbols is expensive, so require that you have one JS/TS file open before doing this


Temperature not visible in panel

When I put applet into panel, temperature is not shown, is replaced by nice, but not much useful icon. I have to click on it to see the temperature. I prefer to see temperature directly.

Sorry for the delayed response. Unfortunately I don't know why the widget displays only icon when put into the panel. Any idea how to fix it?


Add files via upload

eldor.is-cool.dev.json is added
Description
The website is simple cv website. I am going to use the subdomain for my cv website.
Link to Website
https://eldorabdukhamidov.github.io/

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA


Update specs2-core to 4.10.5

Updates org.specs2:specs2-core from 3.+ to 4.10.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

labels: test-library-update

Superseded by #20.

Superseded by #20.