Make & Camera Model not shown, content Description bleeds into those fields

Hi,
I just started using Lychee and uploaded a first bunch of photos. Exported from Adobe Lightroom with all metadata except location.
Detailed description of the problem
Lychee doesn't show content for "Make" and "Camera Model", and if there is a Description, parts of the content of that field are shown in Make and Camera Model.
Example with Description can be viewed here:
http://www.holger-pontius.de/lychee/#14686757680526/14686758015961
There are 9 photos in that album, all of them show the same issue.
exiftool shows this (before uploading):
$ exiftool IMG_5006.jpg | egrep "(Make|Camera Model|winde)"
Image Description               : Purpur-Prunkwinde
Make                            : Canon
Camera Model Name               : Canon EOS 70D
Description                     : Purpur-Prunkwinde
Caption-Abstract                : Purpur-Prunkwinde

Since exiftool shows everything fine, I think the files should be fine.
Best regards
Holger
Output of the diagnostics (Settings => Diagnostics)
Diagnostics
-----------
Warning: You may experience problems when uploading a large amount of photos. Take a look in the FAQ for details.
No critical problems found. Lychee should work without problems!

System Information
------------------
Lychee Version:  3.1.2
DB Version:      030102
System:          Linux
PHP Version:     5.6
MySQL Version:   50549
Imagick:         -
Imagick Active:  1
Imagick Version: -
GD Version:      2.1.1
Plugins:

Browser and system
OS X 10.11.5 / Safari 9.1.1, Chrome 51.0.2704.103 (64-bit)

Updated link: http://www.holger-pontius.de/lychee/#14686757680526/14688774048192

Can confirm the issue. It looks like exif_read_data returns an invalid value for Make and Model. Not sure if we can do something about it. Let me know when you find more about it.
Here's where the parsing happens in Lychee: https://github.com/electerious/Lychee/blob/master/php/Modules/Photo.php#L844

After reading the comments below here: http://php.net/manual/en/function.exif-read-data.php
and search a bit for 'Make' and 'Model' here: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/EXIF.html
... I came up with the suspicion, that the culprit might be the 'EXIF' as $sections parameter here: https://github.com/electerious/Lychee/blob/master/php/Modules/Photo.php#L827
Not tested yet, but it seems to me that IFD0 data isn't read if only 'EXIF' is given as $sections parameter. And Make an Model are part of IFD0.
I will test it eventually, but that will take quite some time.

Okay, now that I had time to check it, this is merely a duplicate of #481. Sorry for the confusion.


Support Audio Classification and Sound Event Detection

Need to at least expose a spectrogram audio feature extraction. There is code for mel spectrogram in emlearn, so that would be the primary candidate https://emlearn.readthedocs.io/en/stable/eml_audio.html
Furthermore would need to have some audio classifier models. The best models here are CNNs and RNNs. At the moment these are not supported in emlearn. But a Multi-Layer-Perceptron (https://github.com/emlearn/emlearn-micropython/issues/1) can also do a decent job. RandomForest can also be used for simple tasks.
Should also have some simple examples. The "simple audio" tutorial from Tensorflow could be a good starting point, https://www.tensorflow.org/tutorials/audio/simple_audio

There is now an emlearn_fft module included. So that is one piece of the puzzle for a spectrogram implementation.

The other pieces being a windowing function (like Hann). And a method of reduce dimensionality of FFT a bit (like mel-filters). And a computationally efficient way to do the overlapped windows, before the windowing.

There is a CNN implementation now in emlearn_tinymaix_cnn, so that provides a strong general classifier.


[ENHANCEMENT] Disk persistent storage configuration

After checking https://github.com/marqo-ai/marqo/issues/296, seems that the only way to persist the data is to run maqro-os locally, but is it possible to add a feature to mount the volume to store the data outside of container, so that we don't need to explicitly run maqro-os outside docker.
An example from Weaviate.
https://weaviate.io/developers/weaviate/configuration/persistence

just realize someone ask the same question in support,
https://community.marqo.ai/t/how-to-configure-the-persistent-storage-path/75
now I wonder can we achieve same thing without running maqro-os (running inside maqro)


mcfly: init at v0.3.1

Motivation for this change
mcfly is a very nice ctrl+r replacement that takes into account your working directory and the context of recently executed commands.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@Infinisil is it possible for you to merge this PR? I removed the part in question and it should be OK to merge now.

Yeah, can you squash the commits first?


How to configure persistent volumes when using docker ?

Environment

VerneMQ Version: 1.5
OS: Centos / Docker

Issue
I'd like to use docker image to run simple vernemq server(single instance) but I cannot find any documentation on how to configure persistent volumes for docker-compose / kubernetes. My goal is to have proper configuration of persistent directories, especially related to retained messages and persistent client sessions in case of broker restarts.

I guess it's missing in the docs but if you look into the Dockerfile (https://hub.docker.com/r/erlio/docker-vernemq/~/dockerfile/) you can find these volumes:
VOLUME ["/var/log/vernemq", "/var/lib/vernemq", "/etc/vernemq"]

/var/lib/vernemq holds the message persistence so you can map a dedicated host path there.

Thanks, that's what I was looking for. Should I leave issue open to improve documentation or close ?

Happy to accept PRs for adding a section about volumes in the readme! :)

If I understood the comments in #214, it looks like if you want to run VerneMQ in a clustered setup the only folder you need to really keep safe is /var/lib/vernemq/msgstore. Am I right @dergraf ?

@francois-travais /var/lib/vernemq/msgstore holds only the messages (qos1/2), /var/lib/vernemq/meta holds the subscriber information (clean session flag/subscriptions/...).


Fix Windows CI kernel cache

I noticed that atime is not updated in Windows by default.
This PR changes the script to generate cache from scratch and reuse it in pull-requests.

/test

/test


Loader: Allow to toggle default family filters between "include" or "exclude" filtering

Brief description
This implements #2516
It adds an extra boolean checkbox in Admin Settings for Family Filters to decide whether the filtering is to "include" what you've selected or to "exclude" what you've selected.
Like the label describes in settings it works like this:

Include: show selected families by default. Hides others by default.
Exclude: hide selected families by default. Shows others by default.

So on Exclude always all families will be enabled except for those selected in the filter. On Include, it behaves like before, only the families you select in settings are enabled by default in the Loader.
Screenshot
This is how it looks in Settings:

Testing notes:
👍 I tested it in Maya 2020 on both include and exclude mode and it worked as intended.

I would just reduce the texts. The label should be moved before the checkbox and should have just one line Include/Exclude selected families ..... I think the (OFF) and (ON) is not needed too.

I agree with @iLLiCiTiT that Exclude / Include as a label would be enough. We're designing a way to include in -situ documentation for all possible settings, so this verbose approach will be obsolete hopefully soon.

Removed the description label and reduced the checkbox label to solely Exclude / Include with commit https://github.com/pypeclub/OpenPype/pull/2541/commits/d5bae9c288221e0e1269cfa3c9eb0e77844ef19e
It now looks like this:


Incorrect documentation on overriding resource properties

The documentation on https://docs.aws.amazon.com/CDK/latest/userguide/cfn_layer.html under the section "Overriding Resource Properties" does not work. The documentation specfies:
bucketResource.propertyOverrides.analyticsConfigurations = [
    {
        id: 'config1',
        storageClassAnalysis: {
            dataExport: {
                outputSchemaVersion: '1',
                destination: {
                    format: 'html',
                    bucketArn: otherBucket.bucketArn // use tokens freely
                }
            }
        }
    }
];

Someone found you can use addPropertyOverride() though the capitalization becomes important so this block would become:
bucketResource.addPropertyOverride('AnalyticsConfigurations', [
    {
        Id: 'config1',
        StorageClassAnalysis: {
            dataExport: {
                OutputSchemaVersion: '1',
                Destination: {
                    Format: 'html',
                    BucketArn: otherBucket.bucketArn // use tokens freely
                }
            }
        }
    }
]);

Somewhat related: #1595

@Doug-AWS

When you say "does not work", what's the error message?

On it. I'm slowly replacing these hard-coded code examples with snippets (a system of adding tags within comments to identify the beginning and end of a chunk of code to put in the docs). This enables me to test my doc code examples with every release. and avoid making users feel the pain.

Fixed. See https://docs.aws.amazon.com/CDK/latest/userguide/cfn_layer.html#cfn_layer_resource_props.


Fix Perk "One Step Ahead"

The third perk in the Tactics branch, "One Step Ahead", does not work as of e1.0.5. Any chance you could patch it in?

Sure. What's the deal with it?

that perk hasn't worked correctly since the launch, almost none of the perks are working the way they are described to work if they work at all.
your supposed to have time to setup your troops and issue orders before the enemy is allowed to move. They meaning TW I don't think have ever stated how long the perk is supposed to give you to setup. I would think atleast 60 seconds. Its a Tactics Perk which is supposed to give you an edge in troop verses troop combat. The chance to order your units into formation etc.

Oh yeah, I've never seen it have any affect... I'll look into it.

I always imagined it might work something like the PBOD mod from Warband. PBOD stands for Pre-Battle-Deployment-Orders. As KenRiehle explained, it along with most of the perks in the game donesnt function. I haven't looked through the code yet myself to see if its only disabled or was never actually added in the first place.

This was never added in the first place, I've taken a look into it and have something semi functional, but its highly buggy and not really fit for purpose.
There's only two type of 'Deployments' available in the code:
'Ambush' - Not implemented
'Siege' - As we know.

This was never added in the first place, I've taken a look into it previously and have something semi functional, but its highly buggy and not really fit for purpose.
There's only two type of 'Deployments' available in the code:
'Ambush' - Not implemented
'Siege' - As we know.

Hmmmm, its strange that they wouldn't have implemented it at all. In their "Known Issues" thread on Tale Worlds Forums, Tale Worlds doesn't point out that they haven't implemented some of the perks. Instead they only say "Some perks might not be working properly."
https://forums.taleworlds.com/index.php?threads/known-issues-updated.401168/

"Some perks might not be working properly" is the understatement of the year.

I second that statement.
On Mon, Apr 6, 2020, 8:44 PM Kristoffer Skau<EMAIL_ADDRESS>wrote:

"Some perks might not be working properly" is the understatement of the
year.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Tyler-IN/MnB2-Bannerlord-CommunityPatch/issues/14#issuecomment-610109934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZ7JN6LSDDG4BYJCQJDKNLRLJZQVANCNFSM4MBYFDIQ
.


dtype of tensor map is 6

Pushed the branch dtype6 where this has happened. In the metatensor-learn test on the TorchScript API the test in file linear.py. The single_block_tensor.dtype is 6 there. Is this normal?

It's a known limitation of running TorchScript code inside Python: https://lab-cosmo.github.io/metatensor/latest/torch/reference/tensor.html#metatensor.torch.TensorMap.dtype
The fix is to do all of your dtype checking inside @torch.jit.script functions, as shown in the docs.


cannot import 'graphics' when running the DIB-R testing script

When I run python3 ./test_dibr.py under the directory "/kaolin/examples/renderers/test", there is an import error saying that there is no module called 'graphics'.
At first I supposed that it's a missing module in my computer, so I search for graphics.py in Pypi.org and install it. But the error still exist. This time it says there is no module called 'graphics.utils'. Then I suspected that maybe the graphics module required here isn't the graphics.py I installed just now. Thus I deleted all the code importing graphics and then import the DIBRenderer from kaolin.
I replaced rows 15 to 18:
import graphics
from graphics.utils.utils_perspective import lookatnp, perspectiveprojectionnp
from graphics.utils.utils_sphericalcoord import get_spherical_coords_x
from graphics.render.base import Render as Dib_Renderer

with:
from kaolin.graphics import DIBRenderer as Dib_Renderer

But it seems that there do exist other problems. Error information is below:
Drawing DIBRenderer VertexColor:   0%|                   | 0/90 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "test_dibr.py", line 90, in <module>
    main()
  File "test_dibr.py", line 83, in main
    predictions, _, _ = renderer(points=[vertices, faces[0].long()], colors=[textures])
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in __call__
    result = self.forward(*input, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/kaolin-0.1.0-py3.6-linux-x86_64.egg/kaolin/graphics/dib_renderer/renderer/base.py", line 62, in forward
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 532, in __call__
    result = self.forward(*input, **kwargs)
TypeError: forward() got an unexpected keyword argument 'colors'

After reading the original code, I revise the code at row 83:
# predictions, _, _ = renderer.forward(points=[vertices, faces[0].long()], colors=[textures])
predictions, _, _ = renderer.forward(points=[vertices, faces[0].long()], colors_bxpx3=textures)

It works well.

I am trying to run kaolin/examples/ImageRecon/Dib/train.py and run into similar problems. It looks like it is using an older version of Kaolin. I’ve tried to change the imports and interfaces but they seem to have diverged quite a bit. Can you maybe provide the commit where it was working? Thanks.

Have the same problem with running train.py for DIB-R, if anyone's able to provide a working code please do so! Thanks.

Hi, thank you for using Kaolin! The library went through a major rewrite with the version 0.9.0, and only the core library components we can thoroughly test and maintain are now part of this repository. Please refer to our latest documentation:
https://kaolin.readthedocs.io/en/latest/
Closing the bug as it is no longer relevant to this repo.


Switch from Serial.print to Log.info

Problem
Firmware currently uses Serial.print() type statements frequently.
Solution

According to https://community.particle.io/t/jsn-sr04-callback-confusion/65888/2, it is preferable to use Log.info() type statements. However, it's not as simple as just a text-based find and replace operation.
Read the docs on logging here: https://docs.particle.io/reference/device-os/api/logging/logging/
Replace Serial.print-type statements (i.e., including Serial.println, and any formatted print statements) with Log.info type statements.

@ gracelower, this would be a great next issue for you to tackle.
Recommended approach:

Fork the repo, or if you have a fork, make sure it's caught up with the main repo/branch here.
Create a branch called something like log_info
Read the issue as described above and begin wrapping in these changes. Some of the swaps from Serial.print to Log.info will be extremely quick and easy, but some where formatting is needed may present a bit more of a challenge, but I'm confident you're up to it!

@SUPScientist Sounds good - I'll get to this ASAP!

Solution for errors in Line 255:

Updated code with Log.info statements and adjusted Getting_Started instructions (in Firmware folder) to reflect these changes https://github.com/COAST-Lab/Open-Water-Level/commit/c8fbb673e3e3e8fefc8327921a47488ecf37b049

[x] Find solution to Serial.print issue; document
[ ] Change sample code in Firmware folder; upload to GH
[ ] Edit Getting-Started instructions

New proposal: combination of Serial.print + Log.info statements

Serial.print sends data locally to the serial monitor
Log.info uses a Particle logging library and is useful for viewing messages in Particle Workbench + remote monitoring
"If you want to ensure that a message is seen both locally and remotely, use both Serial.print and Log.info for the same message"

A WORK-IN-PROGRESS file was created in the Firmware > SLR_Maxbotix_... folder to house code that combines these two statement types. Resulting zeros in the data are only for battery voltage and battery level (due to the device being powered by a computer, not battery).
Please note that part of this proposal was generated in part by AI.

Everything sounds like it's on the right trajectory till this last comment that starts "New proposal." Not sure I follow. The goal is to switch completely away from Serial.print() type statements and use only Log.info() type statements, so I don't think the combo idea is what we want.
I think the issue is that I disagree with the last bullet of your AI-generated proposal

"If you want to ensure that a message is seen both locally and remotely, use both Serial.print and Log.info for the same message"

Log.info() will print to screen in my understanding.

I had initially switched all Serial.print statements to Log.info statements to eliminate all instances of Serial.print as you mentioned. The code compiled and flashed successfully, but I ran into a problem where no results were being returned at all to the serial monitor, instead simply showing the serial monitor opening and closing. When I added some of the Serial.print statements back into the code, I was able to see data in the serial monitor once more.
I will do some more research on this and refer back to the Particle Community forum for ways to navigate this issue without reinstating any Serial.print statements. Thanks!

Added SerialLogHandler logHandler; to Global objects list before void_setup(void) {

changed Serial.print statements to Log.info statements
condensed final two Serial.print statements into single line: Log.info("Sleeping for %i", seconds_to_sleep);
compiled/flashed line-by-line to check results
updated screenshot of what results should look like in serial monitor & embedded in instructions

Changes staged; will commit & submit pull request once current pull request is merged.

Pull request https://github.com/COAST-Lab/Open-Water-Level/pull/45 addresses this issue

Agreed. https://github.com/COAST-Lab/Open-Water-Level/pull/45 solves the issue. Closing. Nice work!


AwsTileRequest.get_data() doesn't work

Hi there,
I'm jsut getting into your python tool but I am not able to reproduce your Aws example.

Hi shmulik90,
you are right, the example doesn't work anymore and we found out the reason is the new version of opencv-python Python package used for reading JPEG 2000 images from file.
It was updated 2 days ago from <IP_ADDRESS> to <IP_ADDRESS> and now supports OpenCV library 3.4.1. The new version can only read 8-bit or 16-bit JPEG 2000 files and in case of Sentinel-2 tiles, which are 15-bit, just returns None.
(This is actually somewhat improvement from the previous version which read 15-bit incorrectly and we had to write additional code in sentinelhub to correct the values.)
So the solution would be that you revert your version of opencv-python library to <IP_ADDRESS> with:
pip uninstall opencv-python
pip install opencv-python==<IP_ADDRESS>

And we will update sentinelhub setup with dependency to this older version of python-opencv. Until OpenCV is improved again or we find alternative library for reading 15-bit jp2 files this solution will have to do.

We have just released sentinelhub version 2.0.2 with dependency opencv-python==<IP_ADDRESS>. With this everything should work again.
Thanks for reporting the problem.


Investigate moving locust into containers

The current load test setup runs locust directly on the host machine and additional workers need to be spawned manually.
It would be nice if we could move the cluster (main and wokers) into Docker but on first attempt we were seeing resource utilisation issues. For example, the Docker VM had access to multiple CPUs but only used one which limited locust's ability to send higher rates of requests.
Locust's example docker-compose that configures a main node and 4 workers.

Another option: we could deploy locust into k8s so that its client traffic to other k8s services appears as tcp streams between pods. OTel microservices demo does this with their own load-generator image; ours might be simpler than theirs.


Add go to specific line feature

One common way of navigating the source code is by jumping to a specific line in a file. Would've been great to have a popup, where you type a file name or a namespace name and a line number in it and the UI would jump to that. Something my-company.my-namespace:123 or my_company/my_namespace.clj:123. I'm specifically giving the example containing dots, dashes, underscores and slashes to remind about what particular annoying this that you may only have one form and the UI may only accept another and you have to manually edit it. Ideally this should accept both. We can also consider adding a jump from the currently selected line in editor as an alternative.
Discussion link: https://clojurians.slack.com/archives/C03KZ3XT0CF/p1711124000385799?thread_ts=1711119029.324069&cid=C03KZ3XT0CF.

Isn't the Quick Jump + Jump to first record here much faster than a window to type or copy->paste->format a filename and a line?
I can see this being handy as an editor integration, so a keystroke on the editor can take you there faster, and we could add it in the nrepl middleware, but then it would require specific editors plugins or setups to be useful.

Isn't the Quick Jump + Jump to first record here much faster than a window to type or copy->paste->format a filename and a line? I can see this being handy as an editor integration, so a keystroke on the editor can take you there faster, and we could add it in the nrepl middleware, but then it would require specific editors plugins or setups to be useful.

Quick jump is a great tool. So maybe this could be combined. Like that you can paste the string with the line number to jump to that line precisely. Without this I still need to manually search through the code to find something that I already have opened in my editor. And I'm also looking for a particular line of code, rather than the beginning of the test or a function which may be many lines and screens away.
Since we're talking about Quick Jump, we could also improve it:

by not showing all the anonymous functions. Those are usually concatenations of different names and numbers and most of the time you don't know which one you're looking for. I often do not see the main function that contains them because there is so many of them.
by prioritizing exact matches or supporting regexp. It is quite often that the name of the function of interest is a substring of another function or namespace name and all of those gets shown (with all of those anonymous functions). So it may be tricky to find what you're looking for when it may not even fit in the list due to list size limit and a lot of matches.

I can see this being handy as an editor integration, so a keystroke on the editor can take you there faster, and we could add it in the nrepl middleware, but then it would require specific editors plugins or setups to be useful.

Yeah, editor integration would be the best. But that requires some setup which users may not have. So it is good to have a simple alternative.

by not showing all the anonymous functions.

Yeah, we could remove all the fn--DIGIT named ones, but leave the named ones, like (fn named [] )

by prioritizing exact matches or supporting regexp

I guess it also make sense

@mrkam2 There are a couple of commits now on master that implements Action->Goto flie:line and the Quick Jump autocomplete doesn't show unnamed anonymous functions.

Nice! I'll give it a try.


when start Java warped on windows, there is a cmd window, how to hide it?

thank you for great work ! i have followed:https://github.com/dgiagio/warp/issues/51 to wrap my java program on windows 10. and i succeed to build my "exe“. but when start the ”exe“, it always started with a cmd window.  this is not elegant for my customers. i tried to hide it in the way below ,but failed, all this can do is to minimize the window.
@ECHO OFF
:: below is to minimized cmd window
if not DEFINED IS_MINIMIZED set IS_MINIMIZED=1 && start "" /min "%~dpnx0" %* && exit
SETLOCAL
SET "JAVA_EXE=%~dp0\jre\bin\java.exe"
SET "APP_JAR=%~dp0\demo.jar"
%JAVA_EXE% -jar %APP_JAR% -Djava.ext.dirs=%~dp0\jre\lib

this is the cmd i used to wrap my exe, i think the key is the param "exec", need your help~~
warp-packer.exe --arch windows-x64 --input_dir  "./bundle" --exec run.cmd --output cntvFtpClientV5.exe
thank you for tool by the way.

Hi @zenos879 ,
You could try to use javaw instead.
SET "JAVA_EXE=%~dp0\jre\bin\javaw.exe"


HUE 4.7 "'ascii' codec can't decode byte" error

Is the issue already present in https://github.com/cloudera/hue/issues or discussed in the forum https://discourse.gethue.com?
No, at least I couldn't find it
Describe the bug:
When running Hive or Impala query that contains special characters, for example çã the error is returned:
'ascii' codec can't decode byte 0xc3 in position 90: ordinal not in range(128)
Log file with more details attached. hue_47_ascii_codec_cant_decode_error.txt
The same query works without errors when executed from Hue 4.6
Steps to reproduce it?
Create table with data that contains symbols ç or ã in string fields and try to query it like this:
select * from db.table where name='Don Pelição'
The query works fine if it doesn't contain special characters.
Hue version or source? (e.g. open source 4.5, CDH 5.16, CDP 1.0...). System info (e.g. OS, Browser...).
Open source 4.7. System info - OS: Windows 10; Browsers: Firefox and Chrome.

Indeed, this is has not been working for a while. There are a few tricky unicode places to handle correctly. I faced a few of those while porting to Python 3 (in the fetch result call) and will see if possible to fix at some point.

@romainr thanks for a quick reply!
In phrase "has not been working for a while" what amount of time is meant? Just want to highlight that this problem was noticed by my team only in Hue 4.7. So we rolled back to 4.6 where queries with special characters work fine.

Indeed, I see the same with the HiveServer2 interface.
I was thinking about another issue, which is actually different:
SELECT 'fix Lỗi CS1: ngày tháng'

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

comment

we are facing the same problem. With HUE 4.8.0 some LDAP users are not able to login anymore.
Same users and same LDAP backend but Hue 4.4.0 works fine for us.
[18/Mar/2021 21:06:02 +0000] decorators   INFO     AXES: Calling decorated function: dt_login
[18/Mar/2021 21:06:02 +0000] backend      INFO     Augmenting users with class: <class 'desktop.auth.backend.DefaultUserAugmentor'>
[18/Mar/2021 21:06:03 +0000] forms        ERROR    LDAP auth error: 'ascii' codec can't decode byte 0xc3 in position 18: ordinal not in range(128)
[18/Mar/2021 21:06:03 +0000] access       WARNING  <IP_ADDRESS> -anon- - "POST /hue/accounts/login HTTP/1.1" --- Failed login for user: dummy
[18/Mar/2021 21:06:03 +0000] access       WARNING  <IP_ADDRESS> -anon- - "POST /hue/accounts/login HTTP/1.1" --- Failed login for user: dummy
[18/Mar/2021 21:06:03 +0000] decorators   INFO     AXES: New login failure by <IP_ADDRESS>. Creating access record.

Fixed as part of : https://github.com/cloudera/hue/commit/13822608d8302c04bee110e281e1f5a1b20b7fa6

Closing the issue as it has been fixed as part of https://github.com/cloudera/hue/commit/13822608d8302c04bee110e281e1f5a1b20b7fa6

This isn't been fixed for the LDAP problem in Hue 4.10 as @milletnis was writing.


fix text of clipboard button and pop-in

Changes

fixes pop-in of CodeBlocks.
fixes clipboard button text, which causes it to be cut off and have a scroll bar at the bottom. If we want to display more text here we could move the tooltip to the left and move the arrow to the right but not sure if that's worth it.

Tests
Tested locally with the mit client and a starter template.
There is one warning from the CodeBlock component that remains:
Extra attributes from the server: tabindex

The warning is caused by the Tabs component from HeadlessUI by the way

Yea I saw It happens only for the CodeBlock Tabs. I'll try fixing the leftover warning in another PR/Issue


Find and replaces occurrences of vocabulary with vue-vocabulary

Vocabulary has now been split into two repositories:

style-only library named vocabulary
Vue component library named vue-vocabulary

This split has left us with rampant misnaming throughout the project, in the HTML titles, in copy texts, in documentations and in links. These mistakes must be resolved going forward. That is the goal of this issue.

@dhruvkb Can I take this up?

@ritesh-pandey yes, please go ahead.

Next I am picking up src directory

There is one more file where we should use Vocabulary instead of CC Vocabulary. But I am not sure. @dhruvkb can you help?

Where exactly in the file?

Where exactly in the file?

First paragraph. First line.
As CC Vocabulary grows, so does the effort for maintaining code quality and keeping technical debt to a minimum. Having a set of rules makes sure that some semblance of order is maintained in the chaos that is developing and maintaining a component library.

Yeah it should be Vocabulary.

@ritesh-pandey are there any more occurrences of CC Vocabulary in the repository? Or any mislabeled occurrences of Vocabulary?

You read my mind. I was writing the same comment.
I am unable to find any more such occurrences.

Great, feel free to take up another issue. Closing.


:set equalalways not respected anymore.

As described in https://github.com/neovim/neovim/issues/6748 :set equalalways doesn't work anymore. Here's how to reproduce the bug:
vim -c "set equalalways | vs | windo sp" -c "sp | wincmd J | close"

Glacambre wrote:
Nothing changed in this area.  Please give a reproducible example.
--
Did Adam and Eve have navels?
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Sorry, I added a reproducible example by editing the issue instead of creating a new message, I forgot github didn't mail issue modifications.
Here's how the bug can be reproduced on Vim 8.0.567:
vim -c "set equalalways | vs | windo sp" -c "sp | wincmd J | close"

I tried Vim 7.3.0, Vim 7.4.0, Vim 8.0 and Vim 8.0.569 and all behave the same.

@chrisbra This is odd, the issue can be reproduced in vim according to @justinmk in this issue: https://github.com/neovim/neovim/issues/6748

I am not saying Vim is doing it right, I am just commenting to your

doesn't work anymore

And I cannot see, that this behaviour changed recently. It might still be wrong, however. It would help, if you clearly state what you expect and what you see.

Oh, sorry, I misunderstood your message.
When vim has the following window layout:
---------
¦ a ¦ b ¦
---------
¦ c ¦ d ¦
---------
¦   e   ¦
---------

I'm 90% certain that closing the 'e' window used to result in the following layout:
---------
¦ a ¦ b ¦
---------
¦ c ¦ d ¦
---------

However, with current vim, closing 'e' results in the following layout:
---------
¦ a ¦ b ¦
¦   ¦----
----¦   ¦
¦ c ¦ d ¦
---------

I think this behaviour changed within the last 3 months. I think it's a bug because according to the "equalalways" doc closing a window should resize all windows to the same size after closing a window.

Glacambre wrote:

Oh, sorry, I misunderstood your message.
When vim has the following window layout:
---------
¦ a ¦ b ¦
---------
¦ c ¦ d ¦
---------
¦   e   ¦
---------

I'm 90% certain that closing the 'e' window used to result in the following layout:
---------
¦ a ¦ b ¦
---------
¦ c ¦ d ¦
---------

However, with current vim, closing 'e' results in the following layout:
---------
¦ a ¦ b ¦
¦   ¦----
----¦   ¦
¦ c ¦ d ¦
---------

I think this behaviour changed within the last 3 months. I think it's a bug because according to the "equalalways" doc closing a window should resize all windows to the same size after closing a window.

I can reproduce it with this example.  Indeed seems wrong.
--
An SQL statement walks into a bar.  He approaches two tables
and says, "Mind if I join you?"
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

that must have been there for a very long time. From your command, I see the same behaviour with older Vims as well

Right after 'e' is closed;
     Frames
-----------------
|   A   |   B   |
| ----- | ----- |
| | a | | | c | |
| ----- | ----- |
| | b | | | d | |
| ----- | ----- |
-----------------

top-frame - A - [a, b]
          \ B - [c, d]

'A' is a parent frame of 'a' and 'b' frames
'B' is a parent frame of 'c' and 'd' frames
a, b, c, d have each window

sequence:
win_close
-> win_equal
   -> win_equal_rec

https://github.com/vim/vim/blob/06f1ed2f78c5c03af95054fc3a8665df39dec362/src/window.c#L1956-L1958
When try to adjust 'B' frame (fr is 'B'), above condition is false:

!current is false
dir is 'v'
topfr->fr_parent is NULL
new_size is equal to fr->fr_width
next_curwin is 'a', so frame_has_win(...) is false ('a' is a child of 'A')

so only 'A' and its childs are adjusted, not 'B'.
proposal of fix
Adjustment all frames always:
--- a/src/window.c
+++ b/src/window.c
@@ -2459,7 +2459,7 @@ win_close(win_T *win, int free_buf)
        check_cursor();
     }
     if (p_ea && (*p_ead == 'b' || *p_ead == dir))
-       win_equal(curwin, TRUE, dir);
+       win_equal(curwin, FALSE, dir);
     else
        win_comp_pos();
     if (close_curwin)

2017-05-16 9:14 GMT+03:00 Christian Brabandt<EMAIL_ADDRESS>
I tried Vim 7.3.0, Vim 7.4.0, Vim 8.0 and Vim 8.0.569 and all behave the
same.

I have a working vim-7.0.112 at my disposal and it does behave the same as well.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>For more options, visit https://groups.google.com/d/optout.


Cannot indicate which month is visible on open

Ideally this should be a controlled prop that would default to the current month. That way you can close the <DayPicker /> and reopen to where you were previously
My vision is that this would be a currentMonth prop on the SingleDatePicker and on the DateRangePicker that would take in a moment object. If a parent component wanted to keep track of this in the state then, they could do so using the onPrevMonthClick and onNextMonthClick callbacks.

I can take a stab at this. You still want DayPicker to own the current month in its state after mounting right? Or should currentMonth be able to dynamically change and rerender the view?

I think that the DayPicker should still own its state, so this would not be fully controlled I guess. This would just be what month is visible when you first open the datepicker. So maybe we could name it something like visibleMonthOnOpen or something? What do you think?

Ya, I was concerned that if currentMonth was a prop the parent owned after showing it would mess up all the animation goodness.
Agree with calling it visibleMonthOnOpen. If there is a date passed to the component, do you want to use that as the default month as a backup?
Order I'm envisioning: month showing on mount goes visibleMonthOnOpen || date || moment().startOf('month')?

Trying to think if it's ever expected behavior for the month to be the current month if an initial date prop was passed...

Hmmm, I feel like it should be either explicitly defined or it should be the present month. I think that maybe it's not transparent enough behavior if we fall back to the selected date (plus with the DateRangePicker, do you use startDate? endDate? I think we probably want visibleMonthOnOpen || moment().startOf('month')

sounds good!

@majapw @travisbloom fyi: https://github.com/airbnb/react-dates/pull/12/files#diff-38206f500edecedcd970973ba637f407R12

@Corei13 does that handle this use case?
If a user selects a visibleMonthOnOpen that is before minimumAllowedDate, I'm assuming they should still be taken to that month. I could add a warning to the prop type of visibleMonthOnOpen if it detects its before minimumAllowedDate?

I feel like that should be on the parent component to guarantee, not on the
DRP/SDP itself and so these should maybe be two separate changes.
On Thu, Aug 18, 2016, 6:46 PM Travis Bloom<EMAIL_ADDRESS>wrote:

@Corei13 https://github.com/Corei13 does that handle this use case?
If a user selects a visibleMonthOnOpen that is before minimumAllowedDate,
I'm assuming they should still be taken to that month. I could add a
warning to the prop type of visibleMonthOnOpen if it detects its before
minimumAllowedDate?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/issues/17#issuecomment-240906407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUdtWgRHfrhgakm8e61CWYZor6TlCK7ks5qhQrxgaJpZM4JoAzb
.

So, is there any reason why when using DRP it wouldn't just open to the month containing the startDate that was passed in?

I think that the fine tuned control of this prop allows for behavior like:

User opens date picker, navigates to 6 months in the future
User closes date picker without selecting a date
User reopens the date picker, it is still 6 months in the future

I think that while in a lot of cases, it makes sense to open to the start
date month, we want to be able to cover all options easily, especially
those cases where no date has been selected.
On Fri, Aug 19, 2016, 10:29 AM jcreamer898<EMAIL_ADDRESS>wrote:

So, is there any reason why when using DRP it wouldn't just open to the
month containing the startDate that was passed in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/issues/17#issuecomment-241050316,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUdtf7V2pArC6DcLvLNiSjzvO_fFnDAks5qhcvFgaJpZM4JoAzb
.

Sorry that is actually the case right now. What am I even talking about. :p
However it does cover @Corei13's case where when the datepicker opens, if
the allowed selectable range is not near the current month, we can still
show that month.
On Fri, Aug 19, 2016, 11:45 AM Maja Wichrowska<EMAIL_ADDRESS>wrote:

I think that the fine tuned control of this prop allows for behavior like:

User opens date picker, navigates to 6 months in the future
User closes date picker without selecting a date
User reopens the date picker, it is still 6 months in the future

I think that while in a lot of cases, it makes sense to open to the start
date month, we want to be able to cover all options easily, especially
those cases where no date has been selected.
On Fri, Aug 19, 2016, 10:29 AM jcreamer898<EMAIL_ADDRESS>wrote:

So, is there any reason why when using DRP it wouldn't just open to the
month containing the startDate that was passed in?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/issues/17#issuecomment-241050316,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUdtf7V2pArC6DcLvLNiSjzvO_fFnDAks5qhcvFgaJpZM4JoAzb
.

Good call, let me know if I can help!

@majapw so there's a use case that isn't being addressed right now and I'm wondering if we can incorporate it in this fix. I have a form that has multiple date ranges to select from. I'd like to be able to change the month the calendar opens to based off data thats constantly changing in the form.
To achieve this, we need to be able to override currentMonth on the DayPicker but still enable it to be controlled internally if the dynamic currentMonth functionality isn't needed.
This is how I'm proposing we'd tackle it, let me know your thoughts: https://github.com/travisbloom/react-dates/blob/feature/issue-17-initial-month-on-open-prop/src/components/DayPicker.jsx#L109. This means DayPicker will have to get the focused prop passed down to it.
I made it so you can't dynamically update currentMonth while the datepicker is open because that would mess up all the built in animations but this shouldnt cause any issues (still need to add stories/tests).

then if someone just wanted to set the initialMonth and let the component control all changes after that, we would use a seperate prop, maybe initialVisibleMonthOnOpen?

Another option is to overhaul the API so that animation effects are triggered by watching for the currentMonth prop to change. We'd let a HoC always control the displayed month and pressing the "next month" button would just trigger a callback that the HoC would have to use to update currentMonth.
We would trigger animations like normal if the new currentMonth is  + or - 1 month, and any other month would override the animation effect and jump to it right away.
Figured this might be a bit much API churn :/

I like initialVisibleMonth as a function that returns a moment object, so that the time of mounting, as opposed to props creation, can determine which month is visible. (Consider the clock ticking over from the 31st to the 1st)

For the sake of simplicity, I've opened a PR with the initial task completed. The more complex example of currentMonth updating based on changing props can be done in a separate ticket.
I've taken @ljharb's recommendations and made the prop a fn that gets triggered. Awaiting https://github.com/airbnb/react-dates/pull/32 to write passing tests

hmmm, so this might not be as simple as I thought. For some reason SingleDatePicker passes focused=true on render but DateRangePicker waits until the initial click

Sorry can you clarify that? Like focused is true when you first load the SingleDatePicker? Wouldn't it imply that it's open on pageload?
Also there shouldn't be any real differences between the two components, but I did write one much much later so there might be accidental differences! D:

so if you go to https://github.com/rocketrip/react-dates/blob/master/src/components/DayPicker.jsx#L82 I'm trying to set the initialVisibleMonth initially and then in componentWillRecieveProps. I'm passing the focused prop down from SingleDatePicker and DateRangePicker and when it first is set to true, using that to determine when to call initialVisibleMonth (see @ljharb's comment).
The issue is that focused will always be true on the DateRangePicker

wait scratch that sorry, didnt see DateRangePicker is using different props, let me try that again

@majapw I think its working as expected, just carelessness on my end :)
I'll reopen the PR once https://github.com/airbnb/react-dates/pull/32 goes through and I can run mount enzyme tests

Since this initial problem is solved by #70, I'm going to close this and move discussion on making the visible month a fully controlled prop to https://github.com/airbnb/react-dates/issues/48.
Thanks!

@majapw i know this is an oldie but can't find it in the docs. so basically can we get the current month with onClickNextMonth or onClickPrevMonth ? i only get the click event when using these functions

@sag1v
You can access to the currentMoment state (moment object) in your parent component by adding a ref to the date component
this.dayPicker.state.currentMonth
Day picker implementation with ref and prev/next callbacks.
 <DayPicker
    ref={(dayPicker) => { this.dayPicker = dayPicker; }}
    onPrevMonthClick={this.prevMonthClick}
    onNextMonthClick={this.nextMonthClick}
 />

But at this moment, currentMonth hasn't yet been updated (+/- 1 month) because the callback method is called before updating the state value.
@majapw
Is there a better way to get this value without adding or removing 1 month like I did ?
   nextMonthClick() {
        const newMonth = this.dayPicker.state.currentMonth.clone().add(1, 'month');
        this.setState({ currentMonth: newMonth });
    }


OpenBLAS or BLIS instead of ATLAS?

After doing some more testing with Ampere's recommended HPL setup (with an Ampere-optimized BLIS library), I would like to investigate switching away from ATLAS.
The primary motivation is build speed. I've noticed some machines can compile in an hour or two, but others take 2-3 days (especially slower systems like the Raspberry Pi 4...).
That's not especially fun, but in the past I've stuck with this method thinking it will compile ATLAS in a way that is tuned to each specific processor the best. Supposedly. (Who understands all this math that well anyway?)
I would like to compare other options like OpenBLAS or BLIS to see:

If they are able to be used easily as a drop-in replacement for ATLAS
If the performance result is affected too drastically (which would trigger me wanting to re-run HPL on all my machines, heh)

Forum user arif-ali used OpenBLAS and got 13 Gflops on the Pi 4, which beats my result of 11-ish with ATLAS: https://forums.raspberrypi.com/viewtopic.php?p=1674010#p1674010

More detail from aa3025: https://www.hydromag.eu/~aa3025/rpi/

ATLAS compile was taking absolutely forever on the big.LITTLE Orange Pi 5 RK3588s (I confirmed no throttling... not sure why it got hung up so long!). I decided to start working on this.
With OpenBLAS:
TASK [Output the results.] *********************************************************************************************
ok: [<IP_ADDRESS>] =>
  mpirun_output.stdout: |-
    ================================================================================
    HPLinpack 2.3  --  High-Performance Linpack benchmark  --   December 2, 2018
    Written by A. Petitet and R. Clint Whaley,  Innovative Computing Laboratory, UTK
    Modified by Piotr Luszczek, Innovative Computing Laboratory, UTK
    Modified by Julien Langou, University of Colorado Denver
    ================================================================================

    An explanation of the input/output parameters follows:
    T/V    : Wall time / encoded variant.
    N      : The order of the coefficient matrix A.
    NB     : The partitioning blocking factor.
    P      : The number of process rows.
    Q      : The number of process columns.
    Time   : Time in seconds to solve the linear system.
    Gflops : Rate of execution for solving the linear system.

    The following parameter values will be used:

    N      :   14745
    NB     :     256
    PMAP   : Row-major process mapping
    P      :       1
    Q      :       4
    PFACT  :   Right
    NBMIN  :       4
    NDIV   :       2
    RFACT  :   Crout
    BCAST  :  1ringM
    DEPTH  :       1
    SWAP   : Mix (threshold = 64)
    L1     : transposed form
    U      : transposed form
    EQUIL  : yes
    ALIGN  : 8 double precision words

    --------------------------------------------------------------------------------

    - The matrix A is randomly generated for each test.
    - The following scaled residual check will be computed:
          ||Ax-b||_oo / ( eps * ( || x ||_oo * || A ||_oo + || b ||_oo ) * N )
    - The relative machine precision (eps) is taken to be               1.110223e-16
    - Computational tests pass if scaled residuals are less than                16.0

    ================================================================================
    T/V                N    NB     P     Q               Time                 Gflops
    --------------------------------------------------------------------------------
    WR11C2R4       14745   256     1     4             211.86             1.0089e+01
    HPL_pdgesv() start time Thu Sep  7 10:54:22 2023

    HPL_pdgesv() end time   Thu Sep  7 10:57:54 2023

    --------------------------------------------------------------------------------
    ||Ax-b||_oo/(eps*(||A||_oo*||x||_oo+||b||_oo)*N)=   4.45732385e-03 ...... PASSED
    ================================================================================

    Finished      1 tests with the following results:
                  1 tests completed and passed residual checks,
                  0 tests completed and failed residual checks,
                  0 tests skipped because of illegal input values.
    --------------------------------------------------------------------------------

    End of Tests.
    ================================================================================

That seems low, so I'm going to re-run my OpenBLAS setup on a Pi 4 model B to see how it compares to the ATLAS library.
Note that OpenBLAS seems to support A72/A73, but doesn't have any optimizations for A76, and seems to be using the A55 optimizations since there are LITTLE cores on the RK3588s, and maybe it's only picking those up...

On the Pi 4, I'm seeing 11.679 Gflops using OpenBLAS:
ok: [<IP_ADDRESS>] =>
  mpirun_output.stdout: |-
    ================================================================================
    HPLinpack 2.3  --  High-Performance Linpack benchmark  --   December 2, 2018
    Written by A. Petitet and R. Clint Whaley,  Innovative Computing Laboratory, UTK
    Modified by Piotr Luszczek, Innovative Computing Laboratory, UTK
    Modified by Julien Langou, University of Colorado Denver
    ================================================================================

    An explanation of the input/output parameters follows:
    T/V    : Wall time / encoded variant.
    N      : The order of the coefficient matrix A.
    NB     : The partitioning blocking factor.
    P      : The number of process rows.
    Q      : The number of process columns.
    Time   : Time in seconds to solve the linear system.
    Gflops : Rate of execution for solving the linear system.

    The following parameter values will be used:

    N      :   23314
    NB     :     256
    PMAP   : Row-major process mapping
    P      :       1
    Q      :       4
    PFACT  :   Right
    NBMIN  :       4
    NDIV   :       2
    RFACT  :   Crout
    BCAST  :  1ringM
    DEPTH  :       1
    SWAP   : Mix (threshold = 64)
    L1     : transposed form
    U      : transposed form
    EQUIL  : yes
    ALIGN  : 8 double precision words

    --------------------------------------------------------------------------------

    - The matrix A is randomly generated for each test.
    - The following scaled residual check will be computed:
          ||Ax-b||_oo / ( eps * ( || x ||_oo * || A ||_oo + || b ||_oo ) * N )
    - The relative machine precision (eps) is taken to be               1.110223e-16
    - Computational tests pass if scaled residuals are less than                16.0

    ================================================================================
    T/V                N    NB     P     Q               Time                 Gflops
    --------------------------------------------------------------------------------
    WR11C2R4       23314   256     1     4             723.40             1.1679e+01
    HPL_pdgesv() start time Thu Sep  7 12:47:15 2023

    HPL_pdgesv() end time   Thu Sep  7 12:59:19 2023

    --------------------------------------------------------------------------------
    ||Ax-b||_oo/(eps*(||A||_oo*||x||_oo+||b||_oo)*N)=   3.68158083e-03 ...... PASSED
    ================================================================================

    Finished      1 tests with the following results:
                  1 tests completed and passed residual checks,
                  0 tests completed and failed residual checks,
                  0 tests skipped because of illegal input values.
    --------------------------------------------------------------------------------

    End of Tests.
    ================================================================================

(Note that it is tuned for A72...).

Using Blis... got 11.889 Gflops, nice!
ok: [<IP_ADDRESS>] =>
  mpirun_output.stdout: |-
    ================================================================================
    HPLinpack 2.3  --  High-Performance Linpack benchmark  --   December 2, 2018
    Written by A. Petitet and R. Clint Whaley,  Innovative Computing Laboratory, UTK
    Modified by Piotr Luszczek, Innovative Computing Laboratory, UTK
    Modified by Julien Langou, University of Colorado Denver
    ================================================================================

    An explanation of the input/output parameters follows:
    T/V    : Wall time / encoded variant.
    N      : The order of the coefficient matrix A.
    NB     : The partitioning blocking factor.
    P      : The number of process rows.
    Q      : The number of process columns.
    Time   : Time in seconds to solve the linear system.
    Gflops : Rate of execution for solving the linear system.

    The following parameter values will be used:

    N      :   23314
    NB     :     256
    PMAP   : Row-major process mapping
    P      :       1
    Q      :       4
    PFACT  :   Right
    NBMIN  :       4
    NDIV   :       2
    RFACT  :   Crout
    BCAST  :  1ringM
    DEPTH  :       1
    SWAP   : Mix (threshold = 64)
    L1     : transposed form
    U      : transposed form
    EQUIL  : yes
    ALIGN  : 8 double precision words

    --------------------------------------------------------------------------------

    - The matrix A is randomly generated for each test.
    - The following scaled residual check will be computed:
          ||Ax-b||_oo / ( eps * ( || x ||_oo * || A ||_oo + || b ||_oo ) * N )
    - The relative machine precision (eps) is taken to be               1.110223e-16
    - Computational tests pass if scaled residuals are less than                16.0

    ================================================================================
    T/V                N    NB     P     Q               Time                 Gflops
    --------------------------------------------------------------------------------
    WR11C2R4       23314   256     1     4             710.67             1.1889e+01
    HPL_pdgesv() start time Thu Sep  7 14:02:20 2023

    HPL_pdgesv() end time   Thu Sep  7 14:14:11 2023

    --------------------------------------------------------------------------------
    ||Ax-b||_oo/(eps*(||A||_oo*||x||_oo+||b||_oo)*N)=   3.83945609e-03 ...... PASSED
    ================================================================================

    Finished      1 tests with the following results:
                  1 tests completed and passed residual checks,
                  0 tests completed and failed residual checks,
                  0 tests skipped because of illegal input values.
    --------------------------------------------------------------------------------

    End of Tests.
    ================================================================================

On the Orange Pi 5, using Blis:
  mpirun_output.stdout: |-
    ================================================================================
    HPLinpack 2.3  --  High-Performance Linpack benchmark  --   December 2, 2018
    Written by A. Petitet and R. Clint Whaley,  Innovative Computing Laboratory, UTK
    Modified by Piotr Luszczek, Innovative Computing Laboratory, UTK
    Modified by Julien Langou, University of Colorado Denver
    ================================================================================

    An explanation of the input/output parameters follows:
    T/V    : Wall time / encoded variant.
    N      : The order of the coefficient matrix A.
    NB     : The partitioning blocking factor.
    P      : The number of process rows.
    Q      : The number of process columns.
    Time   : Time in seconds to solve the linear system.
    Gflops : Rate of execution for solving the linear system.

    The following parameter values will be used:

    N      :   14745
    NB     :     256
    PMAP   : Row-major process mapping
    P      :       1
    Q      :       4
    PFACT  :   Right
    NBMIN  :       4
    NDIV   :       2
    RFACT  :   Crout
    BCAST  :  1ringM
    DEPTH  :       1
    SWAP   : Mix (threshold = 64)
    L1     : transposed form
    U      : transposed form
    EQUIL  : yes
    ALIGN  : 8 double precision words

    --------------------------------------------------------------------------------

    - The matrix A is randomly generated for each test.
    - The following scaled residual check will be computed:
          ||Ax-b||_oo / ( eps * ( || x ||_oo * || A ||_oo + || b ||_oo ) * N )
    - The relative machine precision (eps) is taken to be               1.110223e-16
    - Computational tests pass if scaled residuals are less than                16.0

    ================================================================================
    T/V                N    NB     P     Q               Time                 Gflops
    --------------------------------------------------------------------------------
    WR11C2R4       14745   256     1     4              39.94             5.3517e+01
    HPL_pdgesv() start time Thu Sep  7 14:23:28 2023

    HPL_pdgesv() end time   Thu Sep  7 14:24:08 2023

    --------------------------------------------------------------------------------
    ||Ax-b||_oo/(eps*(||A||_oo*||x||_oo+||b||_oo)*N)=   4.07780599e-03 ...... PASSED
    ================================================================================

    Finished      1 tests with the following results:
                  1 tests completed and passed residual checks,
                  0 tests completed and failed residual checks,
                  0 tests skipped because of illegal input values.
    --------------------------------------------------------------------------------

    End of Tests.
    ================================================================================


More Details MacOutlook parameters

Hi,
the Set-CasMailbox has two paramaters namend -EwsAllowMacOutlook and -MacOutlookEnabled.
Where is the difference between those two commands? Could you give more details or refer to other documentation?
Basically both parameters just say "Outlook for Mac"
How do I know which Outlook for Mac uses EWS?
One says:

The EwsAllowMacOutlook parameter enables or disables access to the mailbox by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later).
The other:
The MacOutlookEnabled parameter enables or disables access to the mailbox by using Outlook for Mac.

I have an O365 plan and use Outlook for Mac 16.39.  Does it use EWS or not?
Do I need to disable both?
best regards
Joerg
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 54cde16c-a0fd-2dc4-762e-3e953c3cb426
Version Independent ID: eaaa07c6-4335-2fcf-6d8a-976e3589039d
Content: Set-CASMailbox (exchange)
Content Source: exchange/exchange-ps/exchange/Set-CASMailbox.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@joergrenn, both of those statements are semi-correct. EWS is used in Outlook for Mac 2011 or later. Apparently, only the New Outlook for Mac that's currently in Preview doesn't use EWS; it uses the newer 'Microsoft Sync technology' that's used in the Windows 8 and 10 mail app, and also Outlook for iOS and Android.
Further evidence is the EwsAllowMacOutlook parameter is very old (likely, it was used back in the day to allow block newer versions of Outlook for Mac vs. older versions of Entourage), while the MacOutlookEnabled parameter is quite new by comparison (added to the topic just yesterday, but likely available since ~January).

I updated the descriptions for the EwsAllowMacOutlook and MacOutlookEnabled parameters as described.
Thanks for the feedback.
Closing


Version 1.3.0 too old

Hi,
I check the release version(1.3.0) and the version committed is not the same, for example in version 1.3.0 there is no fixedSegmentWidth property.

v1.4.0 is now available.

Thank you!


nixos/duplicity: init

Add a simple module that wrap duplicity in a systemd service.
I've used this module for a while on my server. It's handy to set services.duplicity.include in multiple places of my nix configuration, next to where the directories are used. It could help other duplicity users.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Gentle ping?

Looking good thanks :)

Thanks!


New indicator: test positivity and volume from DSEW Community Profile Report

Description
This indicator generates COVID-19 test positivity and total test volume signals using the Community Profile Report (CPR) published by the Data Strategy and Execution Workgroup at https://healthdata.gov/Health/COVID-19-Community-Profile-Report/gqxm-d9w9.
The geo handling on this one is a bit different, since the CPR already includes a separate sheet for most of our geographic aggregation levels, including HHS regions, states, MSAs (a subset of CBSAs), and counties. The indicator pulls data frames from each of these sheets, rather than using our GeoMapper and risk publishing figures that don't match what was in the report.
Changelog
Itemize code/test/documentation changes and files added/removed.

run.py: thin wrapper in charge of reading params and exporting CSVs
constants.py: URLs formulae, a small configuration object for each of the geo level sheets, signals list, formula for making a full signal name out of the short name
pull.py: Figures out which reports are available, which haven't been downloaded yet, & which reports to include in the final data frames, then parses all matching reports into a data frame for each (geo, signal) combination.

Fixes

Fixes #1354

(failing test is unrelated; due to spurious network call made by validator tests and fixed in #1458)


7.6.0 Overridden Validate methode not called

Hi, just upgraded from 7.5.2 to 7.6.0 and now behaviour is changed. Overridden 'Validate' is not called anymore. The validator is applied with 'SetCollectionValidator' and 'SetValidator'.
Why override? To validate tree structure DTO object for example. Via property chain any errors are reported as a path in the tree. 'Childs[2].Childs[0].Prop'.
Is this not supported anymore?
public class FooValidator : AbstractValidator<Foo>
{
    public override ValidationResult Validate(ValidationContext<Foo> ctx)
    {
        // Create ValidationResult
        // Use InstanceToValidate in ctx
        // Modify PropertyChain in ctx
        // Add erros to validation result
    }
}

Ah i see, 'ValidateAsync' is now called, and 'Validate' is not.

It should depend on the type of validator. If it’s an async validator then ValidateAsync should be called, and if it’s a non-async validator then Validate should be called (ie it depends on which method you’re calling on the root validator)
If that’s not the behaviour you’re seeing could you put together a small sample that I could take a look at?
If that’s not what you’re

using FluentValidation;
using FluentValidation.Results;
using System.Threading;
using System.Threading.Tasks;

namespace Repro
{
    public class Program
    {
        public static void Main(string[] args)
        {
            var rootDto = new RootDto();
            rootDto.Foo = new FooDto();

            var rootValidator = new RootDtoValidator();
            var result = rootValidator.Validate(rootDto);
        }
    }

    public class RootDto
    {
        public FooDto Foo { get; set; }
    }

    public class FooDto
    {
    }

    public class RootDtoValidator : AbstractValidator<RootDto>
    {
        public RootDtoValidator()
        {
            RuleFor(o => o.Foo)
                .SetValidator(new FooDtoValidator());
        }
    }

    public class FooDtoValidator : AbstractValidator<FooDto>
    {
        public override Task<ValidationResult> ValidateAsync(ValidationContext<FooDto> context, CancellationToken cancellation = default(CancellationToken))
        {
            // Called in 7.6.0
            return Task.FromResult(new ValidationResult());
        }

        public override ValidationResult Validate(ValidationContext<FooDto> context)
        {
            // Called in 7.5.2
            var result = new ValidationResult();
            result.Errors.Add(new ValidationFailure("Prop", "Message"));
            return result;
        }
    }
}

Thanks, I should have some time on Friday to look into this.

@JeremySkinner I am seeing potentially related issues.  When I upgraded to 7.6, my unit tests verifying cases where rule.SetValidator is used have all started failing.
In my tests, I inject mocked versions of child IValidator instances into the parent validator. Mocks set up the Validate method to return a (passing) validation result. This worked great prior to 7.6, and I could test my validators in isolation, ex:
Mock<IValidator<BilingualValue>>().Validate(Arg.Any<ValidationContext>()).Returns(new ValidationResult());
Now, with 7.6, those tests that include child validators are failing, and this is the exception I see:
Initialization method Bwalk.Properties.Core.Tests.Validators.BrandValidatorSpecs+WhenBrandLogoIsNotNullAndValidatingBrandLogoOnly.SetupFixture threw exception. System.AggregateException: System.AggregateException: One or more errors occurred. ---> System.NullReferenceException: Object reference not set to an instance of an object..
    at FluentValidation.Validators.ChildValidatorAdaptor.<>c.<ValidateAsync>b__11_1(ValidationResult r)
   at System.Threading.Tasks.TaskHelpers.<>c__DisplayClass4_0`2.<Then>b__0(Task`1 t)
   at System.Threading.Tasks.TaskHelpers.ThenImpl[TTask,TOuterResult](TTask task, Func`2 continuation, CancellationToken cancellationToken, Boolean runSynchronously)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at FluentValidation.Validators.DelegatingValidator.<ValidateAsync>d__17.MoveNext()
 --- End of inner exception stack trace ---
    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at System.Threading.Tasks.Task`1.get_Result()
   at FluentValidation.Internal.PropertyRule.<Validate>d__64.MoveNext()
   at System.Linq.Enumerable.<SelectManyIterator>d__17`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at FluentValidation.Results.ValidationResult..ctor(IEnumerable`1 failures)
   at FluentValidation.AbstractValidator`1.Validate(ValidationContext`1 context)
   at FluentValidation.AbstractValidator`1.FluentValidation.IValidator.Validate(ValidationContext context)
   at Bwalk.Properties.Core.Validation.ValidatorExtensions.Validate[T](IValidator`1 validator, T instance, ValidationRuleSet[] ruleSets) in D:\Projects\Properties-API\Bwalk.Properties.Core\Validation\ValidatorExtensions.cs:line 21
   at Bwalk.Properties.Core.Tests.Validators.BrandValidatorSpecs.WhenBrandLogoIsNotNullAndValidatingBrandLogoOnly.When() in D:\Projects\Properties-API\Bwalk.Properties.Core.Tests\Validators\BrandValidatorSpecs.cs:line 149
   at Bwalk.Shared.Tests.SpecsBase`1.SetupFixture()

The first few lines of stack trace, like FluentValidation.Validators.ChildValidatorAdaptor.<>c.<ValidateAsync>b__11_1(ValidationResult r), seem to suggest that child validators perform async validations.  After further investigation based on this stack trace, and @MrGroovy second comment in particular, I changed the mock to set up ValidateAsync and my tests started passing:
Mock<IValidator<BilingualValue>>().ValidateAsync(Arg.Any<ValidationContext>()).Returns(new ValidationResult());
I would expect child validators to validate synchronously, as per parent validation method, confirmed by your earlier comment "it depends on which method you’re calling on the root validator".  I am calling the synchronous Validate, via my own extension. Snippet:
var context = new ValidationContext<T>(instance, new PropertyChain(), selector);
return validator.Validate(context);

It looks like this was a regression introduced in a recent pull request that made some improvements to the async workflow, which I missed when doing this. I’m hoping to have a new release out either tonight or tomorrow, time permitting.

This is now fixed, and I've released 7.6.100 - please download it and give it a try.
Some background information if you're interested:
Every property validator has a flag called IsAsync that indicates whether it can be run asynchronously. Child validators have this marked as true as they can contain async validators of their own.
Prior to 7.6, if you call ValidateAsync on the root validator, then all property validators that are marked with IsAsync are run asynchronously, and then all validators without this flag are run synchronously. However, if you called Validate on the root validator, all child validators were run synchronously.
A fix for a separate issue changed the behaviour of Validate so that if a child validator supports async validation, it synchronusly calls its ValidateAsync. Because child validators do support being called asynchrously, this behaviour took priority over the non-async method.
The fix was to improve the async check to only run async methods when the root validator was called Asynchronously.


[Bug Fix] Fixing rotational bug in tasks.rearrange.utils.get_camera_transform

Motivation and Context
Fixes issue #1804
How Has This Been Tested
Tested with zf/obs-wm-updates branch of habitat-llm. Following is the relevant driver code:
fixed_pose = get_camera_transform(
                    self.sim.agents_mgr._all_agent_data[0].articulated_agent,
                    camera_name=f"{curr_agent}_{camera_source}_rgb",
                )

Check fixed point-clouds generated through this method in this PR comment.
Types of changes

[Docs change] Addition or changes to the documentation
[Refactoring] Large changes to the code that improve its functionality or performance
[Dependency Upgrade] Upgrades one or several dependencies in habitat
[Bug Fix] (non-breaking change which fixes an issue)
[Development] A pull request that add new features to the habitat-lab task and environment codebase. Development Pull Requests must be small (less that 500 lines of code change), have unit testing, very extensive documentation and examples. These are typically new tasks, environments, sensors, etc... The review process for these Pull Request is longer because these changes will be maintained by our core team of developers, so make sure your changes are easy to understand!
[Experiment] A pull request that add new features to the habitat-baselines training codebase. Experiments Pull Requests can be any size, must have smoke/integration tests and be isolated from the rest of the code. Your code additions should not rely on other habitat-baselines code. This is to avoid dependencies between different parts of habitat-baselines. You must also include a README that will document how to use your new feature or trainer. You will be the maintainer of this code, if the code becomes stale or is not supported often enough, we will eventually remove it.

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated the documentation if required.
[ ] I have read the CONTRIBUTING document.
[ ] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes if required.

Based on offline conversations:

@aclegg3's concern that the current code uses value of (0, 0, 0) as an unassigned default while it is a valid setting. Should be replaced with None instead.
Let's wrap get_camera_from_link logic as a util and use it consistently in setter + getter in: habitat.tasks.rearrange.utils.get_camera_transform, kinematic_humanoid.update and manipulator.update
Add a print warning notifying change in logic and a use_deprecated_logic flag to make sure logic change does not break things for other users who depend on old logic (CC: @jimmytyyang )

@jimmytyyang @xavierpuigf Please take a look at this change as it directly touches your agent functions.


Code review for software sustainability

ICCS have conducted a code review on this repository. It is available as a google doc with public viewing permissions along with the output of an SSI Sustainability review (automated).
Code Review
SSI Checklist Review

All outputs form the code review have now been translated to issues with the code review label.


tsdoc-characters-after-block-tag not implemented in eslint plugin

Bug
eslint-ts-doc-plugin crashed when trying to lint the code below, because of the ,:
/** @deprecated, hello

This error is returned:
> npm run lint --cache
npm WARN invalid config cache=true
npm WARN invalid config Must be a valid filesystem path

><EMAIL_ADDRESS>lint /Users/guillaumeclochard/Downloads/a
> eslint src --ext .js,.jsx,.ts,.tsx

TypeError: context.report() called with a messageId of 'tsdoc-characters-after-block-tag' which is not present in the 'messages' config: {
  "error-loading-config-file": "Error loading TSDoc config file:\n{{details}}",
  "error-applying-config": "Error applying TSDoc configuration: {{details}}",
  "tsdoc-at-sign-in-word": "tsdoc-at-sign-in-word: {{unformattedText}}",

...

Full error here: https://github.com/guillaumewuip/eslint-tsdoc-error-example/pull/2
Reproduction repo here: https://github.com/guillaumewuip/eslint-tsdoc-error-example
Expected behavior
No crash. Either the correct tsdoc-characters-after-block-tag message is used for this lint error, or something more generic like "TSDoc unknown error message" ?

Quick remedy until fixed, use exact version "0.1.1".

This fix was released with tsdoc version 0.12.19 and eslint-plugin-tsdoc version 0.2.4.


feat: add marketmaker module

Description

closes: #320
Tasks

[x] spec
[x] skeleton
[x] core logics
[x] proposal
[x] test codes
[x] validation
[x] cli
[x] invariant
[x] simulation

References

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Appropriate labels applied
[ ] Targeted PR against correct branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

@hallazzang Thanks for the review, all of the suggestions applied on https://github.com/cosmosquad-labs/squad/pull/353


Suggest users to use iDeep4py v1 for now

Refs #4933.
iDeep4py v2 seems to have different API than v1, and it also has a separate package for AVX2 environment and AVX512 environment.

Jenkins CI test (for commit 53ce9d9a21ec7043962d018a6311f69e0b6e22f8) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Once https://github.com/chainer/chainer/pull/4933 is merged to chainer, iDeep1.* will not be supported anymore.

Once, we will merge this.
Cloud you fix this tips in your PR? @mingxiaoh

Jenkins CI test (for commit 53ce9d9a21ec7043962d018a6311f69e0b6e22f8) succeeded without errors!


Copy menu command is disabled when emacs is running in a terminal

Hello Steve - when using this config with emacs -nw (sans window system), I cannot then use the terminal's edit/copy menu command to copy a selection of text to the clipboard. The menu command becomes greyed out. However, if I quit emacs, then the copy menu command is restored.  Or, if I blow away emacs config with  rm -rf ~/.emacs.d,   copy functionality is restored to emacs sessions.
M-x version says: 'GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu) of 2021-02-08'. I get the emacs package from Homebrew for what that's worth. Problem exhibited on two Linux boxes and on a macbook pro under the iTerm terminal program. Changing Linux terminal applications has no effect on this problem.
Otherwise your config is excellent I really appreciate the work you have put into it.  But this clipboard issue is a nuisance to me, I wonder if you would take a look.
Thanks

Yeah, I think that's because the terminal emacs app itself supports clipboard terminal escape sequences. IIRC I've turned off xterm-mouse-mode in terminals previously so that when I select some text with the mouse, it's the terminal emulator controlling the highlight and selection rather than Emacs. But then of course there's no seamless copy/paste across Emacs/OS with Emacs keys.

Maybe you'd like to try the osx-clipboard package and see if it helps.

(For my part, I rarely use Emacs in a terminal, preferring a long-running GUI app. )

Also the clipmon package looks promising, for Linux + MacOS support.

Thanks Steve -- I've found a crude workaround by just commenting out (xterm-mouse-mode 1)  in lisp/init-xterm.el.
Is there a way this could be made an option in a local dotfile or the like?

Thanks Steve -- I've found a crude workaround by just commenting out (xterm-mouse-mode 1) in lisp/init-xterm.el.

Yeah, that would do it.

Is there a way this could be made an option in a local dotfile or the like?

I need to think about whether the current default is the best, but in the meantime you'd need to locally modify the config, or maybe putting (remove-hook 'after-make-console-frame-hooks 'sanityinc/console-frame-setup) in init-local.el would do the trick.

Thanks Steve.  Sounds like you have a better solution in mind so I will leave this open for now, but in the mean time, yes your suggestion  of  (remove-hook 'after-make-console-frame-hooks 'sanityinc/console-frame-setup) does the trick. Maybe this will be of use to other terminal users out there who are fans of yours. I can't be the only one!


Add support for TCP and Docker health checks (v0.6.0)

Issue: #82
This PR adds support for TCP and Docker health checks via HTTP API exposed by Consul v0.6.0.
Tests have not been updated as this requires update of consul binaries used in test. 0.5.2 -> 0.6.0 is a breaking update.

@cablehead upgrading to v0.6.0 breaks a few tests. Not sure how you want to handle those, do you prefer maintaining compatibility or just support latest release?

Thinking if we do a full minor version tick, to 0.5, we can upgrade the
binary in the test folder and target 0.6 from that version on.
On Fri, Dec 25, 2015 at 10:14 PM, Arun Babu Neelicattu <
<EMAIL_ADDRESS>wrote:

@cablehead https://github.com/cablehead upgrading to v0.6.0 breaks a
few tests. Not sure how you want to handle those, do you prefer maintaining
compatibility or just support latest release?
—
Reply to this email directly or view it on GitHub
https://github.com/cablehead/python-consul/pull/86#issuecomment-167283931
.

@cablehead so I am guessing you are okay with not maintaining compatibility with consul < 0.6.0 ?

Yeah, I think so. The 0.4.* versions of python-consul will still be
available, and if there's anything important that needs an update we can do
a patch release.
Do you have any concerns?
To save confusion we could bump this next version of python-consul up to
0.6, to match Consul releases.
On Mon, Dec 28, 2015 at 7:09 PM, Arun Babu Neelicattu <
<EMAIL_ADDRESS>wrote:

@cablehead https://github.com/cablehead so I am guessing you are okay
with not maintaining compatibility with consul < 0.6.0 ?
—
Reply to this email directly or view it on GitHub
https://github.com/cablehead/python-consul/pull/86#issuecomment-167708515
.

No issues, patch release sounds good. Just wanted to make sure. :)

Sorry for the delay in getting to this @abn. It's been a busy new year! This looks great. Merging!

Uploaded to pypi as v0.6.0


Implemented event_data_template

Description:
Implemented event_data_template within scripts. This can be used to create custom triggers or
pass data to other scripts. A good use case (mine) would be to pass custom data to an appdaemon app.
Related issue (if applicable): fixes #N/A
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#4180
Example entry for configuration.yaml (if applicable):
script:
  set_timer:
    sequence:
      - event: APP_SET_TIMER
        event_data_template:
          name: '{{ name }}'
          hours: '{{ hours }}'
          minutes: '{{ minutes }}'
          seconds: '{{ seconds }}'

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Thx for this functionality, I'll be waiting for it in release =)

@balloob Sorry, I got over my frustration and moved this into template.py. Added tests for lists and dicts as items and referencing specific elements so this should be all set.


Dead link https://www.microsoft.com/licensing/product-licensing/products.aspx

Found in subscriptions//TOC.md

@nschonni Thanks for reporting this; we have this in our queue to fix.
@evanwindom Is this something that you can attend to? It's the "Volume License and Product Use Rights (PUR)" link in the Resources section of the TOC. If so, please let us know whence it's fixed by commenting as such in this GitHub Issue.
@prrana FYI.

Changed link in TOC to point to a new licensing terms page.  Added to PR.


chore: upgrade charts

updated chart jx3/bucketrepo from 0.1.61 to 0.1.62
updated chart jx3/jx-build-controller from 0.2.7 to 0.2.8

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rajdavies
You can assign the PR to them by writing /assign @rajdavies in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Allow per parser syntax overrides

For example, suppose I want to enforce a syntax like foo=3 bar=v everywhere instead of the default --foo 3 --bar v. Instead of attributing every single case of the union type with EqualsAssignment; AltCommandLine I'd like to do it on the type level or as a configuration argument to UnionArgParser.Create.
May give it a shot if you think it's a good idea.

Easy. Just put the attributes on the type and all branches will inherit them.

Ok, that works for the EqualsAssignment but not for getting rid of the --. Right?

Right.

Probably what you need is an attribute that changes the CLI parameter name generation rules, for example DropCLIDashPrefixAttribute or CustomCLIPrefixAttribute.

Yes, something like that.

Up for discussion; opine freely ;)

Also, this https://github.com/nessos/UnionArgParser/blob/master/src/UnionArgParser/ArgInfo.fs#L278 needs a true passed in for EqualsAssignmentAttribute on the type to work.

Sorry, not sure I got that.

I want to put EqualsAssignmentAttribute on the type, to apply it to all union cases. This currently does not work because the optional argument to GetAttrs in that line of code needs to be true - at least. Haven't had time to check if that really fixes it.

Ok, I see it now. Fixed.

I pushed a nuget package containing the feature.


Fix UtilsCubemap compilation error in Ubuntu 22.04

I just added a single missing #include <cstdio> for a printf in shared/UtilsCubemap.cpp: it now correctly builds on Ubuntu 22.04.

@ghidosoft Thank you!


Testnet caution added

Using the testnet endpoint does not work with websockets, returning error 426.
Added short warning about that at the beginning.

Hi @tnguyen42 - The websocket API should be working on the BigchainDB Testnet. If it's not, then let us know and we'll make efforts to fix it. One way to let us know is to post a comment in one of our Gitter chat rooms, such as https://gitter.im/bigchaindb/bigchaindb

I have tested and the websocket is working. Please use the following code.
const WebSocket = require('ws');

let ws_url = 'wss://test.bigchaindb.com:443/api/v1/streams/valid_transactions'

startWebSocketListener()
function startWebSocketListener() {
    const ws = new WebSocket(ws_url, {origin: 'http://localhost:9985'});

    ws.on('open', function open() {
        console.log('web socket connected')
    })

    ws.on('close', function close() {
        console.log('web socket disconnected')
    })

    ws.on('message', function incoming(data) {
        console.log('Message recieved:', data.toString())
    })
}

Thank you @ttmc !

Oh sorry, I assumed the testnet was blocking websockets in order to prevent overloading from clients. I'm gonna try your code @manolodewiner !

@manolodewiner It seems like the websockets only works with ssl. That was my mistake. Shouldn't it be indicated in the documentation? Also, the connection object is named "conn" when connected to a local node and "bdb" when connected to the testnet.
Those are little things... But it could avoid some people to waste some time on details.


Docker

https://packages.ubuntu.com/xenial/docker.io
https://packages.ubuntu.com/xenial/docker-compose
https://apps.fedoraproject.org/packages/docker
https://apps.fedoraproject.org/packages/docker-compose
https://packages.debian.org/buster/docker.io
https://packages.debian.org/stretch/docker-compose

@Vuwij are you intentionally adding keys for the docker package in Stretch and Xenial which is described as a "System tray for KDE3/GNOME2 docklet applications" and is not related to the Moby/Docker project?

Is it correct now?

@tfoote @nuclearsandwich should it be ok now?

bump


webapp: improve the help of 'az webapp log tail/download'

Fix #3600

[x] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[x ] Each command and parameter has a meaningful description.
~- [ ] Each new command has a test.~

(see Authoring Command Modules)

Codecov Report

Merging #3624 into master will decrease coverage by 0.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3624      +/-   ##
==========================================
- Coverage   71.62%   71.47%   -0.16%
==========================================
  Files         420      420
  Lines       26209    26211       +2
  Branches     3968     3968
==========================================
- Hits        18773    18734      -39
- Misses       6258     6297      +39
- Partials     1178     1180       +2

Impacted Files
Coverage Δ

...ice/azure/cli/command_modules/appservice/custom.py
73.41% <ø> (-0.25%)
:arrow_down:

...ce/azure/cli/command_modules/appservice/_params.py
97.18% <100%> (ø)
:arrow_up:

...vice/azure/cli/command_modules/appservice/_help.py
100% <100%> (ø)
:arrow_up:

...cli-core/azure/cli/core/commands/_introspection.py
83.11% <0%> (-11.69%)
:arrow_down:

...d_modules/azure-cli-interactive/azclishell/util.py
56.25% <0%> (-6.25%)
:arrow_down:

.../azure/cli/command_modules/resource/_validators.py
65.21% <0%> (-4.35%)
:arrow_down:

...-cli-acs/azure/cli/command_modules/acs/_actions.py
51.92% <0%> (-3.85%)
:arrow_down:

src/azure-cli-core/azure/cli/core/_session.py
67.27% <0%> (-3.64%)
:arrow_down:

...-testsdk/azure/cli/testsdk/recording_processors.py
51.11% <0%> (-2.23%)
:arrow_down:

.../azure/cli/command_modules/keyvault/_validators.py
71.52% <0%> (-1.33%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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


Update Export scripting test

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
The Export unit test for Routing and Faulting was failing after the high-level scripting APIs were added. This change updates the exported data used to compare with the data returned by the scripting API.
Why should this Pull Request be merged?
Update the scripting test to pass.
What testing has been done?
Ran tests in dev environment with LabVIEW and VeriStand 2017

This test is still failing on my machine, which makes me think we have different VI packages installed. This is concerning, because I'm questioning what version of these packages we have installed on the build machine.
Can you validate that you have the same versions of the packages as listed in this pull request (which is what I have installed)? https://github.com/ni/niveristand-routing-and-faulting-custom-device/pull/167
It does not look like that is what is currently being hosted in the list of packages used by the build machine...

The test as it exists on master passes on my machine. I think the test asset was updated correctly, but the ATS and build machines (and your dev VM) are using outdated versions of the advanced sysdef resources.

Thanks @buckd for doing some rapid testing to help figure out what was going on!
The TL;DR appears to be that this pull request can be closed, and that we don't have anything to worry about (although that's not the case at first glance, and we got lucky) other than updating the files we are installing on the build and test machines.

It looks like the 19.2 release was built against ni_lib_advanced_sysdef_api-<IP_ADDRESS>.vip, which was created as a workaround when the source for the Advanced SysDef repository had moved to LabVIEW 2019. This release included new support for preserving item order.
When the Advanced SysDef repository was moved to 2019, some additional changes were made to the repo to handle relative paths. When the changes to preserve item order were merged after the 2019 source was saved-for-previous, this was exported as ni_lib_advanced_sysdef_api-<IP_ADDRESS>.vip, which is what the tests were created with.
In the <IP_ADDRESS> case (and <IP_ADDRESS>), TreeItem.Property.Get.vi uses an empty variant as the value for an attribute to indicate that the string is actually a path. In <IP_ADDRESS>, a bool is used as the value of the attribute, and the bools value indicated whether it is a relative path. Fortunately, the variant used by <IP_ADDRESS>/<IP_ADDRESS> should be handled correctly by <IP_ADDRESS>.
This means that the 19.2 release was built against a slightly mystery-meat version of the Advanced SysDef API. Luckily, it appears to be internally consistent, and the version we intended to build with and should build with moving forward (<IP_ADDRESS>) is backwards compatible.
We should define a better process for updating the package versions, so this doesn't happen again. We should also do some sanity testing, to confirm what I wrote is actually correct.

The build machines and my test VM are updated with the correct VI Package versions. The test now passes as it exists in master, so closing this PR.


v1.8 backports 2020-10-06

#13319 -- Automatic rate limiting of endpoint API calls (@tgraf)

Note: This PR includes several commits from @christarazi created in #13392 for the v1.7 backports.
It also includes an additional commit to document the added --enable-api-rate-limit option.

#13397 -- Fix Azure IPAM regression (@tgraf)
#13401 -- pkg/option: re-introduce conntrack-gc-interval flag (@aanm)

Once this PR is merged, you can update the PR labels via:
$ for pr in 13319 13397 13401; do contrib/backporting/set-labels.py $pr done 1.8; done

test-backport-1.8

Note: This PR includes several commits from @christarazi created in #13392 for the v1.7 backports.

It also includes an additional commit to document the added --enable-api-rate-limit option.

Do we need to forwardport these?

@pchaigno https://github.com/cilium/cilium/pull/13422

Do we need to forwardport these?

I don't believe so, as far as I understand the opt-in behaviour was added to limit the risks related to new features in v1.7/v1.8, but looking at how it works (Documentation/configuration/api-rate-limiting.rst), the default configuration parameters do not seem to enforce rate limiting (rate-limit: None), so you already have to “opt-in” somehow.


Update ios version and xcode version, can not run any more.

Hi, I just update my ios version to 11.3, my bad!
So I also update xcode to match my iphone, and I got some error like: "Module compiled with Swift 4.0.3 cannot be imported in Swift 4.1".
And I also got some error in Layer.swift:"Type of expression is ambiguous without more context"
or "'MPSRectNoClip' is only available on iOS 11.0 or newer".
Could you please help me to fix this problem?
Thank you!

A screenshot of one error.

I don't know about that first error (do a clean build?) but the others have been fixed so if you pull in the latest changes that should work again.

Thank you. I already fix this problem.


v0.3.8 and v0.3.10 don't detect gfx1103 (AMD RadeonT 780M)

What is the issue?
v0.3.8 and v0.3.10 don't detect gfx1103 (AMD RadeonT 780M) but still using CPU

However v0.3.6 detects gfx1103 and uses GPU well

OS
Windows
GPU
AMD
CPU
AMD
Ollama version
0.3.8, 0.3.10

That's a bug relate to drivers /amdhip64_6.dll which support rocm6.1.2 some drivers can not pick it up . and there are several version of it . make sure get the latest drivers . and try the solution https://github.com/likelovewant/ollama-for-amd/issues/18

I followed the steps in the bug but didn't help.
Please advise if I have missed something from below steps

Download ollama-windows-amd64.7z from https://github.com/likelovewant/ollama-for-amd/releases/tag/v0.3.11
unzip the file in "C:\Program Files\ollama"
Move all "C:\Program Files\ollama\lib\ollama*.dll" to "C:\Program Files\ollama\lib\ollama\runners\rocm_v6.1"
Move a folder "C:\Program Files\ollama\lib\ollama\rocblas" to "C:\Program Files\ollama\lib\ollama\runners\rocm_v6.1"
So now I have all *.dll and rocblas folder moved in "C:\Program Files\ollama\lib\ollama\runners\rocm_v6.1"
Execute "C:\Program Files\ollama\ollama.exe serve" to start ollama server

FYI, I have HIP SDK 6.1.0 installed on my Windows 11 and HIP_PATH, HIP_PATH_61 environment variable configured

1,The directory is in C:\Users\usrname\AppData\Local\Programs\Ollama\: rather than  "C:\Program Files\ollama\
2, it's recommend to install or update ollama via OllamaSetup.exe rather than ollama-windows-amd64.7z since
3, make sure you had latest drivers also.

Thanks for your assistance and now my issue is resolved after updating with latest AMD Driver. v0_3_11 uses gfx1103 now